WO2019137125A1 - 会话管理方法、设备及*** - Google Patents

会话管理方法、设备及*** Download PDF

Info

Publication number
WO2019137125A1
WO2019137125A1 PCT/CN2018/119736 CN2018119736W WO2019137125A1 WO 2019137125 A1 WO2019137125 A1 WO 2019137125A1 CN 2018119736 W CN2018119736 W CN 2018119736W WO 2019137125 A1 WO2019137125 A1 WO 2019137125A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
local
session management
management network
terminal
Prior art date
Application number
PCT/CN2018/119736
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
Priority claimed from CN201811379260.9A external-priority patent/CN110167003B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22178965.4A priority Critical patent/EP4125284A1/en
Priority to EP18899139.2A priority patent/EP3720160B1/en
Priority to ES18899139T priority patent/ES2928328T3/es
Publication of WO2019137125A1 publication Critical patent/WO2019137125A1/zh
Priority to US16/906,842 priority patent/US11432366B2/en
Priority to US17/860,533 priority patent/US12004264B2/en

Links

Images

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8033—Rating or billing plans; Tariff determination aspects location-dependent, e.g. business or home
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8044—Least cost routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/20—Communication route or path selection, e.g. power-based or shortest path routing based on geographic position or location
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • 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
    • 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/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
    • 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
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • 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/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a session management method, device, and system.
  • a packet data unit (PDU) session is managed by a session management function (SMF) network element.
  • SMF session management function
  • UPF user plane function
  • the PDU session of the terminal corresponds to two UPF network elements, one UPF network element is located at the location of the access device close to the terminal, and the other UPF network element is located in the central equipment room.
  • the SMF network element of the PDU session of the terminal is managed. Need to control the UPF network elements of these two different locations.
  • the above 5G network architecture is inconsistent with the actual deployment of the operator.
  • the SMF network element and the UPF network element are usually considered in consideration of the complexity of the configuration across the administrative area and the requirement of the operator to hide the network topology. They are all divided by administrative area.
  • the SMF network element serving an administrative area can only manage the UPF network element serving the administrative area, and cannot manage the UPF network element serving other administrative areas; and the UPF network serving certain special areas of the administrative area.
  • the yuan cannot be managed by the general SMF network element serving the administrative area.
  • how to perform session management so that the terminal is not in the management area of the remote anchor SMF network element can still access the local data network through the local UPF network element, which is a hot research topic.
  • the embodiment of the present invention provides a session management method, a device, and a system, which can still access the local data network through the local UPF network element when the terminal is not in the management area of the remote anchor SMF network element.
  • a first aspect provides a session management method, the method comprising: an intermediate session management network element receiving one or more local data network access identifiers DNAI; the intermediate session management network element according to current location information of the terminal, and the one or A plurality of native DNAIs are used to determine a target DNAI, which is used to select a local session management network element for the terminal.
  • the intermediate session management network element can determine the target DNAI according to the current location information of the terminal and the acquired one or more local DNAIs, and the target DNAI is used to select a local session management network element for the terminal, and the local session
  • the management network element can manage the local user plane function network element of the terminal service. Therefore, the local data network can still be accessed through the local user plane function network element when the terminal is not in the management area of the remote anchor session management network element.
  • the target DNAI is further configured to select a local user plane function network element for the terminal.
  • the session access mode is further configured to select at least one of a local user plane function network element or the local session management network element for the terminal.
  • the method further includes: the intermediate session management network element receiving application identification information corresponding to the one or more local DNAIs; correspondingly, the first message further carries an application corresponding to the target DNAI
  • the identification information, the application identification information corresponding to the target DNAI is used to generate a local routing rule, and the local routing rule is used to offload data to a local data network corresponding to the target DNAI.
  • the method further includes: the intermediate session management network element receiving the second message from the mobility management network element, the second The message is used to release the session resource of the terminal on the intermediate session management network element and the intermediate user plane function network element; the intermediate session management network element releases the session resource of the terminal on the intermediate session management network element according to the second message. And the intermediate session management network element sends a third message to the intermediate user plane function network element, where the third message is used to indicate that the session resource of the terminal on the intermediate user plane function network element is released.
  • the storage resources of the intermediate session management network element and the intermediate user plane function network element are always occupied by the session resources, thereby causing waste of storage resources on the intermediate session management network element and the intermediate user plane function network element;
  • the intermediate session management network element and the intermediate user plane function network element on the original session path are respectively managed by the local session management network element and the local user of the local user plane function network element.
  • the face function network element is replaced, so that the control plane path between the mobility management network element and the local session management network element is short.
  • the method further includes: determining, by the intermediate session management network element, the local session management network element serving the terminal according to the target DNAI. Based on the scheme, the local session management network element serving as the terminal service can be determined by the intermediate session management network element.
  • the intermediate session management network element determines the local session management network element serving the terminal according to the target DNAI, and the intermediate session management network element is configured according to the target DNAI and local configuration information.
  • the terminal selects the local session management network element.
  • the intermediate session management network element determines, according to the target DNAI, the local session management network element serving the terminal, including: the intermediate session management network element according to the target DNAI and the session access mode. Information, selecting the local session management network element for the terminal.
  • the intermediate session management network element determines the local session management network element serving the terminal according to the target DNAI, and the intermediate session management network element sends a fifth message to the mobility management network element.
  • the fifth message carries the target DNAI; the intermediate session management network element receives information from the local session management network element of the mobility management network element.
  • the method further includes: the intermediate session management network element sending a sixth message to the local session management network element, where the sixth message carries current location information of the terminal, and the current location information of the terminal is used by The local user plane function network element is selected for the terminal.
  • the sixth message further carries information of a session access mode, and the information of the session access mode is used to determine an access mode of the local session.
  • the method further includes: the intermediate session management network element transmitting the target DNAI to the remote anchor session management network element, where the target DNAI is used for charging and policy control.
  • the method further includes: the intermediate session management network element sends a request message to the local session management network element, where the request message is used to establish a current access device of the terminal and a local user plane function network element.
  • the path between the local user plane function network element and the remote anchor user plane function network element is established. Based on this scheme, the user plane path of the session can be established.
  • the method further includes: the intermediate session management network element sending a seventh message to the intermediate user plane function network element, where the seventh message is used to indicate that the intermediate user plane function network element is released on the terminal Session resources.
  • the session resource can always avoid the storage space of the intermediate user plane function network element, thereby causing waste of storage resources on the intermediate user plane function network element; on the other hand, inserting the local user plane function network on the session path After the element, the intermediate session management network element on the original session path continues to be reserved, and the intermediate user plane function network element is replaced by the local session management network element and the local user plane function network element, so that the local session management network element is a simplified session management.
  • the network element which supports some functions of the session management network element, for example, supports the selection and control functions of the user plane function network element, and supports the session management network element with the upper level, such as the intermediate session management network element interface, according to the intermediate session management.
  • the instruction of the network element performs corresponding operations, and does not directly interface with other control plane network elements, thereby reducing the number of interfaces of the local session management network element and other control plane functions, and not only shielding the external network topology, but also the external network element. No need to perceive the local network topology, which can reduce the complexity of the network configuration
  • an intermediate session management network element having the function of implementing the method of any of the first aspect or the ninth aspect described below.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an intermediate session management network element including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the intermediate session management network element is running, the processor executes the computer stored by the memory The instruction is executed to cause the intermediate session management network element to perform the session management method according to any of the above first aspect or the ninth aspect.
  • a fourth aspect provides an intermediate session management network element, including: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute the first aspect or the following ninth according to the instruction according to the instruction.
  • the session management method of any of the aspects including: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute the first aspect or the following ninth according to the instruction according to the instruction.
  • a fifth aspect provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the first aspect or any of the following ninth aspects The session management method described in the item.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the session management method of any of the above first aspect or the ninth aspect.
  • a session management system includes: an intermediate session management network element and a mobility management network element; the intermediate session management network element is configured to receive one or more local data network access identifiers DNAI; The intermediate session management network element is further configured to determine a target DNAI according to the current location information of the terminal and the one or more local DNAIs; the intermediate session management network element is further configured to send the first message to the mobility management network element, The first message carries the target DNAI; the mobility management network element is configured to receive the first message from the intermediate session management network element, and determine a local session management network element serving the terminal according to the target DNAI.
  • the terminal can be disabled.
  • the remote anchor session manages the management area of the NE, the local data network can still be accessed through the local user plane function network element.
  • the session management system includes: a local session management network element; the mobile management network element is further configured to send a second message to the local session management network element, where the second message carries the current status of the terminal.
  • the local session management network element is configured to receive the second message from the mobility management network element, and determine a local user plane function network element serving the terminal according to the current location information of the terminal. Based on the solution, the local user plane function network element serving as the terminal service can be determined.
  • the second message further carries the target DNAI; the local session management network element is further configured to send the target DNAI to the remote anchor session management network element, where the target DNAI is used for charging And policy control.
  • the first message further carries information of a session access mode; correspondingly, the second message further carries information about the session access mode, where information of the session access mode is used to determine a local session. Access mode.
  • the local session management network element obtains the session access mode information when there is no interface between the remote anchor session management network element and the local session management network element.
  • the session access mode includes a multi-homing multi-homing mode; the local session management network element is further configured to allocate a local internet protocol IP address to the terminal, and the local session management network element, The local session management network element is further configured to notify the local user plane function network element to offload the data whose source address is the local IP address to the remote IP address of the terminal.
  • the local data network corresponding to the target DNAI, and the data whose source address is the remote IP address is offloaded to the remote anchor user plane function network element.
  • data splitting of the local data network and the remote data network can be implemented when the session mode is the Multi-homing mode.
  • the local session management network element is further configured to send the local IP address to the remote anchor session management network element, where the local IP address is used to manage the network element by using the remote anchor session.
  • the local session management network element is further configured to send a route advertisement to the terminal, where the route advertisement carries the local IP address. Based on the solution, the terminal can obtain the local IP address when the session access mode is the Multi-homing mode.
  • the local session management network element is further configured to initiate a path between the current access device of the terminal and the local user plane function network element, and the local user plane function network element and The path between the remote anchor user plane function network elements. Based on this scheme, the user plane path of the session can be established.
  • a session management system includes: an intermediate session management network element and a local session management network element; the intermediate session management network element is configured to receive one or more local data network access identifiers DNAI The intermediate session management network element is further configured to determine a target DNAI according to the current location information of the terminal and the one or more local DNAIs; the intermediate session management network element is further configured to determine, according to the target DNAI, the terminal a local session management network element of the service; the intermediate session management network element is further configured to send a first message to the local session management network element, where the first message carries current location information of the terminal; the local session management network element uses Receiving the first message from the intermediate session management network element, and determining a local user plane function network element serving the terminal according to the current location information of the terminal.
  • the first message further carries session access mode information; the session access mode information is used to determine an access mode of the local session.
  • a ninth aspect provides a session management method, the method comprising: an intermediate session management network element receiving one or more local data network access identifiers DNAI; and an intermediate session management network element according to current location information of the terminal, and one or more The local DNAI determines the target DNAI; the intermediate session management network element selects the local user plane function network element for the terminal according to the target DNAI.
  • the session management method provided by the embodiment of the present application may further include: the intermediate session management network element acquires a session access mode, a remote internet protocol IP address, a local routing policy corresponding to the target DNAI, or a target DNAI. At least one of the corresponding application identification information; the intermediate session management network element generates at least one of a session access mode, a remote internet protocol IP address, a local routing policy corresponding to the target DNAI, or application identification information corresponding to the target DNAI.
  • the target rule is used by the local user plane function network element to forward the received data packet.
  • the session management method provided by the embodiment of the present application may further include: the intermediate session management network element acquires information about the session access mode, where the information of the session access mode is used to determine an access mode of the local session. .
  • the session access mode is also used to select a local user plane function network element for the terminal.
  • the session access mode includes an uplink classifier ULCL mode or a multi-homed multi-homing mode.
  • the one or more local DNAIs are locally supported by the intermediate session management network element in the policy and charging control PCC rules of the terminal. DNAI.
  • the session management method provided by the embodiment of the present application may further include: the intermediate session management network element sends a request message to the remote anchor session management network element, The request message is used to request the remote anchor session management network element to support the local DNAI supported by the intermediate session management network element in the PCC rule corresponding to the one or more service data flows detected by the anchor user plane function network element. Send to the intermediate session management network element.
  • the intermediate session management network element receives one or more local DNAIs, including: the intermediate session management network element receives the remote management session network element from the remote point Or policy controls one or more local DNAIs of the network element.
  • FIG. 1 is a schematic diagram of deployment of SMF network elements and UPF network elements corresponding to different networks according to an embodiment of the present disclosure
  • FIG. 2 is a schematic structural diagram 1 of a session management system according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of application of the session management system shown in FIG. 2 in a 5G network;
  • FIG. 4 is a schematic structural diagram 2 of a session management system according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of application of the session management system shown in FIG. 4 in a 5G network;
  • FIG. 6 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart 1 of a session management method according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an intermediate session management network element according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram 3 of a session management system according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of application of the session management system shown in FIG. 10 in a 5G network;
  • FIG. 12 is a schematic flowchart diagram of a session management method according to an embodiment of the present application.
  • the words “first”, “second”, and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the number and execution order, and the words “first”, “second” and the like are not necessarily limited.
  • the general-purpose SMF network element, the UPF network element a1 of the network A, the UPF network element a2 and the UPF network element a3 are general UPF network elements serving the network A, and the SMF network element b1 and the SMF network element b2 of the network B are the network B.
  • the general SMF network element of the service, the UPF network element b1 of the network B, the UPF network element b2 and the UPF network element b3 are general UPF network elements serving the network B.
  • the general SMF network elements and the universal UPF network elements are generally deployed at the convergence.
  • the machine room in the central city of the layer is used to support mobile coverage within the network; below the dotted line is a dedicated SMF network element and a dedicated UPF network element serving some hotspot locations in the network, such as the SMF network element a3 and SMF of network A
  • the network element a4 is a dedicated SMF network element serving a special area in the network A.
  • the UPF network element a4 and the UPF network element a5 of the network A are dedicated UPFs managed by the SMF network element a3 to serve one of the special areas in the network A.
  • the network element, the UPF network element a6 and the UPF network element a7 of the network A are dedicated UPs managed by the SMF network element a4 for another special area in the network A.
  • the “network” in the embodiment of the present application specifically refers to a network corresponding to an administrative area, for example, a network corresponding to Shanghai; and a special area in the network in this embodiment may be, for example, The area in which an enterprise is located is uniformly described herein, and the embodiment of the present application does not specifically limit this.
  • the remote anchor user plane function network element in this embodiment is a universal user plane function network element connected to a remote data network, and may also be called a remote PDU session anchor.
  • the PDU session anchor (PSA) is not specifically limited in this embodiment of the present application.
  • the remote anchor session management network element in this embodiment is a general session management network element that manages the remote anchor user plane network element.
  • the intermediate session management network element in the embodiment of the present application is a general session management network element for managing an intermediate user plane function network element.
  • the local user plane function network element in this embodiment is a dedicated user plane function network element that interfaces with a specific network.
  • the local session management network element in this embodiment of the present application manages a dedicated session management network element of the local user plane function network element.
  • a session management system 20 is provided in the embodiment of the present application.
  • the session management system 20 includes an intermediate session management network element 201 and a mobility management network element 202.
  • the intermediate session management network element 201 is configured to receive one or more local data network access identifiers (DNAIs), and determine the target DNAI according to the current location information of the terminal and one or more local DNAIs. Thereafter, a first message is sent to the mobility management network element 202, the first message carrying the target DNAI.
  • DNAIs local data network access identifiers
  • the mobility management network element 202 is configured to receive the first message from the intermediate session management network element 201, and determine the local session management network element serving as the terminal service according to the target DNAI.
  • the intermediate session management network element 201 and the mobility management network element 202 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the terminal can be disabled.
  • the remote anchor session manages the management area of the NE, the local data network can still be accessed through the local user plane function network element.
  • the session management system 20 shown in FIG. 2 can be applied to the 5G network and other networks in the future, which is not specifically limited in this embodiment of the present invention.
  • the network element or entity corresponding to the intermediate session management network element may be an intermediate SMF network element in the 5G network.
  • the network element or entity corresponding to the foregoing mobility management network element may be an access and mobility management function (AMF) network element in the 5G network.
  • AMF access and mobility management function
  • the 5G network may further include an access network element, an intermediate UPF network element, a local SMF network element, a local UPF network element, a remote anchor SMF network element, and a remote anchor point UPF network element.
  • Policy control function (PCF) network element etc.
  • PCF Policy control function
  • the intermediate SMF network element is a general SMF network element serving the network B
  • the intermediate UPF network element is a general UPF network element managed by the intermediate SMF network element
  • the local SMF network element is a dedicated SMF network element serving the network B
  • the local UPF The network element is a dedicated UPF network element managed by the local SMF network element.
  • the terminal accesses the network through the access network element, and the terminal communicates with the AMF network element through the next generation (N) interface 1 (N1 for short); the access network element passes the N2 interface (referred to as N2) and the AMF network.
  • the N3 interface communicates with the intermediate UPF network element and the local UPF network element through the N3 interface (N3 for short); the AMF network element communicates with the intermediate SMF network element and the local SMF network element through the N11 interface (referred to as N11), and passes through the N15 interface (referred to as N15).
  • the remote anchor point UPF network element communicates with the intermediate UPF network element and the local UPF network element through the N9 interface (N9 for short); the remote anchor point UPF network element accesses the remote data through the N6 interface (N6 for short)
  • the local UPF network element accesses the local data network through the N6.
  • a session management system 40 is provided in the embodiment of the present application.
  • the session establishment system 40 includes an intermediate session management network element 401 and a local session management network element 402.
  • the intermediate session management network element 401 is configured to receive one or more local number DNAIs, determine the target DNAI according to the current location information of the terminal, and the one or more local DNAIs, and determine the terminal service according to the target DNAI.
  • Local session management NE Local session management NE.
  • the intermediate session management network element 401 is further configured to send a first message to the local session management network element 402, where the first message carries current location information of the terminal.
  • the intermediate session management network element 401 and the local session management network element 402 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the intermediate session management network element can determine the local session management network element serving as the terminal service according to the target DNAI, and send a first message carrying the current location information of the terminal to the local session management network element, so that the local message
  • the management network element can select the local user plane function network element for the terminal according to the current location information of the terminal, so that the terminal can still access the local data through the local user plane function network element when the terminal is not in the management area of the remote anchor session management network element.
  • the network element or entity corresponding to the intermediate session management network element may be an intermediate SMF network element in the 5G network.
  • the network element or entity corresponding to the local session management network element may be a local SMF network element in the 5G network.
  • the 5G network may further include an access network element, an AMF network element, an intermediate UPF network element, a local UPF network element, a remote anchor SMF network element, a remote anchor point UPF network element, and a PCF.
  • Network elements etc. Assume that the terminal is located in the network element A before the mobile terminal and the network B is located after the terminal moves.
  • the remote anchor SMF network element and the remote anchor point UPF network element are the network A service, the intermediate SMF network element, the intermediate UPF network element, and the local SMF network.
  • the meta and local UPF network elements serve the network B.
  • the intermediate SMF network element is a general-purpose SMF network element serving the network B
  • the intermediate UPF network element is a general-purpose UPF network element managed by the intermediate SMF network element
  • the local SMF network element is a dedicated SMF network element serving the network B
  • the local UPF The network element is a dedicated UPF network element managed by the local SMF network element.
  • the intermediate session management network element 1001 and the local user plane function network element 1002 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the intermediate session management network element can determine the local user plane function network element serving as the terminal service according to the target DNAI, so that the terminal can still pass the remote anchor point session management network element management area.
  • the local user plane function network element accesses the local data network.
  • the session management system 100 shown in FIG. 10 can be applied to the 5G network and other networks in the future, which is not specifically limited in this embodiment of the present invention.
  • the network element or entity corresponding to the intermediate session management network element 1001 may be an intermediate SMF network in a 5G network.
  • the network element or the entity corresponding to the local user plane function network element 1002 may be a local UPF network element in the 5G network.
  • the 5G network may further include an access network element, an AMF network element, an intermediate UPF network element, a remote anchor SMF network element, a remote anchor point UPF network element, and a PCF network element, and the like.
  • the 5G network shown in Figure 5 is similar. The difference is only that, in FIG.
  • the local UPF network element connected to the local data network communicates with the intermediate SMF network element through the N4 interface (N4 for short), that is, the local UPF network element in FIG. 11 is directly connected to the intermediate SMF network.
  • N4 for short
  • the local SMF network element is no longer needed.
  • the interface name between the network elements in FIG. 3 or FIG. 5 or FIG. 11 is only an example. In the specific implementation, the interface name may be another name, which is not specifically limited in this embodiment of the present application.
  • the access network element In the 5G network and other networks in the future, the access network element, the AMF network element, the intermediate SMF network element, the intermediate UPF network element, the local SMF network element, the local UPF network element, the remote anchor point SMF network element, and the remote anchor
  • the network elements or entities corresponding to the UPF network element and the PCF network element may also be other names, which are not specifically limited in this embodiment of the present application.
  • the local UPF network element may be replaced with a local UPF or a local UPF entity, and so on.
  • the intermediate SMF network element is inserted in the session path before the local UPF network element is inserted in the session path. And the intermediate UPF network element can make the remote anchor SMF network element and the remote anchor point UPF network element corresponding to the session not change, so that the continuity of the session can be maintained.
  • the path of the terminal accessing the remote DN is: the access network element and the intermediate UPF network element serving the network B, and accessing the remote anchor point UPF network element serving the network A.
  • the intermediate SMF network element and the intermediate UPF network element on the original session path are respectively managed.
  • the local SMF network element of the local UPF network element is replaced with the local UPF network element, so that the control plane path between the AMF network element and the local SMF network element is shorter; in the 5G network shown in FIG. 11, the session path is inserted.
  • the intermediate SMF network element in the original session path is retained, and the intermediate UPF network element is replaced by the local UPF network element, so that the terminal can access the application deployed in the local data network through the local UPF network element, thereby The time delay of accessing the application is reduced, and the transmission resource of the network is saved.
  • the terminal involved in the embodiment of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; Including user unit (subscriber unit), cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device Handheld, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (user equipment) , UE), mobile station (MS), terminal device or relay user equipment.
  • the relay user equipment may be, for example, a 5G residential gateway (RG).
  • RG 5G residential gateway
  • the access network element involved in the embodiment of the present application refers to a network element that accesses the core network, and may be, for example, a base station, a broadband network service gateway (BNG), an aggregation switch, and a third. 3rd generation partnership project (3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.
  • the intermediate session management network element or the mobility management network element in FIG. 2, or the intermediate session management network element or the local session management network element in FIG. 4, or the intermediate session management network element in FIG. 10 may be configured by one device.
  • the implementation may be implemented by a plurality of devices, or may be a function module in a device, which is not specifically limited in this embodiment. It can be understood that the above functions can be either a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • FIG. 6 is a schematic diagram showing the hardware structure of a communication device according to an embodiment of the present application.
  • the communication device 600 includes at least one processor 601, a communication line 602, a memory 603, and at least one communication interface 604.
  • the processor 601 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 602 can include a path for communicating information between the components described above.
  • Communication interface 604 using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 603 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory may be stand-alone and connected to the processor via communication line 602. The memory can also be integrated with the processor.
  • the memory 603 is used to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 601 for execution.
  • the processor 601 is configured to execute computer execution instructions stored in the memory 603, thereby implementing the session management method provided by the following embodiments of the present application.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.
  • the processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 600 can include multiple processors, such as processor 601 and processor 608 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • processors herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the communication device 600 can also include an output device 605 and an input device 606.
  • Output device 605 is in communication with processor 601 and can display information in a variety of ways.
  • the output device 605 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 606 is in communication with processor 601 and can receive user input in a variety of ways.
  • input device 606 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the communication device 600 described above may be a general purpose device or a dedicated device.
  • the communication device 600 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or the like in FIG. device.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 600.
  • the session management system shown in FIG. 2 is applied to the 5G network shown in FIG. 3 .
  • the session management method provided by the embodiment of the present application includes the following steps:
  • the terminal After the terminal moves from the network A to the network B, the terminal establishes a session, where the network A to which the remote anchor SMF network element belongs is different from the network B to which the current access network element of the terminal belongs. Therefore, in addition to the remote anchor SMF network element serving the network A and the remote anchor UPF network element managed by the remote anchor SMF network element, the session path includes an intermediate SMF serving the network B. The network element and the intermediate UPF network element managed by the intermediate SMF network element. At this time, the user plane path of the session is: terminal ⁇ -> intermediate UPF network element ⁇ -> remote anchor point UPF network element.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may be the DNAI in the PCC rule corresponding to the session.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may be all DNAIs included in the PCC rules corresponding to the session.
  • the PCC rules corresponding to the session include PCC Rule 1 and PCC Rule 2.
  • DNAI1 and DNAI2 are included in PCC Rule 1
  • DNAI3 and DNAI4 are included in PCC Rule 2
  • the one or more native DNAIs include DNAI1 and DNAI2, DNAI3 and DNAI4.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may be the DNAI supported by the intermediate SMF network element in the PCC rule corresponding to the session.
  • the PCC rules corresponding to the session include PCC Rule 1 and PCC Rule 2.
  • DNAI1 and DNAI2 are included in PCC Rule 1
  • DNAI3 and DNAI4 are included in PCC Rule 2.
  • the DNAI supported by the intermediate SMF network element includes DNAI4 and DNAI5, and the one or more native DNAIs include DNAI4.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may be the DNAI included in the first PCC rule corresponding to the session, the first PCC rule.
  • the PCC rules corresponding to the session include PCC Rule 1 and PCC Rule 2.
  • DNAI1 and DNAI2 are included in PCC Rule 1
  • DNAI3 and DNAI4 are included in PCC Rule 2.
  • the DNAI supported by the intermediate SMF network element includes DNAI4 and DNAI5, and the one or more native DNAIs include DNAI3 and DNAI4 included in PCC Rule 2.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may also be the PCC rules corresponding to one or more service data flows detected by the anchor UPF network element. DNAI.
  • the remote anchor SMF network element may send a report rule to the anchor point UPF network element, where the anchor point UPF network element sends a report to the remote anchor point SMF network element when detecting the corresponding service data flow, thereby The remote anchor SMF network element learns one or more service data flows detected by the anchor point UPF network element.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may be PCC rules corresponding to one or more service data flows detected by the anchor UPF network element. All DNAI included.
  • the PCC rules corresponding to one or more service data streams detected by the anchor UPF network element include PCC Rule 1 and PCC Rule 2.
  • DNAI1 and DNAI2 are included in PCC Rule 1
  • DNAI3 and DNAI4 are included in PCC Rule 2
  • the one or more native DNAIs include DNAI1 and DNAI2, DNAI3 and DNAI4.
  • the reporting rule sent by the remote anchor SMF network element to the anchor point UPF network element may detect the service data flow corresponding to the PCC rule including one or more DNAIs in all PCC rules corresponding to the session.
  • the anchor UPF network element sends a report to the anchor SMF network element.
  • the reporting rule sent by the remote anchor SMF network element to the anchor point UPF network element may be related to the service data corresponding to the PCC rule of at least one of the DNAI supported by the intermediate SMF network element in all the PCC rules corresponding to the session.
  • the flow is detected.
  • the anchor UPF network element sends a report to the anchor SMF network element.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may be corresponding to one or more service data flows detected by the anchor UPF network element.
  • the PCC rules corresponding to one or more service data flows detected by the anchor UPF network element include PCC Rule 1 and PCC Rule 2.
  • DNAI1 and DNAI2 are included in PCC Rule 1
  • DNAI3 and DNAI4 are included in PCC Rule 2.
  • the DNAI supported by the intermediate SMF network element includes DNAI4 and DNAI5, and the one or more native DNAIs include DNAI3 and DNAI4 included in PCC Rule 2.
  • the reporting rule sent by the remote anchor SMF network element to the anchor UPF network element may be used to include the service data flow corresponding to at least one PCC rule supported by the intermediate SMF network element for all PCC rules corresponding to the session. The detection is performed, and when the corresponding service data flow is detected, the anchor UPF network element sends a report to the anchor SMF network element.
  • the intermediate SMF network element may subscribe to the service data of the remote anchor SMF network element.
  • the flow discovery report is configured to send the one or more local DNAIs to the intermediate SMF network element after the remote anchor SMF network element learns one or more service data flows detected by the anchor point UPF network element.
  • the intermediate SMF network element may provide a set of local DNAIs (including one or more DNAIs), so that when the remote SMF network element learns one or more detected by the anchor point UPF network element
  • the service data stream, and the PCC rule corresponding to the service data stream includes at least one DNAI of the set of local DNAIs, and then sends one or more local DNAIs to the intermediate SMF network element.
  • the reporting rule sent by the remote anchor SMF network element to the anchor point UPF network element may detect the service data flow corresponding to the PCC rule including at least one of the local DNAIs in all PCC rules corresponding to the session.
  • the anchor UPF network element sends a report to the anchor SMF network element.
  • the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element may be included in the first PCC rule corresponding to the one or more service data flows detected by the anchor UPF network element.
  • the first PCC rule is a PCC rule comprising at least one DNAI of a set of native DNAIs.
  • the PCC rules corresponding to one or more service data flows detected by the anchor UPF network element include PCC Rule 1 and PCC Rule 2.
  • DNAI1 and DNAI2 are included in PCC Rule 1
  • DNAI3 and DNAI4 are included in PCC Rule 2.
  • One set of native DNAI includes DNAI4 and DNAI5, and the one or more native DNAIs include DNAI3 and DNAI4 included in PCC Rule 2.
  • the reporting rule sent by the remote anchor SMF network element to the anchor point UPF network element may detect the service data flow corresponding to the PCC rule including at least one of the local DNAIs in all PCC rules corresponding to the session.
  • the anchor UPF network element sends a report to the anchor SMF network element.
  • the set of local DNAIs in the embodiment of the present application may be the DNAI supported by the intermediate SMF network element, which is not specifically limited in this embodiment of the present application.
  • information for identifying one or more DNAIs of the DNAI supported by the intermediate SMF network element may be, for example, an identifier of the intermediate SMF network element, and the remote anchor SMF network element is identified according to the identifier of the intermediate SMF network element. Determining one or more DNAIs supported by the intermediate SMF network element; for example, an area identifier of the intermediate SMF network element, a set identifier of the intermediate SMF network element, and the like. In these manners, the remote anchor SMF network element exemplifies the corresponding management of the one or more DNAIs supported by the intermediate SMF network element, which is not specifically limited in this embodiment of the present application.
  • the foregoing merely provides an exemplary manner for determining the one or more local DNAIs sent by the remote anchor SMF network element to the intermediate SMF network element.
  • the remote anchor may be determined by other means.
  • One or more local DNAIs that are sent by the SMF network element to the intermediate SMF network element are not specifically limited in this embodiment of the present application.
  • the remote SMF network element if the intermediate SMF network element provides only one DNAI at the time of subscription, the remote SMF network element discovers the service data flow, and the PCC rule corresponding to the service data flow includes the In the case of the DNAI, a notification message is sent to the intermediate SMF network element, and the notification message may not carry the DNAI, and the notification message is used to indicate that a service data stream supporting the DNAI is found.
  • the one or more local DNAIs may be sent by the PCF network element to the remote anchor SMF network element, and then directly forwarded to the intermediate SMF network element by using the remote anchor SMF network element; After the remote anchor SMF network element receives the plurality of local DNAIs from the PCF network element, the one or more local DNAIs are selected from the plurality of local DNAIs and sent to the intermediate SMF network element. This is not specifically limited.
  • the remote anchor SMF network element may further send information about the session access mode to the intermediate SMF network element, where the session access mode may be, for example, an uplink classifier (ULCL) mode. Or a multi-homing mode or the like, which is not specifically limited in the embodiment of the present application.
  • the information about the session access mode is sent to the local SMF network element after the remote anchor SMF network element learns the information of the local SMF network element, which is not specifically limited in this embodiment.
  • the information of the session access mode in the embodiment of the present application may be sent by the PCF network element to the remote anchor SMF network element, or may be determined by the remote anchor SMF network element. This is not specifically limited.
  • the PCF network element may also send the foregoing information, such as one or more local DNAIs, application identification information, and session access mode.
  • the information, or the remote IP address, and the like are directly sent to the intermediate SMF network element, which is not specifically limited in this embodiment of the present application.
  • the intermediate SMF network element determines the target DNAI according to the current location information of the terminal and one or more local DNAIs.
  • the local DNAI corresponding to the local data network may be determined as the target DNAI; or, according to the current location information of the terminal. If it is determined that there are a plurality of relatively close local data networks in the vicinity of the current location of the terminal, the local DNAI corresponding to the lower-load local data network in the plurality of local data networks may be determined as the target DNAI, which is not specifically described in this embodiment of the present application. limited.
  • the intermediate SMF network element sends an insertion request to the AMF network element, so that the AMF network element receives the insertion request from the intermediate SMF network element.
  • the insertion request carries the target DNAI for requesting insertion into the local UPF network element.
  • the insertion request may further carry the application identifier information corresponding to the target DNAI after the intermediate SMF network element determines the target DNAI.
  • the insertion request may further carry information about the session access mode.
  • the local UPF network element may be a ULCL; if the session access mode is the multi-homing mode, the local UPF network element may be a branch point ( Branching point, BP), hereby unified, the following will not repeat.
  • Branching point BP
  • the insertion request may further carry the remote IP address assigned by the remote anchor SMF network element to the terminal. This is not specifically limited.
  • the local SMF network element that is determined by the AMF network element to be the terminal service according to the target DNAI may include: the AMF network element selects the local SMF network element for the terminal according to the target DNAI and the local configuration information; or ,
  • the AMF network element may consider the session in addition to the target DNAI when determining the local SMF network element serving as the terminal service.
  • the information of the inbound mode for example, the AMF network element or the NRF network element, selects the local SMF network element that supports the session access mode, which is not specifically limited in this embodiment of the present application.
  • the AMF network element sends a session establishment request to the local SMF network element, so that the local SMF network element receives the session establishment request from the AMF network element.
  • the session establishment request carries current location information of the terminal.
  • the session establishment request may further carry the information of the session access mode, which is not specifically limited in this embodiment of the present application.
  • the session establishment request may further carry the application identifier information corresponding to the target DNAI, which is not used in this embodiment of the present application. Specifically limited.
  • the session establishment request may further carry the information of the remote anchor SMF network element, where the local SMF network element communicates with the remote SMF, which is not specifically limited in this embodiment of the present application.
  • the local SMF network element determines the local UPF network element serving as the terminal service according to the current location information of the terminal.
  • the local SMF network element that is determined to be the local UPF network element of the terminal according to the current location information of the terminal may include: the local SMF network element selects the local UPF for the terminal according to the current location information of the terminal. Network element; or:
  • the local SMF network element may determine that the local UPF network element serving as the terminal service according to the current location information of the terminal may include: the local SMF network element requests the network function storage network element, for example, the NRF network element. After the local UPF network element is selected by the NRF network element according to the current location information of the terminal, the NRF network element sends the information of the local UPF network element to the local SMF network element.
  • the manner in which the local SMF network element is determined to be the local UPF network element of the terminal service according to the current location information of the terminal is not specifically limited.
  • the local SMF may consider the location information of the terminal in addition to the location information of the terminal when determining the local UPF network element of the terminal service.
  • the information of the session access mode for example, the local SMF network element or the NRF network element selects a local UPF network element that supports the session access mode, which is not specifically limited in this embodiment.
  • the local SMF network element sends an N4 session establishment request 1 to the local UPF network element, so that the local UPF network element receives the N4 session establishment request 1 from the local SMF network element.
  • the N4 session establishment request 1 is used to create a corresponding session on the local UPF network element.
  • the local SMF network element can obtain the session access mode information, and the session access mode corresponding to the session access mode information is in the multi-homing mode, the local SMF network element can also be allocated to the terminal.
  • the local IP address, and the N4 session establishment request 1 is used to notify the local UPF network element to offload the data packet whose source address is the local IP address to the local data network corresponding to the target DNAI, which is not specifically limited in this embodiment of the present application.
  • the method of informing the local UPF network element to offload the data whose source address is the local IP address to the local data network corresponding to the target DNAI may be that the local SMF network element generates the first local routing rule, and then the first local routing rule is passed through the N4.
  • the session establishment request 1 is sent to the local UPF network element, and the first local routing rule is used to offload the data packet whose source address is the local IP address to the local data network corresponding to the target DNAI, which is not specifically limited in this embodiment of the present application.
  • the local SMF network element can obtain the remote IP address.
  • the local SMF network element may also notify the local UPF network element to forward the data whose source address is the remote IP address to the remote anchor UPF network element by using the N4 session establishment request 1 to notify the local UPF network element that the source address is The remote IP address is forwarded to the remote UPF network element by the local SMF network element.
  • the remote routing rule is sent to the local UPF network element through the N4 session update request 1.
  • the remote routing rule is used to offload packets with the source address to the remote IP address to the remote anchor UPF network element.
  • the local SMF network element can obtain the session access mode information, and the session access mode corresponding to the session access mode information is in the ULCL mode, the local SMF network element can be configured according to the local configuration information or the target. At least one of the application identifier information corresponding to the DNAI, after generating the second local routing rule, the second local routing rule is sent to the local UPF network element by using the N4 session establishment request 1, and the second local routing rule is used to offload the data.
  • the local data network corresponding to the target DNAI is not specifically limited in this embodiment of the present application.
  • the application identifier information corresponding to the target DNAI required to generate the second routing rule may be carried in the session establishment request in step S706, or may be the remote anchor SMF carried in the session establishment request in step S706.
  • the information of the network element is sent to the local SMF network element by the remote anchor SMF network element after being communicated with the remote anchor SMF network element (for example, it is sent to the local SMF network element in the subsequent step S712). This is not specifically limited.
  • the local UPF network element may also send the N4 session establishment response 1 corresponding to the N4 session establishment request 1 to the local SMF network element, which is not specifically limited in this embodiment of the present application.
  • the local SMF network element sends a session update request 1 to the remote anchor SMF network element, so that the remote anchor SMF network element receives the session update request 1 from the local SMF network element.
  • the session update request is used to update the downlink tunnel of the remote anchor UPF network element to connect to the local UPF network element.
  • the session update request 1 may carry the downlink tunnel information of the local UPF network element, where the downlink tunnel information of the local UPF network element may include, for example, an N9 tunnel between the remote anchor UPF network element and the local UPF network element.
  • the tunnel identifier of the local UPF network element, the tunnel identifier may include, for example, an endpoint address or an endpoint identifier, and the endpoint identifier may be, for example, a tunnel endpoint identifier (TEID), which is not specifically limited in this embodiment of the present application.
  • the downlink tunnel information of the local UPF network element may be allocated by the local SMF network element, or may be sent by the local UPF network element to the local SMF network element, which is not specifically limited in this embodiment.
  • the session update request 1 can also carry the local The local IP address assigned by the SMF network element to the terminal.
  • the session update request 1 may further carry the target DNAI, where the target DNAI is used for charging and policy control, for example, the remote end.
  • the anchor SMF network element can determine which charging and policy control rules should be performed by the local UPF network element according to the target DNAI, which is not specifically limited in this embodiment of the present application.
  • step S708 may be performed first.
  • Step S709 is performed; the step S709 may be performed first, and then the step S708 may be performed; or the steps S708 and S709 may be performed at the same time, which is not specifically limited in the embodiment of the present application.
  • the remote anchor SMF network element sends an N4 session update request 1 to the remote anchor UPF network element, so that the remote anchor UPF network element receives the N4 session update request 1 from the remote anchor SMF network element.
  • the N4 session update request 1 carries the downlink tunnel information of the local UPF network element, and is used to establish an N9 tunnel between the local UPF network element and the remote anchor point UPF network element.
  • the remote anchor UPF network element may also send the N4 session update response 1 corresponding to the N4 session update request 1 to the remote anchor SMF network element, which is not specifically implemented in this embodiment of the present application. limited.
  • the PCC update request may carry a local IP address that is allocated by the local SMF network element for the terminal, which is not specifically limited in this embodiment of the present application.
  • step S710 and S711 there is no necessary execution sequence between the step S710 and the step S711, and the step S710 may be performed first, and then the step S711 may be performed; or the step S711 may be performed first, and then the step S710 is performed; Steps S710 and S711 may be performed at the same time, which is not specifically limited in this embodiment of the present application.
  • the local SMF network element may send the local IP address to the remote anchor SMF network element after the subsequent assignment of the local IP address to the terminal.
  • the local IP address is sent by the remote anchor SMF network element to the PCF network element, which is not specifically limited in this embodiment.
  • the PCF network element may also send a PCC update response corresponding to the PCC update request to the remote anchor SMF network element, which is not specifically limited in this embodiment of the present application.
  • the remote anchor SMF network element sends a session update response 1 to the local SMF network element, so that the local SMF network element receives the session update response 1 from the remote anchor SMF network element.
  • the session update response 1 carries the uplink tunnel information of the remote anchor UPF network element, and the uplink tunnel information of the remote anchor point UPF network element may include, for example, between the remote anchor point UPF network element and the local UPF network element.
  • the tunnel identifier of the N9 tunnel on the remote node's UPF network element side, the tunnel identifier may include, for example, an endpoint address or an endpoint identifier, and the endpoint identifier may be, for example, a TEID, which is not specifically limited in this embodiment of the present application.
  • the uplink tunnel information of the remote anchor UPF network element may be allocated by the remote anchor SMF network element, or may be sent by the remote anchor point UPF network element to the remote anchor SMF network element.
  • the application examples are not specifically limited thereto.
  • the session update response 1 in step S712 may carry the session. Access mode information.
  • the session establishment response may also carry the uplink tunnel information of the local UPF network element, where the uplink tunnel information of the local UPF network element is used to establish the local UPF network element and the access network.
  • the uplink tunnel information of the local UPF network element may include, for example, a tunnel identifier of the N3 tunnel between the local UPF network element and the access network element on the local UPF network element side, and the tunnel identifier may include, for example, an endpoint address or an endpoint identifier.
  • the endpoint identifier may be, for example, a TEID or the like, which is not specifically limited in this embodiment of the present application.
  • the AMF network element sends an N2 session management (SM) request to the access network element, so that the access network element receives the N2SM request from the AMF network element.
  • SM N2 session management
  • the access network element sends an N2SM response to the AMF network element, so that the AMF network element receives the N2SM response from the access network element.
  • the access network element may further configure the radio resource for the session according to the requirement before the N2SM response is sent to the AMF network element, which is not specifically limited in this embodiment.
  • the AMF network element sends a session update request 2 to the local SMF network element, so that the local SMF network element receives the session update request 2 from the AMF network element.
  • the session update request 2 carries the downlink tunnel information of the access network element.
  • the local SMF network element may further send the session update response 2 corresponding to the session update request 2 to the AMF network element, which is not specifically limited in this embodiment.
  • the local SMF network element sends an N4 session update request 2 to the local UPF network element, so that the local UPF network element receives the N4 session update request 2 from the local SMF network element.
  • the N4 session update request 2 is used to update the corresponding session on the local UPF network element.
  • the N4 session update request 2 carries the uplink tunnel information of the remote anchor UPF network element, and is used to establish an N9 tunnel between the remote anchor UPF network element and the local UPF network element; and the N4 session update request 2
  • the downlink tunnel information of the access network element is used to establish an N3 tunnel between the access network element and the local UPF network element.
  • the local SMF network element may be configured according to local configuration information or At least one of the application identifier information corresponding to the target DNAI, after generating the second local routing rule, sending the second local routing rule to the local UPF network element by using the N4 session update request 2, where the second local routing rule is used for data
  • the embodiment of the present application does not specifically limit the flow to the local data network corresponding to the target DNAI.
  • the local SMF network element may Step S708 is not performed; or, optionally, in the embodiment of the present application, if the local SMF network element obtains the session access mode information in step S706, but the session access mode is multi-homing mode, the local SMF network element
  • the local IP address may not be allocated to the terminal after step S706, but the local IP address is allocated to the terminal after the step S712, and the first local routing rule is generated, and then sent to the local UPF network element through the N4 session establishment request 2.
  • the embodiment of the present application does not specifically limit this.
  • the local UPF network element may also send the N4 session update response 2 corresponding to the N4 session update request 2 to the local SMF network element, which is not specifically limited in this embodiment of the present application.
  • step S718 is an optional step, and correspondingly, the local SMF network element obtains the information of the session access mode in step S712.
  • the local SMF network element allocates the local IP address to the terminal according to the information of the session access mode, the local IP address may be carried in the session update request 1 of step S709. No specific limitation.
  • the remote anchor SMF network element sends a route advertisement (RA) to the terminal, so that the terminal receives the route advertisement from the remote anchor SMF network element.
  • the route advertisement carries a local IP address.
  • the remote anchor SMF network element sends a route advertisement to the terminal through the user
  • the user plane refers to the N9 tunnel between the remote anchor point UPF network element and the local UPF network element. No longer.
  • step S719 is an optional step, and the corresponding situation is that the session access mode is the multi-homing mode, which is uniformly described herein, and is not described below.
  • the route advertisement may be sent by the local SMF network element to the terminal after the local SMF network element allocates the local IP address to the terminal, which is not specifically limited in this embodiment.
  • the AMF network element sends a session release request 1 to the intermediate SMF network element, so that the intermediate SMF network element receives the session release request 1 from the AMF network element.
  • the session release request 1 is used to indicate that the session resources of the terminal on the intermediate SMF network element and the intermediate UPF network element are released.
  • the session release request 1 may carry an indication information, where the indication information is used to indicate that only the session resources of the terminal on the intermediate SMF network element and the intermediate UPF network element are released, and the remote anchor point SMF network element is not released.
  • the session resource of the terminal is obtained, so that the intermediate SMF network element can release the session resource of the terminal on the intermediate SMF network element after receiving the session release request, and does not release the session resource of the terminal on the remote anchor SMF network element.
  • the intermediate UPF network element can release the session resources of the terminal on the intermediate UPF network element.
  • the intermediate UPF network element After the release of the session resource of the terminal on the intermediate UPF network element, the intermediate UPF network element sends a session release response 2 to the intermediate SMF network element.
  • the session release response 2 is used to indicate that the session resource release of the terminal on the intermediate UPF network element ends.
  • the intermediate SMF network element After the release of the session resource of the terminal on the intermediate UPF network element and the intermediate SMF network element, the intermediate SMF network element sends a session release request 1 to the AMF network element.
  • the session release response 2 is used to indicate that the session resource release of the terminal is ended on the intermediate UPF network element and the intermediate SMF network element.
  • the action of the intermediate SMF network element in the foregoing steps S701 to S723 can be performed by the processor 601 in the communication device 600 shown in FIG. 6 to call the application code stored in the memory 603, and the embodiment of the present application does not do any limit.
  • FIG. 7 For example, the embodiment shown in FIG. 7 is omitted, and details are not described herein again.
  • step S802 similar to step S702, except that in the embodiment, because there is no interface between the remote anchor SMF network element and the local SMF network element, the session access mode information and the application corresponding to one or more local DNAIs
  • the identification information can only be sent by the remote anchor SMF network element to the intermediate SMF network element.
  • the remote anchor SMF network element can learn the information of the local SMF network element, and then The information about the application identification information and the session access mode corresponding to the one or more local DNAIs is sent to the local SMF network element.
  • the embodiment shown in FIG. 7 and details are not described herein again.
  • the intermediate SMF network element may be based on the session access mode, the remote IP address, the local routing policy corresponding to the target DNAI, or the target. At least one of the application identifier information corresponding to the DNAI generates a target rule, where the target rule is used by the local UPF network element to forward the received data packet, which is not specifically limited in this embodiment of the present application.
  • the local UPF network element in the embodiment of the present application may include a local anchor UPF network element and a ULCL/BP.
  • the local anchor UPF network element and the ULCL/BP may be separately and independently deployed, or may be unified.
  • the embodiment of the present application does not specifically limit this.
  • the local anchor UPF network element is a UPF network element that interfaces with the target DNAI;
  • the ULCL/BP is a UPF network element that interfaces with the current access device of the terminal, and is uniformly described herein, and details are not described herein.
  • the rules installed on the local UPF network element in the embodiment of the present application may include installing the local anchor point UPF. At least one of the rules on the network element or the rules installed on the ULCL/BP is uniformly described herein, and will not be described below.
  • the local SMF network element that is determined to be the terminal service according to the target DNAI may include: the intermediate SMF network element selects the local SMF network element for the terminal according to the target DNAI and the local configuration information. ;or:
  • the local SMF network element that is determined to be the terminal service according to the target DNAI may include: the intermediate SMF network element requests the network function storage network element, for example, the NRF network element requests the local SMF The information of the network element, after the NRF network element selects the local SMF network element according to the target DNAI, sends the information of the local SMF network element to the intermediate SMF network element; or:
  • the local SMF network element determined by the intermediate SMF network element to be the terminal service according to the target DNAI may include: the intermediate SMF network element requests the information of the local SMF network element from the AMF network element, by the AMF. After selecting the local SMF network element for the terminal according to the target DNAI, the network element sends the information of the local SMF network element to the intermediate SMF network element.
  • the manner in which the intermediate network element determines the local SMF network element serving as the terminal service according to the target DNAI is not specifically limited.
  • step S805 similar to step S706, except that the AMF network element in the embodiment shown in FIG. 7 is replaced with the intermediate SMF network element in the embodiment of the present application; and, in the embodiment of the present application, the session establishment request is further
  • the uplink tunnel information of the remote anchor point UPF network element may be carried.
  • step S807 similar to step S708, except that the local SMF network element sends the N4* session establishment request 1 to the local UPF network element in step S807 of the embodiment, and the N4* session establishment request 1 can also carry the S712.
  • the uplink tunnel information of the remote anchor point UPF network element refer to the embodiment shown in FIG. 7 for related description, and details are not described herein again.
  • the local SMF network element sends a session establishment response to the intermediate SMF network element, so that the intermediate SMF network element receives the session establishment response from the local SMF network element.
  • the session establishment response is carried out with the downlink tunnel information of the local UPF network element.
  • the downlink tunnel information of the local UPF network element refer to step S709 of the embodiment shown in FIG. 7 , and details are not described herein again.
  • the session establishment response further carries the local SMF network element.
  • the local IP address assigned to the terminal is not specifically limited in this embodiment.
  • step S809 similar to step S709, except that the local SMF network element in the step S709 of the embodiment shown in FIG. 7 is replaced with the intermediate SMF network element in the embodiment of the present application.
  • the embodiment shown in FIG. 7. will not repeat them here.
  • the remote anchor SMF network element sends a session update response 1 to the intermediate SMF network element, so that the intermediate SMF network element receives the session update response 1 from the remote anchor SMF network element.
  • the uplink offloading rule When the ULCL is deployed separately from the local anchor UPF network element, the uplink offloading rule includes an uplink offloading rule installed on the ULCL.
  • the uplink offloading rule that is installed on the ULCL is used by the ULCL to send the data packet to the local anchor UPF network element or the remote anchor point UPF network element according to the source address of the data packet. This is not specifically limited in this embodiment.
  • the intermediate SMF network element sends a session update request 3 to the AMF network element, so that the AMF network element receives the session update request 3 from the intermediate SMF network element.
  • the AMF network element sends a session update response 3 to the intermediate SMF network element, so that the intermediate SMF network element receives the session update response 3 from the AMF network element.
  • the intermediate SMF network element sends a session update request 2 to the local SMF network element, so that the local SMF network element receives the session update request 2 from the intermediate SMF network element.
  • the session update request 2 in step S817 can also carry the installed local UPF.
  • the uplink offloading rule on the network element is not specifically limited in this embodiment of the present application.
  • the intermediate SMF network element may send the remote IP address to the local SMF network element, and the local SMF network element generates an uplink traffic distribution rule for the local UPF network element.
  • the local SMF network element may send the remote IP address to the local SMF network element, and the local SMF network element generates an uplink traffic distribution rule for the local UPF network element.
  • the N4* session update request 2 carries the downlink tunnel information of the access network element.
  • the local UPF network element may also send the N4* session update response 2 corresponding to the N4* session update request 2 to the local SMF network element, which is not specifically limited in this embodiment of the present application.
  • the N4* session update request 2 in step S818 can also carry the installation.
  • the uplink offloading rule on the local UPF network element is not specifically limited in this embodiment of the present application.
  • step S819 the same as step S719, the related description can refer to the embodiment shown in FIG. 7, and details are not described herein again.
  • the session management method provided by the embodiment of the present invention can still access the local data network through the local UPF network element when the terminal is not in the management area of the remote anchor SMF network element.
  • the intermediate SMF network element selects a local UPF network element for the terminal according to the target DNAI.
  • the intermediate SMF network element selects the local UPF network element for the terminal according to the target DNAI, and specifically includes: the intermediate SMF network element according to the The target DNAI selects a local anchor UPF network element for the terminal; and the intermediate SMF network element selects ULCL/BP for the terminal according to the location information of the terminal.
  • the intermediate SMF network element selects a local anchor point UPF network element for the terminal according to the target DNAI, and specifically includes: the intermediate SMF network element according to the target DNAI, local configuration information, and an optional terminal location.
  • the information is used to select a local anchor UPF network element for the terminal; or the intermediate SMF network element requests the network function storage network element, for example, the NRF network element to request the information of the local anchor UPF network element, and the NRF network element selects the target according to the target DNAI.
  • the information of the local anchor UPF network element is sent to the intermediate SMF network element, which is not specifically limited in this embodiment.
  • the intermediate SMF network element selects the ULCL/BP for the terminal according to the location information of the terminal, and specifically includes: the intermediate SMF network element selects the ULCL/ for the terminal according to the location information and the local configuration information of the terminal. BP; or, the intermediate SMF network element requests the ULCL/BP information from the network function storage network element, for example, the NRF network element, and the NRF network element sends the ULCL/BP to the terminal according to the location information of the terminal, and then sends the information to the intermediate SMF network element.
  • the information of the ULCL/BP is not specifically limited in this embodiment of the present application.
  • the intermediate SMF network element selects the local UPF network element for the terminal according to the target DNAI, and the intermediate SMF network element may include: The target DNAI, the location information of the terminal, and the local configuration information, select a local UPF network element for the terminal; or the intermediate SMF network element requests the network function storage network element, for example, the NRF network element to request the information of the local UPF network element, by the NRF network After the local UPF network element is selected for the terminal according to the target DNAI and the terminal location information, the information of the local UPF network element is sent to the intermediate SMF network element, which is not specifically limited in this embodiment.
  • the intermediate SMF network element may select different local anchor UPF network elements for different target DNAIs. For example, the local anchor UPF network elements corresponding to each target DNAI are different.
  • step S1205 similar to step S807, the difference is that the local SMF network element in step S807 is replaced with the intermediate SMF network element, and the N4* session establishment request 1 in step S807 is replaced with the N4 session establishment request 1.
  • the embodiment shown in FIG. 8 is not described herein again.
  • step S1214 is similar to step S818.
  • the difference is that the local SMF network element in step S818 is replaced with the intermediate SMF network element, and the N4* session establishment request 2 in step S818 is replaced with the N4 session establishment request 2.
  • the embodiment shown in FIG. 8 is not described herein again.
  • the session management method provided by the embodiment of the present invention can still access the local data network through the local UPF network element when the terminal is not in the management area of the remote anchor SMF network element.
  • the action of the intermediate SMF network element in the foregoing steps S1201 to S1217 can be performed by the processor 601 in the communication device 600 shown in FIG. 6 to call the application code stored in the memory 603, and the embodiment of the present application does not do any limit.
  • the embodiment shown in FIG. 12 is described by taking a local anchor UPF network element and a ULCL/BP integrated deployment as an example.
  • the local anchor point UPF network element and the ULCL/BP in the embodiment of the present application may also be deployed separately.
  • the intermediate SMF network element needs to separately send an N4* session to the local anchor point UPF network element and the ULCL/BP.
  • the request is to establish a tunnel between the ULCL/BP and the local anchor UPF network element, and establish a tunnel between the ULCL/BP and the remote anchor UPF network element.
  • FIG. Let me repeat. Let me repeat.
  • the method further includes: the intermediate session management network element sends a first message to the mobility management network element, where the first message carries the target DNAI.
  • the target DNAI is also used to select a local user plane function network element for the terminal.
  • the first message further carries information of a session access mode, where the information of the session access mode is used to determine an access mode of the local session.
  • the session access mode is further configured to select at least one of a local user plane function network element or a local session management network element for the terminal.
  • the session access mode includes a ULCL mode or a Multi-homing mode.
  • the session management method further includes: the intermediate session management network element receives application identification information corresponding to one or more local DNAIs; correspondingly, the first message further carries application identification information corresponding to the target DNAI, and the target DNAI The corresponding application identification information is used to generate a local routing rule, which is used to offload data to a local data network corresponding to the target DNAI.
  • the session management method further includes: the intermediate session management network element receives the second message from the mobility management network element, where the second message is used to indicate The session resource of the terminal on the intermediate session management network element and the intermediate user plane function network element is released; the intermediate session management network element releases the session resource of the terminal on the intermediate session management network element according to the second message; and the intermediate session management network
  • the third message is sent to the intermediate user plane function network element, and the third message is used to indicate that the session resource of the terminal on the intermediate user plane function network element is released.
  • the session management method further includes: determining, by the intermediate session management network element, the local session served by the terminal according to the target DNAI Manage network elements.
  • the intermediate session management network element determines, according to the target DNAI, a local session management network element serving as a terminal service, including: the intermediate session management network element selects local session management for the terminal according to the target DNAI and local configuration information.
  • Network element or:
  • the intermediate session management network element determines the local session management network element serving as the terminal service according to the target DNAI, and the method includes: the intermediate session management network element sends a fourth message to the network function storage network element, where the fourth message is sent. Carrying the target DNAI; the intermediate session management network element receives the information of the local session management network element from the network function storage network element; the intermediate session management network element determines the local session management network element serving as the terminal service according to the information of the local session management network element; or,
  • the intermediate session management network element determines, according to the target DNAI, a local session management network element serving as a terminal service, including: the intermediate session management network element selects a local location for the terminal according to the information of the target DNAI and the session access mode. Session management network element; or,
  • the intermediate session management network element determines the local session management network element serving as the terminal service according to the target DNAI, and the intermediate session management network element sends a fifth message to the mobility management network element, where the fifth message carries
  • the target session management network element receives the information of the local session management network element from the mobility management network element; the intermediate session management network element determines the local session management network element that is the terminal service according to the information of the local session management network element.
  • the session management method further includes: the intermediate session management network element sends a sixth message to the local session management network element, where the sixth message carries current location information of the terminal, and the current location information of the terminal is used to select a local user for the terminal. Face function network element.
  • the session access mode includes a ULCL mode; the session management method further includes: the intermediate session management network element receives application identification information locally corresponding to one or more DNAIs; correspondingly, the sixth message The application identification information corresponding to the target DNAI is also carried, and the application identification information corresponding to the target DNAI is used to generate a local routing rule, which is used to offload data to a local data network corresponding to the target DNAI.
  • the session access mode includes a multi-homing mode; the session management method further includes: the intermediate session management network element sends the local session management network element to the remote anchor session management network element.
  • the local IP address assigned by the terminal is used to send the terminal to the terminal through the remote anchor session management network element; or the intermediate session management network element sends a route advertisement to the terminal, where the route advertisement carries the local session management network element as The local IP address assigned by the terminal.
  • the session management method further includes: the intermediate session management network element sends the target DNAI to the remote anchor session management network element, where the target DNAI is used for charging and policy control.
  • the session management method further includes: the intermediate session management network element sends a request message to the local session management network element, where the request message is used to establish a path between the current access device of the terminal and the local user plane function network element, And establishing a path between the local user plane function network element and the remote anchor user plane function network element.
  • the session management method further includes: the intermediate session management network element sends a seventh message to the intermediate user plane function network element, where the seventh message is used to indicate that the session resource of the terminal on the intermediate user plane function network element is released.
  • the operation of the intermediate session management network element for example, the operation of the intermediate SMF network element in FIG. 7 or FIG. 8 and the related text descriptions are not described herein.
  • the embodiment of the present application further discloses a session management method, where the method includes: the intermediate session management network element receives one or more local data network access identifiers DNAI; and the intermediate session management network element is based on the current location information of the terminal. And one or more local DNAIs to determine the target DNAI; the intermediate session management network element selects a local user plane function network element for the terminal according to the target DNAI.
  • the session management method provided by the embodiment of the present application may further include: the intermediate session management network element sends the target rule to the local user plane function network element.
  • the session management method provided by the embodiment of the present application may further include: the intermediate session management network element receives the session access mode, the remote IP address, and the target DNAI from the remote session management network element or the policy control function network element. At least one of a local routing policy or application identification information corresponding to the target DNAI.
  • the session access mode is further configured to select a local user plane function network element for the terminal.
  • the session access mode includes an uplink classifier ULCL mode or a multi-homed multi-homing mode.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that, in order to implement the above functions, the foregoing intermediate session management network element includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide the function modules of the intermediate session management network element according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 9 shows a schematic structural diagram of an intermediate session management network element 90.
  • the intermediate session management network element 90 includes a transceiver module 901 and a processing module 902.
  • the transceiver module 901 is configured to receive one or more local DNAIs.
  • the processing module 902 is configured to determine, according to the current location information of the terminal, and the one or more local DNAIs, the target DNAI is used to select a local session management network element for the terminal.
  • the transceiver module 901 is further configured to send a first message to the mobility management network element, where the first message carries the target DNAI.
  • the transceiver module 901 is further configured to receive application identifier information corresponding to one or more local DNAIs; correspondingly, the first message further carries application identifier information corresponding to the target DNAI, and the application identifier corresponding to the target DNAI The information is used to generate a local routing rule that is used to offload data to a local data network corresponding to the target DNAI.
  • the transceiver module 901 is further configured to receive a second message from the mobility management network element, where the second message is used to indicate that the session resources of the terminal on the intermediate session management network element and the intermediate user plane function network element are released;
  • the 902 is further configured to: release, according to the second message, the session resource of the terminal on the intermediate session management network element; and the transceiver module 901 is further configured to send a third message to the intermediate user plane function network element, where the third message is used to indicate The session resources of the terminal on the intermediate user plane function network element are released.
  • the processing module 902 is further configured to determine, according to the target DNAI, a local session management network element serving as a terminal.
  • the processing module 902 is configured to determine, according to the target DNAI, a local session management network element serving as a terminal, and configured to: select, according to the target DNAI and local configuration information, a local session management network element for the terminal.
  • the processing module 902 is configured to determine, according to the target DNAI, a local session management network element serving as a terminal, including: sending, to the network function storage network element, a fourth message, where the fourth message carries the target DNAI; Information from the local session management network element of the network function storage network element.
  • the processing module 902 is configured to determine, according to the target DNAI, a local session management network element serving as a terminal, including: selecting, according to the information of the target DNAI and the session access mode, a local session management network element for the terminal.
  • the processing module 902 is configured to determine, according to the target DNAI, a local session management network element serving as a terminal, including: sending a fifth message to the mobility management network element, where the fifth message carries the target DNAI; The information of the local session management NE of the mobility management network element.
  • the transceiver module 901 is further configured to send a sixth message to the local session management network element, where the sixth message carries the current location information of the terminal, and the current location information of the terminal is used to select a local user plane function network element for the terminal. .
  • the sixth message further carries information about a session access mode, where the information of the session access mode is used to determine an access mode of the local session.
  • the session access mode includes a ULCL mode
  • the transceiver module 901 is further configured to receive application identification information corresponding to one or more DNAIs.
  • the sixth message further carries a corresponding identifier corresponding to the target DNAI.
  • the application identification information, the application identification information corresponding to the target DNAI is used to generate a local routing rule, and the local routing rule is used to offload data to the local data network corresponding to the target DNAI.
  • the session access mode includes a multi-homing mode
  • the transceiver module 901 is further configured to send, to the remote anchor session management network element, a local IP address assigned by the local session management network element to the terminal, where The local IP address is sent to the terminal through the remote anchor session management network element; or the transceiver module 901 is further configured to send a route advertisement to the terminal, where the route advertisement carries the local IP address allocated by the local session management network element to the terminal.
  • the transceiver module 901 is further configured to send the target DNAI to the remote anchor session management network element, where the target DNAI is used for charging and policy control.
  • the transceiver module 901 is further configured to send a request message to the local session management network element, where the request message is used to establish a path between the current access device of the terminal and the local user plane function network element, and establish a local user.
  • the transceiver module 901 is further configured to send a seventh message to the intermediate user plane function network element, where the seventh message is used to indicate that the session resource of the terminal on the intermediate user plane function network element is released.
  • the intermediate session management network element 90 includes the transceiver module 901 and the processing module 902, the transceiver module 901 is configured to receive one or more local DNAIs; the processing module 902 And determining, according to the current location information of the terminal, and one or more local DNAIs, the target DNAI, and selecting a local user plane function network element for the terminal according to the target DNAI.
  • the processing module 902 is further configured to acquire at least one of a session access mode, a remote IP address, a local routing policy corresponding to the target DNAI, or application identification information corresponding to the target DNAI; and according to the session access mode, At least one of a remote IP address, a local routing policy corresponding to the target DNAI, or application identification information corresponding to the target DNAI generates a target rule, where the target rule is used by the local user plane function network element to forward the received data packet.
  • the processing module 902 is further configured to obtain information about a session access mode, where the information of the session access mode is used to determine an access mode of the local session.
  • the one or more DNAIs are local DNAIs supported by the intermediate session management network element in the PCC rules corresponding to the one or more service data flows detected by the anchor user plane function network element.
  • the transceiver module 901 is further configured to send a request message to the remote anchor session management network element, where the request message is used to request the remote anchor session management network element to detect one of the anchor user plane function network elements.
  • the local DNAI supported by the intermediate session management network element in the PCC rule corresponding to the multiple service data flows is sent to the intermediate session management network element.
  • the transceiver module 901 is configured to receive one or more local DNAIs, including: for receiving one or more local DNAIs from a remote anchor session management network element or a policy control network element.
  • the intermediate session management network element 90 is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the intermediate session management network element 90 can take the form shown in FIG.
  • the processor 501 in FIG. 5 can execute the instruction by calling the computer stored in the memory 503, so that the intermediate session management network element 90 executes the session management method in the above method embodiment.
  • the function/implementation process of the transceiver module 901 and the processing module 902 in FIG. 9 can be implemented by the processor 501 in FIG. 5 calling a computer execution instruction stored in the memory 503.
  • the function/implementation process of the processing module 902 in FIG. 9 can be implemented by the processor 501 in FIG. 5 calling the computer execution instructions stored in the memory 503, and the function/implementation process of the transceiver module 901 in FIG.
  • the communication interface 503 in 5 is implemented.
  • the intermediate session management network element provided by the embodiment of the present application can perform the foregoing session management method. Therefore, the technical solution can be obtained by referring to the foregoing method embodiment, and details are not described herein again.
  • the embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support an intermediate session management network element to implement the foregoing session management method, for example, according to current location information of the terminal, and one or more local DNAI, the target DNAI is determined.
  • the chip system also includes a memory.
  • the memory is used to save necessary program instructions and data of the intermediate session management network element.
  • the memory may not be in the chip system.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供会话管理方法、设备及***，可以使得终端不在远端锚点SMF网元的管理区域时仍然可以通过本地UPF网元访问本地数据网络的问题。方法包括：中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；该中间会话管理网元根据终端的当前位置信息、以及该一个或多个本地DNAI，确定目标DNAI，该目标DNAI用于为该终端选择本地会话管理网元。

Description

会话管理方法、设备及***
本申请要求了2018年1月12日提交的、申请号为201810031226.6、发明名称为“会话管理方法、设备及***”的中国申请的优先权，以及2018年4月9日提交的、申请号为201810313129.6、发明名称为“会话管理方法、设备及***”的中国申请的优先权,以及2018年11月19日提交的、申请号为201811379260.9、发明名称为“会话管理方法、设备及***”的中国申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及会话管理方法、设备及***。
背景技术
在现有的第五代(5rd generation，5G)网络架构中，一个分组数据单元(packet data unit，PDU)会话由一个会话管理功能(session management function，SMF)网元管理。这意味着，在现有的5G网络架构中，当终端处于非漫游状态时，终端的PDU会话的用户面路径中的所有用户面功能(user plane function，UPF)网元均由一个SMF网元控制。比如，终端的PDU会话对应两个UPF网元，一个UPF网元位于靠近终端的接入设备的位置，而另外一个UPF网元位于中心机房，此时，管理该终端的PDU会话的SMF网元需要能控制这两个不同位置的UPF网元。
然而，上述5G网络架构与运营商的实际部署并不一致，在运营商的实际部署中，考虑到跨行政区域配置的复杂性以及运营商希望隐藏网络拓扑的需求，通常SMF网元和UPF网元均是按行政区域进行划分的。其中，为一个行政区域服务的SMF网元只能管理为该行政区域服务的UPF网元，不能管理为其它行政区域服务的UPF网元；并且，为该行政区域某些特殊区域服务的UPF网元也不能被为该行政区域服务的通用SMF网元管理。此时，如何进行会话管理，使得终端不在远端锚点SMF网元的管理区域时，仍然可以通过本地UPF网元访问本地数据网络，是目前研究的热点。
发明内容
本申请实施例提供会话管理方法、设备及***，可以使得终端不在远端锚点SMF网元的管理区域时仍然可以通过本地UPF网元访问本地数据网络的问题。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供一种会话管理方法，该方法包括：中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；该中间会话管理网元根据终端的当前位置信息、以及该一个或多个本地DNAI，确定目标DNAI，该目标DNAI用于为该终端选择本地会话管理网元。基于该方案，由于中间会话管理网元可以根据终端的当前位置信息、以及获取的一个或多个本地DNAI，确定目标DNAI，该目标DNAI用于为该终端选择本地会话管理网元，而本地会话管理网元可以管理为终端服务的本地用户面功能网元，因此可以使得终端不在远端锚点会话管理网元的管理区域时，仍然可以通过本地用户面功能网元访问本地数据网络。
在一种可能的设计中，在该中间会话管理网元确定目标DNAI之后，还包括：该中间会话管理网元向移动管理网元发送第一消息，该第一消息携带该目标DNAI。基于该方案，可以由 移动管理网元确定为终端服务的本地会话管理网元。
可选的，该目标DNAI还用于为该终端选择本地用户面功能网元。
可选的，该第一消息还携带会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
可选的，该会话接入模式还用于为该终端选择本地用户面功能网元或该本地会话管理网元中的至少一个。
可选的，该会话接入模式包括上行分类器ULCL模式或多穴Multi-homing模式。
在一种可能的设计中，该方法还包括：该中间会话管理网元接收与该一个或多个本地DNAI对应的应用标识信息；相应的，该第一消息还携带与该目标DNAI对应的应用标识信息，该与该目标DNAI对应的应用标识信息用于生成本地路由规则，该本地路由规则用于将数据分流到该目标DNAI对应的本地数据网络。
在一种可能的设计中，在该中间会话管理网元向移动管理网元发送第一消息之后，还包括：该中间会话管理网元接收来自该移动管理网元的第二消息，该第二消息用于指示释放该中间会话管理网元和中间用户面功能网元上该终端的会话资源；该中间会话管理网元根据该第二消息，释放该中间会话管理网元上该终端的会话资源；以及，该中间会话管理网元向该中间用户面功能网元发送第三消息，该第三消息用于指示释放该中间用户面功能网元上该终端的会话资源。基于该方案，一方面可以避免会话资源一直占用中间会话管理网元和中间用户面功能网元的存储空间，从而造成中间会话管理网元和中间用户面功能网元上存储资源的浪费；另一方面，在会话路径上***本地用户面功能网元之后，原会话路径上的中间会话管理网元和中间用户面功能网元分别被管理本地用户面功能网元的本地会话管理网元和本地用户面功能网元替换，这样可以使得移动管理网元和本地会话管理网元之间的控制面路径较短。
在一种可能的设计中，在该中间会话管理网元确定目标DNAI之后，还包括：该中间会话管理网元根据该目标DNAI，确定为该终端服务的该本地会话管理网元。基于该方案，可以由中间会话管理网元确定为终端服务的本地会话管理网元。
在一种可能的设计中，该中间会话管理网元根据该目标DNAI，确定为该终端服务的该本地会话管理网元，包括：该中间会话管理网元根据该目标DNAI和本地配置信息，为该终端选择该本地会话管理网元。
在一种可能的设计中，该中间会话管理网元根据该目标DNAI，确定为该终端服务的该本地会话管理网元，包括：该中间会话管理网元向网络功能存储网元发送第四消息，该第四消息携带该目标DNAI；该中间会话管理网元接收来自该网络功能存储网元的该本地会话管理网元的信息。
在一种可能的设计中，该中间会话管理网元根据该目标DNAI，确定为该终端服务的该本地会话管理网元，包括：该中间会话管理网元根据该目标DNAI和会话接入模式的信息，为该终端选择该本地会话管理网元。
在一种可能的设计中，该中间会话管理网元根据该目标DNAI，确定为该终端服务的该本地会话管理网元，包括：该中间会话管理网元向移动管理网元发送第五消息，该第五消息携带该目标DNAI；该中间会话管理网元接收来自该移动管理网元的该本地会话管理网元的信息。
在一种可能的设计中，该方法还包括：该中间会话管理网元向该本地会话管理网元发送第六消息，该第六消息携带该终端的当前位置信息，该终端的当前位置信息用于为该终端选择本地用户面功能网元。
在一种可能的设计中，该第六消息还携带会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
在一种可能的设计中，该会话接入模式包括ULCL模式；该方法还包括：该中间会话管理网元接收与该一个或多个DNAI本地对应的应用标识信息；相应的，该第六消息还携带与该目标DNAI对应的应用标识信息，该与该目标DNAI对应的应用标识信息用于生成本地路由规则，该本地路由规则用于将数据分流到该目标DNAI对应的本地数据网络。
在另一种可能的设计中，该会话接入模式包括Multi-homing模式；该方法还包括：该中间会话管理网元向远端锚点会话管理网元发送该本地会话管理网元为该终端分配的本地互联网协议IP地址，该本地IP地址用于通过该远端锚点会话管理网元发送给该终端；或者，该中间会话管理网元向该终端发送路由通告，该路由通告携带该本地会话管理网元为该终端分配的本地IP地址。基于该方案，可以在会话接入模式为Multi-homing模式时，使得终端获取本地IP地址。
在一种可能的设计中，该方法还包括：该中间会话管理网元向远端锚点会话管理网元发送该目标DNAI，该目标DNAI用于进行计费和策略控制。
在一种可能的设计中，该方法还包括：该中间会话管理网元向本地会话管理网元发送请求消息，该请求消息用于建立该终端的当前接入设备和本地用户面功能网元之间的路径，以及，建立该本地用户面功能网元和远端锚点用户面功能网元之间的路径。基于该方案，可以建立会话的用户面路径。
在一种可能的设计中，该方法还包括：该中间会话管理网元向中间用户面功能网元发送第七消息，该第七消息用于指示释放该中间用户面功能网元上该终端的会话资源。基于该方案，一方面可以避免会话资源一直占用中间用户面功能网元的存储空间，从而造成中间用户面功能网元上存储资源的浪费；另一方面，在会话路径上***本地用户面功能网元之后，原会话路径上的中间会话管理网元继续保留，中间用户面功能网元被本地会话管理网元和本地用户面功能网元替换，这样相当于本地会话管理网元是一个简化会话管理网元，即支持会话管理网元的部分功能，比如支持用户面功能网元的选择和控制功能，以及支持与上一层级的会话管理网元，如中间会话管理网元接口，根据中间会话管理网元的指令进行相应的操作等，不直接与其他控制面网元接口，从而可以减少该本地会话管理网元与其他控制面功能的接口数量，不仅可以屏蔽外部的网络拓扑，外部网元也不需要感知本地网络拓扑，从而可以降低网络配置的复杂度。
第二方面，提供了一种中间会话管理网元，该中间会话管理网元具有实现上述第一方面或下述第九方面中任一项所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第三方面，提供了一种中间会话管理网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该中间会话管理网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该中间会话管理网元执行如上述第一方面或下述第九方面中任一项所述的会话管理方法。
第四方面，提供了一种中间会话管理网元，包括：处理器；该处理器用于与存储器耦合，并读取存储器中的指令之后，根据该指令执行如上述第一方面或下述第九方面中任一项所述的会话管理方法。
第五方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当 其在计算机上运行时，使得计算机可以执行上述第一方面或下述第九方面中任一项所述的会话管理方法。
第六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面或下述第九方面中任一项所述的会话管理方法。
其中，第二方面至六方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第七方面，提供一种会话管理***，该会话管理***包括：中间会话管理网元和移动管理网元；该中间会话管理网元，用于接收一个或多个本地数据网络接入标识DNAI；该中间会话管理网元，还用于根据终端的当前位置信息、以及该一个或多个本地DNAI，确定目标DNAI；该中间会话管理网元，还用于向移动管理网元发送第一消息，该第一消息携带该目标DNAI；该移动管理网元，用于接收来自该中间会话管理网元的该第一消息，并根据该目标DNAI确定为该终端服务的本地会话管理网元。基于该会话管理***，由于移动管理网元可以根据目标DNAI确定为终端服务的本地会话管理网元，而本地会话管理网元可以管理为终端服务的本地用户面功能网元，因此可以使得终端不在远端锚点会话管理网元的管理区域时，仍然可以通过本地用户面功能网元访问本地数据网络。
在一种可能的设计中，该会话管理***包括：本地会话管理网元；该移动管理网元，还用于向该本地会话管理网元发送第二消息，该第二消息携带该终端的当前位置信息；该本地会话管理网元，用于接收来自该移动管理网元的该第二消息，并根据该终端的当前位置信息为确定该终端服务的本地用户面功能网元。基于该方案，可以确定为终端服务的本地用户面功能网元。
在一种可能的设计中，该第二消息还携带该目标DNAI；该本地会话管理网元，还用于向远端锚点会话管理网元发送该目标DNAI，该目标DNAI用于进行计费和策略控制。
在一种可能的设计中，该第一消息还携带会话接入模式的信息；相应的，该第二消息还携带该会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。基于该方式，可以在远端锚点会话管理网元和本地会话管理网元之间没有接口时，使得本地会话管理网元获取会话接入模式的信息。
在一种可能的设计中，该本地会话管理网元，还用于接收来自远端锚点会话管理网元的会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
在一种可能的设计中，该会话接入模式包括多穴Multi-homing模式；该本地会话管理网元，还用于为该终端分配本地互联网协议IP地址，以及，该本地会话管理网元，还用于接收远端锚点会话管理网元为该终端分配的远端IP地址；该本地会话管理网元，还用于通知本地用户面功能网元将源地址为本地IP地址的数据分流到该目标DNAI对应的本地数据网络，将源地址为远端IP地址的数据分流到远端锚点用户面功能网元。基于该方案，可以在会话模式为Multi-homing模式时，实现本地数据网络和远端数据网络的数据分流。
在一种可能的设计中，该本地会话管理网元，还用于向该远端锚点会话管理网元发送该本地IP地址，该本地IP地址用于通过该远端锚点会话管理网元发送给该终端；或者，该本地会话管理网元，还用于向该终端发送路由通告，该路由通告携带该本地IP地址。基于该方案，可以在会话接入模式为Multi-homing模式时，使得终端获取本地IP地址。
在一种可能的设计中，该会话接入模式包括上行分类器ULCL模式；该本地会话管理网元，还用于根据本地配置信息或者与该一个或多个本地DNAI对应的应用标识信息中的至少一个， 生成本地路由规则；该本地会话管理网元，还用于向本地用户面功能网元发送该本地路由规则，该本地路由规则用于将数据分流到该目标DNAI对应的本地数据网络。基于该方案，可以在会话模式为ULCL模式时，实现本地数据网络的数据分流。
在一种可能的设计中，该本地会话管理网元，还用于发起建立该终端的当前接入设备和该本地用户面功能网元之间的路径，以及，该本地用户面功能网元和远端锚点用户面功能网元之间的路径。基于该方案，可以建立会话的用户面路径。
第八方面，提供一种会话管理***，该会话管理***包括：中间会话管理网元和本地会话管理网元；该中间会话管理网元，用于接收一个或多个本地数据网络接入标识DNAI；该中间会话管理网元，还用于根据终端的当前位置信息、以及该一个或多个本地DNAI，确定目标DNAI；该中间会话管理网元，还用于根据该目标DNAI，确定为该终端服务的本地会话管理网元；该中间会话管理网元，还用于向该本地会话管理网元发送第一消息，该第一消息携带该终端的当前位置信息；该本地会话管理网元，用于接收来自该中间会话管理网元的该第一消息，并根据该终端的当前位置信息确定为该终端服务的本地用户面功能网元。基于该会话管理***，由于中间会话管理网元可以根据目标DNAI，确定为终端服务的本地会话管理网元，并向本地会话管理网元发送携带终端的当前位置信息的第一消息，使得本地话管理网元可以根据终端的当前位置信息为终端选择本地用户面功能网元，因此可以使得终端不在远端锚点会话管理网元的管理区域时，仍然可以通过本地用户面功能网元访问本地数据网络。
可选的，该第一消息还携带会话接入模式信息；该会话接入模式信息用于确定本地会话的接入模式。
第九方面，提供一种会话管理方法，该方法包括：中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；中间会话管理网元根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI；中间会话管理网元根据目标DNAI，为该终端选择本地用户面功能网元。
在一种可能的设计中，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元获取会话接入模式、远端互联网协议IP地址、目标DNAI对应的本地路由策略、或者目标DNAI对应的应用标识信息中的至少一个；中间会话管理网元根据会话接入模式、远端互联网协议IP地址、目标DNAI对应的本地路由策略、或者目标DNAI对应的应用标识信息中的至少一个，生成目标规则，该目标规则用于本地用户面功能网元对接收到的数据包进行转发。
在一种可能的设计中，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元获取会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
在一种可能的设计中，该会话接入模式还用于为该终端选择本地用户面功能网元。
在一种可能的设计中，该会话接入模式包括上行分类器ULCL模式或多穴Multi-homing模式。
在一种可能的设计中，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元向远端锚点会话管理网元发送该目标DNAI，该目标DNAI用于进行计费和策略控制。
结合上述第一方面或第九方面，在一种可能的设计中，该一个或多个本地DNAI是该终端的会话对应的策略和计费控制PCC规则中该中间会话管理网元所支持的本地DNAI。
结合上述第一方面或第九方面，在一种可能的设计中，该一个或多个DNAI是锚点用户面功能网元所检测到的一个或多个业务数据流所对应的PCC规则中该中间会话管理网元所支持的本地DNAI。
结合上述第一方面或第九方面，在一种可能的设计中，本申请实施例提供的会话管理方法还可以包括：该中间会话管理网元向远端锚点会话管理网元发送请求消息，该请求消息用于请求远端锚点会话管理网元将锚点用户面功能网元所检测到的一个或多个业务数据流所对应的PCC规则中该中间会话管理网元所支持的本地DNAI发送给该中间会话管理网元。
结合上述第一方面或第九方面，在一种可能的设计中，该请求消息中包括指示该中间会话管理网元所支持的一个或多个DNAI的信息。
结合上述第一方面或第九方面，在一种可能的设计中，该中间会话管理网元接收一个或多个本地DNAI，包括：该中间会话管理网元接收来自远端锚点会话管理网元或策略控制网元的一个或多个本地DNAI。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1为本申请实施例提供的不同网络对应的SMF网元和UPF网元的部署示意图；
图2为本申请实施例提供的会话管理***的架构示意图一；
图3为图2所示的会话管理***在5G网络中的应用示意图；
图4为本申请实施例提供的会话管理***的架构示意图二；
图5为图4所示的会话管理***在5G网络中的应用示意图；
图6为本申请实施例提供的通信设备的硬件结构示意图；
图7为本申请实施例提供的会话管理方法的流程示意图一；
图8为本申请实施例提供的会话管理方法的流程示意图二；
图9为本申请实施例提供的中间会话管理网元的结构示意图；
图10为本申请实施例提供的会话管理***的架构示意图三；
图11为图10所示的会话管理***在5G网络中的应用示意图；
图12为本申请实施例提供的会话管理方法的流程示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
首先给出本申请实施例所适用的一种可能的场景描述如下：
图1为不同网络对应的SMF网元和UPF网元的部署示意图。其中，图1中的(1a)为网络A对应的SMF网元和UPF网元的部署示意图；图1中的(1b)为网络B对应的SMF网元和UPF网元的部署示意图。在图1中的(1a)和(1b)中，虚线上面是为该网络服务的通用SMF网元和通用UPF网元，如网络A的SMF网元a1和SMF网元a2是为网络A服务的通用SMF网元，网络A的UPF网元a1、UPF网元a2和UPF网元a3是为网络A服务的通用UPF网元，网络B的SMF网元b1和SMF网元b2是为网络B服务的通用SMF网元，网络B的UPF网元b1、UPF网元b2和UPF网元b3是为网络B服务的通用UPF网元，这些通用SMF网元和通用UPF网元一般部署在位于汇聚层的中心城市的机房，用于支持本网络内的移动覆盖；虚线下面是为该网络内某些热点位置服务的专用SMF网元和专用UPF网元，如网络A的SMF网元a3和SMF网元a4是为网络A中的特殊区域服务的专用SMF网元，网络A的UPF网元a4和UPF网元a5是SMF网元a3管理的为网络A中的其中一个特殊区域服务的专用UPF网元，网络A的UPF网元a6和UPF网元a7是SMF网元a4管理的为网络A中的另外一个特殊区域服务的专用UPF网元，网络B的SMF网元b3和SMF网元b4是为网络B中的特殊区域服务的专用SMF网元，网络B的UPF网元b4和UPF网元b5是SMF网元b3管理的为网络B中的其中一个特殊区域服务的专用UPF网元，网络B的UPF网元b6和UPF网元b7是SMF网元b4管理的为网络B中的另外一个特殊区域服务的专用UPF网元，这些专用SMF网元和专用UPF网元通常部署在边缘位置，用于支持特殊业务和场景。
然而，为一个网络服务的SMF网元只能管理为该网络服务的UPF网元，不能管理为其它网络服务的UPF网元；并且，为该网络某些特殊区域服务的UPF网元也不能被为该网络服务的通用SMF网元管理。比如，为网络A服务的SMF网元a1只能管理为网络A服务的UPF网元a1、UPF网元a2或UPF网元a3，不能管理为网络B服务的UPF网元b1、UPF网元b2或UPF网元b3；为网络A中的特殊区域服务的UPF网元a4只能被为该特殊区域服务的SMF网元a3管理，不能被为网络A服务的SMF网元a1或SMF网元a2管理。
需要说明的是，本申请实施例中，一个数据网络可能由一个UPF网元服务，也可能由多个UPF网元服务，如图1中的数据网络1和数据网络4均由多个UPF网元服务，而图1中的数据网络2、数据网络3、数据网络5和数据网络6均由一个UPF网元服务，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中所述的“网络”具体是指某个行政区域所对应的网络，例如上海所对应的网络；而本申请实施例中的网络中的特殊区域例如可以是某个企业所在的区域，在此统一说明，本申请实施例对此不做具体限定。
基于上述场景，为使得终端不在远端锚点SMF网元的管理区域时仍然可以通过本地UPF网元访问本地数据网络，本申请实施例提供如下会话管理方法、设备及***，下面将分别介绍如下。
首先给出下述实施例所涉及的几个关键网元的介绍如下：
远端锚点用户面功能网元：本申请实施例中的远端锚点用户面功能网元为与远端数据网络连接的通用用户面功能网元，也可以称之为远端PDU会话锚点(PDU session anchor，PSA)，本申请实施例对此不作具体限定。
远端锚点会话管理网元：本申请实施例中的远端锚点会话管理网元为管理远端锚点用户面网元的通用会话管理网元。
中间用户面功能网元：本申请实施例中的中间用户面功能网元为与终端当前的接入网元接口的通用用户面功能网元。
中间会话管理网元：本申请实施例中的中间会话管理网元为管理中间用户面功能网元的通用会话管理网元。
本地用户面功能网元：本申请实施例中的本地用户面功能网元为与特定网络接口的专用用户面功能网元。
本地会话管理网元：本申请实施例中的本地会话管理网元管理本地用户面功能网元的专用会话管理网元。
需要说明的是，上述各个网元的名字仅是一个示例，名字对网元本身不构成限定。在具体实现时，还可能是其他的名字，本申请实施例对此不作具体限定。
在一种可能的实现方式中，如图2所示，为本申请实施例提供的一种会话管理***20，该会话管理***20包括中间会话管理网元201和移动管理网元202。
其中，中间会话管理网元201，用于接收一个或多个本地数据网络接入标识(data network access identifier，DNAI)，并根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI之后，向移动管理网元202发送第一消息，该第一消息携带目标DNAI。
移动管理网元202，用于接收来自中间会话管理网元201的第一消息，并根据目标DNAI确定为终端服务的本地会话管理网元。
可选的，本申请实施例中的中间会话管理网元201和移动管理网元202之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
基于该会话管理***，由于移动管理网元可以根据目标DNAI确定为终端服务的本地会话管理网元，而本地会话管理网元可以管理为终端服务的本地用户面功能网元，因此可以使得终端不在远端锚点会话管理网元的管理区域时，仍然可以通过本地用户面功能网元访问本地数据网络。
可选的，图2所示的会话管理***20可以应用于5G网络以及未来其它的网络，本发明实施例对此不作具体限定。
示例性的，假设图2所示的会话管理***20应用于5G网络，则如图3所示，上述的中间会话管理网元所对应的网元或者实体可以为5G网络中的中间SMF网元，上述的移动管理网元所对应的网元或者实体可以为5G网络中的接入和移动性管理功能(access and mobility management function，AMF)网元。
此外，如图3所示，该5G网络还可以包括接入网元、中间UPF网元、本地SMF网元、本地UPF网元、远端锚点SMF网元、远端锚点UPF网元以及策略控制功能(policy control function，PCF)网元等。假设终端移动前位于网络A，终端移动后位于网络B，则远端锚点SMF网元和远端锚点UPF网元为网络A服务，中间SMF网元、中间UPF网元、本地SMF网元和本地UPF网元为网络B服务。其中，中间SMF网元是为网络B服务的通用SMF网元，中间UPF网元是中间SMF网元管理的通用UPF网元，本地SMF网元是为网络B服务的专用SMF网元，本地UPF网元是本地SMF网元管理的专用UPF网元。
虽然未示出，上述5G网络还可以包括鉴权服务功能(authentication server function，AUSF)网元或者统一数据管理(unified data management，UDM)网元等，本申请实施例对此不做具体限定。
其中，终端通过接入网元接入网络，并且终端通过下一代网络(next generation，N) 接口1(简称N1)与AMF网元通信；接入网元通过N2接口(简称N2)与AMF网元通信，通过N3接口(简称N3)与中间UPF网元和本地UPF网元通信；AMF网元通过N11接口(简称N11)与中间SMF网元和本地SMF网元通信，通过N15接口(简称N15)与PCF网元通信；PCF网元通过N7接口(简称N7)与远端锚点SMF网元通信；中间SMF网元通过N4接口(简称N4)与中间UPF网元通信；远端锚点SMF网元通过N4与远端锚点UPF网元通信；本地SMF网元通过N4与本地UPF网元通信；远端锚点SMF网元通过N16*接口(简称N16*)与本地SMF网元和中间SMF网元通信；远端锚点UPF网元通过N9接口(简称N9)与中间UPF网元和本地UPF网元通信；远端锚点UPF网元通过N6接口(简称N6)接入远端数据网络，本地UPF网元通过N6接入本地数据网络。
在另一种可能的实现方式中，如图4所示，为本申请实施例提供的一种会话管理***40，该会话建立***40包括中间会话管理网元401和本地会话管理网元402。
其中，中间会话管理网元401，用于接收一个或多个本地数DNAI，并根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI之后，根据目标DNAI，确定为终端服务的本地会话管理网元。
中间会话管理网元401，还用于向本地会话管理网元402发送第一消息，该第一消息携带终端的当前位置信息。
本地会话管理网元402，用于接收来自中间会话管理网元的第一消息，并根据终端的当前位置信息为终端选择本地用户面功能网元。
可选的，本申请实施例中的中间会话管理网元401和本地会话管理网元402之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
基于该会话管理***，由于中间会话管理网元可以根据目标DNAI，确定为终端服务的本地会话管理网元，并向本地会话管理网元发送携带终端的当前位置信息的第一消息，使得本地话管理网元可以根据终端的当前位置信息为终端选择本地用户面功能网元，因此可以使得终端不在远端锚点会话管理网元的管理区域时，仍然可以通过本地用户面功能网元访问本地数据网络。
可选的，图4所示的会话管理***40可以应用于5G网络以及未来其它的网络，本发明实施例对此不作具体限定。
示例性的，假设图4所示的会话管理***40应用于5G网络，则如图5所示，上述的中间会话管理网元所对应的网元或者实体可以为5G网络中的中间SMF网元，上述的本地会话管理网元所对应的网元或者实体可以为5G网络中的本地SMF网元。
此外，如图5所示，该5G网络还可以包括接入网元、AMF网元、中间UPF网元、本地UPF网元、远端锚点SMF网元、远端锚点UPF网元以及PCF网元等。假设终端移动前位于网元A，终端移动后位于网络B，则远端锚点SMF网元和远端锚点UPF网元为网络A服务，中间SMF网元、中间UPF网元、本地SMF网元和本地UPF网元为网络B服务。其中，中间SMF网元为为网络B服务的通用SMF网元，中间UPF网元为中间SMF网元管理的通用UPF网元，本地SMF网元为为网络B服务的专用SMF网元，本地UPF网元为本地SMF网元管理的专用UPF网元。
需要说明的是，本申请实施例中的本地SMF网元是一个简化SMF网元，即只支持SMF网元的部分功能，比如支持UPF网元的选择和控制功能，以及支持与上一层级的SMF网元，如本申请实施例中的中间SMF网元接口，根据中间SMF网元的指令进行相应的操作等，不直接与其他控制面网元接口，从而可以减少该本地SMF网元与其他控制面功能的接口数量，不仅 可以屏蔽外部的网络拓扑，外部网元也不需要感知本地网络拓扑，从而可以降低网络配置的复杂度。其中，该本地SMF网元也可以称之为本地用户面管理网元，本申请实施例对此不作具体限定。
虽然未示出，上述5G网络还可以包括AUSF网元或者UDM网元等，本申请实施例对此不做具体限定。
其中，终端通过接入网元接入网络，并且终端通过N1与AMF网元通信；接入网元通过N2与AMF网元通信，通过N3与中间UPF网元和本地UPF网元通信；AMF网元通过与中间SMF网元通信，通过N15与PCF网元通信；PCF网元通过N7与远端锚点SMF网元通信；中间SMF网元通过N4与中间UPF网元通信，通过Nxy接口(简称Nxy)与本地SMF网元通信；本地SMF网元通过N4*接口(简称N4*)与本地UPF网元通信；远端锚点SMF网元通过N4与远端锚点UPF网元通信，通过N16*与本地SMF网元和中间SMF网元通信；远端锚点UPF网元通过N9与中间UPF网元和本地UPF网元通信；远端锚点UPF网元通过N6接入远端DN，本地UPF网元通过N6接入本地DN。
在另一种可能的实现方式中，如图10所示，为本申请实施例提供的一种会话管理***100，该会话建立***100包括中间会话管理网元1001和本地用户面功能网元1002。
中间会话管理网元1001，用于接收一个或多个本地数DNAI，并根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI之后，根据目标DNAI，为终端选择本地用户面功能网元1002。
进而，中间会话管理网元1001可以通过本地用户面功能网元1002访问本地数据网络。
需要说明的是，本申请实施例中，为终端选择的本地用户面功能网元也就是将要为该终端服务的本地用户面功能网元，在此统一说明，以下不再赘述。
可选的，本申请实施例中的中间会话管理网元1001和本地用户面功能网元1002之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
基于该会话管理***，由于中间会话管理网元可以根据目标DNAI，确定为终端服务的本地用户面功能网元，因此可以使得终端不在远端锚点会话管理网元的管理区域时，仍然可以通过本地用户面功能网元访问本地数据网络。
可选的，图10所示的会话管理***100可以应用于5G网络以及未来其它的网络，本发明实施例对此不作具体限定。
示例性的，假设图10所示的会话管理***100应用于5G网络，则如图11所示，上述的中间会话管理网元1001所对应的网元或者实体可以为5G网络中的中间SMF网元，上述的本地用户面功能网元1002所对应的网元或者实体可以为5G网络中的本地UPF网元。此外，如图11所示，该5G网络还可以包括接入网元、AMF网元、中间UPF网元、远端锚点SMF网元、远端锚点UPF网元以及PCF网元等，与图5所示的5G网络类似。区别仅在于：在图11中，与本地数据网络连接的本地UPF网元通过N4接口(简称N4)与中间SMF网元通信，也就是说，图11中的本地UPF网元直接由中间SMF网元进行控制，不再需要本地SMF网元，其余相关描述可参考图5所示的实施例，在此不再赘述。
需要说明的是，图3或图5或者图11中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图3或图5或者图11中的接入网元、AMF网元、中间SMF网元、中间UPF网元、本地SMF网元、本地UPF网元、远端锚点SMF网元、远端锚点UPF网元以及PCF网元 等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入网元、AMF网元、中间SMF网元、中间UPF网元、本地SMF网元、本地UPF网元、远端锚点SMF网元、远端锚点UPF网元以及PCF网元所对应的网元或实体也可以是其他的名字，本申请实施例对此不作具体限定。例如，该本地UPF网元还有可能被替换为本地UPF或者本地UPF实体，等等，在此进行统一说明，以下不再赘述。
其中，在上述图3、图5或者图11所示的5G网络中，当终端从网络A移动到网络B之后，在会话路径上***本地UPF网元之前，在会话路径上***中间SMF网元和中间UPF网元可以使得会话对应的远端锚点SMF网元和远端锚点UPF网元不发生改变，从而可以保持会话的连续性。此时终端接入远端DN的路径为：经过接入网元和为网络B服务的中间UPF网元，接入为网络A服务的远端锚点UPF网元。而图3、图5或者图11的区别在于：图3所示的5G网络中，在会话路径上***本地UPF网元之后，原会话路径上的中间SMF网元和中间UPF网元分别被管理本地UPF网元的本地SMF网元和本地UPF网元替换，这样可以使得AMF网元和本地SMF网元之间的控制面路径较短；图11所示的5G网络中，在会话路径上***本地UPF网元之后，原会话路径上的中间SMF网元继续保留，中间UPF网元被本地UPF网元替换，这样可以使得终端可以通过本地UPF网元访问部署在本地数据网络中的应用，从而减少访问应用的时延，节省网络的传输资源；而图5所示的5G网络中，在会话路径上***本地UPF网元之后，原会话路径上的中间SMF网元继续保留，中间UPF网元被本地SMF网元和本地UPF网元替换，这样如上所述，由于该本地SMF网元是一个简化SMF网元，因此不仅可以屏蔽外部的网络拓扑，外部网元也不需要感知本地网络拓扑，从而可以降低网络配置的复杂度。
可选的，本申请实施例中所涉及到的终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)或者中继用户设备等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。为方便描述，本申请中，上面提到的设备统称为终端。
可选的，本申请实施例中所涉及的接入网元指的是接入核心网的网元，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非第三代合作伙伴计划(3rd generation partnership project，3GPP)接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
可选的，图2中的中间会话管理网元或移动管理网元，或图4中的中间会话管理网元或本地会话管理网元，或者图10中的中间会话管理网元可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，图2中的中间会话管理网元或移动管理网元，或图4中的中间会话管理网元或本地会话管理网元，或者图10中的中间会话管理网元可以通过图6中的通信设备来实现。图6 所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备600包括至少一个处理器601，通信线路602，存储器603以及至少一个通信接口604。
处理器601可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路602可包括一通路，在上述组件之间传送信息。
通信接口604，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器603可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路602与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器603用于存储执行本申请方案的计算机执行指令，并由处理器601来控制执行。处理器601用于执行存储器603中存储的计算机执行指令，从而实现本申请下述实施例提供的会话管理方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器601可以包括一个或多个CPU，例如图6中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备600可以包括多个处理器，例如图6中的处理器601和处理器608。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信设备600还可以包括输出设备605和输入设备606。输出设备605和处理器601通信，可以以多种方式来显示信息。例如，输出设备605可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备606和处理器601通信，可以以多种方式接收用户的输入。例如，输入设备606可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备600可以是一个通用设备或者是一个专用设备。在具体实现中，通信设备600可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备或有图6中类似结构的设备。本申请实施例不限定通信设备600的类型。
下面将结合图1至图6对本申请实施例提供的会话管理方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等 只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
以图2所示的会话管理***应用于如图3所示的5G网络为例，如图7所示，为本申请实施例提供的一种会话管理方法，该会话管理方法包括如下步骤：
S701、终端从网络A移动到网络B之后，终端建立会话，该会话的远端锚点SMF网元所属的网络A与终端当前的接入网元所属的网络B不同。因此，该会话路径上除了为网络A服务的远端锚点SMF网元、以及远端锚点SMF网元管理的远端锚点UPF网元之外，还包括了为网络B服务的中间SMF网元、以及该中间SMF网元管理的中间UPF网元，此时，该会话的用户面路径为：终端<->中间UPF网元<->远端锚点UPF网元。
S702、在会话建立过程中，或者会话建立之后的任何时间，远端锚点SMF网元向中间SMF网元发送一个或多个本地DNAI，以使得中间SMF网元接收来自远端锚点SMF网元的一个或多个本地DNAI。
本申请实施例中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是该会话对应的PCC规则中的DNAI。
在一种实现方式中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是该会话所对应的PCC规则中包括的所有DNAI。例如，该会话所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4，则该一个或多个本地DNAI包括DNAI1和DNAI2、DNAI3和DNAI4。
或者，另一种实现方式中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是该会话所对应的PCC规则中中间SMF网元所支持的DNAI。比如，该会话所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4。中间SMF网元所支持的DNAI包括DNAI4和DNAI5，则该一个或多个本地DNAI包括DNAI4。
或者，另一种实现方式中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是该会话所对应的第一PCC规则中包括的DNAI，该第一PCC规则为包括中间SMF网元所支持的DNAI中的至少一个DNAI的PCC规则。比如，该会话所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4。中间SMF网元所支持的DNAI包括DNAI4和DNAI5，则该一个或多个本地DNAI包括PCC规则2中包括的DNAI3和DNAI4。
或者：
本申请实施例中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI也可以是锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则中的DNAI。远端锚点SMF网元可以向锚点UPF网元发送上报规则(Report Rule)，用于锚点UPF网元在检测到相应的业务数据流时给远端锚点SMF网元发送报告，从而远端锚点SMF网元获知锚点UPF网元所检测到的一个或多个业务数据流。
在一种实现方式中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则中包括的所有DNAI。例如，锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4，则该一个或多个本地DNAI包括DNAI1和DNAI2、DNAI3和DNAI4。相应的，远端锚点SMF网元发送给锚点UPF网元的上报规则可针对该会话对应的所有PCC规则中包括了一个或多个DNAI的PCC规 则所对应的业务数据流进行检测，当检测到对应的业务数据流时，锚点UPF网元给锚点SMF网元发送报告。
或者，另外一种实现方式中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则中中间SMF网元所支持的DNAI。例如，锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4。中间SMF网元所支持的DNAI包括DNAI4和DNAI5，则该一个或多个本地DNAI包括DNAI4。相应地，远端锚点SMF网元发送给锚点UPF网元的上报规则可针对该会话对应的所有PCC规则中包括了中间SMF网元所支持DNAI中至少一个的PCC规则所对应的业务数据流进行检测，当检测到对应的业务数据流时，锚点UPF网元给锚点SMF网元发送报告。
或者，另一种实现方式中，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是锚点UPF网元所检测到的一个或多个业务数据流所对应的第一PCC规则中包括的DNAI，该第一PCC规则为包括中间SMF网元所支持的DNAI中的至少一个DNAI的PCC规则。比如，锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4。中间SMF网元所支持的DNAI包括DNAI4和DNAI5，则该一个或多个本地DNAI包括PCC规则2中包括的DNAI3和DNAI4。相应的，远端锚点SMF网元发送给锚点UPF网元的上报规则可针对该会话对应的所有PCC规则中包括了中间SMF网元所支持DNAI至少一个的PCC规则所对应的业务数据流进行检测，当检测到对应的业务数据流时，锚点UPF网元给锚点SMF网元发送报告。
其中，在上述可选的实现方式中，对应锚点UPF网元检测到一个或多个业务数据流的场景，则可选的，中间SMF网元可以向远端锚点SMF网元订阅业务数据流发现报告，以便当远端锚点SMF网元获知锚点UPF网元所检测到的一个或多个业务数据流之后，向中间SMF网元发送上述一个或多个本地DNAI。
可选的，在订阅上述发现报告时，中间SMF网元可提供一组本地DNAI(包括一个或多个DNAI)，以便当远端SMF网元获知锚点UPF网元所检测到的一个或多个业务数据流，且该业务数据流对应的PCC规则中包括了该一组本地DNAI中的至少一个DNAI时再向中间SMF网元发送一个或多个本地DNAI。此时，相应的：
远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则中与一组本地DNAI有交集的DNAI。比如，锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4，一组本地DNAI中包括DNAI4和DNAI5，则远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI中包括DNAI4。相应地，远端锚点SMF网元发送给锚点UPF网元的上报规则可针对该会话对应的所有PCC规则中包括了一组本地DNAI中至少一个的PCC规则所对应的业务数据流进行检测，当检测到对应的业务数据流时，锚点UPF网元给锚点SMF网元发送报告。
或者，远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI可以是锚点UPF网元所检测到的一个或多个业务数据流所对应的第一PCC规则中包括的DNAI，该第一PCC规则为包括一组本地DNAI中的至少一个DNAI的PCC规则。比如，锚点UPF网元所检测到的一个或多个业务数据流所对应的PCC规则包括PCC规则1和PCC规则2。PCC规则1中包括DNAI1和DNAI2，PCC规则2中包括DNAI3和DNAI4。一组本地DNAI中包括DNAI4和DNAI5，则该一 个或多个本地DNAI包括PCC规则2中包括的DNAI3和DNAI4。相应地，远端锚点SMF网元发送给锚点UPF网元的上报规则可针对该会话对应的所有PCC规则中包括了一组本地DNAI中至少一个的PCC规则所对应的业务数据流进行检测，当检测到对应的业务数据流时，锚点UPF网元给锚点SMF网元发送报告。
可选的，本申请实施例中的一组本地DNAI可以是中间SMF网元所支持的DNAI，本申请实施例对此不作具体限定。此时，相应的，用于标识中间SMF网元所支持的DNAI的一个或多个DNAI的信息，例如可以是中间SMF网元的标识，远端锚点SMF网元根据中间SMF网元的标识确定中间SMF网元所支持的一个或多个DNAI；再例如，中间SMF网元的区域标识、中间SMF网元的集合标识等。在这些方式中，示例性地，远端锚点SMF网元配置这些标识与中间SMF网元所支持的一个或多个DNAI的对应管理，本申请实施例对此不作具体限定。
需要说明的是，上述仅是示例性的提供了几种远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI的确定方式，当然，还可以通过其他方式确定远端锚点SMF网元向中间SMF网元发送的一个或多个本地DNAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若中间SMF网元在订阅时只提供了一个DNAI，则远端SMF网元在发现了业务数据流，且该业务数据流对应的PCC规则中包括了该DNAI时，给中间SMF网元发送通知消息，该通知消息中可不携带DNAI，该通知消息用于指示一个支持该DNAI的业务数据流被发现。
可选的，本申请实施例中，该一个或多个本地DNAI可以是PCF网元发送给远端锚点SMF网元之后，经由远端锚点SMF网元直接转发给中间SMF网元的；也可以是远端锚点SMF网元接收来自PCF网元的多个本地DNAI之后，从多个本地DNAI中选择出该一个或多个本地DNAI发送给中间SMF网元的，本申请实施例对此不作具体限定。
可选的，本申请实施例中，远端锚点SMF网元还可以向中间SMF网元发送与一个或多个本地DNAI对应的应用标识信息，该应用标识信息可以包括应用标识或者五元组或者其他可以标识应用的信息等，本申请实施例对此不作具体限定。或者，可选的，本申请实施例中，也可以是在远端锚点SMF网元获知本地SMF网元的信息之后，再向本地SMF网元发送该应用标识信息，本申请实施例对此不作具体限定。其中，本申请实施例中的应用标识信息通常是由PCF网元发送给远端锚点SMF网元的，在此统一说明，以下不再赘述。
可选的，本申请实施例中，远端锚点SMF网元还可以向中间SMF网元发送会话接入模式的信息，该会话接入模式例如可以是上行分类器(uplink classifier，ULCL)模式或者多穴(multi-homing)模式等，本申请实施例对此不作具体限定。或者，可选的，也可以是在远端锚点SMF网元获知本地SMF网元的信息之后，再向本地SMF网元发送该会话接入模式的信息，本申请实施例对此不作具体限定。其中，本申请实施例中的会话接入模式的信息可以是由PCF网元发送给远端锚点SMF网元的，也可以是由远端锚点SMF网元确定的，本申请实施例对此不作具体限定。
可选地，本申请实施例中，若会话接入模式为multi-homing模式，则远端锚点SMF网元还可以将远端锚点SMF网元为终端分配的远端互联网协议(internet protocol，IP)地址发送给中间SMF网元，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若中间SMF网元与PCF网元之间有接口，PCF网元也可以将上述信息，如一个或多个本地DNAI、应用标识信息、会话接入模式的信息、或远端IP地址等直接发送给中间SMF网元，本申请实施例对此不作具体限定。
S703、中间SMF网元根据终端的当前位置信息，以及一个或多个本地DNAI，确定目标DNAI。
示例性的，若根据终端的当前位置信息确定终端的当前位置附近有比较接近的本地数据网络，则可以将该本地数据网络对应的本地DNAI确定为目标DNAI；或者，若根据终端的当前位置信息确定终端的当前位置附近有多个比较接近的本地数据网络，则可以将这多个本地数据网络中负载较低的本地数据网络对应的本地DNAI确定为目标DNAI，本申请实施例对此不作具体限定。
可选的，若根据终端的当前位置信息，以及一个或多个本地DNAI，确定没有目标DNAI，则中间SMF网元可以在终端的位置再次发生变更后，根据终端的当前位置信息，以及一个或多个本地DNAI，确定目标DNAI，本申请实施例对此不作具体限定。
可选的，若一个应用与一个或多个本地DNAI对应，中间SMF网元可以根据终端的位置信息从一个或多个本地DNAI中选择一个目标DNAI。
可选的，若在步骤S702中包括了多个应用，则中间SMF网元可以为每个应用选择一个目标DNAI。
S704、中间SMF网元向AMF网元发送***请求，以使得AMF网元接收来自中间SMF网元的***请求。其中，该***请求携带目标DNAI，用于请求***本地UPF网元。
可选的，若中间SMF网元可以获取与一个或多个本地DNAI对应的应用标识信息，则在中间SMF网元确定目标DNAI之后，该***请求还可以携带与目标DNAI对应的应用标识信息。
可选的，若中间SMF网元可以获取会话接入模式的信息，则该***请求还可以携带该会话接入模式的信息。
可选的，本申请实施例中，若会话接入模式为ULCL模式，则本地UPF网元具体可以为ULCL；若会话接入模式为multi-homing模式，则本地UPF网元可以为分支点(branching point，BP)，在此统一说明，以下不再赘述。
可选的，本申请实施例中，若会话接入模式为multi-homing模式，则该***请求中还可以携带远端锚点SMF网元为终端分配的远端IP地址，本申请实施例对此不作具体限定。
S705、AMF网元根据目标DNAI，确定为终端服务的本地SMF网元。
可选的，本申请实施例中，AMF网元根据目标DNAI，确定为终端服务的本地SMF网元具体可以包括：AMF网元根据目标DNAI和本地配置信息，为终端选择本地SMF网元；或者，
可选的，本申请实施例中，AMF网元根据目标DNAI，确定为终端服务的本地SMF网元具体可以包括：AMF网元向网络功能存储网元，例如网元功能存储功能(network Function repository function，NRF)网元请求该本地SMF网元的信息，由NRF网元根据目标DNAI为终端选择本地SMF网元之后，向AMF网元发送该本地SMF网元的信息。本申请实施例对AMF网元如何根据目标DNAI，确定为终端服务的本地SMF网元的方式不作具体限定。
可选的，本申请实施例中，若***请求还携带会话接入模式的信息，则AMF网元在确定为终端服务的本地SMF网元时除了考虑目标DNAI之外，还可以考虑该会话接入模式的信息，比如，AMF网元或者NRF网元选择支持该会话接入模式的本地SMF网元，本申请实施例对此不作具体限定。
S706、AMF网元向本地SMF网元发送会话建立请求，以使得本地SMF网元接收来自AMF网元的会话建立请求。其中，该会话建立请求携带终端的当前位置信息。
可选的，本申请实施例中，若AMF网元还可以获取会话接入模式的信息，则该会话建立请求还可以携带该会话接入模式的信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若AMF网元还可以获取与目标DNAI对应的应用标识信息，则该会话建立请求还可以携带与目标DNAI对应的应用标识信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若本地SMF网元支持多个本地数据网络，则该会话建立请求还可以携带目标DNAI，该目标DNAI用于指示终端当前接入的本地数据网络，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若AMF网元还可以获取远端IP地址，则该会话建立请求还可以携带该远端IP地址，本申请实施例对此不作具体限定。
可选的，本申请实施例中，该会话建立请求还可以携带远端锚点SMF网元的信息，用于本地SMF网元与远端SMF通信，本申请实施例对此不作具体限定。
S707、本地SMF网元根据终端的当前位置信息，确定为终端服务的本地UPF网元。
可选的，本申请实施例中，本地SMF网元根据终端的当前位置信息，确定为终端服务的本地UPF网元具体可以包括：本地SMF网元根据终端的当前位置信息，为终端选择本地UPF网元；或者:
可选的，本申请实施例中，本地SMF网元根据终端的当前位置信息，确定为终端服务的本地UPF网元具体可以包括：本地SMF网元向网络功能存储网元，例如NRF网元请求该本地UPF网元的信息，由NRF网元根据终端的当前位置信息为终端选择本地UPF网元之后，向本地SMF网元发送该本地UPF网元的信息。本申请实施例对本地SMF网元如何根据终端的当前位置信息，确定为终端服务的本地UPF网元的方式不作具体限定。
可选的，本申请实施例中，若会话建立请求中携带会话接入模式的信息，则本地SMF在确定为终端服务的本地UPF网元时除了考虑终端的位置信息之外，还可以考虑该会话接入模式的信息，比如，本地SMF网元或NRF网元选择支持该会话接入模式的本地UPF网元，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若会话建立请求中携带目标DNAI，则本地SMF在确定为终端服务的本地UPF网元时还可以考虑该目标DNAI，比如，本地SMF网元或NRF网元选择与该目标DNAI对应的本地数据网络连接的本地UPF网元，本申请实施例对此不作具体限定。
S708、本地SMF网元向本地UPF网元发送N4会话建立请求1，以使得本地UPF网元接收来自本地SMF网元的N4会话建立请求1。其中，该N4会话建立请求1用于在本地UPF网元上创建相应的会话。
可选的，若此时本地SMF网元可以获取会话接入模式的信息，且会话接入模式的信息对应的会话接入模式为multi-homing模式，则本地SMF网元还可以为该终端分配本地IP地址，并通过N4会话建立请求1通知本地UPF网元将源地址为本地IP地址的数据包分流到目标DNAI对应的本地数据网络，本申请实施例对此不作具体限定。其中，通知本地UPF网元将源地址为本地IP地址的数据分流到目标DNAI对应的本地数据网络的方式可以是本地SMF网元生成第一本地路由规则后，将该第一本地路由规则通过N4会话建立请求1发送给本地UPF网元，该第一本地路由规则用于将源地址为本地IP地址的数据包分流到目标DNAI对应的本地数据网络，本申请实施例对此不作具体限定。
可选的，若此时本地SMF网元可以获取会话接入模式的信息，且会话接入模式的信息对应的会话接入模式为multi-homing模式，同时本地SMF网元可以获取远端IP地址，则本地SMF网元还可以通过N4会话建立请求1通知本地UPF网元将源地址为远端IP地址的数据分 流到远端锚点UPF网元，其中，通知本地UPF网元将源地址为远端IP地址的数据分流到远端锚点UPF网元的方式可以是本地SMF网元生成远端路由规则后，将该远端路由规则通过N4会话更新请求1发送给本地UPF网元，该远端路由规则用于将源地址为远端IP地址的数据包分流到远端锚点UPF网元。
当然，若可以同时生成第一本地路由规则和远端路由规则，则该第一本地路由规则和远端路由规则也可以是通过不同的消息发送给本地UPF网元，本申请实施例对此不作具体限定。
可选的，若此时本地SMF网元可以获取会话接入模式的信息，且会话接入模式的信息对应的会话接入模式为ULCL模式，则本地SMF网元可以根据本地配置信息或者与目标DNAI对应的应用标识信息中的至少一个，生成第二本地路由规则后，将该第二本地路由规则通过N4会话建立请求1发送给本地UPF网元，该第二本地路由规则用于将数据分流到目标DNAI对应的本地数据网络，本申请实施例对此不作具体限定。其中，生成第二路由规则所需的与目标DNAI对应的应用标识信息可以是携带在步骤S706中的会话建立请求中，也可以是根据步骤S706中的会话建立请求中携带的远端锚点SMF网元的信息，和远端锚点SMF网元通信后，由远端锚点SMF网元发送给本地SMF网元的(比如在后续步骤S712发送给本地SMF网元)，本申请实施例对此不作具体限定。
可选的，本申请实施例中，本地UPF网元还可以向本地SMF网元发送与N4会话建立请求1对应的N4会话建立响应1，本申请实施例对此不作具体限定。
S709、本地SMF网元向远端锚点SMF网元发送会话更新请求1，以使得远端锚点SMF网元接收来自本地SMF网元的会话更新请求1。其中，该会话更新请求用于将远端锚点UPF网元的下行隧道更新为连接到本地UPF网元。
可选的，该会话更新请求1可以携带本地UPF网元的下行隧道信息，该本地UPF网元的下行隧道信息例如可以包括远端锚点UPF网元和本地UPF网元之间的N9隧道在该本地UPF网元侧的隧道标识，该隧道标识例如可以包括端点地址或端点标识，该端点标识例如可以是隧道端点标识(tunnel endpoint identifier，TEID)等，本申请实施例对此不作具体限定。其中，该本地UPF网元的下行隧道信息可以是本地SMF网元分配的，也可以是本地UPF网元分配后发送给本地SMF网元的，本申请实施例对此不作具体限定。
可选的，若此时本地SMF网元可以获取会话接入模式的信息，且会话接入模式的信息对应的会话接入模式为multi-homing模式，则该会话更新请求1中还可以携带本地SMF网元为终端分配的本地IP地址。
可选的，本申请实施例中，若此时本地SMF网元可以获取目标DNAI，则该会话更新请求1还可以携带目标DNAI，该目标DNAI用于进行计费和策略控制，例如，远端锚点SMF网元可根据该目标DNAI确定哪些计费和策略控制规则应由本地UPF网元执行，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若由本地SMF网元分配该本地UPF网元的下行隧道信息，则步骤S708和步骤S709之间没有必然的执行先后顺序，可以是先执行步骤S708，再执行步骤S709；也可以是先执行步骤S709，再执行步骤S708；还可以是同时执行步骤S708和S709，本申请实施例对此不作具体限定。
S710、远端锚点SMF网元向远端锚点UPF网元发送N4会话更新请求1，以使得远端锚点UPF网元接收来自远端锚点SMF网元的N4会话更新请求1。
其中，该N4会话更新请求1携带本地UPF网元的下行隧道信息，用于建立本地UPF网元 和远端锚点UPF网元之间的N9隧道。
可选的，本申请实施例中，远端锚点UPF网元还可以向远端锚点SMF网元发送与N4会话更新请求1对应的N4会话更新响应1，本申请实施例对此不作具体限定。
S711、远端锚点SMF网元向PCF网元发送策略和计费控制(policy and charge control，PCC)更新请求，以使得PCF网元接收来自远端锚点SMF网元的PCC更新请求。其中，该PCC更新请求携带目标DNAI，用于进行计费和策略控制。
可选的，该PCC更新请求可以携带本地SMF网元为终端分配的本地IP地址，本申请实施例对此不作具体限定。
可选的，本申请实施例中，步骤S710和步骤S711之间没有必然的执行先后顺序，可以是先执行步骤S710，再执行步骤S711；也可以是先执行步骤S711，再执行步骤S710；还可以是同时执行步骤S710和S711，本申请实施例对此不作具体限定。
可选的，若上述过程中本地SMF网元还未为终端分配本地IP地址，则本地SMF网元可以在后续为终端分配本地IP地址之后，向远端锚点SMF网元发送给本地IP地址(比如在后续步骤S718中发送给远端锚点SMF网元)，由远端锚点SMF网元向PCF网元发送该本地IP地址，本申请实施例对此不作具体限定。
可选的，本申请实施例中，PCF网元还可以向远端锚点SMF网元发送与PCC更新请求对应的PCC更新响应，本申请实施例对此不作具体限定。
S712、远端锚点SMF网元向本地SMF网元发送会话更新响应1，以使得本地SMF网元接收来自远端锚点SMF网元的会话更新响应1。
其中，该会话更新响应1携带远端锚点UPF网元的上行隧道信息，该远端锚点UPF网元的上行隧道信息例如可以包括远端锚点UPF网元和本地UPF网元之间的N9隧道在该远端锚点UPF网元侧的隧道标识，该隧道标识例如可以包括端点地址或端点标识，该端点标识例如可以是TEID等，本申请实施例对此不作具体限定。其中，该远端锚点UPF网元的上行隧道信息可以是远端锚点SMF网元分配的，也可以是远端锚点UPF网元分配后发送给远端锚点SMF网元的，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若步骤S702中远端锚点SMF网元未将会话接入模式的信息发送给中间SMF网元，则步骤S712中的会话更新响应1中可以携带该会话接入模式的信息。
可选的，本申请实施例中，若步骤S702中远端锚点SMF网元未将与一个或多个本地DNAI对应的应用标识信息发送给中间SMF网元，则步骤S712中的会话更新响应1中可以携带该与一个或多个本地DNAI对应的应用标识信息或者携带与目标DNAI对应的应用标识信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若会话接入模式为multi-homing模式，则该会话更新响应1中还可以携带远端锚点SMF网元为终端分配的远端IP地址，本申请实施例对此不作具体限定。
S713、本地SMF网元向AMF网元发送会话建立响应，以使得AMF网元接收来自本地SMF网元的会话建立响应。
可选的，若该会话当前处于激活状态，则该会话建立响应中还可以携带本地UPF网元的上行隧道信息，该本地UPF网元的上行隧道信息用于建立本地UPF网元与接入网元之间的N3隧道。其中，该本地UPF网元的上行隧道信息例如可以包括本地UPF网元与接入网元之间的N3隧道在该本地UPF网元侧的隧道标识，该隧道标识例如可以包括端点地址或端点标识，该端点标识例如可以是TEID等，本申请实施例对此不作具体限定。
S714、AMF网元向接入网元发送N2会话管理(session management，SM)请求，以使得接入网元接收来自AMF网元的N2SM请求。
其中，该N2SM请求携带本地UPF网元的上行隧道信息，用于建立本地UPF网元和接入网元之间的N3隧道。此外，该N2SM请求还用于为会话分配无线资源。
S715、接入网元向AMF网元发送N2SM响应，以使得AMF网元接收来自接入网元的N2SM响应。
其中，该N2SM响应携带接入网元的下行隧道信息。该接入网元的下行隧道信息用于建立本地UPF网元与接入网元之间的N3隧道。其中，该接入网元的下行隧道信息例如可以包括本地UPF网元与接入网元之间的N3隧道在该接入网元侧的隧道标识，该隧道标识例如可以包括端点地址或端点标识，该端点标识例如可以是TEID等，本申请实施例对此不作具体限定。
可选地，本申请实施例中，接入网元在向AMF网元发送N2SM响应之前还可以根据需要为该会话配置无线资源，本申请实施例对此不作具体限定。
S716、AMF网元向本地SMF网元发送会话更新请求2，以使得本地SMF网元接收来自AMF网元的会话更新请求2。
其中，该会话更新请求2携带接入网元的下行隧道信息。
可选的，本申请实施例中，本地SMF网元还可以向AMF网元发送与会话更新请求2对应的会话更新响应2，本申请实施例对此不作具体限定。
S717、本地SMF网元向本地UPF网元发送N4会话更新请求2，以使得本地UPF网元接收来自本地SMF网元的N4会话更新请求2。其中，该N4会话更新请求2用于更新本地UPF网元上相应的会话。
其中，该N4会话更新请求2携带远端锚点UPF网元的上行隧道信息，用于建立远端锚点UPF网元和本地UPF网元之间的N9隧道；以及，该N4会话更新请求2携带接入网元的下行隧道信息，用于建立接入网元和本地UPF网元之间的N3隧道。
可选的，本申请实施例中，若本地SMF网元在步骤S706之后可以获取会话接入模式的信息，且会话接入模式的信息对应的会话接入模式为multi-homing模式，但是本地SMF网元无法获知远端IP地址的信息，则此时本地SMF网元还可以通知本地UPF网元将源地址为远端IP地址的数据分流到远端锚点UPF网元，其中，本地SMF网元通知本地UPF网元将源地址为远端IP地址的数据分流到远端锚点UPF网元的方式可参考步骤S708中的描述，在此不再赘述。
可选的，本申请实施例中，若本地SMF网元在步骤S712中才获得会话接入模式的信息，且会话接入模式是multi-homing模式，则本地SMF网元此时为终端分配本地IP地址，并通知本地UPF网元将源地址为本地IP地址的数据分流到目标DNAI对应的本地数据网络，将源地址为远端IP地址的数据分流到远端锚点UPF网元。其中，通知本地UPF网元将源地址为本地IP地址的数据分流到目标DNAI对应的本地数据网络的方式、以及通知本地UPF网元将源地址为远端IP地址的数据分流到远端锚点UPF网元的方式可参考步骤S708中的相关描述，在此不再赘述。
可选的，本申请实施例中，若本地SMF网元在步骤S712中才获得会话接入模式的信息，且会话接入模式是ULCL模式，则此时本地SMF网元可以根据本地配置信息或者目标DNAI对应的应用标识信息中的至少一个，生成第二本地路由规则后，将该第二本地路由规则通过N4会话更新请求2发送给本地UPF网元，该第二本地路由规则用于将数据分流到目标DNAI对应 的本地数据网络，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若本地SMF网元在步骤S712中才获得会话接入模式的信息，且由本地SMF网元分配本地UPF网元的下行隧道信息，则本地SMF网元可以不用执行步骤S708；或者，可选的，本申请实施例中，若本地SMF网元通过步骤S706获取了会话接入模式的信息，但是会话接入模式为multi-homing模式，则本地SMF网元可以不用在步骤S706之后为终端分配本地IP地址，而是在步骤S712之后，为终端分配本地IP地址，并生成上述的第一本地路由规则后，通过N4会话建立请求2发送给本地UPF网元，本申请实施例对此不作具体限定。
可选的，本申请实施例中，本地UPF网元还可以向本地SMF网元发送与N4会话更新请求2对应的N4会话更新响应2，本申请实施例对此不作具体限定。
S718、本地SMF网元向远端锚点SMF网元发送通知消息，以使得远端锚点SMF网元接收来自本地SMF网元的通知消息。其中，该通知消息携带本地SMF网元为终端分配的本地IP地址。
需要说明的是，步骤S718是个可选的步骤，对应的是本地SMF网元在步骤S712中才获得会话接入模式的信息情况。当然，若在步骤S706之后，本地SMF网元根据会话接入模式的信息为终端分配了本地IP地址，则该本地IP地址可以携带在步骤S709的会话更新请求1中，本申请实施例对此不作具体限定。
S719、远端锚点SMF网元向终端发送路由通告(router advertisement，RA)，以使得终端接收来自远端锚点SMF网元的路由通告。其中，该路由通告携带本地IP地址。
本申请实施例中，远端锚点SMF网元通过用户面向终端发送路由通告，该用户面是指远端锚点UPF网元和本地UPF网元之间的N9隧道，在此统一说明，以下不再赘述。
需要说明的是，步骤S719是个可选的步骤，对应的是会话接入模式为multi-homing模式的情况，在此统一说明，以下不再赘述。
可选的，该路由通告也可以是在本地SMF网元为终端分配本地IP地址后，由本地SMF网元发送给终端，本申请实施例对此不作具体限定。
S720、AMF网元向中间SMF网元发送会话释放请求1，以使得中间SMF网元接收来自AMF网元的会话释放请求1。其中，该会话释放请求1用于指示释放中间SMF网元上和中间UPF网元上该终端的会话资源。
可选的，该会话释放请求1中可以携带一个指示信息，该指示信息用于指示仅释放中间SMF网元上和中间UPF网元上该终端的会话资源，不释放远端锚点SMF网元上该终端的会话资源，这样，中间SMF网元接收到该会话释放请求后，可以释放中间SMF网元上该终端的会话资源，不释放远端锚点SMF网元上该终端的会话资源。
S721、中间SMF网元向中间UPF网元发送会话释放请求2，以使得中间UPF网元接收来自中间SMF网元的会话释放请求2。其中，该会话释放请求2用于指示释放中间UPF网元上该终端的会话资源。
这样，中间UPF网元在接收该会话释放请求2之后，可以释放中间UPF网元上该终端的会话资源。
S722、在中间UPF网元上该终端的会话资源释放结束之后，中间UPF网元向中间SMF网元发送会话释放响应2。其中，该会话释放响应2用于指示中间UPF网元上该终端的会话资源释放结束。
S723、在中间UPF网元和中间SMF网元上该终端的会话资源释放结束之后，中间SMF网 元向AMF网元发送会话释放请求1。其中，该会话释放响应2用于指示中间UPF网元和中间SMF网元上该终端的会话资源释放结束。
至此，该会话路径上除了为网络A服务的远端锚点SMF网元、以及远端锚点SMF网元管理的远端锚点UPF网元之外，还包括了为网络B服务的本地SMF网元、以及该本地SMF网元管理的本地UPF网元，此时，该会话的用户面路径为：终端<->本地UPF网元<->远端锚点UPF网元。
基于本申请实施例提供的会话管理方法，可以使得终端不在远端锚点SMF网元的管理区域时，仍然可以通过本地UPF网元访问本地数据网络。
其中，上述步骤S701至S723中的中间SMF网元的动作可以由图6所示的通信设备600中的处理器601调用存储器603中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图4所示的会话管理***应用于如图5所示的5G网络为例，如图8所示，为本申请实施例提供的另一种会话管理方法，该会话管理方法包括如下步骤：
S801、同步骤S701，具体可参考图7所示的实施例，在此不再赘述。
S802、与步骤S702类似，区别在于本实施例中，由于远端锚点SMF网元和本地SMF网元之间没有接口，因此会话接入模式的信息以及与一个或多个本地DNAI对应的应用标识信息只能由远端锚点SMF网元发送给中间SMF网元，而不能像图7所示的实施例一样，可以在远端锚点SMF网元获知本地SMF网元的信息之后，再向本地SMF网元发送该与一个或多个本地DNAI对应的应用标识信息和会话接入模式的信息，相关描述可参考图7所示的实施例，在此不再赘述。
可选的，本申请实施例中，远端锚点SMF网元还可以向中间SMF网元发送一个或多个本地DNAI对应的本地路由策略，本申请实施例对此不作具体限定。
S803、同步骤S703，相关描述可参考图7所示的实施例，在此不再赘述。
可选的，本申请实施例中，中间SMF网元在从一个或多个本地DNAI中确定目标DNAI之后，可以根据会话接入模式、远端IP地址、目标DNAI对应的本地路由策略、或者目标DNAI对应的应用标识信息中的至少一个，生成目标规则，该目标规则用于本地UPF网元对接收到数据包进行转发，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中的目标规则也可以称之为安装在本地UPF网元上的规则，本申请实施例对此不作具体限定。
可选的，本申请实施例中的本地UPF网元可以包括本地锚点UPF网元和ULCL/BP，该本地锚点UPF网元和ULCL/BP可以是分开独立部署的，也可以是合一部署的，本申请实施例对此不作具体限定。其中，本地锚点UPF网元为与目标DNAI接口的UPF网元；ULCL/BP为与终端当前的接入设备接口的UPF网元，在此统一说明，以下不再赘述。
可选的，若本申请实施例中的本地锚点UPF网元与ULCL/BP是分开部署的，则本申请实施例中的安装在本地UPF网元上的规则可以包括安装在本地锚点UPF网元上的规则或者安装在ULCL/BP上的规则中的至少一个，在此统一说明，以下不再赘述。
S804、中间SMF网元根据目标DNAI，确定为终端服务的本地SMF网元。
可选的，本申请实施例中，中间SMF网元根据目标DNAI，确定为终端服务的本地SMF网元具体可以包括：中间SMF网元根据目标DNAI和本地配置信息，为终端选择本地SMF网元；或者:
可选的，本申请实施例中，中间SMF网元根据目标DNAI，确定为终端服务的本地SMF网元具体可以包括：中间SMF网元向网络功能存储网元，例如NRF网元请求该本地SMF网元的信息，由NRF网元根据目标DNAI为终端选择本地SMF网元之后，向中间SMF网元发送该本地SMF网元的信息；或者:
可选的，本申请实施例中，中间SMF网元根据目标DNAI，确定为终端服务的本地SMF网元具体可以包括：中间SMF网元向AMF网元请求该本地SMF网元的信息，由AMF网元根据目标DNAI为终端选择本地SMF网元之后，向中间SMF网元发送该本地SMF网元的信息。本申请实施例对中间网元如何根据目标DNAI，确定为终端服务的本地SMF网元的方式不作具体限定。
可选的，本申请实施例中，若中间SMF网元还可以获取会话接入模式的信息，则中间SMF网元在确定为终端服务的本地SMF网元时还可以考虑该会话接入模式的信息，比如，中间SMF网元或NRF网元或AMF网元选择支持该会话接入模式的本地SMF网元，本申请实施例对此不作具体限定。
S805、与步骤S706类似，区别仅在于将图7所示的实施例中的AMF网元替换为本申请实施例中的中间SMF网元；以及，本申请实施例中，该会话建立请求中还可以携带远端锚点UPF网元的上行隧道信息，相关描述可参考图7所示的实施例，在此不再赘述。
可选的，本申请实施例中，若中间SMF网元可以获取目标规则，则步骤S805中的会话建立请求中还可以携带该目标规则，本申请实施例对此不作具体限定。
S806、同步骤S707，相关描述可参考图7所示的实施例，在此不再赘述。
S807、与步骤S708类似，区别仅在于本实施例步骤S807中本地SMF网元向本地UPF网元发送的是N4*会话建立请求1，且该N4*会话建立请求1中还可以携带S712中的远端锚点UPF网元的上行隧道信息，相关描述可参考图7所示的实施例，在此不再赘述。
可选的，本申请实施例中，若在步骤S805中本地SMF网元获得了目标规则，则步骤S807中的N4*会话更新请求1中还可以携带上述目标规则，本申请实施例对此不作具体限定。
S808、本地SMF网元向中间SMF网元发送会话建立响应，以使得中间SMF网元接收来自本地SMF网元的会话建立响应。
其中，该会话建立响应携带本地UPF网元的下行隧道信息，该本地UPF网元的下行隧道信息的相关描述可参考图7所示的实施例的步骤S709，在此不再赘述。
可选的，若本地SMF网元可以获取会话接入模式的信息，且该会话接入模式的信息对应的会话接入模式为multi-homing模式，则该会话建立响应中还携带本地SMF网元为终端分配的本地IP地址，本申请实施例对此不作具体限定。
可选的，若本地SMF网元可以获取目标DNAI，则该会话建立响应中还可以携带目标DNAI，该目标DNAI用于进行计费和策略控制，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若由本地SMF网元分配该本地UPF网元的下行隧道信息，则步骤S807和步骤S808之间没有必然的执行先后顺序，可以是先执行步骤S807，再执行步骤S808；也可以是先执行步骤S808，再执行步骤S807；还可以是同时执行步骤S807和S808，本申请实施例对此不作具体限定。
S809、与步骤S709类似，区别仅在于将图7所示的实施例步骤S709中的本地SMF网元替换为本申请实施例中的中间SMF网元，相关描述可参考图7所示的实施例，在此不再赘述。
S810-S811、同步骤S710-S711，相关描述可参考图7所示的实施例，在此不再赘述。
S812、远端锚点SMF网元向中间SMF网元发送会话更新响应1，以使得中间SMF网元接 收来自远端锚点SMF网元的会话更新响应1。
可选的，本申请实施例中，若会话接入模式为multi-homing模式，则该会话更新响应1中还可以携带远端锚点SMF网元为终端分配的远端IP地址，该远端IP地址可用于中间SMF网元或本地SMF网元生成用于安装在本地UPF网元上的上行分流规则。其中，当ULCL与本地锚点UPF网元合一部署时，该上行分流规则用于本地UPF网元按照数据包的源地址将数据分别发送给本地数据网络或者发送给远端锚点UPF网元。当ULCL与本地锚点UPF网元分开部署时，该上行分流规则包括安装在ULCL上的上行分流规则。其中，安装在ULCL上的上行分流规则用于ULCL按照数据包的源地址将该数据包发送给本地锚点UPF网元或远端锚点UPF网元；本申请实施例对此不作具体限定。
S813、中间SMF网元向AMF网元发送会话更新请求3，以使得AMF网元接收来自中间SMF网元的会话更新请求3。
其中，该会话更新请求3携带本地UPF的网元上行隧道信息。
S814-S815、同步骤S714-S715，相关描述可参考图7所示的实施例，在此不再赘述。
S816、AMF网元向中间SMF网元发送会话更新响应3，以使得中间SMF网元接收来自AMF网元的会话更新响应3。
其中，该会话更新响应3携带接入网元的下行隧道信息。
S817、中间SMF网元向本地SMF网元发送会话更新请求2，以使得本地SMF网元接收来自中间SMF网元的会话更新请求2。
其中，该会话更新请求2携带接入网元的下行隧道信息。
可选的，本申请实施例中，若步骤S812中中间SMF网元可以获取安装在本地UPF网元上的上行分流规则，则步骤S817中的会话更新请求2中还可以携带该安装在本地UPF网元上的上行分流规则，本申请实施例对此不作具体限定。
可选的，本申请实施例中，中间SMF网元可以将远端IP地址发送给本地SMF网元，以用于本地SMF网元生成用于安装在本地UPF网元上的上行分流规则，相关描述可参考步骤S816，在此不再赘述。
S818、本地SMF网元向本地UPF网元发送N4*会话更新请求2，以使得本地UPF网元接收来自本地SMF网元的N4*会话更新请求2。
其中，该N4*会话更新请求2携带接入网元的下行隧道信息。
可选的，本申请实施例中，本地UPF网元还可以向本地SMF网元发送与N4*会话更新请求2对应的N4*会话更新响应2，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若步骤S817中本地SMF网元可以获取安装在本地UPF网元上的上行分流规则，则步骤S818中的N4*会话更新请求2中还可以携带该安装在本地UPF网元上的上行分流规则，本申请实施例对此不作具体限定。
S819、同步骤S719，相关描述可参考图7所示的实施例，在此不再赘述。
S820-S821、同步骤S721-S722，相关描述可参考图7所示的实施例，在此不再赘述。
基于本申请实施例提供的会话管理方法，可以使得终端不在远端锚点SMF网元的管理区域时，仍然可以通过本地UPF网元访问本地数据网络。
其中，上述步骤S801至S821中的中间SMF网元的动作可以由图6所示的通信设备600中的处理器601调用存储器603中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图10所示的会话管理***应用于如图11所示的5G网络为例，如图12所示，为本申请实施例提供的另一种会话管理方法，该会话管理方法包括如下步骤：
S1201-S1203、同步骤S801-S803，具体可参考图8所示的实施例，在此不再赘述。
S1204、中间SMF网元根据目标DNAI，为终端选择本地UPF网元。
其中，本地UPF网元的相关描述可参考步骤S803，在此不再赘述。
其中，若本申请实施例中的本地锚点UPF网元与ULCL/BP是分开部署的，则中间SMF网元根据目标DNAI，为终端选择本地UPF网元，具体可以包括：中间SMF网元根据目标DNAI，为终端选择本地锚点UPF网元；以及，中间SMF网元根据终端的位置信息，为终端选择ULCL/BP。
可选的，本申请实施例中，中间SMF网元根据目标DNAI，为终端选择本地锚点UPF网元，具体可以包括：中间SMF网元根据目标DNAI、本地配置信息和可选的终端的位置信息，为终端选择本地锚点UPF网元；或者，中间SMF网元向网络功能存储网元，例如NRF网元请求该本地锚点UPF网元的信息，由NRF网元根据目标DNAI为终端选择本地锚点UPF网元之后，向中间SMF网元发送该本地锚点UPF网元的信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，中间SMF网元根据终端的位置信息，为终端选择ULCL/BP，具体可以包括：中间SMF网元根据终端的位置信息和本地配置信息，为终端选择ULCL/BP；或者，中间SMF网元向网络功能存储网元，例如NRF网元请求该ULCL/BP的信息，由NRF网元根据终端的位置信息为终端选择ULCL/BP之后，向中间SMF网元发送该ULCL/BP的信息，本申请实施例对此不作具体限定。
其中，若本申请实施例中的本地锚点UPF网元与ULCL/BP是合一部署的，则中间SMF网元根据目标DNAI，为终端选择本地UPF网元具体可以包括：中间SMF网元根据目标DNAI、终端的位置信息、以及本地配置信息，为终端选择本地UPF网元；或者，中间SMF网元向网络功能存储网元，例如NRF网元请求该本地UPF网元的信息，由NRF网元根据目标DNAI和终端位置信息为终端选择本地UPF网元之后，向中间SMF网元发送该本地UPF网元的信息，本申请实施例对此不作具体限定。
可选的，若存在多个目标DNAI，则中间SMF网元可能会为不同的目标DNAI选择不同本地锚点UPF网元，例如，每个目标DNAI对应的本地锚点UPF网元均不相同。
假设本申请实施例中本地锚点UPF网元与ULCL/BP合一部署，则本申请实施例提供的会话管理方法还可以包括如下步骤：
S1205、与步骤S807类似，区别比如在于：将步骤S807中的本地SMF网元替换为中间SMF网元，将步骤S807中的N4*会话建立请求1替换为N4会话建立请求1，相关描述可参考图8所示的实施例，在此不再赘述。
S1206-1213、同步骤S809-816，相关描述可参考图8所示的实施例，在此不再赘述。
S1214、与步骤S818类似，区别比如在于：将步骤S818中的本地SMF网元替换为中间SMF网元，将步骤S818中的N4*会话建立请求2替换为N4会话建立请求2，相关描述可参考图8所示的实施例，在此不再赘述。
S1215、同步骤S819，相关描述可参考图8所示的实施例，在此不再赘述。
S1216-S1217、同步骤S820-S821，相关描述可参考图8所示的实施例，在此不再赘述。
基于本申请实施例提供的会话管理方法，可以使得终端不在远端锚点SMF网元的管理区域时，仍然可以通过本地UPF网元访问本地数据网络。
其中，上述步骤S1201至S1217中的中间SMF网元的动作可以由图6所示的通信设备600 中的处理器601调用存储器603中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
图12所示的实施例以本地锚点UPF网元与ULCL/BP合一部署为例进行说明。可选的，本申请实施例中的本地锚点UPF网元与ULCL/BP也可以分开部署，此时，中间SMF网元需要分别向本地锚点UPF网元和ULCL/BP发送N4*会话建立请求，以便建立ULCL/BP与本地锚点UPF网元间的隧道，以及建立ULCL/BP与远端锚点UPF网元间的隧道，相关描述可参考图12所示的实施例，在此不再赘述。
综上，因此，本申请实施例公开了一种会话管理方法，该方法包括：中间会话管理网元接收一个或多个本地DNAI；中间会话管理网元根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI，该目标DNAI用于为终端选择本地会话管理网元。
在一种可能的实现方式中，在中间会话管理网元确定目标DNAI之后，还包括：中间会话管理网元向移动管理网元发送第一消息，该第一消息携带所述目标DNAI。
作为一种实现，该目标DNAI还用于为终端选择本地用户面功能网元。
可选的，第一消息还携带会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
作为一种实现，该会话接入模式还用于为终端选择本地用户面功能网元或本地会话管理网元中的至少一个。
作为一种实现，会话接入模式包括ULCL模式或Multi-homing模式。
进一步的，该会话管理方法还包括：中间会话管理网元接收与一个或多个本地DNAI对应的应用标识信息；相应的，第一消息还携带与目标DNAI对应的应用标识信息，该与目标DNAI对应的应用标识信息用于生成本地路由规则，该本地路由规则用于将数据分流到目标DNAI对应的本地数据网络。
进一步的，在中间会话管理网元向移动管理网元发送第一消息之后，该会话管理方法还包括：中间会话管理网元接收来自移动管理网元的第二消息，该第二消息用于指示释放中间会话管理网元和中间用户面功能网元上该终端的会话资源；中间会话管理网元根据该第二消息，释放中间会话管理网元上该终端的会话资源；以及，中间会话管理网元向中间用户面功能网元发送第三消息，该第三消息用于指示释放中间用户面功能网元上该终端的会话资源。
在另一种可能的实现方式中，在中间会话管理网元确定目标DNAI之后，该会话管理方法还包括：中间会话管理网元根据所述目标DNAI，确定为所述终端服务的所述本地会话管理网元。
作为一种实现，中间会话管理网元根据所述目标DNAI，确定为终端服务的本地会话管理网元，包括：中间会话管理网元根据所述目标DNAI和本地配置信息，为终端选择本地会话管理网元；或者：
作为另一种实现，中间会话管理网元根据所述目标DNAI，确定为终端服务的本地会话管理网元，包括：中间会话管理网元向网络功能存储网元发送第四消息，该第四消息携带目标DNAI；中间会话管理网元接收来自网络功能存储网元的本地会话管理网元的信息；中间会话管理网元根据本地会话管理网元的信息，确定为终端服务的本地会话管理网元；或者，
作为另一种实现，中间会话管理网元根据所述目标DNAI，确定为终端服务的本地会话管理网元，包括：中间会话管理网元根据目标DNAI和会话接入模式的信息，为终端选择本地会话管理网元；或者，
作为另一种实现，中间会话管理网元根据所述目标DNAI，确定为终端服务的本地会话管理网元，包括：中间会话管理网元向移动管理网元发送第五消息，该第五消息携带目标DNAI；中间会话管理网元接收来自移动管理网元的本地会话管理网元的信息；中间会话管理网元根据本地会话管理网元的信息，确定为终端服务的本地会话管理网元。
进一步的，该会话管理方法还包括：中间会话管理网元向本地会话管理网元发送第六消息，该第六消息携带终端的当前位置信息，该终端的当前位置信息用于为终端选择本地用户面功能网元。
作为一种实现，该第六消息还携带会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
在一种可能的实现方式中，该会话接入模式包括ULCL模式；该会话管理方法还包括：中间会话管理网元接收与一个或多个DNAI本地对应的应用标识信息；相应的，第六消息还携带与目标DNAI对应的应用标识信息，该与所述目标DNAI对应的应用标识信息用于生成本地路由规则，该本地路由规则用于将数据分流到目标DNAI对应的本地数据网络。
在另一种可能的实现方式中，该会话接入模式包括Multi-homing模式；该会话管理方法还包括：中间会话管理网元向远端锚点会话管理网元发送本地会话管理网元为所述终端分配的本地IP地址，该本地IP地址用于通过远端锚点会话管理网元发送给终端；或者，中间会话管理网元向终端发送路由通告，该路由通告携带本地会话管理网元为终端分配的本地IP地址。
可选的，该会话管理方法还包括：中间会话管理网元向远端锚点会话管理网元发送目标DNAI，该目标DNAI用于进行计费和策略控制。
可选的，该会话管理方法还包括：中间会话管理网元向本地会话管理网元发送请求消息，该请求消息用于建立终端的当前接入设备和本地用户面功能网元之间的路径，以及，建立本地用户面功能网元和远端锚点用户面功能网元之间的路径。
进一步的，该会话管理方法还包括：中间会话管理网元向中间用户面功能网元发送第七消息，该第七消息用于指示释放中间用户面功能网元上该终端的会话资源。
上述会话管理方法中，例如，中间会话管理网元的操作可参考图7或图8中中间SMF网元的操作及上述相关文字说明，在此不再赘述。
可选的，本申请实施例还公开了一种会话管理方法，该方法包括：中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；中间会话管理网元根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI；中间会话管理网元根据目标DNAI，为终端选择本地用户面功能网元。
作为一种实现，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元获取会话接入模式、远端IP地址、目标DNAI对应的本地路由策略、或者目标DNAI对应的应用标识信息中的至少一个；中间会话管理网元根据会话接入模式、远端IP地址、目标DNAI对应的本地路由策略、或者目标DNAI对应的应用标识信息中的至少一个，生成目标规则，该目标规则用于本地用户面功能网元对接收到的数据包进行转发。
作为一种实现，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元将目标规则发送给本地用户面功能网元。
作为一种实现，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元从远端会话管理网元或策略控制功能网元接收会话接入模式、远端IP地址、目标DNAI对应的本 地路由策略、或者目标DNAI对应的应用标识信息中的至少一个。
作为一种实现，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元获取会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
可选的，该会话接入模式还用于为该终端选择本地用户面功能网元。
可选的，该会话接入模式包括上行分类器ULCL模式或多穴Multi-homing模式。
作为一种实现，本申请实施例提供的会话管理方法还可以包括：中间会话管理网元向远端锚点会话管理网元发送该目标DNAI，该目标DNAI用于进行计费和策略控制。
上述会话管理方法中，例如，中间会话管理网元的操作可参考图12中中间SMF网元的操作及上述相关文字说明，在此不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述中间会话管理网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对中间会话管理网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图9示出了一种中间会话管理网元90的结构示意图。该中间会话管理网元90包括：收发模块901和处理模块902。收发模块901，用于接收一个或多个本地DNAI。处理模块902，用于根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI，该目标DNAI用于为终端选择本地会话管理网元。
在一种可能的实现方式中，收发模块901，还用于向移动管理网元发送第一消息，该第一消息携带目标DNAI。
可选的，收发模块901，还用于接收与一个或多个本地DNAI对应的应用标识信息；相应的，第一消息还携带与目标DNAI对应的应用标识信息，该与目标DNAI对应的应用标识信息用于生成本地路由规则，该本地路由规则用于将数据分流到目标DNAI对应的本地数据网络。
可选的，收发模块901，还用于接收来自移动管理网元的第二消息，该第二消息用于指示释放中间会话管理网元和中间用户面功能网元上终端的会话资源；处理模块902，还用于根据第二消息，释放中间会话管理网元上终端的会话资源；以及，收发模块901，还用于向中间用户面功能网元发送第三消息，该第三消息用于指示释放中间用户面功能网元上终端的会话资源。
在另一种可能的实现方式中，处理模块902，还用于根据目标DNAI，确定为终端服务的本地会话管理网元。
作为一种实现，处理模块902用于根据目标DNAI，确定为终端服务的本地会话管理网元，包括：用于根据目标DNAI和本地配置信息，为终端选择本地会话管理网元。
作为另一种实现，处理模块902用于根据目标DNAI，确定为终端服务的本地会话管理网 元，包括：用于向网络功能存储网元发送第四消息，该第四消息携带目标DNAI；接收来自网络功能存储网元的本地会话管理网元的信息。
作为另一种实现，处理模块902用于根据目标DNAI，确定为终端服务的本地会话管理网元，包括：用于根据目标DNAI和会话接入模式的信息，为终端选择本地会话管理网元。
作为另一种实现，处理模块902用于根据目标DNAI，确定为终端服务的本地会话管理网元，包括：用于向移动管理网元发送第五消息，该第五消息携带目标DNAI；接收来自移动管理网元的本地会话管理网元的信息。
可选的，收发模块901，还用于向本地会话管理网元发送第六消息，该第六消息携带终端的当前位置信息，该终端的当前位置信息用于为终端选择本地用户面功能网元。
可选的，该第六消息还携带会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
一种可能的实现方式中，会话接入模式包括ULCL模式；收发模块901，还用于接收与一个或多个DNAI本地对应的应用标识信息；相应的，第六消息还携带与目标DNAI对应的应用标识信息，与目标DNAI对应的应用标识信息用于生成本地路由规则，该本地路由规则用于将数据分流到目标DNAI对应的本地数据网络。
另一种可能的实现方式中，会话接入模式包括Multi-homing模式；收发模块901，还用于向远端锚点会话管理网元发送本地会话管理网元为终端分配的本地IP地址，该本地IP地址用于通过远端锚点会话管理网元发送给终端；或者，收发模块901，还用于向终端发送路由通告，路由通告携带本地会话管理网元为终端分配的本地IP地址。
可选的，收发模块901，还用于向远端锚点会话管理网元发送目标DNAI，该目标DNAI用于进行计费和策略控制。
可选的，收发模块901，还用于向本地会话管理网元发送请求消息，该请求消息用于建立终端的当前接入设备和本地用户面功能网元之间的路径，以及，建立本地用户面功能网元和远端锚点用户面功能网元之间的路径。
可选的，收发模块901，还用于向中间用户面功能网元发送第七消息，该第七消息用于指示释放中间用户面功能网元上终端的会话资源。
作为另一种可能的实现方式，可选的，在该中间会话管理网元90包括收发模块901和处理模块902的情况下，收发模块901，用于接收一个或多个本地DNAI；处理模块902，用于根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI，并根据目标DNAI，为终端选择本地用户面功能网元。
可选的，处理模块902，还用于获取会话接入模式、远端IP地址、目标DNAI对应的本地路由策略、或者目标DNAI对应的应用标识信息中的至少一个；并根据会话接入模式、远端IP地址、目标DNAI对应的本地路由策略、或者目标DNAI对应的应用标识信息中的至少一个，生成目标规则，该目标规则用于本地用户面功能网元对接收到的数据包进行转发。
可选的，处理模块902，还用于获取会话接入模式的信息，该会话接入模式的信息用于确定本地会话的接入模式。
可选的，一个或多个DNAI是锚点用户面功能网元所检测到的一个或多个业务数据流所对应的PCC规则中中间会话管理网元所支持的本地DNAI。
可选的，收发模块901，还用于向远端锚点会话管理网元发送请求消息，请求消息用于请求远端锚点会话管理网元将锚点用户面功能网元所检测到的一个或多个业务数据流所对应 的PCC规则中中间会话管理网元所支持的本地DNAI发送给中间会话管理网元。
可选的，收发模块901用于接收一个或多个本地DNAI，包括：用于接收来自远端锚点会话管理网元或策略控制网元的一个或多个本地DNAI。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本申请实施例中，该中间会话管理网元90以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到用中间会话管理网元90可以采用图5所示的形式。
比如，图5中的处理器501可以通过调用存储器503中存储的计算机执行指令，使得中间会话管理网元90执行上述方法实施例中的会话管理方法。
具体的，图9中的收发模块901和处理模块902的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现。或者，图9中的处理模块902的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现，图9中的收发模块901的功能/实现过程可以通过图5中的通信接口503来实现。
由于本申请实施例提供的中间会话管理网元可执行上述的会话管理方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例提供了一种芯片***，该芯片***包括处理器，用于支持中间会话管理网元实现上述会话管理方法，例如根据终端的当前位置信息、以及一个或多个本地DNAI，确定目标DNAI。在一种可能的设计中，该芯片***还包括存储器。该存储器，用于保存中间会话管理网元必要的程序指令和数据。当然，存储器也可以不在芯片***中。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (51)

  1. 一种会话管理方法，其特征在于，所述方法包括：
    中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；
    所述中间会话管理网元根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI，所述目标DNAI用于为所述终端选择本地会话管理网元。
  2. 根据权利要求1所述的方法，其特征在于，在所述中间会话管理网元确定目标DNAI之后，还包括：
    所述中间会话管理网元向移动管理网元发送第一消息，所述第一消息携带所述目标DNAI。
  3. 根据权利要求1或2所述的方法，其特征在于，所述目标DNAI还用于为所述终端选择本地用户面功能网元。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第一消息还携带会话接入模式的信息，所述会话接入模式的信息用于确定本地会话的接入模式。
  5. 根据权利要求4所述的方法，其特征在于，所述会话接入模式还用于为所述终端选择本地用户面功能网元或所述本地会话管理网元中的至少一个。
  6. 根据权利要求4或5所述的方法，其特征在于，所述会话接入模式包括上行分类器ULCL模式或多穴Multi-homing模式。
  7. 根据权利要求2-5任一项所述的方法，其特征在于，所述方法还包括：
    所述中间会话管理网元接收与所述一个或多个本地DNAI对应的应用标识信息；
    相应的，所述第一消息还携带与所述目标DNAI对应的应用标识信息，所述与所述目标DNAI对应的应用标识信息用于生成本地路由规则，所述本地路由规则用于将数据分流到所述目标DNAI对应的本地数据网络。
  8. 根据权利要求2-7任一项所述的方法，其特征在于，在所述中间会话管理网元向移动管理网元发送第一消息之后，还包括：
    所述中间会话管理网元接收来自所述移动管理网元的第二消息，所述第二消息用于指示释放所述中间会话管理网元和中间用户面功能网元上所述终端的会话资源；
    所述中间会话管理网元根据所述第二消息，释放所述中间会话管理网元上所述终端的会话资源；以及，所述中间会话管理网元向所述中间用户面功能网元发送第三消息，所述第三消息用于指示释放所述中间用户面功能网元上所述终端的会话资源。
  9. 根据权利要求1所述的方法，其特征在于，在所述中间会话管理网元确定目标DNAI之后，还包括：
    所述中间会话管理网元根据所述目标DNAI，确定为所述终端服务的所述本地会话管理网元。
  10. 根据权利要求9所述的方法，其特征在于，所述中间会话管理网元根据所述目标DNAI，确定为所述终端服务的所述本地会话管理网元，包括：
    所述中间会话管理网元根据所述目标DNAI和本地配置信息，为所述终端选择所述本地会话管理网元；或者，
    所述中间会话管理网元向网络功能存储网元发送第四消息，所述第四消息携带所述目标DNAI；所述中间会话管理网元接收来自所述网络功能存储网元的所述本地会话管理 网元的信息；或者，
    所述中间会话管理网元根据所述目标DNAI和会话接入模式的信息，为所述终端选择所述本地会话管理网元；或者，
    所述中间会话管理网元向移动管理网元发送第五消息，所述第五消息携带所述目标DNAI；所述中间会话管理网元接收来自所述移动管理网元的所述本地会话管理网元的信息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述中间会话管理网元向所述本地会话管理网元发送第六消息，所述第六消息携带所述终端的当前位置信息，所述终端的当前位置信息用于为所述终端选择本地用户面功能网元。
  12. 根据权利要求11所述的方法，其特征在于，所述第六消息还携带会话接入模式的信息，所述会话接入模式的信息用于确定本地会话的接入模式。
  13. 根据权利要求12所述的方法，其特征在于，所述会话接入模式包括ULCL模式；所述方法还包括：
    所述中间会话管理网元接收与所述一个或多个DNAI本地对应的应用标识信息；
    相应的，所述第六消息还携带与所述目标DNAI对应的应用标识信息，所述与所述目标DNAI对应的应用标识信息用于生成本地路由规则，所述本地路由规则用于将数据分流到所述目标DNAI对应的本地数据网络。
  14. 根据权利要求12所述的方法，其特征在于，所述会话接入模式包括Multi-homing模式；所述方法还包括：
    所述中间会话管理网元向远端锚点会话管理网元发送所述本地会话管理网元为所述终端分配的本地互联网协议IP地址，所述本地IP地址用于通过所述远端锚点会话管理网元发送给所述终端；或者，
    所述中间会话管理网元向所述终端发送路由通告，所述路由通告携带所述本地会话管理网元为所述终端分配的本地IP地址。
  15. 根据权利要求9-14任一项所述的方法，其特征在于，所述方法还包括：
    所述中间会话管理网元向远端锚点会话管理网元发送所述目标DNAI，所述目标DNAI用于进行计费和策略控制。
  16. 根据权利要求9-15任一项所述的方法，其特征在于，所述方法还包括：
    所述中间会话管理网元向本地会话管理网元发送请求消息，所述请求消息用于建立所述终端的当前接入设备和本地用户面功能网元之间的路径，以及，建立所述本地用户面功能网元和远端锚点用户面功能网元之间的路径。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述中间会话管理网元向中间用户面功能网元发送第七消息，所述第七消息用于指示释放所述中间用户面功能网元上所述终端的会话资源。
  18. 一种会话管理方法，其特征在于，所述方法包括：
    中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；
    所述中间会话管理网元根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI；
    所述中间会话管理网元向移动管理网元发送第一消息，所述第一消息携带所述目标 DNAI；
    所述移动管理网元接收来自所述中间会话管理网元的所述第一消息，并根据所述目标DNAI确定为所述终端服务的本地会话管理网元。
  19. 一种会话管理方法，其特征在于，所述方法包括：
    中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；
    所述中间会话管理网元根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI；
    所述中间会话管理网元根据所述目标DNAI，确定为所述终端服务的本地会话管理网元；
    所述中间会话管理网元向所述本地会话管理网元发送第一消息，所述第一消息携带所述终端的当前位置信息；
    所述本地会话管理网元接收来自所述中间会话管理网元的所述第一消息，并根据所述终端的当前位置信息确定为所述终端服务的本地用户面功能网元。
  20. 一种中间会话管理网元，其特征在于，所述中间会话管理网元包括：收发模块和处理模块；
    所述收发模块，用于接收一个或多个本地数据网络接入标识DNAI；
    所述处理模块，用于根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI，所述目标DNAI用于为所述终端选择本地会话管理网元。
  21. 根据权利要求20所述的中间会话管理网元，其特征在于，
    所述收发模块，还用于向移动管理网元发送第一消息，所述第一消息携带所述目标DNAI。
  22. 根据权利要求21所述的中间会话管理网元，其特征在于，
    所述收发模块，还用于接收与所述一个或多个本地DNAI对应的应用标识信息；
    相应的，所述第一消息还携带与所述目标DNAI对应的应用标识信息，所述与所述目标DNAI对应的应用标识信息用于生成本地路由规则，所述本地路由规则用于将数据分流到所述目标DNAI对应的本地数据网络。
  23. 根据权利要求21或22所述的中间会话管理网元，其特征在于，
    所述收发模块，还用于接收来自所述移动管理网元的第二消息，所述第二消息用于指示释放所述中间会话管理网元和中间用户面功能网元上所述终端的会话资源；
    所述处理模块，还用于根据所述第二消息，释放所述中间会话管理网元上所述终端的会话资源；以及，所述收发模块，还用于向所述中间用户面功能网元发送第三消息，所述第三消息用于指示释放所述中间用户面功能网元上所述终端的会话资源。
  24. 根据权利要求20所述的中间会话管理网元，其特征在于，
    所述处理模块，还用于根据所述目标DNAI，确定为所述终端服务的所述本地会话管理网元。
  25. 根据权利要求24所述的中间会话管理网元，其特征在于，
    所述收发模块，还用于向本地会话管理网元发送请求消息，所述请求消息用于建立所述终端的当前接入设备和本地用户面功能网元之间的路径，以及，建立所述本地用户面功能网元和远端锚点用户面功能网元之间的路径。
  26. 根据权利要求25所述的中间会话管理网元，其特征在于，
    所述收发模块，还用于向中间用户面功能网元发送第七消息，所述第七消息用于指示释放所述中间用户面功能网元上所述终端的会话资源。
  27. 一种会话管理***，其特征在于，所述会话管理***包括：中间会话管理网元和移动管理网元；
    所述中间会话管理网元，用于接收一个或多个本地数据网络接入标识DNAI；根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI；向移动管理网元发送第一消息，所述第一消息携带所述目标DNAI；
    所述移动管理网元，用于接收来自所述中间会话管理网元的所述第一消息，并根据所述目标DNAI确定为所述终端服务的本地会话管理网元。
  28. 根据权利要求27所述的会话管理***，其特征在于，所述会话管理***包括：本地会话管理网元；
    所述移动管理网元，还用于向所述本地会话管理网元发送第二消息，所述第二消息携带所述终端的当前位置信息；
    所述本地会话管理网元，用于接收来自所述移动管理网元的所述第二消息，并根据所述终端的当前位置信息为确定所述终端服务的本地用户面功能网元。
  29. 根据权利要求28所述的会话管理***，其特征在于，所述第一消息还携带会话接入模式的信息；相应的，所述第二消息还携带所述会话接入模式的信息，所述会话接入模式的信息用于确定本地会话的接入模式。
  30. 根据权利要求27或28所述的会话管理***，其特征在于，
    所述本地会话管理网元，还用于接收来自远端锚点会话管理网元的会话接入模式的信息，所述会话接入模式的信息用于确定本地会话的接入模式。
  31. 根据权利要求29或30所述的会话管理***，其特征在于，所述会话接入模式包括多穴Multi-homing模式；
    所述本地会话管理网元，还用于为所述终端分配本地互联网协议IP地址，以及，所述本地会话管理网元，还用于接收远端锚点会话管理网元为所述终端分配的远端IP地址；
    所述本地会话管理网元，还用于通知本地用户面功能网元将源地址为本地IP地址的数据分流到所述目标DNAI对应的本地数据网络，将源地址为远端IP地址的数据分流到远端锚点用户面功能网元。
  32. 根据权利要求29或30所述的会话管理***，其特征在于，所述会话接入模式包括上行分类器ULCL模式；
    所述本地会话管理网元，还用于根据本地配置信息或者与所述一个或多个本地DNAI对应的应用标识信息中的至少一个，生成本地路由规则；
    所述本地会话管理网元，还用于向本地用户面功能网元发送所述本地路由规则，所述本地路由规则用于将数据分流到所述目标DNAI对应的本地数据网络。
  33. 一种会话管理***，其特征在于，所述会话管理***包括：中间会话管理网元和本地会话管理网元；
    所述中间会话管理网元，用于接收一个或多个本地数据网络接入标识DNAI；根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI；根据所述目标DNAI，确定为所述终端服务的本地会话管理网元；向所述本地会话管理网元发送第一消息，所述第一消息携带所述终端的当前位置信息；
    所述本地会话管理网元，用于接收来自所述中间会话管理网元的所述第一消息，并根据所述终端的当前位置信息确定为所述终端服务的本地用户面功能网元。
  34. 根据权利要求33所述的会话管理***，其特征在于，所述第一消息还携带会话接入模式信息；所述会话接入模式信息用于确定本地会话的接入模式。
  35. 一种会话管理方法，其特征在于，所述方法包括：
    中间会话管理网元接收一个或多个本地数据网络接入标识DNAI；
    所述中间会话管理网元根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI；
    所述中间会话管理网元根据所述目标DNAI，为所述终端选择本地用户面功能网元。
  36. 根据权利要求35所述的会话管理方法，其特征在于，所述一个或多个本地DNAI是所述终端的会话对应的策略和计费控制PCC规则中所述中间会话管理网元所支持的本地DNAI。
  37. 根据权利要求35所述的会话管理方法，其特征在于，所述一个或多个DNAI是锚点用户面功能网元所检测到的一个或多个业务数据流所对应的PCC规则中所述中间会话管理网元所支持的本地DNAI。
  38. 根据权利要求37所述的会话管理方法，其特征在于，所述方法还包括：
    所述中间会话管理网元向远端锚点会话管理网元发送请求消息，所述请求消息用于请求远端锚点会话管理网元将锚点用户面功能网元所检测到的一个或多个业务数据流所对应的PCC规则中所述中间会话管理网元所支持的本地DNAI发送给所述中间会话管理网元。
  39. 根据权利要求38所述的会话管理方法，其特征在于，所述请求消息中包括指示所述中间会话管理网元所支持的一个或多个DNAI的信息。
  40. 根据权利要求35-39任一项所述的会话管理方法，其特征在于，所述中间会话管理网元接收一个或多个本地DNAI，包括：
    所述中间会话管理网元接收来自远端锚点会话管理网元或策略控制网元的一个或多个本地DNAI。
  41. 根据权利要求35-40任一项所述的会话管理方法，其特征在于，所述方法还包括：
    所述中间会话管理网元获取会话接入模式、远端互联网协议IP地址、所述目标DNAI对应的本地路由策略、或者所述目标DNAI对应的应用标识信息中的至少一个；
    所述中间会话管理网元根据所述会话接入模式、所述远端IP地址、所述目标DNAI对应的本地路由策略、或者所述目标DNAI对应的应用标识信息中的至少一个，生成目标规则，所述目标规则用于所述本地用户面功能网元对接收到的数据包进行转发。
  42. 一种中间会话管理网元，其特征在于，所述中间会话管理网元包括收发模块和处理模块；
    所述收发模块，用于接收一个或多个本地数据网络接入标识DNAI；
    所述处理模块，用于根据终端的当前位置信息、以及所述一个或多个本地DNAI，确定目标DNAI；
    所述处理模块，还用于根据所述目标DNAI，为所述终端选择本地用户面功能网元。
  43. 根据权利要求42所述的中间会话管理网元，其特征在于，所述一个或多个DNAI 是锚点用户面功能网元所检测到的一个或多个业务数据流所对应的PCC规则中所述中间会话管理网元所支持的本地DNAI。
  44. 根据权利要求43所述的中间会话管理网元，其特征在于，
    所述收发模块，还用于向远端锚点会话管理网元发送请求消息，所述请求消息用于请求远端锚点会话管理网元将锚点用户面功能网元所检测到的一个或多个业务数据流所对应的PCC规则中所述中间会话管理网元所支持的本地DNAI发送给所述中间会话管理网元。
  45. 根据权利要求42-44任一项所述的中间会话管理网元，其特征在于，所述收发模块用于接收一个或多个本地DNAI，包括：
    用于接收来自远端锚点会话管理网元或策略控制网元的一个或多个本地DNAI。
  46. 根据权利要求42-45所述的中间会话管理网元，其特征在于，
    所述处理模块，还用于获取会话接入模式、远端互联网协议IP地址、所述目标DNAI对应的本地路由策略、或者所述目标DNAI对应的应用标识信息中的至少一个；
    所述处理模块，还用于根据所述会话接入模式、所述远端IP地址、所述目标DNAI对应的本地路由策略、或者所述目标DNAI对应的应用标识信息中的至少一个，生成目标规则，所述目标规则用于所述本地用户面功能网元对接收到的数据包进行转发。
  47. 一种中间会话管理网元，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述中间会话管理网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述中间会话管理网元执行如权利要求1-17任一项，或权利要求18，或权利要求19，或权利要求35-41任一项所述的会话管理方法。
  48. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-17任一项，或权利要求18，或权利要求19，或权利要求35-41任一项所述的会话管理方法。
  49. 一种计算机程序产品，其特征在于，所述计算机程序产品中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-17任一项，或权利要求18，或权利要求19，或权利要求35-41任一项所述的会话管理方法。
  50. 一种用来执行权利要求1-17任一项，或权利要求18，或权利要求19，或权利要求35-41任一项所述的会话管理方法的装置。
  51. 一种芯片***，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，使得安装有所述芯片***的设备执行如权利要求1-17任一项，或权利要求18，或权利要求19，或权利要求35-41任一项所述的会话管理方法。
