WO2018166336A1 - 一种发起用户面路径重建的方法、装置及通信系统 - Google Patents

一种发起用户面路径重建的方法、装置及通信系统 Download PDF

Info

Publication number
WO2018166336A1
WO2018166336A1 PCT/CN2018/077025 CN2018077025W WO2018166336A1 WO 2018166336 A1 WO2018166336 A1 WO 2018166336A1 CN 2018077025 W CN2018077025 W CN 2018077025W WO 2018166336 A1 WO2018166336 A1 WO 2018166336A1
Authority
WO
WIPO (PCT)
Prior art keywords
function entity
session
terminal device
user plane
service area
Prior art date
Application number
PCT/CN2018/077025
Other languages
English (en)
French (fr)
Inventor
朱奋勤
孙德奎
吴问付
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020197016274A priority Critical patent/KR102231693B1/ko
Priority to BR112019014020-4A priority patent/BR112019014020A2/pt
Priority to JP2019532789A priority patent/JP6987866B2/ja
Priority to EP21192955.9A priority patent/EP3979707B1/en
Priority to EP18767026.0A priority patent/EP3598800B1/en
Publication of WO2018166336A1 publication Critical patent/WO2018166336A1/zh
Priority to US16/415,148 priority patent/US11224085B2/en
Priority to US17/538,734 priority patent/US11805567B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • 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
    • 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/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/249—Reselection being triggered by specific parameters according to timing information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a communication system for initiating user plane path reconstruction.
  • AMF Core Access and Mobility Management Function
  • SMF Session Management Function
  • the AMF is responsible for the mobility management of the terminal device, including the development of a Tracking Area List (TA List).
  • TA List Tracking Area List
  • the SMF is responsible for session management, including the selection of User Plane Function (UPF) and the establishment of a Packet Data Unit (PDU) session.
  • UPF User Plane Function
  • PDU Packet Data Unit
  • the UPF can be divided into an N3 UPF and a PDU session anchor UPF (PSA, PDU Session Anchor) according to the functions it is responsible for, wherein the N3 UPF and the Radio Access Network (RAN) ) Connected through the N3 interface, the PSA and the data network are connected through the N6 interface.
  • PDU session anchor UPF PSA, PDU Session Anchor
  • RAN Radio Access Network
  • Each of the UPFs has a certain service range.
  • the service range of the N3 UPF refers to the sum of the service ranges of the RANs connected to the N3 UPF.
  • the terminal device When the terminal device establishes a user plane path with the N3 UPF and the PSA, Generally, when the location of the terminal device is within the service range of the N3 UPF and the optimal service area of the PSA, the N3 UPF and the PSA can provide better services for the terminal.
  • the terminal device is another mobile terminal device such as a mobile phone
  • the location of the terminal device is not fixed, and compared with the fourth generation mobile communication technology (4-Generation, 4G)
  • the deployment position of the UPF is flexible in the 5G, UPF
  • the service scope will also change greatly with the change of the deployment location, and the mobility management and session management are split into two entities. Therefore, in order to provide better service for data communication of the terminal device, it is necessary to reconstruct the user plane. Path, but the mechanism for initiating user plane path reconstruction is not explicitly activated in the existing 5G standard. To this end, the embodiment of the present application provides a method for initiating user plane path reconstruction.
  • the present application provides a method, apparatus, and communication system for initiating user plane path reconstruction, which are used to provide better services for a session of a terminal device to improve user experience.
  • the method for initiating user plane path reconstruction in the embodiment of the present application includes:
  • the session management function entity determines, according to the first location information of the terminal device, the session service area to which the current session of the terminal device belongs, and after receiving the second location information of the terminal device sent by the mobility management function entity, Determining that the second location information is not in the session service area, instructing the terminal device to initiate a re-establishment process for the current session, or initiating a handover procedure, where the handover procedure is used to serve the current session.
  • the user plane function entity switches to the target user plane function entity, and the target user plane function entity is configured to provide a service for the session of the terminal device after completing the handover procedure.
  • the first location information is the terminal device that is received by the session management function entity in the process of establishing the current session or in the process of switching the first user plane function entity to the second user plane function entity.
  • Location information the first user plane function entity is configured to provide a service for the session of the terminal device before switching to the second user plane function entity, where the second user plane function entity is used for the current location Session delivery service.
  • the current session establishment process includes: a process of initially creating a current session, and a process of reestablishing a session to a current session.
  • the session service area is introduced, when the terminal device moves back and forth at the edge of the service area of two adjacent user plane function entities, the ping-pong effect caused by switching back and forth between the two user plane function entities is avoided, thereby Improve the user experience.
  • the session service area includes a service area of a user plane function entity that provides service for the current session.
  • the session management function entity receives the mobile After the second location information of the terminal device sent by the sex management function entity, determining that the second location information is not in the session service area and determining that the second location information is not in the user plane serving the current session
  • the terminal device is instructed to initiate a re-establishment process for the current session or initiate the handover process.
  • the session management function entity determines a center location of the session service area centering on first location information of the terminal device; and determining the session service area size.
  • the session management function entity determines the size of the session service area based on the following manner:
  • the session management function entity Determining, by the session management function entity, a size of the session service area according to a service area of a user plane function entity serving the current session and/or a mobility mode of the terminal device; wherein the mobility mode includes the At least one of a moving range of the terminal device, a moving speed of the terminal device, and a moving trajectory of the terminal device.
  • the session management function entity determines the session service area, determining, according to the session service area, a location reporting granularity of the terminal device, where the location reporting granularity And a range for indicating that the mobility management function entity reports the location information of the terminal device to the session management function entity; and sends the location report granularity to the mobility management function entity.
  • the mobility management function entity Since the mobility management function entity reduces the signaling amount of reporting the location information of the terminal device to the session management function entity by the location reporting granularity, it is not necessary to give each session function entity each time the mobility management function receives the location information of the terminal. Report the location information of the terminal device.
  • the session management function entity acquires at least one location reporting requirement, where the at least one location reporting requirement includes at least one area information, where the at least one area information is used to indicate The range of the location information is required to be reported by the terminal device; the location reporting granularity is determined according to the session service area and the at least one area information, where the location reporting granularity is the intersection of the session service area and the at least one area information.
  • the apparatus for initiating a user plane path reconstruction of the embodiment of the present application includes one or more modules that can implement the first aspect or any one of the foregoing first aspects, each module may perform one or more step.
  • the embodiment of the present application further provides a session management function device, where the session management function device includes a processor, a memory, and a communication interface, where the communication interface is used to receive and send information, and the memory is used to store a software program. And the data information or the like received or transmitted, the processor is configured to read the software program and data stored in the memory and implement the method provided by the first aspect or any one of the foregoing first aspects.
  • the embodiment of the present application further provides a computer storage medium, which may be non-volatile, that is, the content is not lost after power off.
  • the storage medium stores a software program that, when read and executed by one or more processors, implements the method provided by the first aspect or 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, causing a computer to perform the method provided by the above first aspect and any one of the foregoing first aspects.
  • the embodiment of the present application further provides a communication system, including: a session management function entity and a mobility management function entity; wherein the session management function entity is configured to determine a current location of the terminal device according to the first location information of the terminal device.
  • the session service area to which the session belongs and after receiving the second location information of the terminal device sent by the mobility management function entity, if it is determined that the second location information is not in the session service area, the terminal device is instructed to initiate a re-establishment process for the current session.
  • the handover process is used to switch the user plane function entity serving the current session to the target user plane function entity, and the target user plane function entity is configured to provide a service for the terminal device session after completing the handover process;
  • the first location information is location information of the terminal device that is received by the session management function entity during the current session establishment process or in the process of switching the first user plane function entity to the second user plane function entity, and the first user plane function entity Used to end before switching to the second user plane functional entity Session with the device to provide services, the second user plane entity for providing a service function for the current session; a mobility management entity, a second transmitting terminal device location information to the session management function entity.
  • the session management function entity is further configured to: after determining the session service area, determine a location reporting granularity of the terminal device according to the session service area, and send the location to the mobility management function entity.
  • the reporting granularity, the location reporting granularity is used to indicate that the mobility management function entity reports the range information of the terminal device to the session management function entity; the mobility management function entity is further configured to send the second location information of the terminal device to the session management function entity.
  • the receiving location reports the granularity, and determines that the second location information of the terminal device is not within the location reporting granularity.
  • session management function entity in the communication system provided in the sixth aspect may perform the method provided by the first aspect of the embodiment of the present application and any one of the implementation manners of the first aspect.
  • the method for initiating user plane path reconstruction in the embodiment of the present application includes:
  • the session management function entity receives the first location information of the terminal device sent by the mobility management function entity; if it is determined that the first location information is not in the first service area, selecting the first target user according to the first location information Dedicating a functional entity and initiating a re-establishment process for the user plane path of the current session, the first target user plane function entity serving a session of the terminal device in the reconstructed user plane path.
  • the first service area is a service area of the first user plane function entity, and the first user plane function entity is used to provide a service for the current session of the terminal device.
  • the first location information is included in the service area of the first target user plane functional entity.
  • the terminal device can reconstruct the user plane path to the first target user plane function entity after moving out of the first service area, the activation of the user initiates the user plane path reconstruction mechanism, so that the network can provide better terminal equipment.
  • the service thus enhances the user experience.
  • the session management function entity before the session management function entity receives the first location information of the terminal device sent by the mobility management function entity, determining, according to the first service region, a location reporting granularity of the terminal device, where the location reporting granularity is used to indicate that the mobility management function entity reports a range of location information of the terminal device to the session management function entity; and to the mobility management The entity sends the location report granularity.
  • the mobility management function entity Since the mobility management function entity reduces the signaling amount of reporting the location information of the terminal device to the session management function entity by the location reporting granularity, it is not necessary to give each session function entity each time the mobility management function receives the location information of the terminal. Report the location information of the terminal device.
  • the session management function entity determines, according to the second location information of the terminal device, the session service area to which the current session belongs, according to the first service area and the The session service area is configured to determine a location reporting granularity of the terminal device, where the location reporting granularity is not greater than an intersection area of the first service area and the session service area.
  • the second location information is received by the session management function entity during a session establishment process of the current terminal device, or in a process of switching a second user plane function entity to a third user plane function entity.
  • the location information of the terminal device, where the second user plane function entity is configured to provide a service for the session of the terminal device before switching to the third user plane function entity, where the third user plane function entity is used to Providing a service to the current session;
  • the session management function entity acquires at least one location reporting requirement, where the at least one location reporting requirement includes at least one area information, where the at least one area information is used to indicate And determining, by the terminal device, the range of the location information, and determining, according to the first service area and the at least one area information, the location reporting granularity, where the location reporting granularity is the first serving area and the The intersection of at least one regional information.
  • the session management function entity initiates the re-establishment of the user plane path for the current session, if it is determined that the first user plane function entity has cached data, And creating a forwarding tunnel, where the forwarding tunnel is a tunnel between the first target user plane function entity and the first user plane function entity, so that the first user plane function entity performs the The cached data is sent to the first target user plane functional entity.
  • the session management function entity creates the forwarding tunnel
  • the forwarding is deleted.
  • the session management function entity starts a forwarding timer, and deletes the forwarding tunnel after the forwarding timer reaches a preset duration.
  • the apparatus for initiating user plane path reconstruction in the embodiment of the present application includes one or more modules that can implement any one of the fifth aspect or the foregoing fifth aspect, each module may perform one or more step.
  • the embodiment of the present application further provides a session management function device, where the session management function device includes a processor, a memory, and a communication interface, where the communication interface is used to receive and send information, and the memory is used to store a software program. And the data information or the like received or transmitted, the processor is configured to read the software program and data stored in the memory and implement the method provided by the seventh aspect or any one of the foregoing seventh aspects.
  • the embodiment of the present application further provides a computer storage medium, which may be non-volatile, that is, the content is not lost after power off.
  • the storage medium stores a software program that, when read and executed by one or more processors, implements the method of any one of the seventh aspect or the seventh aspect described above.
  • the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing a computer to perform the method provided by the foregoing seventh aspect and any one of the foregoing tenth aspects.
  • the eleventh aspect provides a communication system, including a session management function entity and a mobility management function entity, where the mobility management function entity is configured to send first location information of the terminal device to the session management function entity;
  • the session management function entity is configured to: after receiving the first location information of the terminal device sent by the mobility management function entity, if it is determined that the first location information is not in the first service area, select the first target user according to the first location information The functional entity and initiate a reconstruction process for the user plane path of the current session;
  • the first service area is a service area of the first user plane function entity, and the first user plane function entity is used to provide a service for the current session of the terminal device, where the first target user plane function entity is in the reconstructed user plane path.
  • the session of the terminal device provides services.
  • the session management function entity is further configured to determine a location reporting granularity of the terminal device according to the first service area, and send a location reporting granularity to the mobility management function entity;
  • the reporting granularity is used to indicate that the mobility management function entity reports the range information of the location information of the terminal device to the session management function entity;
  • the mobility management function entity is further configured to receive the location before sending the first location information of the terminal device to the session management function entity.
  • the granularity is reported, and it is determined that the first location information of the terminal device is not within the location reporting granularity.
  • session management function entity in the communication system provided in the eleventh aspect may perform the method provided by any one of the seventh aspect and the seventh aspect of the embodiments of the present application.
  • a method for reporting location information including:
  • the mobility management function entity receives the location reporting granularity for the current session of the terminal device; when determining that the location information of the terminal device is not within the granularity of the location, the location information of the terminal device is sent to the session management function entity, and if the terminal device is determined When the location information is reported in the granularity, the location information of the terminal device is not sent to the session management function entity.
  • the mobility management function entity Since the mobility management function entity reduces the signaling amount of reporting the location information of the terminal device to the session management function entity by the location reporting granularity, it is not necessary to give each session function entity each time the mobility management function receives the location information of the terminal. Report the location information of the terminal device.
  • the apparatus for reporting location information in the embodiment of the present application includes one or more modules that can implement the twelfth aspect or any one of the foregoing twelfth aspects, each module can execute one or more modules. Steps.
  • the embodiment of the present application further provides a mobility management function device, where the mobility management function device includes a processor, a memory, and a communication interface, where the communication interface is used to receive and send information, where the memory is used to And storing the software program and the received or transmitted data information, etc., the processor for reading the software program and data stored in the memory and implementing the method provided by the ninth aspect or any one of the foregoing ninth aspects.
  • the mobility management function device includes a processor, a memory, and a communication interface, where the communication interface is used to receive and send information, where the memory is used to And storing the software program and the received or transmitted data information, etc., the processor for reading the software program and data stored in the memory and implementing the method provided by the ninth aspect or any one of the foregoing ninth aspects.
  • the embodiment of the present application further provides a computer storage medium, which may be non-volatile, that is, the content is not lost after power off.
  • the storage medium stores a software program that, when read and executed by one or more processors, implements the method of the ninth aspect or any one of the foregoing ninth aspects.
  • an embodiment of the present application further provides a computer program product comprising instructions, which when executed on a computer, cause the computer to perform the method described in the above aspects.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIGS. 2a and 2b are schematic flowcharts of initiating user plane path reconstruction according to an embodiment of the present application
  • 3a and 3b are respectively schematic diagrams showing the relationship between a session service area and a service area of a user plane function entity serving a current session according to an embodiment of the present application;
  • FIG. 4a and FIG. 4b are respectively schematic flowcharts of a method for initiating user plane path reconstruction according to an embodiment of the present application
  • FIG. 5 is a schematic view for explaining the beneficial effects of the embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for reconstructing a user plane path according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of a specific communication system according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a process of initially creating a PDU session or reestablishing a PDU session according to an embodiment of the present application
  • FIG. 9 is a schematic diagram of a method for user plane path switching in an Xn handover procedure according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of user plane path switching in a registration process according to an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of user plane path switching of a terminal device in a service request according to an embodiment of the present disclosure
  • FIG. 12 is a schematic flowchart of reestablishing a PDU session according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of an apparatus for initiating user plane path reconstruction according to an embodiment of the present application.
  • 13b is a schematic structural diagram of hardware of a session management function device according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of an apparatus for initiating user plane path reconstruction according to an embodiment of the present application.
  • FIG. 14b is a schematic structural diagram of hardware of a session management function device according to an embodiment of the present application.
  • the session management function entity, the mobility management function entity, the user plane function entity, and the like in the embodiment of the present application are only one name, and the name does not limit the device itself.
  • the network element or the entity corresponding to the session management function entity, the mobility management function entity, and the user plane function entity may be other names, which is not specifically limited in this embodiment of the present application.
  • the session management function entity may be a Session Management Function (SMF)
  • the mobility management function entity may be a Core Access and Mobility Management Function (AMF) or a user plane function entity.
  • AMF Core Access and Mobility Management Function
  • UPF User Plane Function
  • the session management function entity, the mobility management function entity, the user plane function entity, and the like in the embodiments of the present application may have other functions in addition to the functions in the embodiments of the present application, which are not specifically limited in this embodiment of the present application.
  • the mobility management function entity may have other functions in addition to the function of sending the location information of the terminal device to the session management function entity, which is not specifically limited in this embodiment of the present application.
  • the session management function entity, the mobility management function entity, the user plane function entity, and the like in the embodiments of the present application may be implemented by one entity device, or may be implemented by multiple entity devices. Specifically limited. That is, the session management function entity, the mobility management function entity, the user plane function entity, and the like in the embodiment of the present application may be a logical function module in the entity device, or may be composed of multiple entity devices. A logical function module is not specifically limited in this embodiment of the present application.
  • the method for initiating user plane path reconstruction in the embodiment of the present application is applicable to the communication system 100 shown in FIG. 1.
  • the communication system 100 includes a session management function entity 110 and a mobility management function entity 120, which should be understood and implemented in the present application.
  • the session for initiating the re-establishment of the user plane may be a Packet Data Unit (PDU) session, a Public Data Network (PDN) session, or other sessions, and is not in this application. Make a limit.
  • PDU Packet Data Unit
  • PDN Public Data Network
  • the PDU session is taken as an example to describe the method for initiating the user plane re-establishment in the embodiment of the present application.
  • the session is a PDN session or other session
  • the method for initiating the user plane re-establishment is similar to the PDU session, and details are not described herein.
  • the method for initiating user plane path reconstruction in the embodiment of the present application includes:
  • step 200a the session management function entity 110 determines the session service area to which the current session of the terminal device belongs according to the first location information of the terminal device.
  • the first location information is location information of the terminal device that is received by the session management function entity 110 during the current session establishment process or in the process of switching the first user plane function entity to the second user plane function entity, the first user.
  • the face function entity is configured to provide a service for the session of the terminal device before switching to the second user plane function entity, and the second user plane function entity is used to provide services for the current session.
  • the current session establishment process in the embodiment of the present application includes: a process of initially creating a current session, and a process of reestablishing a session to a current session.
  • the first location information may be carried in a request message that is sent to the session management function entity to initially create a current session, or a message that separately sends the first location information, or a request message in the process of re-establishing the session to the current session.
  • the path switching request message it is not limited in the embodiment of the present application.
  • step 210a the mobility management function entity 120 sends the second location information of the terminal device to the session management function entity 110, and the session management function entity 110 receives the second location information of the terminal device sent by the mobility management function entity 120.
  • step 220a after receiving the second location information of the terminal device sent by the mobility management function entity 120, the session management function entity 110 determines that the second location information is not in the session service area, and instructs the terminal device to initiate a re-establishment process for the current session. .
  • the process ends, that is, the terminal device is no longer instructed to initiate a re-establishment process for the current session.
  • the session service area may be named as a packet data unit (PDU Session Service Area, PSSA).
  • PDU Session Service Area PSSA
  • the session service area is a logical concept, and the session management function entity 110 can determine the session service area by:
  • the session management function entity 110 determines the center location of the session service area centering on the first location information of the terminal device, and then determines the size of the session service area.
  • the size of the session service area may be determined based on a pre-configured policy, for example, the number of cells included in the session service area, the number of Tracking Areas (TAs), and the like are configured in advance.
  • TAs Tracking Areas
  • the session management function entity 110 can also determine the size of the session service area based on the following:
  • the session management function entity 110 determines the size of the session service area according to the service area of the user plane function entity serving the current session and/or the mobile mode of the terminal device; wherein the mobile mode includes the mobile range of the terminal device and the moving speed of the terminal device. At least one of the movement trajectories of the terminal device.
  • the user plane function entity serving the current session may be an anchor UPF serving the current session, for example, an anchor point UPF that does not move very much and is not located close to the current session.
  • the terminal device at the boundary of the service area may formulate the session service area as the service area of the anchor UPF serving the current session; for the service area boundary of the anchor point UPF that does not move very much and is close to serve the current session.
  • the terminal device can set the session service area to be relatively small, so that the user plane path can be switched early after the location of the terminal device is relatively stable.
  • the specific mobile device mode can be based on the subscription information or the historical movement track of the terminal device. determine.
  • the session management function entity may also consider other factors when formulating the session service area, so as to be able to provide better services for the terminal device's session.
  • the session service area determined by the session management function entity may include providing the current session as shown in FIG. 3a.
  • the service area of the user plane function entity of the service may also include only the service area of the user plane function entity that partially serves the current session as shown in FIG. 3b.
  • step 220a it is not only determined whether the second location information is in the session service area, but also whether the second location information is determined to be
  • the step of providing a service area of the user plane function entity serving the current session specifically, when the session management function entity 110 determines that the second location information is not in the session service area and is not in the service of the user plane function entity serving the current session In the case of the area, the terminal device is instructed to initiate a re-establishment process for the current session, otherwise the process ends.
  • FIG. 2b another method for initiating user plane path reconstruction according to an embodiment of the present application is provided.
  • the concept of the location reporting granularity of the terminal device is introduced on the basis of the method for initiating the user plane path reconstruction shown in FIG. 2a.
  • the specific method for initiating the user plane path reconstruction includes:
  • step 200a the session management function entity 110 determines the session service area to which the current session of the terminal device belongs according to the first location information of the terminal device.
  • the first location information is location information of the terminal device that is received by the session management function entity 110 during the current session establishment process or in the process of switching the first user plane function entity to the second user plane function entity, the first user.
  • the face function entity is configured to provide a service for the session of the terminal device before switching to the second user plane function entity, and the second user plane function entity is used to provide services for the current session.
  • the current session establishment process in the embodiment of the present application includes: a process of initially creating a current session, and a process of reestablishing a session to a current session.
  • the session management function entity 110 determines the location reporting granularity of the terminal device according to the session service area, and the location reporting granularity is used to indicate that the mobility management function entity 120 reports the range information of the terminal device to the session management function entity 110.
  • step 200c the session management function entity 110 sends a location report granularity to the mobility management function entity 120, and the mobility management function entity 120 receives the location report granularity.
  • step 200d the mobility management function entity 120 determines that the second location information of the terminal device is not within the location reporting granularity, and then performs step 210a.
  • the process ends, that is, the terminal device is not sent to the session management function entity 110. Two location information.
  • step 210a the mobility management function entity 120 sends the second location information of the terminal device to the session management function entity 110.
  • step 220a after receiving the second location information of the terminal device sent by the mobility management function entity 120, the session management function entity 110 determines that the second location information is not in the session service area, and instructs the terminal device to initiate a re-establishment process for the current session. .
  • the process ends, that is, the terminal device is no longer instructed to initiate a re-establishment process for the current session.
  • the location reporting granularity causes the mobility management function entity to reduce the signaling amount of reporting the location information of the terminal device to the session management function entity, without requiring mobility management at each time.
  • the function receives the location information of the terminal, it reports the location information of the terminal device to each session function entity.
  • the session management function entity 110 may determine the location reporting granularity of the terminal device according to the following manner:
  • the first method for determining the granularity of the location reporting the session management function entity acquires at least one location reporting requirement, the at least one location reporting requirement includes at least one area information, and the at least one area information is used to indicate that the terminal device needs to report the range of the location information;
  • the session management function entity determines the location report granularity according to the session service area and the at least one area information, where the location report granularity is an intersection of the session service area and the at least one area information.
  • the session management function entity may need to consider other location reporting requirements when reporting the granularity of the PDU session.
  • the charging requirement also requires the mobility management function entity to report the location information of the terminal device.
  • the session management is performed.
  • the functional entity selects the minimum reporting granularity of these requirements as the location reporting granularity of the PDU session.
  • the area information of the charging requirement is TAI. If the session service area is a set of TAIs, the location reporting function entity has a location reporting granularity of TAI instead of a set of TAIs of the session service area.
  • the session management function entity may separately obtain at least one location reporting requirement for the terminal device from the at least one other network element device, or the session management function entity may report the requirement for the locality according to the needs of the at least one location generated locally.
  • the other network element device refers to a device different from the network element device where the session management function entity is located.
  • the second method for determining the granularity of the location reporting the session management function entity determines that the location reporting requirement is not obtained, and determines the granularity of the location reporting only according to the session service area.
  • the location reporting granularity does not exceed the scope of the session service area.
  • the specific location reporting granularity and the size of the session service area may be determined based on a preset policy.
  • FIG. 4a another method for initiating user plane path reconstruction in the embodiment of the present application is different from the method for initiating user plane path reconstruction as shown in FIG. 2a in that step 220a in FIG. 2a is replaced with steps. 400, the other steps in the method for initiating user plane path reconstruction shown in FIG. 4a are the same as the steps in FIG. 2a. Therefore, the specific implementation manner of the method for initiating user plane path reconstruction shown in FIG. 4a is as shown in FIG. 2a. The specific implementation manner of the method for initiating the user plane path reconstruction is not described here.
  • the embodiment of the present application further provides a method for initiating user plane path reconstruction, and a different step from the method for initiating user plane path reconstruction as shown in FIG. 2b is to replace step 220a in FIG. 2b.
  • a different step from the method for initiating user plane path reconstruction as shown in FIG. 2b is to replace step 220a in FIG. 2b.
  • the other steps in the method of initiating user plane path reconstruction shown in FIG. 4b are the same as the steps in FIG. 2b. Therefore, the specific implementation manner of the method for initiating user plane path reconstruction shown in FIG. 4b is as follows. A specific implementation manner of the method for initiating the user plane path reconstruction shown in FIG. 2b is not described herein again.
  • the session management function entity 110 determines that the second location information is no longer in the session service area, and initiates a handover process, where the handover process is used to switch the user plane function entity serving the current session to the target user plane function entity.
  • the target user plane function entity is used to provide services for the terminal device's session after the handover process is completed.
  • step 200a in the method for initiating user plane path reconstruction shown in FIG. 4a and FIG. 4b when the first location information is in the process of switching the first user plane function entity to the second user plane function entity,
  • the user plane function entity that serves the current session in the handover procedure initiated by the session management function entity 110 in step 400 is the second user plane function entity.
  • the first location information is the location information of the terminal device that is received during the current session establishment process, then the user management function entity 110 initiates the current process in the handover process for the current session. After the session is established, the user plane function entity serving the current session service is served.
  • the user plane function entity may be a PDU session anchor point.
  • the face function entity, and the user plane entity serving the current session are different anchor points UPF in the PDU session anchor UPF.
  • the user plane function entity is the PDU session anchor point UPF
  • the session service area is introduced in the embodiment of the present application
  • the terminal device is in the area 1 and the area 2 as shown in FIG.
  • the edge moves back and forth, the ping-pong effect caused by switching back and forth between the two anchor points UPF is avoided, where area 1 is the service area of one anchor point UPF, and area 2 is the service area of another anchor point UPF.
  • the embodiment of the present application further provides another method for user plane path reconstruction, including:
  • Step 600 The mobility management function entity 120 sends the first location information of the terminal device to the session management function entity, and the session management function entity 110 receives the first location information of the terminal device sent by the mobility management function entity 120.
  • Step 610 After receiving the first location information of the terminal device sent by the mobility management function entity 120, the session management function entity 110 determines that the first location information is not in the first service area, and then performs step 620.
  • the first service area is a service area of the first user plane function entity, and the first user plane function entity is used to provide a service for the current session of the terminal device.
  • step 620 if the session management function entity 110 determines that the first location information is in the first service area, the process ends, that is, step 620 is not performed, and the following steps are performed.
  • Step 620 The session management function entity 110 selects a first target user plane function entity according to the first location information.
  • the first target user plane function entity provides a service for the session of the terminal device in the reconstructed user plane path.
  • step 630 the session management function entity 110 initiates a re-establishment process for the user plane path of the current session.
  • Step 640 After determining that the first user plane function entity has cached data, the session management function entity 110 creates a forwarding tunnel, and the forwarding tunnel is a tunnel between the first target user plane function entity and the first user plane function entity, so that the A user plane functional entity sends the cached data to the first target user plane functional entity through the forwarding tunnel.
  • Step 650 After receiving the identifier of the completed cache data transmission sent by the first user plane function entity, the session management function entity 110 deletes the forwarding tunnel. Alternatively, the session management function entity 110 starts the forwarding timer after forwarding the forwarding tunnel. The forwarding tunnel is deleted when the timer reaches the preset duration.
  • step 640 and step 650 are non-essential steps, that is, only the method for initiating user plane path reconstruction as shown in FIG. 6 can be performed.
  • Step 600 to step 630, step 600 to step 640 may also be performed, and step 600 to step 640 may also be performed, and specific steps may be determined according to actual needs. For example, when there is no cached data in the first user plane function entity, only step 600 to step 630 may be performed.
  • the service-providing user-side functional entity of the session initiates the re-establishment process of the user-side path for the current session of the terminal device of the part, without considering that the session management function entity is the terminal device of the other part of the current session of the plurality of terminal devices The process of rebuilding the user plane path of the current session.
  • the number of messages that need to be reported by the mobility management function entity is reduced by increasing the location reporting granularity.
  • the session management function entity 110 determines the location reporting granularity of the terminal device according to the first service area, and sends the location reporting granularity to the mobility management function entity 120, where the location reporting granularity is used to indicate mobility management.
  • the functional entity 120 reports the range of location information of the terminal device to the session management function entity 110.
  • the mobility management function entity 120 determines whether the first location information of the terminal device is within the granularity of the location of the terminal device, if it is determined that the first location information is in the If the location of the terminal device is reported in the granularity, the process ends. If it is determined that the first location information of the terminal device is not within the location reporting granularity, step 600 is performed.
  • the first implementation manner of determining the location reporting granularity is: the session management function entity may determine the location reporting granularity of the terminal device according to the first service area, for example, setting the location reporting granularity to the first service area, or the first service.
  • the multiple of the area for example, the first service area of 0.5 times, the specific multiple relationship may be set according to the movement mode of the terminal, such as the moving speed, the moving range, etc., or may be configured in advance, etc., and is not limited herein, usually
  • the location reporting granularity is not greater than the first service area.
  • the second implementation manner of determining the location reporting granularity is: the session management function entity determines, according to the second location information of the terminal device, the session service area to which the current session belongs, where the second location information is the session management function entity in the terminal device.
  • the location information of the terminal device received during the current session establishment process or during the process of switching the second user plane function entity to the third user plane function entity, and the second user plane function entity is used to switch to the third user plane function
  • the entity previously provides services for the session of the terminal device, and the third user plane function entity is used to provide services for the current session.
  • the session management function entity determines the location reporting granularity of the terminal device according to the first service area and the session service area, where the location reporting granularity is not greater than the intersection area of the first service area and the session service area.
  • the first user plane function entity may be an N3 UPF
  • the second user plane function entity and the third user plane function entity may be an anchor point UPF
  • the anchor UPF does not change at all. Therefore, the manner in which the location reporting granularity is determined is applicable to the PDU session being SSC mode 2 and SSC mode 3.
  • the specific implementation manner of determining the location reporting granularity is: the session management function entity acquires at least one location reporting requirement, and the at least one location reporting requirement includes at least one area information, where the at least one area information is used to indicate that the terminal device needs to report the location information.
  • the session management function entity determines the location report granularity according to the first service area and the at least one area information, where the location reporting granularity is an intersection of the first service area and the at least one area information.
  • the session management function entity may obtain at least one location reporting requirement from other network element devices, and may also generate at least one location reporting requirement according to the needs of the network element device, for example, the charging requirement also needs to report the location information of the terminal device by the mobility management function entity.
  • the session management function entity selects the minimum reporting granularity among these requirements as the location reporting granularity of the PDU session.
  • the specific implementation manner of determining the granularity of reporting the third location of the location reporting granularity and the specific implementation manner of reporting the granularity of the second determining location may be performed.
  • the location reporting granularity is determined according to the first service area, the session service area, and the at least one area information, where the location reporting granularity is not greater than the first service area, the session service area, and the at least one area information. Intersection.
  • the manner of determining the session service area in the method for reconstructing the user plane path as shown in FIG. 6 may be determined in the method for reconstructing the originating user plane as shown in FIG. 2a in the embodiment of the present application.
  • the manner of the session service area will not be described here.
  • FIG. 7 it is a communication system in which the communication system shown in FIG. 7 is a specific implementation form of the communication system as shown in FIG.
  • the communication system shown in FIG. 7 includes AMF, SMF, UPF, Policy Control Function (PCF), UDM, Authentication Server Function (AUSF), and Radio Access Network (RAN).
  • the RAN is also called AN, Data Network (DN).
  • DN Data Network
  • the N3 UPF and the anchor UPF for providing services for the current PDU session of the terminal device in the communication system shown in FIG. 7 are integrated into different logical function modules on the same physical device, and thus in FIG. 7 It is indicated by an UPF.
  • the N3 UPF and the anchor UPF can also be integrated on different physical devices.
  • the terminal device is connected to the AMF through N1; the RAN and the AMF are connected through N2; the N3 UPF is connected to the RAN through the N3; the SMF is connected to the N3 UPF and the anchor UPF through the N4; and the anchor point UPF is passed through the N6.
  • the SMF is connected to the PCF through the N7; the AMF is connected to the UDM through the N8; the interface between the UPFs is N9, wherein the interface between the N3 UPF and the anchor UPF, the interface between the N3 UPF and the N3 UPF, and the anchor
  • the interface between the point UPF and the anchor UPF is N9; the SMF is connected to the UDM through N10; the AMF is connected to the SMF through N11; the AUSF is connected to the AMF through N12; the AUSF is connected to the UDM through N13; and the AMF is connected to the AMF through the N14.
  • AMF is connected to PCF via N15.
  • the session management function entity in the method for initiating user plane path reconstruction as shown in FIG. 2a, FIG. 2b or FIG. 4a, FIG. 4b is equivalent to the SMF shown in FIG.
  • the mobility management function entity in the method for initiating the user plane path reconstruction shown in FIG. 2a, FIG. 2b or FIG. 4a, FIG. 4b is equivalent to the AMF as shown in FIG. 7, and FIG. 2a in the embodiment of the present application
  • the user plane function entity in the method for initiating the user plane path reconstruction shown in FIG. 2b or FIG. 4a and FIG. 4b is equivalent to the UPF as shown in FIG. 7.
  • the user plane function management entity in the method of initiating the user plane path reconstruction may be equivalent to the PDU session anchor UPF and the second user plane in the method of initiating the reconstruction of the user plane path as shown in FIG. 4a or 4b.
  • the functional entity, the third user plane functional entity is equivalent to the PDU session anchor UPF, and the first user plane functional entity and the first target user plane functional entity in the method for initiating the reconstruction of the user plane path as shown in FIG. 4a or FIG. 4b Equivalent to N3 UPF.
  • the following is a description of the technical solution for initiating the user plane path reconstruction of the PDU session in the communication system shown in FIG. 7 as an example.
  • the process of initially creating a PDU session or re-establishing a PDU session includes:
  • Step 800 The terminal device sends a PDU session establishment request to the AMF, and initiates a process of creating a PDU session, where the PDU session establishment request may be carried in a Non Access Stratum (NAS) message or other message, the PDU session.
  • the establishment request includes the parameter information required by the network (referred to as AMF or SMF) to create a PDU session for the terminal device.
  • AMF Access Management Function
  • SMF Selection Function
  • the AMF selects the SMF according to the parameter information included in the PDU session establishment request and the location information of the terminal device.
  • Step 801 The AMF sends a session establishment request message to the selected SMF, where the session establishment request message includes location information of the terminal device and parameter information required for establishing a PDU session.
  • the location information of the terminal device is the current cell ID or TAI of the terminal device, where the location information of the terminal device is obtained from the RAN.
  • the AMF can also send a TA List to the selected SMF.
  • the SMF selects the N3 UPF and the PDU session anchor UPF according to the parameter information required for establishing the PDU session and the location information of the terminal device included in the session establishment request.
  • the N3 UPF and the anchor UPF are integrated in one entity.
  • the process of establishing the tunnel between the N3 UPF and the anchor UPF needs to be added in the PDU session creation process.
  • the specific process refer to the related art. It is not described in the embodiment of the present application.
  • Step 802 The SMF obtains subscription information related to the PDU session of the terminal device from the UDM.
  • Step 803 The SMF obtains related policy information of the PDU session of the terminal device from the PCF.
  • Step 804 The SMF generates an N4 message according to the obtained subscription information and related policy information of the PDU session of the terminal device, sends an N4 message to the UPF, creates a user plane resource required for the PDU session, and configures a PDU session for the UPF. Forwarding rules, reporting rules, and other information.
  • Step 805 For the PDU session of the SSC mode 1, the SMF determines the location reporting granularity of the PDU session according to the service area of the selected N3 UPF. For the PDU session of the SSC mode 2 or the SSC mode 3, the SMF includes the message according to the session establishment request. The location information of the terminal device determines the PDU Session Service Area (PSSA for short); then determines the location reporting granularity of the PDU session for the terminal device according to the service area of the N3 UPF and the PSSA. The SMF saves the determined location report granularity.
  • PSSA PDU Session Service Area
  • the SMF may also need to consider other requirements when reporting granularity in the location of the PDU session, such as billing requirements. If other requirements, such as billing requirements, require the AMF to report the location information of the terminal device, the SMF selects the minimum reporting granularity among the requirements as the location reporting granularity of the PDU session. For example, when the charging requirement needs to charge the PDU session according to the TAI, the reporting granularity according to the charging policy is based on the TAI. If the service area of the N3 UPF is a set of TAIs, the location reporting granularity defined by the SMF is based on the TAI, rather than the set of TAIs of the UPF-based service area.
  • the SMF When the SMF does not receive other requirements for affecting the location reporting granularity, the SMF only determines the location reporting granularity according to the service area of the N3 UPF. Assuming that the service area of the N3 UPF is a subset of the TA List, the service area with the granularity of the UPF is reported. At this time, when the terminal device moves out of the service area of the N3 UPF, the AMF reports the new location information of the terminal device to the SMF.
  • Step 806 The SMF generates a session establishment response message according to the location reporting granularity, where the session establishment response message includes a location reporting granularity and an N2 message, and the N2 message includes an SM N2 message and an SM NAS message, and sends a session establishment response message to the AMF.
  • Step 807 After receiving the session establishment response message, the AMF acquires and saves the location reporting granularity, and generates a PDU session establishment response, and sends a PDU session establishment response NAS message and an SM N2 message to the RAN.
  • the AMF generates a PDU session establishment response according to the receiving of the SM NAS from the SMF, and sends the PDU session establishment response to the AN together with the SM N2 information received from the SMF.
  • the PDU session establishment response may be carried in a NAS message or other message.
  • Step 808 The RAN configures an RRC link according to the SM N2 information message, and sends a PDU session establishment response to the terminal device.
  • Step 809 The RAN sends an N2 message to the AMF, where the N2 message includes an SM N2 message, and the SM N2 information includes downlink N3 tunnel information of the RAN.
  • step 810 the AMF forwards the SM N2 information to the SMF.
  • step 811 the SMF updates the UPF.
  • step 812 the SMF sends a response message to the AMF.
  • a method for user plane path switching in the Xn handover procedure is taken as an example of a PDU session in SSC mode 1. Wherein, it is assumed that the original user plane path of the terminal device is the terminal device. (source RAN) Anchor point UPF, the method for user plane path switching in the Xn handover process as shown in FIG. 9 includes:
  • Step 900 After the S-RAN determines that the terminal device needs to be handed over to the T-RAN (destination-RAN), an Xn-based handover procedure is performed between the S-RAN and the T-RAN.
  • the Xn-based handover process may include context transfer, data forwarding, and the like.
  • the T-RAN initiates an update process of the N3 tunnel.
  • the T-RAN sends an N2 message to the AMF.
  • the N2 message includes current cell information and/or TAI of the terminal device.
  • the N2 message also carries the SM N2 information, and the SM N2 information includes the downlink tunnel information of the T-RAN corresponding to all the PDU sessions in the activated state.
  • Step 902 After receiving the N2 message, the AMF determines that the SM N2 information includes the downlink tunnel information of the T-RAN corresponding to all the PDU sessions in the activated state, and sends the information to the SMF corresponding to all the PDU sessions included in the SM N2 information.
  • a path update message including the current location of the terminal device, such as a cell ID and/or a TAI.
  • the AMF determines whether it is necessary to send a location update notification message of the terminal device to the corresponding SMF according to the location granularity of each PDU session not included in the SM N2 message and the current location information of the corresponding terminal device. .
  • the AMF sends an update session notification message to each SMF that needs to send a location update notification message, and sends the current location information of the terminal device, such as a cell ID or TAI, to the corresponding SMF.
  • Step 903 The SMF determines, according to the current location information of the terminal device and the service area of the N3 UPF1 of the PDU session, whether to modify the user plane path, for example, whether to add a new N3 UPF or perform N3 UPF switching or delete the original user plane path. N3 UPF.
  • the anchor UPF ie, PDU session anchor UPF
  • the SMF determines that a new N3 UPF is required, the SMF selects a new N3 UPF (corresponding to N3 UPF2 in the figure) based on information such as the location of the UE.
  • the SMF selects a new N3 UPF (corresponding to N3 UPF2 in the figure) based on information such as the location of the UE.
  • the actual process is to delete the N3 UPF1 in the original user plane path.
  • the N3 UPF1 and the anchor UPF in the original user plane path are combined, the actual process is to add N3 in the user plane path.
  • UPF2 selects a new N3 UPF (corresponding to N3 UPF2 in the figure) based on information such as the location of the UE.
  • the actual process is to delete the N3 UPF1 in the original user plane path.
  • the N3 UPF1 and the anchor UPF in the original user plane path are combined, the actual process is to add N3 in the user plane path.
  • Step 904 The SMF sends a message to the N3 UPF2 to create a user plane path (the user plane path is an N9 tunnel and an N3 tunnel).
  • the SMF For a PDU session that does not need to switch N3 tunnels, the SMF only creates an uplink tunnel for the N9 tunnel and the N3 tunnel.
  • the SMF creates N9 tunnels and N3 tunnels (including upstream and downstream).
  • step 905 the SMF instructs the anchor UPF to update the user plane path.
  • Step 906 If the SMF selects a new N3 UPF for the PDU session (such as N3 UPF2 as shown in FIG. 9, that is, the N3 UPF handover is performed), the SMF determines the new location reporting granularity according to the service area of the N3 UPF2. The SMF sends an update session response message to the AMF, where the update session response message includes a new location report granularity.
  • a new N3 UPF for the PDU session such as N3 UPF2 as shown in FIG. 9, that is, the N3 UPF handover is performed
  • the SMF sends an update session response message to the AMF, where the update session response message includes a new location report granularity.
  • the update session response message further includes an SM N2 message, where the SM N2 message includes N3 uplink tunnel information of the N3 UPF2 corresponding to the PDU session.
  • Step 907 The AMF sends the SM N2 message sent by the SMF to the T-RAN for the PDU session that needs to switch the N3 tunnel.
  • step 908 the SMF initiates a PDU session for deleting the N3 UPF1.
  • the user plane path after switching is: terminal device Anchor point UPF.
  • the method for switching the household path as shown in FIG. 9 is also applicable to other switching processes in the connected state, for example, the switching process based on the N2 interface.
  • FIG. 10 it is a flow of user plane path switching in the registration process.
  • the flow of the user plane path switching in the registration process shown in FIG. 10 is exemplified by the PDU session based on the SSC mode 1 in the communication system shown in FIG. 7.
  • the terminal device specifically The type of registration process in this embodiment may be periodic registration, or location update registration due to movement of the terminal device.
  • the specific user plane switching process shown in FIG. 10 includes:
  • Step 1000 The terminal device sends a registration request to the AMF, and the type of the registration request may be a periodic registration request or a location update registration request.
  • the registration request may be carried in the NAS message or other message, and the RAN selects the AMF according to the temporary ID of the terminal device, and sends the registration request and the current location information (such as the cell ID and/or TAI) of the terminal device to the AMF.
  • the terminal device may request to activate some or all of the PDU sessions in the registration request.
  • Step 1001 If the AMF determines that the real ID information of the terminal device is not stored, the AMF requests the terminal device for the ID information.
  • step 1002 the AMF initiates an authentication process according to its own needs.
  • step 1003 the AMF sends a location update request to the UDM, registers the AMF as the service AMF of the terminal device, and acquires the user subscription data from the UDM.
  • Step 1004 If the terminal device requests to activate the PDU session in the registration request, the AMF sends a session update request message to the SMF corresponding to the request to activate the PDU session, where the session update request message includes location information of the terminal device, such as a cell ID and / or TAI.
  • the AMF checks the location reporting granularity information and the current location information of the terminal device. If the current terminal device moves out of the location reporting granularity of the session subscription, the AMF sends a session update request to the SMF. In the message, the AMF sends the current location of the terminal device (such as the cell ID and/or TAI) to the SMF.
  • Step 1005 The SMF determines, according to the current location information of the terminal device and the service area of the N3 UPF1 of the PDU session, whether to modify the user plane path, for example, whether to add a new N3 UPF or perform N3 UPF switching or the original N3 UPF. Remove from the path.
  • the SMF determines that a new N3 UPF needs to be selected, the SMF selects a new N3 UPF based on the location information of the terminal device and the like (N3 UPF2 as shown in FIG. 10).
  • N3 UPF2 and the anchor UPF are integrated in the same physical device, the actual process is to delete the N3 UPF1 in the path.
  • the N3 UPF1 and the anchor UPF are combined, the actual process is to add N3 UPF2 to the path.
  • the SMF sends an N4 message to the N3 UPF2 to create a user plane path (the user plane path is N3, N9 tunnel).
  • the SMF For PDU sessions that do not need to be activated, the SMF only creates an upstream tunnel for the N9 tunnel and the N3 tunnel.
  • the SMF creates an N9 tunnel and an N3 uplink and downlink tunnel for the PDU session to be activated.
  • step 1007 the N3 UPF2 sends an N4 response message to the sending SMF.
  • step 1008 the SMF sends an indication to the anchor UPF to update the user plane path.
  • step 1009 the anchor UPF sends an N4 response message to the SMF.
  • step 1010 other steps of the registration process are performed.
  • the SMF determines a new location reporting granularity based on the new N3 UPF of the PDU session (ie, N3 UPF2).
  • the SMF reports the granularity of the new location of the PDU session to the AMF.
  • the SMF creates an N3 tunnel for the UE.
  • the flow of the user plane path switching of the terminal device in the service request is performed by taking the PDU session based on the SSC mode 1 in the communication system shown in FIG. 7 as an example, and specifically includes:
  • the terminal device sends a service request to the AMF.
  • the RAN carries the current location information of the terminal device, such as a cell ID and a TAI, etc., when forwarding the service request.
  • the service request may be carried in a NAS message or other message, which is not limited herein.
  • step 1101 the AMF authenticates the terminal device according to its own requirements.
  • Step 1102 If the terminal device requests to activate one or more PDU sessions in the service request, the AMF sends an update session request to the SMF corresponding to the PDU session. In the update session request, the AMF sends the current location information of the terminal device to the SMF. .
  • the AMF checks the location reporting granularity corresponding to other PDU sessions of the terminal device that are not required to be activated. If the current location information of the terminal device moves out of the range of the reported location granularity, the AMF sends an update to the SMF corresponding to the PDU session.
  • the session request sends the current location information (such as cell ID and/or TAI) of the terminal device to the SMF.
  • Step 1103 The SMF that receives the current location information of the terminal device determines whether to add a new N3 UPF, delete the N3 UPF, or switch the N3 UPF according to the current location information of the terminal device and the service area of the N3 UPF1. If the SMF determines that a new N3 UPF is required, the SMF selects N3 UPF2 based on information such as the location of the terminal device.
  • Step 1104 The SMF sends an N4 message to the N3 UPF2 to create an N9 tunnel between the N3 UPF2 and the anchor UPF.
  • the SMF For PDU sessions that do not need to be activated, the SMF only creates an upstream tunnel for the N9 tunnel and the N3 tunnel.
  • the SMF creates an N9 tunnel and an N3 uplink and downlink tunnel for the PDU session to be activated. If the service request is triggered by the network, the N4 message also creates a forwarding tunnel of N3 UPF1 to N3 UPF2 for the PDU session that needs to be activated.
  • Step 1105 N3 UPF2 sends an N4 response message to the SMF.
  • step 1106 the SMF sends an N4 message to the anchor UPF to update the user plane path (N9 tunnel) of the PDU session.
  • step 1107 the anchor UPF sends an N4 response message to the SMF.
  • Step 1108 If the service request is triggered by the network, the SMF sends an N4 message to the N3 UPF1 to create a forwarding tunnel between the N3 UPF1 and the N3 UPF2. At the same time, the N4 message deletes the N9 tunnel between N3 UPF1 and the anchor UPF.
  • Step 1109 N3 UPF1 sends an N4 response message to the SMF.
  • Step 1110 If the N3 UPF changes, the SMF determines the new location reporting granularity of the PDU session according to the service range of the new N3 UPF (N3 UPF2 in FIG. 11).
  • the SMF sends an update session response message to the AMF, which includes the new location reporting granularity of the PDU session.
  • the message further includes SM N2 information, and the SM N2 information includes N3 uplink tunnel information of the N3 UPF2.
  • steps 1112 to 1118 need not be performed.
  • Step 1111 The AMF sends an N2 message to the RAN, where the N2 message includes an SM N2 message sent by the SMF.
  • Step 1112 RRC reconfiguration is performed between the RAN and the terminal device to allocate resources for the PDU session PDU session just activated.
  • the uplink data will be sent from the RAN to N3 UPF2.
  • the RAN sends an N2 message response to the AMF, where the N2 message response carries the SM N2 information, and the SM N2 message includes the N3 downlink tunnel information of the RAN.
  • Step 1114 The AMF sends an N11 message to the SMF, where the N11 message includes the SM N2 information sent by the RAN.
  • step 1115 the SMF updates the session policy.
  • the SMF sends an N4 message to the N3 UPF2 to update the N3 tunnel of the N3 UPF2.
  • the downlink data is sent from the N3 UPF2 to the RAN, and the downlink forwarding data is sent from the N3 UPF1 to the RAN via the N3 UPF2.
  • N3 UPF1 sends an end identifier to the SMF after transmitting the last cached data.
  • the SMF sends a Delete Forwarding Tunnel Request N4 message to N3 UPF1 and N3 UPF2, instructing N3 UPF1 and N3 UPF2 to delete the forwarding tunnel.
  • the SMF sets a forwarding timer locally. When the forwarding timer expires, the SMF sends a Delete Forwarding Tunnel Request N4 message to N3 UPF1 and N3 UPF2, instructing N3 UPF1 and N3 UPF2 to delete the forwarding tunnel.
  • the N3 UPF1 and the N3 UPF2 After receiving the request to delete the forwarding tunnel, the N3 UPF1 and the N3 UPF2 delete the forwarding tunnel, and the N3 UPF1 and the N3 UPF2 respectively send a delete forwarding tunnel response to the SMF, and notify the SMF to complete the deletion of the forwarding tunnel.
  • the delete forwarding tunnel request and the delete forwarding tunnel response may be carried in an N4 message or other message, which is not limited herein.
  • step 1118 the SMF sends an N11 response message to the AMF.
  • Step 1118 can be performed prior to step 1117.
  • the flow of the reconstruction of the PDU session is exemplified by the PDU session based on the SSC mode 2 or the SSC mode 3 in the communication system shown in FIG. 7.
  • the SMF is based on The location information after the terminal device is moved and the session service area of the PDU session (also referred to as the PSSA).
  • the session service area of the PDU session also referred to as the PSSA.
  • the process of reestablishing a specific PDU session includes:
  • Step 1200 Before the terminal device moves, the anchor point of the PDU session of the terminal device is the anchor point UPF1. After the terminal device moves, a process such as a re-registration process or a handover process may be triggered, and the terminal device may initiate a service request (SR) process to trigger activation of the PDU session in an idle state or a connected state.
  • SR service request
  • the AMF determines whether the location information of the terminal device needs to be notified to the SMF according to the location reporting granularity of the terminal device in the re-registration process or the handover process. If the AMF determines the location of the PDU session of a certain terminal device and determines the location information of the terminal device to notify the SMF, the AMF sends the location information of the terminal device to the SMF. The location information of the terminal device can be sent to the SMF along with other N11 messages.
  • Step 1202 The SMF determines whether the location information of the terminal device is within the PSSA of the PDU session to determine whether to initiate a re-establishment process of the PDU session. If the SMF determines a re-establishment procedure for instructing the terminal device to initiate a PDU session, step 1203 is performed.
  • the process of reestablishing a PDU session refers to establishing a PDU session to the same data network.
  • Step 1203 The SMF sends a NAS message to the terminal device, instructing the UE to initiate reestablishment of the PDU session.
  • the NAS message is sent via AMF.
  • Step 1204 The terminal device initiates reestablishment of the PDU session after receiving the NAS message sent by the SMF.
  • the anchor point for the new PDU session is the anchor point UPF2.
  • the terminal device releases the original PDU session before re-establishing the PDU session.
  • the terminal device releases the original PDU session as needed after establishing a new PDU session.
  • the device in the embodiment of the present application further provides a device for initiating user plane path reconstruction as shown in FIG. 13a and FIG. 14a, and the method corresponding to the device shown in FIG. 13a in the embodiment of the present application is the present application.
  • Implementing a method for initiating user plane path reconstruction, such as shown in FIG. 2a and FIG. 2b so that an implementation of the apparatus shown in FIG. 13a, such as FIG. 2a and FIG. 2b, may be used to initiate user plane path reconstruction.
  • the implementation of the method the repetition will not be repeated.
  • the method corresponding to the device shown in FIG. 14a in the embodiment of the present application is a method for initiating user plane path reconstruction, such as shown in FIG. 4a and FIG. 4b
  • the present application implements the device shown in FIG. 14a.
  • the apparatus for initiating user plane path reconstruction in the embodiment of the present application includes: a processing module 1310a, and a receiving module 1320a;
  • the processing module 1310a is configured to determine, according to the first location information of the terminal device, a session service area to which the current session of the terminal device belongs, where the first location information is that the session management function entity is in the process of establishing the current session, or is switching the first user.
  • the location information of the terminal device received by the function entity to the second user plane function entity, the first user plane function entity is configured to provide a service for the session of the terminal device before switching to the second user plane function entity, and second The user plane function entity is used to provide services for the current session;
  • the receiving module 1320a is configured to receive second location information of the terminal device that is sent by the mobility management function entity.
  • the processing module 1310a is further configured to: when determining that the second location information received by the receiving module is not in the session service area, instruct the terminal device to initiate a re-establishment process for the current session, or initiate a handover process, where the handover process is used for the current session.
  • the user plane function entity of the service switches to the target user plane function entity, and the target user plane function entity is used to provide services for the terminal device session after the handover process is completed.
  • the session service area includes a service area of a user plane function entity that serves the current session.
  • the processing module 1310a is configured to: determine that the second location information is not in the session service area and is not in the user plane serving the current session.
  • the terminal device is instructed to initiate a re-establishment process for the current session or initiate a handover process.
  • the processing module 1310a may determine the session service area based on the following implementations:
  • processing module 1310a may determine the size of the session service area based on the following:
  • the processing module 1310a determines the location reporting granularity of the terminal device according to the session service area, where the location reporting granularity is used to instruct the mobility management function entity to report the terminal to the session management function entity.
  • the range of location information of the device; the sending module 1330 in the device sends the location reporting granularity determined by the processing module to the mobility management function entity.
  • the processing module 1310a obtains at least one location reporting requirement before determining the location reporting granularity according to the session service area, and the at least one location reporting requirement includes at least one area information, where the at least one area information is used to indicate that the terminal device needs to report the location information. The range is determined. Then, according to the session service area and the at least one area information, the location reporting granularity is determined, and the location reporting granularity is an intersection of the session service area and the at least one area information.
  • the device for initiating user plane path reconstruction as shown in FIG. 13a exists as a physical device alone, its hardware structure may be a session management function device as shown in FIG. 13b, wherein the processing module 1310a shown in FIG. 13a may be processed.
  • the receiver 1310b is implemented, and the receiving module 1320a and the sending module 1330a can be implemented by the communication interface 1320b.
  • the session management function device shown in FIG. 13b further includes a memory 1330b for storing the software program for storing and the communication interface 1320b. Transmitting data information and the like, the processor 1310b is configured to read the software programs and data stored in the memory 1330b and implement the method of the present application such as that shown in FIG. 2a or FIG. 2b.
  • the processor 1310b may be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for performing related operations.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • session management function device shown in FIG. 13b only shows the processor 1310b, the communication interface 1320b, and the memory 1330b, in a specific implementation process, those skilled in the art should understand that the session management function device further includes Other devices necessary for proper operation. At the same time, those skilled in the art will appreciate that the session management function device may also include hardware devices that implement other additional functions, depending on the particular needs. Moreover, those skilled in the art will appreciate that the session management function device may also only include the devices or modules necessary to implement the embodiments of the present application, and does not necessarily include all of the devices shown in FIG. 13b.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • the apparatus for initiating user plane path reconstruction includes: a processing module 1410a and a receiving module 1420a;
  • the receiving module 1420a is configured to receive first location information of the terminal device sent by the mobility management function entity;
  • the processing module 1410a is configured to: when determining that the first location information received by the receiving module 1420a is not in the first service area, select the first target user plane function entity according to the first location information, and initiate a user plane path for the current session. Reconstruction process;
  • the first service area is a service area of the first user plane function entity, and the first user plane function entity is used to provide a service for the current session of the terminal device, where the first target user plane function entity is in the reconstructed user plane path.
  • the session of the terminal device provides services.
  • the processing module 1410a determines the location reporting granularity of the terminal device according to the first service area, where the receiving module 1420a receives the first location information of the terminal device sent by the mobility management function entity, where the location report is The granularity is used to indicate that the mobility management function entity reports the location information of the terminal device to the session management function entity.
  • the sending module 1430a in the device is configured to send the location reporting granularity to the mobility management entity.
  • the processing module 1410a determines, according to the second location information of the terminal device, the session service area to which the current session belongs, where the second location information is the session management function entity at the current.
  • the location information of the terminal device received during the session establishment process of the terminal device or during the process of switching the second user plane function entity to the third user plane function entity, and the second user plane function entity is used to switch to the third user
  • the function entity provides a service for the session of the terminal device, and the third user plane function entity is used to provide a service for the current session; and the location report granularity of the terminal device is determined according to the first service area and the session service area, where the granularity of the location report is not It is larger than the intersection area of the first service area and the session service area.
  • the example processing module 1410a obtains at least one location reporting requirement before determining the location reporting granularity according to the first service area, where the at least one location reporting requirement includes at least one area information, and the at least one area information is used to indicate that the terminal device needs to report the location information. And determining, according to the first service area and the at least one area information, a location reporting granularity, where the location reporting granularity is an intersection of the first service area and the at least one area information.
  • a forwarding tunnel is created, and the forwarding tunnel is the first target user.
  • the tunnel between the surface functional entity and the first user plane functional entity causes the first user plane functional entity to send the cached data to the first target user plane functional entity through the forwarding tunnel.
  • the example processing module 1410a deletes the forwarding tunnel after determining that the receiving module receives the identifier of the completed cache data transmission sent by the first user plane function entity, or starts the forwarding timer after creating the forwarding tunnel.
  • the forwarding tunnel is deleted after the forwarding timer reaches the preset duration.
  • the device for initiating user plane path reconstruction as shown in FIG. 14a exists as a physical device alone, its hardware structure may be a session management function device as shown in FIG. 14b, wherein the processing module 1410a shown in FIG. 14a may be processed.
  • the receiver 1410b is implemented, and the receiving module 1420a and the transmitting module 1430a are implemented by the communication interface 1420b.
  • the session management function device shown in FIG. 14b further includes a memory 1430b for storing the software program for storing and the communication interface 1420b. Transmitting data information and the like, the processor 1410b is configured to read the software programs and data stored in the memory 1430b and implement the method of the present application such as that shown in FIG. 2a or as shown in FIG. 2b.
  • the processor 1410b may be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for performing related operations.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • session management function device shown in FIG. 14b only shows the processor 1410b, the communication interface 1420b, and the memory 1430b, in a specific implementation process, those skilled in the art should understand that the session management function device further includes Other devices necessary for proper operation. At the same time, those skilled in the art will appreciate that the session management function device may also include hardware devices that implement other additional functions, depending on the particular needs. Moreover, those skilled in the art will appreciate that the session management function device may also only include the devices or modules necessary to implement the embodiments of the present application, and does not necessarily include all of the devices shown in FIG. 14b.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software 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 invention 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 Transfer 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 such as a server, data center, or the like that includes one or more available 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)).
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种发起用户面路径重建的方法、装置及通信系统，用以为终端设备的会话提供更好的服务，以提高用户体验。其中该方法包括：会话管理功能实体根据终端设备的第一位置信息，确定所述终端设备的当前会话所属的会话服务区，并在接收到移动性管理功能实体发送的所述终端设备的第二位置信息后，若确定所述第二位置信息不在所述会话服务区内，则指示所述终端设备发起针对所述当前会话的重建流程，或者发起切换流程。由于引入了会话服务区，因此当终端设备为在两个相邻的用户面功能实体的服务区域的边缘来回移动时，避免了在两个用户面功能实体之间来回切换导致的乒乓效应，从而提高了用户体验。

