WO2018153253A1 - 一种选择会话管理功能实体的方法、装置和系统 - Google Patents

一种选择会话管理功能实体的方法、装置和系统 Download PDF

Info

Publication number
WO2018153253A1
WO2018153253A1 PCT/CN2018/075472 CN2018075472W WO2018153253A1 WO 2018153253 A1 WO2018153253 A1 WO 2018153253A1 CN 2018075472 W CN2018075472 W CN 2018075472W WO 2018153253 A1 WO2018153253 A1 WO 2018153253A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
management function
function entity
session management
information
Prior art date
Application number
PCT/CN2018/075472
Other languages
English (en)
French (fr)
Inventor
丁辉
王晓燕
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20178336.2A priority Critical patent/EP3796617B1/en
Priority to EP18757355.5A priority patent/EP3471377B1/en
Priority to KR1020187036850A priority patent/KR102138002B1/ko
Priority to BR112019001845-0A priority patent/BR112019001845A2/pt
Priority to JP2019518349A priority patent/JP6701446B2/ja
Publication of WO2018153253A1 publication Critical patent/WO2018153253A1/zh
Priority to US16/192,713 priority patent/US10743218B2/en
Priority to US16/874,326 priority patent/US11882485B2/en
Priority to US18/522,959 priority patent/US20240098578A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H04W36/385—Reselection control by fixed network equipment of the core network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • 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
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, apparatus, and system for selecting a session management function entity.
  • the Service and Session Continuity mode is divided into three types, which are respectively introduced below.
  • the first mode is to ensure session continuity if the Terminated User Plane Function (TUPF) is unchanged.
  • TUPF Terminated User Plane Function
  • TUPF is the last UPF that the user plane connects to the data network.
  • TUPF can be considered as a user plane functional entity with anchor function.
  • the second mode is to maintain session continuity in a certain area. The TUPF does not change in a certain area. When the user equipment (User Equipment, UE) used by the user moves out of the area, the TUPF changes.
  • UE User Equipment
  • the third is to ensure session continuity in the case of TUPF changes.
  • the TUPF changes, and the session continuity can be guaranteed by using the new TUPF for the newly initiated session of the UE and the current TUPF for the existing session of the UE.
  • the first mode, the second mode, and the third mode of the SSC mode are referred to as SSC mode 1, SSC mode 2, and SSC mode 3, respectively.
  • a session management function entity (SMF) needs to be selected due to an event such as a UE location change (selected).
  • SMF session management function entity
  • the SMF selection operation will be performed by the Access and Mobility Management Function (AMF), but this method has the following drawbacks: AMF does not Perceived PDU session management related information. If the SMF selection operation is continued by the AMF, the selected SMF may be unreasonable.
  • the embodiments of the present invention provide a method, an apparatus, and a system for selecting a session management function entity, so as to solve the problem that the session management function entity selected in the prior art is unreasonable.
  • the embodiment of the present invention provides the following technical solutions:
  • a method for selecting a session management function entity comprising: first receiving information of a first session of a user equipment UE from a first session management function entity and a reselection indication, the reselection indication And indicating to reselect the session management function entity; and then, according to the reselection indication, saving the correspondence between the information of the first session and the first session management function entity; and thereafter, receiving the session establishment request message carrying the information of the first session, determining different And a second session management function entity of the first session management function entity; sending a session management request to the second session management function entity.
  • the first session management function entity is a session management function entity corresponding to the information of the first session determined by querying the corresponding relationship saved by itself.
  • the first session management function entity Since the first session management function entity can perceive the session management related information, it is determined by the first session management function entity whether to reselect the session management function entity, if the reselection needs to be determined, the reselection indication is sent, and then the reselection indication is received.
  • the party selects other session management function entities other than the first session management function entity to continue to serve the UE, which is more reasonable than the session management function entity selected in the prior art.
  • the reselection indication may be specifically used to indicate that the first session needs to reselect the session management function entity.
  • the information of the first session includes an identifier of the first session, or the information of the first session includes an identifier of the UE and an identifier of the first session.
  • the session establishment request message carries the identifier of the second session to be created by the UE, in addition to the information of the first session.
  • the session identifier assigned by the UE for the session to be created is different from the identifier of the first session.
  • the method before receiving the session establishment request message, the method further includes: sending a re-establishment session indication to the UE to notify the UE to establish the second session.
  • the method before receiving the location change notification message, the method further includes: establishing the first session; wherein the first session management function entity is a session management function entity serving the first session.
  • an embodiment of the present invention provides another method for selecting a session management function entity, the method comprising: first, receiving information and session management function of a first session of a user equipment UE from a first session management function entity As a result of the weight selection, the session management function entity reselection result includes information of the second session management function entity; then, the correspondence between the information of the first session and the second session management function entity is saved; and thereafter, the information carrying the first session is received a session establishment request message, querying the correspondence relationship to determine a second session management function entity corresponding to the information of the first session; and sending a session management request to the second session management function entity.
  • the first session management function entity Since the first session management function entity can perceive the session management related information, it is determined by the first session management function entity whether to reselect the session management function entity, and if the reselection needs to be determined, the reselected session management function entity is determined and sent The result is selected, and then the receiver of the reselection result selects the reselection result to continue to serve the UE, which is more reasonable than the session management function entity selected in the prior art.
  • the reselection result may specifically include a second session management function entity reselected for the first session.
  • an embodiment of the present invention provides another method for selecting a session management function entity, the method comprising: first, receiving information of a first session of a user equipment UE from a first session management function entity and a session management function entity Selecting a result, the session management function entity selection result includes information of the first session management function entity; or: receiving information and indication information of the first session of the user equipment UE from the first session management function entity; and then saving the Corresponding relationship between the information of the first session and the first session management function entity; then, receiving a session establishment request message, the session establishment request message carrying the first session information; querying the correspondence relationship to determine the first session Corresponding to the first session management function entity; sending a session management request to the first session management function entity. Since the first session management function entity can perceive the session management related information, it is more reasonable for the first session management function entity to determine the reselection session management function entity than the session management function entity selected in the prior art.
  • an embodiment of the present invention provides an apparatus for selecting a session management function entity, the apparatus having the function of implementing an execution body of an embodiment of the method provided by any one of the above first to third aspects.
  • 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 embodiment of the present invention provides an apparatus for selecting a session management function entity, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor and the memory pass the bus Connecting, when the device is running, the processor executing the computer-executable instructions stored in the memory to cause the device selecting the session management function entity to perform the select session management function entity of any of the first to third aspects above Methods.
  • an embodiment of the present invention provides a system for selecting a session management function entity, including the execution entity in the foregoing method embodiment or the device embodiment, and further includes a first session management function entity.
  • the first session management function entity is configured to determine whether the session management function entity needs to be reselected, and sends a reselection indication; or the first session management function entity is configured to determine the reselected session management function entity, and send the reselection result.
  • an embodiment of the present invention provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • an embodiment of the present invention provides a computer storage medium comprising instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • FIG. 1 is a schematic diagram of a possible system network according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of another possible system network according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for selecting a session management function entity according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of another method for selecting a session management function entity according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of another method for selecting a session management function entity according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of another method for selecting a session management function entity according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of another method for selecting a session management function entity according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of another method for selecting a session management function entity according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of an apparatus for selecting a session management function entity according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another apparatus for selecting a session management function entity according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of another apparatus for selecting a session management function entity according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are used to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation of the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • An embodiment of the present invention provides a system 100 for selecting a session management function entity, where the system 100 includes a mobility management function entity 10 and a session management function entity 20.
  • the mobility management function entity 10 receives a location change notification message; then, the mobility management function entity 10 sends a session management message to the session management function entity 20, where the session management function entity 20 can be used as the first session management function entity.
  • the session management function entity 20 determines whether to reselect the session management function entity. If reselection is required, the session management function entity 20 transmits information of the first session of the user equipment UE and a reselection indication to the mobility management function entity 10, the reselection indication being used to indicate reselection of the session management function entity.
  • the mobility management function entity 10 saves the correspondence between the information of the first session and the first session management function entity according to the reselection indication. Then, the mobility management function entity 10 receives the session establishment request message, where the session establishment request message carries the information of the first session; after receiving the session establishment request message, the mobility management function entity 10 determines that it is different from the first The session management function entity of the session management function entity 20, such as the second session management function entity, then the mobility management function entity 20 sends a session management request to the second session management function entity.
  • the mobility management function entity 10 selects other session management function entities other than the session management function entity 20 to continue to serve the UE, compared to the mobility management function entity in the prior art.
  • the selected session management function entity is more reasonable.
  • the reselection indication may be specifically used to indicate that the first session needs to reselect the session management function entity.
  • the mobility management function entity 10 receives the location change notification message; then, the mobility management function entity 10 sends a session management message to the session management function entity 20.
  • the session management function entity 20 can be used as the first session management function entity.
  • the session management function entity 20 determines whether to reselect the session management function entity. If reselection is required, the session management function entity 20 determines a reselected session management function entity, such as a third session management function entity.
  • the session management function entity 20 After determining the third session management function entity, the session management function entity 20 transmits the information of the first session of the user equipment UE and the session management function entity reselection result to the mobility management function entity 10, the session management function entity reselection result includes The information of the third session management function entity determined above. After receiving the session management function entity reselection result, the mobility management function entity 10 saves the correspondence between the information of the first session and the third session management function entity.
  • the mobility management function entity 10 receives the session establishment request message, where the session establishment request message carries the first session information; after receiving the session establishment request message, the mobility management function entity 10 determines by using the saved correspondence relationship The session management function entity corresponding to the information of the first session, that is, the third session management function entity, then the mobility management function entity 10 sends the session management request third session management function entity.
  • the information of the third session management function entity that is determined may be the identifier of the third session management function entity, the address of the third session management function entity, or other information that may represent the third session management function entity. This application is not limited.
  • the session management function entity 20 since the session management function entity 20 can perceive the session management related information, it is determined by the session management function entity 20 whether to reselect the session management function entity, and if it is necessary to determine the reselection, Determining the reselected third session management function entity and sending a reselection result, and then the receiver of the reselection result selects the reselection result to continue to serve the UE, which is more than the session management function entity selected in the prior art. reasonable.
  • the reselection result may specifically include a second session management function entity reselected for the first session.
  • the mobility management function entity 10 receives the location change notification message; then, the mobility management function entity 10 sends a session management message to the session management function entity 20.
  • the session management function entity 20 can be used as the first session management function entity.
  • the session management function entity 20 After receiving the session management message, the session management function entity 20 determines that the UPF needs to be reselected, and the session management function entity 20 sends the information of the first session of the user equipment UE and the session management function entity selection result to the mobility management function entity 10,
  • the session management function entity selection result includes information of the first session management function entity; or, after receiving the session management message, the session management function entity 20 determines that the UPF needs to be reselected, and the session management function entity 20 sends the mobility management function entity 10 to the mobility management function entity 10.
  • Information and indication information of the first session of the user equipment UE After receiving the above information sent by the session management function entity 20, the mobility management function entity 10 saves the correspondence between the information of the first session and the first session management entity.
  • the mobility management function entity 10 receives the session establishment request message, where the session establishment request message carries the first session information; after receiving the session establishment request message, the mobility management function entity 10 determines by using the saved correspondence relationship The session management function entity corresponding to the information of the first session, that is, the first session management function entity, then the mobility management function entity 10 sends a session management request first session management function entity.
  • the information of the first session management function entity may be the identifier of the first session management function entity, the address of the first session management function entity, or other information that may represent the first session management function entity. Not limited.
  • the indication information may be a session re-establishment indication, or may be an UPF re-selection indication, or may be an indication information that does not need to re-select the SMF, or may be a session release timer or other implicit indication message, and the application does not Make a limit.
  • determining that the UPF needs to be reselected For example, it is determined whether the current UPF can continue to provide services for the UE. If the current UPF cannot provide services for the UE, the other UPFs managed by the session management function entity 20 may be The UE provides the service. Of course, other methods of the prior art can also be used to determine that the UPF needs to be reselected. The reason why the current UPF cannot continue to provide services for the UE may be that the load of the source UPF is too heavy, or the location of the UE may be moved, so that the source UPF cannot continue to provide services for the UE.
  • the session management function entity 20 determines the session management function entity, which is higher than the mobility management function entity in the prior art. The selected session management function entity is more reasonable.
  • the user equipment UE related to 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, and various forms of user equipment UEs. , mobile station (MS), terminal, terminal equipment, soft terminal, and the like.
  • MS mobile station
  • terminal terminal equipment
  • soft terminal soft terminal
  • the mobility management function entity 10 and the session management function entity 20 are only one name, and the name itself does not limit the entity.
  • the "mobility management function entity” may also be replaced with an "access and mobility management function entity” or other name; the session management function entity 20 may also be replaced with a "session management function” or other name.
  • the mobility management function entity 10 may also correspond to an entity that includes other functions in addition to the mobility management function.
  • the session management function entity 20 may also correspond to an entity that includes other functions in addition to the session management function. A unified explanation is given here, and will not be described below.
  • the location change notification message may be a handover notification message, or may be a location area update request message, or may be a message of another name, which is not limited herein.
  • the session management message may be a UE mobility event notification message, or may be a handover notification message, or may be a Non-Access-Stratume (NAS) notification message (NAS Message Notify), or may be a message of another name. There is no limit here.
  • the session management request may be a session establishment request, or may be a message of another name, which is not limited herein.
  • the information of the first session may include the identifier of the first session, and may also include the identifier of the UE and the identifier of the first session.
  • the information of the first session may include the identifier of the first session, and may also include the identifier of the UE and the identifier of the first session.
  • other content may also be included.
  • the first session management function entity is a session management function entity serving the first session.
  • the session management function entity 20 determines whether there are multiple methods for reselecting the session management function entity. First, the session management function entity 20 determines that the load is too heavy to continue to provide services for the UE; The session management function entity 20 determines that the source user plane function (UPF) entity currently serving the PDU session cannot continue to provide services for the UE, and the target UPF that can provide services for the UE is managed by other session management function entities. That is, the UE is not within the service scope of the session management function entity 20. The reason why the source UPF cannot continue to provide services for the UE may be that the source UPF is overloaded, or the source UPF cannot continue to provide services for the UE.
  • UPF user plane function
  • the session management function entity 20 can also use other methods in the prior art to determine whether to reselect the session management function entity. If the mobility management function entity 10 sends the session management message to the session management function entity 20 in the SMF granularity described in the following embodiment, the session management function entity 20 may first determine the PDU session that the UE itself provides for the service according to the UE identity. Then determine if the PDU session is to reselect the SMF.
  • the mobility management function entity 10 determines that there are multiple methods for the session management function entity different from the session management function entity 20, and may adopt any one of the following methods, or may adopt other methods in the prior art. method.
  • the mobility management function entity 10 queries the topology management function entity according to the UE location or according to the UE location and data network information, and acquires a session management function entity different from the session management function entity 20 that can provide services for the UE.
  • the data network information may be an Access Point Name (APN) information or a Data Network Name (DNN) information.
  • the topology management function entity may be separately set in the actual deployment, or may be combined with an existing network element in the network, such as a Domain Name System (DNS), a mobility management function entity 10, or a network element registration.
  • DNS Domain Name System
  • NRF Network Repository Function
  • NRF Network Function Repository Function
  • the topology management function entity may obtain other UPF lists that can currently provide services for the UE, and obtain (for example, query the DNS) the session management function entity information corresponding to each UPF in the UPF list, and select corresponding different session management.
  • the session management function entity information includes an identifier of the session management function entity and/or a load of the session management function entity.
  • the session management function entity corresponding to the session management function entity 20 corresponding to the PDU session is selected.
  • the fourth type is configured to construct a session management function entity host name according to the UE identifier and the network configuration information, and obtain (for example, query the DNS) a session management function entity different from the session management function entity 20 corresponding to the host name.
  • the session management function entity 20 determines a method for reselecting the third session management function entity. Specifically, the session management function entity 20 may determine the third session management function entity by using the foregoing first method, that is, according to the following: The UE location, or querying the topology management function entity according to the UE location and data network information, acquires a session management function entity different from the session management function entity 20 that can provide services for the UE.
  • the session management function entity 20 can also employ other methods in the prior art.
  • the UE location (or the target access area information) may be a target base station identifier, or a target cell identifier, or a target tracking area identifier, or may be other location information indicating that the UE is to be switched. limited.
  • a specific example of a 5G system 200 provided by the present application is of course not limited to the system.
  • the method for selecting a session management function entity provided by the embodiment of the present invention can be applied to the system shown in FIGS. 1 and 2.
  • AMF and SMF are included.
  • the AMF is an example of the mobility management function entity 10 of FIG. 1
  • the SMF is an example of the session management function entity 20 of FIG.
  • the AMF is an access and mobility management function entity, performs UE access and mobility management, and receives UE mobility and network selection policies provided by a Policy Function (PCF) and performs policy execution.
  • PCF Policy Function
  • the SMF is a session management function entity, performs session management, receives a session or service flow control policy provided by the PCF, and executes a policy. It can also select a TUPF or allocate a UE's Internet Protocol (IP) address.
  • IP Internet Protocol
  • the system 200 can also include a PCF, a TUPF, or an Access Network (AN).
  • the PCF is a policy control function entity, and is mainly responsible for policy control such as charging, quality of service (QoS), and mobility for the session level or service flow level.
  • TUPF functions as an interface user interface with the data network (Data Network) to perform user plane data forwarding, billing statistics based on session level or service flow level, and bandwidth limitation.
  • Data Network data network
  • the AN is an access network in 5G, and performs functions such as allocation and scheduling of bearer resources. Among them, there may be other user plane functional entities between AN and TUPF.
  • the SMF can perceive session management related information, such as SMF service range, SMF load, UPF load or SSC mode, it is determined by the SMF whether it is heavy. Selecting the SMF, or selecting the reselected SMF by the SMF, is more reasonable than the SMF selected by the AMF in the prior art.
  • the specific function node or the network element in the foregoing system 100 or the system 200 may be implemented by one physical device or may be implemented by multiple physical devices, which is not specifically limited in the embodiment of the present invention. That is, it can be understood that any one of the function nodes or network elements in the system 100 or the system 200 may be a logical function module in the physical device, or may be a logical function module composed of multiple physical devices. The embodiment of the present invention does not specifically limit this.
  • the mobility management function entity 10 of FIG. 1, or the AMF of FIG. 2 may be implemented in the manner of a computer device (or system) in FIG.
  • FIG. 3 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • the computer device 300 includes at least one processor 31, a communication bus 32, a memory 33, and at least one communication interface 34.
  • the processor 31 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 32 can include a path for communicating information between the components described above.
  • the communication interface 34 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 33 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 can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 33 is used to store application code for executing the solution of the present invention, and is controlled by the processor 31 for execution.
  • the processor 31 is configured to execute application code stored in the memory 33.
  • processor 31 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 300 can include multiple processors, such as processor 31 and processor 38 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 300 may also include an output device 35 and an input device 36.
  • the output device 35 is in communication with the processor 31 and can display information in a variety of ways.
  • the output device 35 may 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 36 is in communication with processor 31 and can accept user input in a variety of ways.
  • input device 36 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device 300 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 300 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, a communication device, an embedded device, or have FIG. A device of similar structure.
  • Embodiments of the invention do not limit the type of computer device 300.
  • the mobility management function entity 10 in FIG. 1 or the AMF in FIG. 2 may be the device shown in FIG. 3, and one or more software modules are stored in the memory of the mobility management function entity 10 or the AMF.
  • the mobility management function entity 10 or the AMF can implement the software module through the processor and the program code in the memory to implement the selection of the session management function entity.
  • FIG. 4 provides a schematic flowchart of a method for selecting a session management function entity.
  • the interaction between the session management function entity 10 and the session management function entity 20 in FIG. 1 or the interaction with the external network element may adopt the method in the method embodiment.
  • the interaction between the AMF and the SMF in FIG. 2, or the interaction with the external network element, may also adopt the method in the method embodiment.
  • This embodiment takes SSC mode 2 as an example in the session and service continuity mode.
  • the UE sends a session establishment request to the AMF through the AN, and the AMF selects the SMF to provide the service for the session, and saves the correspondence between the SMF and the PDU session, and sends the session establishment request to the SMF, and the SMF establishes a corresponding PDU session and establishes User plane transmission path.
  • the AN here can be a next generation access network.
  • the specific PDU session establishment process is the same as the prior art, and details are not described herein again.
  • the UE may trigger a PDU session establishment.
  • a PDU session establishment For convenience of description, it may be recorded as a PDU Session1 session; or multiple PDU session establishment procedures may be triggered.
  • multiple PDU sessions may be respectively recorded as PDU Session1, PDU. Session2 and other sessions.
  • the UE negotiates with the AN, and when the handover is needed, the AN sends a handover notification message to the AMF.
  • the AMF receives the handover notification message.
  • the scenario in which the UE performs the handover is relatively large. For example, the service quality of the network that provides services for the UE is relatively poor, or the network that is currently serving the UE is overloaded, and the details are not described herein.
  • the handover notification message includes the UE location information (ie, the target access zone information) and the UE identifier.
  • the target access zone information is exemplified by the target base station identifier.
  • the AMF determines the PDU session information established for the UE in S401 according to the UE identifier, and sends a session management message to the SMF corresponding to the established PDU session.
  • the PDU session established for the UE in S401 is PDU Session1 and PDU Session2
  • the AMF will separately send a session management message to the SMF1 serving the PDU Session1 and the SMF2 serving the PDU Session2, where SMF1 and SMF2 may be the same SMF functional entity.
  • the PDU session established for the UE in S401 is PDU Session1, and the AMF will send a session management message to SMF1 serving the PDU Session1.
  • the PDU session established for the UE in S401 is PDU Session1.
  • the AMF sends the session management message to the SMF1 corresponding to the PDU Session1.
  • SMF1 receives the session management message.
  • the session management message carries the information of the UE identifier, the PDU Session1, and the UE location information.
  • the information of the PDU session1 may be the ID of the PDU session1, the ID of the UE ID and the PDU session1, or other information indicating the PDU session1.
  • the SMF1 After receiving the session management message, the SMF1 determines that the SMF needs to be reselected.
  • the SMF determines, according to the information of the PDU Session1, the session and service continuity mode of the corresponding PDU Session and the PDU Session 1 session as SSC mode 2.
  • the method for determining whether to reselect the SMF by the SMF1 may be determined by the method described in FIG. 1. That is, it is determined that SMF reselection is required based on the load information of the SMF1, the UPF load information managed by the SMF1, or the service range of the SMF1.
  • SMF1 determines that the SMF needs to be reselected.
  • the SMF1 sends a session management response to the AMF, where the session management response carries information of the PDU Session1 and a reselection indication for indicating the reselection of the SMF.
  • the AMF receives the session management response.
  • the session management response may be a response to the UE mobility event, or may be a handover response, or may be a message of another name, which is not limited herein.
  • the AMF After the AMF receives the session management response, if the request carries the reselection indication, the AMF saves the correspondence between the information of the PDU Session1 and the SMF1. The correspondence is used by the subsequent AMF to perform reselection of the SMF upon receiving the session establishment request from the UE.
  • the correspondence may be saved in the form of a table or a chart, and is not limited herein.
  • the correspondence may further include the foregoing reselection indication.
  • the information of the saved SMF1 may be the name of the SMF1, or the SMF1ID, or other information indicating the SMF1. This application is not limited.
  • the purpose of saving the SMF1 information is to prevent the AMF from reselecting to SMF1 when reselecting the SMF.
  • the AMF sends a handover command to the AN to indicate that the subsequent handover procedure is completed.
  • the SMF initiates a PDU Session 1 release process.
  • the SMF will also send a reestablishment session indication to inform the UE to initiate a new PDU session establishment request after the session release is completed.
  • the re-establishment session indication may be a specific cause value or a specific indication, which is not limited in this application.
  • the UE After the UE releases the original session, the UE sends a session establishment request to the AMF.
  • the AMF receives the session establishment request.
  • the session establishment includes information of the PDU Session1.
  • AMF will query the saved correspondence to prevent AMF from selecting SMF1 when reselecting SMF.
  • the session establishment request carries the PDU Session ID allocated by the UE for the new PDU session to be established.
  • the session establishment request carries the ID of the PDU Session1, or carries the ID of the UE and the ID of the PDU Session1.
  • the session establishment request carries the new session ID and the ID of the PDU Session1, or carries the new session ID and the UE. ID and ID of the PDU Session1.
  • the session establishment request may also carry the location information of the UE, and may also carry DNN information (such as a DNN identifier, etc.).
  • the AMF determines that the second SMF different from the first SMF is a reselected SMF, that is, the second SMF serves the UE.
  • the method in which the AMF determines the second SMF different from the first SMF may be determined by the method described in FIG. 1. I won't go into details here.
  • the AMF searches for the saved correspondence to avoid selecting the SMF1 saved in the AMF.
  • the AMF sends a session management request to the SMF2.
  • SMF2 receives the session management request.
  • the session management request may be a session creation request, or other names, which are not limited in this application.
  • the SMF2 allocates a new TUPF and an IP address to the UE.
  • the TUPF is used as the anchor UPF of the newly established session, and is used to establish a user plane path of the new side PDU session.
  • the new IP address is used for data transmission between the UE and the data network.
  • the SMF2 initiates a new PDU session establishment process for the UE.
  • the SMF1 since the SMF1 can perceive the session management related information, it is determined by the SMF whether to reselect the SMF, and if the reselection needs to be determined, the reselection indication is sent to the AMF by the AMF. To select other SMFs other than SMF1 to continue to serve the UE is more reasonable than the SMF selected by AMF in the prior art.
  • step 403 the AMF receives the handover notification.
  • the session management function entity is also selected.
  • the main difference between the method flow of selecting the session management function entity and the handover scenario described in FIG. 4 is S403, S413 and S415 are different.
  • the UE initiates a location area update request message to the AMF through the target AN.
  • the request may be triggered by the UE moving to a new location area, or by a timer triggering the UE to initiate a periodic location area update, or by the UE moving to another network coverage.
  • the AMF sends a location area update response message (TAU Response or TAU Accept message) to the AN, and the indication information carried in the message does not change.
  • TAU Response or TAU Accept message
  • the original PDU session does not have an air interface bearer.
  • the establishment process of the user plane connection between the UE, the target AN, and the UPF needs to be performed.
  • the other steps are consistent with the process in the switching scenario.
  • the session management message is sent to the SMF corresponding to each PDU session in the PDU session granularity, so that if an SMF is simultaneously a UE, The PDU session provides services, and the SMF may receive multiple session management messages in the process.
  • the AMF may also send a session management message to the SMF currently serving the UE in the SMF granularity, that is, the same SMF serving multiple PDU sessions of the UE will receive only one session in the process.
  • Manage messages In the message notification mode, the main difference from the original process is S405, S407, S409, and S411, and the specific differences are as follows.
  • the S401 may be related to multiple PDU session establishment procedures. For ease of description, three PDU sessions are established by the UE, which are respectively recorded as PDU Session 1, PDU Session 2 and PDU Session 3. PDU Session1 and PDU Session 2 are served by SMF1, and PDU Session 3 is served by SMF2.
  • the main difference between the flow and the current process is as follows: corresponding to S405 is S405', after the AMF receives the handover notification sent by the AN, the AMF will be based on the UE identifier in the handover notification and The correspondence between the PDU session and the SMF saved in S401 determines the information of the SMF that provides the service to the UE.
  • the AMF sends a session management message to SMF1 and SMF2.
  • the session management message carries the UE identity and the UE location information.
  • each SMF after receiving the session management message sent by the AMF, each SMF first determines each PDU session that is served by the UE according to the UE identifier (in this example, the SMF1 query results in PDU Session 1) The result of the query with PDU Session 2 and SMF2 is PDU Session 3), and then it is determined whether the SMF needs to be reselected for each PDU session, and the basis for judging whether the SMF needs to be reselected is consistent with the manner described in the flow of FIG.
  • the SMF1 determines that the PDU Session 1 and the PDU Session 2 need to reselect the SMF, and the SMF 2 determines that the PDU Session 3 needs to reselect the SMF.
  • S409' after each SMF determines that the PDU session of the provided service needs to be reselected, the SMF will return a session management response to the AMF, and carry the PDU session with the SMF to be reselected in the response message. Re-election instructions.
  • the SMF1 since both the PDU Session 1 and the PDU Session 2 need to reselect the SMF, the SMF1 will simultaneously return the information of the PDU Session 1 and the PDU Session 2 and the reselection indication; the SMF 2 returns the information of the PDU Session 3 and the reselection indication.
  • the reselection indication in the session management response returned by the SMF may be one, or one PDU Session that needs to be reselected.
  • Re-election instructions For example, the SMF1 in the above example may return: information of the PDU Session1, information of the PDU Session2, and a reselection indication; or: information of the PDU Session1, indicating that the PDU Session1 needs to be reselected, the reselection indication 1, the PDU The information of Session 2 indicates that the PDU Session 2 needs to be reselected by the reselection indication 2.
  • one PDU Session corresponds to one reselection indication
  • one PDU Session corresponding to one reselection indication may be used, that is, one PDU Session corresponds to one reselection indication, and is used in combination with one PDU Session corresponding to one reselection indication.
  • other methods are not excluded, and this application does not limit this.
  • the reselection indication may be a specific cause value or a specific indication, which is not limited by the present invention.
  • the PDU session information the AMF saves the correspondence between the information of the corresponding PDU session and the SMF currently serving the service, and the save format is consistent with the manner described in the flow of FIG. The correspondence is used by the subsequent AMF to perform reselection of the SMF upon receiving the session establishment request from the UE.
  • step 407 is triggered by a session management message sent by the AMF.
  • the SMF determines that the UPF corresponding to the PDU Session1 is overloaded or the corresponding SMF is overloaded, the session management function entity is also selected.
  • the main difference between the method flow for selecting the session management function entity and the handover scenario shown in FIG. 4 is S403, S405, S409, S413, and S415.
  • the SMF directly acquires factors such as UPF or SMF load according to the message itself or from other functional entities, and triggers step S407.
  • This information may include information such as UPF load conditions, SMF load conditions, or UPF failures.
  • the message may be a session management notification message, or may be other messages, and is not limited herein.
  • the indication information carried in the message does not change.
  • step 415 the message will send a session re-establishment indication to the UE via the AMF.
  • step 415 may be performed separately from step S409, or may be combined and sent in step S409.
  • the other steps are consistent with the process in the switching scenario.
  • the actions of the AMF can be performed by the AMF in accordance with the software modules in the memory mentioned above.
  • the embodiment of the present invention does not impose any limitation on this.
  • FIG. 5 provides another schematic flow chart of a method for selecting a session management function entity.
  • the interaction between the session management function entity 10 and the session management function entity 20 in FIG. 1 or the interaction with the external network element may adopt the method in the method embodiment.
  • the interaction between the AMF and the SMF in FIG. 2, or the interaction with the external network element, may also adopt the method in the method embodiment.
  • This embodiment takes SSC mode 3 as an example in the session and service continuity mode.
  • the SMF1 After receiving the session management message, the SMF1 determines whether the SMF needs to be reselected.
  • the SMF determines, according to the information of the PDU Session1, the session and service continuity mode of the corresponding PDU Session and the PDU Session 1 session as SSC mode 3.
  • the method for determining whether to reselect the SMF by the SMF1 may be determined by the method described in FIG. 1.
  • the SMF sends a session redirection request to the UE after the handover is completed, and carries the reestablishment session indication in the request to notify the UE to initiate establishment of a new PDU session.
  • the UE receives the redirect request.
  • the session redirection request may be a session reestablishment request, or may be another message name, which is not limited in this application.
  • the SMF1 since the SMF1 can perceive the session management related information, the SMF is selected by the SMF1, so that the selected SMF is more reasonable than the SMF selected by the AMF in the prior art. .
  • the UE initiates a location area update request to the AMF through the target AN; correspondingly, corresponding to S513, the AMF sends a location area update response message to the AN.
  • the session management message is sent to the SMF corresponding to each PDU session by using the PDU session granularity, so that if an SMF is simultaneously multiple of the UE, The PDU session provides services, and the SMF may receive multiple session management messages in the process.
  • the AMF may also send a session management message to the SMF currently serving the UE in the SMF granularity, that is, the same SMF serving multiple PDU sessions of the UE will receive only one session in the process. Manage messages.
  • the main difference from the original process is S505, S507, S509, and S511.
  • S505, S507, S509, and S511 are replaced with S505', S507', S509', and S511', respectively.
  • S505', S507', S509', and S511' are the same as S405', S407', S409', and S411', respectively, and will not be described again.
  • step 507 is triggered by a session management message sent by the AMF.
  • the SMF determines that the UPF corresponding to the PDU Session1 is overloaded or the corresponding SMF is overloaded, the session management function entity is also selected.
  • the main difference between the method flow of selecting the session management function entity and the handover scenario described in FIG. 5 is S503, S505, S509, S513, and S515.
  • the SMF directly obtains UPF or SMF load and other factors according to the message itself or from other functional entities.
  • Step S507 is triggered.
  • This information may include information such as UPF load conditions, SMF load conditions, or UPF failures.
  • the message will send a session reestablishment indication to the UE via the AMF.
  • the step may be performed separately from step S509, or may be combined and sent in step S509.
  • the other steps are consistent with the process in the switching scenario.
  • the actions of the AMF may be performed by the AMF in accordance with the software modules in the memory mentioned above.
  • the embodiment of the present invention does not impose any limitation on this.
  • FIG. 6 provides another schematic flow chart of a method for selecting a session management function entity.
  • the interaction between the session management function entity 10 and the session management function entity 20 in FIG. 1 or the interaction with the external network element may adopt the method in the method embodiment.
  • the interaction between the AMF and the SMF in FIG. 2, or the interaction with the external network element, may also adopt the method in the method embodiment.
  • This embodiment takes SSC mode 2 as an example in the session and service continuity mode.
  • the SMF1 determines whether the SMF needs to be reselected. If it is determined that the SMF needs to be reselected, the SMF1 determines the second SMF, that is, the second SMF is the reselected SMF, and the second SMF serves the UE.
  • the SMF determines, according to the information of the PDU Session1, the session and service continuity mode of the corresponding PDU Session and the PDU Session 1 session as SSC mode 2.
  • the method in which the SMF1 determines whether to reselect the SMF is the same as that described in S407.
  • the method by which the SMF1 determines the second SMF may be determined by the method in which the session management function entity 20 of FIG. 1 determines the reselected third session management function entity. That is, the topology management function entity acquires the load information of other SMFs or the load information of the UPF, and determines an SMF different from SMF1 that can provide services for the UE to provide services for the UE.
  • the SMF1 sends a session management response to the AMF, where the session management response carries the information of the PDU Session1 and the SMF reselection result.
  • the SMF reselection result is the information of the second SMF.
  • the AMF receives the session management response.
  • the AMF After receiving the session management response, the AMF saves the correspondence between the information of the PDU Session1 and the second SMF information. The correspondence is used for subsequent purposes, and the AMF selects the second SMF as the SMF serving the UE upon receiving the session establishment request from the UE.
  • the correspondence may be saved in the form of a table or a chart, and is not limited herein.
  • the correspondence may further include indication information that needs to reselect the SMF.
  • the indication information of the SMF to be re-selected may be a specific indication or a specific cause value, which is not limited in this application.
  • the information of the saved second SMF may be the name of the second SMF, the ID of the second SMF, or other information indicating the SMF, which is not limited in this application.
  • the AMF After receiving the session establishment request, the AMF queries the corresponding relationship to determine that the SMF corresponding to the information of the PDU session1 is SMF2. That is, the second SMF is selected to serve the UE.
  • the AMF determines the SMF2 by querying the corresponding relationship according to the information of the PDU session1 carried in the session establishment request message during the process of determining the second SMF.
  • the SMF1 since the SMF1 can perceive the session management related information, it is determined by the SMF1 whether to reselect the SMF, and if it is necessary to determine the reselection, the reselected SMF is determined and the reselection is sent. The result is more reasonable for AMF than for SMF selected by AMF in the prior art.
  • the method described in FIG. 6 is also applicable to a scenario in which a UE location area is updated.
  • the main difference between the method flow of selecting the session management function entity and the handover scenario described in FIG. 6 is S603, S613 and S615 are different.
  • the UE initiates a location area update request message to the AMF through the target AN.
  • the request may be triggered by the UE moving to a new location area, or by a timer triggering the UE to initiate a periodic location area update, or by the UE moving to another network coverage.
  • the AMF sends a location area update response message to the AN, and the indication information carried in the message does not change.
  • the location area update response message may be a TAU Response or a TAU Accept message, or other name.
  • the original PDU session does not have an air interface bearer.
  • the establishment process of the user plane connection between the UE, the target AN, and the UPF needs to be performed.
  • the other steps are consistent with the process in the switching scenario.
  • the session management message is sent to the SMF corresponding to each PDU session in the PDU session granularity, so that if an SMF is simultaneously multiple of the UE, The PDU session provides services, and the SMF may receive multiple session management messages in the process.
  • the AMF may also send a session management message to the SMF currently serving the UE in the SMF granularity, that is, the same SMF serving multiple PDU sessions of the UE will receive only one session in the process.
  • Manage messages In the message notification mode, the main difference from the original process is S605, S607, S609, and S611, and the specific differences are as follows.
  • the S601 may be involved in multiple PDU session establishment procedures. For ease of description, three PDU sessions are established by the UE, which are respectively recorded as PDU Session 1, PDU Session 2 and PDU Session 3. PDU Session1 and PDU Session 2 are served by SMF1, and PDU Session 3 is served by SMF2.
  • S605 Corresponding to S605 is S605', after the AMF receives the handover notification sent by the AN, the AMF determines the information of the SMF serving the UE according to the UE identifier in the handover notification and the correspondence between the PDU session and the SMF saved in S601. . In this example, corresponding to SMF1 and SMF2, the AMF sends a session management message to SMF1 and SMF2.
  • the session management message carries the UE identity and the UE location information.
  • each SMF after receiving the session management message sent by the AMF, each SMF first determines each PDU session that is served by the UE according to the UE identifier (in this example, the SMF1 query results in PDU Session1 and PDU Session 2, the SMF2 query results in the PDU Session 3), and then determines whether the SMF needs to be reselected for each PDU session. If the SMF needs to be reselected, the SMF reselection operation is performed to determine that another SMF provides the UE with a service, and determines whether The process of reselection and reselection is consistent with the approach described in the process of Figure 6.
  • SMF1 determines that PDU Session 1 and PDU Session 2 need to reselect SMF, and selects SMF3 and SMF4 to provide services respectively.
  • SMF2 determines that PDU Session 3 needs to reselect SMF and provides service for SMF5, wherein SMF3, SMF4 and SMF5 may be the same or different SMFs.
  • S609' corresponding to S609 is S609', after each SMF determines that the PDU session of the provided service needs to be reselected, the SMF will return a session management response to the AMF, and carry the session information and the weight of the reselected SMF in the response message. Choose the result.
  • the SMF1 since both the PDU Session 1 and the PDU Session 2 need to reselect the SMF, the SMF1 will simultaneously return the information of the PDU Session 1 and the PDU Session 2, and reselect the SMF reselection result, that is, the information of the SMF3 and the SMF4; SMF2 returns the information of PDU Session 3 to reselect the SMF reselection result, that is, the information of SMF5.
  • S611 corresponding to S611 after the AMF receives the session management response returned by SMF1 and SMF2, if the response carries the reselection result and the PDU session information of the SMF to be reselected, the AMF saves the information of the corresponding PDU session.
  • the save format is consistent with the manner described in the flow of FIG. 6. The correspondence is used for subsequent purposes, and the AMF selects a corresponding SMF providing service for the session establishment request from the UE.
  • step 607 is triggered by a session management message sent by the AMF.
  • the SMF determines that the UPF corresponding to the PDU Session1 is overloaded or the corresponding SMF is overloaded, the session management function entity is also selected.
  • the main difference between the method flow for selecting the session management function entity and the handover scenario described in FIG. 6 is S603, S605, S609, S613, and S615. The specific difference is similar to that described in FIG. 4, and details are not described herein again.
  • the actions of the AMF may be performed by the AMF in accordance with the software modules in the memory mentioned above.
  • the embodiment of the present invention does not impose any limitation on this.
  • FIG. 7 provides another schematic flow chart of a method for selecting a session management function entity.
  • the interaction between the session management function entity 10 and the session management function entity 20 in FIG. 1 or the interaction with the external network element may adopt the method in the method embodiment.
  • the interaction between the AMF and the SMF in FIG. 2, or the interaction with the external network element, may also adopt the method in the method embodiment.
  • This embodiment takes SSC mode 3 as an example in the session and service continuity mode.
  • the SMF1 After receiving the session management message, the SMF1 determines whether the SMF needs to be reselected. If it is determined that the SMF needs to be reselected, the SMF1 determines the second SMF, that is, the second SMF is the reselected SMF, and the second SMF serves the UE.
  • the SMF determines, according to the information of the PDU Session1, the session and service continuity mode of the corresponding PDU Session and the PDU Session 1 session as SSC mode 3.
  • the SMF1 since the SMF1 can perceive the session management related information, the SMF is selected by the SMF1, so that the selected SMF is more reasonable than the SMF selected by the AMF in the prior art. .
  • the UE initiates a location area update request to the AMF through the target AN; correspondingly, corresponding to S713, the AMF sends a location area update response message to the AN.
  • the session management message is sent to the SMF corresponding to each PDU session by using the PDU session granularity, so that if an SMF is simultaneously multiple of the UE, The PDU session provides services, and the SMF may receive multiple session management messages in the process.
  • the AMF may also send a session management message to the SMF currently serving the UE in the SMF granularity, that is, the same SMF serving multiple PDU sessions of the UE will receive only one session in the process. Manage messages.
  • the main difference from the original process is S705, S707, S709, and S711.
  • S705, S707, S709, and S711 are replaced with S705', S707', S709', and S711', respectively.
  • S705', S707', S709', and S711' are the same as S605', S607', S609', and S611', respectively, and will not be described again.
  • step 707 is triggered by a session management message sent by the AMF.
  • the SMF determines that the UPF corresponding to the PDU Session1 is overloaded or the corresponding SMF is overloaded, the session management function entity is also selected.
  • the main difference between the method flow for selecting the session management function entity and the handover scenario described in FIG. 7 is S703, S705, S709, S713, and S715. The specific difference is similar to that described in FIG. 5, and details are not described herein again.
  • the actions of the AMF can be performed by the AMF in accordance with the software modules in the memory mentioned above.
  • the embodiment of the present invention does not impose any limitation on this.
  • FIG. 8 provides a schematic flowchart of a method for selecting a session management function entity.
  • the interaction between the session management function entity 10 and the session management function entity 20 in FIG. 1 or the interaction with the external network element may adopt the method in the method embodiment.
  • the interaction between the AMF and the SMF in FIG. 2, or the interaction with the external network element may also adopt the method in the method embodiment.
  • the session and service continuity mode is taken as an example of SSC mode2, and the UPF needs to be reselected, but the SMF does not need to be reselected.
  • the SMF1 determines that a PDU session on the UE needs to reselect the UPF.
  • PDU Session1 is taken as an example here.
  • the triggering reason may be the UE location information, the UPF load information, or the SMF1 load information, and may be triggered by other information, which is not limited in this application.
  • the SMF1 determines, according to the information of the PDU Session1, the session and service continuity mode of the corresponding PDU Session and the PDU Session1 session as SSC mode 2.
  • the method for the SMF1 to determine that the UPF needs to be reselected may be determined by the method described in FIG. 1.
  • the SMF1 returns a session management notification, and carries the PDU Session1 information and the indication information in the notification.
  • the PDU Session1 information and the SMF1 information may also be carried in the session management notification returned by the SMF1.
  • the session management notification may be a UE mobility event notification, or may be a session management event notification, or may be another name, which is not limited herein.
  • the AMF After receiving the session management notification, the AMF saves the correspondence between the information of the PDU Session1 and the SMF1. The correspondence is used by the subsequent AMF to perform reselection of the SMF upon receiving the session establishment request from the UE.
  • the indication information may also be included in the correspondence.
  • the purpose of saving the SMF1 information is for the subsequent AMF to continue to select SMF1 to provide services for the UE when reselecting the SMF.
  • the purpose of saving the indication information is for the subsequent AMF to avoid selecting another SMF different from SMF1 when selecting the SMF.
  • the indication information as described in FIG. 1 can be in various forms.
  • the SMF will also initiate a PDU session release command to the UE, and carry a reestablishment session indication in the message, and the message will be forwarded by the AMF during the delivery process.
  • the message may be sent in combination with the message S805, which is not limited herein.
  • the AMF queries the saved correspondence to ensure that the AMF continues to select SMF1 to provide services for the UE when selecting the SMF.
  • the AMF determines to continue to select the first SMF to serve the UE, that is, SMF1.
  • the AMF searches for the saved correspondence to avoid selecting an SMF different from the SMF1 saved in the AMF.
  • the AMF sends a session management request to the SMF1.
  • SMF1 receives the session management request.
  • the session management request may be a session creation request, or other names, which are not limited in this application.
  • SMF1 is processed in the same manner as SMF2 in S423.
  • the SMF1 initiates a new PDU session establishment process for the UE.
  • the SMF determined by the SMF is more reasonable than the SMF selected by the AMF in the prior art.
  • FIG. 9 provides a schematic flowchart of a method for selecting a session management function entity.
  • the interaction between the session management function entity 10 and the session management function entity 20 in FIG. 1 or the interaction with the external network element may adopt the method in the method embodiment.
  • the interaction between the AMF and the SMF in FIG. 2, or the interaction with the external network element may also adopt the method in the method embodiment.
  • the SSC mode 3 is taken as an example in the session and service continuity mode, and the UPF needs to be reselected, but the SMF does not need to be reselected.
  • S903 The SMF1 determines that a PDU session on the UE needs to reselect the UPF.
  • PDU Session1 is taken as an example here.
  • the triggering reason may be triggered by the UE location information, the UPF load information, the SMF1 load information, or may be triggered by other information, which is not limited by the present invention.
  • the SMF1 determines, according to the information of the PDU Session1, the session and service continuity mode of the corresponding PDU Session and the PDU Session1 session as SSC mode 3.
  • the method for the SMF1 to determine that the UPF needs to be reselected may be determined by the method described in FIG. 1.
  • SMF1 can continue to provide services for the UE, assuming that the current UPF cannot provide services to the UE due to overload or failure, and the target access area is still within the service range of the SMF1. Therefore, SMF1 determines that UPF needs to be reselected.
  • the SMF will also initiate a session redirection request to the UE, and carry a session reestablishment indication in the message, and the message will be forwarded by the AMF during the delivery process.
  • the session reestablishment indication is used to notify the UE to initiate a new PDU session establishment request.
  • the message may be sent in combination with the message S905, which is not limited herein.
  • the SMF determined by the SMF is more reasonable than the SMF selected by the AMF in the prior art.
  • the solution provided by the embodiment of the present invention is mainly introduced from the perspective of interaction between the network elements.
  • the foregoing device (or device) implementing the mobility management function entity or the session management function entity includes corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above functions.
  • the present invention 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 for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module of the mobility management function entity or the session management function entity according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated in the function.
  • a processing module In a 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 invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 10 is a schematic structural diagram of a device for implementing a session management function entity in the above embodiment, and the device 1000 includes: a transceiver module 1001. The processing module 1003 and the determining module 1005.
  • the transceiver module is configured to receive a location change notification message, send a session management message to the first session management function entity, and receive information and a reselection indication of the first session of the user equipment UE from the first session management function entity.
  • the reselection indication is used to indicate that the session management function entity is reselected;
  • the processing module is configured to save, according to the reselection indication, a correspondence between the information of the first session and the first session management function entity;
  • the transceiver module is further configured to receive a session establishment request message, where the session establishment request message carries information of the first session;
  • the determining module is configured to determine a second session management function entity different from the first session management function entity, where the first session management function entity is determined by querying the correspondence relationship saved by itself a session management function entity corresponding to the information of one session;
  • the transceiver module is further configured to send a session management request to the second session management function entity.
  • the information of the first session includes an identifier of the first session; or the information of the first session includes an identifier of the UE and an identifier of the first session. .
  • the session establishment request message further carries an identifier of the second session to be created by the UE.
  • the transceiver module is further configured to send a reestablishment session indication to the UE to notify the UE to establish a second session.
  • the device may be a mobility management function entity in the communication network, or may be an AMF, or may be another entity in the communication network. All related content of each step involved in the foregoing method embodiments may be referred to a corresponding function module. The functional description will not be repeated here.
  • FIG. 11 is a schematic structural diagram of a device for implementing a selective session management function entity in the foregoing embodiment.
  • the device 1100 includes a transceiver module 1101, a processing module 1103, and a determination module 1105.
  • the transceiver module is configured to receive a location change notification message, send a session management message to the first session management function entity, receive information of the first session of the user equipment UE from the first session management function entity, and reselect the result of the session management function entity
  • the session management function entity reselection result includes information of the second session management function entity
  • the processing module is configured to save a correspondence between the information of the first session and the second session management function entity;
  • the transceiver module is further configured to receive a session establishment request message, where the session establishment request message carries the first session information;
  • the determining module is configured to query the correspondence relationship to determine a second session management function entity corresponding to the information of the first session;
  • the transceiver module is further configured to send a session management request to the second session management function entity.
  • the information of the first session includes an identifier of the first session; or the information of the first session includes an identifier of the UE and an identifier of the first session. .
  • the session establishment request message further carries an identifier of the second session to be created by the UE.
  • the transceiver module is further configured to send a reestablishment session indication to the UE to notify the UE to establish a second session.
  • FIG. 12 is a schematic structural diagram of a device for implementing a selective session management function entity involved in the foregoing embodiment.
  • the device 1200 includes a transceiver module 1201, a processing module 1203, and a determining module 1205.
  • the transceiver module is configured to receive information about a first session of the user equipment UE from the first session management function entity and a session management function entity selection result, where the session management function entity selection result includes information of the first session management function entity; Or: a transceiver module, configured to receive information and indication information of the first session of the user equipment UE from the first session management function entity;
  • the processing module is configured to save a correspondence between the information of the first session and the first session management function entity; the transceiver module is further configured to receive a session establishment request message, where the session establishment request message carries the a first session information; the determining module is configured to query the corresponding relationship to determine the first session management function entity corresponding to the information of the first session; the transceiver module is further configured to send a session management request to the first A session management function entity.
  • the information of the first session includes an identifier of the first session; or the information of the first session includes an identifier of the UE and an identifier of the first session.
  • the session establishment request message further carries an identifier of the second session to be created by the UE.
  • the transceiver module is further configured to send a reestablishment session indication to the UE to notify the UE to establish a second session.
  • the device may be a mobility management function entity in the communication network, or may be an AMF or other entity in the communication network. All related content of each step involved in the foregoing method embodiments may be referred to a corresponding function module. The functional description will not be repeated here.
  • the device for selecting the session management function entity is presented in the form of dividing each function module corresponding to each function, or the device for selecting the session management function entity is configured to divide the form of each function module in an integrated manner.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the apparatus 1000 which implements the selection session management function entity, may take the form shown in FIG.
  • the transceiver module 10 can be implemented by the processor 31 (and/or the processor 38) and the memory 33 of FIG. 3, specifically, the transceiver module 1001, the processing module 1003, and The determining module 1005 can be executed by calling the application code stored in the memory 33 by the processor 31 (and/or the processor 38), which is not limited in this embodiment of the present invention.
  • the transceiver module 1101, the processing module 1103 and the determining module 1105 in FIG. 11 can be implemented by the processor 31 (and/or the processor 38) and the memory 33 of FIG. 3, specifically, the transceiver module 1101, the processing module 1103, and the determining module. 1105 may be performed by calling the application code stored in the memory 33 by the processor 31 (and/or the processor 38), which is not limited in this embodiment of the present invention.
  • the transceiver module 1201, the processing module 1203, and the determination module 1205 in FIG. 12 may be implemented by the processor 31 (and/or the processor 38) and the memory 33 of FIG. 3, and in particular, by the processor 31 (and/or The processor 38) is to be executed by calling the application code stored in the memory 33, which is not limited in this embodiment of the present invention.
  • the embodiment of the present invention further provides a computer storage medium for storing computer software instructions for implementing the device for selecting a session management function entity shown in FIG. 4 or FIG. 5, which is used to execute the foregoing method embodiment. Designed program.
  • the embodiment of the present invention further provides another computer storage medium for storing computer software instructions used by the apparatus for implementing the selection session management function entity shown in FIG. 6 or FIG. 7 above, which includes an embodiment for performing the above method.
  • the embodiment of the present invention further provides another computer storage medium for storing computer software instructions used by the apparatus for implementing the selection session management function entity shown in FIG. 8 or FIG. 9 above, which includes an embodiment for performing the above method.
  • the embodiment of the invention further provides a computer program product for storing as a mobility management function entity, or a computer software instruction used by the AMF, which comprises a program designed to execute the above method embodiment.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, data subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请公开了一种选择会话管理功能实体的方法、装置和系统，该方法包括：接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和重选指示，所述重选指示用于指示重选会话管理功能实体；根据该重选指示保存所述第一会话的信息与所述第一会话管理功能实体的对应关系；接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话的信息；确定不同于所述第一会话管理功能实体的第二会话管理功能实体；发送会话管理请求给所述第二会话管理功能实体。通过上述方案，解决了现有技术中选择的会话管理功能实体不合理的问题。