PCT/CN2018/119736 2018-01-12 2018-12-07 会话管理方法、设备及*** WO2019137125A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP22178965.4A EP4125284A1 (en) 2018-01-12 2018-12-07 Session management method, device and system
EP18899139.2A EP3720160B1 (en) 2018-01-12 2018-12-07 Session management method, device and system
ES18899139T ES2928328T3 (es) 2018-01-12 2018-12-07 Método, dispositivo y sistema de gestión de sesión
US16/906,842 US11432366B2 (en) 2018-01-12 2020-06-19 Session management method, device, and system
US17/860,533 US12004264B2 (en) 2018-01-12 2022-07-08 Session management method, device, and system

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201810031226 2018-01-12
CN201810031226.6 2018-01-12
CN201810313129.6 2018-04-09
CN201810313129 2018-04-09
CN201811379260.9A CN110167003B (zh) 2018-01-12 2018-11-19 会话管理方法、设备及***
CN201811379260.9 2018-11-19

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/906,842 Continuation US11432366B2 (en) 2018-01-12 2020-06-19 Session management method, device, and system

Publications (1)

Publication Number Publication Date
WO2019137125A1 true WO2019137125A1 (zh) 2019-07-18

Family

ID=67218183

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/119736 WO2019137125A1 (zh) 2018-01-12 2018-12-07 会话管理方法、设备及***