Description

一种发起用户面路径重建的方法、装置及通信系统
本申请要求于2017年3月17日提交中国专利局、申请号为201710161100.6、发明名称为“一种发起用户面路径重建的方法、装置及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种发起用户面路径重建的方法、装置及通信系统。
背景技术
在第五代移动通信技术(5-Generation，5G)中，移动性管理与会话管理分拆成两个实体，分别为核心网接入和移动性管理功能(Core Access and Mobility Management Function，AMF)和会话管理功能(Session Management Function，SMF)。其中AMF负责终端设备的移动性管理，包括跟踪区列表(Tracking Area List，TA List)的制定。而SMF负责会话管理，包括用户面功能(User Plane Function，UPF)的选择、分组数据单元(Packet Data Unit，PDU)会话的建立等。并且，在5G中，UPF根据其负责的功能不同，又可以分为N3 UPF和PDU会话锚点UPF(简称PSA，PDU Session Anchor)，其中，N3 UPF与无线接入网(Radio Access Network，RAN)通过N3接口连接，PSA与数据网络通过N6接口连接。其中，每个UPF会有一定的服务范围，具体的，N3 UPF的服务范围是指该与N3 UPF所连接的RAN的服务范围的总和，当终端设备与N3 UPF、PSA建立用户面路径时，通常情况下，终端设备的位置处于N3 UPF的服务范围和PSA的最佳服务区域内时，N3 UPF和PSA能够为终端提供较优的服务。
然而由于终端设备为手机等其它移动终端设备时，终端设备的位置不固定，而且与第四代移动通信技术(4-Generation，4G)相比，在5G中，UPF的部署位置比较灵活，UPF的服务范围也会随着部署位置的变化而有比较大的变化，且移动性管理与会话管理分拆成两个实体，因此为了为终端设备的数据通信提供更好的服务，需要重建用户面路径，但是现有的5G标准中未明确激活发起用户面路径重建的机制，为此，本申请实施例提供了一种发起用户面路径重建的方法。
发明内容
本申请提供了一种发起用户面路径重建的方法、装置及通信系统，用以为终端设备的会话提供更好的服务，以提高用户体验。
第一方面，本申请实施例发起用户面路径重建的方法，包括：
会话管理功能实体根据终端设备的第一位置信息，确定所述终端设备的当前会话所属的会话服务区，并在接收到移动性管理功能实体发送的所述终端设备的第二位置信息后， 若确定所述第二位置信息不在所述会话服务区内，则指示所述终端设备发起针对所述当前会话的重建流程，或者发起切换流程，所述切换流程用于将为所述当前会话服务的用户面功能实体切换到目标用户面功能实体，所述目标用户面功能实体用于在完成所述切换流程后为所述终端设备的会话提供服务。
其中，所述第一位置信息为所述会话管理功能实体在所述当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的所述终端设备的位置信息，所述第一用户面功能实体用于在切换到所述第二用户面功能实体之前为所述终端设备的会话提供服务，所述第二用户面功能实体用于为所述当前会话提供服务。
需要说明的是，在本申请实施例中当前会话建立过程包括：初始创建当前会话的过程，以及重建会话到当前会话的过程。
由于引入了会话服务区，因此当终端设备为在两个相邻的用户面功能实体的服务区域的边缘来回移动时，避免了在两个用户面功能实体之间来回切换导致的乒乓效应，从而提高了用户体验。
基于第一方面，在一种可能的实现方式中，所述会话服务区包含为所述当前会话提供服务的用户面功能实体的服务区域。
基于第一方面，在一种可能的实现方式中，所述会话服务区包含部分为所述当前会话提供服务的用户面功能实体的服务区域时，所述会话管理功能实体在接收到所述移动性管理功能实体发送的所述终端设备的第二位置信息之后，确定所述第二位置信息不在所述会话服务区内且确定所述第二位置信息不在为所述当前会话提供服务的用户面功能实体的服务区域内时，指示所述终端设备发起针对所述当前会话的重建流程、或者发起所述切换流程。
基于第一方面，在一种可能的实现方式中，所述会话管理功能实体以所述终端设备的第一位置信息为中心确定所述会话服务区的中心位置；并确定所述会话服务区的大小。
基于第一方面，在一种可能的实现方式中，所述会话管理功能实体基于下列方式确定所述会话服务区的大小：
所述会话管理功能实体根据为所述当前会话提供服务的用户面功能实体的服务区域和/或所述终端设备的移动模式确定所述会话服务区的大小；其中，所述移动模式包括所述终端设备的移动范围、所述终端设备的移动速度、所述终端设备的移动轨迹中的至少一项。
基于第一方面，在一种可能的实现方式中，所述会话管理功能实体确定所述会话服务区之后，根据所述会话服务区，确定所述终端设备的位置上报粒度，所述位置上报粒度用于指示所述移动性管理功能实体向所述会话管理功能实体上报所述终端设备的位置信息的范围；并向所述移动性管理功能实体发送所述位置上报粒度。
由于通过位置上报粒度使得移动性管理功能实体减少给会话管理功能实体报告终端设备的位置信息的信令数量，无需在每次移动性管理功能收到终端的位置信息时都给每个会话功能实体报告终端设备的位置信息。
基于第一方面，在一种可能的实现方式中，所述会话管理功能实体获取至少一个位置上报需求，所述至少一个位置上报需求中包括至少一个区域信息，所述至少一个区域信息用于指示需要终端设备上报位置信息的范围；根据所述会话服务区和所述至少一个区域信 息，确定所述位置上报粒度，所述位置上报粒度为所述会话服务区与所述至少一个区域信息的交集。
第二方面，本申请实施例的发起用户面路径重建的装置，包括可实现第一方面或上述第一方面的任意一种实现方式的一个或多个模块，每个模块可执行一个或多个步骤。
第三方面，本申请实施例还提供一种会话管理功能设备，该会话管理功能设备包括处理器、存储器和通信接口，所述通信接口用于接收和发送信息，所述存储器用于存储软件程序以及接收或发送的数据信息等，所述处理器用于读取所述存储器中存储的软件程序和数据并实现第一方面或上述第一方面的任意一种实现方式提供的方法。
第四方面，本申请实施例还提供一种计算机存储介质，该存储介质可以是非易失性的，即断电后内容不丢失。该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现第一方面或上述第一方面的任意一种实现方式提供的方法。
第五方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面以及上述第一方面的任意一种实现方式提供的方法。
第六方面，本申请实施例还提供了一种通信系统，包括：会话管理功能实体和移动性管理功能实体；其中会话管理功能实体用于根据终端设备的第一位置信息，确定终端设备的当前会话所属的会话服务区；并在接收到移动性管理功能实体发送的终端设备的第二位置信息后，若确定第二位置信息不在会话服务区内，则指示终端设备发起针对当前会话的重建流程，或者发起切换流程，切换流程用于将为当前会话服务的用户面功能实体切换到目标用户面功能实体，目标用户面功能实体用于在完成切换流程后为终端设备的会话提供服务；其中，第一位置信息为会话管理功能实体在当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的终端设备的位置信息，第一用户面功能实体用于在切换到第二用户面功能实体之前为终端设备的会话提供服务，第二用户面功能实体用于为当前会话提供服务；移动性管理功能实体，用于向会话管理功能实体发送终端设备的第二位置信息。
基于第六方面，在一种可能的实现方式中，会话管理功能实体还用于在确定会话服务区之后，根据会话服务区，确定终端设备的位置上报粒度，并向移动性管理功能实体发送位置上报粒度，位置上报粒度用于指示移动性管理功能实体向会话管理功能实体上报终端设备的位置信息的范围；移动性管理功能实体还用于在向会话管理功能实体发送终端设备的第二位置信息之前，接收位置上报粒度，并确定终端设备的第二位置信息不在位置上报粒度内。
需要说明的是，在第六方面所提供的通信系统中的会话管理功能实体可以执行本申请实施例第一方面以及第一方面的任意一种实现方式提供的方法。
第七方面，本申请实施例发起用户面路径重建的方法，包括：
会话管理功能实体接收到移动性管理功能实体发送的终端设备的第一位置信息；若确定所述第一位置信息不在第一服务区域内，则根据所述第一位置信息，选择第一目标用户面功能实体，并发起针对所述当前会话的用户面路径的重建流程，所述第一目标用户面功能实体在重建后的用户面路径中为所述终端设备的会话提供服务。
其中，所述第一服务区域为第一用户面功能实体的服务区域，所述第一用户面功能实 体用于为所述终端设备的当前会话提供服务。
应理解，通常情况下，第一目标用户面功能实体的服务区域中包括第一位置信息。
由于终端设备在移出第一服务区域后，能够将用户面路径重建到第一目标用户面功能实体上，因此本申请这种激活发起用户面路径的重建机制，使得网络能够为终端设备提供更优的服务，从而提高了用户体验。
基于第七方面，在一种可能的实现方式中，所述会话管理功能实体接收所述移动性管理功能实体发送的所述终端设备的第一位置信息之前，根据所述第一服务区域，确定所述终端设备的位置上报粒度，其中所述位置上报粒度用于指示所述移动性管理功能实体向所述会话管理功能实体上报所述终端设备的位置信息的范围；并向所述移动性管理实体发送所述位置上报粒度。
由于通过位置上报粒度使得移动性管理功能实体减少给会话管理功能实体报告终端设备的位置信息的信令数量，无需在每次移动性管理功能收到终端的位置信息时都给每个会话功能实体报告终端设备的位置信息。
基于第七方面，在一种可能的实现方式中，所述会话管理功能实体根据终端设备的第二位置信息，确定所述当前会话所属的会话服务区之后，根据所述第一服务区域和所述会话服务区，确定所述终端设备的位置上报粒度，其中所述位置上报粒度不大于所述第一服务区域和所述会话服务区的交集区域。其中，所述第二位置信息为所述会话管理功能实体在当前所述终端设备的会话建立过程中、或在切换第二用户面功能实体到第三用户面功能实体的过程中接收到的所述终端设备的位置信息，所述第二用户面功能实体用于在切换到所述第三用户面功能实体之前为所述终端设备的会话提供服务，所述第三用户面功能实体用于为所述当前会话提供服务；
基于第七方面，在一种可能的实现方式中，所述会话管理功能实体获取至少一个位置上报需求，所述至少一个位置上报需求中包括至少一个区域信息，所述至少一个区域信息用于指示需要所述终端设备上报位置信息的范围，然后，根据所述第一服务区域和所述至少一个区域信息，确定所述位置上报粒度，所述位置上报粒度为所述第一服务区域与所述至少一个区域信息的交集。
基于第七方面，在一种可能的实现方式中，所述会话管理功能实体在发起针对所述当前会话的用户面路径的重建之后，若确定所述第一用户面功能实体中有缓存数据，则创建转发隧道，所述转发隧道为所述第一目标用户面功能实体与所述第一用户面功能实体之间的隧道，使得所述第一用户面功能实体通过所述转发隧道将所述缓存数据发送到所述第一目标用户面功能实体。
基于第七方面，在一种可能的实现方式中，所述会话管理功能实体创建转发隧道之后，在收到所述第一用户面功能实体发送的完成缓存数据发送的标识后，删除所述转发隧道；或者，所述会话管理功能实体在创建所述转发隧道后启动转发定时器，在所述转发定时器达到预设时长时后删除所述转发隧道。
第七方面，本申请实施例的发起用户面路径重建的装置，包括可实现第五方面或上述第五方面的任意一种实现方式的一个或多个模块，每个模块可执行一个或多个步骤。
第八方面，本申请实施例还提供一种会话管理功能设备，该会话管理功能设备包括处 理器、存储器和通信接口，所述通信接口用于接收和发送信息，所述存储器用于存储软件程序以及接收或发送的数据信息等，所述处理器用于读取所述存储器中存储的软件程序和数据并实现第七方面或上述第七方面的任意一种实现方式提供的方法。
第九方面，本申请实施例中还提供一种计算机存储介质，该存储介质可以是非易失性的，即断电后内容不丢失。该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现第七方面或上述第七方面的任意一种实现方式提供的方法。
第十方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第七方面以及上述第十方面的任意一种实现方式提供的方法。
第十一方面，提供了一种通信系统，包括会话管理功能实体和移动性管理功能实体；其中，移动性管理功能实体用于向会话管理功能实体发送终端设备的第一位置信息；
会话管理功能实体用于在接收到移动性管理功能实体发送的终端设备的第一位置信息之后，若确定第一位置信息不在第一服务区域内，则根据第一位置信息，选择第一目标用户面功能实体，并发起针对当前会话的用户面路径的重建流程；
其中，第一服务区域为第一用户面功能实体的服务区域，第一用户面功能实体用于为终端设备的当前会话提供服务，第一目标用户面功能实体在重建后的用户面路径中为终端设备的会话提供服务。
基于第十一方面，在一种可能的实现方式中，会话管理功能实体还用于根据第一服务区域，确定终端设备的位置上报粒度，并向移动性管理功能实体发送位置上报粒度；其中位置上报粒度用于指示移动性管理功能实体向会话管理功能实体上报终端设备的位置信息的范围；移动性管理功能实体还用于在向会话管理功能实体发送终端设备的第一位置信息之前，接收位置上报粒度，并确定终端设备的第一位置信息不在位置上报粒度内。
需要说明的是，在第十一方面所提供的通信系统中的会话管理功能实体可以执行本申请实施例第七方面以及第七方面的任意一种实现方式提供的方法。
第十二方面，提供了一种位置信息上报的方法，包括：
移动性管理功能实体针对终端设备的当前会话接收位置上报粒度；在确定终端设备的位置信息不在该位置上报粒度内时，则向会话管理功能实体发送该终端设备的位置信息，若确定终端设备的位置信息在该位置上报粒度内时，则确定不向会话管理功能实体发送该终端设备的位置信息。
由于通过位置上报粒度使得移动性管理功能实体减少给会话管理功能实体报告终端设备的位置信息的信令数量，无需在每次移动性管理功能收到终端的位置信息时都给每个会话功能实体报告终端设备的位置信息。
第十三方面，本申请实施例的位置信息上报的装置，包括可实现第十二方面或上述第十二方面的任意一种实现方式的一个或多个模块，每个模块可执行一个或多个步骤。
第十四方面，本申请实施例还提供一种移动性管理功能设备，该移动性管理功能设备包括处理器、存储器和通信接口，所述通信接口用于接收和发送信息，所述存储器用于存储软件程序以及接收或发送的数据信息等，所述处理器用于读取所述存储器中存储的软件程序和数据并实现第九方面或上述第九方面的任意一种实现方式提供的方法。
第十五方面，本申请实施例中还提供一种计算机存储介质，该存储介质可以是非易失 性的，即断电后内容不丢失。该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现第九方面或上述第九方面的任意一种实现方式提供的方法。
第六方面，本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1为本申请实施例通信系统的示意图；
图2a和图2b分别为本申请实施例的发起用户面路径重建的流程示意图；
图3a和图3b分别为本申请实施例会话服务区域与为当前会话提供服务的用户面功能实体的服务区域之间的关系示意图；
图4a和图4b分别为本申请实施例发起用户面路径重建的方法的流程示意图；
图5为用于解释本申请实施例的有益效果的示意图；
图6为本申请实施例用户面路径重建的方法的流程示意图；
图7为本申请实施例一种具体的通信系统的示意图；
图8为本申请实施例初始创建PDU会话或者重建PDU会话的过程的示意图；
图9为本申请实施例在Xn切换流程中用户面路径切换的方法的示意图；
图10为本申请实施例在注册流程中用户面路径切换的流程示意图；
图11为本申请实施例终端设备在业务请求时用户面路径切换的流程示意图；
图12为本申请实施例PDU会话的重建的流程示意图；
图13a为本申请实施例发起用户面路径重建的装置的结构示意图；
图13b为本申请实施例会话管理功能设备的硬件结构示意图；
图14a为本申请实施例发起用户面路径重建的装置的结构示意图；
图14b为本申请实施例会话管理功能设备的硬件结构示意图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
需要说明的是，本申请实施例中的会话管理功能实体、移动性管理功能实体、用户面功能实体等仅是一个名字，名字对设备本身不构成限定。在未来的5G网络以及未来其它的网络中，会话管理功能实体、移动性管理功能实体、用户面功能实体所对应的网元或实体也可以是其他的名字，本申请实施例对此不作具体限定。例如，会话管理功能实体可以是会话管理功能(Session Management Function，SMF)，移动性管理功能实体可以是核心网接入和移动性管理功能(Core Access and Mobility Management Function，AMF)、用户面功能实体可以为用户面功能(User Plane Function，UPF)等等，在此进行统一说明，以下不再赘述。
此外，本申请实施例中的会话管理功能实体、移动性管理功能实体、用户面功能实体等除了具备本申请实施例中的功能，还可能具备其他的功能，本申请实施例对此不作具体限定。比如，移动性管理功能实体除了具备向会话管理功能实体发送终端设备的位置信息 的功能之外，还可能具备其他的功能，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例会话管理功能实体、移动性管理功能实体、用户面功能实体等，可能由一个实体设备实现，也可能由多个实体设备共同实现，本申请实施例对此不作具体限定。即可以理解的是，本申请实施例中的会话管理功能实体、移动性管理功能实体、用户面功能实体等，都可能是实体设备内的一个逻辑功能模块，也可能是由多个实体设备组成的一个逻辑功能模块，本申请实施例对此不作具体限定。
本申请实施例发起用户面路径重建的方法可应用于如图1所示的通信系统100中，该通信系统100包括会话管理功能实体110和移动性管理功能实体120，应理解，在本申请实施例中发起用户面路径的重建针对的会话可以为分组数据单元(Packet Data Unit，PDU)会话，也可以为公用数据网(Public Data Network，PDN)会话，或者是其它会话，在本申请中不做限定。
其中，如图1所示的通信系统100中的会话管理功能实体110和移动性管理功能实体120的信息处理及信息交互过程参见本申请下面实施例提供的发起用户面路径重建的方法。
下面以PDU会话为例对本申请实施例发起用户面路径重建的方法进行详细说明，当会话为PDN会话或者其它会话时，发起用户面路径重建的方法与PDU会话类似，在此不赘述。
如图2a所示，本申请实施例发起用户面路径重建的方法，包括：
步骤200a，会话管理功能实体110根据终端设备的第一位置信息，确定终端设备的当前会话所属的会话服务区。
其中，第一位置信息为会话管理功能实体110在当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的终端设备的位置信息，第一用户面功能实体用于在切换到第二用户面功能实体之前为终端设备的会话提供服务，第二用户面功能实体用于为当前会话提供服务。
具体的，在本申请实施例中当前会话建立过程包括：初始创建当前会话的过程，以及重建会话到当前会话的过程。
例如，第一位置信息可以携带在发送给会话管理功能实体的初始创建当前会话的请求消息中，或者是单独发送第一位置信息的一个消息，或者是重建会话到当前会话的过程中的请求消息中，或者是在路径切换请求消息中，在本申请实施例中不做限定。
步骤210a，移动性管理功能实体120向会话管理功能实体110发送终端设备的第二位置信息，会话管理功能实体110接收移动性管理功能实体120发送的终端设备的第二位置信息。
步骤220a，会话管理功能实体110在接收到移动性管理功能实体120发送的终端设备的第二位置信息后，确定第二位置信息不在会话服务区内，则指示终端设备发起针对当前会话的重建流程。
在一种可能的具体实现方式中，会话管理功能实体110若确定第二位置信息在会话服务区内，则本流程结束，即不再指示终端设备发起针对当前会话的重建流程。
具体的，当会话为PDU会话时，会话服务区又可命名为分组数据单元会话服务区(PDU Session Service Area，PSSA)。其中，会话服务区是个逻辑概念，会话管理功能实体110可 以通过下列方式确定会话服务区：
会话管理功能实体110以终端设备的第一位置信息为中心，确定会话服务区的中心位置，然后，确定会话服务区的大小。
示例的，会话服务区的大小可以基于预先配置的策略进行确定，例如事先配置好会话服务区包括的小区的数量、跟踪区(Tracking Area，TA)的数量等。
此外，会话管理功能实体110还可基于下列方式确定会话服务区的大小：
会话管理功能实体110根据为当前会话提供服务的用户面功能实体的服务区域和/或终端设备的移动模式确定会话服务区的大小；其中，移动模式包括终端设备的移动范围、终端设备的移动速度、终端设备的移动轨迹中的至少一项。
以PDU会话为例，为当前会话提供服务的用户面功能实体可以为为当前会话提供服务的锚点UPF，例如对于那些不怎么移动的、且位置不靠近为当前会话提供服务的锚点UPF的服务区域边界的终端设备，可以将会话服务区制定为为当前会话提供服务的锚点UPF的服务区域；对于那些不怎么移动的、且位置靠近为当前会话提供服务的锚点UPF的服务区域边界的终端设备，可以将会话服务区制定的比较小，从而能在终端设备的位置相对稳定后，及早切换用户面路径，具体的终端设备的移动模式可以根据签约信息、或终端设备的历史移动轨迹确定。
除此之外，会话管理功能实体在制定会话服务区时，还可以考虑其他因素，以便能够为终端设备的会话提供更优的服务。
从上述会话服务区确定的方式中可以看出，不同的情况下会话管理功能实体确定的会话服务区的大小不同，会话管理功能实体确定的会话服务区可能如图3a所示包括为当前会话提供服务的用户面功能实体的服务区域，也可能如图3b所示只包括部分为当前会话提供服务的用户面功能实体的服务区域。
当会话服务区只包括部分为当前会话提供服务的用户面功能实体的服务区域时，在步骤220a中不仅要判断第二位置信息是否在会话服务区内，还要增加判断第二位置信息是否在为当前会话提供服务的用户面功能实体的服务区域的步骤，具体的，当会话管理功能实体110确定第二位置信息不在会话服务区内、且不在为当前会话提供服务的用户面功能实体的服务区域时，则指示终端设备发起针对当前会话的重建流程，否则本流程结束。
如图2b所示，为本申请实施例提供的另一种发起用户面路径重建的方法。在图2a所示的发起用户面路径重建的方法的基础上引入了终端设备的位置上报粒度的概念，具体的发起用户面路径重建的方法包括：
步骤200a，会话管理功能实体110根据终端设备的第一位置信息，确定终端设备的当前会话所属的会话服务区。
其中，第一位置信息为会话管理功能实体110在当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的终端设备的位置信息，第一用户面功能实体用于在切换到第二用户面功能实体之前为终端设备的会话提供服务，第二用户面功能实体用于为当前会话提供服务。
具体的，在本申请实施例中当前会话建立过程包括：初始创建当前会话的过程，以及重建会话到当前会话的过程。
步骤200b，会话管理功能实体110根据会话服务区，确定终端设备的位置上报粒度，位置上报粒度用于指示移动性管理功能实体120向会话管理功能实体110上报终端设备的位置信息的范围。
步骤200c，会话管理功能实体110向移动性管理功能实体120发送位置上报粒度，移动性管理功能实体120接收位置上报粒度。
步骤200d，移动性管理功能实体120确定终端设备的第二位置信息不在位置上报粒度内，则执行步骤210a。
在一种可能的具体实现方式中，移动性管理功能实体120若确定终端设备的第二位置信息在位置上报粒度内，则本流程结束，即不再向会话管理功能实体110发送终端设备的第二位置信息。
步骤210a，移动性管理功能实体120向会话管理功能实体110发送终端设备的第二位置信息。
步骤220a，会话管理功能实体110在接收到移动性管理功能实体120发送的终端设备的第二位置信息后，确定第二位置信息不在会话服务区内，则指示终端设备发起针对当前会话的重建流程。
在一种可能的具体实现方式中，会话管理功能实体110若确定定第二位置信息在会话服务区域内，则本流程结束，即不再指示终端设备发起针对当前会话的重建流程。
在如图2b所示的发起用户面路径重建的方法中，通过位置上报粒度使得移动性管理功能实体减少给会话管理功能实体报告终端设备的位置信息的信令数量，无需在每次移动性管理功能收到终端的位置信息时都给每个会话功能实体报告终端设备的位置信息。
下面针对图2b中与图2a中发起用户面路径重建的方法中不同的步骤进行具体介绍，针对图2b和图2a中相同的步骤解释，如会话服务区的确定方式、发起针对当前会话的重建流程的具体实现方式、以及对步骤200a、步骤210a、步骤220a一些解释等参见如图2a所示的发起用户面路径重建的方法中的实施方式，在此不再赘述。
具体的，在步骤200b会话管理功能实体110根据会话服务区，可基于下列方式确定终端设备的位置上报粒度：
第一种确定位置上报粒度的方式：会话管理功能实体获取至少一个位置上报需求，至少一个位置上报需求中包括至少一个区域信息，至少一个区域信息用于指示需要终端设备上报位置信息的范围；然后，会话管理功能实体根据会话服务区和至少一个区域信息，确定位置上报粒度，位置上报粒度为会话服务区与至少一个区域信息的交集。
以PDU会话为例，会话管理功能实体在制定PDU会话的位置上报粒度时还可能需要考虑其他位置上报需求，如计费需求也需要移动管理功能实体上报终端设备的位置信息，通常情况下会话管理功能实体选择这些需求中的最小上报粒度作为该PDU会话的位置上报粒度。比如，当计费需求中需要对PDU会话按跟踪区标识(Tracking Area Identity，TAI)计费时，计费需求的区域信息为TAI。若会话服务区是一组TAI，则会话管理功能实体制定的位置上报粒度为TAI，而不是会话服务区的一组TAI。
应理解，会话管理功能实体可以从至少一个其他网元设备分别获取针对该终端设备的至少一个位置上报需求，或者，会话管理功能实体根据自身的需求在本地生成的至少一个 位置上报需要求。其中，其他网元设备指的是与会话管理功能实体所在的网元设备不同的设备。
第二种确定位置上报粒度的方式：会话管理功能实体确定未获取到位置上报需求，则仅根据会话服务区，确定位置上报粒度。
为了确保终端设备的位置未移出会话服务区，通常情况下，位置上报粒度不超出会话服务区的范围，具体的位置上报粒度与会话服务区的大小关系可以基于预先设定的策略确定。
如图4a所示，本申请实施例另一种发起用户面路径重建的方法，与如图2a所示的发起用户面路径重建的方法中不同的步骤在于将图2a中的步骤220a替换为步骤400，图4a中所示的发起用户面路径重建的方法中的其它步骤与图2a中的步骤相同，因此，图4a中所示的发起用户面路径重建的方法的具体实现方式参见如图2a所示的发起用户面路径重建的方法的具体实现方式，在此不再赘述。
如图4b所示，本申请实施例还提供了一种发起用户面路径重建的方法，与如图2b所示的发起用户面路径重建的方法中不同的步骤在于将图2b中的步骤220a替换为步骤400，图4b中所示的发起用户面路径重建的方法中的其它步骤与图2b中的步骤相同，因此，图4b中所示的发起用户面路径重建的方法的具体实现方式参见如图2b所示的发起用户面路径重建的方法的具体实现方式，在此不再赘述。
具体的，步骤400，会话管理功能实体110确定第二位置信息不再会话服务区内，则发起切换流程，切换流程用于将为当前会话服务的用户面功能实体切换到目标用户面功能实体，目标用户面功能实体用于在完成切换流程后为终端设备的会话提供服务。
需要说明的是，在图4a和图4b所示的发起用户面路径重建的方法中的步骤200a，当第一位置信息为在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的所述终端设备的位置信息，则步骤400中会话管理功能实体110发起的切换流程中为当前会话服务的用户面功能实体即为第二用户面功能实体。当第一位置信息为在当前会话建立过程中接收到的所述终端设备的位置信息时，则步骤400中会话管理功能实体110发起的切换流程中为当前会话服务的用户面功能实体指的当前会话建立完成后，服务于当前会话服务的用户面功能实体。
还需要说明的是，本申请实施例如图2a、图2b、图4a和图4b所示的发起用户面路径重建的流程中，当会话为PDU会话时，用户面功能实体可以为PDU会话锚点UPF，具体的在本申请实施例如图2a、图2b、图4a和图4b所示的发起用户面路径重建的流程中涉及到的第一用户面功能实体、第二用户面功能实体、目标用户面功能实体、以及为当前会话提供服务的用户面实体等为PDU会话锚点UPF中不同的锚点UPF。
以PDU会话为例，当用户面功能实体为PDU会话锚点UPF时，由于在本申请实施例中引入了会话服务区，因此当终端设备为在如图5所示的区域1和区域2的边缘来回移动时，避免了在两个锚点UPF之间来回切换导致的乒乓效应，其中区域1为一个锚点UPF的服务区域，区域2为另一个锚点UPF的服务区域。
如图6所示，本申请实施例还提供了另一种用户面路径重建的方法，包括：
步骤600，移动性管理功能实体120向会话管理功能实体发送终端设备的第一位置信 息，会话管理功能实体110接收移动性管理功能实体120发送的终端设备的第一位置信息。
步骤610，会话管理功能实体110在接收到移动性管理功能实体120发送的终端设备的第一位置信息后，确定第一位置信息不在第一服务区域内，则执行步骤620。其中，第一服务区域为第一用户面功能实体的服务区域，第一用户面功能实体用于为终端设备的当前会话提供服务。
在一种可能的实现方式中，会话管理功能实体110若确定第一位置信息在第一服务区域内，则本流程结束，即不再执行步骤620，及其以下步骤。
步骤620，会话管理功能实体110根据第一位置信息，选择第一目标用户面功能实体。其中，第一目标用户面功能实体在重建后的用户面路径中为终端设备的会话提供服务。
步骤630，会话管理功能实体110发起针对当前会话的用户面路径的重建流程。
步骤640，会话管理功能实体110在确定第一用户面功能实体中有缓存数据后，创建转发隧道，转发隧道为第一目标用户面功能实体与第一用户面功能实体之间的隧道，使得第一用户面功能实体通过转发隧道将缓存数据发送到第一目标用户面功能实体。
步骤650，会话管理功能实体110在收到第一用户面功能实体发送的完成缓存数据发送的标识后，删除转发隧道；或者，会话管理功能实体110在创建转发隧道后启动转发定时器，在转发定时器达到预设时长时后删除转发隧道。
需要说明的是，在如图6所示的发起用户面路径重建的方法中步骤640、步骤650为非必要的步骤，即在如图6所示的发起用户面路径重建的方法中可以只执行步骤600至步骤630，也可以执行步骤600至步骤640，还可以执行步骤600至步骤640，具体的可根据实际需求决定执行哪些步骤。例如当第一用户面功能实体中没有缓存数据时，则可以只执行步骤600至步骤630。
应理解，在本申请实施例如图6所示发起用户面路径重建的方法中，由于通过判断终端设备的位置信息是否在为该终端设备的当前会话提供服务的用户面功能实体的服务区域内，来确定是否选择第一目标用户面功能实体，发起针对当前会话的用户面路径的重建，因此当会话管理功能实体为多个终端设备的当前会话提供服务时，当部分终端设备移出对应的为当前会话的提供服务的用户面功能实体时，则针对这部分的终端设备的当前会话发起用户面路径的重建流程，而无需考虑会话管理功能实体为多个终端设备的当前会话中其它部分终端设备的当前会话的用户面路径的重建流程。
示例的，还可在本申请实施例中如图6所示的发起用户面路径重建的方法的基础上，通过增加位置上报粒度，来降低移动性管理功能实体需要上报的消息数量。
具体的，在步骤600之前，会话管理功能实体110根据第一服务区域，确定终端设备的位置上报粒度，并向移动性管理功能实体120发送位置上报粒度，其中位置上报粒度用于指示移动性管理功能实体120向会话管理功能实体110上报终端设备的位置信息的范围。移动性管理功能实体120在向会话管理功能实体110发送终端设备的第一位置信息之前，判断终端设备的第一位置信息是否在该终端设备的位置上报粒度内，若确定第一位置信息在该终端设备的位置上报粒度内，则本流程结束，若确定终端设备的第一位置信息不在位置上报粒度内时，则执行步骤600。
在本申请实施例如图6所示的发起用户面路径的重建的方法中提供了确定位置上报粒度的三种具体实现方式：
第一种确定位置上报粒度的具体实现方式为：会话管理功能实体可以仅根据第一服务区域，确定终端设备的位置上报粒度，例如，将位置上报粒度设置为第一服务区域，或者第一服务区域的倍数，如0.5倍的第一服务区域，具体的倍数关系可以基于终端的移动模式如移动速度、移动范围等进行相应的设置，或预先进行配置等，在此不做限定，通常情况下，位置上报粒度不大于第一服务区域。
第二种确定位置上报粒度的具体实现方式为：会话管理功能实体根据终端设备的第二位置信息，确定当前会话所属的会话服务区，其中，第二位置信息为会话管理功能实体在终端设备的当前会话建立过程中、或在切换第二用户面功能实体到第三用户面功能实体的过程中接收到的终端设备的位置信息，第二用户面功能实体用于在切换到第三用户面功能实体之前为终端设备的会话提供服务，第三用户面功能实体用于为当前会话提供服务。然后，会话管理功能实体根据第一服务区域和会话服务区，确定终端设备的位置上报粒度，其中位置上报粒度不大于第一服务区域和会话服务区的交集区域。
需要说明的是，当会话为PDU会话时，第一用户面功能实体可以为N3 UPF，第二用户面功能实体和第三用户面功能实体可以为锚点UPF，由于当会话为PDU会话时，在PDU会话为SSC模式1时，锚点UPF始终不发生改变，因此这种位置上报粒度确定的方式适用于PDU会话为SSC模式2和SSC模式3。
第三种确定位置上报粒度的具体实现方式为：会话管理功能实体获取至少一个位置上报需求，至少一个位置上报需求中包括至少一个区域信息，至少一个区域信息用于指示需要终端设备上报位置信息的范围；然后会话管理功能实体根据第一服务区域和至少一个区域信息，确定位置上报粒度，位置上报粒度为第一服务区域与至少一个区域信息的交集。
具体的，会话管理功能实体可以从其它的网元设备获取至少一个位置上报需求，还可以根据自身需要生成至少一个位置上报需求，例如计费需求也需要移动管理功能实体上报终端设备的位置信息，通常情况下会话管理功能实体选择这些需求中的最小上报粒度作为该PDU会话的位置上报粒度。
在本申请实施例如图6所示的发起用户面路径的重建的方法中可以将确定位置上报粒度的第三种确定位置上报粒度的具体实现方式与第二种确定位置上报粒度的具体实现方式进行相结合来确定位置上报粒度，具体的：根据第一服务区域、会话服务区和至少一个区域信息确定位置上报粒度，其中位置上报粒度不大于第一服务区域、会话服务区和至少一个区域信息的交集。
应理解，本申请实施例中如图6所示的发起用户面路径的重建方法中确定会话服务区的方式可参见本申请实施例中如图2a所示的发起用户面路径的重建方法中确定会话服务区的方式，在此不再赘述。
如图7所示，为一种通信系统，其中如图7所示的通信系统为如1所示的通信系统的一种具体实现形式。
如图7所示的通信系统包括AMF、SMF、UPF、策略控制功能(Policy Control function，PCF)、UDM、认证服务器功能(Authentication Server Function，AUSF)、无线接入网(Radio  Access Network，RAN)，其中，RAN又称之为AN、数据网络(Data Network，DN)。需要说明的是在图7中所示的通信系统中用于为终端设备当前的PDU会话提供服务的N3 UPF和锚点UPF集成在同一个实体设备上的不同的逻辑功能模块，因此在图7中通过一个UPF进行示意。但是需要说明的是，N3 UPF和锚点UPF也可分别集成在不同的实体设备上。
其中，在现有的5G标准中，终端设备通过N1与AMF连接；RAN与AMF通过N2连接；N3 UPF与RAN通过N3 连接；SMF通过N4与N3 UPF和锚点UPF连接；锚点UPF通过N6与DN连接；SMF通过N7与PCF连接；AMF通过N8与UDM连接；UPF之间的接口为N9，其中，N3 UPF和锚点UPF之间的接口、N3 UPF和N3 UPF之间的接口、锚点UPF和锚点UPF之间的接口均为N9；SMF通过N10与UDM连接；AMF与SMF通过N11连接；AUSF通过N12与AMF连接；AUSF通过N13与UDM连接；AMF与AMF之间通过N14连接；AMF通过N15与PCF连接。
需要说明的是，本申请实施例中如图2a、图2b或图4a、图4b所示的发起用户面路径重建的方法中的会话管理功能实体相当于如图7所示的SMF，本申请实施例中如图2a、图2b或图4a、图4b所示的发起用户面路径重建的方法中的移动性管理功能实体相当于如图7所示的AMF，本申请实施例中如图2a、图2b或图4a、图4b所示的发起用户面路径重建的方法中的用户面功能实体相当于如图7中所示的UPF，具体的，本申请实施例中如图2a或图2b所示的发起用户面路径重建的方法中的用户面功能管理实体可以相当于PDU会话锚点UPF，以及如图4a或图4b所示的发起用户面路径的重建的方法中的第二用户面功能实体、第三用户面功能实体相当于PDU会话锚点UPF，如图4a或图4b所示的发起用户面路径的重建的方法中的第一用户面功能实体、第一目标用户面功能实体相当于N3 UPF。
接下来以在图7所示的通信系统中为例，对本申请的发起针对PDU会话的用户面路径重建的技术方案进行介绍。
如图8所示，为初始创建PDU会话或者重建PDU会话的过程，包括：
步骤800，终端设备向AMF发送PDU会话建立请求，发起创建PDU会话的创建过程，其中，PDU会话建立请求可以携带在非接入层(Non Access Stratum，NAS)消息或者其它消息中，该PDU会话建立请求中包括网络(指AMF或SMF)为终端设备创建PDU会话所需要的参数信息。AMF在接收到PDU会话建立请求后，根据PDU会话建立请求中包括的参数信息和终端设备的位置信息，选择SMF。
步骤801，AMF向选择的SMF发送会话建立请求消息，其中会话建立请求消息中包括终端设备的位置信息和建立PDU会话所需要的参数信息。
示例的，终端设备的位置信息如终端设备当前的小区ID或TAI，其中终端设备的位置信息是从RAN获取的。此外，AMF还可向选择的SMF发送TA List。然后，SMF根据会话建立请求中包括的建立PDU会话所需的参数信息和终端设备的位置信息选择N3 UPF和PDU会话锚点UPF，如图7所示，N3 UPF和锚点UPF集成在一个实体设备中，在实际应用中N3 UPF和锚点UPF分别为一个独立的实体设备时，需要在PDU会话创建流程中增加N3 UPF和锚点UPF间隧道建立的过程，具体的过程可参见现有技术，本申请实施例中不再赘述。
步骤802，SMF从UDM获取终端设备的PDU会话相关的签约信息。
步骤803，SMF从PCF获取终端设备的PDU会话的相关策略信息。
步骤804，SMF根据获取的终端设备的PDU会话相关的签约信息和相关策略信息，生成N4消息，向UPF发送N4消息，创建PDU会话所需的用户面资源，并给UPF配置PDU会话所需的转发规则、上报规则等信息。
步骤805，针对SSC模式1的PDU会话，SMF根据选择的N3 UPF的服务区域，确定该PDU会话的位置上报粒度；针对SSC模式2或SSC模式3的PDU会话，SMF根据会话建立请求消息中包括的终端设备的位置信息，确定PDU会话服务区(简称PSSA)；然后根据N3 UPF的服务区域和PSSA，确定针对终端设备的PDU会话的位置上报粒度。SMF保存确定的位置上报粒度。
需要说明的是，SMF在制定PDU会话的位置上报粒度时还可能需要考虑其他需求，如，计费需求。若其他需求，如计费需求，也需要AMF报告终端设备的位置信息，SMF选择这些需求中的最小上报粒度作为该PDU会话的位置上报粒度。比如，当计费需求需要对PDU会话按TAI计费时，根据计费策略制定的上报粒度是基于TAI。若N3 UPF的服务区域是一组TAI，则SMF制定的位置上报粒度为基于TAI，而不是基于UPF的服务区域的那一组TAI。
当SMF没有收到其他影响位置上报粒度的需求时，SMF只根据N3 UPF的服务区域确定位置上报粒度。假设N3 UPF的服务区是TA List的子集，则上报粒度为UPF的服务区域，此时，当终端设备移出N3 UPF的服务区域时，AMF将终端设备新的位置信息报告给SMF。
应理解，确定位置上报粒度的具体实现方式可参见本申请实施例如图6所示的发起用户面路径重建的方法中确定位置上报粒度的具体实现方式，在此不再赘述。
步骤806，SMF根据位置上报粒度，生成会话建立响应消息，会话建立响应消息中包括位置上报粒度和N2消息，N2消息中包括SM N2消息和SM NAS消息，并向AMF发送会话建立响应消息。
步骤807，AMF接收到会话建立响应消息后，获取并保存位置上报粒度，以及生成PDU会话建立响应，并向RAN发送PDU会话建立响应NAS消息和SM N2消息。
具体的，AMF根据从SMF收到SM NAS生成PDU会话建立响应，将该PDU会话建立响应和从SMF收到的SM N2信息一起发送给AN。其中，PDU会话建立响应可以携带在NAS消息或者其它消息中
步骤808，RAN根据SM N2信息消息配置RRC链路，并向终端设备发送PDU会话建立响应。
步骤809，RAN向AMF发送N2消息，其中N2消息中包括SM N2消息，SM N2信息包括了RAN的下行N3隧道信息。
步骤810，AMF将SM N2信息转发给SMF。
步骤811，SMF更新UPF。
步骤812，SMF给AMF发送响应消息。
如图9所示，为以SSC模式1的PDU会话为例在Xn切换流程中用户面路径切换的 方法。其中，假设终端设备的原用户面路径为终端设备
Figure PCTCN2018077025-appb-000001
(源RAN)
Figure PCTCN2018077025-appb-000002
锚点UPF，则如图9所示的在Xn切换流程中用户面路径切换的方法，包括：
步骤900，S-RAN确定需要将终端设备切换到T-RAN(目的-RAN)后，在S-RAN与T-RAN之间执行基于Xn的切换流程。其中基于Xn的切换过程可能包括上下文传递、数据转发等。切换完成后由T-RAN发起N3隧道的更新过程。
步骤901，T-RAN向AMF发送N2消息。其中，N2消息中包括终端设备当前的小区信息和/或TAI。该N2消息还携带SM N2信息，SM N2信息包括所有处于激活状态的PDU会话所对应的T-RAN的下行隧道信息。
步骤902，AMF在接收到N2消息后，确定SM N2信息包括所有处于激活状态的PDU会话所对应的T-RAN的下行隧道信息，并向SM N2信息中所包括的所有PDU会话对应的SMF发送路径更新消息，该路径更新消息中包括终端设备的当前位置，如小区ID和/或TAI。
除此之外，AMF根据每个不包括在SM N2消息中的PDU会话的位置上报粒度，和对应的终端设备的当前的位置信息，决定是否需要给对应的SMF发送终端设备的位置更新通知消息。AMF给需要发送位置更新通知消息的每个SMF发送更新会话通知消息，向对应的SMF发送终端设备的当前位置信息，如小区ID或TAI。
步骤903，SMF根据终端设备的当前位置信息和PDU会话的N3 UPF1的服务区域确定是否要修改用户面路径，比如，是否需要增加新的N3 UPF或者进行N3 UPF的切换或者在原用户面路径上删除N3 UPF。
具体的SMF根据终端设备的当前位置信息和PDU会话的N3 UPF1的服务区域确定是否修改用户面路径的方式参见如图6所示的发起用户面路径的重建方法。
由于本实施例流程假设PDU会话是SSC模式1，因此，锚点UPF(即PDU会话锚点UPF)保持不变。
若SMF判定需要新的N3 UPF，SMF根据UE位置等信息选择新N3 UPF(对应图中的N3 UPF2)。当N3 UPF2与锚点UPF合一时，实际流程是将原用户面路径中的N3 UPF1删除；当原用户面路径中的N3 UPF1与锚点UPF合一时，实际流程是在用户面路径中增加N3 UPF2。
步骤904，SMF向N3 UPF2发送消息创建用户面路径(用户面路径即N9隧道和N3隧道)。
对不需要切换N3隧道的PDU会话，SMF仅创建N9隧道及N3隧道的上行隧道。
对需要切换N3隧道的PDU会话，SMF创建N9隧道和N3隧道(包括上行和下行)。
步骤905，SMF指示锚点UPF更新用户面路径。
步骤906，若SMF为PDU会话选择了新的N3 UPF(如图9中所示的N3 UPF2，即进行了N3 UPF的切换)，SMF根据N3 UPF2的服务区域确定新的位置上报粒度。SMF向AMF发送更新会话响应消息，该更新会话响应消息中包括新的位置上报粒度。
此外，该更新会话响应消息中还携带SM N2消息，其中该SM N2消息中包括PDU会话对应的N3 UPF2的N3上行隧道信息。
步骤907，对需要切换N3隧道的PDU会话，AMF将SMF发来的SM N2消息发送给T-RAN。
步骤908，SMF发起删除N3 UPF1的PDU会话。切换后的用户面路径为：终端设备
Figure PCTCN2018077025-appb-000003
锚点UPF。
需要说明的是，如图9所示的户面路径切换的方法同样适用于连接态的其他切换流程，例如基于N2接口的切换流程。
如图10所示，为在注册流程中用户面路径切换的流程。其中，如图10所示的在注册流程中用户面路径切换的流程是以在图7所示的通信系统中基于SSC模式1的PDU会话为例的，终端设备在发起注册的过程中，具体的在该实施例中注册流程的类型可以为周期性注册，或者由于终端设备的移动而引起的位置更新注册。具体的如图10所示的用户面切换的流程包括：
步骤1000，终端设备向AMF发送注册请求，该注册请求的类型可以为周期性的注册请求或者是位置更新注册请求。其中，注册请求可以携带在NAS消息或者其它消息中，RAN根据终端设备的临时ID选择AMF，并向AMF发送注册请求和终端设备的当前位置信息(如小区ID和/或TAI)。终端设备在该注册请求中可以请求激活部分或全部PDU会话。
步骤1001，AMF若确定未存储有终端设备的真实ID信息，则向终端设备请求ID信息。
步骤1002，AMF根据自身需求，发起认证流程。
步骤1003，AMF向UDM发送位置更新请求，并将AMF注册为终端设备的服务AMF，并从UDM获取用户签约数据。
步骤1004，若在注册请求中，终端设备请求激活PDU会话，则AMF发送会话更新请求消息给请求激活PDU会话所对应的SMF，该会话更新请求消息中包括终端设备的位置信息，如小区ID和/或TAI。
对那些终端设备未请求激活的PDU会话，AMF检查其位置上报粒度信息和终端设备的当前位置信息，若当前终端设备移出了该会话订阅的位置上报粒度，AMF向SMF发送会话更新请求，在该消息中AMF将终端设备的当前位置(如小区ID和/或TAI)发送给SMF。
步骤1005，SMF根据终端设备的当前位置信息和PDU会话的N3 UPF1的服务区域确定是否要修改用户面路径，比如，是否需要增加新的N3 UPF或者进行N3 UPF的切换或者在将原来的N3 UPF从路径上删除。
由于本实施例流程假设PDU会话是SSC模式1，因此，锚点UPF保持不变。
若SMF判定需要选择新的N3 UPF，SMF根据终端设备的位置信息等信息选择新N3 UPF(如图10中所示的N3 UPF2)。当N3 UPF2与锚点UPF集成在同一个实体设备时，实际流程是将路径中的N3 UPF1删除；当N3 UPF1与锚点UPF合一时，实际流程是在路径中增加N3 UPF2。
步骤1006，SMF向N3 UPF2发送N4消息，创建用户面路径(用户面路径即N3、N9隧道)。对不需要激活的PDU会话，SMF仅创建N9隧道及N3隧道的上行隧道。对需要激活的PDU会话，SMF创建N9隧道和N3上下行隧道。
步骤1007，N3 UPF2向发送SMF发送N4响应消息。
步骤1008，SMF发送指示锚点UPF更新用户面路径。
步骤1009，锚点UPF向SMF发送N4响应消息。
步骤1010，执行注册过程其他步骤。例如SMF根据PDU会话的新N3 UPF(即N3 UPF2)确定新的位置上报粒度。SMF向AMF发送PDU会话的新位置上报粒度。对需要激活的PDU会话，SMF为UE创建N3隧道。
如图11所示，为终端设备在业务请求时用户面路径切换的流程，该流程是以在图7所示的通信系统基于SSC模式1的PDU会话为例的，具体的包括：
步骤1100，终端设备向AMF发送业务请求。RAN在转发业务请求时携带终端设备的当前位置信息，如小区ID和\或TAI等。其中，业务请求可以携带在NAS消息或者其它消息中，在此不做限定。
步骤1101，AMF根据自身的需求，对终端设备进行认证。
步骤1102，若在业务请求中终端设备要求激活一个或多个PDU会话，则AMF向PDU会话对应的SMF发送更新会话请求，在该更新会话请求中，AMF将终端设备的当前位置信息发送给SMF。
除此之外，AMF检查终端设备的其他不需激活的PDU会话对应的位置上报粒度，若终端设备的当前位置信息移出了订阅的位置上报粒度的范围，AMF给这些PDU会话对应的SMF发送更新会话请求，将终端设备的当前位置信息(如小区ID和/或TAI)发送给SMF。
步骤1103，收到终端设备的当前位置信息的SMF根据终端设备的当前位置信息和N3 UPF1的服务区域决定是否在用户面路径上增加新N3 UPF、删除N3 UPF、或者切换N3 UPF。若SMF判定需要新的N3 UPF，SMF根据终端设备的位置等信息选择N3 UPF2。
步骤1104，SMF向N3 UPF2发送N4消息，创建N3 UPF2与锚点UPF之间的N9隧道。对不需要激活的PDU会话，SMF仅创建N9隧道及N3隧道的上行隧道。对需要激活的PDU会话，SMF创建N9隧道和N3上下行隧道。若该业务请求由网络触发，对需要激活的PDU会话，该N4消息还创建N3 UPF1到N3 UPF2的转发隧道。
步骤1105，N3 UPF2向SMF发送N4响应消息。
步骤1106，SMF向锚点UPF发送N4消息，更新PDU会话的用户面路径(N9隧道)。
步骤1107，锚点UPF向SMF发送N4响应消息。
步骤1108，若该业务请求由网络触发，SMF发送N4消息给N3 UPF1，创建N3 UPF1与N3 UPF2间的转发隧道。同时，该N4消息删除N3 UPF1到锚点UPF间的N9隧道。
步骤1109，N3 UPF1给SMF发送N4响应消息。
步骤1110，若N3 UPF发生了改变，SMF根据新N3 UPF(如图11中的N3 UPF2)的服务范围确定PDU会话的新位置上报粒度。
SMF发送更新会话响应消息给AMF，该消息中包括了PDU会话的新位置上报粒度。对所有待激活的PDU会话，该消息中还包括SM N2信息，SM N2信息中包括N3 UPF2的N3上行隧道信息。
对那些用户面路径变更了(即N3 UPF切换了)，但不需要激活的PDU会话，不需要执行步骤1112～1118。
步骤1111，AMF向RAN发送N2消息，该N2消息中包括SMF发送的SM N2消息。
步骤1112，RAN与终端设备之间进行RRC重配置，为刚刚激活的PDU会话PDU会话分配资源。上行数据将从RAN发送到N3 UPF2。
步骤1113，RAN给AMF发送N2消息应答，该N2消息应答携带SM N2信息，SM N2消息中包括RAN的N3下行隧道信息。
步骤1114，AMF向SMF发送N11消息，该N11消息包括RAN发送的SM N2信息。
步骤1115，SMF更新会话策略。
步骤1116，SMF向N3 UPF2发送N4消息，更新N3 UPF2的N3隧道。下行数据从N3 UPF2发送给RAN，并且下行转发数据从N3 UPF1经过N3 UPF2发送给RAN。
步骤1117，N3 UPF1在发送完最后一个缓存数据后发送结束标识给SMF。SMF发送删除转发隧道请求N4消息给N3 UPF1和N3 UPF2，指示N3 UPF1和N3 UPF2删除转发隧道。或者，SMF在本地设置一个转发定时器，当转发定时器到时后，SMF发送删除转发隧道请求N4消息给N3 UPF1和N3 UPF2，指示N3 UPF1和N3 UPF2删除转发隧道。在N3 UPF1和N3 UPF2接收到删除转发隧道请求后，删除转发隧道，N3 UPF1和N3 UPF2分别向SMF发送删除转发隧道应答，通知SMF完成转发隧道的删除。其中，删除转发隧道请求和删除转发隧道应答可以携带在N4消息或者其它消息中，在此不做限定。
步骤1118，SMF发送N11响应消息给AMF。步骤1118可以在步骤1117之前执行。
如图12所示，为PDU会话的重建的流程，该流程是以在图7所示的通信系统中基于SSC模式2或SSC模式3的PDU会话为例的，当终端设备移动后，SMF根据终端设备移动后的位置信息和PDU会话的会话服务区(又称PSSA)，具体PSSA的确定方式参见本申请实施例中如图2a所示的发起用户面路径重建中的确定会话服务区的方式，在此不再赘述。具体的PDU会话的重建流程包括：
步骤1200，在终端设备移动之前，终端设备的PDU会话的锚点是锚点UPF1。终端设备移动之后可能会触发重新注册流程或者切换流程等流程，并且，终端设备在空闲态或者连接态都可能发起业务请求(Service request，SR)过程触发PDU会话的激活。
步骤1201，AMF在重新注册流程或者切换流程中根据该终端设备的位置上报粒度，判断是否需要将终端设备的位置信息通知给SMF。若AMF判断某个终端设备的PDU会话的位置上报粒度后决定要将终端设备的位置信息通知SMF，AMF给SMF发送终端设备的位置信息。该终端设备的位置信息可以和其他N11消息一起发送给SMF。
步骤1202，SMF判断终端设备的位置信息是否在PDU会话的PSSA内，来决定是否要发起PDU会话的重建流程。若SMF确定指示终端设备发起PDU会话的重建流程，则执行步骤1203。PDU会话的重建流程指的是建立一个到同一数据网络的PDU会话。
步骤1203，SMF向终端设备发送NAS消息，指示UE发起PDU会话的重建。该NAS消息是经过AMF发送的。
步骤1204，终端设备在接收到SMF发送的NAS消息后发起PDU会话的重建。新PDU会话的锚点是锚点UPF2。针对SSC模式2的PDU会话，终端设备在重建PDU会话前先释放原PDU会话。针对SSC模式3的PDU会话，终端设备在建立完新PDU会话后根据需要释放原PDU会话。
基于同一构思，本申请实施例中还提供了如图13a和如图14a所示的发起用户面路径重建的装置，由于本申请实施例中的如图13a所示的装置对应的方法为本申请实施例如图2a和如图2b所示的发起用户面路径重建的方法，因此本申请实施例如图13a所示的装置的实施可以参见如图2a和如图2b所示的发起用户面路径重建的方法的实施，重复之处不再赘述。由于本申请实施例中的如图14a所示的装置对应的方法为本申请实施例如图4a和如图4b所示的发起用户面路径重建的方法，因此本申请实施例如图14a所示的装置的实施可以参见如图4a和如图4b所示的发起用户面路径重建的方法的实施，重复之处不再赘述。
如图13a所示，本申请实施例的发起用户面路径重建的装置，包括：处理模块1310a、接收模块1320a；其中，
处理模块1310a用于根据终端设备的第一位置信息，确定终端设备的当前会话所属的会话服务区，其中，第一位置信息为会话管理功能实体在当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的终端设备的位置信息，第一用户面功能实体用于在切换到第二用户面功能实体之前为终端设备的会话提供服务，第二用户面功能实体用于为当前会话提供服务；
接收模块1320a用于接收移动性管理功能实体发送的终端设备的第二位置信息；
处理模块1310a还用于在确定通过接收模块接收到的第二位置信息不在会话服务区内时，则指示终端设备发起针对当前会话的重建流程，或者发起切换流程，切换流程用于将为当前会话服务的用户面功能实体切换到目标用户面功能实体，目标用户面功能实体用于在完成切换流程后为终端设备的会话提供服务。
示例的，会话服务区包括为当前会话提供服务的用户面功能实体的服务区域。
示例的，会话服务区包括部分为当前会话提供服务的用户面功能实体的服务区域时，处理模块1310a用于：在确定第二位置信息不在会话服务区内且不在为当前会话提供服务的用户面功能实体的服务区域内时，则指示终端设备发起针对当前会话的重建流程、或者发起切换流程。
具体的，处理模块1310a可基于下列实现方式确定会话服务区：
以终端设备的第一位置信息为中心确定会话服务区的中心位置；并确定会话服务区的大小。
示例的，处理模块1310a可基于下列方式确定会话服务区的大小：
根据为当前会话提供服务的用户面功能实体的服务区域和/或终端设备的移动模式确定会话服务区的大小；其中，移动模式包括终端设备的移动范围、终端设备的移动速度、终端设备的移动轨迹中的至少一项。
在一种可能的实现方式中，处理模块1310a在确定会话服务区之后，根据会话服务区，确定终端设备的位置上报粒度，位置上报粒度用于指示移动性管理功能实体向会话管理功能实体上报终端设备的位置信息的范围；该装置中的发送模块1330向移动性管理功能实体发送处理模块确定的位置上报粒度。
具体的，处理模块1310a在根据会话服务区，确定位置上报粒度之前，获取至少一个位置上报需求，至少一个位置上报需求中包括至少一个区域信息，至少一个区域信息用于 指示需要终端设备上报位置信息的范围；然后，根据会话服务区和至少一个区域信息，确定位置上报粒度，位置上报粒度为会话服务区与至少一个区域信息的交集。
应理解的是，上述单元的具体划分仅作为举例，不做为本申请的限定。
当如图13a所示的发起用户面路径重建的装置作为一个实体设备单独存在时，其硬件结构可以如图13b所示的会话管理功能设备，其中图13a中所示的处理模块1310a可通过处理器1310b实现，接收模块1320a和发送模块1330a可通过通信接口1320b实现，此外，如图13b所示的会话管理功能设备还包括存储器1330b，其中存储器1330b用于存储用于存储软件程序以及通信接口1320b收发的数据信息等，处理器1310b用于读取存储器1330b中存储的软件程序和数据并实现本申请实施例如图2a或如图2b所示的方法。
其中，处理器1310b可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关操作，以实现本申请实施例所提供的技术方案。
应注意，尽管图13b所示的会话管理功能设备仅仅示出了处理器1310b、通信接口1320b和存储器1330b，但是在具体实现过程中，本领域的技术人员应当明白，该会话管理功能设备还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，该会话管理功能设备还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，该会话管理功能设备也可仅仅包含实现本申请实施例所必须的器件或模块，而不必包含图13b中所示的全部器件。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，上述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，上述的存储介质可为磁盘、光盘、只读存储记忆体(ROM：Read-Only Memory)或随机存储记忆体(RAM：Random Access Memory)等。
如图14a所示，本申请实施例发起用户面路径重建的装置，包括：处理模块1410a、接收模块1420a；其中，
接收模块1420a用于接收到移动性管理功能实体发送的终端设备的第一位置信息；
处理模块1410a用于在确定接收模块1420a接收到的第一位置信息不在第一服务区域内，则根据第一位置信息，选择第一目标用户面功能实体，并发起针对当前会话的用户面路径的重建流程；
其中，第一服务区域为第一用户面功能实体的服务区域，第一用户面功能实体用于为终端设备的当前会话提供服务，第一目标用户面功能实体在重建后的用户面路径中为终端设备的会话提供服务。
在一种可能的实现方式中，处理模块1410a在接收模块1420a接收移动性管理功能实体发送的终端设备的第一位置信息之前，根据第一服务区域，确定终端设备的位置上报粒度，其中位置上报粒度用于指示移动性管理功能实体向会话管理功能实体上报终端设备的位置信息的范围；该装置中的发送模块1430a，用于向移动性管理实体发送位置上报粒度。
示例的，处理模块1410a在根据第一服务区域，确定位置上报粒度之前，根据终端设备的第二位置信息，确定当前会话所属的会话服务区，其中，第二位置信息为会话管理功 能实体在当前终端设备的会话建立过程中、或在切换第二用户面功能实体到第三用户面功能实体的过程中接收到的终端设备的位置信息，第二用户面功能实体用于在切换到第三用户面功能实体之前为终端设备的会话提供服务，第三用户面功能实体用于为当前会话提供服务；并根据第一服务区域和会话服务区，确定终端设备的位置上报粒度，其中位置上报粒度不大于第一服务区域和会话服务区的交集区域。
示例的处理模块1410a在根据第一服务区域，确定位置上报粒度之前，获取至少一个位置上报需求，至少一个位置上报需求中包括至少一个区域信息，至少一个区域信息用于指示需要终端设备上报位置信息的范围；并根据第一服务区域和至少一个区域信息，确定位置上报粒度，位置上报粒度为第一服务区域与至少一个区域信息的交集。
在一种可能的实现方式中，处理模块1410a在发起针对当前会话的用户面路径的重建之后，若确定第一用户面功能实体中有缓存数据，则创建转发隧道，转发隧道为第一目标用户面功能实体与第一用户面功能实体之间的隧道，使得第一用户面功能实体通过转发隧道将缓存数据发送到第一目标用户面功能实体。
此外，示例的处理模块1410a在创建转发隧道之后，在确定接收模块接收到第一用户面功能实体发送的完成缓存数据发送的标识后，删除转发隧道；或者，在创建转发隧道后启动转发定时器，在转发定时器达到预设时长时后删除转发隧道。
应理解的是，上述单元的具体划分仅作为举例，不做为本申请的限定。
当如图14a所示的发起用户面路径重建的装置作为一个实体设备单独存在时，其硬件结构可以如图14b所示的会话管理功能设备，其中图14a中所示的处理模块1410a可通过处理器1410b实现，接收模块1420a和发送模块1430a可通过通信接口1420b实现，此外，如图14b所示的会话管理功能设备还包括存储器1430b，其中存储器1430b用于存储用于存储软件程序以及通信接口1420b收发的数据信息等，处理器1410b用于读取存储器1430b中存储的软件程序和数据并实现本申请实施例如图2a或如图2b所示的方法。
其中，处理器1410b可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关操作，以实现本申请实施例所提供的技术方案。
应注意，尽管图14b所示的会话管理功能设备仅仅示出了处理器1410b、通信接口1420b和存储器1430b，但是在具体实现过程中，本领域的技术人员应当明白，该会话管理功能设备还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，该会话管理功能设备还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，该会话管理功能设备也可仅仅包含实现本申请实施例所必须的器件或模块，而不必包含图14b中所示的全部器件。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，上述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，上述的存储介质可为磁盘、光盘、只读存储记忆体(ROM：Read-Only Memory)或随机存储记忆体(RAM：Random Access Memory)等。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。 当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (31)

  1. 一种发起用户面路径重建的方法，其特征在于，包括：
    会话管理功能实体根据终端设备的第一位置信息，确定所述终端设备的当前会话所属的会话服务区，其中，所述第一位置信息为所述会话管理功能实体在所述当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的所述终端设备的位置信息，所述第一用户面功能实体用于在切换到所述第二用户面功能实体之前为所述终端设备的会话提供服务，所述第二用户面功能实体用于为所述当前会话提供服务；
    所述会话管理功能实体在接收到移动性管理功能实体发送的所述终端设备的第二位置信息后，若确定所述第二位置信息不在所述会话服务区内，则指示所述终端设备发起针对所述当前会话的重建流程，或者发起切换流程，所述切换流程用于将为所述当前会话服务的用户面功能实体切换到目标用户面功能实体，所述目标用户面功能实体用于在完成所述切换流程后为所述终端设备的会话提供服务。
  2. 如权利要求1所述的方法，其特征在于，所述会话服务区包括为所述当前会话提供服务的用户面功能实体的服务区域。
  3. 如权利要求1所述的方法，其特征在于，所述会话服务区包括部分为所述当前会话提供服务的用户面功能实体的服务区域时，所述会话管理功能实体在接收到所述移动性管理功能实体发送的所述终端设备的第二位置信息之后，在指示所述终端设备发起针对所述当前会话的重建流程、或者发起所述切换流程之前，还包括：
    所述会话管理功能实体确定所述第二位置信息不在为所述当前会话提供服务的用户面功能实体的服务区域内。
  4. 如权利要求1至3任一所述的方法，其特征在于，所述会话管理功能实体根据所述终端设备的第一位置信息，确定所述会话服务区，包括：
    所述会话管理功能实体以所述终端设备的第一位置信息为中心确定所述会话服务区的中心位置；
    所述会话管理功能实体确定所述会话服务区的大小。
  5. 如权利要求4所述的方法，其特征在于，所述会话管理功能实体确定所述会话服务区的大小，包括：
    所述会话管理功能实体根据为所述当前会话提供服务的用户面功能实体的服务区域和/或所述终端设备的移动模式确定所述会话服务区的大小；
    其中，所述移动模式包括所述终端设备的移动范围、所述终端设备的移动速度、所述终端设备的移动轨迹中的至少一项。
  6. 如权利要求1至5任一所述的方法，其特征在于，所述会话管理功能实体确定所述会话服务区之后，还包括：
    所述会话管理功能实体根据所述会话服务区，确定所述终端设备的位置上报粒度，所述位置上报粒度用于指示所述移动性管理功能实体向所述会话管理功能实体上报所述终端设备的位置信息的范围；
    所述会话管理功能实体向所述移动性管理功能实体发送所述位置上报粒度。
  7. 如权利要求6所述的方法，其特征在于，所述会话管理功能实体根据所述会话服务区，确定所述位置上报粒度之前，还包括：
    所述会话管理功能实体获取至少一个位置上报需求，所述至少一个位置上报需求中包括至少一个区域信息，所述至少一个区域信息用于指示需要终端设备上报位置信息的范围；
    相应的，所述会话管理功能实体根据所述会话服务区，确定所述位置上报粒度，包括：
    所述会话管理功能实体根据所述会话服务区和所述至少一个区域信息，确定所述位置上报粒度，所述位置上报粒度为所述会话服务区与所述至少一个区域信息的交集。
  8. 一种用户面路径重建的方法，其特征在于，包括：
    会话管理功能实体接收到移动性管理功能实体发送的终端设备的第一位置信息；
    所述会话管理功能实体若确定所述第一位置信息不在第一服务区域内，则根据所述第一位置信息，选择第一目标用户面功能实体，所述第一服务区域为第一用户面功能实体的服务区域，所述第一用户面功能实体用于为所述终端设备的当前会话提供服务；
    所述会话管理功能实体发起针对所述当前会话的用户面路径的重建流程，所述第一目标用户面功能实体在重建后的用户面路径中为所述终端设备的会话提供服务。
  9. 如权利要求8所述的方法，其特征在于，还包括：
    所述会话管理功能实体根据所述第一服务区域，确定所述终端设备的位置上报粒度，其中所述位置上报粒度用于指示所述移动性管理功能实体向所述会话管理功能实体上报所述终端设备的位置信息的范围；
    所述会话管理功能实体向所述移动性管理实体发送所述位置上报粒度。
  10. 如权利要求9所述的方法，其特征在于，还包括：
    所述会话管理功能实体根据终端设备的第二位置信息，确定所述当前会话所属的会话服务区，其中，所述第二位置信息为所述会话管理功能实体在当前所述终端设备的会话建立过程中、或在切换第二用户面功能实体到第三用户面功能实体的过程中接收到的所述终端设备的位置信息，所述第二用户面功能实体用于在切换到所述第三用户面功能实体之前为所述终端设备的会话提供服务，所述第三用户面功能实体用于为所述当前会话提供服务；
    相应的，所述会话管理功能实体根据所述第一服务区域，确定所述终端设备的位置上报粒度，包括：
    所述会话管理功能实体根据所述第一服务区域和所述会话服务区，确定所述终端设备的位置上报粒度，其中所述位置上报粒度不大于所述第一服务区域和所述会话服务区的交集区域。
  11. 如权利要求9所述的方法，其特征在于，还包括：
    所述会话管理功能实体获取至少一个位置上报需求，所述至少一个位置上报需求中包括至少一个区域信息，所述至少一个区域信息用于指示需要所述终端设备上报位置信息的范围；
    相应的，所述会话管理功能实体根据所述第一服务区域，确定所述位置上报粒度，包括：
    所述会话管理功能实体根据所述第一服务区域和所述至少一个区域信息，确定所述位置上报粒度，所述位置上报粒度为所述第一服务区域与所述至少一个区域信息的交集。
  12. 如权利要求8至11任一所述的方法，其特征在于，还包括：
    所述会话管理功能实体在确定所述第一用户面功能实体中有缓存数据后，创建转发隧道，所述转发隧道为所述第一目标用户面功能实体与所述第一用户面功能实体之间的隧道，使得所述第一用户面功能实体通过所述转发隧道将所述缓存数据发送到所述第一目标用户面功能实体。
  13. 如权利要求12所述的方法，其特征在于，还包括：
    所述会话管理功能实体在收到所述第一用户面功能实体发送的完成缓存数据发送的标识后，删除所述转发隧道；或者，所述会话管理功能实体在创建所述转发隧道后启动转发定时器，在所述转发定时器达到预设时长时后删除所述转发隧道。
  14. 一种发起用户面路径重建的装置，其特征在于，包括：
    处理模块，用于根据终端设备的第一位置信息，确定所述终端设备的当前会话所属的会话服务区，其中，所述第一位置信息为所述装置在所述当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的所述终端设备的位置信息，所述第一用户面功能实体用于在切换到所述第二用户面功能实体之前为所述终端设备的会话提供服务，所述第二用户面功能实体用于为所述当前会话提供服务；
    接收模块，用于接收移动性管理功能实体发送的所述终端设备的第二位置信息；
    所述处理模块，还用于在确定通过所述接收模块接收到的所述第二位置信息不在所述会话服务区内时，则指示所述终端设备发起针对所述当前会话的重建流程，或者发起切换流程，所述切换流程用于将为所述当前会话服务的用户面功能实体切换到目标用户面功能实体，所述目标用户面功能实体用于在完成所述切换流程后为所述终端设备的会话提供服务。
  15. 如权利要求14所述的装置，其特征在于，所述会话服务区包括为所述当前会话提供服务的用户面功能实体的服务区域。
  16. 如权利要求15所述的装置，其特征在于，所述会话服务区包括部分为所述当前会话提供服务的用户面功能实体的服务区域时，所述处理模块，还用于：
    在指示所述终端设备发起针对所述当前会话的重建流程、或者发起所述切换流程之前，确定所述第二位置信息不在为所述当前会话提供服务的用户面功能实体的服务区域内。
  17. 如权利要求15至16任一所述的装置，其特征在于，所述处理模块根据所述终端设备的第一位置信息，确定所述会话服务区，具体用于：
    以所述终端设备的第一位置信息为中心确定所述会话服务区的中心位置；并确定所述会话服务区的大小。
  18. 如权利要求17所述的装置，其特征在于，所述处理模块确定所述会话服务区的大小，具体用于：
    根据为所述当前会话提供服务的用户面功能实体的服务区域和/或所述终端设备的移动模式确定所述会话服务区的大小；其中，所述移动模式包括所述终端设备的移动范围、所述终端设备的移动速度、所述终端设备的移动轨迹中的至少一项。
  19. 如权利要求15至18任一所述的装置，其特征在于，所述处理模块，还用于：
    在确定所述会话服务区之后，根据所述会话服务区，确定所述终端设备的位置上报粒 度，所述位置上报粒度用于指示所述移动性管理功能实体向所述装置上报所述终端设备的位置信息的范围；
    所述装置中的发送模块，用于向所述移动性管理功能实体发送所述处理模块确定的所述位置上报粒度。
  20. 如权利要求19所述的装置，其特征在于，所述处理模块，还用于：
    在根据所述会话服务区，确定所述位置上报粒度之前，获取至少一个位置上报需求，所述至少一个位置上报需求中包括至少一个区域信息，所述至少一个区域信息用于指示需要终端设备上报位置信息的范围；
    相应的，所述处理模块根据所述会话服务区，确定所述位置上报粒度，具体用于：
    根据所述会话服务区和所述至少一个区域信息，确定所述位置上报粒度，所述位置上报粒度为所述会话服务区与所述至少一个区域信息的交集。
  21. 一种用户面路径重建的装置，其特征在于，包括：
    接收模块，用于接收到移动性管理功能实体发送的终端设备的第一位置信息；
    处理模块，用于在确定所述接收模块接收到的所述第一位置信息不在第一服务区域内，则根据所述第一位置信息，选择第一目标用户面功能实体，并发起针对所述当前会话的用户面路径的重建流程；
    其中，所述第一服务区域为第一用户面功能实体的服务区域，所述第一用户面功能实体用于为所述终端设备的当前会话提供服务，所述第一目标用户面功能实体在重建后的用户面路径中为所述终端设备的会话提供服务。
  22. 如权利要求21所述的装置，其特征在于，所述处理模块，还用于：
    根据所述第一服务区域，确定所述终端设备的位置上报粒度，其中所述位置上报粒度用于指示所述移动性管理功能实体向所述装置上报所述终端设备的位置信息的范围；
    所述装置中的发送模块，用于向所述移动性管理实体发送所述位置上报粒度。
  23. 如权利要求22所述的装置，其特征在于，所述处理模块，还用于：
    根据终端设备的第二位置信息，确定所述当前会话所属的会话服务区，其中，所述第二位置信息为所述装置在当前所述终端设备的会话建立过程中、或在切换第二用户面功能实体到第三用户面功能实体的过程中接收到的所述终端设备的位置信息，所述第二用户面功能实体用于在切换到所述第三用户面功能实体之前为所述终端设备的会话提供服务，所述第三用户面功能实体用于为所述当前会话提供服务；
    相应的，所述处理模块根据所述第一服务区域，确定所述位置上报粒度，具体用于：
    根据所述第一服务区域和所述会话服务区，确定所述终端设备的位置上报粒度，其中所述位置上报粒度不大于所述第一服务区域和所述会话服务区的交集区域。
  24. 如权利要求23所述的装置，其特征在于，所述处理模块，还用于：
    获取至少一个位置上报需求，所述至少一个位置上报需求中包括至少一个区域信息，所述至少一个区域信息用于指示需要所述终端设备上报位置信息的范围；
    相应的，所述处理模块根据所述第一服务区域，确定所述位置上报粒度，具体用于：
    根据所述第一服务区域和所述至少一个区域信息，确定所述位置上报粒度，所述位置上报粒度为所述第一服务区域与所述至少一个区域信息的交集。
  25. 如权利要求21至24任一所述的装置，其特征在于，所述处理模块，还用于：
    若确定所述第一用户面功能实体中有缓存数据，则创建转发隧道，所述转发隧道为所述第一目标用户面功能实体与所述第一用户面功能实体之间的隧道，使得所述第一用户面功能实体通过所述转发隧道将所述缓存数据发送到所述第一目标用户面功能实体。
  26. 如权利要求25所述的装置，其特征在于，所述处理模块，还用于：
    在确定所述接收模块接收到所述第一用户面功能实体发送的完成缓存数据发送的标识后，删除所述转发隧道；或者，在创建所述转发隧道后启动转发定时器，在所述转发定时器达到预设时长时后删除所述转发隧道。
  27. 一种通信系统，其特征在于，包括会话管理功能实体和移动性管理功能实体；其中：
    所述会话管理功能实体，用于根据终端设备的第一位置信息，确定所述终端设备的当前会话所属的会话服务区；并在接收到移动性管理功能实体发送的所述终端设备的第二位置信息后，若确定所述第二位置信息不在所述会话服务区内，则指示所述终端设备发起针对所述当前会话的重建流程，或者发起切换流程，所述切换流程用于将为所述当前会话服务的用户面功能实体切换到目标用户面功能实体，所述目标用户面功能实体用于在完成所述切换流程后为所述终端设备的会话提供服务；
    其中，所述第一位置信息为所述会话管理功能实体在所述当前会话建立过程中、或在切换第一用户面功能实体到第二用户面功能实体的过程中接收到的所述终端设备的位置信息，所述第一用户面功能实体用于在切换到所述第二用户面功能实体之前为所述终端设备的会话提供服务，所述第二用户面功能实体用于为所述当前会话提供服务；
    所述移动性管理功能实体，用于向所述会话管理功能实体发送所述终端设备的第二位置信息。
  28. 如权利要求27所述的通信系统，其特征在于，所述会话管理功能实体，还用于根据所述会话服务区，确定所述终端设备的位置上报粒度，并向所述移动性管理功能实体发送所述位置上报粒度，所述位置上报粒度用于指示所述移动性管理功能实体向所述会话管理功能实体上报所述终端设备的位置信息的范围；
    所述移动性管理功能实体，还用于接收所述位置上报粒度，并确定所述终端设备的第二位置信息不在所述位置上报粒度内。
  29. 一种通信系统，其特征在于，包括会话管理功能实体和移动性管理功能实体；其中，所述移动性管理功能实体，用于向所述会话管理功能实体发送终端设备的第一位置信息；
    所述会话管理功能实体，用于在若确定所述第一位置信息不在第一服务区域内，则根据所述第一位置信息，选择第一目标用户面功能实体，并发起针对所述当前会话的用户面路径的重建流程；
    其中，所述第一服务区域为第一用户面功能实体的服务区域，所述第一用户面功能实体用于为所述终端设备的当前会话提供服务，所述第一目标用户面功能实体在重建后的用户面路径中为所述终端设备的会话提供服务。
  30. 如权利要求29所述的通信系统，其特征在于，所述会话管理功能实体，还用于 根据所述第一服务区域，确定所述终端设备的位置上报粒度，并向所述移动性管理功能实体发送所述位置上报粒度；其中所述位置上报粒度用于指示所述移动性管理功能实体向所述会话管理功能实体上报所述终端设备的位置信息的范围；
    所述移动性管理功能实体，还用于接收所述位置上报粒度，并确定所述终端设备的第一位置信息不在所述位置上报粒度内。
  31. 一种会话管理功能实体，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述会话管理功能实体运行时，所述处理器执行所述存储器存储的该计算机执行指令，以使所述会话管理功能实体执行如权利要求8-13任一项所述的用户面路径重建的方法。