Description

一种选择会话管理功能实体的方法、装置和系统
本申请要求了2017年2月21日提交的、申请号为201710092451.6、发明名称为“一种选择会话管理功能实体的方法、装置和系统”的中国申请的优先权，以及2017年3月7日提交的、申请号为201710132027.X、发明名称为“一种选择会话管理功能实体的方法、装置和系统”的中国申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种选择会话管理功能实体的方法、装置及系统。
背景技术
在第五代(5rd generation，5G)通信系统中，将会话及业务连续性模式(Service and Session Continuity mode，SSC mode)分为三种，下面分别进行介绍。第一种模式是在用户面终止功能(Terminated User Plane Function，TUPF)不变的情况下，保证会话连续性。其中，TUPF作为用户面的锚点保持不变，以此来保证会话连续性。TUPF是用户面连接数据网络的最后一个UPF。其中，TUPF可以认为是有锚定功能的用户面功能实体。第二种模式是在一定区域内保持会话连续性。TUPF在一定的区域内不变，在用户使用的用户设备(User Equipment，UE)移动出该区域时，TUPF发生变化，所以，是在一定或者说特定的区域内保证会话的连续性，在该区域外不保证会话的连续性。第三种是在TUPF变化的情况下，保证会话连续性。在第三种模式下，TUPF发生变化，可以通过如下方式来保证会话连续性：对于UE新发起的会话，使用新的TUPF；对于UE现有的会话，仍然使用当前的TUPF。为了描述方便，下面将SSC mode的第一种模式，第二种模式和第三种模式分别称为SSC mode1，SSC mode2和SSC mode3。
在现有方案中，对于SSC mode2类型与SSC mode3类型的分组数据单元(Packet Data Unit，PDU)会话，由于UE位置变更等事件需要选择会话管理功能实体(Session Management Function，SMF)时(所选择的SMF可以是当前SMF，也可以是一个重选的新SMF)，将由接入和移动性管理功能实体(Access and Mobility Management Function，AMF)执行SMF选择操作，但该方式存在以下缺陷：AMF不感知PDU会话管理相关信息，若继续由AMF执行SMF选择操作，可能导致所选择SMF不合理。
发明内容
本发明实施例提供一种选择会话管理功能实体的方法、装置及系统，以解决现有技术中选择的会话管理功能实体不合理的问题。
为达到上述目的，本发明实施例提供如下技术方案：
第一方面，提供一种选择会话管理功能实体的方法，该方法包括：首先，接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和重选指示，所述重选指示用于指示重选会话管理功能实体；然后，根据该重选指示保存第一会话的信息与第一会话管理功 能实体的对应关系；之后，接收携带第一会话的信息的会话建立请求消息，确定不同于第一会话管理功能实体的第二会话管理功能实体；发送会话管理请求给所述第二会话管理功能实体。其中，所述第一会话管理功能实体是通过查询自身保存的所述对应关系确定的所述第一会话的信息对应的会话管理功能实体。
由于第一会话管理功能实体可以感知会话管理相关信息，因此由第一会话管理功能实体来确定是否重选会话管理功能实体，如果需要确定重选，则发送重选指示，然后重选指示的接收方就选择第一会话管理功能实体之外的其他会话管理功能实体来继续为UE服务，要比现有技术中选择的会话管理功能实体更加合理。其中，重选指示具体可以用于指示该第一会话需要重选会话管理功能实体。
在一种可能的设计中，第一会话的信息包括所述第一会话的标识，或，第一会话的信息包括UE的标识和第一会话的标识。
在一种可能的设计中，会话建立请求消息除携带第一会话的信息外，还携带所述UE待创建的第二会话的标识。这种情况对应UE为待创建的会话分配的会话标识和第一会话的标识不同。
在一种可能的设计中，接收会话建立请求消息之前，还包括：发送重建会话指示给UE，以通知UE建立第二会话。
在一种可能的设计中，所述接收位置变更通知消息之前，还包括：建立所述第一会话；其中，第一会话管理功能实体是为第一会话服务的会话管理功能实体。
第二方面，本发明的实施例提供另一种选择会话管理功能实体的方法，该方法包括：首先，接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体重选结果，该会话管理功能实体重选结果包括第二会话管理功能实体的信息；然后，保存第一会话的信息与第二会话管理功能实体的对应关系；之后，接收携带第一会话的信息的会话建立请求消息，查询所述对应关系确定所述第一会话的信息对应的第二会话管理功能实体；发送会话管理请求给所述第二会话管理功能实体。
由于第一会话管理功能实体可以感知会话管理相关信息，因此由第一会话管理功能实体来确定是否重选会话管理功能实体，如果需要确定重选，则确定重选的会话管理功能实体并发送重选结果，然后重选结果的接收方就选择该重选结果来继续为UE服务，该方法要比现有技术中选择的会话管理功能实体更加合理。其中，重选结果具体可以包括为第一会话重选的第二会话管理功能实体。
第三方面，本发明的实施例提供另一种选择会话管理功能实体的方法，该方法包括：首先，接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体选择结果，所述会话管理功能实体选择结果包括第一会话管理功能实体的信息；或：接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和指示信息；然后，保存所述第一会话的信息与第一会话管理功能实体的对应关系；接着，接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；查询所述对应关系确定所述第一会话的信息对应的所述第一会话管理功能实体；发送会话管理请求给所述第一会话管理功能实体。由于第一会话管理功能实体可以感知会话管理相关信息，因此由第一会话管理功能实体来确定重选会话管理功能实体，要比现有技术中选择的会话管理功能实体更加合理。
第四方面，本发明的实施例提供一种选择会话管理功能实体的装置，该装置具有实现上述第一方面到第三方面任意一项提供的方法实施例的执行主体的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本发明的实施例提供一种选择会话管理功能实体的装置，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使该选择会话管理功能实体的装置执行如上述第一方面到第三方面任意一项的选择会话管理功能实体的方法。
第六方面，本发明的实施例提供一种选择会话管理功能实体的系统，包括上述方法实施例中或装置实施例中的执行主体，还包括第一会话管理功能实体。其中，第一会话管理功能实体用于确定是否需要重选会话管理功能实体，发送重选指示；或，第一会话管理功能实体用于确定重选的会话管理功能实体，并发送该重选结果。
第七方面，本发明实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第八方面，本发明实施例提供了一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1所示为本发明实施例的一种可能的系统网络示意图；
图2所示为本发明实施例的另一种可能的系统网络示意图；
图3所示为本发明实施例提供的计算机设备示意图；
图4所示为本发明实施例提供的一种选择会话管理功能实体的方法流程示意图；
图5所示为本发明实施例提供的另一种选择会话管理功能实体的方法流程示意图；
图6所示为本发明实施例提供的另一种选择会话管理功能实体的方法流程示意图；
图7所示为本发明实施例提供的另一种选择会话管理功能实体的方法流程示意图；
图8所示为本发明实施例提供的另一种选择会话管理功能实体的方法流程示意图；
图9所示为本发明实施例提供的另一种选择会话管理功能实体的方法流程示意图；
图10所示为本发明实施例提供的一种选择会话管理功能实体的装置结构示意图；
图11所示为本发明实施例提供的另一种选择会话管理功能实体的装置结构示意图；
图12所示为本发明实施例提供的另一种选择会话管理功能实体的装置结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知， 随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
本发明实施例提供一种选择会话管理功能实体的系统100，该系统100包括：移动性管理功能实体10和会话管理功能实体20。
在具体实现中，作为一种实现方式，首先，移动性管理功能实体10接收位置变更通知消息；然后，移动性管理功能实体10发送会话管理消息给会话管理功能实体20，其中，会话管理功能实体20可以作为第一会话管理功能实体。会话管理功能实体20收到会话管理消息后，确定是否要重选会话管理功能实体。如果需要重选，会话管理功能实体20向移动性管理功能实体10发送用户设备UE的第一会话的信息和重选指示，所述重选指示用于指示重选会话管理功能实体。移动性管理功能实体10根据该重选指示保存该第一会话的信息与第一会话管理功能实体的对应关系。然后，移动性管理功能实体10接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话的信息；在收到会话建立请求消息后，移动性管理功能实体10确定不同于第一会话管理功能实体20的会话管理功能实体，比如为第二会话管理功能实体，然后，移动性管理功能实体20发送会话管理请求给第二会话管理功能实体。
在上述提供的选择会话管理功能实体的方法中，由于会话管理功能实体20可以感知会话管理相关信息，因此由会话管理功能实体20来确定是否重选会话管理功能实体，如果需要确定重选，则发送重选指示给移动性管理功能实体10，由移动性管理功能实体10来选择会话管理功能实体20之外的其他会话管理功能实体来继续为UE服务，要比现有技术中移动性管理功能实体选择的会话管理功能实体更加合理。
其中，重选指示具体可以用于指示该第一会话需要重选会话管理功能实体。
在具体实现中，作为另一种实现方式，首先，移动性管理功能实体10接收位置变更通知消息；然后，移动性管理功能实体10发送会话管理消息给会话管理功能实体20。其中，会话管理功能实体20可以作为第一会话管理功能实体。会话管理功能实体20收到会话管理消息后，确定是否要重选会话管理功能实体。如果需要重选，则会话管理功能实体20确定重选的会话管理功能实体，比如为第三会话管理功能实体。在确定第三会话管理功能实体后，会话管理功能实体20向移动性管理功能实体10发送用户设备UE的第一会话的信息和会话管理功能实体重选结果，该会话管理功能实体重选结果包括上述确定的第三会话管理功能实体的信息。在接收到会话管理功能实体重选结果后，移动性管理功能实体10保存该第一会话的信息与第三会话管理功能实体的对应关系。之后，移动性管理功能实体10接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；在接收会话建立请求消息后，移动性管理功能实体10通过查询保存的对应关系确定所述第一会话的信息对应的会话管理功能实体，即第三会话管理功能实体，然后，移动性管理功能实体10发送会话管理请求第三会话管理功能实体。其中，上述确定的第三会话管理功能实体的信息可以为第三会话管理功能实体的标识，也可以为第三会话管理功能实体的地址，也可以为其他可以表示第三会话管理功能实体的信息，本申请不做限定。
在上述提供的选择会话管理功能实体的方法中，由于会话管理功能实体20可以感知会话管理相关信息，因此由会话管理功能实体20来确定是否重选会话管理功能实体，如 果需要确定重选，则确定重选的第三会话管理功能实体并发送重选结果，然后重选结果的接收方就选择该重选结果来继续为UE服务，该方法要比现有技术中选择的会话管理功能实体更加合理。
其中，重选结果具体可以包括为第一会话重选的第二会话管理功能实体。
在具体实现中，作为另一种实现方式，首先，移动性管理功能实体10接收位置变更通知消息；然后，移动性管理功能实体10发送会话管理消息给会话管理功能实体20。其中，会话管理功能实体20可以作为第一会话管理功能实体。会话管理功能实体20收到会话管理消息后，确定需重选UPF，则会话管理功能实体20向移动性管理功能实体10发送用户设备UE的第一会话的信息和会话管理功能实体选择结果，该会话管理功能实体选择结果包括第一会话管理功能实体的信息；或者，会话管理功能实体20收到会话管理消息后，确定需重选UPF，则会话管理功能实体20向移动性管理功能实体10发送用户设备UE的第一会话的信息和指示信息。在接收到会话管理功能实体20发送的上述信息后，移动性管理功能实体10保存该第一会话的信息与第一会话管理实体的对应关系。之后，移动性管理功能实体10接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；在接收会话建立请求消息后，移动性管理功能实体10通过查询保存的对应关系确定所述第一会话的信息对应的会话管理功能实体，即第一会话管理功能实体，然后，移动性管理功能实体10发送会话管理请求第一会话管理功能实体。其中，第一会话管理功能实体的信息可以为第一会话管理功能实体的标识，也可以为第一会话管理功能实体的地址，也可以为其他可以表示第一会话管理功能实体的信息，本申请不做限定。
其中，所述指示信息可以是会话重建指示，也可以是UPF重选指示，也可以是无需重选SMF的指示信息，也可以为会话释放定时器，或是其他隐式指示消息，本申请不做限定。
另外，上述确定需重选UPF的方法有多种，比如：先判断当前UPF是否能继续为UE提供服务，若当前UPF无法为UE提供服务，但是会话管理功能实体20所管理的其他UPF可以为UE提供服务。当然，也可以采用现有技术其他方法来确定需重选UPF。其中，当前UPF无法继续为UE提供服务的原因有多种，可以是源UPF的负载过重；也可以是因为UE位置的移动，从而导致源UPF无法继续为UE提供服务等。
在上述提供的选择会话管理功能实体的方法中，由于会话管理功能实体20可以感知会话管理相关信息，因此由会话管理功能实体20来确定会话管理功能实体，要比现有技术中移动性管理功能实体选择的会话管理功能实体更加合理。
其中，本申请所涉及到的用户设备UE可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备UE，移动台(Mobile station,MS)，终端(terminal)，终端设备(Terminal Equipment)，软终端等等。为方便描述，本申请中，上面提到的设备统称为用户设备或UE。
图1中，移动性管理功能实体10和会话管理功能实体20仅是一个名字，名字本身对实体不构成限定。例如，该“移动性管理功能实体”还有可能被替换为“接入和移动性管理功能实体”或其他名字；会话管理功能实体20也有可能被替换为“会话管理功能”或其他名字。而且，该移动性管理功能实体10还可以对应一个包括除了移动性管理功能外，还有其他功能的实体。会话管理功能实体20也可以对应一个包括除了会话管理功能外， 还有其他功能的实体。在此进行统一说明，以下不再赘述。
具体实现中，位置变更通知消息可以为切换通知消息，也可以为位置区更新请求消息，也可以为其他名称的消息，这里不做限定。会话管理消息可以为UE移动性事件通知消息，也可以为切换通知消息，也可以为非接入层(Non-Access-Stratum，NAS)通知消息(NAS Message Notify)，也可以为其他名称的消息，这里不做限定。会话管理请求可以为会话建立请求，也可以为其他名称的消息，这里不做限定。
具体实现中，第一会话的信息可以包括第一会话的标识；也可以包括UE标识和所述第一会话的标识，当然，也可以包括其他内容。
具体实现中，移动性管理功能实体10接收位置变更通知消息之前，所述第一会话已经建立，第一会话管理功能实体是为所述第一会话服务的会话管理功能实体。
具体实现中，会话管理功能实体20确定是否要重选会话管理功能实体的方法有多种：第一种，会话管理功能实体20确定自身负载过重，无法继续为UE提供服务；第二种，会话管理功能实体20确定当前为PDU会话提供服务的源用户面功能(User Plane Function，UPF)实体无法继续为UE提供服务，而能为UE提供服务的目标UPF是由其他会话管理功能实体管理，即：UE不在会话管理功能实体20的服务范围内。其中，源UPF无法继续为UE提供服务的原因有多种，可以是源UPF的负载过重；也可以是因为UE位置的移动，从而导致源UPF无法继续为UE提供服务。当然，会话管理功能实体20也可以采用现有技术中其他方法来确定是否要重选会话管理功能实体。其中，如果移动性管理功能实体10以下面实施例所述的SMF粒度向会话管理功能实体20发送会话管理消息，那么会话管理功能实体20可以先根据UE标识确定自身为UE提供服务的PDU会话，然后再确定PDU会话是否要重选SMF。
具体实现中，移动性管理功能实体10确定不同于会话管理功能实体20的会话管理功能实体的方法有多种，可以采用下面几种方法中的任一种，也可以采用现有技术中其他的方法。
第一种，移动性管理功能实体10根据UE位置，或者根据UE位置和数据网络信息查询拓扑管理功能实体，获取可以为UE提供服务的不同于会话管理功能实体20的会话管理功能实体。其中，数据网络信息可以为接入点名称(Access Point Name，APN)信息或数据网络名称(Data Network Name，DNN)信息。其中，拓扑管理功能实体在实际部署中可以单独设置，也可以与网络中现有网元合设，比如与域名服务器(Domain Name System，DNS)、移动性管理功能实体10、或网元注册与发现功能实体(Network Repository Function，NRF)或(Network Function Repository Function,NRF)进行合设。
具体的，可以由拓扑管理功能实体获取到当前可以为UE提供服务的其他UPF列表，获取(比如向DNS查询)UPF列表中各UPF所对应的会话管理功能实体信息，选择对应的不同于会话管理功能实体20的会话管理功能实体。其中，会话管理功能实体信息包括会话管理功能实体的标识和/或会话管理功能实体的负载。
第二种，选择用户签约数据中配置的不同于会话管理功能实体20的会话管理功能实体。
第三种，若UE已有相同数据网络信息的PDU会话，则选择该PDU会话所对应的不同 于会话管理功能实体20的会话管理功能实体。
第四种，根据UE标识和网络配置信息，构造会话管理功能实体主机名，获取(比如向DNS查询)该主机名对应的不同于会话管理功能实体20的会话管理功能实体。
具体实现中，会话管理功能实体20确定重选的第三会话管理功能实体的方法，具体可以是，会话管理功能实体20可以采用上面第一种方法来确定第三会话管理功能实体，即：根据UE位置，或者根据UE位置和数据网络信息查询拓扑管理功能实体，获取可以为UE提供服务的不同于会话管理功能实体20的会话管理功能实体。会话管理功能实体20也可以采用现有技术中其他方法。
具体实现中，UE位置(或者说目标接入区域信息)，可以为目标基站标识、或目标小区标识、或目标跟踪区标识，也可以是其他可以表示UE待切换到的位置信息，这里不做限定。
如图2所示，为本申请提供的一种具体的5G系统200例子，当然本申请不限于该系统中。本发明实施例提供的选择会话管理功能实体方法，可应用于如图1和2所示的系统中。
在图2所示的系统200中，包括AMF和SMF。AMF为图1中移动性管理功能实体10的一个示例，SMF为图1中会话管理功能实体20的一个示例。其中，AMF为接入和移动性管理功能实体，进行UE的接入与移动性管理，接收策略功能实体(Policy Function，PCF)提供的UE移动性以及网络选择策略并进行策略执行。SMF为会话管理功能实体，进行会话管理，接收PCF提供的会话或业务流控制策略并执行策略，还可以选择TUPF、或分配UE的网际协议(Internet Protocol，IP)地址等功能。
该系统200还可以包括PCF，TUPF或接入网(Access Network，AN)。PCF为策略控制功能实体，主要负责针对会话级别或业务流级别进行计费、服务质量(Quality of Service，QoS)、移动性等策略控制。TUPF作为和数据网络(Data Network)的接口用户面功能，完成用户面数据转发、基于会话级别或业务流级别的计费统计、带宽限制等功能。AN为5G中的接入网，进行承载资源的分配调度等功能。其中，AN和TUPF之间也可能还有其他的用户面功能实体。
在该系统200中，通过使用本申请提供的会话管理功能实体选择方法，由于SMF可以感知会话管理相关信息，比如，SMF服务范围、SMF负载、UPF负载或SSC mode，因此由SMF来确定是否重选SMF，或者由SMF来选择重选的SMF，要比现有技术中AMF选择的SMF更加合理。
上述系统100或系统200中的任意一种功能节点或网元，具体实现中，可能由一个实体设备实现，也可能由多个实体设备共同实现，本发明实施例对此不作具体限定。即，可以理解的是，上述系统100或系统200中的任意一种功能节点或者网元，都可能是实体设备内的一个逻辑功能模块，也可能是由多个实体设备组成的一个逻辑功能模块，本发明实施例对此不作具体限定。
如图3所示，图1中的移动性管理功能实体10，或者图2中的AMF可以以图3中的计算机设备(或系统)的方式来实现。
图3所示为本发明实施例提供的计算机设备示意图。计算机设备300包括至少一个处 理器31，通信总线32，存储器33以及至少一个通信接口34。
处理器31可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线32可包括一通路，在上述组件之间传送信息。所述通信接口34，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器33可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器33用于存储执行本发明方案的应用程序代码，并由处理器31来控制执行。所述处理器31用于执行所述存储器33中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器31可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备300可以包括多个处理器，例如图3中的处理器31和处理器38。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备300还可以包括输出设备35和输入设备36。输出设备35和处理器31通信，可以以多种方式来显示信息。例如，输出设备35可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备36和处理器31通信，可以以多种方式接受用户的输入。例如，输入设备36可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备300可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备300可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图3中类似结构的设备。本发明实施例不限定计算机设备300的类型。
示例性的，图1中的移动性管理功能实体10或者图2中的AMF可以为图3所示的设备，移动性管理功能实体10或者AMF的存储器中存储了一个或多个软件模块。移动性管理功能实体10或者AMF可以通过处理器以及存储器中的程序代码来实现软件模块，实现会话管理功能实体的选择。
下面结合流程图来介绍本发明实施例提供的选择会话管理功能实体的方法。
图4提供了一种选择会话管理功能实体的方法流程示意图。图1中会话管理功能实体10和会话管理功能实体20之间的交互，或者与外部网元之间的交互，可以采用该方法实施例中的方法。图2中AMF和SMF之间的交互，或者与外部网元之间的交互，也可以采用该方法实施例中的方法。该实施例以会话及业务连续性模式为SSC mode2为例。
S401，UE通过AN发送会话建立请求到AMF，AMF为该会话选择SMF为其提供服务，并保存SMF与PDU会话的对应关系，同时将会话建立请求发送至SMF，SMF建立对应的PDU会话并建立用户面传输路径。这里的AN可以为下一代接入网。具体的PDU会话建立过程同现有技术，这里不再赘述。
在401步骤中，UE可能触发一个PDU会话建立，为便于描述，可记作PDU Session1会话；也可能触发多个PDU会话建立过程，为便于描述，多个PDU会话可分别记作PDU Session1，PDU Session2等会话。
S403，UE与AN协商，在需要进行切换时，AN向AMF发送切换通知消息。AMF接收切换通知消息。
其中，UE执行切换的场景比较多，比如，当前为UE提供服务的网络的服务质量比较差，或者当前为UE提供服务的网络的负荷过重等，这里不再赘述。
该切换通知消息中包括UE位置信息(即：目标接入区域信息)和UE标识，本实施例中，目标接入区域信息以目标基站标识为例。
S405，AMF根据UE标识确定S401中为UE所建立的PDU会话信息，并发送会话管理消息给上述所建立的PDU对话对应的SMF。例如：在一种实现方式中，S401中为UE建立的PDU会话为PDU Session1与PDU Session2，则AMF将分别发送会话管理消息至为PDU Session1提供服务的SMF1及为PDU Session2提供服务的SMF2，其中SMF1与SMF2可能为同一SMF功能实体。在另一种实现方式中，S401中为UE建立的PDU会话为PDU Session1，则AMF将发送会话管理消息至为PDU Session1提供服务的SMF1。
在本实施例中，以S401中为UE建立的PDU会话为PDU Session1为例，相应的，AMF发送会话管理消息至PDU Session1所对应的SMF1。SMF1接收该会话管理消息。
其中，该会话管理消息中携带UE标识、PDU Session1的信息和UE位置信息。
PDU session1的信息可以为PDU session1的ID，也可以为UE ID和PDU session1的ID，或者其他可以表示PDU session1的信息。
S407，SMF1收到会话管理消息后，确定需要重选SMF。
具体实现中，SMF根据PDU Session1的信息确定对应的PDU Session和PDU Session1会话的会话及业务连续性模式为SSC mode2。
具体实现中，SMF1确定是否重选SMF的方法可以采用图1中所述的方法来确定。即：根据SMF1的负载信息、SMF1管理的UPF负载信息、或SMF1的服务范围来确定需要进行SMF重选。
在本实施例中，假设目标基站不在SMF1的服务范围内，所以SMF1无法继续为UE提供服务。因此，SMF1确定需要重选SMF。
S409，SMF1发送会话管理响应给AMF，其中，该会话管理响应中携带PDU Session1 的信息和用于指示重选SMF的重选指示。AMF接收该会话管理响应。
其中，该会话管理响应可以为UE移动性事件响应，也可以为切换响应，也可以为其他名称的消息，这里不做限定。
S411，当AMF接收会话管理响应后，若该请求中携带重选指示，AMF则保存PDU Session1的信息与SMF1的对应关系。该对应关系用于后续AMF在收到来自UE的会话建立请求时来进行SMF的重选。
其中，该对应关系可以以表格或图表等形式保存，这里不做限制。
在一种具体实现中，该对应关系还可以包括上述重选指示。
其中，保存的SMF1的信息可以为SMF1的名字，或者为SMF1ID，或者其他可以表示SMF1的信息。本申请不做限定。
这里，保存SMF1信息的目的是为了后续AMF在重选SMF时避免重选至SMF1。
S413，AMF发送切换命令至AN，以指示完成后续切换流程。
S415，在切换完成后，SMF将发起PDU Session 1释放流程。
在释放过程中，SMF还将发送重建会话指示通知UE在会话释放完成后发起新的PDU会话建立请求。其中，该重建会话指示可以为特定原因值，也可以为特定指示，本申请对此不做限制。
S417，UE在原会话释放完成后，发送会话建立请求给AMF。AMF接收该会话建立请求。该会话建立中包括PDU Session1的信息。
这样，通过发送会话建立请求给AMF，发起了新PDU会话(或者说目标PDU会话)的建立。AMF收到PDU session1的信息后，会查询所保存的对应关系，避免AMF在重选SMF时选择SMF1。
其中，会话建立请求中携带UE为本次待建立的新PDU会话分配的PDU Session ID。
如果UE为该新PDU会话分配的是PDU Session1的ID，则会话建立请求中携带PDU Session1的ID，或者携带UE标识和PDU Session1的ID。
如果UE为该新PDU分配的是一个新的会话ID(即不同于PDU Session1的ID)，则会话建立请求中携带该新的会话ID和PDU Session1的ID，或者携带该新的会话ID、UE标识和PDU Session1的ID。
对于UE为本次待建立的PDU会话分配的会话标识为原PDU会话(即：PDU Session1)的会话标识的情况，是因为PDU Session1已经被释放，所以PDU Session1的会话标识也被释放掉了。
会话建立请求中还可以携带UE的位置信息，还可以携带DNN信息(比如：DNN标识等)。
S419，AMF接收会话建立请求后，确定不同于所述第一SMF的第二SMF为重选的SMF，即由第二SMF来为UE服务。
其中，AMF确定不同于所述第一SMF的第二SMF的方法，可以采用图1中所述的方法来确定。这里不再赘述。
其中，AMF在确定第二SMF过程中，会查找保存的对应关系以避免选择AMF中保存的SMF1。
S421，AMF发送会话管理请求给SMF2。SMF2接收该会话管理请求。
其中，在具体实现中，会话管理请求可以为会话创建请求，或者为其他名字，本申请不做限定。
S423，SMF2为UE分配新的TUPF及IP地址。
其中，TUPF作为新建立的会话的锚定UPF，用于建立新侧PDU会话的用户面路径，新的IP地址则用于UE与数据网络间进行数据传输使用。
S425，SMF2为UE发起新的PDU会话建立流程。
在本实施例提供的选择会话管理功能实体的方法中，由于SMF1可以感知会话管理相关信息，因此由SMF来确定是否重选SMF，如果需要确定重选，则发送重选指示给AMF，由AMF来选择SMF1之外的其他SMF来继续为UE服务，要比现有技术中AMF选择的SMF更加合理。
上述图4所示的实施例中，步骤403中，AMF接收的是切换通知。在具体实现中，在UE位置区更新的场景中，也会选择会话管理功能实体。在位置区更新场景下，该选择会话管理功能实体的方法流程与图4所述的切换场景的主要区别为S403，S413和S415不同。
对应图4的S403，在位置区更新场景中，其流程与切换场景的主要区别描述如下：
UE通过目标AN向AMF发起位置区更新请求消息。该请求可能由于UE移动到新的位置区、或定时器触发UE发起周期性位置区更新，或UE移动至另一网络覆盖范围等触发。
相应的，对应S413，AMF向AN发送的是位置区更新响应消息(TAU Response或TAU Accept消息)，消息中所携带指示信息不变。
相应的，对应S415，由于此时UE处于空闲状态，因此原PDU会话不存在空口承载，在触发原PDU会话释放流程前，还需执行UE、目标AN及UPF间用户面连接的建立过程。除此之外，其他步骤与切换场景下流程一致。
在上述图4所示的实施例中，AMF向SMF发送会话管理消息时，会以PDU会话粒度向每个PDU会话所对应的SMF发送会话管理消息，这样，若某个SMF同时为UE的多个PDU会话提供服务，则在该流程中该SMF可能收到多次会话管理消息。
在另一种可能的实现中，AMF也可以以SMF粒度向当前服务该UE的SMF发送会话管理消息，即为UE多个PDU会话提供服务的同一个SMF在该流程中将仅收到一次会话管理消息。在该消息通知方式下，与原流程主要区别为S405、S407、S409、S411不同，具体不同点如下所述。
由于S401可能涉及多个PDU会话建立过程，为便于描述，此处以UE建立了三个PDU会话进行举例，分别记为PDU Session 1，PDU Session 2与PDU Session 3。其中PDU Session1与PDU Session 2由SMF1提供服务，PDU Session 3由SMF2提供服务。
对应图4在新的消息通知方式下，其流程与当前流程的主要区别描述如下：对应S405的为S405’，AMF在收到AN所发送切换通知后，AMF将根据切换通知中的UE标识及S401中所保存的PDU会话和SMF的对应关系，确定为UE提供服务的SMF的信息。在该例中，对应SMF1与SMF2，AMF向SMF1与SMF2发送会话管理消息。该会话管理消息中携带UE标识和UE位置信息。
相应地，对应S407的为S407’，各SMF收到AMF所发送会话管理消息后，将先根据UE标识确定其为UE提供服务的各PDU会话(在本例中SMF1查询得到结果为PDU Session 1与PDU Session 2，SMF2查询得到结果为PDU Session 3)，随后对各PDU会话判断是否需要重选SMF，判断是否需要重选SMF的依据与图4流程中所描述方式一致。这里，假定SMF1判断PDU Session 1与PDU Session 2需要重选SMF，SMF2判断PDU Session 3需要重选SMF。
相应地，对应S409的为S409’，各SMF对所提供服务的PDU会话判断完成需要重选SMF后，将返回会话管理响应至AMF，并在该响应消息中携带需重选SMF的PDU会话和重选指示。在本例中，由于PDU Session 1与PDU Session 2均需重选SMF，因此SMF1将同时返回PDU Session 1与PDU Session 2的信息和重选指示；SMF2返回PDU Session 3的信息和重选指示。
具体实现中，如果一个SMF提供服务的多个PDU Session都需要重选SMF，那么该SMF返回的会话管理响应中的重选指示可以是一个，也可以是每个需要重选的PDU Session有一个重选指示。比如：上述例子中的SMF1返回的可以是：PDU Session1的信息，PDU Session2的信息，和一个重选指示；也可以是：PDU Session1的信息，指示PDU Session1需要重选的重选指示1，PDU Session2的信息，指示PDU Session2需要重选的重选指示2。具体实现中，还可以是上述两种方式的结合，即：一个PDU Session对应1个重选指示，和多个PDU Session对应1个重选指示结合使用。当然，也不排除其他方式，本申请对此不作限定。
其中，该重选指示可以为特定原因值，也可以为特定指示，本发明对此不做限制。
相应地，对应S411的为S411’，当AMF接收SMF1与SMF2所返回的会话管理响应后，若该响应中携带重选指示与待重选SMF的PDU会话信息，或携带了待重选SMF的PDU会话信息，AMF则保存对应PDU会话的信息与当前为其提供服务的SMF的对应关系，保存格式与图4流程中所描述方式一致。该对应关系用于后续AMF在收到来自UE的会话建立请求时来进行SMF的重选。
在另一种可能的实现中，在上述图4所示的实施例中，步骤407是由AMF所发送会话管理消息所触发。在具体实现中，若SMF判断PDU Session1所对应的UPF过载或所对应的SMF发生过载等场景下，也会选择会话管理功能实体。在该场景下，该选择会话管理功能实体的方法流程与图4所示的切换场景的主要区别为S403，S405，S409，S413，S415不同。
具体来说，对应图4的S403与S405，在UPF或SMF过载场景下，其流程与切换场景的主要区别描述如下：
SMF直接根据自身或来自其他功能实体的消息获取到UPF或SMF负载等因素，触发步骤S407。该信息可能包含UPF负载情况，SMF负载情况，或UPF故障等信息。
相应的，对应S409，该消息可为会话管理通知消息，也可为其他消息，这里不作限制。该消息中所携带指示信息不变。
相应的，对应S413，由于该流程不是由UE或AN触发，因此AMF将不执行该步骤。
对应S415，该消息将经由AMF向UE发送会话重建指示，在具体实现中，步骤415可与步骤S409分开执行，也可与步骤S409合并发送。除此之外，其他步骤与切换场景下流程一致。
在图4所示的实施例中，AMF的动作可以由AMF可以根据上述提及的存储器中的软件模块来执行。本发明实施例对此不作任何限制。
图5提供了另一种选择会话管理功能实体的方法流程示意图。图1中会话管理功能实体10和会话管理功能实体20之间的交互，或者与外部网元之间的交互，可以采用该方法实施例中的方法。图2中AMF和SMF之间的交互，或者与外部网元之间的交互，也可以采用该方法实施例中的方法。该实施例以会话及业务连续性模式为SSC mode3为例。
S501-S505，同S401-S405。
S507，SMF1收到会话管理消息后，确定是否需要重选SMF。
具体实现中，SMF根据PDU Session1的信息确定对应的PDU Session和PDU Session1会话的会话及业务连续性模式为SSC mode3。
具体实现中，SMF1确定是否重选SMF的方法可以采用图1中所述的方法来确定。
S509-S513，同S409-S413。
S515，SMF在切换完成后发送会话重定向请求至UE，并在该请求中携带重建会话指示，以通知UE发起新的PDU会话的建立。UE接收该重定向请求。
其中，该会话重定向请求可以为会话重建请求，也可以为其他消息名称，本申请不做限制。
S517-S525，同S417-S425。
S527，待原PDU会话上的业务流结束后，原PDU会话将通过原PDU会话释放流程被释放掉。
在本实施例提供的选择会话管理功能实体的方法中，由于SMF1可以感知会话管理相关信息，因此由SMF1来选择重选的SMF，这样选择的SMF要比现有技术中AMF选择的SMF更加合理。
在位置区更新场景下，该选择会话管理功能实体的方法流程与图5所述的切换场景的主要区别为S503和S513不同：
在位置区更新场景下，对应S503，UE通过目标AN向AMF发起位置区更新请求；相应的，对应S513，AMF向AN发送的是位置区更新响应消息。
上述图5所示的实施例中，AMF向SMF发送会话管理消息时，会以PDU会话粒度向每个PDU会话所对应的SMF发送会话管理消息，这样，若某个SMF同时为UE的多个PDU会话提供服务，则在该流程中该SMF可能收到多次会话管理消息。
在另一种可能的实现中，AMF也可以以SMF粒度向当前服务该UE的SMF发送会话管理消息，即为UE多个PDU会话提供服务的同一个SMF在该流程中将仅收到一次会话管理消息。在该消息通知方式下，与原流程主要区别为S505、S507、S509、S511不同。S505、S507、S509和S511分别替换为S505’、S507’、S509’和S511’。S505’、S507’、S509’和S511’分别与S405’、S407’、S409’和S411’相同，这里不再赘述。
在另一种可能的实现中，步骤507是由AMF所发送会话管理消息所触发。在具体实现中，若SMF判断PDU Session1所对应的UPF过载或所对应的SMF发生过载等场景下，也会选择会话管理功能实体。在该场景下，该选择会话管理功能实体的方法流程与图5所述的切换场景的主要区别为S503，S505，S509，S513，S515不同。
具体的，对应图5的S503与S505，在UPF或SMF过载场景下，其流程与切换场景的主要区别描述如下：SMF直接根据自身或来自其他功能实体的消息获取到UPF或SMF负载等因素，触发步骤S507。该信息可能包含UPF负载情况，SMF负载情况，或UPF故障等信息。
相应的，对应S513，由于该流程不是由UE或AN触发，因此AMF将不执行该步骤。
对应S515，该消息将经由AMF向UE发送会话重建指示，在具体实现中，该步骤可与步骤S509分开执行，也可与步骤S509合并发送。除此之外，其他步骤与切换场景下流程一致。
在图5所示的实施例中，AMF的动作可以由AMF可以根据上述提及的存储器中的软件模块来执行。本发明实施例对此不作任何限制。
图6提供了另一种选择会话管理功能实体的方法流程示意图。图1中会话管理功能实体10和会话管理功能实体20之间的交互，或者与外部网元之间的交互，可以采用该方法实施例中的方法。图2中AMF和SMF之间的交互，或者与外部网元之间的交互，也可以采用该方法实施例中的方法。该实施例以会话及业务连续性模式为SSC mode2为例。
S601-S605，同S401-S405。
S607，SMF1收到会话管理消息后，确定是否需要重选SMF。若确定需要重选SMF，则SMF1确定第二SMF，即第二SMF为重选的SMF，由第二SMF来为UE服务。
具体实现中，SMF根据PDU Session1的信息确定对应的PDU Session和PDU Session1会话的会话及业务连续性模式为SSC mode2。
其中，SMF1确定是否重选SMF的方法同S407中所述。
SMF1确定第二SMF的方法，可以采用图1中会话管理功能实体20确定重选的第三会话管理功能实体的方法来确定。即：通过拓扑管理功能实体获取其他SMF的负载信息或UPF的负载信息，确定可以为UE提供服务的不同于SMF1的SMF来为UE提供服务。
S609，SMF1发送会话管理响应给AMF，其中，该会话管理响应中携带PDU Session1的信息和SMF重选结果，这里，SMF重选结果为第二SMF的信息。AMF接收该会话管理响应。
S611，当AMF接收会话管理响应后，保存PDU Session1的信息与第二SMF信息的对应关系。该对应关系用于后续，AMF在收到来自UE的会话建立请求时选择第二SMF作为为UE服务的SMF。
其中，该对应关系可以以表格或图表等形式保存，这里不做限制。
在一种具体实现中，该对应关系还可以包括需重选SMF的指示信息。该需重选SMF的指示信息可为特定指示，也可为特定原因值，本申请不做限定。
其中，保存的第二SMF的信息，可以为第二SMF的名字，也可以为第二SMF的ID，或者为其他可以表示SMF的信息，本申请不做限定。
S613-S617，同S413-S417。
S619，AMF收到会话建立请求后，查询所述对应关系确定PDU session1的信息对应的SMF为SMF2。即选择第二SMF来为UE服务。
其中，AMF在确定第二SMF过程中，会根据会话建立请求消息中携带的PDU session1 的信息查询所述对应关系来确定SMF2。
S621-S625，同S421-S425。
在本实施例提供的选择会话管理功能实体的方法中，由于SMF1可以感知会话管理相关信息，因此由SMF1来确定是否重选SMF，如果需要确定重选，则确定重选的SMF并发送重选结果给AMF，要比现有技术中AMF选择的SMF更加合理。
在具体实现中，图6所述的方法也适用于UE位置区更新的场景。在位置区更新场景下，该选择会话管理功能实体的方法流程与图6所述的切换场景的主要区别为S603，S613和S615不同。
对应图6的S603，在位置区更新场景中，其流程与图6的切换场景的主要区别描述如下：
UE通过目标AN向AMF发起位置区更新请求消息。该请求可能由于UE移动到新的位置区、或定时器触发UE发起周期性位置区更新，或UE移动至另一网络覆盖范围等触发。
相应的，对应S613，AMF向AN发送的是位置区更新响应消息，消息中所携带指示信息不变。其中，是位置区更新响应消息可以是TAU Response或TAU Accept消息，或者是其他名称。
相应的，对应S615，由于此时UE处于空闲状态，因此原PDU会话不存在空口承载，在触发原PDU会话释放流程前，还需执行UE、目标AN及UPF间用户面连接的建立过程。除此之外，其他步骤与切换场景下流程一致。
上述图6所示的实施例中，AMF向SMF发送会话管理消息时，会以PDU会话粒度向每个PDU会话所对应的SMF发送会话管理消息，这样，若某个SMF同时为UE的多个PDU会话提供服务，则在该流程中该SMF可能收到多次会话管理消息。
在另一种可能的实现中，AMF也可以以SMF粒度向当前服务该UE的SMF发送会话管理消息，即为UE多个PDU会话提供服务的同一个SMF在该流程中将仅收到一次会话管理消息。在该消息通知方式下，与原流程主要区别为S605、S607、S609、S611不同，具体不同点如下所述。
由于S601可能涉及多个PDU会话建立过程，为便于描述，此处以UE建立了三个PDU会话进行举例，分别记为PDU Session 1，PDU Session 2与PDU Session 3。其中PDU Session1与PDU Session 2由SMF1提供服务，PDU Session 3由SMF2提供服务。
对应图6，在新的消息通知方式下，其流程与当前流程的主要区别描述如下：
对应S605的为S605’，AMF在收到AN所发送切换通知后，AMF将根据切换通知中的UE标识及S601中所保存的PDU会话和SMF的对应关系，确定为UE提供服务的SMF的信息。在该例中，对应SMF1与SMF2，AMF向SMF1与SMF2发送会话管理消息。
该会话管理消息中携带UE标识和UE位置信息。
相应地，对应S607的为S607’，各SMF收到AMF所发送会话管理消息后，将先根据UE标识确定其为UE提供服务的各PDU会话(在本例中SMF1查询得到结果为PDU Session1与PDU Session 2，SMF2查询得到结果为PDU Session 3)，随后对各PDU会话判断是否需要重选SMF，若SMF需要重选，则执行SMF重选操作，确定另一SMF为UE提供服务，判断是否需要重选及重选过程与图6流程中所描述方式一致。此时假定SMF1判断PDU Session 1与PDU Session 2需要重选SMF，并为其分别选择SMF3与SMF4提供服务，SMF2判断PDU Session 3需要重选SMF，并为其选择SMF5提供服务，其中，SMF3、SMF4、SMF5可能为相同，也可能为不同SMF。
相应地，对应S609的为S609’，各SMF对所提供服务的PDU会话判断完成需要重选SMF后，将返回会话管理响应至AMF，并在该响应消息中携带会话信息和重选SMF的重选结果。在本例中，由于PDU Session 1与PDU Session 2均需重选SMF，因此SMF1将同时返回PDU Session 1与PDU Session 2的信息，和重选SMF的重选结果，即SMF3与SMF4的信息；SMF2返回PDU Session 3的信息重选SMF的重选结果，即SMF5的信息。
相应地，对应S611的为S611’，当AMF接收SMF1与SMF2所返回的会话管理响应后，若该响应中携带重选结果与需重选SMF的PDU会话信息，AMF则保存对应PDU会话的信息与所重选SMF信息的对应关系，保存格式与图6流程中所描述方式一致。该对应关系用于后续，AMF在收到来自UE的会话建立请求时为其选择对应SMF提供服务。
在另一种可能的实现中，步骤607是由AMF所发送会话管理消息所触发。在具体实现中，若SMF判断PDU Session1所对应的UPF过载或所对应的SMF发生过载等场景下，也会选择会话管理功能实体。在该场景下，该选择会话管理功能实体的方法流程与图6所述的切换场景的主要区别为S603，S605，S609，S613，S615不同。具体不同，同图4中描述类似，这里不再赘述。
在图6所示的实施例中，AMF的动作可以由AMF可以根据上述提及的存储器中的软件模块来执行。本发明实施例对此不作任何限制。
图7提供了另一种选择会话管理功能实体的方法流程示意图。图1中会话管理功能实体10和会话管理功能实体20之间的交互，或者与外部网元之间的交互，可以采用该方法实施例中的方法。图2中AMF和SMF之间的交互，或者与外部网元之间的交互，也可以采用该方法实施例中的方法。该实施例以会话及业务连续性模式为SSC mode3为例。
S701-S705，同S601-S605。
S707，SMF1收到会话管理消息后，确定是否需要重选SMF。若确定需要重选SMF，则SMF1确定第二SMF，即第二SMF为重选的SMF，由第二SMF来为UE服务。
具体实现中，SMF根据PDU Session1的信息确定对应的PDU Session和PDU Session1会话的会话及业务连续性模式为SSC mode3。
S709-S711，同S609-S611。
S713-S715，同S513-S515。
S717-S725，同S617-S625。
S727，待原PDU会话上的业务流结束后，原PDU会话将通过原PDU会话释放流程被释放掉。
在本实施例提供的选择会话管理功能实体的方法中，由于SMF1可以感知会话管理相关信息，因此由SMF1来选择重选的SMF，这样选择的SMF要比现有技术中AMF选择的SMF更加合理。
在位置区更新场景下，该选择会话管理功能实体的方法流程与图6所述的切换场景的主要区别为S603和S613不同：
对应图7，在位置区更新场景下，对应S703，UE通过目标AN向AMF发起位置区更新请求；相应的，对应S713，AMF向AN发送的是位置区更新响应消息。
上述图7所示的实施例中，AMF向SMF发送会话管理消息时，会以PDU会话粒度向每个PDU会话所对应的SMF发送会话管理消息，这样，若某个SMF同时为UE的多个PDU会话提供服务，则在该流程中该SMF可能收到多次会话管理消息。
在另一种可能的实现中，AMF也可以以SMF粒度向当前服务该UE的SMF发送会话管理消息，即为UE多个PDU会话提供服务的同一个SMF在该流程中将仅收到一次会话管理消息。在该消息通知方式下，与原流程主要区别为S705、S707、S709、S711不同。S705、S707、S709和S711分别替换为S705’、S707’、S709’和S711’。S705’、S707’、S709’和S711’分别与S605’、S607’、S609’和S611’相同，这里不再赘述。
在另一种可能的实现中，步骤707是由AMF所发送会话管理消息所触发。在具体实现中，若SMF判断PDU Session1所对应的UPF过载或所对应的SMF发生过载等场景下，也会选择会话管理功能实体。在该场景下，该选择会话管理功能实体的方法流程与图7所述的切换场景的主要区别为S703，S705，S709，S713，S715不同。具体不同，同图5中描述类似，这里不再赘述。
在图7所示的实施例中，AMF的动作可以由AMF可以根据上述提及的存储器中的软件模块来执行。本发明实施例对此不作任何限制。
图8提供了一种选择会话管理功能实体的方法流程示意图。图1中会话管理功能实体10和会话管理功能实体20之间的交互，或者与外部网元之间的交互，可以采用该方法实施例中的方法。图2中AMF和SMF之间的交互，或者与外部网元之间的交互，也可以采用该方法实施例中的方法。该实施例以会话及业务连续性模式为SSC mode2为例，UPF需重选，但SMF不需重选。
S801，同S401；
S803，SMF1判断UE上某PDU会话需重选UPF。为便于描述，此处以PDU Session1为例。
具体实现中：该步骤触发原因可能为UE位置信息，UPF负载信息，或SMF1负载信息等，也可由其他信息触发，本申请对此不作限定。
具体实现中，SMF1根据PDU Session1的信息确定对应的PDU Session和PDU Session1会话的会话及业务连续性模式为SSC mode2。
具体实现中，SMF1确定需重选UPF的方法可以采用图1中所述的方法来确定。
在本实施例中，假设当前UPF由于过载或故障导致其无法为UE提供服务，而目标接入区域仍在SMF1的服务范围内，且SMF1所管理的其他UPF信息满足为UE服务的条件，则SMF1可以继续为UE提供服务。因此，SMF1确定需重选UPF。
S805，SMF1返回会话管理通知，并在该通知中携带PDU Session1信息及指示信息。
在具体实现中，也可以在SMF1返回的会话管理通知中携带PDU Session1信息和SMF1的信息。
其中，该会话管理通知可以为UE移动性事件通知，也可以为会话管理事件通知，也可以为其他名称，这里不做限定。
S807，当AMF接收会话管理通知后，保存PDU Session1的信息与SMF1的对应关系。该对应关系用于后续AMF在收到来自UE的会话建立请求时来进行SMF的重选。
具体实现中，若S805中，SMF1所发送会话管理通知中携带了指示信息，则该对应关系中也可包括该指示信息。
这里，保存SMF1信息的目的是为了后续AMF在重选SMF时继续选择SMF1为UE提供服务。
这里，保存指示信息的目的是为了后续AMF在选择SMF时避免选择不同于SMF1的另一SMF。该指示信息如图1中所述的，可以为多种形式。
S809，由于该PDU会话为SSC mode2，SMF还将向UE发起PDU会话释放命令，并在该消息中携带重建会话指示，该消息在传递过程中将由AMF进行转发。
具体实现中，该消息可与消息S805合并发送，在这里不作限制。
S811，与S417不同的是，AMF收到PDU session1的信息后，会查询所保存的对应关系，保证AMF在选择SMF时继续选择SMF1为UE提供服务。
其他同S417。
S813，AMF接收会话建立请求后，确定继续选择第一SMF来为UE服务，即SMF1。
其中，AMF在确定第一SMF过程中，会查找保存的对应关系以避免选择不同于AMF中保存的SMF1的SMF。
S815，AMF发送会话管理请求给SMF1。SMF1接收该会话管理请求。
其中，在具体实现中，会话管理请求可以为会话创建请求，或者为其他名字，本申请不做限定。
S817，SMF1的处理同S423中SMF2。
S819，SMF1为UE发起新的PDU会话建立流程。
在本实施例提供的选择会话管理功能实体的方法中，由于SMF1可以感知会话管理相关信息，因此由SMF来确定的SMF要比现有技术中AMF选择的SMF更加合理。
图9提供了一种选择会话管理功能实体的方法流程示意图。图1中会话管理功能实体10和会话管理功能实体20之间的交互，或者与外部网元之间的交互，可以采用该方法实施例中的方法。图2中AMF和SMF之间的交互，或者与外部网元之间的交互，也可以采用该方法实施例中的方法。该实施例以会话及业务连续性模式为SSC mode3为例，UPF需重选，但SMF不需重选。
S901，同S401；
S903，SMF1判断UE上某PDU会话需重选UPF。为便于描述，此处以PDU Session1为例。
具体实现中：该步骤触发原因可能为UE位置信息，UPF负载信息，SMF1负载信息触发，也可能由其他信息触发，本发明对此不作限定。
具体实现中，SMF1根据PDU Session1的信息确定对应的PDU Session和PDU Session1会话的会话及业务连续性模式为SSC mode3。
具体实现中，SMF1确定需重选UPF的方法可以采用图1中所述的方法来确定。
在本实施例中，假设当前UPF由于过载或故障导致其无法为UE提供服务，而目标接 入区域仍在SMF1的服务范围内，则SMF1可以继续为UE提供服务。因此，SMF1确定需重选UPF。
S905-S907，同S805-S807。
S909，由于该PDU会话为SSC mode3，SMF还将向UE发起会话重定向请求，并在该消息中携带会话重建指示，该消息在传递过程中将由AMF进行转发。其中，会话重建指示用于通知UE发起新的PDU会话建立请求。
具体实现中，该消息可与消息S905合并发送，在这里不作限制。
S911-S919，同S811-S819。
S921，同S527。
在本实施例提供的选择会话管理功能实体的方法中，由于SMF1可以感知会话管理相关信息，因此由SMF来确定的SMF要比现有技术中AMF选择的SMF更加合理。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，上述实现移动性管理功能实体或会话管理功能实体的设备(或：装置)为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对移动性管理功能实体或会话管理功能实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图10示出了上述实施例中所涉及的一种实现选择会话管理功能实体的装置可能的结构示意图，该装置1000包括：收发模块1001，处理模块1003和确定模块1005。
该收发模块，用于接收位置变更通知消息，发送会话管理消息给第一会话管理功能实体，接收来自所述第一会话管理功能实体的用户设备UE的第一会话的信息和重选指示，所述重选指示用于指示重选会话管理功能实体；
该处理模块，用于根据该重选指示保存所述第一会话的信息与所述第一会话管理功能实体的对应关系；
该收发模块，还用于接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话的信息；
该确定模块，用于确定不同于所述第一会话管理功能实体的第二会话管理功能实体；其中，所述第一会话管理功能实体是通过查询自身保存的所述对应关系确定的所述第一会话的信息对应的会话管理功能实体；
该收发模块，还用于发送会话管理请求给所述第二会话管理功能实体。
在一种可能的实现方式中，所述第一会话的信息包括所述第一会话的标识；或，所述第一会话的信息包括所述UE的标识和所述第一会话的标识。。
在另一种可能的实现方式中，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
在另一种可能的实现方式中，该收发模块，还用于发送重建会话指示给所述UE，以通知所述UE建立第二会话。
其中，该装置可以为通信网络中的移动性管理功能实体，也可以为AMF，也可以为通信网络中的其他实体，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图11示出了上述实施例中所涉及的一种实现选择会话管理功能实体的装置可能的结构示意图，该装置1100包括：收发模块1101，处理模块1103和确定模块1105。
该收发模块，用于接收位置变更通知消息，发送会话管理消息给第一会话管理功能实体；接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体重选结果，所述会话管理功能实体重选结果包括第二会话管理功能实体的信息；
该处理模块，用于保存所述第一会话的信息与第二会话管理功能实体的对应关系；
该收发模块，还用于接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；
该确定模块，用于查询所述对应关系确定所述第一会话的信息对应的第二会话管理功能实体；
该述收发模块，还用于发送会话管理请求给所述第二会话管理功能实体。
在一种可能的实现方式中，所述第一会话的信息包括所述第一会话的标识；或，所述第一会话的信息包括所述UE的标识和所述第一会话的标识。。
在另一种可能的实现方式中，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
在另一种可能的实现方式中，该收发模块还用于发送重建会话指示给所述UE，以通知所述UE建立第二会话。
图12示出了上述实施例中所涉及的一种实现选择会话管理功能实体的装置可能的结构示意图，该装置1200包括：收发模块1201，处理模块1203和确定模块1205。
该收发模块，用于接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体选择结果，所述会话管理功能实体选择结果包括第一会话管理功能实体的信息；或：收发模块，用于接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和指示信息；
该处理模块，用于保存所述第一会话的信息与第一会话管理功能实体的对应关系；该所述收发模块，还用于接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；该确定模块，用于查询所述对应关系确定所述第一会话的信息对应的所述第一会话管理功能实体；该收发模块，还用于发送会话管理请求给所述第一会话管理功能实体。
在一种可能的实现方式中，所述第一会话的信息包括所述第一会话的标识；或，所述第一会话的信息包括所述UE的标识和所述第一会话的标识。
在另一种可能的实现方式中，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
在另一种可能的实现方式中，该收发模块还用于发送重建会话指示给所述UE，以通知所述UE建立第二会话。其中，该装置可以为通信网络中的移动性管理功能实体，也可以为AMF，也可以为通信网络中的其他实体，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该实现选择会话管理功能实体的装置以对应各个功能划分各个功能模块的形式来呈现，或者，该实现选择会话管理功能实体的装置以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该实现选择会话管理功能实体的装置1000，1100可以采用图3所示的形式。比如，图10中的收发模块1001，处理模块1003和确定模块1005可以通过图3的处理器31(和/或处理器38)和存储器33来实现，具体的，收发模块1001，处理模块1003和确定模块1005可以通过由处理器31(和/或处理器38)来调用存储器33中存储的应用程序代码来执行，本发明实施例对此不作任何限制。图11中的收发模块1101，处理模块1103和确定模块1105可以通过图3的处理器31(和/或处理器38)和存储器33来实现，具体的，收发模块1101，处理模块1103和确定模块1105可以通过由处理器31(和/或处理器38)来调用存储器33中存储的应用程序代码来执行，本发明实施例对此不作任何限制。图12中的收发模块1201，处理模块1203和确定模块1205可以通过图3的处理器31(和/或处理器38)和存储器33来实现，具体的，可以通过由处理器31(和/或处理器38)来调用存储器33中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
本发明实施例还提供了一种计算机存储介质，用于储存为上述图4或图5所示的实现选择会话管理功能实体的装置所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本发明实施例还提供了另一种计算机存储介质，用于储存为上述图6或图7所示的实现选择会话管理功能实体的装置所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本发明实施例还提供了另一种计算机存储介质，用于储存为上述图8或图9所示的实现选择会话管理功能实体的装置所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本发明实施例还提供了一种计算机程序产品，用于储存为移动性管理功能实体，或者AMF所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本申请实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”，“第三”等并不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”或“具有”及其任何变形，意图在于覆盖不排他的方案，例如，包括了一系列步 骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意结合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数据用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如：软盘、硬盘、磁带)、光介质(例如：DVD)、或者半导体介质(例如：固态硬盘Solid State Disk(SSD))等。
综上，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (24)

  1. 一种选择会话管理功能实体的方法，其特征在于，包括：
    接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和重选指示，所述重选指示用于指示重选会话管理功能实体；
    根据该重选指示保存所述第一会话的信息与所述第一会话管理功能实体的对应关系；
    接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话的信息；
    确定不同于所述第一会话管理功能实体的第二会话管理功能实体，其中，所述第一会话管理功能实体是通过查询自身保存的所述对应关系确定的所述第一会话的信息对应的会话管理功能实体；
    发送会话管理请求给所述第二会话管理功能实体。
  2. 如权利要求1所述的方法，其特征在于，所述第一会话的信息包括所述第一会话的标识；或，
    所述第一会话的信息包括所述UE的标识和所述第一会话的标识。
  3. 如权利要求1至2所述的方法，其特征在于，所保存的对应关系中还可包含重选指示，所述重选指示用于指示重选会话管理功能实体。
  4. 如权利要求1至3所述的方法，其特征在于，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
  5. 如权利要求1至4任一所述的方法，其特征在于，所述接收会话建立请求消息之前，还包括：
    发送重建会话指示给所述UE，以通知所述UE建立第二会话。
  6. 如权利要求1至5任一所述的方法，其特征在于，所述接收位置变更通知消息之前，还包括：
    建立所述第一会话；其中，第一会话管理功能实体是为所述第一会话服务的会话管理功能实体。
  7. 一种选择会话管理功能实体的方法，其特征在于，包括：
    接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体重选结果，所述会话管理功能实体重选结果包括第二会话管理功能实体的信息；
    保存所述第一会话的信息与第二会话管理功能实体的对应关系；
    接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话的信息；查询所述对应关系确定所述第一会话的信息对应的第二会话管理功能实体；
    发送会话管理请求给所述第二会话管理功能实体。
  8. 如权利要求7所述的方法，其特征在于，所述第一会话的信息包括所述第一会话的标识；或，
    所述第一会话的信息包括所述UE的标识和所述第一会话的标识。
  9. 如权利要求7至8所述的方法，其特征在于，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
  10. 如权利要求7至9任一所述的方法，其特征在于，所述接收会话建立请求消息之前，还包括：
    发送重建会话指示给所述UE，以通知所述UE建立第二会话。
  11. 如权利要求7至10任一所述的方法，其特征在于，所述接收位置变更通知消息之前，还包括：
    建立所述第一会话；其中，第一会话管理功能实体是为所述第一会话服务的会话管理功能实体。
  12. 一种选择会话管理功能实体的装置，其特征在于，包括：
    收发模块，用于接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和重选指示，所述重选指示用于指示重选会话管理功能实体；
    处理模块，用于根据该重选指示保存所述第一会话的信息与所述第一会话管理功能实体的对应关系；
    所述收发模块，还用于接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话的信息；
    确定模块，用于确定不同于所述第一会话管理功能实体的第二会话管理功能实体；其中，所述第一会话管理功能实体是通过查询自身保存的所述对应关系确定的所述第一会话的信息对应的会话管理功能实体；
    所述收发模块，还用于发送会话管理请求给所述第二会话管理功能实体。
  13. 如权利要求12所述的装置，其特征在于，所述第一会话的信息包括所述第一会话的标识；或，
    所述第一会话的信息包括所述UE的标识和所述第一会话的标识。
  14. 如权利要求12或13所述的方法，其特征在于，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
  15. 如权利要求12至14任一所述的方法，其特征在于，所述收发模块，还用于发送重建会话指示给所述UE，以通知所述UE建立第二会话。
  16. 一种选择会话管理功能实体的装置，其特征在于，包括：
    收发模块，用于接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体重选结果，所述会话管理功能实体重选结果包括第二会话管理功能实体的信息；
    处理模块，用于保存所述第一会话的信息与第二会话管理功能实体的对应关系；
    所述收发模块，还用于接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；
    确定模块，用于查询所述对应关系确定所述第一会话的信息对应的第二会话管理功能实体；
    所述收发模块，还用于发送会话管理请求给所述第二会话管理功能实体。
  17. 如权利要求16所述的装置，其特征在于，所述第一会话的信息包括所述第一会话的标识；或，
    所述第一会话的信息包括所述UE的标识和所述第一会话的标识。
  18. 如权利要求16或17所述的装置，其特征在于，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
  19. 如权利要求17至18任一所述的装置，其特征在于，所述收发模块，还用于发送重建会话指示给所述UE，以通知所述UE建立第二会话。
  20. 一种选择会话管理功能实体的方法，其特征在于，包括：
    接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体选择结果，所述会话管理功能实体选择结果包括第一会话管理功能实体的信息；或：接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和指示信息；
    保存所述第一会话的信息与第一会话管理功能实体的对应关系；
    接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；查询所述对应关系确定所述第一会话的信息对应的所述第一会话管理功能实体；
    发送会话管理请求给所述第一会话管理功能实体。
  21. 如权利要求20所述的方法，其特征在于，所述第一会话的信息包括所述第一会话的标识；或，所述第一会话的信息包括所述UE的标识和所述第一会话的标识。
  22. 如权利要求20至21所述的方法，其特征在于，若接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和指示信息，则该对应关系中还包括指示信息。
  23. 如权利要求20至22所述的方法，其特征在于，所述会话建立请求消息还携带所述UE待创建的第二会话的标识。
  24. 一种选择会话管理功能实体的装置，其特征在于，包括：
    收发模块，用于接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和会话管理功能实体选择结果，所述会话管理功能实体选择结果包括第一会话管理功能实体的信息；或：收发模块，用于接收来自第一会话管理功能实体的用户设备UE的第一会话的信息和指示信息；
    处理模块，用于保存所述第一会话的信息与第一会话管理功能实体的对应关系；
    所述收发模块，还用于接收会话建立请求消息，所述会话建立请求消息中携带所述第一会话信息；
    确定模块，用于查询所述对应关系确定所述第一会话的信息对应的所述第一会话管理功能实体；
    所述收发模块，还用于发送会话管理请求给所述第一会话管理功能实体。