Country Status (4)

Country Link
EP (1) EP4125284A1 (zh)
CN (1) CN117544941A (zh)
ES (1) ES2928328T3 (zh)
WO (1) WO2019137125A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021012736A1 (zh) * 2019-07-23 2021-01-28 华为技术有限公司 一种会话管理网元的选择方法、装置及***
CN112311691A (zh) * 2019-07-26 2021-02-02 华为技术有限公司 策略控制方法、设备及***
WO2021018242A1 (zh) * 2019-07-30 2021-02-04 华为技术有限公司 一种数据转发方法、装置及***
WO2023236764A1 (zh) * 2022-06-08 2023-12-14 华为技术有限公司 一种分配互联网协议地址的方法及通信装置
EP4185010A4 (en) * 2020-07-31 2024-02-07 Huawei Tech Co Ltd METHOD AND DEVICE FOR ACCESSING A LOCAL NETWORK

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296225A (zh) * 2007-04-29 2008-10-29 华为技术有限公司 会话管理功能装置及提供业务的***和方法
WO2017219973A1 (en) * 2016-06-21 2017-12-28 Huawei Technologies Co., Ltd. Systems and methods for user plane path selection, reselection, and notification of user plane changes

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351777B (zh) * 2018-04-03 2022-12-06 华为技术有限公司 指示业务分流的方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296225A (zh) * 2007-04-29 2008-10-29 华为技术有限公司 会话管理功能装置及提供业务的***和方法
WO2017219973A1 (en) * 2016-06-21 2017-12-28 Huawei Technologies Co., Ltd. Systems and methods for user plane path selection, reselection, and notification of user plane changes

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP TS 23.501 V15.0.0, 22 December 2017 (2017-12-22), pages 1 - 181, XP055623209 *
NTT DOCOMO ET AL.: "23.501: AF Subscription to DNAI Change Events and Concept of DNAI Service Area", SA WG2 MEETING #122BIS S2-176477, 25 August 2017 (2017-08-25), XP051326106 *
NTT DOCOMO ET AL.: "23.501: AF subscription to DNAI Change Events and Concept of DNAI Service Area", SA WG2 MEETING #122BIS S2-176549, 25 August 2017 (2017-08-25), XP051326137 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021012736A1 (zh) * 2019-07-23 2021-01-28 华为技术有限公司 一种会话管理网元的选择方法、装置及***
CN112311691A (zh) * 2019-07-26 2021-02-02 华为技术有限公司 策略控制方法、设备及***
CN112311691B (zh) * 2019-07-26 2024-04-16 华为技术有限公司 策略控制方法、设备及***
WO2021018242A1 (zh) * 2019-07-30 2021-02-04 华为技术有限公司 一种数据转发方法、装置及***
EP4185010A4 (en) * 2020-07-31 2024-02-07 Huawei Tech Co Ltd METHOD AND DEVICE FOR ACCESSING A LOCAL NETWORK
WO2023236764A1 (zh) * 2022-06-08 2023-12-14 华为技术有限公司 一种分配互联网协议地址的方法及通信装置