PCT/CN2018/077025 2017-03-17 2018-02-23 一种发起用户面路径重建的方法、装置及通信系统 WO2018166336A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
KR1020197016274A KR102231693B1 (ko) 2017-03-17 2018-02-23 사용자 평면 경로 재구축을 개시하는 방법 및 장치 그리고 통신 시스템
BR112019014020-4A BR112019014020A2 (pt) 2017-03-17 2018-02-23 Método e aparelho para iniciar restabelecimento de caminho de plano de usuário e sistema de comunicações
JP2019532789A JP6987866B2 (ja) 2017-03-17 2018-02-23 ユーザープレーン経路再確立を開始するための方法および装置ならびに通信システム
EP21192955.9A EP3979707B1 (en) 2017-03-17 2018-02-23 Method for initiating user plane path modification in a communications system
EP18767026.0A EP3598800B1 (en) 2017-03-17 2018-02-23 Method and apparatus for initiating user-plane path modification, and communication system
US16/415,148 US11224085B2 (en) 2017-03-17 2019-05-17 Method and apparatus for initiating user plane path re-establishment and communications system
US17/538,734 US11805567B2 (en) 2017-03-17 2021-11-30 Method and apparatus for initiating user plane path re-establishment and communications system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710161100.6 2017-03-17
CN201710161100.6A CN108696822B (zh) 2017-03-17 2017-03-17 一种发起用户面路径重建的方法、装置及通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/415,148 Continuation US11224085B2 (en) 2017-03-17 2019-05-17 Method and apparatus for initiating user plane path re-establishment and communications system