PCT/CN2018/075472 2017-02-21 2018-02-06 一种选择会话管理功能实体的方法、装置和系统 WO2018153253A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
EP20178336.2A EP3796617B1 (en) 2017-02-21 2018-02-06 Session management function entity selection method, apparatus, and system
EP18757355.5A EP3471377B1 (en) 2017-02-21 2018-02-06 Method, apparatus and system for selecting session management functional entity
KR1020187036850A KR102138002B1 (ko) 2017-02-21 2018-02-06 세션 관리 기능 엔티티 선택 방법, 장치, 및 시스템
BR112019001845-0A BR112019001845A2 (pt) 2017-02-21 2018-02-06 sistema, aparelho e método de seleção de entidade de função de gerenciamento de sessão
JP2019518349A JP6701446B2 (ja) 2017-02-21 2018-02-06 セッション管理機能エンティティ選択方法、機器、及びシステム
US16/192,713 US10743218B2 (en) 2017-02-21 2018-11-15 Session management function entity selection method, apparatus, and system
US16/874,326 US11882485B2 (en) 2017-02-21 2020-05-14 Session management function entity selection method, apparatus, and system
US18/522,959 US20240098578A1 (en) 2017-02-21 2023-11-29 Session Management Function Entity Selection Method, Apparatus, and System

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710092451.6 2017-02-21
CN201710092451 2017-02-21
CN201710132027.XA CN108462735B (zh) 2017-02-21 2017-03-07 一种选择会话管理功能实体的方法和装置
CN201710132027.X 2017-03-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/192,713 Continuation US10743218B2 (en) 2017-02-21 2018-11-15 Session management function entity selection method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2018153253A1 true WO2018153253A1 (zh) 2018-08-30