Also Published As

Publication number Publication date
EP4125284A1 (en) 2023-02-01
CN117544941A (zh) 2024-02-09
ES2928328T3 (es) 2022-11-17
US20220346190A1 (en) 2022-10-27

Similar Documents

Publication Publication Date Title
EP3720160B1 (en) Session management method, device and system
US11882485B2 (en) Session management function entity selection method, apparatus, and system
US11871283B2 (en) Service continuity implementation method, device, and service continuity implementation system
CN110035562B (zh) 会话管理方法、设备及***
WO2019137125A1 (zh) 会话管理方法、设备及***
US11812484B2 (en) Data transmission method, device, and data transmission system
WO2018214597A1 (zh) 接入网类型选择方法、设备及***
WO2019223702A1 (zh) 管理pdu会话的方法、装置和***
CN110557265B (zh) 一种组播方法及装置
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及***
WO2019174437A1 (zh) 地址管理方法、设备及***
WO2019137521A1 (zh) 会话管理方法、设备及***
US20230137283A1 (en) Systems and methods to optimize registration and session establishment in a wireless network
WO2022099484A1 (zh) 标识发送方法和通信装置
US12004264B2 (en) Session management method, device, and system
US20230093193A1 (en) Systems and methods for indicating the presence of a multi-access edge computing application
WO2020011173A1 (zh) 搬迁管理方法及装置
WO2019210779A1 (zh) 切换方法、设备及***

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18899139

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018899139

Country of ref document: EP

Effective date: 20200702