Publications (1)

Publication Number Publication Date
WO2018166336A1 true WO2018166336A1 (zh) 2018-09-20

Family

ID=63521714

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077025 WO2018166336A1 (zh) 2017-03-17 2018-02-23 一种发起用户面路径重建的方法、装置及通信系统

Country Status (7)

Country Link
US (2) US11224085B2 (zh)
EP (2) EP3979707B1 (zh)
JP (1) JP6987866B2 (zh)
KR (1) KR102231693B1 (zh)
CN (3) CN110290471B (zh)
BR (1) BR112019014020A2 (zh)
WO (1) WO2018166336A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113676986A (zh) * 2021-07-21 2021-11-19 武汉虹旭信息技术有限责任公司 获取终端位置的方法及系统

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102293669B1 (ko) * 2017-05-08 2021-08-25 삼성전자 주식회사 5g 셀룰러망의 세션 연속성 지원 방안
US20190007992A1 (en) * 2017-07-03 2019-01-03 Electronics And Telecommunications Research Institute Network triggered service request method and user equipment (ue) triggered service request method
CN111200849B (zh) * 2018-11-19 2022-08-09 大唐移动通信设备有限公司 一种用户路由更新方法及设备
CN111328115B (zh) 2018-12-14 2022-03-11 大唐移动通信设备有限公司 一种数据发送方法及设备
CN111757340B (zh) * 2019-03-28 2023-04-18 华为技术有限公司 一种确定服务区域的方法、装置及系统
CN111757312A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种会话的处理方法及装置
CN112449395B (zh) * 2019-08-28 2022-09-02 中国联合网络通信集团有限公司 一种数据传输方法、核心网设备和amf
CN112449394B (zh) * 2019-08-28 2022-09-16 中国联合网络通信集团有限公司 一种数据传输方法和核心网设备
CN112584437B (zh) * 2019-09-30 2023-03-28 中国移动通信有限公司研究院 一种数据分流方法及装置
CN112584327B (zh) * 2019-09-30 2022-04-05 华为技术有限公司 一种更新用户面路径的方法、装置及系统
CN112654070B (zh) * 2019-10-12 2022-02-08 大唐移动通信设备有限公司 用户终端间的通信方法、装置、设备及存储介质
CN111277470B (zh) * 2020-02-19 2022-07-26 联想(北京)有限公司 一种用户面功能切换方法、装置、系统和存储介质
CN112291752B (zh) * 2020-11-16 2022-08-12 中国联合网络通信集团有限公司 一种网络注册方法及装置
US11451954B1 (en) 2021-02-03 2022-09-20 Sprint Communications Company L.P. Wireless communication service delivery using multiple data network names (DNNs)
US20220408353A1 (en) * 2021-06-18 2022-12-22 Commscope Technologies Llc User plane function selection and hosting for real-time applications
WO2023043286A1 (ko) * 2021-09-17 2023-03-23 엘지전자 주식회사 무선 통신 시스템에서 mbs를 제공하는 방법 및 장치
CN117042069B (zh) * 2023-09-28 2024-02-27 新华三技术有限公司 应用于5g核心网中的路径切换方法、装置及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101094509A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 演进网络及用户设备锚点迁移的方法
CN101563887A (zh) * 2006-10-17 2009-10-21 松下电器产业株式会社 具有重叠池区的移动通信系统中的用户面实体选择
US20150181550A1 (en) * 2013-12-23 2015-06-25 Cellco Partnership D/B/A Verizon Wireless Processing of a coarse location request for a mobile device

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039506B (zh) * 2006-03-15 2011-02-02 华为技术有限公司 一种移动管理实体/用户面实体迁移方法
EP1914930A1 (en) * 2006-10-17 2008-04-23 Matsushita Electric Industrial Co., Ltd. User plane entity selection in a mobile communication system having overlapping pool areas
EP2204066B1 (en) * 2007-10-25 2017-06-28 Cisco Technology, Inc. Interworking gateway for mobile nodes
KR101521886B1 (ko) * 2009-01-23 2015-05-28 삼성전자주식회사 이동통신 시스템에서 지티피 처리를 위한 장치 및 방법
US8971845B2 (en) * 2013-02-26 2015-03-03 Cisco Technology, Inc. Systems, methods and media for location reporting at a charging area level granularity
CN106102106B (zh) * 2016-06-20 2020-03-24 电信科学技术研究院 一种终端接入的方法、装置及网络架构
EP3490297A4 (en) * 2016-08-22 2019-06-12 Samsung Electronics Co., Ltd. METHOD AND APPARATUS FOR OPERATING A WIRELESS COMMUNICATION SYSTEM WITH SEPARATE MOBILITY MANAGEMENT AND SESSION MANAGEMENT
CN108617032B (zh) * 2017-01-09 2019-12-27 电信科学技术研究院 一种ue空闲态处理方法、mm功能实体及sm功能实体
US10448239B2 (en) * 2017-02-06 2019-10-15 Qualcomm Incorporated Mechanism to enable optimized user plane anchoring for minimization of user plane relocation due to user equipment mobility

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101094509A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 演进网络及用户设备锚点迁移的方法
CN101563887A (zh) * 2006-10-17 2009-10-21 松下电器产业株式会社 具有重叠池区的移动通信系统中的用户面实体选择
US20150181550A1 (en) * 2013-12-23 2015-06-25 Cellco Partnership D/B/A Verizon Wireless Processing of a coarse location request for a mobile device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Functionalities of UPF and SMF, S 2-170208", 3GPP SA WG2 MEETING #118BIS, 17 February 2017 (2017-02-17), XP051216397 *
HUAWEI ET AL.: "Selection of SMF, S 2-170210", 3GPP SAWG2 MEETING #118BIS, 17 February 2017 (2017-02-17), XP051216399 *
SAMSUNG: "TS 23.502: Xn Based Inter NG RAN Handover Procedures, S 2-171028", 3GPP SA WG2 MEETING #119, 17 February 2017 (2017-02-17), XP051234534 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113676986A (zh) * 2021-07-21 2021-11-19 武汉虹旭信息技术有限责任公司 获取终端位置的方法及系统
CN113676986B (zh) * 2021-07-21 2024-04-09 武汉虹旭信息技术有限责任公司 获取终端位置的方法及系统