Family

ID=63220211

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/075472 WO2018153253A1 (zh) 2017-02-21 2018-02-06 一种选择会话管理功能实体的方法、装置和系统

Country Status (7)

Country Link
US (3) US10743218B2 (zh)
EP (2) EP3796617B1 (zh)
JP (2) JP6701446B2 (zh)
KR (1) KR102138002B1 (zh)
CN (2) CN112492573A (zh)
BR (1) BR112019001845A2 (zh)
WO (1) WO2018153253A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167088A (zh) * 2019-05-29 2019-08-23 中国联合网络通信集团有限公司 一种会话的管理方法及装置
CN111132121A (zh) * 2018-10-30 2020-05-08 中国电信股份有限公司 信息处理方法和网络仓库功能nrf网元
TWI733216B (zh) * 2018-10-16 2021-07-11 聯發科技股份有限公司 無效協定資料單元會話之處理方法及其使用者設備

Families Citing this family (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109673174B (zh) * 2016-07-01 2021-08-10 Idac控股公司 以逐个会话为基础支持会话连续性的方法
KR102247424B1 (ko) * 2017-03-31 2021-05-04 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Nr 및 5gc에서의 애플리케이션 토폴로지 인식형 사용자 평면 선택
KR102293669B1 (ko) * 2017-05-08 2021-08-25 삼성전자 주식회사 5g 셀룰러망의 세션 연속성 지원 방안
CN110612776B (zh) * 2017-05-09 2021-06-04 华为技术有限公司 一种数据处理方法及终端设备、网络设备
CN109041136B (zh) * 2017-06-12 2020-07-03 电信科学技术研究院 一种插入smf的方法及amf实体
CN109429362B (zh) * 2017-06-20 2022-02-11 华为技术有限公司 会话处理方法及装置
US10797894B2 (en) * 2017-12-28 2020-10-06 Ofinno, Llc Service type and device type-based policy and charging control
CN110120988B (zh) 2018-02-07 2021-03-30 华为技术有限公司 地址管理方法、设备及系统
CN110831253B (zh) * 2018-08-08 2022-01-14 华为技术有限公司 连接重建方法、设备及系统
US11224093B2 (en) * 2018-08-13 2022-01-11 Ofinno, Llc Network initiated UPF sessions transfer
CN110830543B (zh) 2018-08-13 2021-10-19 华为技术有限公司 通信方法和通信设备
CN110876154B (zh) * 2018-09-04 2023-04-25 中兴通讯股份有限公司 实现nf就近选择的方法、设备和存储介质
WO2020060007A1 (ko) * 2018-09-17 2020-03-26 엘지전자 주식회사 5g 이동통신에서 pdu 세션을 핸들링하는 방법 및 무선 기기
CN112690039B (zh) * 2018-09-21 2023-11-03 株式会社Ntt都科摩 网络节点
CN110536330B (zh) * 2018-09-27 2023-06-23 中兴通讯股份有限公司 一种ue迁移方法、装置、系统及存储介质
CN110958718B (zh) * 2018-09-27 2023-09-26 中兴通讯股份有限公司 一种pdu会话重建方法、装置、系统及存储介质
CN111083718B (zh) * 2018-10-22 2023-07-21 中国移动通信有限公司研究院 一种会话管理方法、网络功能及网络系统
CN111132274B (zh) * 2018-11-01 2021-06-11 大唐移动通信设备有限公司 会话管理功能设备地址的获取、发送方法及装置
WO2020087546A1 (zh) * 2018-11-02 2020-05-07 Oppo广东移动通信有限公司 一种网络信息传输方法、获取方法、网络设备及终端设备
JP2020088472A (ja) * 2018-11-19 2020-06-04 シャープ株式会社 ユーザ装置
CN111225401B (zh) 2018-11-23 2022-12-20 中兴通讯股份有限公司 一种实现容灾的方法及相关设备
CN111327529A (zh) * 2018-12-13 2020-06-23 中国电信股份有限公司 业务转发方法和系统
CN113556410B (zh) * 2018-12-28 2024-07-09 华为技术有限公司 一种域名服务器的分配方法和装置
CN111757312A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种会话的处理方法及装置
WO2020200297A1 (zh) 2019-04-02 2020-10-08 华为技术有限公司 选择会话管理网元的方法和装置
CN111901899B (zh) * 2019-05-06 2022-09-16 华为技术有限公司 一种通信方法及装置
CN110662165B (zh) * 2019-10-09 2020-12-15 广州爱浦路网络技术有限公司 一种基于节点编号选择用户面功能upf的方法
CN114731557B (zh) 2019-11-29 2024-07-30 华为技术有限公司 报文传输方法、通信装置和通信系统
CN111107666B (zh) * 2019-12-30 2022-02-18 联想(北京)有限公司 一种基于pdu会话的网元选取方法、设备及存储介质
CN111556539B (zh) * 2020-05-13 2024-05-17 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
CN112637896B (zh) * 2020-12-10 2023-04-07 中国联合网络通信集团有限公司 最大聚合速率的分配方法、会话管理功能实体及终端
CN114650575B (zh) * 2020-12-18 2024-06-21 维沃移动通信有限公司 Pdu会话选择方法、装置、网络功能及存储介质
CN112929933B (zh) * 2021-02-08 2022-08-02 中国联合网络通信集团有限公司 Amf实体重定向方法和系统、管理节点、终端
CN113316269B (zh) * 2021-04-28 2022-07-19 武汉虹旭信息技术有限责任公司 会话管理方法及装置
CN113260010B (zh) * 2021-07-06 2021-11-09 中兴通讯股份有限公司 Smf发现方法、装置、电子设备和介质
EP4125293B1 (en) 2021-07-29 2024-02-28 Ntt Docomo, Inc. Communication network arrangement
WO2023098718A1 (en) * 2021-12-03 2023-06-08 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for context resumption
CN114158079B (zh) * 2021-12-21 2023-04-18 中国联合网络通信集团有限公司 通信方法和装置、电子设备、计算机可读介质
CN114615132A (zh) * 2022-02-25 2022-06-10 亚信科技（中国）有限公司 一种分流upf的故障处理方法、装置、设备和存储介质
CN116709337A (zh) * 2022-02-28 2023-09-05 华为技术有限公司 通信方法与装置
CN115567536B (zh) * 2022-09-22 2024-04-16 中国联合网络通信集团有限公司 一种算力网络调度方法、装置、电子设备及存储介质
CN118301683A (zh) * 2023-01-04 2024-07-05 中国移动通信有限公司研究院 会话更新方法、装置、网络功能及存储介质
WO2024156135A1 (en) * 2023-03-23 2024-08-02 Zte Corporation Systems and methods for session management function (smf) re-allocation

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH02166674A (ja) * 1988-12-20 1990-06-27 Nec Corp 磁気テープのブロック順序番号チェック方式
JPH02171086A (ja) * 1988-12-23 1990-07-02 Matsushita Electric Ind Co Ltd 同期信号分離器
KR100395487B1 (ko) * 2001-09-14 2003-08-25 한국전자통신연구원 이동 스위칭 센터 경유 기지국 제어기간 링크 설정을 통한패킷 데이터 서비스 노드 간 고속 하드 핸드오프 수행 방법
US7979557B2 (en) * 2008-04-11 2011-07-12 Mobitv, Inc. Fast setup response prediction
US9282046B1 (en) * 2012-11-15 2016-03-08 Qlogic, Corporation Smoothing FIFO and methods thereof
CN105792368B (zh) * 2016-02-26 2019-08-23 上海华为技术有限公司 一种控制信息处理的方法、相关设备以及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects ; '' Study on Architecture for Next Generation System (Release 14)", 3GPP TR 23.799 V1.1.0, 31 October 2016 (2016-10-31), pages 1 - 501, XP055562606 *
CATT: "Network Slicing Architecture and Slice Selection Mechanism", SA WG2 MEETING #115, 23 May 2016 (2016-05-23), Nanjing, P. R. China, pages 2 - 162652, XP051109402 *
HUAWEI ET AL.: "An Alternative Solution and Interim Agreement on a Network-based SSC Mode Determination", SA WG2 MEETING #S2-118, 8 November 2016 (2016-11-08), Reno, Nevada, USA, XP051185265 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI733216B (zh) * 2018-10-16 2021-07-11 聯發科技股份有限公司 無效協定資料單元會話之處理方法及其使用者設備
US11212720B2 (en) 2018-10-16 2021-12-28 Mediatek Inc. 5GSM handling on invalid PDU session
US11582656B2 (en) 2018-10-16 2023-02-14 Mediatek Inc. 5GSM handling on invalid PDU session
CN111132121A (zh) * 2018-10-30 2020-05-08 中国电信股份有限公司 信息处理方法和网络仓库功能nrf网元
CN111132121B (zh) * 2018-10-30 2022-03-22 中国电信股份有限公司 信息处理方法和网络仓库功能nrf网元
CN110167088A (zh) * 2019-05-29 2019-08-23 中国联合网络通信集团有限公司 一种会话的管理方法及装置

Also Published As

Publication number Publication date
JP6701446B2 (ja) 2020-05-27
CN112492573A (zh) 2021-03-12
EP3796617B1 (en) 2023-06-21
US20190090164A1 (en) 2019-03-21
KR102138002B1 (ko) 2020-07-27
US11882485B2 (en) 2024-01-23
EP3471377B1 (en) 2020-08-26
KR20190009788A (ko) 2019-01-29
BR112019001845A2 (pt) 2019-05-07
US10743218B2 (en) 2020-08-11
US20240098578A1 (en) 2024-03-21
JP2019518398A (ja) 2019-06-27
JP6890698B2 (ja) 2021-06-18
EP3471377A1 (en) 2019-04-17
CN108462735A (zh) 2018-08-28
EP3796617A1 (en) 2021-03-24
US20200275321A1 (en) 2020-08-27
EP3471377A4 (en) 2019-09-04
CN108462735B (zh) 2020-11-17
JP2020145703A (ja) 2020-09-10

Similar Documents

Publication Publication Date Title
WO2018153253A1 (zh) 一种选择会话管理功能实体的方法、装置和系统
US11115876B2 (en) Service continuity implementation method, device, and service continuity implementation system
US11026080B2 (en) Policy control function determining method, apparatus, and system
US11432366B2 (en) Session management method, device, and system
US12004264B2 (en) Session management method, device, and system
WO2019158010A1 (zh) 资源管理的方法、设备及系统
WO2019137553A1 (zh) 一种配置ue的策略的方法、装置和系统
EP3930378B1 (en) Handover from a non-public-network
WO2018214597A1 (zh) 接入网类型选择方法、设备及系统
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2018000202A1 (zh) 一种负载迁移方法、装置及系统
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及系统
WO2017076126A1 (zh) 一种会话切换的方法、设备及系统
WO2020199620A1 (zh) 一种会话的处理方法及装置
WO2019137521A1 (zh) 会话管理方法、设备及系统
WO2018191867A1 (zh) 终端监控信息的同步方法、设备及系统
WO2020011173A1 (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: 18757355

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20187036850

Country of ref document: KR

Kind code of ref document: A

Ref document number: 2019518349

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018757355

Country of ref document: EP

Effective date: 20190111

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019001845

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112019001845

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190129

NENP Non-entry into the national phase

Ref country code: DE