WO2018232759A1 - 实现业务连续性的方法、设备及系统 - Google Patents

实现业务连续性的方法、设备及系统 Download PDF

Info

Publication number
WO2018232759A1
WO2018232759A1 PCT/CN2017/089859 CN2017089859W WO2018232759A1 WO 2018232759 A1 WO2018232759 A1 WO 2018232759A1 CN 2017089859 W CN2017089859 W CN 2017089859W WO 2018232759 A1 WO2018232759 A1 WO 2018232759A1
Authority
WO
WIPO (PCT)
Prior art keywords
function entity
user plane
entity
session management
terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/089859
Other languages
English (en)
French (fr)
Inventor
孙德奎
周汉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CN202110430101.2A priority Critical patent/CN113286376A/zh
Priority to BR112019027767-6A priority patent/BR112019027767A2/pt
Priority to PCT/CN2017/089859 priority patent/WO2018232759A1/zh
Priority to KR1020197038993A priority patent/KR102364802B1/ko
Priority to CN201780091279.0A priority patent/CN110679192B/zh
Priority to JP2019570991A priority patent/JP6961730B2/ja
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP17914804.4A priority patent/EP3637926B1/en
Priority to EP21200831.2A priority patent/EP4002921B1/en
Publication of WO2018232759A1 publication Critical patent/WO2018232759A1/zh
Priority to US16/716,049 priority patent/US11115876B2/en
Anticipated expiration legal-status Critical
Priority to US17/397,056 priority patent/US11871283B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H04W36/185—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection using make before break
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, device, and system for implementing business continuity.
  • next generation mobile communication system next generation system
  • 5G fifth generation
  • the 5G network architecture defines an ultra-reliable low latency communication (URLLC) scenario, which mainly includes services such as driverless, industrial automation, etc. that require low latency and high reliability.
  • URLLC ultra-reliable low latency communication
  • TS 22186 stipulates that the end-to-end delay between the terminal and the server needs to be kept within 5 ms in the remote driving scenario.
  • AS application server
  • the terminal is in a high-speed state, there is a scenario in which the user plane function (UPF) entity and the AS switch.
  • UPF user plane function
  • ULCL uplink classifier
  • PDU packet data unit
  • the embodiments of the present application provide a method, device, and system for implementing service continuity, which can ensure continuity of services in a handover process.
  • a method for implementing service continuity comprising: a session management function entity selecting a destination user plane function entity as a terminal service; a session management function entity sending a first message to a control device; the session management function entity receiving Controlling, by the first application server AS of the device, the session management function entity, according to the indication information of the first AS, sending a first routing rule to the destination user plane function entity, where the first routing rule includes: The data of the address of the AS is sent to the first AS.
  • the session management function entity can receive the indication information from the first AS, and according to the indication information of the first AS, to the destination user.
  • the function entity sends the first routing rule, so that the destination user plane function entity can transmit the service data according to the first routing rule, so that the continuity of the service in the process of switching the user plane function entity can be ensured.
  • the first routing rule is to send data of the address whose destination address is the first AS to the first AS
  • the destination user plane function entity can be prevented from routing the data addressed to the address of the first AS to the remote data.
  • the problem is that the network then routes to the first AS, so that the path from the terminal to the first AS is the shortest and the delay is controllable.
  • the method further includes: the session management function entity to the destination The user plane function entity sends a second routing rule, where the second routing rule includes: sending the data whose destination address is the address of the second AS to the source user plane function entity, where the second AS is the AS currently serving the terminal.
  • the source user plane function entity is a user plane function entity that is in communication with the second AS.
  • the method further includes: the session management function entity sends the first path information to the destination user plane function entity; and the session management function entity sends the source user plane function The entity sends the second path information, where the first path information and the second path information are used to establish a forwarding path between the destination user plane function entity and the source user plane function entity. Based on the scheme, a forwarding path between the target user plane functional entity and the source user plane functional entity can be established.
  • the method further includes: the session management function entity sends a third routing rule to the destination user plane function entity, where the third routing rule includes: the destination address is The data of the address of the first data network is sent to the remote user plane function entity, wherein the remote user plane function entity is a user plane function entity that is in communication with the first data network.
  • the routing user rule of the service data of the address of the first data network exists in the destination user plane function entity after the handover, and thus may occur in the user plane function entity. Maintain the continuity of the service when switching.
  • the method further includes: the session management function entity sends the third path information to the destination user plane function entity; and the session management function entity faces the remote user.
  • the function entity sends the fourth path information, where the third path information and the fourth path information are used to establish a forwarding path between the target user plane function entity and the remote user plane function entity. Based on the solution, a forwarding path between the target user plane functional entity and the remote user plane functional entity can be established.
  • the method further includes: the session management function entity sends a second message to the destination user plane function entity, where the second message is used to request to delete the second message. Routing rules. That is to say, in the case that the path on the network side is ready to be completed, the routing rule corresponding to the old service in the functional entity of the target user plane can be released.
  • the method further includes: the session management function entity sending a third message to the destination user plane function entity, where the third message is used to request to delete the first Path information. That is to say, in the case that the network side path is ready to be completed, the path information corresponding to the old service in the target user plane function entity may be released.
  • the method further includes: the session management function entity sends a fourth message to the source user plane function entity, where the fourth message is used to request to delete the source user.
  • the user plane information corresponding to the terminal in the function entity the user plane information including the second path information. That is to say, in the case that the network side path is ready to be completed, the user plane information corresponding to the terminal in the source user plane function entity may be released.
  • the method further includes: the session management function entity sends the fifth path information to the target base station; and the session management function entity sends the The six-path information, where the five-path information and the sixth path information are used to establish a forwarding path between the destination base station and the source user plane functional entity, where the source user plane function entity is to establish a first packet data unit with the terminal.
  • the session management function entity selects the destination user plane function entity as the terminal service, and the method includes: the session management function entity sends a fifth message to the terminal, where the fifth message is used to request to establish a second PDU session; and the second PDU session is established.
  • the session management function entity selects the destination user plane function entity to serve the terminal. Based on the solution, the session management function entity can select the destination user plane function entity as the terminal service.
  • the method further includes: the session management function entity sends a sixth message to the terminal, where the sixth message is used to request to release the first PDU session. That is to say, in the case that the network side path of the new PDU session is ready to be completed, the old PDU session resource can be released.
  • the method further includes: the session management function entity sending a seventh message to the control device, where the seventh message is used to request the terminal to be the second The AS switches to the first AS, where the second AS is the AS currently serving the terminal. Based on this scheme, the terminal can be caused to switch from the second AS to the first AS.
  • the method further includes: the session management function entity receiving an eighth message from the control device, where the eighth message is used to indicate that the terminal has been switched from the second AS to the second AS First AS.
  • the control device can know in time whether the AS is completed, and then perform subsequent operations in time.
  • the first message includes at least one of location information of the target user plane function entity and location information of the terminal, and at least one of location information of the destination user plane function entity and location information of the terminal is used for
  • the AS determined to serve the terminal is the first AS.
  • the control device can determine the AS serving the terminal according to the first message.
  • the indication information of the first AS includes the location information of the first AS, or the identifier information of the first AS, or the information indicating that the AS has not changed, which is not specifically limited in this embodiment of the present application.
  • a second aspect a method for implementing service continuity, the method comprising: a control device receiving a first message from a session management function entity; and a control device transmitting, to the session management function entity, indication information of the first application server AS, the The indication information of an AS is used to indicate that the session management function entity sends a first routing rule to the destination user plane function entity, where the first routing rule includes: sending data of the address whose destination address is the first AS to the first AS.
  • the session management function entity may receive the indication information from the first AS, and according to the indication information of the first AS, to the destination
  • the user plane function entity sends the first routing rule, so that the destination user plane function entity can transmit the service data according to the first routing rule, so that the continuity of the service in the user plane function entity switching process can be ensured.
  • the first routing rule is to send data of the address whose destination address is the first AS to the first AS
  • the destination user plane function entity can be prevented from routing the data addressed to the address of the first AS to the remote data.
  • the problem is that the network then routes to the first AS, so that the path from the terminal to the first AS is the shortest and the delay is controllable.
  • the first message includes at least one of location information of the target user plane function entity and location information of the terminal, and at least one of location information of the destination user plane function entity and location information of the terminal is used for
  • the AS determined to serve the terminal is the first AS.
  • the control device can determine the AS serving the terminal according to the first message.
  • the method further includes: the control device receives a seventh message from the session management function entity, where the seventh message is used to indicate that the terminal is from the second AS Switching to the first AS, where the second AS is an AS currently serving the terminal; and the control device switches the terminal from the second AS to the first AS according to the seventh message. Based on this scheme, the terminal can be caused to switch from the second AS to the first AS.
  • control device comprises a communication V2X control function entity between the vehicle and the outside world.
  • a session management function entity having the functionality to implement the method described in the first aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a fourth aspect provides a session management function entity, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the session management function entity In operation, the processor executes the computer-executable instructions stored by the memory to cause the session management function entity to perform the method of implementing business continuity as described in any of the first aspects above.
  • the embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores instructions, when executed on a computer, to enable the computer to perform any one of the foregoing first aspects.
  • an embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, to cause a computer to perform the method for implementing business continuity according to any of the above first aspects.
  • a control device having the function of implementing the method of the second aspect described above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a control device including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the control device is running, The processor executes the computer-executable instructions stored by the memory to cause the control device to perform the method of implementing business continuity as described in any of the above second aspects.
  • a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform business continuity of any of the above second aspects Methods.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of achieving business continuity of any of the above second aspects.
  • a method for implementing service continuity comprising: a session management function entity selecting a destination user plane function entity as a terminal service; the session management function entity sending a first message to the control device, the control device receiving the session from the session a first message of the management function entity; the control device sends the indication information of the first application server AS to the session management function entity, the session management function entity receives the indication information of the first AS from the control device; and the session management function entity is configured according to the first AS
  • the indication information is sent to the destination user plane function entity, where the first routing rule includes: sending the data whose destination address is the address of the first AS to the first AS.
  • a twelfth aspect a control system for implementing business continuity, comprising the control device of any of the preceding aspects, and the session management function entity of any of the above aspects.
  • FIG. 1 is a schematic structural diagram 1 of a system for implementing service continuity according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram 2 of a system for implementing service continuity according to an embodiment of the present application
  • FIG. 3 is a schematic structural diagram 3 of a system for implementing service continuity according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart 1 of a method for implementing service continuity according to an embodiment of the present disclosure
  • FIG. 6 is a second schematic flowchart of a method for implementing service continuity according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart 3 of a method for implementing service continuity according to an embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart 4 of a method for implementing service continuity according to an embodiment of the present disclosure
  • FIG. 9 is a schematic flowchart 5 of a method for implementing service continuity according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram 1 of a session management function entity according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram 2 of a session management function entity according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram 1 of a control device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram 2 of a control device according to an embodiment of the present application.
  • the tunnel in the embodiment of the present application includes a Next Generation (N) interface 3 (N3 for short) N3 tunnel and an N interface 9 (N9 for short) tunnel.
  • the N3 tunnel is a tunnel between the access device (such as a base station) and the UPF entity; the N9 tunnel is a tunnel between the UPF entity and the UPF entity.
  • an N3 tunnel is a tunnel of a session granularity, and an N9 tunnel may be a tunnel of a session granularity or a tunnel of a device granularity.
  • the session granularity tunnel refers to a tunnel resource established for a PDU session, and the tunnel is used only for one PDU session.
  • a tunnel with a session granularity includes only one routing rule, and only the routing rule can forward data to the tunnel.
  • the lifetime of the tunnel of the session granularity is the lifetime of a PDU session. That is, when a PDU session disappears or is released, the tunnel of the session granularity needs to be released.
  • a device granular tunnel refers to a tunnel resource established for one or more PDU sessions, which may be used by one or more PDU sessions.
  • the tunnel of one device granularity may include one or more routing rules, and the one or more routing rules may forward the data corresponding to the tunnel.
  • the lifetime of the tunnel of the device granularity is the lifetime of multiple PDU sessions corresponding to the tunnel, that is, if the tunnel of the device granularity corresponds to the M PDU sessions, then the first M-1 of the multiple PDU sessions corresponding to the tunnel When the PDU session disappears or is released, only the routing rule corresponding to the corresponding PDU session is released.
  • the device granular tunnel may be released.
  • the tunnel of the device granularity may be reserved, so that the tunnel does not need to be re-established. .
  • the routing rule in the embodiment of the present application specifically refers to a rule for routing service data to a next hop device.
  • the first routing rule on the destination UPF entity in the following embodiment includes: sending the data whose destination address is the address of the first AS to the first AS, specifically, the service data whose destination address is the address of the first AS.
  • the next hop device is the first AS.
  • the second routing rule on the destination UPF entity in the following embodiment includes: sending data of the address of the destination address AS1 to the source UPF entity, specifically, the service data of the address of the destination address AS1 One
  • the hop device is the source UPF entity.
  • the third routing rule on the destination UPF entity includes: sending data of an address whose destination address is an anchor data network (DN, A-DN) or sending default data of the destination address to A-
  • the UPF entity specifically, the service data of the address with the destination address being the address of the A-DN or the next hop of the default service data of the destination address is the A-UPF entity.
  • the fourth routing rule on the source UPF entity includes: sending the data whose destination address is the address of the terminal to the destination UPF entity, specifically, the destination hop is the next hop device of the service data of the address of the terminal. UPF entity.
  • the fifth routing rule on the source UPF entity includes: sending the data whose destination address is the address of the terminal to the destination base station, where the next hop device of the service data whose destination address is the address of the terminal is the destination base station. .
  • the path information in the embodiment of the present application includes at least one of tunnel uplink information of A and tunnel downlink information of B, and is used to establish a tunnel between A and B.
  • the tunnel uplink information of A may include the endpoint address of the tunnel on the A side and the address of the A.
  • the tunnel downlink information of the B includes the endpoint address of the tunnel on the B side and the address of the B, which is not specifically limited in this embodiment of the present application.
  • path information in the embodiment of the present disclosure may include a routing rule or may not include a routing rule.
  • the following embodiments use path information as an example to describe the routing rule. Let me repeat.
  • the words “first”, “second”, and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same.
  • the words “first”, “second” and the like do not limit the number and execution order, and the words “first”, “second” and the like are not necessarily limited.
  • the first AS and the second AS in the embodiment of the present application may be the same AS, and may be different ASs.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • FIG. 1 is a schematic structural diagram of a system 10 for implementing service continuity according to an embodiment of the present application.
  • the system 10 for implementing business continuity includes a session management function entity 101, a control device 102, and a plurality of user plane function entities.
  • the plurality of user plane functional entities may include, for example, a destination user plane function entity 103, a source user plane function entity 104, and the like.
  • the session management function entity 101 communicates with the source user plane function entity 104.
  • the session management function entity 101 is configured to select the destination user plane function entity 103 to serve the terminal, and send the first message to the control device 102.
  • the control device 102 is configured to receive the first message from the session management function entity 101 and to the session management function.
  • the entity 101 sends the indication information of the first AS.
  • the session management function entity 101 is further configured to receive the indication information of the first AS from the control device 102, and send a first routing rule to the destination user plane function entity 103 according to the indication information of the first AS, where the first routing rule includes : Send the data whose destination address is the first AS to the first AS.
  • the destination user plane function entity 103 is configured to receive the first routing rule from the session management function entity 101, and transmit the service data according to the first routing rule after establishing the PDU session.
  • the session management function entity 101 and the control device 102 in FIG. 1 may communicate directly, and may also perform communication through forwarding of other network devices, which is not specifically limited in this embodiment of the present application.
  • the session management function entity 101 and the destination user plane function entity 103 in FIG. 1 may communicate directly or may be forwarded through forwarding of other network devices, which is not specifically limited in this embodiment of the present application.
  • the session management function entity may receive the indication information from the first AS, and according to the first The indication information of the AS sends the first routing rule to the destination user plane function entity, so that the destination user plane function entity can transmit the service data according to the first routing rule, so that the continuity of the service in the user plane function entity switching process can be ensured.
  • the first routing rule is to send data of the address whose destination address is the first AS to the first AS
  • the destination user plane function entity can be prevented from routing the data addressed to the address of the first AS to the remote data.
  • the data network (DN) is routed to the first AS, the path from the terminal to the first AS is the shortest and the delay is controllable.
  • system 10 for implementing the service continuity may be applied to the future 5G network and other networks in the future, which is not specifically limited in this embodiment of the present application.
  • the following two typical scenarios of the system 10 for implementing service continuity applied to the current 5G network are as follows:
  • the ULCL architecture shown in FIG. 2 is the ULCL architecture shown in FIG. 2.
  • multiple UDP sessions can exist in one PDU session, and local offload can be implemented through ULCL.
  • the multiple UPF entities include at least one local UPF entity and one remote UPF entity, and the at least one local UPF entity may include, for example, a local UPF entity 1, a local UPF entity 2, ..., a local UPF entity n.
  • the session management function entity 101 in FIG. 1 may specifically be a session management function (SMF) entity in the ULCL architecture; the control device 102 in FIG.
  • SMF session management function
  • the target user plane function entity in FIG. 1 may be any UPF entity in the ULCL architecture, such as the local UPF entity 1.
  • the source user plane function entity in FIG. 1 may specifically be in the ULCL architecture and the local UPF entity 1 Any of the same UPF entities, such as the local UPF entity 2.
  • the ULCL architecture may further include a terminal, an access device, an access and mobility management function (AMF) entity, a ULCL, and a plurality of data networks (DNs).
  • the multiple DNs include a remote DN and multiple local DNs, and the multiple local DNs may include, for example, DN1, DN2, . . . , DNn, and the like.
  • the terminal communicates with the AMF entity through the next generation (N) interface 1 (N1 for short), and communicates with the ULCL through the access device;
  • the access device communicates with the AMF entity through the N interface 2 (N2 for short), and Communicate with the ULCL through the N interface 3 (N3 for short);
  • the AMF entity communicates with the SMF entity through the N interface 11 (N11 for short);
  • the SMF entity passes the N interface 4 (N4 for short) and the UPF entity (including the remote UPF entity and the local UPF entity) ) and ULCL communication;
  • the entity communicates with the local UPF entity, and the UPF entity (including the remote UPF entity and the local UPF entity) communicates with the DN (including the remote DN and the local DN) through the N interface 6 (N6 for short).
  • the local UPF entity and the ULCL in the embodiment of the present application may be deployed in a unified manner, and may be deployed separately.
  • the ULCL can be implemented by the UPF entity.
  • the local UPF entity is a local service anchor
  • the local AS is deployed in the DN of the communication connection with the local UPF entity, and the terminal can access the local AS through the local UPF entity.
  • the remote UPF entity is an internet protocol (IP) anchor
  • IP anchor point is that the IP address remains unchanged if the UPF entity does not change.
  • a remote AS can be deployed in the DN that is connected to the remote UPF entity.
  • the terminal can access the remote AS through the remote UPF entity.
  • the terminal can also communicate with other terminals through the DN that is in communication with the remote UPF entity, which is not specifically limited in this embodiment.
  • the ULCL forwards the local service to the local UPF entity according to the offloading rule delivered by the SMF entity, and forwards the non-local service to the remote UPF entity.
  • the remote UPF entity remains unchanged during the terminal mobility process, so the IP address remains unchanged.
  • the local UPF entity and the AS may need to switch. Since the AS controller maintains the topology information of the AS, the AS may be selected or reselected according to the location information of the local UPF entity and/or the location information of the terminal. Therefore, when the local UPF entity needs to be switched, the SMF entity needs to interact with the AS controller. The AS is reselected to achieve the shortest path between the terminal and the AS.
  • FIG. 2 illustrates an example in which different local UPF entities communicate with ASs in different DNs.
  • different local UPF entities may also communicate with the ASs in the same DN. That is, the AS may not be switched after the local UPF entity is switched, which is not specifically limited in this embodiment.
  • FIG. 3 corresponds to a single-anchor PDU session scenario, that is, one PDU session corresponds to one UPF entity.
  • the session management function entity 101 in FIG. 1 may specifically be the SMF entity in FIG. 3; the control device 102 in FIG. 1 may specifically be the AS controller in FIG. 3, and the target user plane function entity in FIG.
  • the source user plane function entity in FIG. 1 may be the UPF entity 2 in FIG. 3 .
  • the network architecture may further include a terminal, an access device, an AMF entity, and a DN, where the AS is deployed in the DN.
  • the UPF entity and the AS generally need to be deployed locally.
  • the UPF entity and the AS may not be deployed locally, and the embodiment of the present application does not specifically limit the service.
  • the terminal communicates with the AMF entity through the N1, and communicates with the UPF entity (including the UPF entity 1 to the UPF entity n) through the access device; the access device communicates with the AMF entity through the N2, and passes through the N3 and the UPF entity (including the UPF entity). 1 to UPF entity n) communication; AMF entity communicates with SMF entity through N11; SMF entity communicates with UPF entity (including UPF entity 1 to UPF entity n) through N4; UPF entity (including UPF entity 1 to UPF entity n) passes N6 Communicate with DN (including DN1 to DNn).
  • the UPF entity and the AS may need to switch during the terminal mobility.
  • the AS controller maintains the topology information of the AS according to the location information of the local UPF entity and/or the location of the terminal. The information performs the selection or reselection of the AS. Therefore, when the UPF entity needs to switch, the SMF entity needs to interact with the AS controller to implement the reselection of the AS, thereby achieving the shortest path between the terminal and the AS.
  • FIG. 3 illustrates an example in which different UPF entities communicate with ASs in different DNs.
  • the different UPF entities may also communicate with the ASs in the same DN. That is, the AS may not be switched after the UPF entity is switched, which is not specifically limited in this embodiment.
  • the interface name between the network elements in FIG. 2 and FIG. 3 is only an example. In the specific implementation, the interface name may be referred to as another name, which is not specifically limited in this embodiment of the present application.
  • the access device, the AMF entity, the SMF entity, the UPF entity, the AS, and the AS controller in FIG. 2 and FIG. 3 are only one name, and the name does not limit the device itself.
  • the access device, the AMF entity, the SMF entity, the UPF entity, the AS, and the AS controller may also be other names, which are not specifically limited in this embodiment of the present application.
  • the UPF entity may also be replaced by UP
  • the AS may be replaced by an application management platform or a mobile edge computing (MEC) platform, which may be replaced by a car and the outside world.
  • V2X communication to everything communication
  • Control Function Control Function
  • the terminal involved in the embodiment of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; Including user unit (subscriber unit), cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device Handheld, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (user equipment) , UE), mobile station (MS), terminal device, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • user equipment user equipment
  • UE user equipment
  • MS mobile station
  • the access device involved in the embodiment of the present application refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (BNG), an aggregation switch, and a non-3GPP access. Equipment, etc.
  • the base station may include various forms of base stations, such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.
  • the AMF entity involved in the embodiment of the present application is responsible for registration management, mobility management, and lawful interception.
  • the functions of the SMF entity and the AS controller involved in the embodiment of the present application may be referred to the description in FIG. 1 , and details are not described herein again.
  • the SMF entity is also used for session management, including: session establishment, session modification, session release, terminal IP address allocation and management, UPF entity selection and control, and lawful interception and other session-related control functions.
  • the UPF entity involved in the embodiment of the present application may be responsible for processing, such as forwarding, statistics, and the like of the terminal.
  • the UPF entity may implement a user plane function of a serving gateway (SGW) and a packet data network gateway (PGW).
  • SGW serving gateway
  • PGW packet data network gateway
  • the UPF entity may also be a software-defined network (SDN) switch (Switch), which is not specifically limited in this embodiment.
  • SDN software-defined network
  • the session management function entity 101 and the control device 102 in FIG. 1 may be implemented by one entity device, or may be implemented by multiple entity devices, or may be a logical function module in a physical device.
  • the embodiment does not specifically limit this.
  • both the session management function entity 101 and the control device 102 of FIG. 1 can be implemented by the communication device of FIG.
  • FIG. 4 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present application.
  • the communication device 400 includes at least one processor 401, a communication bus 402, a memory 403, and at least one communication interface 404.
  • the processor 401 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 402 can include a path for communicating information between the components described above.
  • Communication interface 404 using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 403 is used to store application code for executing the solution of the present application, and is controlled by the processor 401 for execution.
  • the processor 401 is configured to execute the application code stored in the memory 403, thereby implementing the method for implementing business continuity provided by the following embodiments of the present application.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 400 can include multiple processors, such as processor 401 and processor 408 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • processors herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the communication device 400 can also include an output device 405 and an input device 406.
  • Output device 405 is in communication with processor 401 and can display information in a variety of ways.
  • the output device 405 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 406 is in communication with processor 401 and can accept user input in a variety of ways.
  • input device 406 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the communication device 400 described above may be a general communication device or a dedicated communication device.
  • the communication device 400 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or the like in FIG. device.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 400.
  • the schematic flowchart of the method for implementing service continuity provided by the embodiment of the present application is as shown in FIG. 5, and relates to the session management function entity 101, the control device 102, and the purpose.
  • the interaction between the user plane function entities 103 includes the following steps:
  • the session management function entity selects a destination user plane function entity to be a terminal service.
  • the session management function entity sends a first message to the control device, so that the control device receives the first message from the session management function entity.
  • the control device sends the indication information of the first AS to the session management function entity, so that the session management function entity receives the indication information of the first AS from the control device.
  • the indication information of the first AS may be the location information of the first AS, the identifier information of the first AS, and the information indicating that the AS has not changed. This example does not specifically limit this.
  • S504 The session management function entity sends a first routing rule to the destination user plane function entity according to the indication information of the first AS, so that the destination user plane function entity receives the first routing rule from the session management function entity, where the first routing rule
  • the method includes: sending data of the address whose destination address is the first AS to the first AS.
  • routing rules For a description of the routing rules, refer to the preamble of the specific implementation, and details are not described herein.
  • the session management function entity may receive the indication information from the first AS, and according to The indication information of the first AS sends the first routing rule to the destination user plane function entity, so that the destination user plane function entity can transmit the service data according to the first routing rule, so that the continuity of the service in the user plane function entity switching process can be ensured.
  • the first routing rule is to send the data whose destination address is the address of the first AS to the first AS
  • the destination user plane function entity can be prevented from routing the data addressed to the address of the first AS to the remote DN.
  • the problem is then routed to the first AS, so that the path from the terminal to the first AS is the shortest and the delay is controllable.
  • the actions of the session management function entity in the foregoing S501, S502, and S504 can be performed by the processor 401 in the communication device 400 shown in FIG. 4 to call the application code stored in the memory 403. limit.
  • control device in the above-mentioned 503 can be performed by the processor 401 in the communication device 400 shown in FIG. 4 to call the application code stored in the memory 403, which is not limited in this embodiment of the present application.
  • the terminal communicates with AS1 through the access device (here assumed to be the source base station) and the local UPF entity 2 (herein referred to as the source UPF entity); meanwhile, the terminal passes the source UPF entity and the remote UPF entity (here noted as The A-UPF entity is in communication with the remote DN (herein referred to as A-DN), as shown in FIG. 6 , which is a schematic flowchart of a method for implementing service continuity according to an embodiment of the present application, which relates to a terminal and a source.
  • the interaction between the base station, the destination base station, the source UPF entity, the local UPF entity 1 (herein referred to as the destination UPF entity), the A-UPF entity, the AMF entity, the SMF entity, the AS controller, AS1 and AS2, includes the following steps:
  • the source base station initiates a wireless handover.
  • the target base station After the air interface handover is completed, the target base station sends a path switch request to the SMF entity, so that the SMF entity receives the path switch request from the target base station.
  • the path switching request includes the N3 tunnel uplink information of the target base station, the location information of the terminal, and the like.
  • Head The N3 tunnel of the base station specifically refers to a tunnel between the destination base station and the destination UPF entity.
  • the N3 tunnel uplink information of the destination base station may include the endpoint address of the N3 tunnel of the destination base station on the destination base station side and the address of the destination base station, which are not specifically limited in this embodiment.
  • the SMF entity selects the destination UPF entity as the terminal service according to the location information of the terminal.
  • the SMF entity determines that the local UPF entity needs to be reselected according to the location of the terminal beyond the service scope of the source UPF entity.
  • the SMF entity may select the destination UPF entity to serve the terminal according to at least one of the location information of the terminal, the service capability of the local UPF entity managed by the SMF entity, or the load, which is not specifically limited in this embodiment.
  • the SMF entity sends an N4 session establishment request 1 to the destination UPF entity, so that the destination UPF entity receives the N4 session establishment request 1 from the SMF entity.
  • the N4 session establishment request 1 may include a second routing rule, where the second routing rule includes: sending data of an address whose destination address is AS1 to the source UPF entity.
  • the N4 session establishment request 1 may include first path information, where the first path information is used to establish a forwarding path between the source UPF entity and the destination UPF entity.
  • the first path information in the embodiment of the present application may include the first N9 tunnel downlink information of the source UPF entity.
  • the first path information in the embodiment of the present application may further include the first N9 tunnel uplink information of the destination UPF entity.
  • the first N9 tunnel of the source UPF entity and the first N9 tunnel of the destination UPF entity specifically refer to a tunnel between the source UPF entity and the destination UPF entity.
  • the first N9 tunnel downlink information of the source UPF entity may include the endpoint address of the source and the UPF entity of the first N9 tunnel of the source UPF entity, and the address of the source UPF entity, which is not specifically limited in this embodiment.
  • the first N9 tunnel uplink information of the destination UPF entity may specifically include the endpoint address of the destination NPF entity on the destination UPF entity side and the address of the destination UPF entity, which are not specifically limited in this embodiment of the present application.
  • the downlink information of the first N9 tunnel of the source UPF entity may be allocated by the SMF entity, or may be allocated by the source UPF entity, which is not specifically limited in this embodiment.
  • the first N9 tunnel uplink information of the destination UPF entity may be allocated by the SMF entity, or may be allocated by the destination UPF entity, which is not specifically limited in this embodiment of the present application.
  • the N4 session establishment request 1 may include a third routing rule, where the third routing rule includes: sending data of an address with a destination address of A-DN or sending default data of the destination address to the A-UPF entity. .
  • the N4 session establishment request 1 may include third path information, where the third path information is used to establish a forwarding path between the destination UPF entity and the A-UPF entity.
  • the third path information in the embodiment of the present application may include the second N9 tunnel downlink information of the A-UPF entity.
  • the third path information in the embodiment of the present application may further include the second N9 tunnel uplink information of the destination UPF entity.
  • the second N9 tunnel of the A-UPF entity and the second N9 tunnel of the destination UPF entity specifically refer to a tunnel between the A-UPF entity and the destination UPF entity.
  • the second N9 tunnel downlink information of the A-UPF entity may specifically include the endpoint address of the second N9 tunnel of the A-UPF entity on the A-UPF entity side and the address of the A-UPF entity, which is not specifically limited in this embodiment of the present application. .
  • the second N9 tunnel uplink information of the destination UPF entity may specifically include the endpoint address of the destination NPF entity on the destination UPF entity side and the address of the destination UPF entity, which are not specifically limited in this embodiment.
  • the second N9 tunnel downlink information of the A-UPF entity may be allocated by the SMF entity, or may be allocated by the A-UPF entity, which is not specifically limited in this embodiment.
  • the second N9 tunnel uplink information of the destination UPF entity may be allocated by the SMF entity, or may be allocated by the destination UPF entity. This is not specifically limited.
  • the N4 session establishment request 1 may include seventh path information, where the seventh path information is used to establish a forwarding path between the destination UPF entity and the destination base station.
  • the seventh path information in the embodiment of the present application may include the N3 tunnel uplink information of the target base station in the path switching request.
  • the seventh path information may further include the N3 tunnel downlink information of the destination UPF entity, which is not specifically limited in this embodiment of the present application.
  • the N3 tunnel of the destination UPF entity specifically refers to a tunnel between the destination base station and the destination UPF entity.
  • the N3 tunnel downlink information of the destination UPF entity may specifically include the endpoint address of the destination UPF entity on the destination UPF entity side and the address of the destination UPF entity, which are not specifically limited in this embodiment of the present application.
  • the N3 tunnel downlink information of the destination UPF entity may also be allocated by the destination UPF entity, which is not specifically limited in this embodiment of the present application.
  • the N4 session establishment request 1 may further include other user plane information of the current PDU session, such as a packet statistics and reporting rule, a quality of service (QoS) rule, and the like. .
  • other user plane information of the current PDU session such as a packet statistics and reporting rule, a quality of service (QoS) rule, and the like.
  • the information included in the foregoing N4 session establishment request 1 may also be sent to the destination UPF entity by using different messages, which is not specifically limited in this embodiment of the present application.
  • the destination UPF entity sends a session establishment response 1 to the SMF entity, so that the SMF entity receives the session establishment response 1 from the destination UPF entity.
  • the SMF entity sends an N4 session establishment request 2 to the source UPF entity, so that the destination UPF entity receives the N4 session establishment request 2 from the SMF entity.
  • the N4 session establishment request 2 may include a fourth routing rule, where the fourth routing rule includes: sending data of the address whose destination address is the terminal to the destination UPF entity.
  • the N4 session establishment request 2 may include second path information, where the second path information is used to establish a forwarding path between the source UPF entity and the destination UPF entity.
  • the second path information in the embodiment of the present application may include the first N9 tunnel uplink information of the destination UPF entity.
  • the second path information in the embodiment of the present application may further include the first N9 tunnel downlink information of the source UPF entity.
  • the N4 session establishment request 2 may further include a first tunnel deletion indication information, where the first tunnel deletion indication information is used to indicate that the N3 tunnel of the source UPF entity is deleted or the N3 tunnel of the source UPF entity is invalid.
  • the N3 tunnel of the source UPF entity specifically refers to a tunnel between the source UPF entity and the source base station.
  • the N4 session establishment request 2 may further include a second tunnel deletion indication information, where the second tunnel deletion indication information is used to indicate to delete the second N9 tunnel of the source UPF entity or the second N9 tunnel of the source UPF entity.
  • the second N9 tunnel of the source UPF entity specifically refers to a tunnel between the source UPF entity and the A-UPF entity.
  • the N4 session establishment request 2 may further include other user plane information of the current PDU session, such as a packet statistics and reporting rule, a QoS rule, and the like, which are not specifically limited in this embodiment of the present application.
  • the information included in the foregoing N4 session establishment request 2 may also be sent to the source UPF entity by using different messages, which is not specifically limited in this embodiment of the present application.
  • the source UPF entity sends a session establishment response 2 to the SMF entity, so that the SMF entity receives the session establishment response 2 from the source UPF entity.
  • first path information in step S604 and the second path information in step S606 are both included.
  • the first N9 tunnel downlink information of the source UPF entity and the first N9 tunnel uplink information of the destination UPF entity, the first path information and the second path information may be the same at this time; of course, the first path information in step S604 and step S606
  • the second path information may also be different.
  • the first path information includes only the first N9 tunnel downlink information of the source UPF entity
  • the second path information includes only the first N9 tunnel uplink information of the destination UPF entity. This is not specifically limited.
  • the SMF entity sends an N4 session establishment request 3 to the A-UPF entity, so that the A-UPF entity receives the N4 session establishment request 3 from the SMF entity.
  • the N4 session establishment request 3 may include a fourth routing rule, where the fourth routing rule includes: sending data of the address whose destination address is the terminal to the destination UPF entity.
  • the N4 session establishment request 3 may include fourth path information, where the fourth path information is used to establish a forwarding path between the A-UPF entity and the destination UPF entity.
  • the fourth path information in the embodiment of the present application may include the second N9 tunnel uplink information of the destination UPF entity.
  • the fourth path information in the embodiment of the present application may further include the second N9 tunnel downlink information of the A-UPF entity.
  • the N4 session establishment request 3 may further include a second tunnel deletion indication information, where the second tunnel deletion indication information is used to indicate that the first N9 tunnel of the A-UPF entity is deleted or the first one of the A-UPF entities is deleted.
  • the N9 tunnel is deactivated.
  • the first N9 tunnel of the A-UPF entity specifically refers to a tunnel between the source UPF entity and the A-UPF entity.
  • the N4 session establishment request 3 may further include other user plane information of the current PDU session, such as a packet statistics and reporting rule, a QoS rule, and the like, which are not specifically limited in this embodiment of the present application.
  • the information included in the foregoing N4 session establishment request 3 may also be sent to the source UPF entity through different messages, which is not specifically limited in this embodiment of the present application.
  • the A-UPF entity sends a session establishment response 3 to the SMF entity, so that the SMF entity receives the session establishment response 3 from the A-UPF entity.
  • the third path information in step S604 and the fourth path information in step S608 both include the second N9 tunnel downlink information of the A-UPF entity and the second N9 tunnel uplink information of the destination UPF entity, this
  • the third path information and the fourth path information may be the same; of course, the third path information in step S604 and the fourth path information in step S608 may also be different.
  • the third path information only includes the first part of the A-UPF entity.
  • the N9 tunnel downlink information, the fourth path information includes only the second N9 tunnel uplink information of the destination UPF entity, which is not specifically limited in this embodiment of the present application.
  • the SMF entity sends a path switch response to the target base station, so that the target base station receives the path switch response from the SMF entity.
  • the path switch response may include eighth path information, where the eighth path information is used to establish a forwarding path between the target base station and the destination UPF entity.
  • the eighth path information in the embodiment of the present application may include the N3 tunnel downlink information of the destination UPF entity.
  • the eighth path information in the embodiment of the present application may further include N3 tunnel uplink information of the target base station.
  • the path switching response may further include other user plane information of the current PDU session, such as a packet statistics and reporting rule, a QoS rule, and the like, which are not specifically limited in this embodiment of the present application.
  • the information included in the path switching response may be sent to the target base station by using different messages, which is not specifically limited in this embodiment of the present application.
  • the seventh path information in step S604 and the eighth path information in step S610 are both included.
  • the N3 tunnel downlink information of the destination UPF entity and the N3 tunnel uplink information of the destination base station, the seventh path information and the eighth path information may be the same at this time; of course, the seventh path information in step S604 and the eighth path in step S610.
  • the information may be different.
  • the seventh path information includes only the N3 tunnel uplink information of the destination base station
  • the second path information includes only the N3 tunnel downlink information of the destination UPF entity, which is not specifically limited in this embodiment.
  • the target base station releases the source base station resource.
  • the destination UPF entity can be inserted into the current PDU session, so that the communication between the terminal and the AS1 can be maintained.
  • the destination UPF entity can be regarded as a normal one-hop UPF entity on the PDU session path.
  • the corresponding service transmission path is:
  • steps S604-S605, steps S606-S607, and steps S608-S609, and any one of S604-S605, steps S606-S607, and steps S608-S609 may be performed first. Steps, then perform any of the remaining two sets of steps, and finally perform the remaining set of steps. For example, steps S604-S605 may be performed first, then steps S606-S607 are performed, and finally steps S608-S609 are performed.
  • steps S604-S605, steps S606-S607, and steps S608-S609 may be performed at the same time, which is not specifically limited in this embodiment of the present application.
  • the N9 tunnel is used as an example of the N9 tunnel of the session granularity, including the tunnel between the source UPF entity and the destination UPF entity, and the tunnel between the destination UPF entity and the A-UPF entity. It is to be noted that, of course, the N9 tunnel may also be an N9 tunnel of the device granularity, which is not specifically limited in this embodiment of the present application.
  • the N9 tunnel is the N9 tunnel of the device granularity
  • the N9 tunnel with the granularity of the device is established according to the manner of establishing the session granularity N9 tunnel.
  • the SMF entity sends a second routing rule to the destination UPF entity, so that the destination UPF entity can send the data of the address of the destination address AS1 to the source UPF entity through the tunnel between the source UPF entity and the destination UPF entity.
  • the SMF entity sends a fourth routing rule to the source UPF entity, so that the source UPF entity can send the data whose destination address is the address of the terminal to the destination UPF entity through the tunnel between the source UPF entity and the destination UPF entity.
  • the SMF entity sends a third routing rule to the destination UPF entity, so that the destination UPF entity can send the data of the address with the destination address of the A-DN to the A-UPF through the tunnel between the destination UPF entity and the A-UPF entity.
  • the SMF entity sends a fourth routing rule to the A-UPF entity, so that the A-UPF entity can send the data with the destination address as the address of the terminal to the destination UPF entity through the tunnel between the destination UPF entity and the A-UPF entity.
  • the N9 tunnel is the N9 tunnel of the device granularity
  • the N9 tunnel of the device granularity does not exist in the following scenarios.
  • the SMF entity sends a first message to the AS controller, so that the AS controller receives the first message from the SMF entity.
  • the first message in the embodiment of the present application may be a PDU session change message.
  • the first message may include at least one of location information of the destination UPF entity and location information of the terminal, and at least one of the location information of the destination UPF entity and the location information of the terminal is used to determine The AS of the terminal service is AS2.
  • the SMF entity may determine, according to the local policy, that the first message needs to be sent to the AS controller.
  • the local policy may include a service type or a 5G QoS indicator (5Q QoS indicator, 5QI).
  • the SMF entity may subscribe to such messages.
  • the SMF entity is triggered to send the first message to the AS controller, which is not specifically limited in this embodiment of the present application.
  • the SMF entity may directly communicate with the AS controller, or may be a network exposure function (NEF) entity or a policy control function (PCF) entity and an AS. Controller communication is hereby unified, and will not be described below.
  • NEF network exposure function
  • PCF policy control function
  • step S612 there is no necessary sequence of execution between step S612 and steps S604-S611, and step S612 may be performed first, and then steps S604-S611 may be performed; steps S604-S611 may be performed first, and then step S612 is performed; Step S612 and steps S604-S611 may be performed at the same time, which is not specifically limited in this embodiment of the present application.
  • the AS controller determines, according to the first message, that the AS serving as the terminal is AS2.
  • the AS controller may determine, according to at least one of the location information of the destination UPF entity and the location information of the terminal included in the first message, that the AS serving as the terminal is AS2.
  • the AS controller sends an AS synchronization request to AS1, so that AS1 receives the AS synchronization request from the AS controller.
  • the AS synchronization request is used to request AS1 to synchronize the information of the terminal to AS2.
  • the information of the synchronized terminal may include the service authentication information, the historical data, the context, and the like, which are not specifically limited in this embodiment of the present application.
  • AS synchronization request in the embodiment of the present application may also be another name, and the name does not limit the message itself.
  • AS synchronization request may also be referred to as an AS handover request, and is uniformly described herein, and details are not described herein.
  • S615 and AS1 synchronize the information of the terminal to AS2.
  • the AS1 sends an AS synchronization response to the AS controller, so that the AS controller receives the AS synchronization response from AS1.
  • the synchronization response is used to indicate that synchronization between AS1 and AS2 has been completed.
  • the AS2 sends an AS synchronization response to the AS controller, so that the AS controller receives the AS synchronization response from the AS2.
  • the AS synchronization response is used to indicate that the synchronization between the AS1 and the AS2 is complete, which is not specifically limited in this embodiment of the present application.
  • AS synchronization response in the embodiment of the present application may also be another name, and the name does not limit the message itself.
  • AS synchronization response may also be referred to as an AS handover response, which is uniformly described herein, and is not described here.
  • the AS controller sends the indication information of the AS2 to the SMF entity, so that the SMF entity receives the indication information of the AS2 from the AS controller.
  • the indication information of AS2 may be location information of AS2.
  • the SMF entity sends a offloading rule update request to the destination UPF entity, so that the destination UPF entity receives the offloading rule update request from the SMF entity.
  • the offloading rule update request includes a first routing rule, and the first routing rule includes: sending data of an address whose destination address is AS2 to the AS2.
  • the destination UPF entity may add the first routing rule to the local offloading rule.
  • the destination UPF entity can send the data of the address with the destination address of AS2 to the AS2, and the destination UPF entity sends the data sent to the address of the AS2 to the A-UPF entity according to the ULCL default rule, and sends the data through the A-DN.
  • the problem of AS2 can make the path from the terminal to AS2 the shortest and the delay can be controlled.
  • the destination UPF entity since the local offloading rule of the destination UPF entity further includes the second routing rule and the third routing rule, the destination UPF entity still transmits data according to the service transmission path in step S610, that is, the data whose destination address is AS1 is still sent to The source UPF entity, and the remaining data packets are sent to the A-UPF entity according to the default rule, which is not specifically limited in this embodiment of the present application.
  • the destination UPF entity sends a offload rule update response to the SMF entity, so that the AS controller receives the offload rule update response from the SMF entity.
  • the offload rule update response is used to indicate that the local offloading rule has been established, and the network side path is ready to be completed.
  • the SMF entity sends a seventh message to the AS controller, so that the AS controller receives a seventh message from the SMF entity, where the seventh message is used to indicate that the terminal is switched from AS1 to AS2.
  • the AS controller switches the terminal from AS1 to AS2 according to the seventh message.
  • the AS controller sends an eighth message to the SMF entity, so that the SMF entity receives an eighth message from the AS controller, where the eighth message is used to indicate that the terminal has switched from AS1 to AS2.
  • the SMF entity sends an N4 session modification request to the destination UPF entity, so that the destination UPF entity receives the N4 session modification request from the SMF entity.
  • the N4 session modification request may include the first indication information, where the first indication information is used to indicate that the second routing rule and the first path information are deleted, that is, Delete the tunnel between the source UPF entity and the destination UPF entity.
  • the N9 tunnel is a device-wide N9 tunnel
  • the following two possible implementations are available:
  • the N4 session modification request may include the second The indication information is used to indicate that the second routing rule is deleted.
  • the routing rule corresponding to the tunnel between the source UPF entity and the destination UPF entity does not have other routing rules except the second routing rule
  • the N4 session modification request may include the first indication.
  • the first indication information is used to indicate that the second routing rule and the first path information are deleted, that is, the tunnel between the source UPF entity and the destination UPF entity is deleted.
  • the routing rule corresponding to the tunnel between the source UPF entity and the destination UPF entity has other routing rules except the second routing rule, and the N4 session modification request includes only the second indication.
  • the second indication information is used to indicate that the second routing rule is deleted. That is, when the N9 tunnel is a device grain When a user tunnel is released, the tunnel of the device granularity is not released, and only the routing rules corresponding to the current PDU session are deleted.
  • step S604 For a description of the second routing rule and the first path information, refer to step S604, and details are not described herein again.
  • the information included in the foregoing N4 session modification request may also be sent to the destination UPF entity by using different messages, which is not specifically limited in this embodiment of the present application.
  • the destination UPF entity sends an N4 session modification response to the SMF entity, so that the SMF entity receives the N4 session modification response from the destination UPF entity.
  • the SMF entity sends an N4 session release request to the source UPF entity, so that the source UPF entity receives the N4 session release request from the SMF entity.
  • the N4 session release request is used to request to delete the user plane information corresponding to the terminal in the source UPF entity.
  • the N4 session modification request may include third indication information, where the third indication information is used to indicate that the fourth routing rule and the second path information are deleted, that is, Delete the tunnel between the source UPF entity and the destination UPF entity.
  • the N9 tunnel is a device-wide N9 tunnel
  • the following two possible implementations are available:
  • the N4 session release request may include the fourth The indication information is used to indicate that the fourth routing rule is deleted.
  • the N4 session release request may include a third indication.
  • the third indication information is used to indicate that the fourth routing rule and the second path information are deleted, that is, the tunnel between the source UPF entity and the destination UPF entity is deleted.
  • the routing rule corresponding to the tunnel between the source UPF entity and the destination UPF entity has other routing rules except the fourth routing rule, and the N4 session release request includes only the fourth indication.
  • the fourth indication information is used to indicate that the fourth routing rule is deleted. That is, when the N9 tunnel is a tunnel of the device granularity, the tunnel of the device granularity is not released when the user plane resource is released, and only the routing rule corresponding to the current PDU session is deleted.
  • step S606 For a description of the fourth routing rule and the second path information, refer to step S606, and details are not described herein again.
  • the user plane information corresponding to the terminal may include, in addition to the fourth routing rule and the second path information, a packet detection rule, a QoS rule, and the like, which is not specifically limited in this embodiment of the present application.
  • the information included in the foregoing N4 session release request may also be sent to the source UPF entity by using a different message, which is not specifically limited in this embodiment of the present application.
  • the source UPF entity sends an N4 session release response to the SMF entity, so that the SMF entity receives the N4 session release response from the source UPF entity.
  • steps S623-S624 and steps S625-S626, and steps S623-S624 may be performed first, and then steps S625-S626 may be performed; or steps S625-S626 may be performed first, and then steps S625-S626 may be performed first.
  • Steps S623-S624 are performed; steps S623-S624 and steps S625-S626 may be performed at the same time, which is an embodiment of the present application. This is not specifically limited.
  • the SMF entity can receive the indication information from the AS2, and according to the indication information of the AS2, to the destination UPF.
  • the entity sends the first routing rule, so that the destination UPF entity can transmit the service data according to the first routing rule after the terminal switches from AS1 to AS2.
  • the SMF entity can continue to maintain the service connection between the terminal and AS1 before the terminal switches from AS1 to AS2. Therefore, seamless switching of service data can be implemented in a scenario where the UPF entity and the AS entity switch simultaneously, and the continuity of the service in the handover process is ensured.
  • the destination UPF entity can avoid the problem that the data sent to the address of the AS2 is routed to the A-DN and then to the AS2.
  • the path from the terminal to AS2 is the shortest and the delay is controllable.
  • the actions of the SMF entities in the above 603, S604, S606, S608, S610, S612, S618, S620, S621, S623, and S625 can be stored in the memory 403 by the processor 401 in the communication device 400 shown in FIG.
  • the application code is executed, and the embodiment of the present application does not impose any limitation on this.
  • FIG. 7 is a schematic flowchart of another method for implementing service continuity provided by the embodiment of the present application, where the A-UPF entity is communicated with the remote DN (herein referred to as A-DN).
  • the AS controller determines, according to the first message, that the AS serving as the terminal is AS1.
  • the AS controller may determine, according to at least one of the location information of the destination UPF entity and the location information of the terminal included in the first message, that the AS serving as the terminal is AS1.
  • the AS controller sends the indication information of the AS1 to the SMF entity, so that the SMF entity receives the indication information of the AS1 from the AS controller.
  • the indication information of the AS1 may be the location information of the AS1, the identifier information of the AS1, or the information indicating that the AS1 is not changed, and the embodiment of the present application does not specifically limit the information.
  • the SMF entity may determine that the AS does not switch according to the indication information of the AS1. For example, if the indication information of AS1 is the location information of AS1, the location information of AS1 and the location information of the current AS may be compared. If they are the same, it is determined that the AS does not switch.
  • the SMF entity sends an N4 session modification request to the destination UPF entity, so that the destination UPF entity receives the N4 session modification request from the SMF entity.
  • the N4 session modification request includes a first routing rule, where the first routing rule includes: sending data of an address whose destination address is AS1 to AS1.
  • the destination UPF entity may add the first routing rule to the local offloading rule.
  • the N4 session modification request may include the first indication information, where the first indication information is used to indicate that the second routing rule and the first path information are deleted, that is, Delete source UPF A tunnel between an entity and a destination UPF entity.
  • the N9 tunnel is a device-wide N9 tunnel
  • the following two possible implementations are available:
  • the N4 session modification request may include the second The indication information is used to indicate that the second routing rule is deleted.
  • the routing rule corresponding to the tunnel between the source UPF entity and the destination UPF entity does not have other routing rules except the second routing rule
  • the N4 session modification request may include the first indication.
  • the first indication information is used to indicate that the second routing rule and the first path information are deleted, that is, the tunnel between the source UPF entity and the destination UPF entity is deleted.
  • the routing rule corresponding to the tunnel between the source UPF entity and the destination UPF entity has other routing rules except the second routing rule, and the N4 session modification request includes only the second indication.
  • the second indication information is used to indicate that the second routing rule is deleted. That is, when the N9 tunnel is a tunnel of the device granularity, the tunnel of the device granularity is not released when the user plane resource is released, and only the routing rule corresponding to the current PDU session is deleted.
  • step S704 For a description of the second routing rule and the first path information, refer to step S704, and details are not described herein again.
  • the information included in the foregoing N4 session modification request may also be sent to the destination UPF entity by using different messages, which is not specifically limited in this embodiment of the present application.
  • the destination UPF entity sends an N4 session modification response to the SMF entity, so that the SMF entity receives the N4 session modification response from the destination UPF entity.
  • the first indication information or the second indication information in the step S715 is used to indicate that the second routing rule is deleted. Therefore, the destination UPF entity can directly send the data of the address with the destination address AS1 to the AS1 without going through the source UPF. The forwarding of the entity makes the path from the terminal to AS1 the shortest and the delay is controllable.
  • the destination UPF entity since the local offloading rule of the destination UPF entity further includes the third routing rule, the destination UPF entity still sends the remaining data packets to the A-UPF entity according to the default rule, which is not specifically limited in this embodiment.
  • the SMF entity sends an N4 session release request to the source UPF entity, so that the source UPF entity receives the N4 session release request from the SMF entity.
  • the N4 session release request is used to request to delete the user plane information corresponding to the terminal in the source UPF entity.
  • the N4 session modification request may include third indication information, where the third indication information is used to indicate that the fourth routing rule and the second path information are deleted, that is, Delete the tunnel between the source UPF entity and the destination UPF entity.
  • the N9 tunnel is a device-wide N9 tunnel
  • the following two possible implementations are available:
  • the N4 session release request may include the fourth The indication information is used to indicate that the fourth routing rule is deleted.
  • the N4 session release request may include a third indication.
  • the third indication information is used to indicate that the fourth routing rule and the second path information are deleted, that is, the source UPF is deleted.
  • the routing rule corresponding to the tunnel between the source UPF entity and the destination UPF entity has other routing rules except the fourth routing rule, and the N4 session release request includes only the fourth indication.
  • the fourth indication information is used to indicate that the fourth routing rule is deleted. That is, when the N9 tunnel is a tunnel of the device granularity, the tunnel of the device granularity is not released when the user plane resource is released, and only the routing rule corresponding to the current PDU session is deleted.
  • step S706 For a description of the fourth routing rule and the second path information, refer to step S706, and details are not described herein again.
  • the user plane information corresponding to the terminal may include, in addition to the fourth routing rule and the second path information, a packet detection rule, a QoS rule, and the like, which is not specifically limited in this embodiment of the present application.
  • the information included in the foregoing N4 session release request may also be sent to the source UPF entity by using a different message, which is not specifically limited in this embodiment of the present application.
  • the source UPF entity sends an N4 session release response to the SMF entity, so that the SMF entity receives the N4 session release response from the source UPF entity.
  • the tunnel between the source UPF entity and the destination UPF entity may be deleted.
  • steps S715-S716 and steps S717-S718, and steps S717-S718 may be performed first, and then steps S715-S716 may be performed; or steps S715-S716 may be performed first, and then steps S715-S716 may be performed first.
  • the steps S717-S718 are performed; the steps S715-S716 and the steps S717-S718 are also performed at the same time, which is not specifically limited in this embodiment of the present application.
  • the SMF entity can receive the indication information from the AS1, and according to the indication information of the AS1, to the destination UPF.
  • the entity sends the first routing rule, so that the destination UPF entity can transmit the service data according to the first routing rule.
  • the SMF entity can continue to maintain the service connection between the terminal and the AS1 before the AS controller determines whether the AS switches. Therefore, seamless switching of service data can be implemented in the scenario of UPF entity switching to ensure continuity of services during the handover process.
  • the destination UPF entity can avoid the problem that the data sent to the address of the AS1 is routed to the A-DN and then to the AS1.
  • the path from the terminal to AS1 is the shortest and the delay is controllable.
  • SMF entities in the foregoing 703, S704, S706, S708, S710, S712, S715, and S717 may be performed by the processor 401 in the communication device 400 shown in FIG. 4 calling the application code stored in the memory 403.
  • the embodiment of the present application does not impose any limitation on this.
  • the action of the AS controller in the foregoing S713 and S714 can be performed by the processor 401 in the communication device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not limited in this embodiment.
  • the system 10 for implementing business continuity shown in FIG. 1 is applied to the scenario 2 shown in FIG. 3 as an example, and the method for implementing business continuity shown in FIG. 5 is expanded.
  • FIG. 8 Schematic diagram of a method of service continuity, involving a terminal, a source base station, a destination base station, a source UPF entity, a UPF entity 1 (herein referred to as a destination UPF entity), an AMF entity, an SMF entity, an AS controller, AS1 and AS2
  • the interaction includes the following steps:
  • S801-S802 and the S601-S602 are specifically referred to the embodiment shown in FIG. 6, and details are not described herein again.
  • the SMF entity determines that a UPF entity reselection is required.
  • the SMF entity determines that the local UPF entity needs to be reselected according to the location of the terminal beyond the service scope of the source UPF entity.
  • the SMF entity sends an N4 session establishment request to the source UPF entity, so that the destination UPF entity receives the N4 session establishment request from the SMF entity.
  • the N4 session establishment request may include a fifth routing rule, where the fifth routing rule includes: sending data of the address whose destination address is the terminal to the target base station.
  • the N4 session establishment request may include ninth path information, where the ninth path information is used to establish a forwarding path between the source UPF entity and the base station.
  • the ninth path information in the embodiment of the present application may include the N3 tunnel uplink information of the target base station in the path switching request in step S802.
  • the ninth path information in the embodiment of the present application may further include N3 tunnel downlink information of the source UPF entity.
  • the N3 tunnel of the source UPF entity and the N3 tunnel of the destination base station specifically refer to a tunnel between the source UPF entity and the destination base station.
  • the N3 tunnel uplink information of the destination base station may specifically include the endpoint address of the N3 tunnel of the destination base station on the destination base station side and the address of the destination base station, which are not specifically limited in this embodiment.
  • the N3 tunnel downlink information of the source UPF entity may include the endpoint address of the source UPF entity on the source UPF entity side and the address of the source UPF entity, which are not specifically limited in this embodiment.
  • the N3 tunnel downlink information of the source UPF entity may be allocated by the SMF entity, or may be allocated by the source UPF entity, which is not specifically limited in this embodiment.
  • the N4 session establishment request may further include a first tunnel deletion indication information, where the first tunnel deletion indication information is used to indicate that the N3 tunnel of the source UPF entity is deleted or the N3 tunnel of the source UPF entity is invalid.
  • the N3 tunnel of the source UPF entity specifically refers to a tunnel between the source UPF entity and the source base station.
  • the N4 session establishment request may further include other user plane information of the current PDU session, such as a packet statistics and reporting rule, a QoS rule, and the like, which are not specifically limited in this embodiment of the present application.
  • the information included in the foregoing N4 session establishment request may also be sent to the source UPF entity by using different messages, which is not specifically limited in this embodiment of the present application.
  • the source UPF entity sends a session establishment response to the SMF entity, so that the SMF entity receives the session establishment response from the source UPF entity.
  • the SMF entity sends a path switch response to the target base station, so that the target base station receives the path switch response from the SMF entity.
  • the path switch response may include tenth path information, where the tenth path information is used to establish a forwarding path between the target base station and the source UPF entity.
  • the tenth path information in the embodiment of the present application may include the N3 tunnel downlink information of the source UPF entity.
  • the tenth path information in the embodiment of the present application may further include N3 tunnel uplink information of the target base station.
  • the path switching response may further include other user plane information of the current PDU session, such as a packet statistics and reporting rule, a QoS rule, and the like, which are not specifically limited in this embodiment of the present application.
  • the information included in the path switching response may be sent to the target base station by using different messages, which is not specifically limited in this embodiment of the present application.
  • the ninth path information in step S804 and the tenth path information in step S806 both include the N3 tunnel downlink information of the source UPF entity and the N3 tunnel uplink information of the target base station
  • the ninth path information and The tenth path information may be the same; of course, the ninth path information in step S804 and the tenth path information in step S806 may be different.
  • the ninth path information includes only the N3 tunnel uplink information of the destination base station, and the tenth path information.
  • the information includes only the N3 tunnel downlink information of the source UPF entity, which is not specifically limited in this embodiment of the present application.
  • the target base station releases the source base station resource.
  • the tunnel between the source UPF entity and the source base station can be deleted.
  • step S804 to step S807 communication between the terminal and AS1 can be maintained.
  • the corresponding service transmission path is:
  • the SMF entity sends a PDU session reestablishment notification to the terminal, so that the terminal receives the PDU session reestablishment notification from the SMF entity.
  • the PDU session reestablishment notification includes an identifier (PDU session ID) of the PDU session to be reconstructed.
  • steps S804-S807 and step S808 there is no necessary sequence of execution between steps S804-S807 and step S808, and steps S804-S807 may be performed first, and then step S808 may be performed; step S808 may be performed first, and then steps S804-S807 may be performed; It is also possible to perform S804-S807 and step S808 at the same time, which is not specifically limited in the embodiment of the present application.
  • the terminal initiates a process of establishing a new PDU session (herein referred to as a second PDU session).
  • the SMF entity selects the destination UPF entity as the terminal service in the process of establishing the second PDU session.
  • the terminal may send the identifier of the second PDU session and the identifier of the old PDU session (here denoted as the first PDU session) to the SMF entity, so that the SMF entity receives the terminal from the terminal.
  • the identifier of the first PDU session and the identifier of the second PDU session, and the mapping relationship between the first PDU session and the second PDU session is maintained according to the identifier of the first PDU session and the identifier of the second PDU session, which is not used in this embodiment of the present application. Specifically limited.
  • the SMF entity sends an N4 session modification request to the destination UPF entity, so that the destination UPF entity receives the N4 session modification request from the SMF entity.
  • the N4 session modification request includes a first routing rule, where the first routing rule includes: sending data of an address whose destination address is AS2 to the AS2.
  • the destination UPF entity sends an N4 session modification response to the SMF entity, so that the SMF entity receives the N4 session modification response from the destination UPF entity.
  • the N4 session modification response is used to indicate that the establishment of the underlying network pipe of the terminal and the AS2 is completed.
  • the current corresponding service transmission path is: terminal ⁇ -> destination base station ⁇ -> source UPF entity ⁇ -> AS1;
  • the SMF entity sends a sixth message to the terminal, so that the terminal receives the sixth message from the SMF entity.
  • the sixth message is used to instruct the terminal to release the first PDU session.
  • the terminal releases the first PDU session according to the sixth message.
  • the process of releasing the first PDU session by the terminal may refer to the prior art, and details are not described herein again.
  • the SMF entity can receive the indication information from the AS2, and according to the indication message of the AS2
  • the first routing rule is sent to the destination UPF entity, so that the destination UPF entity can transmit the service data according to the first routing rule after the terminal switches from AS1 to AS2.
  • the SMF entity can continue to maintain the service connection between the terminal and AS1 before the terminal switches from AS1 to AS2. Therefore, seamless switching of service data can be implemented in a scenario where the UPF entity and the AS entity switch simultaneously, and the continuity of the service in the handover process is ensured.
  • the destination UPF entity can avoid the problem that the data sent to the address of the AS2 is routed to the remote DN and then to the AS2.
  • the path from the terminal to AS2 is the shortest and the delay is controllable.
  • SMF entities in the foregoing 803, S804, S806, S808, S809, S810, S816, S818, S819, S821, and S822 may be stored in the memory 403 by the processor 401 in the communication device 400 shown in FIG.
  • the application code is executed, and the embodiment of the present application does not impose any limitation on this.
  • the actions of the AS controllers in the foregoing S811, S812, S815, S819, and S820 can be performed by the processor 401 in the communication device 400 shown in FIG. 4, by calling the application code stored in the memory 403. This is not subject to any restrictions.
  • the terminal communicates with the AS1 through the access device (herein assumed to be the source base station) and the UPF entity 2 (herein referred to as the source UPF entity), as shown in FIG.
  • the access device herein assumed to be the source base station
  • the UPF entity 2 herein referred to as the source UPF entity
  • FIG. A flow diagram of a method for implementing business continuity, involving a terminal, a source base station, a destination base station, a source UPF entity, a UPF entity 1 (herein referred to as a destination UPF entity), an AMF entity, an SMF entity, an AS controller, and an AS1
  • the interaction between the two includes the following steps:
  • the S911 and the AS controller determine that the AS serving as the terminal is AS1 according to the first message.
  • the AS controller may determine, according to at least one of the location information of the destination UPF entity and the location information of the terminal included in the first message, that the AS serving as the terminal is AS1.
  • the AS controller sends the indication information of the AS1 to the SMF entity, so that the SMF entity receives the indication information of the AS1 from the AS controller.
  • the indication information of the AS1 may include the location information of the AS1 or the identifier information of the AS1 or the information indicating that the AS1 is not changed.
  • the SMF entity may determine that the AS does not switch according to the indication information of the AS1. For example, if the indication information of AS1 is the location information of AS1, the location information of AS1 and the location information of the current AS may be compared. If they are the same, it is determined that the AS does not switch.
  • the SMF entity sends an N4 session modification request to the destination UPF entity, so that the destination UPF entity receives the N4 session modification request from the SMF entity.
  • the N4 session modification request includes a first routing rule, where the first routing rule includes: sending data of an address whose destination address is AS1 to AS1.
  • the destination UPF entity sends an N4 session modification response to the SMF entity, so that the SMF entity receives the N4 session modification response from the destination UPF entity.
  • the N4 session modification response is used to indicate that the establishment of the underlying network pipe of the terminal and the AS2 is completed.
  • the current corresponding service transmission path is: terminal ⁇ -> destination base station ⁇ -> source UPF entity ⁇ -> AS1;
  • the SMF entity sends a sixth message to the terminal, so that the terminal receives the sixth message from the SMF entity.
  • the sixth message is used to instruct the terminal to release the first PDU session.
  • the terminal releases the first PDU session according to the sixth message.
  • the process of releasing the first PDU session by the terminal may refer to the prior art, and details are not described herein again.
  • the SMF entity can receive the indication information from the AS1, and according to the indication information of the AS1, to the destination UPF.
  • the entity sends the first routing rule, so that the destination UPF entity can transmit the service data according to the first routing rule.
  • the SMF entity can continue to maintain the service connection between the terminal and the AS1 before the AS controller determines whether the AS switches. Therefore, seamless switching of service data can be implemented in the scenario of UPF entity switching to ensure continuity of services during the handover process.
  • the destination UPF entity can avoid the problem that the data sent to the address of the AS1 is routed to the remote DN and then to the AS1.
  • the path from the terminal to AS1 is the shortest and the delay is controllable.
  • SMF entities in the foregoing 903, S904, S906, S908, S909, S910, S913, S915, and S916 may be invoked by the processor 401 in the communication device 400 shown in FIG. 4 to call the application code stored in the memory 403. Execution, the embodiment of the present application does not impose any limitation on this.
  • the action of the AS controller in the foregoing S911 and S912 can be performed by the processor 401 in the communication device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not limited in this embodiment.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements.
  • the above-mentioned session management function entity and control device include corresponding hardware structures and/or software modules for executing respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide the function module of the session management function entity and the control device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 10 shows a possible structural diagram of the session management function entity 100 involved in the above embodiment.
  • the session management function entity 100 includes a selection module 1001, a sending module 1002, and a receiving module 1003.
  • the selecting module 1001 is configured to select a destination user plane function entity to serve the terminal.
  • the sending module 1002 is configured to send a first message to the control device.
  • the receiving module 1003 is configured to receive indication information of the first AS from the control device.
  • the sending module 1002 is further configured to send, according to the indication information of the first AS, the first routing rule to the destination user plane function entity, where the first routing rule includes: sending, by the destination address, the data of the address of the first AS to the first AS.
  • the sending module 1002 is further configured to: after the selecting module 1001 selects the target user plane function entity as the terminal service, send the second routing rule to the destination user plane function entity before sending the first routing rule to the destination user plane function entity.
  • the second routing rule includes: sending the data whose destination address is the address of the second AS to the source user plane function entity, where the second AS is the AS currently serving the terminal, and the source user plane function entity is to communicate with the second AS.
  • the connected user plane function entity is further configured to: after the selecting module 1001 selects the target user plane function entity as the terminal service, send the second routing rule to the destination user plane function entity before sending the first routing rule to the destination user plane function entity.
  • the second routing rule includes: sending the data whose destination address is the address of the second AS to the source user plane function entity, where the second AS is the AS currently serving the terminal, and the source user plane function entity is to communicate with the second AS.
  • the connected user plane function entity is further configured to: after the selecting module 1001 selects the target user plane function entity
  • the sending module 1002 is further configured to: after the selecting module 1001 selects the target user plane function entity as the terminal service, send the first path information to the destination user plane function entity. And the sending module 1002 is further configured to: after the selecting module 1001 selects the target user plane function entity to serve the terminal, send the second path information to the source user plane function entity, where the first path information and the second path information are used to establish The forwarding path between the destination user plane function entity and the source user plane function entity.
  • the sending module 1002 is further configured to: after the selecting module 1001 selects the target user plane function entity as the terminal service, send the third routing rule to the destination user plane function entity, where the third routing rule includes: the destination address is the first The data of the address of the data network is sent to the remote user plane function entity, wherein the remote user plane function entity is a user plane function entity that is in communication with the first data network.
  • the sending module 1002 is further configured to: after the selecting module 1001 selects the target user plane function entity as the terminal service, send the third path information to the destination user plane function entity; and the sending module 1002 is further configured to select the module.
  • the method 10010 sends the fourth path information to the remote user plane function entity, where the third path information and the fourth path information are used to establish the target user plane function entity and the remote user plane function. The forwarding path between entities.
  • the sending module 1002 is further configured to: after sending the first routing rule to the target user plane function entity, send a second message to the destination user plane function entity, where the second message is used to request to delete the second routing rule.
  • the sending module 1002 is further configured to: after sending the first routing rule to the target user plane function entity, send a third message to the destination user plane function entity, where the third message is used to request to delete the first path information.
  • the sending module 1002 is further configured to: after sending the first routing rule to the target user plane function entity, send a fourth message to the source user plane function entity, where the fourth message is used to request to delete the terminal in the source user plane function entity
  • the user plane information includes second path information.
  • the sending module 1002 is further configured to: before the selecting module 1001 selects the target user plane function entity to serve the terminal, send the fifth path information to the target base station; and the sending module 1002 is further configured to select the destination in the selecting module 1001.
  • the sixth path information is sent to the source user plane function entity, where the five path information and the sixth path information are used to establish a forwarding path between the target base station and the source user plane function entity, and the source user
  • the surface function entity is a user plane function entity that currently establishes a first PDU session with the terminal
  • the destination base station is a base station that is currently in communication connection with the destination user plane function entity.
  • the selecting module 1001 is specifically configured to: send a fifth message to the terminal, where the fifth message is used to request to establish a second PDU session; and in the process of establishing the second PDU session, select the destination user plane function entity to serve the terminal.
  • the sending module 1002 is configured to send a sixth message to the terminal after the first routing rule is sent to the target user plane function entity, where the sixth message is used to request to release the first PDU session.
  • the sending module 1002 is further configured to: after sending the first routing rule to the target user plane function entity, send a seventh message to the control device, where the seventh message is used to request to switch the terminal from the second AS to the first AS.
  • the second AS is an AS that is currently serving the terminal.
  • the receiving module 1003 is further configured to: after the sending module 1002 sends the seventh message to the control device, receive an eighth message from the control device, where the eighth message is used to indicate that the terminal has switched from the second AS to the first AS. .
  • FIG. 11 is a schematic diagram showing a possible structure of the session management function entity 110 involved in the foregoing embodiment, where the session management function entity 110 includes: a processing module. 1101 and a communication module 1102.
  • the processing module 1101 can be used to perform the operations that can be performed by the selection module 1001 in FIG. 10, and the communication module 1102 can be used to perform operations performed by the receiving module 1003 and the sending module 1002 in FIG.
  • the embodiments of the present application are not described herein again.
  • the session management function entity is presented in the form of dividing each function module corresponding to each function, or the session management function entity is presented in the form of dividing each function module in an integrated manner.
  • a “module” herein may refer to an Application-Specific Integrated Circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC Application-Specific Integrated Circuit
  • the session management function entity 100 or the session management function entity 110 may take the form shown in FIG.
  • the selection module 1001, the transmitting module 1002, and the receiving module 1003 in FIG. 10 can be implemented by the processor 401 and the memory 403 of FIG.
  • the selection module 1001, the sending module 1002, and the receiving module 1003 can be executed by calling the application code stored in the memory 403 by the processor 401, which is not limited in this embodiment.
  • the processing module 1101 and the communication module 1102 in FIG. 11 may be implemented by the processor 401 and the memory 403 of FIG.
  • the processing module 1101 and the communication module 1102 can be executed by calling the application code stored in the memory 403 by the processor 401, which is not limited in this embodiment.
  • the session management function provided by the embodiment of the present application can be used to perform the foregoing method for implementing the service continuity. Therefore, the technical effects of the method can be referred to the foregoing method embodiments, and details are not described herein.
  • FIG. 12 shows a possible structural diagram of the control device involved in the foregoing embodiment, and the control device 120 includes: a receiving module 1201 and a sending module 1202. .
  • the receiving module 1201 is configured to receive a first message from the session management function entity.
  • the sending module 1202 is configured to send the indication information of the first AS to the session management function entity, where the indication information of the first AS is used to instruct the session management function entity to send the first routing rule to the target user plane function entity, where the first routing rule includes: The data whose destination address is the address of the first AS is sent to the first AS.
  • the control device 120 further includes a switching module 1203.
  • the receiving module 1201 is further configured to: after the sending module 1202 sends the indication information of the first AS to the session management function entity, receive a seventh message from the session management function entity, where the seventh message is used to indicate that the terminal is switched from the second AS to the second AS The first AS, where the second AS is an AS currently serving the terminal.
  • the switching module 1203 is configured to switch the terminal from the second AS to the first AS according to the seventh message.
  • FIG. 13 is a schematic diagram showing a possible structure of the control device 130 involved in the foregoing embodiment.
  • the control device 130 includes a communication module 1301.
  • the communication module 1301 can be used to perform the operations that can be performed by the receiving module 1201 and the sending module 1202 in FIG. 12 .
  • the communication module 1301 can be used to perform the operations that can be performed by the receiving module 1201 and the sending module 1202 in FIG. 12 .
  • the communication module 1301 can be used to perform the operations that can be performed by the receiving module 1201 and the sending module 1202 in FIG. 12 .
  • FIG. 12 For details, refer to the embodiment shown in FIG. 12 , and details are not described herein again.
  • control device 130 may further include a processing module 1302.
  • the processing module 1302 can be used to perform the operations that can be performed by the switching module 1203 in FIG. 12 .
  • the processing module 1302 can be used to perform the operations that can be performed by the switching module 1203 in FIG. 12 .
  • the control device 130 may further include a processing module 1302.
  • the processing module 1302 can be used to perform the operations that can be performed by the switching module 1203 in FIG. 12 .
  • the control device 130 provided by the embodiment of the present application may further include a processing module 1302.
  • the processing module 1302 can be used to perform the operations that can be performed by the switching module 1203 in FIG. 12 .
  • control device is presented in the form of dividing each functional module corresponding to each function, or the control device is presented in a form that divides each functional module in an integrated manner.
  • a "module” herein may refer to an Application-Specific Integrated Circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC Application-Specific Integrated Circuit
  • control device 120 or control device 130 may take the form shown in FIG.
  • the receiving module 1201, the transmitting module 1202, and the switching module 1203 in FIG. 12 can be implemented by the processor 401 and the memory 403 of FIG.
  • the receiving module 1201, the sending module 1202, and the switching module 1203 may be executed by calling the application code stored in the memory 403 by the processor 401, which is not limited in this embodiment.
  • the processing module 1302 and the communication module 1301 in FIG. 13 may be implemented by the processor 401 and the memory 403 of FIG.
  • the processing module 1302 and the communication module 1301 may be executed by calling the application code stored in the memory 403 by the processor 401, which is not limited in this embodiment.
  • control device provided by the embodiment of the present application can be used to perform the foregoing method for implementing service continuity. Therefore, the technical effects that can be obtained can be referred to the foregoing method embodiments, and details are not described herein again.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a Solid State Disk (SSD)

Landscapes

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

Abstract

本申请实施例提供实现业务连续性的方法、设备及系统，能够保证切换过程中业务的连续性。方法包括：会话管理功能实体选择目的用户面功能实体为终端服务；会话管理功能实体向控制设备发送第一消息；会话管理功能实体接收来自控制设备的第一应用服务器AS的指示信息；会话管理功能实体根据该第一AS的指示信息，向目的用户面功能实体发送第一路由规则，该第一路由规则包括：将目的地址为第一AS的地址的数据发送给该第一AS。

Description

实现业务连续性的方法、设备及系统 技术领域
本申请涉及通信技术领域，尤其涉及实现业务连续性的方法、设备及系统。
背景技术
为了应对无线宽带技术的挑战，保持第三代合作伙伴计划(3rd generation partnership project，3GPP)网络的领先优势，3GPP标准组在2016年底制定了下一代移动通信系统(next generation system)网络架构，称为第五代(5rd generation，5G)网络架构。
5G网络架构中定义了极高可靠性低时延通信(ultra-reliable low latency communication，URLLC)场景，主要包括如无人驾驶、工业自动化等需要低时延、高可靠连接的业务。比如，现有5G技术标准(technical standards，TS)22186规定远程驾驶场景中，要求终端与服务器之间的端到端时延需要始终保持在5ms以内。为了满足端到端时延要求，应用服务器(application server，AS)需要本地部署。同时如果终端处于高速移动状态，则会存在用户面功能(user plane function，UPF)实体和AS切换的场景，为了在切换过程中，始终保持端到端时延要求，需要保证业务的连续性。
目前，将应用服务器本地部署的一个可行解决方案是采用上行分类器(uplink classifier，ULCL)机制实现。ULCL场景下，一个分组数据单元(packet data unit，PDU)会话可以存在多个UPF实体，通过ULCL可实现本地分流，这样使得提供极低时延业务或者高价值服务的应用服务器本地部署。此种部署使得终端和AS的路径最短，使得端到端时延能够满足极低时延要求。
然而，如何保证切换过程中业务的连续性，目前并没有相关的解决方案。
发明内容
本申请实施例提供实现业务连续性的方法、设备及系统，能够保证切换过程中业务的连续性。
第一方面，提供一种实现业务连续性的方法，该方法包括：会话管理功能实体选择目的用户面功能实体为终端服务；会话管理功能实体向控制设备发送第一消息；会话管理功能实体接收来自控制设备的第一应用服务器AS的指示信息；会话管理功能实体根据该第一AS的指示信息，向目的用户面功能实体发送第一路由规则，该第一路由规则包括：将目的地址为第一AS的地址的数据发送给该第一AS。基于该方案，一方面，由于在会话管理功能实体选择目的用户面功能实体为终端服务后，会话管理功能实体可以接收来自第一AS的指示信息，并根据第一AS的指示信息，向目的用户面功能实体发送第一路由规则，使得目的用户面功能实体可以根据第一路由规则传输业务数据，因此可以保证用户面功能实体切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为第一AS的地址的数据发送给第一AS，因此可以避免目的用户面功能实体将发往第一AS的地址的数据路由到远端数据网络后再路由到第一AS的问题，从而可以使得终端到第一AS的路径最短，时延可控。
可选的，在会话管理功能实体选择目的用户面功能实体为终端服务之后，会话管理功能实体向目的用户面功能实体发送第一路由规则之前，还包括：会话管理功能实体向目的 用户面功能实体发送第二路由规则，该第二路由规则包括：将目的地址为第二AS的地址的数据发送给源用户面功能实体，其中，该第二AS为当前为该终端服务的AS，该源用户面功能实体为与该第二AS通信连接的用户面功能实体。基于该方案，由于在用户面功能实体发生切换的情况下，切换后的目的用户面功能实体中存在目的地址为当前AS的地址的业务数据的路由规则，因此可以在用户面功能实体发生切换时，保持该业务的连续性。
可选的，在会话管理功能实体选择目的用户面功能实体为终端服务之后，还包括：会话管理功能实体向目的用户面功能实体发送第一路径信息；以及，会话管理功能实体向源用户面功能实体发送第二路径信息，其中，该第一路径信息和该第二路径信息用于建立该目的用户面功能实体和源用户面功能实体之间的转发路径。基于该方案，可以建立目的用户面功能实体和源用户面功能实体之间的转发路径。
可选的，在会话管理功能实体选择目的用户面功能实体为终端服务之后，还包括：会话管理功能实体向目的用户面功能实体发送第三路由规则，该第三路由规则包括：将目的地址为第一数据网络的地址的数据发送给远端用户面功能实体，其中，该远端用户面功能实体为与第一数据网络通信连接的用户面功能实体。基于该方案，由于在用户面功能实体发生切换的情况下，切换后的目的用户面功能实体中存在目的地址为第一数据网络的地址的业务数据的路由规则，因此可以在用户面功能实体发生切换时，保持该业务的连续性。
可选的，在会话管理功能实体选择目的用户面功能实体为终端服务之后，还包括：会话管理功能实体向目的用户面功能实体发送第三路径信息；以及，会话管理功能实体向远端用户面功能实体发送第四路径信息，其中，该第三路径信息和该第四路径信息用于建立目的用户面功能实体和远端用户面功能实体之间的转发路径。基于该方案，可以建立目的用户面功能实体和远端用户面功能实体之间的转发路径。
可选的，在会话管理功能实体向目的用户面功能实体发送第一路由规则之后，还包括：会话管理功能实体向目的用户面功能实体发送第二消息，该第二消息用于请求删除第二路由规则。也就是说，在网络侧路径已经准备完成的情况下，可以释放目的用户面功能实体中旧业务对应的路由规则。
可选的，在会话管理功能实体向目的用户面功能实体发送第一路由规则之后，还包括：会话管理功能实体向目的用户面功能实体发送第三消息，该第三消息用于请求删除第一路径信息。也就是说，在网络侧路径已经准备完成的情况下，可以释放目的用户面功能实体中旧业务对应的路径信息。
可选的，在会话管理功能实体向目的用户面功能实体发送第一路由规则之后，还包括：会话管理功能实体向源用户面功能实体发送第四消息，该第四消息用于请求删除源用户面功能实体中该终端对应的用户面信息，该用户面信息包括第二路径信息。也就是说，在网络侧路径已经准备完成的情况下，可以释放源用户面功能实体中该终端对应的用户面信息。
可选的，在会话管理功能实体选择目的用户面功能实体为终端服务之前，还包括：会话管理功能实体向目的基站发送第五路径信息；以及，会话管理功能实体向源用户面功能实体发送第六路径信息，其中，该五路径信息和该第六路径信息用于建立目的基站和源用户面功能实体之间的转发路径，该源用户面功能实体为当前与该终端建立第一分组数据单元PDU会话的用户面功能实体，该目的基站为当前与该目的用户面功能实体通信连接的基站。基于该方案，可以预先建立目的基站和源用户面功能实体之间的转发路径，进而在用户面功能实体发生切换的情况下，可以保持当前业务的连续性。
可选的，会话管理功能实体选择目的用户面功能实体为终端服务，包括：会话管理功能实体向终端发送第五消息，该第五消息用于请求建立第二PDU会话；在建立第二PDU会话的过程中，会话管理功能实体选择目的用户面功能实体为该终端服务。基于该方案，会话管理功能实体可以选择目的用户面功能实体为终端服务。
可选的，在会话管理功能实体向目的用户面功能实体发送第一路由规则之后，还包括：会话管理功能实体向终端发送第六消息，该第六消息用于请求释放该第一PDU会话。也就是说，在新的PDU会话的网络侧路径已经准备完成的情况下，可以释放旧的PDU会话资源。
可选的，在会话管理功能实体向目的用户面功能实体发送第一路由规则之后，还包括：会话管理功能实体向控制设备发送第七消息，该第七消息用于请求将该终端从第二AS切换至第一AS，其中，第二AS为当前为该终端服务的AS。基于该方案，可以使得终端从第二AS切换至第一AS。
可选的，在会话管理功能实体向控制设备发送第七消息之后，还包括：会话管理功能实体接收来自控制设备的第八消息，该第八消息用于指示该终端已经从第二AS切换至第一AS。这样，控制设备可以及时获知AS是否切换完成，进而可以及时执行后续的操作。
可选的，该第一消息包括该目的用户面功能实体的位置信息和该终端的位置信息中的至少一个，该目的用户面功能实体的位置信息和该终端的位置信息中的至少一个用于确定为该终端服务的AS为第一AS。这样，控制设备接收到第一消息之后，可以根据第一消息确定出为终端服务的AS。
可选的，第一AS的指示信息包括第一AS的位置信息、或者第一AS的标识信息，或者指示AS未发生变更的信息等，本申请实施例对此不作具体限定。
第二方面，提供一种实现业务连续性的方法，该方法包括：控制设备接收来自会话管理功能实体的第一消息；控制设备向会话管理功能实体发送第一应用服务器AS的指示信息，该第一AS的指示信息用于指示会话管理功能实体向目的用户面功能实体发送第一路由规则，该第一路由规则包括：将目的地址为第一AS的地址的数据发送给该第一AS。基于该方案，一方面，由于在控制设备向会话管理功能实体发送第一AS的指示信息之后，会话管理功能实体可以接收来自第一AS的指示信息，并根据第一AS的指示信息，向目的用户面功能实体发送第一路由规则，使得目的用户面功能实体可以根据第一路由规则传输业务数据，因此可以保证用户面功能实体切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为第一AS的地址的数据发送给第一AS，因此可以避免目的用户面功能实体将发往第一AS的地址的数据路由到远端数据网络后再路由到第一AS的问题，从而可以使得终端到第一AS的路径最短，时延可控。
可选的，该第一消息包括该目的用户面功能实体的位置信息和该终端的位置信息中的至少一个，该目的用户面功能实体的位置信息和该终端的位置信息中的至少一个用于确定为该终端服务的AS为第一AS。这样，控制设备接收到第一消息之后，可以根据第一消息确定出为终端服务的AS。
可选的，在控制设备向会话管理功能实体发送第一AS的指示信息之后，还包括：控制设备接收来自会话管理功能实体的第七消息，该第七消息用于指示将终端从第二AS切换至该第一AS，其中，该第二AS为当前为该终端服务的AS；控制设备根据该第七消息，将该终端从第二AS切换至第一AS。基于该方案，可以使得终端从第二AS切换至第一AS。
可选的，该控制设备包括车与外界的通信V2X控制功能实体。
第三方面，提供一种会话管理功能实体，该会话管理功能实体具有实现上述第一方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，提供一种会话管理功能实体，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该会话管理功能实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该会话管理功能实体执行如上述第一方面中任一所述的实现业务连续性的方法。
第五方面，本申请实施例提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项的实现业务连续性的方法。
第六方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项的实现业务连续性的方法。
其中，第三方面至第六方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第七方面，提供一种控制设备，该控制设备具有实现上述第二方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，提供一种控制设备，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该控制设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使该控制设备执行如上述第二方面中任一所述的实现业务连续性的方法。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二方面中任意一项的实现业务连续性的方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二方面中任意一项的实现业务连续性的方法。
其中，第七方面至第十方面中任一种设计方式所带来的技术效果可参见第二方面中不同设计方式所带来的技术效果，此处不再赘述。
第十一方面，提供一种实现业务连续性的方法，该方法包括：会话管理功能实体选择目的用户面功能实体为终端服务；会话管理功能实体向控制设备发送第一消息，控制设备接收来自会话管理功能实体的第一消息；控制设备向会话管理功能实体发送第一应用服务器AS的指示信息，会话管理功能实体接收来自控制设备的第一AS的指示信息；会话管理功能实体根据第一AS的指示信息，向目的用户面功能实体发送第一路由规则，该第一路由规则包括：将目的地址为第一AS的地址的数据发送给第一AS。
第十二方面，提供一种实现业务连续性的控制系统，包括如上述任一方面所述的控制设备和如上述任一方面所述的会话管理功能实体。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请实施例提供的实现业务连续性的系统的架构示意图一；
图2为本申请实施例提供的实现业务连续性的系统的架构示意图二；
图3为本申请实施例提供的实现业务连续性的系统的架构示意图三；
图4为本申请实施例提供的通信设备的硬件结构示意图；
图5为本申请实施例提供的实现业务连续性的方法的流程示意图一；
图6为本申请实施例提供的实现业务连续性的方法的流程示意图二；
图7为本申请实施例提供的实现业务连续性的方法的流程示意图三；
图8为本申请实施例提供的实现业务连续性的方法的流程示意图四；
图9为本申请实施例提供的实现业务连续性的方法的流程示意图五；
图10为本申请实施例提供的会话管理功能实体的结构示意图一；
图11为本申请实施例提供的会话管理功能实体的结构示意图二；
图12为本申请实施例提供的控制设备的结构示意图一；
图13为本申请实施例提供的控制设备的结构示意图二。
具体实施方式
为了方便理解本申请实施例的技术方案，首先给出本申请相关技术的简要介绍如下。
第一，隧道：
本申请实施例中的隧道包括下一代网络(Next generation，N)接口3(简称N3)N3隧道和N接口9(简称N9)隧道。其中，N3隧道为接入设备(比如基站)与UPF实体之间的隧道；N9隧道为UPF实体与UPF实体之间的隧道。通常，N3隧道为会话粒度的隧道，N9隧道可以为会话粒度的隧道，也可以为设备粒度的隧道。
其中，会话粒度的隧道是指，针对一个PDU会话建立的隧道资源，该隧道仅供一个PDU会话使用。其中，一个会话粒度的隧道仅包括一个路由规则，只有该路由规则才能够对应该隧道转发数据。另外，会话粒度的隧道的生命周期是一个PDU会话的生命周期，即当一个PDU会话消失或释放时，会话粒度的隧道也需要释放。
设备粒度的隧道是指，针对一个或多个PDU会话建立的隧道资源，该隧道可以供一个或多个PDU会话使用。其中，一个设备粒度的隧道可以包括一个或者多个路由规则，该一个或多个路由规则均可以对应该隧道转发数据。另外，设备粒度的隧道的生命周期是该隧道对应的多个PDU会话的生命周期，即假设设备粒度的隧道对应M个PDU会话，则当该隧道对应的多个PDU会话中的前M-1个PDU会话消失或释放时，仅释放相应PDU会话对应的路由规则；当该隧道对应的多个PDU会话中的第M个PDU会话消失或释放时，设备粒度的隧道才可能释放。当然，当该隧道对应的多个PDU会话中的第M个PDU会话消失或释放时，也可以保留该设备粒度的隧道，以便后续不需要重新建立该隧道，本申请实施例对此不作具体限定。
第二，路由规则：
本申请实施例中的路由规则具体是指将业务数据路由到下一跳设备的规则。
比如，下述实施例中目的UPF实体上的第一路由规则包括：将目的地址为第一AS的地址的数据发送给第一AS，具体是指，目的地址为第一AS的地址的业务数据的下一跳设备为第一AS。
或者，比如，下述实施例中目的UPF实体上的第二路由规则包括：将目的地址为AS1的地址的数据发送给源UPF实体，具体是指，目的地址为AS1的地址的业务数据的下一 跳设备为源UPF实体。
或者，比如，目的UPF实体上第三路由规则包括：将目的地址为锚点数据网络(anchor，data network，DN，A-DN)的地址的数据或者将目的地址缺省的数据发送给A-UPF实体，具体是指，目的地址为A-DN的地址的业务数据或者目的地址缺省的业务数据的下一跳设备为A-UPF实体。
或者，比如，源UPF实体上的第四路由规则包括：将目的地址为终端的地址的数据发送给目的UPF实体，具体是指，目的地址为终端的地址的业务数据的下一跳设备为目的UPF实体。
或者，比如，源UPF实体上的第五路由规则包括：将目的地址为终端的地址的数据发送给目的基站，具体是指，目的地址为终端的地址的业务数据的下一跳设备为目的基站。
第三，路径信息：
本申请实施例中的路径信息包括A的隧道上行信息和B的隧道下行信息中的至少一个，用于建立A和B之间的隧道。A的隧道上行信息可以包括隧道在A侧的端点地址和A的地址等，B的隧道下行信息包括隧道在B侧的端点地址和B的地址等，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中的路径信息可以包括路由规则，也可以不包括路由规则，下述各实施例以路径信息不包括路由规则为例进行说明，在此进行统一说明，以下不再赘述。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。比如，本申请实施例中的第一AS和第二AS可能是相同的AS，也可能是不同的AS，本申请实施例对此不作具体限定。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，为本申请实施例提供的实现业务连续性的系统10的架构示意图。该实现业务连续性的系统10包括会话管理功能实体101、控制设备102，还可以包括多个用户面功能实体。该多个用户面功能实体例如可以包括目的用户面功能实体103、源用户面功能实体104，等等。
其中，初始状态下，会话管理功能实体101与源用户面功能实体104通信。
在终端移动后，会话管理功能实体101，用于选择目的用户面功能实体103为终端服务，并向控制设备102发送第一消息。
控制设备102，用于接收来自会话管理功能实体101的第一消息，并向会话管理功能 实体101发送第一AS的指示信息。
会话管理功能实体101，还用于接收来自控制设备102的第一AS的指示信息，并根据第一AS的指示信息，向目的用户面功能实体103发送第一路由规则，该第一路由规则包括：将目的地址为第一AS的数据发送给第一AS。
目的用户面功能实体103，用于接收来自会话管理功能实体101的第一路由规则，并在建立PDU会话后根据第一路由规则传输业务数据。
可选的，图1中的会话管理功能实体101和控制设备102可能直接通信，也可能通过其他网络设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，图1中的会话管理功能实体101和目的用户面功能实体103可能直接通信，也可能通过其他网络设备的转发进行通信，本申请实施例对此不作具体限定。
基于本申请实施例提供的业务连续性系统，一方面，由于在会话管理功能实体选择目的用户面功能实体为终端服务后，会话管理功能实体可以接收来自第一AS的指示信息，并根据第一AS的指示信息，向目的用户面功能实体发送第一路由规则，使得目的用户面功能实体可以根据第一路由规则传输业务数据，因此可以保证用户面功能实体切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为第一AS的地址的数据发送给第一AS，因此可以避免目的用户面功能实体将发往第一AS的地址的数据路由到远端数据网络(data network，DN)后再路由到第一AS的问题，从而可以使得终端到第一AS的路径最短，时延可控。
可选的，上述实现业务连续性的系统10可以应用于未来的5G网络以及未来其它的网络，本申请实施例对此不作具体限定。下面给出上述实现业务连续性的系统10应用于目前的5G网络的两种典型场景，如下：
场景一：
若上述实现业务连续性的系统10应用于目前的5G网络，则一种可能的适用架构为图2所示的ULCL架构。ULCL场景下，一个PDU会话可以存在多个UPF实体，通过ULCL可以实现本地分流。其中，多个UPF实体包括至少一个本地UPF实体和一个远端UPF实体，至少一个本地UPF实体例如可以包括本地UPF实体1、本地UPF实体2、……、本地UPF实体n。具体的，图1中的会话管理功能实体101具体可以为ULCL架构中的会话管理功能(session management function，SMF)实体；图1中的控制设备102具体可以为ULCL架构中的AS控制器(controller)；图1中的目的用户面功能实体具体可以为ULCL架构中的任一UPF实体，比如本地UPF实体1，图1中的源用户面功能实体具体可以为ULCL架构中与本地UPF实体1不相同的任一UPF实体，比如本地UPF实体2。此外，如图2所示，ULCL架构中还可以包括终端、接入设备、接入与移动管理功能(access and mobility management function，AMF)实体、ULCL、以及多个数据网络(data network，DN)。其中，多个DN包括一个远端DN以及多个本地DN，多个本地DN例如可以包括DN1，DN2，……，DNn等。
其中，终端通过下一代网络(next generation，N)接口1(简称N1)与AMF实体通信，并通过接入设备与ULCL通信；接入设备通过N接口2(简称N2)与AMF实体通信，并通过N接口3(简称N3)与ULCL通信；AMF实体通过N接口11(简称N11)与SMF实体通信；SMF实体通过N接口4(简称N4)与UPF实体(包括远端UPF实体和本地UPF实体)和ULCL通信；ULCL通过N接口9(简称N9)与UPF实体(包括远端UPF 实体和本地UPF实体)通信，UPF实体(包括远端UPF实体和本地UPF实体)通过N接口6(简称N6)与DN(包括远端DN和本地DN)通信。
可选的，本申请实施例中的本地UPF实体和ULCL可以合一部署，也可以分开部署，本申请实施例对此不作具体限定。其中，本地UPF实体与ULCL分开部署时，ULCL可以通过UPF实体实现，在此进行统一说明，以下不再赘述。
可选的，本申请实施例中，本地UPF实体为本地业务锚点(anchor)，与本地UPF实体通信连接的DN中部署有本地AS，终端通过本地UPF实体可以接入本地AS。
需要说明的是，本申请实施例中的通信连接可以是直接连接，也可以是经过其他网络设备相连接，在此进行统一说明，以下不再赘述。
可选的，本申请实施例中，远端UPF实体为网际协议(internet protocol，IP)锚点，IP锚点是指若UPF实体不变则IP地址保持不变。其中，与远端UPF实体通信连接的DN中可以部署有远端AS，终端通过远端UPF实体可以接入远端AS。当然，终端也可以通过与远端UPF实体通信连接的DN与其它终端通信，本申请实施例对此不作具体限定。
其中，在图2中，对于上行数据，ULCL根据SMF实体下发的分流规则，将本地业务转发至本地UPF实体，将非本地业务转发至远端UPF实体。
该场景下，对URLLC业务终端，在终端移动过程中，远端UPF实体保持不变，因此IP地址保持不变，但为了保证终端与AS之间路径最短，本地UPF实体和AS可能需要切换。由于AS控制器维护AS的拓扑信息，可以根据本地UPF实体的位置信息和/或终端的位置信息执行AS的选择或重选，因此当本地UPF实体需要切换时，SMF实体需要与AS控制器交互实现AS的重选，进而实现终端和AS之间路径最短。
需要说明的是，图2以不同的本地UPF实体与不同的DN中的AS通信为例进行示意。当然，不同的本地UPF实体也可能与同一DN中的AS通信，即，本地UPF实体发生切换后，AS可能并未发生切换，本申请实施例对此不作具体限定。
场景二：
可选的，若上述实现业务连续性的系统10应用于目前的5G网络，则另一种可能的适用架构如图3所示。图3所示的网络架构对应单锚点的PDU会话场景，即一个PDU会话对应一个UPF实体。具体的，图1中的会话管理功能实体101具体可以为图3中的SMF实体；图1中的控制设备102具体可以为图3中的AS控制器，图1中的目的用户面功能实体具体可以为图3中的UPF实体1，图1中的源用户面功能实体具体可以为图3中的UPF实体2。此外，如图3所示，该网络架构中还可以包括终端、接入设备、AMF实体以及DN，其中，DN中部署有AS。为了保证终端与AS之间的路径最短，UPF实体和AS一般需要本地部署。当然，对于端到端时延要求不高的业务，UPF实体和AS可以不部署在本地，本申请实施例对此不作具体限定。
其中，终端通过N1与AMF实体通信，并通过接入设备与UPF实体(包括UPF实体1至UPF实体n)通信；接入设备通过N2与AMF实体通信，并通过N3与UPF实体(包括UPF实体1至UPF实体n)通信；AMF实体通过N11与SMF实体通信；SMF实体通过N4与UPF实体(包括UPF实体1至UPF实体n)通信；UPF实体(包括UPF实体1至UPF实体n)通过N6与DN(包括DN1至DNn)通信。
该场景下，对URLLC业务终端，在终端移动过程中，UPF实体和AS可能需要切换。由于AS控制器维护AS的拓扑信息，可以根据本地UPF实体的位置信息和/或终端的位置 信息执行AS的选择或重选，因此当UPF实体需要切换时，SMF实体需要与AS控制器交互实现AS的重选，进而实现终端和AS之间路径最短。
需要说明的是，图3以不同的UPF实体与不同的DN中的AS通信为例进行示意。当然，不同的UPF实体也可能与同一DN中的AS通信，即，UPF实体发生切换后，AS可能并未发生切换，本申请实施例对此不作具体限定。
需要说明的是，图2和图3中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能称为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图2和图3中的接入设备、AMF实体、SMF实体、UPF实体、AS和AS控制器等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入设备、AMF实体、SMF实体、UPF实体、AS和AS控制器也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UPF实体还有可能被替换为UP，该AS还有可能被替换为应用管理平台或移动边缘计算(mobile edge computing，MEC)平台，该AS控制器还有可能被替换为车与外界的通信(vehicle to everything communication，V2X)控制功能(Control Function)实体等，在此进行统一说明，以下不再赘述。
可选的，本申请实施例中所涉及到的终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)等。为方便描述，本申请中，上面提到的设备统称为终端。
可选的，本申请实施例中所涉及到的接入设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非3GPP接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
可选的，本申请实施例中所涉及的AMF实体负责注册管理，移动性管理，合法监听等功能。
可选的，本申请实施例中所涉及的SMF实体和AS控制器的功能可参考图1中的描述，在此不再赘述。此外，SMF实体还用于进行会话管理，包括：会话建立，会话修改，会话释放，终端IP地址分配和管理，UPF实体的选择和控制，合法监听等与会话相关的控制功能。
可选的，本申请实施例中所涉及到的UPF实体可负责终端报文的转发、统计等处理功能。例如，UPF实体可实现服务网关(serving gateway，SGW)和分组数据网络网关(packet data network gateway，PGW)的用户面功能。UPF实体还可以是软件定义网络(software defined network，SDN)交换机(Switch)，本申请实施例对此不作具体限定。
可选的，图1中的会话管理功能实体101和控制设备102，可以由一个实体设备实现，也可以由多个实体设备共同实现，还可以是一个实体设备内的一个逻辑功能模块，本申请实施例对此不作具体限定。
例如，如图4所示，图1中的会话管理功能实体101和控制设备102均可以通过图4中的通信设备来实现。
图4所示为本申请实施例提供的通信设备的硬件结构示意图。通信设备400包括至少一个处理器401，通信总线402，存储器403以及至少一个通信接口404。
处理器401可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线402可包括一通路，在上述组件之间传送信息。
通信接口404，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器403可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器403用于存储执行本申请方案的应用程序代码，并由处理器401来控制执行。处理器401用于执行存储器403中存储的应用程序代码，从而实现本申请下述实施例提供的实现业务连续性的方法。
在具体实现中，作为一种实施例，处理器401可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备400可以包括多个处理器，例如图4中的处理器401和处理器408。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信设备400还可以包括输出设备405和输入设备406。输出设备405和处理器401通信，可以以多种方式来显示信息。例如，输出设备405可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备406和处理器401通信，可以以多种方式接受用户的输入。例如，输入设备406可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备400可以是一个通用通信设备或者是一个专用通信设备。在具体实现中，通信设备400可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备或有图4中类似结构的设备。本申请实施例不限定通信设备400的类型。
下面将结合图1至图4对本申请实施例提供的实现业务连续性的方法进行具体阐述。
首先，结合图1所示的实现业务连续性的系统10，本申请实施例提供的实现业务连续性的方法的流程示意图如图5所示，涉及到会话管理功能实体101、控制设备102和目的用户面功能实体103之间的交互，包括如下步骤：
S501、会话管理功能实体选择目的用户面功能实体为终端服务。
S502、会话管理功能实体向控制设备发送第一消息，以使得控制设备接收来自会话管理功能实体的第一消息。
S503、控制设备向会话管理功能实体发送第一AS的指示信息，以使得会话管理功能实体接收来自控制设备的第一AS的指示信息。
可选的，本申请实施例中，第一AS的指示信息可以为第一AS的位置信息，也可以为第一AS的标识信息，还可以为指示AS未发生变更的信息等，本申请实施例对此不作具体限定。
S504、会话管理功能实体根据第一AS的指示信息，向目的用户面功能实体发送第一路由规则，以使得目的用户面功能实体接收来自会话管理功能实体的第一路由规则，该第一路由规则包括：将目的地址为第一AS的地址的数据发送给第一AS。
其中，路由规则的相关描述可参考具体实施方式的前序部分，在此不再赘述。
本申请实施例提供的实现业务连续性的方法中，一方面，由于在会话管理功能实体选择目的用户面功能实体为终端服务后，会话管理功能实体可以接收来自第一AS的指示信息，并根据第一AS的指示信息，向目的用户面功能实体发送第一路由规则，使得目的用户面功能实体可以根据第一路由规则传输业务数据，因此可以保证用户面功能实体切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为第一AS的地址的数据发送给第一AS，因此可以避免目的用户面功能实体将发往第一AS的地址的数据路由到远端DN后再路由到第一AS的问题，从而可以使得终端到第一AS的路径最短，时延可控。
其中，上述S501、S502和S504中会话管理功能实体的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
其中，上述503中控制设备的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
其次，以图1所示的实现业务连续性的系统10应用于图2所示的场景一为例，对图5所示的实现业务连续性的方法进行展开说明。
假设初始状态下，终端通过接入设备(这里假设为源基站)、本地UPF实体2(这里记作源UPF实体)与AS1通信；同时，终端通过源UPF实体、远端UPF实体(这里记作A-UPF实体)与远端DN(这里记作A-DN)通信，则如图6所示，为本申请实施例提供的一种实现业务连续性的方法的流程示意图，涉及到终端、源基站、目的基站、源UPF实体、本地UPF实体1(这里记作目的UPF实体)、A-UPF实体、AMF实体、SMF实体、AS控制器、AS1和AS2之间的交互，包括如下步骤：
S601、当终端移动时，源基站发起无线切换。
其中，源基站发起空口切换的具体实现可参考现有方案，在此不再赘述。
S602、空口切换完成后，目的基站向SMF实体发送路径切换请求，以使得SMF实体接收来自目的基站的路径切换请求。
其中，该路径切换请求中包括目的基站的N3隧道上行信息和终端的位置信息等。目 的基站的N3隧道具体是指目的基站和目的UPF实体之间的隧道。目的基站的N3隧道上行信息具体可以包括目的基站的N3隧道在目的基站侧的端点地址和目的基站的地址等，本申请实施例对此不作具体限定。
S603、SMF实体根据终端的位置信息选择目的UPF实体为终端服务。
可选的，SMF实体确定需要进行本地UPF实体重选的依据可以是终端的位置超出了源UPF实体的服务范围。
可选的，SMF实体可以根据终端的位置信息、SMF实体管理的本地UPF实体的服务能力或负载情况中的至少一个选择目的UPF实体为终端服务，本申请实施例对此不作具体限定。
S604、SMF实体向目的UPF实体发送N4会话建立请求1，以使得目的UPF实体接收来自SMF实体的N4会话建立请求1。
可选的，该N4会话建立请求1中可以包括第二路由规则，该第二路由规则包括：将目的地址为AS1的地址的数据发送给源UPF实体。
可选的，该N4会话建立请求1中可以包括第一路径信息，该第一路径信息用于建立源UPF实体和目的UPF实体之间的转发路径。
其中，本申请实施例中的第一路径信息可以包括源UPF实体的第一N9隧道下行信息。可选的，本申请实施例中的第一路径信息还可以包括目的UPF实体的第一N9隧道上行信息。源UPF实体的第一N9隧道和目的UPF实体的第一N9隧道具体是指源UPF实体和目的UPF实体之间的隧道。源UPF实体的第一N9隧道下行信息具体可以包括源UPF实体的第一N9隧道在源UPF实体侧的端点地址和源UPF实体的地址等，本申请实施例对此不作具体限定。目的UPF实体的第一N9隧道上行信息具体可以包括目的UPF实体的第一N9隧道在目的UPF实体侧的端点地址和目的UPF实体的地址等，本申请实施例对此不作具体限定。其中，源UPF实体的第一N9隧道下行信息可以是由SMF实体分配的，也可以是由源UPF实体分配的，本申请实施例对此不作具体限定。目的UPF实体的第一N9隧道上行信息可以是由SMF实体分配的，也可以是由目的UPF实体分配的，本申请实施例对此不作具体限定。
可选的，该N4会话建立请求1中可以包括第三路由规则，该第三路由规则包括：将目的地址为A-DN的地址的数据或者将目的地址缺省的数据发送给A-UPF实体。
可选的，该N4会话建立请求1中可以包括第三路径信息，该第三路径信息用于建立目的UPF实体与A-UPF实体之间的转发路径。
其中，本申请实施例中的第三路径信息可以包括A-UPF实体的第二N9隧道下行信息。可选的，本申请实施例中的第三路径信息还可以包括目的UPF实体的第二N9隧道上行信息。A-UPF实体的第二N9隧道和目的UPF实体的第二N9隧道具体是指A-UPF实体和目的UPF实体之间的隧道。A-UPF实体的第二N9隧道下行信息具体可以包括A-UPF实体的第二N9隧道在A-UPF实体侧的端点地址和A-UPF实体的地址等，本申请实施例对此不作具体限定。目的UPF实体的第二N9隧道上行信息具体可以包括目的UPF实体的第二N9隧道在目的UPF实体侧的端点地址和目的UPF实体的地址等，本申请实施例对此不作具体限定。其中，A-UPF实体的第二N9隧道下行信息可以是由SMF实体分配的，也可以是由A-UPF实体分配的，本申请实施例对此不作具体限定。目的UPF实体的第二N9隧道上行信息可以是由SMF实体分配的，也可以是由目的UPF实体分配的，本申请实施例对 此不作具体限定。
可选的，该N4会话建立请求1中可以包括第七路径信息，该第七路径信息用于建立目的UPF实体和目的基站之间的转发路径。
其中，本申请实施例中的第七路径信息可以包括上述路径切换请求中的目的基站的N3隧道上行信息。可选的，若目的UPF实体的N3隧道下行信息是由SMF实体分配的，则第七路径信息还可以包括目的UPF实体的N3隧道下行信息，本申请实施例对此不作具体限定。其中，目的UPF实体的N3隧道具体是指目的基站和目的UPF实体之间的隧道。目的UPF实体的N3隧道下行信息具体可以包括目的UPF实体的N3隧道在目的UPF实体侧的端点地址和目的UPF实体的地址等，本申请实施例对此不作具体限定。当然，目的UPF实体的N3隧道下行信息也可以是由目的UPF实体分配的，本申请实施例对此不作具体限定。
此外，该N4会话建立请求1中还可以包括当前PDU会话的其它用户面信息，比如数据包统计与上报规则，服务质量(quality of service，QoS)规则等，本申请实施例对此不作具体限定。
可选的，上述N4会话建立请求1中包括的各个信息也可以是通过不同的消息发送给目的UPF实体，本申请实施例对此不作具体限定。
S605、目的UPF实体向SMF实体发送会话建立应答1，以使得SMF实体接收来自目的UPF实体的会话建立应答1。
S606、SMF实体向源UPF实体发送N4会话建立请求2，以使得目的UPF实体接收来自SMF实体的N4会话建立请求2。
可选的，该N4会话建立请求2中可以包括第四路由规则，该第四路由规则包括：将目的地址为终端的地址的数据发送给目的UPF实体。
可选的，该N4会话建立请求2中可以包括第二路径信息，该第二路径信息用于建立源UPF实体和目的UPF实体之间的转发路径。
其中，本申请实施例中的第二路径信息可以包括目的UPF实体的第一N9隧道上行信息。可选的，本申请实施例中的第二路径信息还可以包括源UPF实体的第一N9隧道下行信息。
可选的，该N4会话建立请求2中还可以包括第一隧道删除指示信息，该第一隧道删除指示信息用于指示删除源UPF实体的N3隧道或将源UPF实体的N3隧道置为无效。其中，源UPF实体的N3隧道具体是指源UPF实体和源基站之间的隧道。
可选的，该N4会话建立请求2中还可以包括第二隧道删除指示信息，该第二隧道删除指示信息用于指示删除源UPF实体的第二N9隧道或将源UPF实体的第二N9隧道置为无效。其中，源UPF实体的第二N9隧道具体是指源UPF实体和A-UPF实体之间的隧道。
此外，该N4会话建立请求2中还可以包括当前PDU会话的其它用户面信息，比如数据包统计与上报规则，QoS规则等，本申请实施例对此不作具体限定。
可选的，上述N4会话建立请求2中包括的各个信息也可以是通过不同的消息发送给源UPF实体，本申请实施例对此不作具体限定。
S607、源UPF实体向SMF实体发送会话建立应答2，以使得SMF实体接收来自源UPF实体的会话建立应答2。
需要说明的是，若步骤S604中的第一路径信息和步骤S606中的第二路径信息均包括 源UPF实体的第一N9隧道下行信息和目的UPF实体的第一N9隧道上行信息，则此时第一路径信息和第二路径信息可以相同；当然，步骤S604中的第一路径信息和步骤S606中的第二路径信息也可以不同，比如，第一路径信息仅包括源UPF实体的第一N9隧道下行信息，第二路径信息仅包括目的UPF实体的第一N9隧道上行信息，本申请实施例对此不作具体限定。
S608、SMF实体向A-UPF实体发送N4会话建立请求3，以使得A-UPF实体接收来自SMF实体的N4会话建立请求3。
可选的，该N4会话建立请求3中可以包括第四路由规则，该第四路由规则包括：将目的地址为终端的地址的数据发送给目的UPF实体。
可选的，该N4会话建立请求3中可以包括第四路径信息，该第四路径信息用于建立A-UPF实体和目的UPF实体之间的转发路径。
其中，本申请实施例中的第四路径信息可以包括目的UPF实体的第二N9隧道上行信息。可选的，本申请实施例中的第四路径信息还可以包括A-UPF实体的第二N9隧道下行信息。
可选的，该N4会话建立请求3中还可以包括第二隧道删除指示信息，该第二隧道删除指示信息用于指示删除A-UPF实体的第一N9隧道或将A-UPF实体的第一N9隧道置为无效。其中，A-UPF实体的第一N9隧道具体是指源UPF实体和A-UPF实体之间的隧道。
此外，该N4会话建立请求3中还可以包括当前PDU会话的其它用户面信息，比如数据包统计与上报规则，QoS规则等，本申请实施例对此不作具体限定。
可选的，上述N4会话建立请求3中包括的各个信息也可以是通过不同的消息发送给源UPF实体，本申请实施例对此不作具体限定。
S609、A-UPF实体向SMF实体发送会话建立应答3，以使得SMF实体接收来自A-UPF实体的会话建立应答3。
需要说明的是，若步骤S604中的第三路径信息和步骤S608中的第四路径信息均包括A-UPF实体的第二N9隧道下行信息和目的UPF实体的第二N9隧道上行信息，则此时第三路径信息和第四路径信息可以相同；当然，步骤S604中的第三路径信息和步骤S608中的第四路径信息也可以不同，比如，第三路径信息仅包括A-UPF实体的第二N9隧道下行信息，第四路径信息仅包括目的UPF实体的第二N9隧道上行信息，本申请实施例对此不作具体限定。
S610、SMF实体向目的基站发送路径切换应答，以使得目的基站接收来自SMF实体的路径切换应答。
可选的，该路径切换应答中可以包括第八路径信息，该第八路径信息用于建立目的基站和目的UPF实体之间的转发路径。
其中，本申请实施例中的第八路径信息可以包括目的UPF实体的N3隧道下行信息。可选的，本申请实施例中的第八路径信息还可以包括目的基站的N3隧道上行信息。
此外，该路径切换应答还可以包括当前PDU会话的其它用户面信息，比如数据包统计与上报规则，QoS规则等，本申请实施例对此不作具体限定。
可选的，上述路径切换应答中包括的各个信息也可以是通过不同的消息发送给目的基站，本申请实施例对此不作具体限定。
需要说明的是，若步骤S604中的第七路径信息和步骤S610中的第八路径信息均包括 目的UPF实体的N3隧道下行信息和目的基站的N3隧道上行信息，则此时第七路径信息和第八路径信息可以相同；当然，步骤S604中的第七路径信息和步骤S610中的第八路径信息也可以不同，比如，第七路径信息仅包括目的基站的N3隧道上行信息，第二路径信息仅包括目的UPF实体的N3隧道下行信息，本申请实施例对此不作具体限定。
S611、目的基站释放源基站资源。
其中，目的基站释放源基站资源的具体实现可参考现有方案，在此不再赘述。
综上，概括的说，通过步骤S604至步骤S611，可以删除：
源UPF实体和源基站之间的隧道，以及源UPF实体和A-UPF实体之间的隧道。
通过步骤S604至步骤S611，可以建立：
源UPF实体和目的UPF实体之间的隧道，以及目的UPF实体和A-UPF实体之间的隧道。
也就是说，通过步骤S604至步骤S611，可以将目的UPF实体插入当前的PDU会话，进而使得终端与AS1之间的通信可以得到维持。此时，目的UPF实体可以看作为PDU会话路径上普通的一跳UPF实体。相应的业务传输路径为：
终端<->目的基站<->目的UPF实体<->源UPF实体<->AS1；
终端<->目的基站<->目的UPF实体<->A-UPF实体<->A-DN。
需要说明的是，步骤S604-S605、步骤S606-S607以及步骤S608-S609之间没有必然的执行先后顺序，可以是先执行S604-S605、步骤S606-S607以及步骤S608-S609中的任一组步骤，再执行剩余两组步骤中的任一组步骤，最后执行剩余的一组步骤。比如，可以先执行步骤S604-S605，再执行步骤S606-S607，最后执行步骤S608-S609。当然，也可以同时执行S604-S605、步骤S606-S607以及步骤S608-S609，本申请实施例对此不作具体限定。
需要说明的是，步骤S604至步骤S610以N9隧道(包括源UPF实体和目的UPF实体之间的隧道，以及目的UPF实体与A-UPF实体之间的隧道)为会话粒度的N9隧道为例进行说明，当然，N9隧道也可以是设备粒度的N9隧道，本申请实施例对此不作具体限定。
其中，当N9隧道为设备粒度的N9隧道时，若设备粒度的N9隧道不存在，则按照上述建立会话粒度N9隧道的方式建立设备粒度的N9隧道。
若设备粒度的N9隧道存在，则可以不用建立设备粒度的N9隧道，而仅是下发该PDU会话对应的路由规则即可。比如，SMF实体向目的UPF实体发送第二路由规则，使得目的UPF实体可以将目的地址为AS1的地址的数据通过源UPF实体和目的UPF实体之间的隧道发送至源UPF实体。或者，比如，SMF实体向源UPF实体发送第四路由规则，使得源UPF实体可以将目的地址为终端的地址的数据通过源UPF实体和目的UPF实体之间的隧道发送至目的UPF实体。或者，比如，SMF实体向目的UPF实体发送第三路由规则，使得目的UPF实体可以将目的地址为A-DN的地址的数据通过目的UPF实体与A-UPF实体之间的隧道发送至A-UPF实体。或者，比如，SMF实体向A-UPF实体发送第四路由规则，使得A-UPF实体可以将目的地址为终端的地址的数据通过目的UPF实体与A-UPF实体之间的隧道发送至目的UPF实体。
其中，当N9隧道为设备粒度的N9隧道时，通常下述几种场景下设备粒度的N9隧道不存在，需要新建设备粒度的N9隧道：
第一，源UPF实体或者目的UPF实体上电时；
第二，需要建立第一条与设备粒度的N9隧道对应的路由规则时；
第三，其他情况。
S612、SMF实体向AS控制器发送第一消息，以使得AS控制器接收来自SMF实体的第一消息。
可选的，本申请实施例中的第一消息可以是PDU会话变更消息。
可选的，本申请实施例中，第一消息可以包括目的UPF实体的位置信息和终端的位置信息中的至少一个，目的UPF实体的位置信息和终端的位置信息中的至少一个用于确定为终端服务的AS为AS2。
可选的，SMF实体可以根据本地策略确定需要向AS控制器发送第一消息。其中，本地策略可以包括业务类型或者5G QoS指示(5G QoS indicator，5QI)。
或者，可选的，SMF实体可能订阅了此类消息。进而，当UPF实体发生变更后，会触发SMF实体向AS控制器发送第一消息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，SMF实体可以是和AS控制器直接通信，也可以是通过网络开放功能(network exposure function，NEF)实体或者策略控制功能(policy control function，PCF)实体与AS控制器通信，在此进行统一说明，以下不再赘述。
需要说明的是，步骤S612与步骤S604-S611之间没有必然的执行先后顺序，可以是先执行步骤S612，再执行步骤S604-S611；还可以是先执行步骤S604-S611，再执行步骤S612；还可以是同时执行步骤S612和步骤S604-S611，本申请实施例对此不作具体限定。
S613、AS控制器根据第一消息，确定为终端服务的AS为AS2。
可选的，AS控制器可以根据第一消息中包括的目的UPF实体的位置信息和终端的位置信息中的至少一个，确定为终端服务的AS为AS2。
S614、AS控制器向AS1发送AS同步请求，以使得AS1接收来自AS控制器的AS同步请求。其中，该AS同步请求用于请求AS1将终端的信息同步至AS2。
其中，同步的终端的信息可以包括业务鉴权信息、历史数据以及上下文等，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中的AS同步请求也可以是其他的名字，名字对消息本身不构成限定。比如，AS同步请求也可以称为AS切换请求，在此进行统一说明，以下不再赘述。
S615、AS1将终端的信息同步至AS2。
S616、AS1向AS控制器发送AS同步应答，以使得AS控制器接收来自AS1的AS同步应答。其中，该同步应答用于指示AS1与AS2之间的同步已经完成。
可选的，也可以是AS2向AS控制器发送AS同步应答，以使得AS控制器接收来自AS2的AS同步应答。其中，该AS同步应答用于指示AS1与AS2之间的同步已经完成，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中的AS同步应答也可以是其他的名字，名字对消息本身不构成限定。比如，AS同步应答也可以称为AS切换应答，在此进行统一说明，以下不再赘述。
S617、AS控制器向SMF实体发送AS2的指示信息，以使得SMF实体接收来自AS控制器的AS2的指示信息。
可选的，AS2的指示信息可以为AS2的位置信息。
S618、SMF实体向目的UPF实体发送分流规则更新请求，以使得目的UPF实体接收来自SMF实体的分流规则更新请求。其中，该分流规则更新请求包括第一路由规则，该第一路由规则包括：将目的地址为AS2的地址的数据发送给AS2。
进而，目的UPF实体在接收来自SMF实体的分流规则更新请求后，可以添加该第一路由规则至本地分流规则。这样，可以使得目的UPF实体将目的地址为AS2的地址的数据发送给AS2，避免了目的UPF实体将发往AS2的地址的数据按照ULCL缺省规则发送给A-UPF实体，通过A-DN发送给AS2的问题，从而可以使得终端到AS2的路径最短，时延可控。
同时，由于目的UPF实体的本地分流规则还包括第二路由规则和第三路由规则，因此目的UPF实体此时仍按照步骤S610中的业务传输路径传输数据，即将目标地址为AS1的数据仍发送给源UPF实体，其余的数据包按照缺省规则发送给A-UPF实体，本申请实施例对此不作具体限定。
此时，相应的业务传输路径为：
终端<->目的基站<->目的UPF实体<->AS2；
终端<->目的基站<->目的UPF实体<->源UPF实体<->AS1；
终端<->目的基站<->目的UPF实体<->A-UPF实体<->A-DN。
S619、目的UPF实体向SMF实体发送分流规则更新应答，以使得AS控制器接收来自SMF实体的分流规则更新应答。其中，该分流规则更新应答用于指示本地分流规则已建立，网络侧路径已经准备完成。
S620、SMF实体向AS控制器发送第七消息，以使得AS控制器接收来自SMF实体的第七消息，该第七消息用于指示将终端从AS1切换到AS2。
S621、AS控制器根据第七消息，将终端从AS1切换到AS2。
S622、AS控制器向SMF实体发送第八消息，以使得SMF实体接收来自AS控制器的第八消息，该第八消息用于指示终端已经从AS1切换到AS2。
S623、SMF实体向目的UPF实体发送N4会话修改请求，以使得目的UPF实体接收来自SMF实体的N4会话修改请求。
可选的，当N9隧道为会话粒度的N9隧道时，该N4会话修改请求中可以包括第一指示信息，该第一指示信息用于指示删除第二路由规则和第一路径信息，也就是说删除源UPF实体和目的UPF实体之间的隧道。
可选的，当N9隧道为设备粒度的N9隧道时，存在以下两种可能的实现方式：
方式一，若目的UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第二路由规则外，还存在其他的路由规则，则该N4会话修改请求中可以包括第二指示信息，该第二指示信息用于指示删除第二路由规则。
或者，若目的UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第二路由规则外，不存在其他的路由规则，则该N4会话修改请求中可以包括第一指示信息，该第一指示信息用于指示删除第二路由规则和第一路径信息，也就是说删除源UPF实体和目的UPF实体之间的隧道。
方式二，无论目的UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第二路由规则外，是否存在其他的路由规则，该N4会话修改请求中仅包括第二指示信息，该第二指示信息用于指示删除第二路由规则。也就是说，当N9隧道为设备粒 度的隧道时，在进行用户面资源释放时，不释放设备粒度的隧道，仅删除当前PDU会话对应的路由规则。
其中，第二路由规则和第一路径信息的相关描述可参考步骤S604，在此不再赘述。
可选的，上述N4会话修改请求中包括的各个信息也可以是通过不同的消息发送给目的UPF实体，本申请实施例对此不作具体限定。
S624、目的UPF实体向SMF实体发送N4会话修改应答，以使得SMF实体接收来自目的UPF实体的N4会话修改应答。
S625、SMF实体向源UPF实体发送N4会话释放请求，以使得源UPF实体接收来自SMF实体的N4会话释放请求。
其中，该N4会话释放请求用于请求删除源UPF实体中该终端对应的用户面信息。
可选的，当N9隧道为会话粒度的N9隧道时，该N4会话修改请求中可以包括第三指示信息，该第三指示信息用于指示删除第四路由规则和第二路径信息，也就是说删除源UPF实体和目的UPF实体之间的隧道。
可选的，当N9隧道为设备粒度的N9隧道时，存在以下两种可能的实现方式：
方式一，若源UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第四路由规则外，还存在其他的路由规则，则该N4会话释放请求中可以包括第四指示信息，该第四指示信息用于指示删除第四路由规则。
或者，若源UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第四路由规则外，不存在其他的路由规则，则该N4会话释放请求中可以包括第三指示信息，该第三指示信息用于指示删除第四路由规则和第二路径信息，也就是说删除源UPF实体和目的UPF实体之间的隧道。
方式二，无论源UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第四路由规则外，是否存在其他的路由规则，该N4会话释放请求中仅包括第四指示信息，该第四指示信息用于指示删除第四路由规则。也就是说，当N9隧道为设备粒度的隧道时，在进行用户面资源释放时，不释放设备粒度的隧道，仅删除当前PDU会话对应的路由规则。
其中，第四路由规则和第二路径信息的相关描述可参考步骤S606，在此不再赘述。
可选的，该终端对应的用户面信息除了上述第四路由规则和第二路径信息之外，还可以包括包检测规则、QoS规则等，本申请实施例对此不作具体限定。
可选的，上述N4会话释放请求中包括的各个信息也可以是通过不同的消息发送给源UPF实体，本申请实施例对此不作具体限定。
S626、源UPF实体向SMF实体发送N4会话释放应答，以使得SMF实体接收来自源UPF实体的N4会话释放应答。
综上，概括的说，通过步骤S623至步骤S626，可以删除：源UPF实体和目的UPF实体之间的隧道，至此，终端与AS1之间的通信结束。相应的业务传输路径为：
终端<->目的基站<->目的UPF实体<->AS2；
终端<->目的基站<->目的UPF实体<->A-UPF实体<->A-DN。
需要说明的是，步骤S623-S624与步骤S625-S626之间没有必然的执行先后顺序，可以是先执行步骤S623-S624，再执行步骤S625-S626；还可以是先执行步骤S625-S626，再执行步骤S623-S624；还可以是同时执行步骤S623-S624与步骤S625-S626，本申请实施例 对此不作具体限定。
本申请实施例提供的实现业务连续性的方法中，一方面，由于在SMF实体选择目的UPF实体为终端服务后，SMF实体可以接收来自AS2的指示信息，并根据AS2的指示信息，向目的UPF实体发送第一路由规则，使得目的UPF实体可以在终端从AS1切换到AS2之后，根据第一路由规则传输业务数据。并且，SMF实体可以在终端从AS1切换到AS2之前，继续维持终端与AS1之间的业务连接。因此可以在UPF实体和AS实体同时切换的场景下实现业务数据的无缝切换，保证切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为AS2的数据发送给AS2，因此可以避免目的UPF实体将发往AS2的地址的数据路由到A-DN后再路由到AS2的问题，从而可以使得终端到AS2的路径最短，时延可控。
其中，上述603、S604、S606、S608、S610、S612、S618、S620、S621、S623和S625中SMF实体的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
其中，上述S613、S614、S617、S621和S622中AS控制器的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，假设初始状态下，终端通过接入设备(这里假设为源基站)、本地UPF实体2(这里记作源UPF实体)与AS1通信；同时，终端通过源UPF实体、远端UPF实体(这里记作A-UPF实体)与远端DN(这里记作A-DN)通信，则如图7所示，为本申请实施例提供的另一种实现业务连续性的方法的流程示意图，涉及到终端、源基站、目的基站、源UPF实体、本地UPF实体1(这里记作目的UPF实体)、A-UPF实体、AMF实体、SMF实体、AS控制器和AS1之间的交互，包括如下步骤：
S701-S712、同S601-S612，具体可参考图6所示的实施例，在此不再赘述。
S713、AS控制器根据第一消息，确定为终端服务的AS为AS1。
可选的，AS控制器可以根据第一消息中包括的目的UPF实体的位置信息和终端的位置信息中的至少一个，确定为终端服务的AS为AS1。
S714、AS控制器向SMF实体发送AS1的指示信息，以使得SMF实体接收来自AS控制器的AS1的指示信息。
可选的，AS1的指示信息可以为AS1的位置信息或者AS1的标识信息或者指示AS1未发生变更的信息等，本申请实施例对此不作具体限定。
其中，SMF实体接收来自AS控制器的AS1的指示信息之后，可以根据AS1的指示信息确定AS未发生切换。比如，若AS1的指示信息为AS1的位置信息，可以将AS1的位置信息和当前AS的位置信息进行对比，若相同，确定AS未发生切换。
S715、SMF实体向目的UPF实体发送N4会话修改请求，以使得目的UPF实体接收来自SMF实体的N4会话修改请求。
其中，N4会话修改请求包括第一路由规则，该第一路由规则包括：将目的地址为AS1的地址的数据发送给AS1。进而，目的UPF实体在接收来自SMF实体的第一路由规则后，可以添加该第一路由规则至本地分流规则。
可选的，当N9隧道为会话粒度的N9隧道时，该N4会话修改请求中可以包括第一指示信息，该第一指示信息用于指示删除第二路由规则和第一路径信息，也就是说删除源UPF 实体和目的UPF实体之间的隧道。
可选的，当N9隧道为设备粒度的N9隧道时，存在以下两种可能的实现方式：
方式一，若目的UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第二路由规则外，还存在其他的路由规则，则该N4会话修改请求中可以包括第二指示信息，该第二指示信息用于指示删除第二路由规则。
或者，若目的UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第二路由规则外，不存在其他的路由规则，则该N4会话修改请求中可以包括第一指示信息，该第一指示信息用于指示删除第二路由规则和第一路径信息，也就是说删除源UPF实体和目的UPF实体之间的隧道。
方式二，无论目的UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第二路由规则外，是否存在其他的路由规则，该N4会话修改请求中仅包括第二指示信息，该第二指示信息用于指示删除第二路由规则。也就是说，当N9隧道为设备粒度的隧道时，在进行用户面资源释放时，不释放设备粒度的隧道，仅删除当前PDU会话对应的路由规则。
其中，第二路由规则和第一路径信息的相关描述可参考步骤S704，在此不再赘述。
可选的，上述N4会话修改请求中包括的各个信息也可以是通过不同的消息发送给目的UPF实体，本申请实施例对此不作具体限定。
S716、目的UPF实体向SMF实体发送N4会话修改应答，以使得SMF实体接收来自目的UPF实体的N4会话修改应答。
其中，由于步骤S715中的第一指示信息或第二指示信息用于指示删除第二路由规则，因此可以使得目的UPF实体将目的地址为AS1的地址的数据直接发送给AS1，不用再经过源UPF实体的转发，使得终端到AS1的路径最短，时延可控。
另外，由于目的UPF实体的本地分流规则还包括第三路由规则，因此目的UPF实体此时仍将其余的数据包按照缺省规则发送给A-UPF实体，本申请实施例对此不作具体限定。
此时，相应的业务传输路径为：
终端<->目的基站<->目的UPF实体<->AS1；
终端<->目的基站<->目的UPF实体<->A-UPF实体<->A-DN。
S717、SMF实体向源UPF实体发送N4会话释放请求，以使得源UPF实体接收来自SMF实体的N4会话释放请求。
其中，该N4会话释放请求用于请求删除源UPF实体中该终端对应的用户面信息。
可选的，当N9隧道为会话粒度的N9隧道时，该N4会话修改请求中可以包括第三指示信息，该第三指示信息用于指示删除第四路由规则和第二路径信息，也就是说删除源UPF实体和目的UPF实体之间的隧道。
可选的，当N9隧道为设备粒度的N9隧道时，存在以下两种可能的实现方式：
方式一，若源UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第四路由规则外，还存在其他的路由规则，则该N4会话释放请求中可以包括第四指示信息，该第四指示信息用于指示删除第四路由规则。
或者，若源UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第四路由规则外，不存在其他的路由规则，则该N4会话释放请求中可以包括第三指示信息，该第三指示信息用于指示删除第四路由规则和第二路径信息，也就是说删除源UPF 实体和目的UPF实体之间的隧道。
方式二，无论源UPF实体中，源UPF实体和目的UPF实体之间的隧道所对应的路由规则除第四路由规则外，是否存在其他的路由规则，该N4会话释放请求中仅包括第四指示信息，该第四指示信息用于指示删除第四路由规则。也就是说，当N9隧道为设备粒度的隧道时，在进行用户面资源释放时，不释放设备粒度的隧道，仅删除当前PDU会话对应的路由规则。
其中，第四路由规则和第二路径信息的相关描述可参考步骤S706，在此不再赘述。
可选的，该终端对应的用户面信息除了上述第四路由规则和第二路径信息之外，还可以包括包检测规则、QoS规则等，本申请实施例对此不作具体限定。
可选的，上述N4会话释放请求中包括的各个信息也可以是通过不同的消息发送给源UPF实体，本申请实施例对此不作具体限定。
S718、源UPF实体向SMF实体发送N4会话释放应答，以使得SMF实体接收来自源UPF实体的N4会话释放应答。
通过步骤S715至步骤S718，可以删除：源UPF实体和目的UPF实体之间的隧道。
需要说明的是，步骤S715-S716与步骤S717-S718之间没有必然的执行先后顺序，可以是先执行步骤S717-S718，再执行步骤S715-S716；还可以是先执行步骤S715-S716，再执行步骤S717-S718；还可以是同时执行步骤S715-S716与步骤S717-S718，本申请实施例对此不作具体限定。
本申请实施例提供的实现业务连续性的方法中，一方面，由于在SMF实体选择目的UPF实体为终端服务后，SMF实体可以接收来自AS1的指示信息，并根据AS1的指示信息，向目的UPF实体发送第一路由规则，使得目的UPF实体可以根据第一路由规则传输业务数据。并且，SMF实体可以在AS控制器确定AS是否切换之前，继续维持终端与AS1之间的业务连接。因此可以在UPF实体切换的场景下实现业务数据的无缝切换，保证切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为AS1的数据发送给AS1，因此可以避免目的UPF实体将发往AS1的地址的数据路由到A-DN后再路由到AS1的问题，从而可以使得终端到AS1的路径最短，时延可控。
其中，上述703、S704、S706、S708、S710、S712、S715和S717中SMF实体的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
其中，上述S713和S714中AS控制器的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
下面以图1所示的实现业务连续性的系统10应用于图3所示的场景二为例，对图5所示的实现业务连续性的方法进行展开说明。
假设初始状态下，终端通过接入设备(这里假设为源基站)、UPF实体2(这里记作源UPF实体)与AS1通信，则如图8所示，为本申请实施例提供的一种实现业务连续性的方法的流程示意图，涉及到终端、源基站、目的基站、源UPF实体、UPF实体1(这里记作目的UPF实体)、AMF实体、SMF实体、AS控制器、AS1和AS2之间的交互，包括如下步骤：
S801-S802、同S601-S602，具体可参考图6所示的实施例，在此不再赘述。
S803、SMF实体确定需要进行UPF实体重选。
可选的，SMF实体确定需要进行本地UPF实体重选的依据可以是终端的位置超出了源UPF实体的服务范围。
S804、SMF实体向源UPF实体发送N4会话建立请求，以使得目的UPF实体接收来自SMF实体的N4会话建立请求。
可选的，该N4会话建立请求中可以包括第五路由规则，该第五路由规则包括：将目的地址为终端的地址的数据发送给目的基站。
可选的，该N4会话建立请求中可以包括第九路径信息，该第九路径信息用于建立源UPF实体和基站之间的转发路径。
其中，本申请实施例中的第九路径信息可以包括步骤S802路径切换请求中的目的基站的N3隧道上行信息。可选的，本申请实施例中的第九路径信息还可以包括源UPF实体的N3隧道下行信息。源UPF实体的N3隧道和目的基站的N3隧道具体是指源UPF实体和目的基站之间的隧道。其中，目的基站的N3隧道上行信息具体可以包括目的基站的N3隧道在目的基站侧的端点地址和目的基站的地址等，本申请实施例对此不作具体限定。源UPF实体的N3隧道下行信息具体可以包括源UPF实体的N3隧道在源UPF实体侧的端点地址和源UPF实体的地址等，本申请实施例对此不作具体限定。其中，源UPF实体的N3隧道下行信息可以是由SMF实体分配的，也可以是由源UPF实体分配的，本申请实施例对此不作具体限定。
可选的，该N4会话建立请求中还可以包括第一隧道删除指示信息，该第一隧道删除指示信息用于指示删除源UPF实体的N3隧道或将源UPF实体的N3隧道置为无效。其中，源UPF实体的N3隧道具体是指源UPF实体和源基站之间的隧道。
此外，该N4会话建立请求中还可以包括当前PDU会话的其它用户面信息，比如数据包统计与上报规则，QoS规则等，本申请实施例对此不作具体限定。
可选的，上述N4会话建立请求中包括的各个信息也可以是通过不同的消息发送给源UPF实体，本申请实施例对此不作具体限定。
S805、源UPF实体向SMF实体发送会话建立应答，以使得SMF实体接收来自源UPF实体的会话建立应答。
S806、SMF实体向目的基站发送路径切换应答，以使得目的基站接收来自SMF实体的路径切换应答。
可选的，该路径切换应答中可以包括第十路径信息，该第十路径信息用于建立目的基站和源UPF实体之间的转发路径。
其中，本申请实施例中的第十路径信息可以包括源UPF实体的N3隧道下行信息。可选的，本申请实施例中的第十路径信息还可以包括目的基站的N3隧道上行信息。
此外，该路径切换应答还可以包括当前PDU会话的其它用户面信息，比如数据包统计与上报规则，QoS规则等，本申请实施例对此不作具体限定。
可选的，上述路径切换应答中包括的各个信息也可以是通过不同的消息发送给目的基站，本申请实施例对此不作具体限定。
需要说明的是，若步骤S804中的第九路径信息和步骤S806中的第十路径信息均包括源UPF实体的N3隧道下行信息以及目的基站的N3隧道上行信息，则此时第九路径信息和第十路径信息可以相同；当然，步骤S804中的第九路径信息和步骤S806中的第十路径信息也可以不同，比如，第九路径信息仅包括目的基站的N3隧道上行信息，第十路径信 息仅包括源UPF实体的N3隧道下行信息，本申请实施例对此不作具体限定。
S807、目的基站释放源基站资源。
其中，目的基站释放源基站资源的具体实现可参考现有方案，在此不再赘述。
综上，概括的说，通过步骤S804至步骤S807，可以删除：源UPF实体和源基站之间的隧道。
通过步骤S804至步骤S806，可以建立：源UPF实体和目的基站之间的隧道。
也就是说，通过步骤S804至步骤S807，可以使得终端与AS1之间的通信可以得到维持。此时，相应的业务传输路径为：
终端<->目的基站<->源UPF实体<->AS1。
S808、SMF实体向终端发送PDU会话重建通知，以使得终端接收来自SMF实体的PDU会话重建通知。其中，该PDU会话重建通知包括待重建的PDU会话的标识(PDU session ID)。
需要说明的是，步骤S804-S807与步骤S808之间没有必然的执行先后顺序，可以是先执行步骤S804-S807，再执行步骤S808；还可以是先执行步骤S808，再执行步骤S804-S807；还可以是同时执行S804-S807与步骤S808，本申请实施例对此不作具体限定。
S809、终端发起新PDU会话(这里记作第二PDU会话)建立流程。其中，在建立第二PDU会话的过程中，SMF实体选择目的UPF实体为终端服务。
可选的，在建立第二PDU会话的过程中，终端可以向SMF实体发送第二PDU会话的标识和旧PDU会话(这里记作第一PDU会话)的标识，以使得SMF实体接收来自终端的第一PDU会话的标识和第二PDU会话的标识，并根据第一PDU会话的标识和第二PDU会话的标识维护第一PDU会话和第二PDU会话的映射关系，本申请实施例对此不作具体限定。
S810-S815、同S612-S617，具体可参考图6所示的实施例，在此不再赘述。
S816、SMF实体向目的UPF实体发送N4会话修改请求，以使得目的UPF实体接收来自SMF实体的N4会话修改请求。
其中，N4会话修改请求包括第一路由规则，该第一路由规则包括：将目的地址为AS2的地址的数据发送给AS2。
S817、目的UPF实体向SMF实体发送N4会话修改应答，以使得SMF实体接收来自目的UPF实体的N4会话修改应答。其中，N4会话修改应答用于指示终端与AS2的底层网络管道建立完成。
由于当前存在第一PDU会话和第二PDU会话两个会话，因此当前相应的业务传输路径为：终端<->目的基站<->源UPF实体<->AS1；
终端<->目的基站<->目的UPF实体<->AS2。
S818-S820、同S620-S622，具体可参考图6所示的实施例，在此不再赘述。
S821、SMF实体向终端发送第六消息，以使得终端接收来自SMF实体的第六消息。其中，该第六消息用于指示终端释放第一PDU会话。
S822、终端根据第六消息，释放第一PDU会话。
其中，终端释放第一PDU会话的流程可参考现有技术，在此不再赘述。
本申请实施例提供的实现业务连续性的方法中，一方面，由于在SMF实体选择目的UPF实体为终端服务后，SMF实体可以接收来自AS2的指示信息，并根据AS2的指示信 息，向目的UPF实体发送第一路由规则，使得目的UPF实体可以在终端从AS1切换到AS2之后，根据第一路由规则传输业务数据。并且，SMF实体可以在终端从AS1切换到AS2之前，继续维持终端与AS1之间的业务连接。因此可以在UPF实体和AS实体同时切换的场景下实现业务数据的无缝切换，保证切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为AS2的数据发送给AS2，因此可以避免目的UPF实体将发往AS2的地址的数据路由到远端DN后再路由到AS2的问题，从而可以使得终端到AS2的路径最短，时延可控。
其中，上述803、S804、S806、S808、S809、S810、S816、S818、S819、S821和S822中SMF实体的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
其中，上述S811、S812、S815、S819和S820中AS控制器的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，假设初始状态下，终端通过接入设备(这里假设为源基站)、UPF实体2(这里记作源UPF实体)与AS1通信，则如图9所示，为本申请实施例提供的一种实现业务连续性的方法的流程示意图，涉及到终端、源基站、目的基站、源UPF实体、UPF实体1(这里记作目的UPF实体)、AMF实体、SMF实体、AS控制器和AS1之间的交互，包括如下步骤：
S901-S910、同S801-S810，具体可参考图8所示的实施例，在此不再赘述。
S911、AS控制器根据第一消息，确定为终端服务的AS为AS1。
可选的，AS控制器可以根据第一消息中包括的目的UPF实体的位置信息和终端的位置信息中的至少一个，确定为终端服务的AS为AS1。
S912、AS控制器向SMF实体发送AS1的指示信息，以使得SMF实体接收来自AS控制器的AS1的指示信息。
可选的，AS1的指示信息可以包括AS1的位置信息或者AS1的标识信息或者指示AS1未发生变更的信息等，本申请实施例对此不作具体限定。
其中，SMF实体接收来自AS控制器的AS1的指示信息之后，可以根据AS1的指示信息确定AS未发生切换。比如，若AS1的指示信息为AS1的位置信息，可以将AS1的位置信息和当前AS的位置信息进行对比，若相同，确定AS未发生切换。
S913、SMF实体向目的UPF实体发送N4会话修改请求，以使得目的UPF实体接收来自SMF实体的N4会话修改请求。
其中，N4会话修改请求包括第一路由规则，该第一路由规则包括：将目的地址为AS1的地址的数据发送给AS1。
S914、目的UPF实体向SMF实体发送N4会话修改应答，以使得SMF实体接收来自目的UPF实体的N4会话修改应答。其中，N4会话修改应答用于指示终端与AS2的底层网络管道建立完成。
由于当前存在第一PDU会话和第二PDU会话两个会话，因此当前相应的业务传输路径为：终端<->目的基站<->源UPF实体<->AS1；
终端<->目的基站<->目的UPF实体<->AS2。
S915、SMF实体向终端发送第六消息，以使得终端接收来自SMF实体的第六消息。 其中，该第六消息用于指示终端释放第一PDU会话。
S916、终端根据第六消息，释放第一PDU会话。
其中，终端释放第一PDU会话的流程可参考现有技术，在此不再赘述。
本申请实施例提供的实现业务连续性的方法中，一方面，由于在SMF实体选择目的UPF实体为终端服务后，SMF实体可以接收来自AS1的指示信息，并根据AS1的指示信息，向目的UPF实体发送第一路由规则，使得目的UPF实体可以根据第一路由规则传输业务数据。并且，SMF实体可以在AS控制器确定AS是否切换之前，继续维持终端与AS1之间的业务连接。因此可以在UPF实体切换的场景下实现业务数据的无缝切换，保证切换过程中业务的连续性。另一方面，由于第一路由规则为将目的地址为AS1的数据发送给AS1，因此可以避免目的UPF实体将发往AS1的地址的数据路由到远端DN后再路由到AS1的问题，从而可以使得终端到AS1的路径最短，时延可控。
其中，上述903、S904、S906、S908、S909、S910、S913、S915和S916中SMF实体的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
其中，上述S911和S912中AS控制器的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述会话管理功能实体和控制设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对会话管理功能实体和控制设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图10示出了上述实施例中所涉及的会话管理功能实体100的一种可能的结构示意图。该会话管理功能实体100包括选择模块1001、发送模块1002和接收模块1003。选择模块1001，用于选择目的用户面功能实体为终端服务。发送模块1002，用于向控制设备发送第一消息。接收模块1003，用于接收来自控制设备的第一AS的指示信息。发送模块1002，还用于根据第一AS的指示信息，向目的用户面功能实体发送第一路由规则，第一路由规则包括：将目的地址为第一AS的地址的数据发送给第一AS。
可选的，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之后，向目的用户面功能实体发送第一路由规则之前，向目的用户面功能实体发送第二路由规则，第二路由规则包括：将目的地址为第二AS的地址的数据发送给源用户面功能实体，其中，第二AS为当前为终端服务的AS，源用户面功能实体为与第二AS通信连接的用户面功能实体。
可选的，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之后，向目的用户面功能实体发送第一路径信息。以及，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之后，向源用户面功能实体发送第二路径信息，其中，第一路径信息和第二路径信息用于建立目的用户面功能实体和源用户面功能实体之间的转发路径。
可选的，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之后，向目的用户面功能实体发送第三路由规则，第三路由规则包括：将目的地址为第一数据网络的地址的数据发送给远端用户面功能实体，其中，远端用户面功能实体为与第一数据网络通信连接的用户面功能实体。
可选的，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之后，向目的用户面功能实体发送第三路径信息；以及，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之后，向远端用户面功能实体发送第四路径信息，其中，第三路径信息和第四路径信息用于建立目的用户面功能实体和远端用户面功能实体之间的转发路径。
可选的，发送模块1002，还用于在向目的用户面功能实体发送第一路由规则之后，向目的用户面功能实体发送第二消息，第二消息用于请求删除第二路由规则。
可选的，发送模块1002，还用于在向目的用户面功能实体发送第一路由规则之后，向目的用户面功能实体发送第三消息，第三消息用于请求删除第一路径信息。
可选的，发送模块1002，还用于在向目的用户面功能实体发送第一路由规则之后，向源用户面功能实体发送第四消息，第四消息用于请求删除源用户面功能实体中终端对应的用户面信息，用户面信息包括第二路径信息。
可选的，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之前，向目的基站发送第五路径信息；以及，发送模块1002，还用于在选择模块1001选择目的用户面功能实体为终端服务之前，向源用户面功能实体发送第六路径信息，其中，五路径信息和第六路径信息用于建立目的基站和源用户面功能实体之间的转发路径，源用户面功能实体为当前与终端建立第一PDU会话的用户面功能实体，目的基站为当前与目的用户面功能实体通信连接的基站。
可选的，选择模块1001具体用于：向终端发送第五消息，第五消息用于请求建立第二PDU会话；在建立第二PDU会话的过程中，选择目的用户面功能实体为终端服务。
可选的，发送模块1002，用于在向目的用户面功能实体发送第一路由规则之后，向终端发送第六消息，第六消息用于请求释放第一PDU会话。
可选的，发送模块1002，还用于在向目的用户面功能实体发送第一路由规则之后，向控制设备发送第七消息，第七消息用于请求将终端从第二AS切换至第一AS，其中，第二AS为当前为终端服务的AS。
可选的，接收模块1003，还用于在发送模块1002向控制设备发送第七消息之后，接收来自控制设备的第八消息，第八消息用于指示终端已经从第二AS切换至第一AS。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
以采用集成的方式划分各个功能模块的情况下，图11示出了上述实施例中所涉及的会话管理功能实体110的一种可能的结构示意图，该会话管理功能实体110包括：处理模块 1101和通信模块1102。其中，该处理模块1101可用于执行图10中选择模块1001所能执行的操作，该通信模块1102可用于执行图10中接收模块1003和发送模块1002所能执行的操作，具体可参考图10所示的实施例，本申请实施例在此不再赘述。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该会话管理功能实体以对应各个功能划分各个功能模块的形式来呈现，或者，该会话管理功能实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(Application-Specific Integrated Circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到会话管理功能实体100或者会话管理功能实体110可以采用图4所示的形式。比如，图10中的选择模块1001、发送模块1002和接收模块1003可以通过图4的处理器401和存储器403来实现。具体的，选择模块1001、发送模块1002和接收模块1003可以通过由处理器401来调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。或者，比如，图11中的处理模块1101和通信模块1102可以通过图4的处理器401和存储器403来实现。具体的，处理模块1101和通信模块1102可以通过由处理器401来调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
由于本申请实施例提供的会话管理功能实体可用于执行上述实现业务连续性的方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
比如，在采用对应各个功能划分各个功能模块的情况下，图12示出了上述实施例中所涉及的控制设备的一种可能的结构示意图，该控制设备120包括：接收模块1201和发送模块1202。接收模块1201，用于接收来自会话管理功能实体的第一消息。发送模块1202，用于向会话管理功能实体发送第一AS的指示信息，第一AS的指示信息用于指示会话管理功能实体向目的用户面功能实体发送第一路由规则，第一路由规则包括：将目的地址为第一AS的地址的数据发送给第一AS。
可选的，如图12所示，控制设备120还包括切换模块1203。接收模块1201，还用于在发送模块1202向会话管理功能实体发送第一AS的指示信息之后，接收来自会话管理功能实体的第七消息，第七消息用于指示将终端从第二AS切换至第一AS，其中，第二AS为当前为终端服务的AS。切换模块1203，用于根据第七消息，将终端从第二AS切换至第一AS。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
以采用集成的方式划分各个功能模块的情况下，图13示出了上述实施例中所涉及的控制设备130的一种可能的结构示意图，该控制设备130包括：通信模块1301。其中，该通信模块1301可用于执行图12中接收模块1201和发送模块1202所能执行的操作，具体可参考图12所示的实施例，本申请实施例在此不再赘述。
可选的，如图13所示，本申请实施例提供的控制设备130还可以包括处理模块1302。其中，该处理模块1302可用于执行图12中切换模块1203所能执行的操作，具体可参考图12所示的实施例，本申请实施例在此不再赘述。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功 能描述，在此不再赘述。
在本实施例中，该控制设备以对应各个功能划分各个功能模块的形式来呈现，或者，该控制设备以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(Application-Specific Integrated Circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到控制设备120或者控制设备130可以采用图4所示的形式。比如，图12中的接收模块1201、发送模块1202和切换模块1203可以通过图4的处理器401和存储器403来实现。具体的，接收模块1201、发送模块1202和切换模块1203可以通过由处理器401来调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。或者，比如，图13中的处理模块1302和通信模块1301可以通过图4的处理器401和存储器403来实现。具体的，处理模块1302和通信模块1301可以通过由处理器401来调用存储器403中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
由于本申请实施例提供的控制设备可用于执行上述实现业务连续性的方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (42)

  1. 一种实现业务连续性的方法，其特征在于，所述方法包括：
    会话管理功能实体选择目的用户面功能实体为终端服务；
    所述会话管理功能实体向控制设备发送第一消息；
    所述会话管理功能实体接收来自所述控制设备的第一应用服务器AS的指示信息；
    所述会话管理功能实体根据所述第一AS的指示信息，向所述目的用户面功能实体发送第一路由规则，所述第一路由规则包括：将目的地址为所述第一AS的地址的数据发送给所述第一AS。
  2. 根据权利要求1所述的方法，其特征在于，在所述会话管理功能实体选择目的用户面功能实体为所述终端服务之后，所述会话管理功能实体向所述目的用户面功能实体发送第一路由规则之前，还包括：
    所述会话管理功能实体向所述目的用户面功能实体发送第二路由规则，所述第二路由规则包括：将目的地址为第二AS的地址的数据发送给源用户面功能实体，其中，所述第二AS为当前为所述终端服务的AS，所述源用户面功能实体为与所述第二AS通信连接的用户面功能实体。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述会话管理功能实体选择目的用户面功能实体为所述终端服务之后，还包括：
    所述会话管理功能实体向所述目的用户面功能实体发送第一路径信息；以及，所述会话管理功能实体向所述源用户面功能实体发送第二路径信息，其中，所述第一路径信息和所述第二路径信息用于建立所述目的用户面功能实体和所述源用户面功能实体之间的转发路径。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，在所述会话管理功能实体选择目的用户面功能实体为所述终端服务之后，还包括：
    所述会话管理功能实体向所述目的用户面功能实体发送第三路由规则，所述第三路由规则包括：将目的地址为第一数据网络的地址的数据发送给远端用户面功能实体，其中，所述远端用户面功能实体为与所述第一数据网络通信连接的用户面功能实体。
  5. 根据权利要求4所述的方法，其特征在于，在所述会话管理功能实体选择目的用户面功能实体为所述终端服务之后，还包括：
    所述会话管理功能实体向所述目的用户面功能实体发送第三路径信息；以及，所述会话管理功能实体向所述远端用户面功能实体发送第四路径信息，其中，所述第三路径信息和所述第四路径信息用于建立所述目的用户面功能实体和所述远端用户面功能实体之间的转发路径。
  6. 根据权利要求2所述的方法，其特征在于，在所述会话管理功能实体向所述目的用户面功能实体发送第一路由规则之后，还包括：
    所述会话管理功能实体向所述目的用户面功能实体发送第二消息，所述第二消息用于请求删除所述第二路由规则。
  7. 根据权利要求3所述的方法，其特征在于，在所述会话管理功能实体向所述目的用户面功能实体发送第一路由规则之后，还包括：
    所述会话管理功能实体向所述目的用户面功能实体发送第三消息，所述第三消息用于请求删除所述第一路径信息。
  8. 根据权利要求3或7所述的方法，其特征在于，在所述会话管理功能实体向所述目的用户面功能实体发送第一路由规则之后，还包括：
    所述会话管理功能实体向所述源用户面功能实体发送第四消息，所述第四消息用于请求删除所述源用户面功能实体中所述终端对应的用户面信息，所述用户面信息包括所述第二路径信息。
  9. 根据权利要求1所述的方法，其特征在于，在所述会话管理功能实体选择目的用户面功能实体为所述终端服务之前，还包括：
    所述会话管理功能实体向目的基站发送第五路径信息；以及，所述会话管理功能实体向源用户面功能实体发送第六路径信息，其中，所述五路径信息和所述第六路径信息用于建立所述目的基站和所述源用户面功能实体之间的转发路径，所述源用户面功能实体为当前与所述终端建立第一分组数据单元PDU会话的用户面功能实体，所述目的基站为当前与所述目的用户面功能实体通信连接的基站。
  10. 根据权利要求9所述的方法，其特征在于，所述会话管理功能实体选择目的用户面功能实体为所述终端服务，包括：
    所述会话管理功能实体向所述终端发送第五消息，所述第五消息用于请求建立第二PDU会话；
    在建立所述第二PDU会话的过程中，所述会话管理功能实体选择所述目的用户面功能实体为所述终端服务。
  11. 根据权利要求10所述的方法，其特征在于，在所述会话管理功能实体向所述目的用户面功能实体发送第一路由规则之后，还包括：
    所述会话管理功能实体向所述终端发送第六消息，所述第六消息用于请求释放所述第一PDU会话。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，在所述会话管理功能实体向所述目的用户面功能实体发送第一路由规则之后，还包括：
    所述会话管理功能实体向所述控制设备发送第七消息，所述第七消息用于请求将所述终端从第二AS切换至所述第一AS，其中，所述第二AS为当前为所述终端服务的AS。
  13. 根据权利要求12所述的方法，其特征在于，在所述会话管理功能实体向所述控制设备发送第七消息之后，还包括：
    所述会话管理功能实体接收来自所述控制设备的第八消息，所述第八消息用于指示所述终端已经从所述第二AS切换至所述第一AS。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，所述第一消息包括所述目的用户面功能实体的位置信息和所述终端的位置信息中的至少一个，所述目的用户面功能实体的位置信息和所述终端的位置信息中的至少一个用于确定为所述终端服务的AS为所述第一AS。
  15. 根据权利要求1-14任一项所述的方法，其特征在于，所述第一AS的指示信息包括所述第一AS的位置信息。
  16. 一种实现业务连续性的方法，其特征在于，所述方法包括：
    控制设备接收来自会话管理功能实体的第一消息；
    所述控制设备向所述会话管理功能实体发送第一应用服务器AS的指示信息，所述第一AS的指示信息用于指示所述会话管理功能实体向目的用户面功能实体发送第一路由规 则，所述第一路由规则包括：将目的地址为所述第一AS的地址的数据发送给所述第一AS。
  17. 根据权利要求16所述的方法，其特征在于，所述第一消息包括所述目的用户面功能实体的位置信息和所述终端的位置信息中的至少一个，所述目的用户面功能实体的位置信息和所述终端的位置信息中的至少一个用于确定为所述终端服务的AS为所述第一AS。
  18. 根据权利要求16或17所述的方法，其特征在于，在所述控制设备向所述会话管理功能实体发送所述第一AS的指示信息之后，还包括：
    所述控制设备接收来自所述会话管理功能实体的第七消息，所述第七消息用于指示将所述终端从第二AS切换至所述第一AS，其中，所述第二AS为当前为所述终端服务的AS；
    所述控制设备根据所述第七消息，将所述终端从第二AS切换至所述第一AS。
  19. 根据权利要求16-18任一项所述的方法，其特征在于，所述控制设备包括车与外界的通信V2X控制功能实体。
  20. 一种会话管理功能实体，其特征在于，所述会话管理功能实体包括：选择模块、发送模块和接收模块；
    所述选择模块，用于选择目的用户面功能实体为终端服务；
    所述发送模块，用于向控制设备发送第一消息；
    所述接收模块，用于接收来自所述控制设备的第一应用服务器AS的指示信息；
    所述发送模块，还用于根据所述第一AS的指示信息，向所述目的用户面功能实体发送第一路由规则，所述第一路由规则包括：将目的地址为所述第一AS的地址的数据发送给所述第一AS。
  21. 根据权利要求20所述的会话管理功能实体，其特征在于，所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之后，向所述目的用户面功能实体发送第一路由规则之前，向所述目的用户面功能实体发送第二路由规则，所述第二路由规则包括：将目的地址为第二AS的地址的数据发送给源用户面功能实体，其中，所述第二AS为当前为所述终端服务的AS，所述源用户面功能实体为与所述第二AS通信连接的用户面功能实体。
  22. 根据权利要求20或21所述的会话管理功能实体，其特征在于，所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之后，向所述目的用户面功能实体发送第一路径信息；
    以及，所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之后，向所述源用户面功能实体发送第二路径信息，其中，所述第一路径信息和所述第二路径信息用于建立所述目的用户面功能实体和所述源用户面功能实体之间的转发路径。
  23. 根据权利要求20-22任一项所述的会话管理功能实体，其特征在于，所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之后，向所述目的用户面功能实体发送第三路由规则，所述第三路由规则包括：将目的地址为第一数据网络的地址的数据发送给远端用户面功能实体，其中，所述远端用户面功能实体为与所述第一数据网络通信连接的用户面功能实体。
  24. 根据权利要求23所述的会话管理功能实体，其特征在于，所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之后，向所述目的用户面功能实体发送第三路径信息；
    所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之后，向所述远端用户面功能实体发送第四路径信息，其中，所述第三路径信息和所述第四路径信息用于建立所述目的用户面功能实体和所述远端用户面功能实体之间的转发路径。
  25. 根据权利要求21所述的会话管理功能实体，其特征在于，所述发送模块，还用于在向所述目的用户面功能实体发送第一路由规则之后，向所述目的用户面功能实体发送第二消息，所述第二消息用于请求删除所述第二路由规则。
  26. 根据权利要求22所述的会话管理功能实体，其特征在于，所述发送模块，还用于在向所述目的用户面功能实体发送第一路由规则之后，向所述目的用户面功能实体发送第三消息，所述第三消息用于请求删除所述第一路径信息。
  27. 根据权利要求22或26所述的会话管理功能实体，其特征在于，所述发送模块，还用于在向所述目的用户面功能实体发送第一路由规则之后，向所述源用户面功能实体发送第四消息，所述第四消息用于请求删除所述源用户面功能实体中所述终端对应的用户面信息，所述用户面信息包括所述第二路径信息。
  28. 根据权利要求20所述的会话管理功能实体，其特征在于，所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之前，向目的基站发送第五路径信息；
    以及，所述发送模块，还用于在所述选择模块选择目的用户面功能实体为所述终端服务之前，向源用户面功能实体发送第六路径信息，其中，所述五路径信息和所述第六路径信息用于建立所述目的基站和所述源用户面功能实体之间的转发路径，所述源用户面功能实体为当前与所述终端建立第一分组数据单元PDU会话的用户面功能实体，所述目的基站为当前与所述目的用户面功能实体通信连接的基站。
  29. 根据权利要求28所述的会话管理功能实体，其特征在于，所述选择模块具体用于：
    向所述终端发送第五消息，所述第五消息用于请求建立第二PDU会话；
    在建立所述第二PDU会话的过程中，选择所述目的用户面功能实体为所述终端服务。
  30. 根据权利要求29所述的会话管理功能实体，其特征在于，所述发送模块，用于在向所述目的用户面功能实体发送第一路由规则之后，向所述终端发送第六消息，所述第六消息用于请求释放所述第一PDU会话。
  31. 根据权利要求20-30任一项所述的会话管理功能实体，其特征在于，所述发送模块，还用于在向所述目的用户面功能实体发送第一路由规则之后，向所述控制设备发送第七消息，所述第七消息用于请求将所述终端从第二AS切换至所述第一AS，其中，所述第二AS为当前为所述终端服务的AS。
  32. 根据权利要求31所述的会话管理功能实体，其特征在于，所述接收模块，还用于在所述发送模块向所述控制设备发送第七消息之后，接收来自所述控制设备的第八消息，所述第八消息用于指示所述终端已经从所述第二AS切换至所述第一AS。
  33. 一种控制设备，其特征在于，所述控制设备包括：接收模块和发送模块；
    所述接收模块，用于接收来自会话管理功能实体的第一消息；
    所述发送模块，用于向所述会话管理功能实体发送第一应用服务器AS的指示信息，所述第一AS的指示信息用于指示所述会话管理功能实体向所述目的用户面功能实体发送第一路由规则，所述第一路由规则包括：将目的地址为所述第一AS的地址的数据发送给 所述第一AS。
  34. 根据权利要求33所述的控制设备，其特征在于，所述控制设备还包括切换模块；
    所述接收模块，还用于在所述发送模块向所述会话管理功能实体发送所述第一AS的指示信息之后，接收来自所述会话管理功能实体的第七消息，所述第七消息用于指示将所述终端从第二AS切换至所述第一AS，其中，所述第二AS为当前为所述终端服务的AS；
    所述切换模块，用于根据所述第七消息，将所述终端从第二AS切换至所述第一AS。
  35. 一种会话管理功能实体，其特征在于，包括：处理器、存储器、总线和通信接口；
    所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述会话管理功能实体运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述会话管理功能实体执行如权利要求1-15中任意一项所述的实现业务连续性的方法。
  36. 一种控制设备，其特征在于，包括：处理器、存储器、总线和通信接口；
    所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述控制设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述控制设备执行如权利要求16-19中任意一项所述的实现业务连续性的方法。
  37. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得所述计算机执行如权利要求1-15中任意一项所述的实现业务连续性的方法。
  38. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得所述计算机执行如权利要求16-19中任意一项所述的实现业务连续性的方法。
  39. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行如权利要求1-15中任意一项所述的实现业务连续性的方法。
  40. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行如权利要求16-19中任意一项所述的实现业务连续性的方法。
  41. 一种实现业务连续性的方法，其特征在于，所述方法包括：
    会话管理功能实体选择目的用户面功能实体为终端服务；
    所述会话管理功能实体向控制设备发送第一消息，所述控制设备接收来自所述会话管理功能实体的所述第一消息；
    所述控制设备向所述会话管理功能实体发送第一应用服务器AS的指示信息，所述会话管理功能实体接收来自所述控制设备的所述第一AS的指示信息；
    所述会话管理功能实体根据所述第一AS的指示信息，向所述目的用户面功能实体发送第一路由规则，所述第一路由规则包括：将目的地址为所述第一AS的地址的数据发送给所述第一AS。
  42. 一种实现业务连续性的系统，其特征在于，所述系统包括如权利要求20-32任一项所述的会话管理功能实体、以及如权利要求33或34所述的控制设备；
    或者，所述系统包括如权利要求35所述的会话管理功能实体、以及如权利要求36所述的控制设备；
    或者，所述系统包括如权利要求37所述的计算机可读存储介质、以及如权利要求38所述的计算机可读存储介质；
    或者，所述系统包括如权利要求39所述的包含指令的计算机程序产品、以及如权利要求40所述的包含指令的计算机程序产品。
PCT/CN2017/089859 2017-06-23 2017-06-23 实现业务连续性的方法、设备及系统 Ceased WO2018232759A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
EP17914804.4A EP3637926B1 (en) 2017-06-23 2017-06-23 Method, device and system for realizing service continuity
BR112019027767-6A BR112019027767A2 (pt) 2017-06-23 2017-06-23 método de implementação de continuidade de serviço, dispositivo, e sistema de implementação de continuidade de serviço
PCT/CN2017/089859 WO2018232759A1 (zh) 2017-06-23 2017-06-23 实现业务连续性的方法、设备及系统
KR1020197038993A KR102364802B1 (ko) 2017-06-23 2017-06-23 서비스 연속성 구현 방법, 장치 및 서비스 연속성 구현 시스템
CN201780091279.0A CN110679192B (zh) 2017-06-23 2017-06-23 实现业务连续性的方法、设备及系统
CN202110430101.2A CN113286376A (zh) 2017-06-23 2017-06-23 实现业务连续性的方法、设备及系统
EP21200831.2A EP4002921B1 (en) 2017-06-23 2017-06-23 Service continuity implementation method, device, and service continuity implementation system
JP2019570991A JP6961730B2 (ja) 2017-06-23 2017-06-23 サービス継続性実現方法、デバイス、およびサービス継続性実現システム
US16/716,049 US11115876B2 (en) 2017-06-23 2019-12-16 Service continuity implementation method, device, and service continuity implementation system
US17/397,056 US11871283B2 (en) 2017-06-23 2021-08-09 Service continuity implementation method, device, and service continuity implementation system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/089859 WO2018232759A1 (zh) 2017-06-23 2017-06-23 实现业务连续性的方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/716,049 Continuation US11115876B2 (en) 2017-06-23 2019-12-16 Service continuity implementation method, device, and service continuity implementation system

Publications (1)

Publication Number Publication Date
WO2018232759A1 true WO2018232759A1 (zh) 2018-12-27

Family

ID=64737529

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/089859 Ceased WO2018232759A1 (zh) 2017-06-23 2017-06-23 实现业务连续性的方法、设备及系统

Country Status (7)

Country Link
US (2) US11115876B2 (zh)
EP (2) EP3637926B1 (zh)
JP (1) JP6961730B2 (zh)
KR (1) KR102364802B1 (zh)
CN (2) CN113286376A (zh)
BR (1) BR112019027767A2 (zh)
WO (1) WO2018232759A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475290A (zh) * 2019-07-23 2019-11-19 中国联合网络通信集团有限公司 一种会话切换方法及装置
CN112714413A (zh) * 2019-10-25 2021-04-27 中国移动通信有限公司研究院 车联网业务处理方法、设备及存储介质
WO2021089034A1 (en) 2019-11-07 2021-05-14 Huawei Technologies Co., Ltd. Systems and methods for user plane handling
CN113676962A (zh) * 2020-05-14 2021-11-19 中国移动通信有限公司研究院 切换处理方法、通信设备、目标基站、源基站及终端
JP2022517176A (ja) * 2019-01-15 2022-03-07 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ローカルエリアネットワーク（ｌａｎ）をサポートする方法および装置
JP2022521538A (ja) * 2019-02-22 2022-04-08 華為技術有限公司 データ伝送方法、装置、及びコンピュータ記憶媒体
EP4044666A4 (en) * 2019-11-08 2022-10-19 Huawei Technologies Co., Ltd. Traffic flow routing method, device, and system

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112019027767A2 (pt) * 2017-06-23 2020-07-07 Huawei Technologies Co., Ltd. método de implementação de continuidade de serviço, dispositivo, e sistema de implementação de continuidade de serviço
US11871291B2 (en) * 2017-08-04 2024-01-09 Apple Inc. Data forwarding tunnel establishment between two user plane functions in fifth generation
CN109981316B (zh) * 2017-12-27 2022-11-25 华为技术有限公司 应用服务器的切换方法及会话管理网元、终端设备
US11122477B2 (en) * 2018-02-26 2021-09-14 Qualcomm Incorporated User plane function (UPF) duplication based make before break handover
US11224093B2 (en) * 2018-08-13 2022-01-11 Ofinno, Llc Network initiated UPF sessions transfer
US11611927B2 (en) * 2019-11-26 2023-03-21 T-Mobile Usa, Inc. Selection of user plane functions and handover of subscriber sessions
CN113473446B (zh) * 2020-03-31 2022-08-30 中国电信股份有限公司 用户面改变方法、系统和移动边缘计算网元
CN111586114B (zh) * 2020-04-24 2025-07-25 腾讯科技（深圳）有限公司 业务协同处理方法及相关设备
CN115699884A (zh) * 2020-05-29 2023-02-03 华为技术有限公司 用于改进通信系统中客户端设备移动性分析的网络节点
CN112788594B (zh) * 2020-06-03 2023-06-27 中兴通讯股份有限公司 数据传输方法、装置和系统、电子设备、存储介质
CN114039945B (zh) * 2020-07-21 2023-03-28 中国移动通信有限公司研究院 用户ip地址分配管理方法、装置及会话管理功能实体
CN113973076B (zh) * 2020-07-24 2023-01-06 华为技术有限公司 一种多播切换方法及装置
CN114079674B (zh) * 2020-08-10 2023-02-21 大唐移动通信设备有限公司 一种数据处理方法、用户面功能及装置
US12114202B2 (en) 2020-08-27 2024-10-08 Samsung Electronics Co., Ltd. Method and apparatus of supervised learning approach for reducing latency during context switchover in 5G MEC
US11368881B1 (en) * 2020-12-15 2022-06-21 Sprint Communications Company L.P. Wireless communication network handovers of wireless user equipment that execute low-latency applications
US11418600B1 (en) * 2020-12-15 2022-08-16 Cisco Technology, Inc. Session and service/flow continuity
CN112752301B (zh) * 2020-12-31 2022-10-14 网络通信与安全紫金山实验室 切换多运营场景的方法及系统、通信设备
CN114885384A (zh) * 2021-02-05 2022-08-09 维沃移动通信有限公司 数据转发方法、装置及通信设备
CN115515187B (zh) * 2021-06-21 2024-12-20 中国电信股份有限公司 用于实现分流的方法、smf实体和通信系统
CN114554615B (zh) * 2021-12-29 2025-06-13 中国电信股份有限公司 一种业务切换方法、装置及网络设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106331200A (zh) * 2015-06-30 2017-01-11 华为技术有限公司 一种节点间数据传输的方法、网关节点及节点
CN106488504A (zh) * 2015-08-28 2017-03-08 华为技术有限公司 网络系统和网络通信的方法
WO2017045643A1 (en) * 2015-09-18 2017-03-23 Huawei Technologies Co., Ltd. System and methods for reliable communication with mobility along a predictable route

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8861426B2 (en) 2010-04-16 2014-10-14 Panasonic Intellectual Property Corporation Of America Path switching system, path switching method, and mobile terminal
EP2873218B1 (en) * 2012-07-10 2019-04-10 Telefonaktiebolaget LM Ericsson (publ) Application service platform with access to context data of remote access node
US10064120B2 (en) * 2015-06-16 2018-08-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and nodes for handling a UE which roams into a visited network
WO2018079691A1 (ja) * 2016-10-26 2018-05-03 日本電気株式会社 通信システム、セキュリティ装置、通信端末、及び通信方法
WO2018111030A1 (ko) * 2016-12-15 2018-06-21 엘지전자(주) 무선 통신 시스템에서 핸드오버 수행 방법 및 이를 위한 장치
US11228949B2 (en) * 2017-01-06 2022-01-18 Samsung Electronics Co., Ltd. Intra-RAT handover for next generation system
CN108632953A (zh) * 2017-02-10 2018-10-09 中兴通讯股份有限公司 一种实现多接入管理的方法及装置
KR102247424B1 (ko) * 2017-03-31 2021-05-04 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Nr 및 5gc에서의 애플리케이션 토폴로지 인식형 사용자 평면 선택
CN117596640A (zh) * 2017-05-05 2024-02-23 北京三星通信技术研究有限公司 一种支持切换的方法
CN108811016B (zh) * 2017-05-05 2022-02-25 北京三星通信技术研究有限公司 一种支持切换的方法
BR112019027767A2 (pt) * 2017-06-23 2020-07-07 Huawei Technologies Co., Ltd. método de implementação de continuidade de serviço, dispositivo, e sistema de implementação de continuidade de serviço

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106331200A (zh) * 2015-06-30 2017-01-11 华为技术有限公司 一种节点间数据传输的方法、网关节点及节点
CN106488504A (zh) * 2015-08-28 2017-03-08 华为技术有限公司 网络系统和网络通信的方法
WO2017045643A1 (en) * 2015-09-18 2017-03-23 Huawei Technologies Co., Ltd. System and methods for reliable communication with mobility along a predictable route

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NOKIA: "TS 23.502: Handover procedure correction for UPF relocation", SA WG2 MEETING # 121, no. S2-173155, 9 May 2017 (2017-05-09), Hangzhou, China, XP051268622 *
SAMSUNG: "23.502: Update of handover without Xn interface", SA WG2 MEETING # 121, no. S2-173265, 9 May 2017 (2017-05-09), Hangzhou, China, XP051268720 *
See also references of EP3637926A4 *

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022517176A (ja) * 2019-01-15 2022-03-07 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ローカルエリアネットワーク（ｌａｎ）をサポートする方法および装置
JP7603098B2 (ja) 2019-01-15 2024-12-19 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ローカルエリアネットワーク（ｌａｎ）をサポートする方法および装置
JP2023109789A (ja) * 2019-01-15 2023-08-08 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ローカルエリアネットワーク（ｌａｎ）をサポートする方法および装置
JP7274582B2 (ja) 2019-01-15 2023-05-16 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ローカルエリアネットワーク（ｌａｎ）をサポートする方法および装置
JP7266695B2 (ja) 2019-02-22 2023-04-28 華為技術有限公司 データ伝送方法、装置、及びコンピュータ記憶媒体
JP2022521538A (ja) * 2019-02-22 2022-04-08 華為技術有限公司 データ伝送方法、装置、及びコンピュータ記憶媒体
US12052646B2 (en) 2019-02-22 2024-07-30 Huawei Technologies Co., Ltd. Data transmission method, apparatus, and computer storage medium
CN110475290B (zh) * 2019-07-23 2023-04-28 中国联合网络通信集团有限公司 一种会话切换方法及装置
CN110475290A (zh) * 2019-07-23 2019-11-19 中国联合网络通信集团有限公司 一种会话切换方法及装置
CN112714413A (zh) * 2019-10-25 2021-04-27 中国移动通信有限公司研究院 车联网业务处理方法、设备及存储介质
WO2021089034A1 (en) 2019-11-07 2021-05-14 Huawei Technologies Co., Ltd. Systems and methods for user plane handling
US11871273B2 (en) 2019-11-07 2024-01-09 Huawei Technologies Co., Ltd. Systems and methods for user plane handling
EP4044666A4 (en) * 2019-11-08 2022-10-19 Huawei Technologies Co., Ltd. Traffic flow routing method, device, and system
US11963032B2 (en) 2019-11-08 2024-04-16 Huawei Technologies Co., Ltd. Traffic routing method, apparatus, and system
US12356239B2 (en) 2019-11-08 2025-07-08 Huawei Technologies Co., Ltd. Traffic routing method, apparatus, and system
CN113676962A (zh) * 2020-05-14 2021-11-19 中国移动通信有限公司研究院 切换处理方法、通信设备、目标基站、源基站及终端
CN113676962B (zh) * 2020-05-14 2023-08-15 中国移动通信有限公司研究院 切换处理方法、通信设备、目标基站、源基站及终端

Also Published As

Publication number Publication date
JP2020524955A (ja) 2020-08-20
US20200120549A1 (en) 2020-04-16
BR112019027767A2 (pt) 2020-07-07
EP4002921C0 (en) 2025-02-19
US11871283B2 (en) 2024-01-09
CN113286376A (zh) 2021-08-20
JP6961730B2 (ja) 2021-11-05
CN110679192A (zh) 2020-01-10
KR102364802B1 (ko) 2022-02-17
EP3637926A4 (en) 2020-04-22
US11115876B2 (en) 2021-09-07
KR20200012980A (ko) 2020-02-05
EP3637926B1 (en) 2022-04-13
CN110679192B (zh) 2021-05-11
EP4002921A1 (en) 2022-05-25
EP4002921B1 (en) 2025-02-19
EP3637926A1 (en) 2020-04-15
US20210368397A1 (en) 2021-11-25

Similar Documents

Publication Publication Date Title
CN110679192B (zh) 实现业务连续性的方法、设备及系统
CN109842639B (zh) 实现切换过程中业务连续性的方法、设备及系统
CN110167003B (zh) 会话管理方法、设备及系统
JP7516448B2 (ja) 通信方法及び通信装置
CN109275160B (zh) 数据分流方法、设备及系统
US12004264B2 (en) Session management method, device, and system
CN109792663B (zh) 使用隧道协议服务移动通信设备的方法和装置
JP2019518398A (ja) セッション管理機能エンティティ選択方法、機器、及びシステム
WO2019085753A1 (zh) 会话建立方法、设备及系统
CN110392448B (zh) 一种会话重建方法、装置和系统
CN111586114A (zh) 业务协同处理方法及相关设备
WO2017133231A1 (zh) 一种传输路径的切换方法、终端和系统
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
EP4297352A1 (en) Data transmission method and apparatus
WO2022022014A1 (zh) QoS流控制方法及通信装置
JP2021524204A (ja) サービス品質監視方法、及びシステム、並びに装置
CN116420393A (zh) 标识发送方法和通信装置
WO2021159238A1 (zh) 一种数据处理方法、通信装置和通信系统
WO2020011173A1 (zh) 搬迁管理方法及装置
CN112449367A (zh) 一种数据传输方法和核心网设备
WO2023071866A1 (zh) 指示信息的传输方法、消息传输方法及相关装置
WO2021190513A1 (zh) 一种数据传输方法、装置及系统
CN117676730A (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: 17914804

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019570991

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197038993

Country of ref document: KR

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019027767

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2017914804

Country of ref document: EP

Effective date: 20200107

ENP Entry into the national phase

Ref document number: 112019027767

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20191223

WWG Wipo information: grant in national office

Ref document number: 201937052971

Country of ref document: IN