Also Published As

Publication number Publication date
JP2020502928A (ja) 2020-01-23
CN110278529A (zh) 2019-09-24
JP6987866B2 (ja) 2022-01-05
CN108696822A (zh) 2018-10-23
KR20190077514A (ko) 2019-07-03
US20190274181A1 (en) 2019-09-05
CN108696822B (zh) 2019-08-23
EP3979707A1 (en) 2022-04-06
EP3598800A1 (en) 2020-01-22
EP3598800B1 (en) 2021-10-27
US11805567B2 (en) 2023-10-31
US11224085B2 (en) 2022-01-11
KR102231693B1 (ko) 2021-03-23
CN110290471B (zh) 2020-06-19
EP3979707B1 (en) 2023-10-25
CN110278529B (zh) 2021-09-14
US20220086942A1 (en) 2022-03-17
BR112019014020A2 (pt) 2020-02-11
EP3598800A4 (en) 2020-02-26
CN110290471A (zh) 2019-09-27

Similar Documents

Publication Publication Date Title
WO2018166336A1 (zh) 一种发起用户面路径重建的方法、装置及通信系统
JP2020502928A5 (zh)
KR102149263B1 (ko) 세션 관리 방법 및 세션 관리 기능 네트워크 엘리먼트
WO2018205153A1 (zh) 一种会话管理方法、终端及系统
JP6222678B2 (ja) ネットワークハンドオーバ方法、ネットワークハンドオーバデバイス、およびネットワークハンドオーバシステム
WO2020156116A1 (zh) 上下文存储方法及装置
WO2019095119A1 (zh) 切换网络的方法、网络设备和终端设备
CN110419249A (zh) 一种移动性管理的处理方法及装置
JP2021516499A (ja) 異なるアクセスネットワーク間で移動体通信装置のハンドオーバを実行する方法およびシステム
US20160337915A1 (en) Switching control method, apparatus, and wireless communications network
CN110505662B (zh) 一种策略控制方法、装置及系统
CN107889180B (zh) 一种异系统小区重选的方法、终端及网络侧设备
WO2018205775A1 (zh) 缓存数据的方法和会话管理功能实体
WO2020200293A1 (zh) 一种终端定位方法及装置
WO2018010127A1 (zh) 无线通信的方法、装置、接入网实体和终端设备
WO2019034058A1 (zh) 消息发送、信息获取方法、装置、终端及接入及移动性管理实体
CN109831810B (zh) 一种建立无线接入承载的方法和装置
WO2019024108A1 (zh) 通信方法、网络设备和终端设备
CN113973076A (zh) 一种多播切换方法及装置
JP6828053B2 (ja) 通信方法、コアネットワーク装置、アクセスネットワーク装置、端末装置と通信システム
CN112822789A (zh) 非激活态终端的重定向方法、电子设备及计算机可读介质
CN112153756B (zh) 一种基于隧道建立服务的数据处理方法和通信设备
KR20170114968A (ko) 이동성 레벨을 관리하는 통신 방법 및 이를 수행하는 통신 장치
CN109963344A (zh) 下行nas信令的处理方法及相关设备

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20197016274

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019532789

Country of ref document: JP

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019014020

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2018767026

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2018767026

Country of ref document: EP

Effective date: 20191017

ENP Entry into the national phase

Ref document number: 112019014020

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190705