WO2018202008A1 - 一种会话管理方法、网络设备和通信*** - Google Patents

一种会话管理方法、网络设备和通信*** Download PDF

Info

Publication number
WO2018202008A1
WO2018202008A1 PCT/CN2018/085099 CN2018085099W WO2018202008A1 WO 2018202008 A1 WO2018202008 A1 WO 2018202008A1 CN 2018085099 W CN2018085099 W CN 2018085099W WO 2018202008 A1 WO2018202008 A1 WO 2018202008A1
Authority
WO
WIPO (PCT)
Prior art keywords
management entity
session management
pdu session
information
local
Prior art date
Application number
PCT/CN2018/085099
Other languages
English (en)
French (fr)
Inventor
朱奋勤
吴问付
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201810150678.6A external-priority patent/CN108811011B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18793911.1A priority Critical patent/EP3606275B1/en
Priority to EP22164618.5A priority patent/EP4090078A3/en
Publication of WO2018202008A1 publication Critical patent/WO2018202008A1/zh
Priority to US16/664,481 priority patent/US11706704B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the present invention relates to the field of communications, and in particular, to a session management method, a network device, and a communication system.
  • the Session Management Function is responsible for session management, including the establishment, modification, and release of a PDU (Protocol Data Unit, PDU) session.
  • the User Plane Function is responsible for forwarding user data.
  • the technical problem to be solved by the embodiments of the present invention is to provide a session management method, a network device, and a communication system, so as to implement user plane entities managing different locations.
  • the present application provides a session management method, including selecting, by a network device, location information of a User Equipment (UE), and a PDU (Protocol Data Unit, PDU for short) session requirement information.
  • a first intermediate session management entity the network device sends the location information of the UE and the PDU session requirement information to the first intermediate session management entity, where the PDU session requirement information is used to select a user plane entity, and the first intermediate session management entity is only responsible for management designation.
  • a network element in the range (for example, an access network device or a user plane entity).
  • the PDU session requirement information indicates related parameters of the PDU session determined by the core network.
  • the network device is a device in the core network, and the network device may be an access management entity or a session management entity.
  • the access management entity is used to perform access management on the UE, and the session management entity is used to manage the session established by the UE.
  • the network device selects the intermediate session management entity according to the location information of the UE and the PDU session requirement information, so that the intermediate session management entity close to the UE can provide services for the PDU session, thereby reducing the delay of data transmission.
  • the intermediate session management entity selects the user plane entity according to the location information of the UE and the PDU requirement information, and the intermediate session management entity only manages the user plane entity in the specified range, and does not need to manage the user plane entity of the entire PDU session, thereby reducing management complexity.
  • the PDU session requirement information includes a PDU session type and/or a SSC (Session and Service Continuity, SSC) mode.
  • SSC Session and Service Continuity, SSC
  • the selecting, by the network device, the first intermediate session management entity for the PDU session according to the location information of the UE and the PDU session requirement includes: the network device selects the PDU session requirement information and the jurisdiction includes the UE.
  • the intermediate session management entity of the serving base station indicated by the location information serves as the first intermediate session management entity.
  • the PDU session requirement includes a PDU session type and/or an SSC.
  • the location information of the UE may be an identifier of the serving base station of the UE or an identifier of the serving cell of the UE or a tracking area identifier of the UE, and the network device may determine, according to the location information of the UE, whether the serving base station indicated by the location information of the UE can be in the first intermediate session.
  • the management entity is connected.
  • Each intermediate session management entity has a certain jurisdiction, and the size of the jurisdiction is not limited in this application. For example, the jurisdiction of the intermediate session management entity is a province, a city, or a data center.
  • the PDU session requirement information includes a PDU session type and/or an SSC, if the network device determines that the service base station that does not exist and satisfies the PDU session requirement and the location information including the location information indication of the UE An intermediate session management entity, the network device respectively selecting a second intermediate session management entity that satisfies the PDU session requirement information, and selecting a third intermediate session management entity, a second intermediate session management entity, and a serving base station whose jurisdiction includes the location information indication of the UE
  • the third intermediate session management entity simultaneously serves the PDU session. In this way, the same PDU session can be served by multiple intermediate session management entities, and each intermediate session management entity is only responsible for managing the network elements in the specified range, which reduces the management load and complexity of the intermediate session management entity.
  • the PDU session requirement information includes a local DNN and a data transmission mode
  • the local DNN represents a name of a local DN (Data Network, Data Network, DN for short).
  • the data transmission mode indicates the transmission mode of the data packet on the user plane, and the data transmission mode is the Mutilhoming mode or the ULCL (Uplink Classifier) mode.
  • the selecting, by the network device, the first intermediate session management entity for the PDU session according to the location information of the UE and the PDU session requirement information includes: the network device selects the location information indication that includes the UE while satisfying the jurisdiction The serving base station and the local DN indicated by the local DNN, and the intermediate session management entity supporting the data transmission mode included in the PDU session requirement information as the first intermediate session management entity.
  • the network device determines that there is no local DN indicated by the local DNN included in the serving base station and the PDU session requirement information included in the jurisdiction information indicating the location information of the UE, and the PDU session requirement information is supported.
  • An intermediate session management entity including a data transmission mode, selecting a second intermediate session management entity of the serving base station whose jurisdiction includes the location information indication of the UE, and selecting a local DN indicating that the jurisdiction includes the local DNN indication included in the PDU session requirement information
  • the network device may be an access management entity or a session management entity, and the second intermediate session management entity and the third intermediate session management entity simultaneously provide services for the PDU session.
  • the data transmission mode is a Mutilhoming mode
  • the network device sends the uplink offload policy and the uplink routing policy to the first intermediate session management entity, where the uplink offload policy is used to control the UE anchoring
  • the branch point BP is offloaded according to the source address of the data packet sent by the UE, and the uplink routing policy is used to control the UE to use the IP address anchored at the anchor user plane entity or the local IP address anchored at the local anchor user plane entity as The source address of the data packet; or the network device sends the uplink routing policy corresponding to the IP address of the anchor user plane entity and the IP address anchored to the anchor user plane entity to the first intermediate session management entity; anchored in The IP address of the anchor user plane entity is used to enable the first intermediate session management entity to generate an uplink offload policy, and the uplink routing policy corresponding to the IP address of the anchor user plane entity is used to enable the first intermediate session management entity to generate an uplink route.
  • the uplink offloading policy is used to control the BP to perform traffic off according to the source address of the data packet sent by the UE, and the uplink routing policy is used to indicate the UE.
  • the data transmission mode is a ULCL mode
  • the network device sends an uplink forwarding policy to the first intermediate session management entity, and the uplink forwarding policy is used to control the UE-anchored ULCL according to the UE.
  • the quintuple and/or application ID of the packet is forwarded.
  • the UE in a handover procedure of the UE, the UE is handed over to the target base station by the current serving base station, and before the handover occurs, the UE has established a PDU session, and the network device saves the PDU session.
  • PDU session requirement information the network device may learn that the UE is handed over to the target base station by the current serving base station according to the path switching message from the target base station, and the network device determines that the target base station is not within the jurisdiction of the current first intermediate session management entity, the network The device selects a target intermediate session management entity, and the target intermediate session management entity is an intermediate session management entity that simultaneously satisfies the target base station and PDU session requirement information that the UE switches to.
  • the network device selects a second intermediate session management entity including the target base station and a third intermediate session management that satisfies the PDU session requirement information when there is no intermediate session management that satisfies the jurisdiction including the target base station and the PDU session requirement information.
  • the entity, the second intermediate session management entity and the third intermediate session management entity are the target intermediate session management entities.
  • the network device is a session management entity
  • the session management entity further includes: session management before selecting the first intermediate session management entity for the PDU session according to the location information of the UE and the PDU session requirement information.
  • the entity determines PDU session requirement information, wherein the session management entity may determine the PDU session requirement information according to the PDU session subscription information; or the session management entity may sign the PDU session according to one or more of the PDU session policy information and the PDU session expectation information.
  • the information determines PDU session demand information.
  • the session management entity selects an anchor user plane entity within the jurisdiction of the session management entity according to the PDU session requirement information.
  • the jurisdiction of the session management entity may be a province, a city, a data center, or other scope.
  • the session management entity determines, according to the location information of the UE, the serving base station indicated by the location information of the UE, and determines that the serving base station indicated by the location information of the UE is not connected to the selected anchor user plane entity, and the session management function is based on the location information and the PDU of the UE.
  • the session requirement information selects the first intermediate session management entity.
  • the PDU session policy information indicates a related policy of the PDU session, for example, QoS (Quality of Service, QoS for short).
  • the PDU session expectation information indicates session related parameters requested by the UE, for example, the PDU session expectation information includes one or more of a local DNN, a PDU session type, and an SSC mode.
  • the network device is a session management entity
  • the session management entity further includes: session management before selecting the first intermediate session management entity for the PDU session according to the location information of the UE and the PDU session requirement information.
  • the entity determines the PDU session requirement information according to the PDU session subscription information; or the session management entity determines the PDU session requirement information according to one or more of the PDU session expectation information and the PDU session policy information, and the PDU session subscription information.
  • the PDU session policy information can come from the policy control entity of the core network.
  • the PDU session expectation information indicates related parameters of the PDU session requested by the UE, and the PDU session expectation information includes one or more of a PDU session type, an SSC mode, and a local DNN.
  • the session management entity determines that the local DN indicated by the local DNN included in the PDU session requirement information is not within the jurisdiction of the session management entity.
  • the network device is an access management entity, and before the network device selects the first intermediate session management entity for the PDU session according to the location information of the UE and the PDU session requirement information, the network device further includes: The management entity selects a session management entity, wherein the access management entity can select a session management entity based on local DNNs from the UE, network slice information, and UE subscription information.
  • the access management entity determines that the serving base station indicated by the location information of the UE is not located within the jurisdiction of the session management entity, and the access management entity according to one or more of the local DNN, the network slice information, and the UE subscription information from the UE and the UE
  • the location information selects a fourth intermediate session management entity, the access management entity receives PDU session requirement information and a reselection indication message from the session management entity, and the reselection indication message is used to instruct the access management entity to reselect a different and fourth intermediate The first intermediate session management entity of the session management entity.
  • the network device is an access management entity, and before the network device selects the first intermediate session management entity for the PDU session according to the location information of the UE and the PDU session requirement information, the network device further includes: The management entity selects a session management entity, wherein the access management entity may select the session management entity according to one or more of local DNN and network slice information carried in the PDU session establishment request from the UE.
  • the access management entity determines that the serving base station indicated by the location information of the UE is not located within the jurisdiction of the session management entity, and the access management entity selects the fourth intermediate session management entity, receives the PDU session requirement information from the session management entity, and determines the fourth intermediate The session management entity does not satisfy the PDU session requirement information.
  • the network device is an access management entity
  • the PDU session request information network device selects the first intermediate session management entity for the PDU session according to the location information of the UE and the PDU session requirement information.
  • the method includes: when the demand of the PDU session changes, the access management entity receives new PDU session requirement information and a reselection indication message from the session management entity, where the reselection indication message is used to instruct the access management entity to reselect an intermediate session management entity.
  • the network device is an access management entity
  • the first intermediate session management entity currently provides a service for the PDU session.
  • the access management entity receives the session from the session.
  • the new PDU session requirement information of the management entity the access management entity determines that the first intermediate session management entity does not satisfy the new PDU session requirement information, and selects the target intermediate session management entity according to the location information of the UE and the new PDU session requirement information.
  • the network device is the session management entity session management entity according to the PDU session subscription information; or according to one or more of the PDU session policy information and the PDU session expectation information, and the PDU session.
  • the subscription information determines the PDU session requirement information
  • the session management entity determines that the fourth intermediate session management entity selected by the access management entity does not satisfy the PDU session requirement information, and the session management entity selects the first PDU session according to the location information of the UE and the PDU session requirement information.
  • An intermediate session management entity the session management entity sends the identifier information of the first intermediate session management entity to the access management entity, where the identifier information is used to uniquely represent the identity of the first intermediate session entity, for example, the identifier information of the first intermediate session management entity It can be address information, location information or ID (Identity, ID for short).
  • the application provides a communication system, where the communication system includes a network device and a first intermediate session management entity, where the network device can be an access management entity or a session management entity, and the network device is configured to use location information and PDUs of the UE.
  • the session requirement information selects a first intermediate session management entity for the PDU session.
  • the first intermediate session management entity is configured to receive PDU session requirement information from the network device, and select a user plane entity according to the location information of the UE and the PDU session requirement information. It should be noted that the session management entity and the first intermediate session management entity have a certain jurisdiction, and the jurisdictions of the session management entity and the first intermediate session management entity do not overlap, and the first intermediate session management entity is responsible for managing the network in the jurisdiction.
  • the user plane entity, the size of the jurisdiction of the first intermediate session management entity may be determined by the operator according to requirements, for example, the jurisdiction of the first intermediate session management entity is a province, a city, or a data center, There are no restrictions on the application.
  • the network device selects the intermediate session management entity according to the location information of the UE and the PDU session requirement information, so that the intermediate session management entity close to the UE can serve the PDU session, reducing the delay of data transmission.
  • the intermediate session management entity selects the user plane entity according to the location information of the UE and the PDU requirement information, and the intermediate session management entity only manages the user plane entity in the specified range, and does not need to manage the user plane entity of the entire PDU session, thereby reducing management complexity.
  • the first intermediate session management entity is further configured to receive an uplink offloading policy and an uplink routing policy from the network device, configure the uplink offloading policy to the BP, and configure the uplink routing policy.
  • the uplink offloading policy is used to control the BP to perform traffic off according to the source address of the data packet sent by the UE, and the uplink routing policy is used to control the UE to use the IP address anchored at the anchor user plane entity or anchored locally.
  • the local IP address of the anchor user plane entity as the source address of the data packet; or
  • the first intermediate session management entity is further configured to send an uplink routing policy corresponding to the IP address of the anchor user plane entity and the IP address anchored to the anchor user plane entity to the first intermediate session management entity;
  • the IP address of the anchor user plane entity is used to enable the first intermediate session management entity to generate an uplink offload policy
  • the uplink routing policy corresponding to the IP address of the anchor user plane entity is used to enable the first intermediate session management entity to generate an uplink. Routing policy;
  • the uplink offloading policy is used to control the BP to perform traffic off according to the source address of the data packet sent by the UE, and the uplink routing policy is used to indicate that the UE uses the IP address anchored at the anchor user plane entity or uses the anchor to the local anchor point user.
  • the local IP address of the polygon entity is used as the source address to send data.
  • the data transmission mode is a ULCL mode
  • the first intermediate session management entity is configured to select, according to location information of the UE and PDU session requirement information, within the jurisdiction of the first intermediate session management entity.
  • the user plane entity is specifically: selecting a local anchor user plane entity for the PDU session, and selecting a ULCL for the PDU session.
  • the session management entity also selects an anchor user plane entity for the PDU session, and the anchor user plane entity is used to connect to the DN.
  • the ULCL corresponds to two transmission links: a transmission link between the ULCL to the anchor user plane entity, and a transmission link between the ULCL and the user plane entity, the ULCL based on the quintuple and/or application of the data packet from the UE
  • the identifier is divided.
  • the quintuple indicates the source IP address, the destination IP address, the source port number, the destination port number, and the protocol version.
  • the application identifier indicates the identification information of the application that generates the data packet on the UE.
  • the ULCL performs offloading according to a preset uplink forwarding policy, where the uplink forwarding policy indicates a correspondence between the transport link identifier and the quintuple and/or the identifier.
  • the first intermediate session management entity is further configured to receive an uplink forwarding policy sent by the network device from the network device, and configure the uplink forwarding policy to the ULCL.
  • the PDU session requirement information further includes a PDU session type, and the PDU session type is an IP type, where the first intermediate session management entity is further configured to send a local anchor user plane entity to the session management entity.
  • the first intermediate session management entity is further configured to send a local anchor user plane entity to the session management entity.
  • One or more of the location information and the location information of the local DN, and the local IP address of the UE, the local IP address of the UE indicating the IP address of the anchor assigned by the first intermediate session management entity on the local anchor user plane entity address.
  • the present application provides an apparatus having a function of implementing the behavior of a network device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the apparatus includes: a selecting unit and a transceiver unit.
  • a selecting unit configured to select a first intermediate session management entity for the PDU session according to the location information of the user equipment UE and the protocol data unit PDU session requirement information.
  • a transceiver unit configured to send the location information of the UE and the PDU session requirement information to the first intermediate session management entity, where the location information of the UE and the PDU session requirement information are used to select a user plane entity .
  • the network device includes: a transceiver, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke program code stored in the memory
  • the session management method of any one of the possible implementations of the first aspect to the first aspect is performed.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible terminal devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • the application provides a session management method, including:
  • the network device selects a first intermediate session management entity for the protocol data unit PDU session according to the local network data name DNN;
  • the network device sends the location information of the user equipment UE to the first intermediate session management entity, where the location information of the UE is used to select a user plane entity.
  • the selecting, by the network device, the first intermediate session management entity for the PDU session according to the local DNN includes:
  • the network device selects a first intermediate session management entity according to location information of the local DNN and the UE; wherein, selecting a local data network DN that supports the local DNN indication, and a location information indication that the jurisdiction includes the UE The first intermediate session management entity of the serving base station.
  • the selecting, by the network device, the first intermediate session management entity for the PDU session according to the local DNN includes:
  • the network device selects an intermediate session management entity supporting the local data network DN indicated by the local DNN as the first intermediate session management entity.
  • the network device is a session management entity, and the method further includes:
  • the network device determines the local DNN based on information from the application function.
  • the method further includes:
  • the network device sends the location information of the UE to the first intermediate session management entity, where the location information of the UE is used to indicate that the first intermediate session management entity selects a user plane entity that supports the UE location, An access network interface that supports the user plane entity of the UE location and the UE.
  • the method further includes:
  • the network device sends the local DNN to the first intermediate session management entity; wherein the local DNN is used to instruct the first intermediate session management entity to select a local anchor user plane entity.
  • the user plane entity selected by the first intermediate session management entity supports both the local DNN and the UE location information
  • the first intermediate session management entity selects a user plane entity supporting the local DNN as a local anchor user plane entity according to the local DNN, and according to the The UE location information selects a user plane entity supporting the UE location information for an access network interface connected to the UE, wherein the local anchor user plane entity is configured to interface with the local DN.
  • the network device sends a data transmission mode to the first intermediate session management entity; wherein the data transmission mode is used to instruct the first intermediate session management entity to determine an uplink traffic distribution rule.
  • the network device further sends the remote UE IP address to the first intermediate session management entity; wherein the remote UE IP is used Instructing the first intermediate session management entity to determine an uplink offload rule.
  • the network device further sends application information to the first intermediate session management entity, where the application information is used to indicate The first intermediate session management entity determines an uplink offload rule; the application information is at least one of an application identifier or a five-tuple corresponding to the application.
  • the network device sends an uplink offload rule or an uplink forwarding rule to the first intermediate session management entity, where the uplink offload rule or the uplink forwarding rule is used to indicate the first intermediate session management.
  • the entity configures the user plane entity to implement uplink data offloading.
  • the network device sends routing information between the local anchor point and the local data network DN identified by the local DNN to the first intermediate session management entity, and the routing information is used to determine the user plane.
  • the forwarding path between the entity and the local data network DN is used to determine the user plane.
  • a still further aspect of the present application provides an apparatus, including: a memory and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke program code stored in the memory, and execute Four possible aspects and various possible implementations of the fourth aspect.
  • the present application provides an apparatus having a function of implementing network device behavior in each of the possible implementation methods of the fourth aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the apparatus includes: a selecting unit and a transceiver unit.
  • Yet another aspect of the present application is directed to a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.
  • Yet another aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • FIG. 1a is a network architecture diagram provided by an embodiment of the present invention.
  • Figure 1b is a diagram of a next generation network architecture based on Figure 1a;
  • 2a is another network architecture diagram provided by an embodiment of the present invention.
  • Figure 2b is a diagram of the next generation network architecture based on Figure 2a;
  • FIG. 3 is a schematic flowchart of a session management method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of another session management method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart diagram of another session management method according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart diagram of another session management method according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a device according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart diagram of another session management method according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart diagram of another session management method according to an embodiment of the present invention.
  • FIG. 1a is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • the communication system may be a Global System for Mobile Communication (GSM), a Code Division Multiple Access (CDMA) system, or a Wideband Code Division Multiple Access (WCDMA) system.
  • GSM Global System for Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • WiMAX Worldwide Interoperability for Microwave Access
  • LTE long term evolution
  • 5G communication system such as new radio (NR) system
  • NR new radio
  • the communication system shown in FIG. 1a includes: an access network, an access management entity, a session management entity, and a first intermediate session management entity, and may also include a policy.
  • the form and number of the various network elements in FIG. 1a are for illustrative purposes only and do not constitute a limitation on the embodiments of the present invention.
  • the access management entity separately communicates with the policy control entity, the access network, and the policy control entity, and the session management entity communicates with the policy control entity, the first intermediate session management entity, and the anchor user plane entity respectively, and the access network respectively.
  • the access management entity and the user plane entity communicate with each other, and the first intermediate session management entity communicates with the session management entity and the user plane entity respectively, and the anchor user plane entity and the data network communicate with each other.
  • the access management entity communicates with the session management entity.
  • the access management entity is mainly responsible for access and mobility management, including functions such as authentication, handover, and location update for the user;
  • the session management entity is mainly responsible for session management, including functions of establishing, modifying, and releasing PDU sessions; It is mainly responsible for the management of user measurement, including the generation of mobility-related policies and PDU session-related policies.
  • PDU session-related policies include QoS (Quality of Service, QoS for short) policies, charging policies, etc.
  • the user plane entity is divided into a common user plane entity and an anchor user plane entity, the anchor user plane function is a user plane function connected with the data network; the data network is a destination of the user's PDU session access;
  • An intermediate session management entity is mainly responsible for the management of user plane entities in the jurisdiction, including load sharing of user plane entities, selection of user plane entities, establishment of tunnels on user plane entities, and formulation and configuration of forwarding rules of user plane entities.
  • the session management entity includes the establishment of a user plane tunnel, the configuration of a forwarding rule of the user plane entity, and the like. It should be noted that the first intermediate session management entity may be deployed separately or integrated in the session management entity, which is not limited in this application.
  • the jurisdiction of the first intermediate session management entity may be determined by the operator as needed during deployment.
  • the jurisdiction of the first intermediate session management entity is a province or a city or a tracking area or a data center, which is not implemented in the embodiment of the present invention. limit.
  • FIG. 1b is an architectural diagram of a 5G communication system.
  • the AMF Access Management Function, AMF for short
  • the RAN corresponds to the access network in FIG. 1a
  • the SMF corresponds to FIG. 1a.
  • the session management entity, the Intermediate Session Management Function (ISMF) corresponds to the first intermediate session management entity in Figure 1a
  • the UPF corresponds to the user plane entity in Figure 1a
  • A-UPF Anchor User Plane Function
  • the anchor user plane function referred to as A-UPF, corresponds to the anchor user plane entity in Figure 1a, DN (Data Network, Data Network, DN for short).
  • the RAN and the AMF communicate with each other through the N2 interface.
  • the RAN and the UPF communicate with each other through the N3 interface.
  • the two UPFs communicate with each other through the N9 interface.
  • the UPF and A-UPF in Figure 1b communicate with each other through the N9 interface.
  • the IS4 and the UPF can communicate with each other through the N4 interface, and the SMF and the A-UPF can also communicate with each other through the N4 interface.
  • the A-UPF communicates with the DN through the N6 interface.
  • the SMF and the PCF communicate with each other through the N7 interface.
  • the SMF and the ISMF can communicate with each other through the N16 interface.
  • the SMF and the AMF communicate with each other through the N11 interface.
  • the AMF and the PCF communicate with each other through the N15 interface.
  • FIG. 2a is another structural diagram of a communication system according to an embodiment of the present invention.
  • the structure of the communication system shown in FIG. 2a and the structure of the communication system of FIG. 1a are only different in that: an access management entity and a session management entity. There is no interworking between the access management entity and the intermediate session management entity.
  • the function of each network element in FIG. 2a can be referred to the description in FIG. 1a, and details are not described herein again.
  • Figure 2b is another architecture diagram of the 5G communication system.
  • the correspondence between the network element in Figure 2b and the network element in Figure 2a can be referred to the corresponding relationship of the network elements in Figure 1b and Figure 1a. Narration.
  • the structure of the communication system of FIG. 2b is different from the structure of the communication system of FIG. 1b only in that the AMF and the SMF are not interworking, and the AMF and the ISMF are interworked through the N11 interface.
  • the access network in the present application may also be referred to as a base station device, and is a device deployed in the radio access network to provide wireless communication functions, including but not limited to: a base station (for example, BTS (Base Transceiver Station, BTS) ), Node B (NB), Evolved Node B (eNB or eNodeB), transmission node or transmission reception point (TRP or TP) or next generation Node B (generation node B) in the NR system , gNB), base station or network equipment in future communication networks), relay stations, access points, in-vehicle devices, wearable devices, wireless-fidelity (Wi-Fi) sites, wireless backhaul nodes, small stations , micro stations and so on.
  • BTS Base Transceiver Station
  • NB Node B
  • eNB or eNodeB Evolved Node B
  • TRP or TP transmission reception point
  • generation node B generation node B
  • gNB next generation node B
  • relay stations access points
  • one PDU session may correspond to multiple user plane entities, different user plane entities may be located at different locations, and the session management entity needs to simultaneously manage user plane entities at different locations, which causes a management process. More complicated.
  • an embodiment of the present invention provides a communication system, including: a network device and a first intermediate session management entity.
  • the network device is configured to select a first intermediate session management entity for the PDU session according to the location information of the user equipment UE and the protocol data unit PDU session requirement information.
  • the network device in this embodiment is an access management entity or a session management entity.
  • the first intermediate session management entity is configured to receive PDU session requirement information from the network device, and select a user plane entity according to the location information of the UE and the PDU session requirement information.
  • the PDU session requirement information includes a data transmission mode and a local data network name DNN.
  • the communication system further includes an anchor user plane entity, a local anchor user plane entity (not shown), a serving base station, and a BP (not shown).
  • the serving base station is an access network device, and the data transmission mode is a multi-homing Mutilhoming mode;
  • the first intermediate session management entity is configured to select a user plane entity according to the location information of the UE and the PDU session requirement information in the jurisdiction of the first intermediate session management entity, specifically: selecting a local anchor user plane entity for the PDU session, and The PDU session selects a branch point BP; wherein, the BP is used to offload the data packet sent by the UE, and the local anchor user plane entity is connected with the local data network DN indicated by the local DNN included in the PDU session requirement information, and the location information of the BP and the UE Indicated service base station connection.
  • the first intermediate session management entity is further configured to receive an uplink offload policy and an uplink routing policy from the network device, configure an uplink offload policy to the BP, and configure an uplink routing policy.
  • the uplink offloading policy is used to control the BP to perform traffic off according to the source address of the data packet sent by the UE, and the uplink routing policy is used to control the UE to use the IP address anchored at the anchor user plane entity or anchored locally.
  • the local IP address of the anchor user plane entity as the source address of the data packet; or
  • the first intermediate session management entity is further configured to send an uplink routing policy corresponding to the IP address of the anchor user plane entity and the IP address anchored to the anchor user plane entity to the first intermediate session management entity;
  • the IP address anchored at the anchor user plane entity is used to enable the first intermediate session management entity to generate an uplink offload policy, and the uplink routing policy corresponding to the IP address of the anchor user plane entity is used to make the
  • the first intermediate session management entity generates the uplink routing policy, where the uplink offloading policy is used to control the BP to perform traffic off according to a source address of a data packet sent by the UE, where the uplink routing policy is used to indicate the UE
  • the data is transmitted using the anchored IP address at the anchor user plane entity or using the local IP address anchored at the local anchor user plane entity as the source address.
  • the communication system further includes a ULCL and a local DN (not shown), the data transmission mode is a ULCL mode, and the first intermediate session management entity is used in the first intermediate session.
  • the user plane entity is selected according to the location information of the UE and the PDU session requirement information in the jurisdiction of the management entity, specifically: selecting a local anchor user plane entity for the PDU session, and selecting an uplink classifier ULCL for the PDU session; wherein, ULCL
  • the application identifier and/or a 5-tuple of the data packet sent by the UE are offloaded, and the local anchor user plane entity is connected to the local DN indicated by the local DNN, and the ULCL is connected to the serving base station indicated by the location information of the UE.
  • the first intermediate session management entity is further configured to receive an uplink forwarding policy from the network device, and configure an uplink forwarding policy to the ULCL; wherein the uplink forwarding policy is used to control the ULCL.
  • the split is performed according to one or more of the quintuple and the application identifier.
  • the PDU session requirement information further includes a PDU session type, and the PDU session type is an IP type.
  • the first intermediate session management entity is further configured to send, to the session management entity, one or more of location information of the local anchor user plane entity and location information of the local DN, and a local IP address of the UE.
  • the PDU session requirement information includes one or more of a session and a service continuity SSC mode and a PDU session type.
  • the network device is configured to select, according to the location information of the UE and the protocol data unit PDU session requirement information, the first intermediate session management entity for the PDU session, specifically: selecting and satisfying the PDU session requirement at the same time.
  • the information and the jurisdiction include the intermediate session management entity of the serving base station indicated by the location information of the UE as the first intermediate session management entity.
  • the network device can be an access management entity or a session management entity.
  • the network device is further configured to: if it is determined that there is no intermediate session management entity that satisfies the PDU session requirement and the jurisdiction includes the location information indication of the UE; and selects to satisfy the PDU session.
  • the network device in this embodiment may be an access management entity or a session management entity.
  • the network device is configured to select a first intermediate session management entity for the PDU session according to the location information of the UE and the protocol data unit PDU session requirement information, where the selection jurisdiction includes the UE.
  • the serving base station indicated by the location information and the local DN indicated by the local DNN including the PDU session requirement information, and the intermediate session management entity supporting the data transmission mode are used as the first intermediate session management entity.
  • the network device in this embodiment may be an access management entity or a session management entity.
  • the network device is further configured to: if it is determined that there is no local DN indicated by the serving base station and the local DNN indicated by the location information of the UE, and an intermediate session management entity that supports the data transmission mode; the location of the selection includes the location of the UE.
  • the information indicates the second intermediate session management entity of the serving base station, and the third intermediate session management entity that selects the local DN whose jurisdiction includes the local DNN indication and supports the data transmission mode.
  • the network device in this embodiment may be an access management entity or a session management entity.
  • the communication system further includes an access management entity and a policy management entity, where the network device is a session management entity, and the access management entity is configured to select a session management entity.
  • the network device is further configured to determine PDU session requirement information according to the PDU session subscription information; or determine PDU session requirement information according to one or more of the PDU session policy information and the PDU session expectation information, and the PDU session subscription information; according to the PDU session requirement
  • the information selects an anchor user plane entity for the PDU session; and determines that the anchor user plane entity and the serving base station indicated by the location information of the UE are not connected.
  • the network device acquires PDU session requirement information from the policy management entity.
  • the communication system includes an access management entity, and the network device is a session management entity.
  • the access management entity is used to select a session management entity.
  • the session management entity is further configured to: determine PDU session requirement information according to the PDU session subscription information; or determine PDU session requirement information according to one or more of PDU session policy information and PDU session expectation information, and PDU session subscription information;
  • the jurisdiction of the managed entity does not include the local DN indicated by the local DNN.
  • the communication system further includes an access management entity, where the network device is a session management entity;
  • the access management entity is configured to select a session management entity, and select a fourth intermediate session management entity (not shown in FIG. 2a) when the jurisdiction of the session management entity does not include the serving base station indicated by the location information of the UE.
  • the session management entity is further configured to: determine the PDU session requirement information according to the PDU session subscription information, or one or more of the PDU session policy information and the PDU session expectation information, and determine that the fourth intermediate session management entity is not satisfied.
  • the PDU session requirement information is used by the session management entity to send the identifier information of the first intermediate session management entity to the access management entity.
  • the communication system further includes a session management entity, and the network device is an access management entity.
  • the session management entity is configured to determine PDU session requirement information according to the PDU session subscription information; or determine PDU session requirement information according to one or more of PDU session policy information and PDU session expectation information, and PDU session subscription information; determine access management
  • the fourth intermediate session management entity selected by the entity does not satisfy the PDU session requirement information, and sends a PDU session requirement information and a reselection indication message to the access management entity, where the reselection indication message is used to instruct the access management entity to select the first intermediate session management entity.
  • the access management entity is further configured to select a session management entity, select a fourth intermediate session management entity when the jurisdiction of the session management entity does not include the serving base station indicated by the location information of the UE, and receive the PDU session requirement information from the session management entity. And reselect the indication message.
  • the communication system further includes a session management entity, and the network device is an access management entity.
  • the session management entity is configured to: according to the PDU session subscription information; or determine the PDU session requirement information according to one or more of the PDU session policy information and the PDU session expectation information, and the PDU session subscription information, and send the PDU session request to the access management entity. information.
  • the access management entity is further configured to select a session management entity, and when the jurisdiction of the session management entity does not include the serving base station indicated by the location information of the UE, select a fourth intermediate session management entity (not shown in FIG. 2a), and determine the fourth The intermediate session management entity does not satisfy the PDU session requirement information from the session management entity.
  • the embodiment of the present invention implements the intermediate session management entity according to the location information of the UE and the PDU session requirement information, so that the intermediate session management entity close to the UE can provide services for the PDU session, thereby reducing the delay of data transmission.
  • the intermediate session management entity selects the user plane entity according to the location information of the UE and the PDU requirement information, and the intermediate session management entity only manages the user plane entity in the specified range, and does not need to manage the user plane entity of the entire PDU session, thereby reducing management complexity.
  • FIG. 3 is a schematic flowchart of a session management method according to an embodiment of the present invention.
  • the session management method is based on the network architecture of FIG. 1a, and the network device is an access management entity.
  • the method includes but is not limited to the following steps:
  • the user equipment sends a PDU session establishment request to the access management entity, where the access management entity receives the PDU session establishment request sent by the user equipment.
  • the user equipment sends a PDU session establishment request to the access management entity by using the serving base station (not shown), where the PDU session establishment request is used to create a PDU session, and the PDU session establishment request carries the PDU session expectation information and The location information of the UE, the PDU session expectation information is a related parameter requirement of the PDU session requested by the user equipment, and the PDU session expectation information includes one or more of local DNN, network slice information, PDU session type, and SSC mode, and network slice information.
  • a related attribute for describing a network slice for example, the network slice information includes one or more of a network slice type, a network slice identifier, and a network slice location.
  • the PDU session expectation information is a NAS (Non-Access Stratum) message.
  • the location information of the UE indicates the location in the access network of the UE, and the location information of the UE may be the identifier of the serving cell of the UE or the identifier of the serving base station of the UE or the tracking area identifier of the UE.
  • the access management entity selects a session management entity.
  • the access management entity obtains the resolvable parameter carried in the PDU session establishment request, where the parameters that the access management entity can parse include the location information of the UE, the local DNN, and the network slice information, and the access management entity according to the location of the UE
  • the session management entity is selected by one or more of information, local DNN, and network slice information.
  • the access management entity may use one or more of the location information of the UE, the local DNN, and the network slice information as input parameters, in a database configured locally according to the input parameter, or in a Network Function Repository Function (NRF).
  • NRF Network Function Repository Function
  • the function referred to as NRF, performs a query to obtain the identity of the selected session management entity.
  • the access management entity sends a PDU session establishment request to the session management entity.
  • the session management entity receives the PDU session request message sent by the access management entity, selects an anchor user plane entity, and determines that the first intermediate session management entity needs to be selected.
  • the session management entity selects the first intermediate session management entity according to the location information of the UE and the PDU session requirement information.
  • the session management entity parses the location information of the UE and the PDU session expectation information in the PDU session management request, and the session management entity obtains the PDU session subscription information from the UDM (Unified Data Management, UDM for short), the policy.
  • the control entity obtains PDU session policy information, for example, the PDU session policy information includes a QoS (Quality of Service) policy and a charging policy.
  • the session management entity may determine the PDU session requirement information according to the PDU session subscription information; or the session management entity determines the PDU session requirement information according to one or more of the PDU session expectation information and the PDU session policy information, and the PDU session subscription information.
  • the PDU session requirement information indicates the relevant parameter requirements of the PDU session that the network side can accept.
  • the PDU session requirement information includes a PDU session type, an SSC mode, a local DNN, and a data transmission mode, and the transmission mode mode is a Mutilhoming mode or a ULCL mode.
  • the session management entity is pre-configured with a jurisdiction, and the session management entity can only manage network elements within the relationship (for example, base stations, user plane entities, etc.), and the jurisdiction can be determined by the operator at the time of deployment, and the size of the jurisdiction is not limited. For example, the jurisdiction of a session management entity is a province, a city, or a data center.
  • the session management entity selects an anchor user plane entity, and the anchor user plane entity is used to interface with the data network.
  • the session management entity determines whether it is necessary to select the first intermediate session management entity, and the method for determining may be:
  • the session management entity determines whether the serving base station indicated by the location information of the UE is connected to the selected anchor user plane entity. If not, the session management entity selects the first intermediate session management entity according to the location information of the UE and the PDU session requirement information.
  • the session management entity determines whether its own jurisdiction includes the data network indicated by the local DNN. If not, the session management entity selects according to the location information of the UE and the PDU session requirement information. The first intermediate session management entity.
  • the method for the session management entity to select the first intermediate session management entity may be:
  • the session management entity will use the intermediate session management entity of the serving base station that satisfies the PDU session requirement information and whose location includes the location information indication of the UE as the first intermediate session management entity.
  • the session management entity determines that there is no intermediate session management entity that satisfies the PDU session requirement information and the jurisdiction includes the location information indication of the UE, the second intermediate session management entity that meets the PDU session requirement information is selected, and the session is selected.
  • the jurisdiction includes a third intermediate session management entity of the serving base station indicated by the location information of the UE, and the second intermediate session management entity and the third intermediate session management entity simultaneously provide services for the PDU session.
  • the session management entity When the transmission mode and the local DNN are included in the PDU session requirement information, the session management entity will support the DN indicated by the local DNN, and the intermediate session management entity supporting the transmission mode as the first intermediate session management entity.
  • the session management entity determines that there is no DN indicated by the serving base station and the local DNN indicated by the location information of the UE, and an intermediate session management entity that supports the transmission mode, where the session management entity selects the location information indication including the UE.
  • the PDU session provides services.
  • the session management entity sends a PDU session establishment request to the first intermediate session management entity.
  • the PDU session establishment request carries the location information of the UE and the PDU session requirement information.
  • the session management entity may send the location information of the UE and the PDU session requirement information to the first intermediate session management entity through the PDU session establishment request.
  • the session management entity sends an uplink offload policy and an uplink routing policy to the first intermediate session management entity, where the uplink offload policy is used to control the branch point BP anchored by the UE.
  • the uplink routing policy is used to control the UE to use the IP address anchored at the anchor user plane entity or the local IP address anchored at the local anchor user plane entity as the source of the data packet. address.
  • the data transmission mode is a Mutilhoming mode
  • the session management entity sends an IP routing address anchored to the anchor user plane entity and an uplink routing policy corresponding to the IP address anchored to the anchor user plane entity to the An intermediate session management entity
  • the IP address anchored at the anchor user plane entity is used to enable the first intermediate session management entity to generate an uplink offload policy
  • the uplink routing policy is used to enable the first intermediate session management Entity generating the uplink routing policy
  • the uplink routing policy is used to indicate that the UE uses the IP address anchored at an anchor user plane entity or uses a local IP address anchored at a local anchor user plane entity as a source Address to send data.
  • the data transmission mode is an uplink classifier ULCL mode
  • the session management entity sends an uplink forwarding policy to the first intermediate session management entity
  • an uplink forwarding policy is used to control the UE anchoring.
  • the uplink classifier ULCL forwards according to one or more of a quintuple and an application identifier of the data packet sent by the UE.
  • the first intermediate session management entity receives a PDU session establishment request from the session management entity, and the first intermediate session management entity selects a BP and a local anchor user plane entity.
  • S306 is an optional step.
  • the transmission mode is the Mutilhoming mode, where the first intermediate session management entity parses the location information of the UE and the PDU session requirement information in the PDU session establishment request.
  • the first intermediate session management entity selects a local anchor user plane entity for the PDU session, and selects a branch point BP for the PDU session; wherein the BP is used to offload the data packet sent by the UE, the local anchor user plane entity and the PDU
  • the session requirement information includes a local data network DN connection indicated by the local DNN, and the BP is connected to the serving base station indicated by the location information of the UE.
  • the first intermediate session management entity selects a local anchor user plane entity for the PDU session, and selects an uplink classifier ULCL for the PDU session; where the ULCL is used to send data to the UE
  • the application identifier and/or quintuple of the packet is offloaded, and the local anchor user plane entity is connected to the local DN indicated by the local DNN, and the ULCL is connected to the serving base station indicated by the location information of the UE.
  • the jurisdiction of the first intermediate session management entity includes the serving base station of the UE
  • the local anchor user plane entity, the user plane entity connected to the serving base station, and the BP/ULCL may be the same user plane entity.
  • the first intermediate session management entity sends an N4 message to the selected BP.
  • S307 is an optional step.
  • the N4 message in this step represents a message transmitted through the N4 interface
  • the first intermediate session management entity allocates N3 uplink tunnel information and N9 downlink tunnel information
  • the N3 uplink tunnel information indicates a tunnel between the BP and the serving base station of the user equipment.
  • the identification information, the N9 downlink tunnel information indicates the identification information of the tunnel between the BP and the local anchor user plane entity, and the identification information of the tunnel between the BP and the anchor user plane entity.
  • the first intermediate session management entity sends the N3 uplink tunnel information and the N9 downlink tunnel information to the BP through the N4 message, and the BP receives the N3 uplink tunnel information and the N9 downlink tunnel information from the first intermediate session management entity, and creates an N3 tunnel on the local path. And the N9 tunnel.
  • the first intermediate session management entity sends an N4 message to the ULCL.
  • the N4 message includes N3 uplink tunnel information and N9 downlink tunnel information, and the ULCL receives the N4 message to create an N3 tunnel and an N9 tunnel.
  • the first intermediate session management entity sends an N4 message to the selected local anchor user plane entity.
  • S308 is an optional step.
  • the first intermediate session management entity allocates a local IP address and N9 uplink and downlink tunnel information to the local anchor user plane entity, and the first intermediate session management entity sends the local IP address and the N9 uplink and downlink to the local anchor user plane entity through the N4 message.
  • Tunnel information the anchor user plane entity receives the N4 message and creates an N9 tunnel of the local path.
  • the first intermediate session management entity sends a response message to the session management entity.
  • S309 is an optional step.
  • the response message may carry the N9 downlink tunnel information of the BP.
  • the first intermediate session management entity may further send the location information and/or the local IP address of the local anchor user plane entity to the session management entity.
  • the session management entity sends an N4 message to the anchor user plane entity.
  • S310 is an optional step.
  • the session management entity allocates an IP address and an N9 uplink and downlink tunnel information of the anchor user plane entity to the PDU session, and sends the allocated IP address and the N9 uplink and downlink tunnel information to the anchor user plane entity through the N4 message, and the anchor user plane entity Receive an N4 message and create an N9 tunnel with BP.
  • S311 Allocate a radio resource of the PDU session.
  • S311 is an optional step.
  • the session management entity requests the access network (shown in the figure) to create a user plane tunnel and allocate air interface resources for the PDU session, and configure the QoS policy of the PDU session to the access access network, and the access network sends the N3 downlink tunnel information. Give the session management entity.
  • the session management entity sends a PDU session update request to the first intermediate session management entity.
  • S312 is an optional step.
  • the session management entity sends the N3 downlink tunnel information to the first intermediate session management entity.
  • the session management entity may also send the IP address assigned by the session management entity to the first intermediate session management entity when the session type of the PDU session is an IP type.
  • the first intermediate session management entity sends a PDU session update request to the BP.
  • S313 is an optional step.
  • the PDU session update request includes the N3 downlink tunnel information, the N9 uplink tunnel information of the anchor user plane entity, and the N9 uplink tunnel information of the local anchor user plane entity.
  • the BP receives the PDU session update request and updates the PDU session. If the uplink offloading policy needs to be updated, the PDU session update request further includes an updated uplink offloading policy.
  • the first intermediate session management entity sends a response message to the session management entity.
  • the response message indicates that the update of the PDU session is completed.
  • S314 is an optional step.
  • the session management entity receives a response message from the first intermediate session management entity, and sends a response message to the access management entity.
  • S315 is an optional step.
  • the first intermediate session management entity sends a route advertisement to the user equipment by using a local anchor user plane entity.
  • S316 is an optional step.
  • the transmission mode in this step is the Mutilhoming mode.
  • the route advertisement carries the uplink routing policy and the IP address assigned by the session management entity.
  • the uplink routing policy is used to control the IP address or the first IP address assigned by the session management entity when the UE sends the data packet.
  • the local IP address assigned by the intermediate session management entity is used as the source address.
  • the user plane entity may be any type of user plane entity.
  • the user plane entity determines that there is no downlink N3 tunnel information, and the user plane entity sends a downlink data notification to the first intermediate session management entity, and the first intermediate session management entity forwards the received downlink data notification to the session management entity, and the session management entity triggers the paging. Process.
  • the session management entity After receiving the downlink N3 tunnel information sent by the serving base station of the UE, the session management entity sends a PDU session update request to the first intermediate session management entity, and the first intermediate session management entity receives the PDU session update request, and learns the downlink from the PDU session update request.
  • the first intermediate session management entity notifies the user plane entity of the downlink N3 tunnel information, and the user plane entity receives the downlink N3 tunnel information, and then performs uplink data transmission.
  • the session management entity and the intermediate session management entity are only responsible for managing user plane entities within the jurisdiction, and do not need to manage all user plane entities in the entire PDU session, reducing the number of messages in the middle of the user plane entity. And reduced the workload.
  • FIG. 4 is a schematic flowchart of a session management method according to an embodiment of the present invention.
  • a handover process of the architecture 1a is used.
  • the source access network of the UE is a serving base station.
  • the source intermediate session management entity (the first intermediate session management entity), the source user plane entity, and the anchor user plane entity provide services for the PDU session.
  • the method includes, but is not limited to, the following steps:
  • the target access network sends a path switch request to the session management entity by using an access management entity.
  • S401 is an optional step.
  • the target access network After the UE is switched from the source access network to the target access network, the target access network sends a path switch request to the session management entity by using the access management entity, where the path switch request carries the location information of the UE, and the location information of the UE may be The identity of the base station where the UE is camped or the identity of the cell that resides.
  • the session management entity receives the path switch request, and determines, according to the location information of the UE, that the UE is not within the jurisdiction of the first intermediate session management entity, and the session management entity selects the target intermediate session management entity.
  • the session management entity saves the PDU session requirement information of the PDU session, and the session management entity selects the target intermediate session management entity according to the location information of the UE and the PDU session requirement information.
  • the specific selection process refer to the description of S304 in FIG. 3, where No longer.
  • the session management entity sends a PDU session establishment request to the target intermediate session management entity.
  • the PDU session establishment request carries the location information of the UE and the PDU session requirement information.
  • the target intermediate session management entity receives the PDU session establishment request, and selects the target user plane entity according to the location information of the UE and the PDU session requirement information.
  • S404 is an optional step.
  • the specific process of selecting the target user plane entity according to the location information of the UE and the PDU session requirement information of the target intermediate session management entity may refer to the description of S306 in FIG. 3 , and details are not described herein again.
  • the target intermediate session management entity sends an N4 message to the selected target user plane entity, and the target user plane entity receives the N4 message from the target intermediate session management entity, and the target user plane entity is created between the target user plane entity and the anchor user plane entity.
  • the target intermediate session management entity sends a response message to the session management entity, where the response message carries the identification information of the created N3 tunnel and the identification information of the N9 tunnel, and the session management entity receives the identifier information of the N3 tunnel sent by the intermediate session management entity and N9.
  • the identification information of the tunnel, and the identifier information of the N9 tunnel of the anchor user plane entity is updated.
  • the session management entity sends a handover response message to the access management entity, and the access management entity receives the handover response message from the session management entity, and learns to complete the update process of the tunnel.
  • the session management entity selects the intermediate session management entity and the user plane entity close to the UE to provide services for the UE, reduces delay in data transmission, and simultaneously manages the session management entity and the intermediate session.
  • the entity is only responsible for managing user plane entities within the jurisdiction, does not need to manage all user plane entities in the entire PDU session, reduces the number of messages in the middle of the user plane entity and reduces the workload.
  • FIG. 5 is a schematic flowchart of a session management method according to an embodiment of the present invention.
  • the embodiment of the present invention is applicable to the architecture of FIG. 2a, and the method includes but is not limited to:
  • S501 The user equipment sends a PDU session establishment request to the access management entity.
  • S501 is an optional step.
  • the user equipment sends a PDU session establishment request to the access management entity through the associated serving base station (not shown).
  • the PDU session establishment request is used to create a PDU session, and the PDU session establishment request carries the PDU session expectation information and the UE.
  • the location information, the PDU session expectation information is a related parameter requirement of the PDU session requested by the user equipment, and the PDU session expectation information includes one or more of a local DNN, a network slice information, a PDU session type, and an SSC mode, and the network slice information is used. Describe the relevant attributes of the network slice, for example, the network slice information includes one or more of a network slice type, a network slice identifier, and a network slice location.
  • the PDU session expectation information is a NAS (Non-Access Stratum) message.
  • the location information of the UE indicates the location in the access network of the UE, and the location information of the UE may be the identifier of the serving cell of the UE or the identifier of the serving base station of the UE.
  • the access management entity receives the PDU session establishment request from the UE, selects a session management entity, and determines that the fourth session management entity needs to be selected.
  • S502 is an optional step.
  • the access management entity obtains the resolvable parameters carried in the PDU session establishment request, and the parameters that the access management entity can parse include the location information of the UE, the local DNN, and the network slice information, and the access management entity according to the location information of the UE, One or more of the local DNN and network slice information selects a session management entity.
  • the access management entity may use one or more of the location information of the UE, the local DNN, and the network slice information as input parameters, in a database configured locally according to the input parameter, or in a Network Function Repository Function (NRF).
  • NRF Network Function Repository Function
  • the access management entity determines whether the jurisdiction of the selected session management entity includes the serving base station indicated by the location information of the UE, and if not, the access management entity determines that a fourth intermediate session management entity needs to be initially selected, and the access management entity selects
  • the method of the fourth intermediate session management entity may be: selecting the fourth intermediate session management entity according to one or more of the location information of the UE, the local DNN, and the network slice information.
  • the access management entity sends a PDU session establishment request to the fourth intermediate session management entity.
  • the PDU session establishment request further carries the identifier information of the session management entity.
  • S503 is an optional step.
  • the identification information of the first intermediate session management entity may be address information, location information, or ID (Identity, ID for short).
  • the fourth intermediate session management entity receives a PDU session establishment request from the access management entity, and selects a user plane entity.
  • S504 is an optional step.
  • the fourth intermediate session management entity acquires the PDU session expectation information carried in the PDU session request message, the location information of the UE, and the identifier information of the session management entity, and the fourth intermediate session management entity selects according to the PDU session expectation information and the location information of the UE.
  • User face entity (not shown).
  • the method for selecting a user plane entity may be: the fourth intermediate session management entity selects a user plane entity within the jurisdiction, and the selected user plane entity is connected to the serving base station of the UE.
  • the fourth intermediate session management entity sends an N4 message to the selected user plane entity, and the user plane entity receives the N4 message to create an N3 downlink tunnel and an N9 uplink tunnel.
  • the fourth intermediate session management entity sends a PDU session establishment request to the session management entity.
  • S505 is an optional step.
  • the session management entity receives a PDU session establishment request from the fourth intermediate session management entity, selects an anchor user plane entity, and determines that the first intermediate session management entity needs to be selected.
  • the session management entity obtains PDU session subscription information from the UDM, and acquires PDU session policy information from the policy control entity.
  • the session management entity may determine the PDU session requirement information according to the PDU session subscription information; or the session management entity determines the PDU session requirement information according to one or more of the PDU session expectation information and the PDU session policy information, and the PDU session subscription information.
  • the PDU session requirement information indicates the relevant parameter requirements of the PDU session that the network side can accept.
  • the PDU session requirement information includes a PDU session type, an SSC mode, a local DNN, and a data transmission mode, and the transmission mode mode is a Mutilhoming mode or a ULCL mode.
  • the session management entity is pre-configured with a jurisdiction, and the session management entity can only manage network elements within the relationship (for example, base stations, user plane entities, etc.), and the jurisdiction can be determined by the operator at the time of deployment, and the size of the jurisdiction is not limited.
  • the jurisdiction of a session management entity is a province, a city, or a data center.
  • the session management entity selects an anchor user plane entity, and the anchor user plane entity is used to interface with the data network.
  • the session management entity determines whether the fourth intermediate session management entity satisfies the PDU session requirement information. If not, the session management entity selects the first intermediate session management entity according to the location information of the UE and the PDU session requirement information, and determines whether the first intermediate is selected.
  • the session management entity and the method for selecting the first intermediate session management entity reference may be made to the description of S304 in FIG. 3, and details are not described herein again.
  • the session management entity After selecting the first intermediate session management entity, the session management entity notifies the first intermediate session management entity of the location information of the UE and the PDU session requirement information.
  • the session management entity notifying the first intermediate session management entity that the location information of the UE and the PDU session requirement information may be the process of S507 to S509.
  • the session management entity sends a response message to the fourth intermediate session management entity.
  • the response message carries the PDU session requirement information, the location information of the UE, and the identifier information of the first intermediate session management entity, because the first intermediate session entity is reselected at S506.
  • the identification information of the first intermediate session management entity may be address information, location information, or ID (Identity, ID for short).
  • the fourth intermediate session management entity receives the response message from the session management entity, and sends a response message to the access management entity.
  • the fourth intermediate session management entity deletes the local session, and the response message carries the identifier information of the first intermediate session management entity and the PDU session requirement information.
  • the access management entity receives the response message from the fourth intermediate session management entity, and sends a PDU session establishment request to the first intermediate session management entity.
  • the PDU session establishment request carries the location information of the UE and the PDU session requirement information.
  • the first intermediate session management entity receives a PDU session establishment request from the access management entity, acquires location information of the UE, and PDU session requirement information, and selects a user plane entity according to the location information of the UE and the PDU session requirement information, and selects a user plane entity.
  • a PDU session establishment request from the access management entity
  • acquires location information of the UE, and PDU session requirement information and selects a user plane entity according to the location information of the UE and the PDU session requirement information, and selects a user plane entity.
  • the first intermediate session management entity sends an N4 message to the selected user plane entity, and the user plane entity receives the N4 message, and creates a local session according to the indication of the N4 message.
  • the first intermediate session management entity sends a PDU session establishment request to the session management entity.
  • the session management entity sends an N4 message to the anchor user plane entity, the anchor user plane entity receives the N4 message from the session management entity, and creates a session according to the indication of the N4 message.
  • the first intermediate session management entity sends a PDU session establishment request to the session management entity.
  • the session management entity sends an N4 message to the selected anchor user plane entity, the anchor user plane entity receives the N4 message, creates a local session, and after the anchor user plane entity successfully creates a local session, sends a response message to the session management entity, and the response message is sent. Indicates that the local session was successfully created.
  • the session management entity receives the response message, and sends a response message to the first intermediate session management entity.
  • the first intermediate session management entity receives the response message from the session management entity, and the first intermediate session management entity sends the received response message to the access message.
  • the management entity receives an response message from the first intermediate session management entity.
  • the redirection indication message and the PDU session requirement information are sent to the access management entity, and the access management entity receives the reselection indication message and the PDU from the session management entity.
  • the session requirement information the first intermediate session management entity is selected according to the location information of the UE and the PDU session requirement information.
  • the method of selection refer to the description of S304 in FIG. 3, and details are not described herein again.
  • the access management entity receives the PDU session requirement information from the session management entity, and when the access management entity determines that the first intermediate session management entity needs to be selected, according to the location information of the UE and the PDU session requirement. The information selects the first intermediate session management entity.
  • the session management entity when the session management entity determines that the first intermediate session management entity does not need to be selected, the session management entity sends an N4 message to the selected anchor user plane entity, and the anchor user plane entity receives the N4 message, and creates an N3 tunnel and an N9 tunnel.
  • the session management entity sends a response message to the fourth intermediate session management entity, where the response message carries the PDU session requirement information and the location information of the UE, and the fourth intermediate session management entity receives the response message from the session management entity to obtain the PDU session requirement information.
  • the fourth intermediate session management entity determines whether the user plane entity selected by S504 satisfies the PDU session requirement information. If not, the fourth intermediate session management entity reselects the user plane entity according to the location information of the UE and the PDU session requirement information. The description of S306 of FIG. 3 will not be repeated here.
  • the session management entity and the intermediate session management entity are only responsible for managing user plane entities within the jurisdiction, and do not need to manage all user plane entities in the entire PDU session, reducing the number of messages in the middle of the user plane entity. And reduced the workload.
  • FIG. 6 is a schematic flowchart of a session management method according to an embodiment of the present invention.
  • a handover process of the architecture 2a is used.
  • the source access network of the UE is a serving base station.
  • the source intermediate session management entity (the first intermediate session management entity), the source user plane entity, and the anchor user plane entity provide services for the PDU session.
  • the method includes, but is not limited to, the following steps:
  • the target access network sends a path switch request to the access management entity.
  • the path switching request carries the location information of the UE.
  • the access management entity receives a path switch request from the target access network, determines that the UE is not within the jurisdiction of the first intermediate session management entity, and selects the target intermediate session management entity.
  • the method of selecting the target intermediate session management entity can refer to the description of S402 in FIG.
  • the access management entity sends a session establishment request to the target intermediate session management entity.
  • the target intermediate session management entity receives a session establishment request from the access management entity, and selects a target user plane entity.
  • the method of selecting the target user plane entity can be referred to the description of S404 in FIG. S604 is an optional step.
  • the access management entity receives the new PDU session requirement information sent by the session management entity, and the session management entity sends the new PDU session requirement information to the access management entity by using the first intermediate session management entity, and the access management entity determines Whether the intermediate session management entity satisfies the new PDU session requirement information, and if not, the access management entity selects the target intermediate session management entity, and the method of selecting the target intermediate session management entity may refer to the description in S402 in FIG.
  • the access management entity selects an intermediate session management entity and a user plane entity close to the UE to provide services for the UE, reducing delay in data transmission, and the session management entity and the intermediate session management entity are only responsible for managing the jurisdiction.
  • the user plane entity inside does not need to manage all user plane entities in the entire PDU session, reducing the number of messages in the middle of the user plane entity and reducing the workload.
  • FIG. 9 is a schematic flowchart of a session management method according to an embodiment of the present invention.
  • a session management method is based on the network architecture of FIG. 1a. This embodiment assumes that a UE has established a PDU session. The session is served by the session management entity and the user plane of the PDU session is served by the anchor user plane entity. The method includes but is not limited to the following steps:
  • the session management entity selects the first intermediate session management entity.
  • the PDU session requirement information includes one or more of a PDU session type, an SSC mode, a local DNN, and a data transmission mode
  • the data transmission mode is a Mutilhoming mode or a ULCL mode.
  • the session management entity determines the local DNN in the PDU session requirement information according to the information from the application function and the location information of the UE, and the information from the application function includes the subordinate information of the application, for example, which local DN the application is deployed, and the information is used locally. DNN logo.
  • the session management entity selects a local DN close to the UE location according to the location of the UE and one or more local DNs to which the application belongs, and uses the local DNN identifier corresponding to the selected local DN as the local DNN in the PDU session requirement information. It should be noted that other information in the PDU session requirement information, such as a data transmission mode, a PDU session type, and the like, are still determined by using the method in S304, and details are not described herein again.
  • the session management entity selects the first intermediate session management entity to determine whether the first intermediate session management entity needs to be selected, and the session management entity determines whether the first intermediate session management entity needs to be selected, and the determining method may be:
  • the session management entity determines, according to the PDU session requirement information, that when the UPF connected to the local DN is not controlled by the session management entity, the session management entity selects (or acquires) the first intermediate session management entity according to the PDU session requirement information.
  • the session management entity acquires the first intermediate session management entity according to the location information of the UE and the PDU session requirement information.
  • the method for the session management entity to select the first intermediate session management entity may be:
  • the session management entity uses the intermediate session management entity that satisfies the PDU session requirement information as the first intermediate session management entity.
  • the session management entity selects the first intermediate session management entity according to the UE location information and the PDU session requirement information, and the session management entity selects the intermediate session management entity of the serving base station that meets the PDU session requirement information and includes the location information indication of the UE.
  • An intermediate session management entity selects the first intermediate session management entity according to the UE location information and the PDU session requirement information, and the session management entity selects the intermediate session management entity of the serving base station that meets the PDU session requirement information and includes the location information indication of the UE.
  • the session management entity When the transmission mode and the local DNN are included in the PDU session requirement information, the session management entity will support the DN indicated by the local DNN, and the intermediate session management entity supporting the transmission mode as the first intermediate session management entity.
  • the session management entity uses the intermediate session management entity supporting the DN indicated by the local DNN as the first intermediate session management entity.
  • the session management entity uses the intermediate session management entity supporting the transmission mode as the first intermediate session management entity.
  • the session management entity selects the first intermediate session management entity, for example, the session management entity includes the jurisdiction The serving base station indicated by the location information of the UE, the DN indicating the local DNN indication, and the intermediate session management entity supporting the transmission mode as the first intermediate session management entity.
  • the method for selecting the first intermediate session management entity according to other combinations is similar to the above method, and the present invention will not be described again.
  • the session management entity sends a PDU session establishment request to the first intermediate session management entity, where the first intermediate session management entity receives a PDU session establishment request from the session management entity.
  • the PDU session establishment request carries the location information of the UE.
  • the session management entity may send the location information of the UE to the first intermediate session management entity through a PDU session establishment request.
  • the session management entity selects a user plane entity according to the location information of the UE, such as a BP, a local anchor user plane entity, and the like.
  • the PDU session establishment request further carries a data transmission mode, and the data transmission mode is a Multihoming or ULCL mode.
  • the session management entity sends an uplink offloading policy to the first intermediate session management entity, where the uplink offloading policy is used to control the branch point BP anchored by the UE according to the UE.
  • the source address of the packet is offloaded.
  • the session management entity sends the UE IP address (the remote UE IP address) anchored at the anchor user plane entity to the first intermediate session management entity; anchored at the anchor point.
  • the UE IP address of the user plane entity (the remote UE IP address) is used to enable the first intermediate session management entity to generate an uplink offload policy, and the uplink offload policy is used by the Branching Point UPF to forward the received uplink data packet according to the source address.
  • the session management entity when the data transmission mode is the uplink classifier ULCL mode, the session management entity sends an uplink forwarding policy to the first intermediate session management entity, and the uplink forwarding policy is used to control the UE-anchored uplink classifier ULCL according to the One or more of the quintuple and the application identifier of the data packet sent by the UE are forwarded.
  • the session management entity when the data transmission mode is the uplink classifier ULCL mode, the session management entity sends the application information of the access local DN to the first intermediate session management entity, where the application information is the application identifier, and the application corresponding quintuple At least one of the application information is used to indicate that the first intermediate session management entity determines an uplink forwarding policy according to the application information, and the uplink forwarding policy is used to control the uplink classifier ULCL anchored by the UE according to the five-element of the data packet sent by the UE. Forward one or more of the group and application IDs.
  • the session management entity sends the routing information between the local anchor user plane entity and the local DN identified by the local DNN to the first intermediate session management entity, where the routing information is used to determine the local anchor user plane entity and the local DN.
  • the forwarding path between the first intermediate session management entity determines the forwarding rule on the interface of the local anchor user plane entity facing the local DN according to the routing information.
  • the session management entity further sends one or more of the PDU session type and the local DNN to the first intermediate session management entity, where the first intermediate session management entity selects the local user according to the PDU session type and/or the local DNN. Face entity.
  • the first intermediate session management entity selects a local user plane entity.
  • the first intermediate session management entity parses the location information of the UE in the PDU session establishment request.
  • the first intermediate session management entity selects a local anchor user plane entity for the PDU session, and selects a BP for the PDU session; wherein the BP is used to offload the data packet sent by the UE, the local anchor user plane entity and the local DNN indication
  • the local data network DN is connected, and the BP is connected to the serving base station indicated by the location information of the UE.
  • the first intermediate session management entity selects a local anchor user plane entity for the PDU session, and selects an uplink classifier ULCL for the PDU session; where the ULCL is used to send the UE
  • the application identifier and/or the quintuple of the data packet is offloaded, and the local anchor user plane entity is connected to the local DN indicated by the local DNN, and the ULCL is connected to the serving base station indicated by the location information of the UE.
  • the local anchor user plane entity and the user plane entity BP/ULCL connected to the serving base station may be the same user plane entity.
  • the first intermediate session management entity selects BP or ULCL according to the location information of the UE:
  • the first intermediate session management entity selects a user plane entity connected to the serving base station indicated by the location of the UE as BP or ULCL.
  • the first intermediate session management entity when the first intermediate session management entity receives one or more of a transmission mode, a local DNN, and a PDU session type in the PDU session establishment request from the session management entity, the first intermediate session management entity may also be configured according to the transmission mode.
  • One or more of the local DNN and PDU session types select the local session anchor user plane entity:
  • the first intermediate session management entity selects a local session anchor user plane entity according to the data transmission mode, and the first intermediate session management entity selects a user plane entity that supports the data transmission mode indicated by the session management entity as the local session anchor user. Face entity.
  • the first intermediate session management entity selects a local session anchor user plane entity according to the local DNN, and the first intermediate session management entity selects a user plane entity that supports the local DNN indicated by the session management entity as the local session anchor user plane entity.
  • the first intermediate session management entity selects a local session anchor user plane entity according to the type of the PDU session, and the first intermediate session management entity selects a user plane entity that supports a type of the PDU session indicated by the session management entity as a local session anchor. Point the user face entity.
  • the first intermediate session management entity may further select a local session anchor user plane entity according to a combination of any two or three of a data transmission mode, a local DNN, and a PDU session type, for example, the first intermediate session management entity. Selecting a local session anchor user plane entity according to the transmission mode and the local DNN. At this time, the first intermediate session management entity selects a data transmission mode indicated by the support session management entity and a user plane supporting the local DNN indicated by the session management entity. The entity acts as a local session anchor user polygon entity. The selection method of other combinations can be analogized by analogy, and will not be described again here.
  • the user plane entity selected according to the foregoing selection method supports connection with the serving base station indicated by the location of the UE, the user plane entity may be selected as the BP/ULCL and the local session anchor user plane entity.
  • the first intermediate session management entity sends an N4 message to the selected BP or ULCL, and the BP/ULCL receives the message. This step is the same as S307, and will not be described here.
  • the first intermediate session management entity sends an N4 message to the selected local anchor user plane entity. This step is the same as S308, and will not be described here.
  • the first intermediate session management entity sends a response message to the session management entity, and the session management entity receives a response message from the first intermediate session management entity.
  • the response message may carry the N9 downlink tunnel information of the BP or the ULCL.
  • the first intermediate session management entity may also send the local UE IP address to the session management entity.
  • the session management entity sends an N4 message to the anchor user plane entity, and the anchor user plane entity receives the N4 message from the session management entity. This step is the same as S310.
  • the session management entity sends a PDU session update request to the first intermediate session management entity, and the first intermediate session management entity receives the PDU session update request from the session management entity. This step is the same as S312.
  • the first intermediate session management entity sends a PDU session update request to the BP/UCLC, and the BP/ULCL receives the PDU session update request from the first intermediate session management entity. This step is the same as S313.
  • the first intermediate session management entity sends a response message to the session management entity, and the session management entity receives a response message from the first intermediate session management entity.
  • the response message indicates that the update of the PDU session is completed. This step is the same as S314.
  • the first intermediate session management entity sends a route advertisement to the user equipment by using a local anchor user plane entity.
  • the transmission mode in the step is the Mutilhoming mode, where the route advertisement carries the uplink routing policy and the local UE IP address allocated by the first intermediate session management entity, and the uplink routing policy is used to control the UE to select the session management entity to allocate when sending the data packet.
  • the remote UE IP address or the local UE IP address allocated by the first intermediate session management entity is used as the source address.
  • the session management entity may also send a route advertisement to the user equipment according to the requirement, where the route advertisement is used to instruct the UE to select a remote UE IP address or a remote UE IP address.
  • FIG. 10 is a schematic flowchart of a session management method according to an embodiment of the present invention.
  • a handover process of the architecture 1a is used.
  • the source access network of the UE is a serving base station.
  • the source intermediate session management entity (the first intermediate session management entity), the source user plane entity, and the anchor user plane entity provide services for the PDU session.
  • the method includes, but is not limited to, the following steps:
  • S1001 The target access network sends a path switch request to the session management entity by using the access management entity, where the session management entity receives the path switch request from the target access network.
  • the description of S401 is not repeated here.
  • the session management entity selects a target intermediate session management entity.
  • the session management entity determines, according to the location information of the UE, that the UE can access the application more conveniently through the target local DN (such as a more recent or faster access application), and the session management entity uses the target local DNN corresponding to the target local DN as the PDU session requirement. For the local DNN in the information, the session management entity selects the target intermediate session management entity. For the specific selection process, refer to the description of S901 in FIG. 9 , and details are not described herein again.
  • the session management entity sends a PDU session establishment request to the target intermediate session management entity, where the target intermediate session management entity receives the session management entity.
  • the description of S902 is not repeated here.
  • the target intermediate session management entity selects a target user plane entity.
  • the description of S903 is not repeated here.
  • the target intermediate session management entity sends an N4 message to the selected target user plane entity, and the target user plane entity receives the N4 message from the target intermediate session management entity, and the target user plane entity is created between the target user plane entity and the anchor user plane entity.
  • the target intermediate session management entity sends a response message to the session management entity, where the response message carries the identification information of the created N3 tunnel and the identification information of the N9 tunnel, and the session management entity receives the identifier information of the N3 tunnel sent by the intermediate session management entity and N9.
  • the identification information of the tunnel, and the identifier information of the N9 tunnel of the anchor user plane entity is updated.
  • the session management entity sends a handover response message to the access management entity, and the access management entity receives the handover response message from the session management entity, and learns to complete the update process of the tunnel.
  • the session management entity selects the intermediate session management entity and the user plane entity close to the UE to provide services for the UE, reduces delay in data transmission, and simultaneously manages the session management entity and the intermediate session.
  • the entity is only responsible for managing user plane entities within the jurisdiction, does not need to manage all user plane entities in the entire PDU session, reduces the number of messages in the middle of the user plane entity and reduces the workload.
  • the apparatus 7 shown in FIG. 7 may implement the access management entity or the session management entity of the embodiment shown in FIG. 3-7, wherein the apparatus 7 includes: a selecting unit 701. And a transceiver unit 702.
  • the selecting unit 701 is configured to select a first intermediate session management entity for the PDU session according to the location information of the user equipment UE and the protocol data unit PDU session requirement information.
  • the transceiver unit 702 is configured to send the location information of the UE and the PDU session requirement information to the first intermediate session management entity, where the location information of the UE and the PDU session requirement information are used to select a user plane. entity.
  • the PDU session requirement information includes one or more of a session and a service continuity SSC mode and a PDU session type.
  • the selecting unit 701 is configured to select, according to the location information of the UE and the protocol data unit PDU session requirement information, the first intermediate session management entity for the PDU session, including: selecting to simultaneously satisfy the PDU session requirement information, and the jurisdiction includes The intermediate session management entity of the serving base station indicated by the location information of the UE serves as the first intermediate session management entity.
  • the device 7 further includes a determining unit
  • a determining unit configured to: if the network device determines that there is no intermediate session management entity that satisfies the PDU session requirement and the jurisdiction includes the location information indication of the UE;
  • the selecting unit 701 is further configured to select a second intermediate session management entity that satisfies the PDU session requirement information, and select a third intermediate session management entity that has a serving base station whose jurisdiction includes the location information indication of the UE.
  • the PDU session requirement information includes a data transmission mode and a local data network name DNN.
  • the selecting unit 701 is configured to select, according to the location information of the UE and the protocol data unit PDU session requirement information, the first intermediate session management entity for the PDU session, including:
  • the intermediate session management entity of the mode acts as the first intermediate session management entity.
  • the device 7 further includes: a determining unit;
  • the determining unit is further configured to: if the network device determines that there is no serving base station that includes the location information indication of the UE and a local DN indicated by the local DNN, and supports data transmission included in the PDU session requirement information Mode intermediate session management entity;
  • the selecting unit 701 is further configured to select a second intermediate session management entity of the serving base station whose jurisdiction includes the location information indication of the UE, and the selection jurisdiction includes a local DN indicated by the local DNN included in the PDU session requirement information.
  • a third intermediate session management entity supporting a data transmission mode included in the PDU session requirement information is further configured to select a second intermediate session management entity of the serving base station whose jurisdiction includes the location information indication of the UE, and the selection jurisdiction includes a local DN indicated by the local DNN included in the PDU session requirement information.
  • the data transmission mode is a multi-homing Mutilhoming mode
  • the transceiver unit 701 is further configured to:
  • the uplink routing policy is used to control the UE to use an IP address anchored at an anchor user plane entity or a local IP address anchored at a local anchor user plane entity as a source address of the data packet;
  • the first intermediate session management entity generates an uplink offloading policy, and the uplink routing policy corresponding to the IP address of the anchor user plane entity is used to enable the first intermediate session management entity to generate an uplink routing policy; the uplink offloading policy is used to control the BP
  • the offloading is performed according to the source address of the data packet sent by the UE, and the uplink routing policy is used to instruct the UE to use the IP address anchored at the anchor user plane entity or use the local IP address anchored at the local anchor user plane entity as the source address. data.
  • the data transmission mode is an uplink classifier ULCL mode
  • the transceiver unit 702 is further configured to:
  • the uplink forwarding policy is used to control the uplink classifier ULCL anchored by the UE according to the quintuple and the application identifier of the data packet sent by the UE One or more are forwarded.
  • the selecting unit 701 is further configured to:
  • the target session management entity is selected.
  • the selecting unit 701 is configured to select a target session management entity, including:
  • the intermediate session management entity acts as the target intermediate session management entity; or
  • the network device If it is determined that there is no intermediate session management entity that satisfies the PDU session requirement information and the jurisdiction includes the target base station to which the UE is handed over; the network device respectively selects a second intermediate session management entity that satisfies the PDU session requirement information and The jurisdiction includes a third intermediate session management entity of the target base station to which the UE is handed over as the target intermediate session management entity.
  • the device 7 is a session management entity, and the device 7 further includes a determining unit.
  • a determining unit configured to determine PDU session requirement information according to the PDU session subscription information; or determine PDU session requirement information according to one or more of PDU session policy information and PDU session expectation information, and PDU session subscription information;
  • the selecting unit 701 is further configured to select an anchor user plane entity within the jurisdiction of the session management entity according to the PDU session requirement information;
  • the determining unit is further configured to determine, according to the location information of the UE, that the serving base station indicated by the location information of the UE is not connected to the anchor user plane entity.
  • the device 7 is a session management entity, and the session management device 7 further includes a determining unit.
  • the determining unit is configured to determine PDU session requirement information according to PDU session subscription information; or determine PDU session requirement information according to one or more of PDU session policy information and PDU session expectation information, and PDU session subscription information; PDU session The demand information includes a local DNN;
  • the determining unit is further configured to determine that the local DN indicated by the local DNN included in the PDU session requirement information is not located within the jurisdiction of the session management entity.
  • the device 7 is an access management entity.
  • the selecting unit 701 is further configured to select a session management entity.
  • the determining unit is further configured to determine that the serving base station indicated by the location information of the UE is not located within the jurisdiction of the session management entity.
  • the selecting unit 701 is further configured to select a fourth intermediate session management entity.
  • the transceiver unit 702 is further configured to receive the PDU session request and a reselection indication message from the session management entity, where the reselection indication message is used to instruct the access management entity to select the first intermediate session management entity .
  • the device 7 is an access management entity.
  • the selecting unit 701 is further configured to select a session management entity.
  • the determining unit is further configured to determine that the serving base station indicated by the location information of the UE is not located within the jurisdiction of the session management entity.
  • the selection unit 701 is further configured to select a fourth intermediate session management entity.
  • the transceiver unit 702 is further configured to receive the PDU session requirement information from the session management entity.
  • the determining unit is further configured to determine that the fourth intermediate session management entity does not satisfy the PDU session requirement information.
  • the device 7 is an access management entity.
  • the transceiver unit 702 is further configured to: when the requirement of the PDU session changes, receive new PDU session requirement information and a reselection indication message from the session management entity, where the reselection indication message is used to instruct the session management apparatus 7 to select The first intermediate session management entity.
  • the network device is an access management entity.
  • the transceiver unit is further configured to: when the demand of the PDU session changes, the network device receives new PDU session requirement information from the session management entity;
  • the determining unit is further configured to determine that the first intermediate session management entity does not satisfy the new PDU session requirement information.
  • the selecting unit 701 is further configured to select the target intermediate session management entity according to the location information of the UE and the new PDU session requirement information.
  • the device 7 is a session management entity, and the device 7 further comprises a determining unit. a determining unit, configured to determine PDU session requirement information according to the PDU session subscription information; or determine PDU session requirement information according to one or more of PDU session policy information and PDU session expectation information, and PDU session subscription information. The determining unit is further configured to determine that the fourth intermediate session management entity selected by the access management entity does not satisfy the PDU session requirement.
  • the transceiver unit 702 is further configured to send the identifier information of the first intermediate session management entity to the access management entity.
  • the apparatus 7 shown in FIG. 7 can implement the session management entity of the embodiment shown in FIG. 9 and FIG. 10, wherein the apparatus 7 includes: a selecting unit 701 and a transceiver unit. 702.
  • the selecting unit 701 is configured to select a first intermediate session management entity for the protocol data unit PDU session according to the protocol local network data name DNN.
  • the transceiver unit 702 is configured to send location information of the user equipment UE to the first intermediate session management entity, where the location information of the UE is used to select a user plane entity.
  • the selecting unit 701 performs the selecting, by the local DNN, the first intermediate session management entity for the PDU session, including:
  • the selecting unit 701 performs the selecting, by the local DNN, the first intermediate session management entity for the PDU session, including:
  • An intermediate session management entity supporting the local DN indicated by the local DNN is selected as the first intermediate session management entity.
  • the network device is a session management entity
  • the selecting unit 701 is further configured to:
  • the local DNN is determined based on information from the application function.
  • the transceiver unit 702 is further configured to:
  • the transceiver unit 702 is further configured to:
  • the user plane entity selected by the first intermediate session management entity supports both the local DNN and the UE location information
  • the first intermediate session management entity selects a user plane entity supporting the local DNN as a local anchor user plane entity according to the local DNN, and according to the The UE location information selects a user plane entity supporting the UE location information for an access network interface connected to the UE, wherein the local anchor user plane entity is configured to interface with the local DN.
  • the transceiver unit 702 is further configured to:
  • the transceiver unit 702 is further configured to:
  • the remote UE IP address is sent to the first intermediate session management entity, where the remote UE IP is used to instruct the first intermediate session management entity to determine an uplink traffic rule. .
  • the transceiver unit 702 is further configured to:
  • the application information is sent to the first intermediate session management entity to determine an uplink traffic distribution rule according to the application information, where the application information is an application identifier or an application corresponding to five At least one of the tuples.
  • the transceiver unit 702 is further configured to:
  • the transceiver unit 702 is further configured to:
  • the routing information between the local anchor network and the local data network DN identified by the local DNN is sent to the first intermediate session management entity, and the routing information is used to determine a forwarding path between the user plane entity and the local DN.
  • the device 7 may be an access management entity or a session management entity, and the device 7 may also be a field-programmable gate array (FPGA) or an application specific integrated circuit (application specific integrated circuit).
  • FPGA field-programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU Micro controller unit
  • PLD programmable logic device
  • an embodiment of the present invention further provides a network device 8.
  • the network device can be an access management entity or a session management entity, including:
  • the memory 803 is configured to store programs and data.
  • the memory may be a random access memory (English: Random Access Memory, RAM for short) or read only memory (English: Read Only Memory, ROM for short) or a flash memory.
  • the 803 can be located either alone in the communication device or inside the processor 801.
  • the processor 801 is configured to execute the program stored in the memory. When the program is executed, the processor 801 is configured to select a first PDU session according to location information of the user equipment UE and protocol data unit PDU session requirement information. Intermediate session management entity.
  • the transceiver 802 can be used as a separate chip, or can be a transceiver circuit in the processor 801 or as an input/output interface.
  • the transceiver 802 is configured to send the location information of the UE and the PDU session requirement information to the first intermediate session management entity, where the location information of the UE and the PDU session requirement information are used to select a user plane. entity.
  • the network device of the present embodiment and the session management device of FIG. 7 and the method processes of FIG. 3 to FIG. 6 and FIG. 9 and FIG. 10 are based on the same concept, and the technical effects thereof are also the same. Referring to the description of the session management apparatus of FIG. 7 and the method flow of FIGS. 3 to 6 and FIGS. 9 and 10, details are not described herein again.
  • the transceiver 802, the memory 803, and the processor 801 are optionally connected by a bus.
  • the network device 8 When the network device 8 is a chip, it may be a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC) for implementing related functions.
  • FPGA field-programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller
  • PLD programmable Controller
  • PLD programmable logic device
  • chips may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • 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 or transmitted by a computer readable storage medium.
  • the computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请公开了一种会话管理方法、网络设备和通信***。采用本发明实施例，根据UE的位置信息和PDU会话需求信息选择中间会话管理实体，这样可以使靠近UE的中间会话管理实体为PDU会话提供服务，减少数据传输的时延。同时中间会话管理实体根据UE的位置信息和PDU需求信息选择用户面实体，中间会话管理实体负责管理指定范围内的用户面实体，不需要管理整个PDU会话的用户面实体，减少管理的复杂性。

Description

一种会话管理方法、网络设备和通信***
本申请要求了2017年5月5日提交的、申请号为201710314201.2、发明名称为“一种会话管理方法、网络设备和通信***”的中国申请的优先权，以及2018年2月13日提交的、申请号为201810150678.6、发明名称为“一种会话管理方法、网络设备和通信***”的中国申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信领域，尤其涉及一种会话管理方法、网络设备和通信***。
背景技术
在5G新空口的网络架构中，会话管理实体(Session Management Function，会话管理功能，简称SMF)负责会话管理，包括PDU(Protocol Data Unit，协议数据单元，简称PDU)会话的建立、修改和释放等，用户面实体(User Plane Function，用户面功能，简称UPF)负责用户数据的转发。在目前的网络架构中，PDU会话的用户面路径中可能存在多个用户面实体，多个用户面实体中不同的两个用户面实体的位置可能相距较远，例如：一个用户面实体可能位于靠近UE的接入点的位置，而另一个用户面实体可能位于靠近数据网络的位置，如何管理PDU会话中的不同位置的多个用户面实体目前正在讨论中。
发明内容
本发明实施例所要解决的技术问题在于，提供一种会话管理方法、网络设备和通信***，以实现管理不同位置的用户面实体。
第一方面，本申请提供了一种会话管理方法，包括网络设备根据UE(User Equipment，用户设备，简称UE)的位置信息和PDU(Protocol Data Unit，协议数据单元，简称PDU)会话需求信息选择第一中间会话管理实体，网络设备向第一中间会话管理实体发送UE的位置信息和PDU会话需求信息，其中，PDU会话需求信息用于选择用户面实体，第一中间会话管理实体只负责管理指定范围内的网元(例如：接入网设备或用户面实体)。PDU会话需求信息表示核心网确定的PDU会话的相关参数。网络设备为核心网中的设备，网络设备可以为接入管理实体或会话管理实体，接入管理实体用于对UE进行接入管理，会话管理实体用于对UE建立的会话进行管理。
实施上述实施例，网络设备根据UE的位置信息和PDU会话需求信息选择中间会话管理实体，这样可以使靠近UE的中间会话管理实体为PDU会话提供服务，减少数据传输的时延。同时中间会话管理实体根据UE的位置信息和PDU需求信息选择用户面实体，中间会话管理实体只管理指定范围内的用户面实体，不需要管理整个PDU会话的用户面实体，减少管理的复杂性。
在第一方面的一种可能的实现方式中，PDU会话需求信息包括PDU会话类型和/或SSC(Session and Service Continuity，会话和业务连续性，简称SSC)模式。
在第一方面的一种可能的实现方式中，网络设备根据UE的位置信息和PDU会话需求为PDU会话选择第一中间会话管理实体包括：网络设备选择同时满足PDU会话需求信息且管辖范围包括UE的位置信息指示的服务基站的中间会话管理实体作为第一中间会话管理实体。其中，PDU会话需求包括PDU会话类型和/或SSC。UE的位置信息可以为UE的服务基站的标识或UE的服务小区的标识或UE的跟踪区标识，网络设备可根据UE的位置信息确定UE的位置信息指示的服务基站能否与第一中间会话管理实体相连。每个中间会话管理实体具有一定的管辖范围，管辖范围的大小本申请不作限制，例如：中间会话管理实体的管辖范围为一个省、一个市或一个数据中心。
在第一方面的一种可能的实现方式中，PDU会话需求信息包括PDU会话类型和/或SSC，若网络设备判断不存在同时满足PDU会话需求和管辖范围包括UE的位置信息指示的服务基站的中间会话管理实体，网络设备分别选择满足PDU会话需求信息的第二中间会话管理实体，以及选择管辖范围包括UE的位置信息指示的服务基站的第三中间会话管理实体，第二中间会话管理实体和第三中间会话管理实体同时为PDU会话提供服务。这样，同一个PDU会话可由多个中间会话管理实体进行服务，每个中间会话管理实体只负责对指定范围内的网元进行管理，减少了中间会话管理实体的管理负荷和复杂度。
在第一方面的一种可能的实现方式中，PDU会话需求信息包括本地DNN和数据传输模式，本地DNN表示本地DN(Data Network，数据网络，简称DN)的名称。数据传输模式表示数据包在用户面上的传输方式，数据传输模式为Mutilhoming(多归属)模式或ULCL(Uplink Classifier，上行链路分类器)模式。
在第一方面的一种可能的实现方式中，网络设备根据UE的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体包括：网络设备选择同时满足管辖范围包括UE的位置信息指示的服务基站和本地DNN指示的本地DN，以及支持PDU会话需求信息中包括的数据传输模式的中间会话管理实体作为第一中间会话管理实体。
在第一方面的一种可能的实现方式中，网络设备判断不存在管辖范围包括UE的位置信息指示的服务基站和PDU会话需求信息中包括的本地DNN指示的本地DN，以及支持PDU会话需求信息包括的数据传输模式的中间会话管理实体，选择管辖范围包括UE的位置信息指示的服务基站的第二中间会话管理实体，以及选择管辖范围包括PDU会话需求信息中包括的本地DNN指示的本地DN和支持PDU会话需求信息中包括的数据传输模式的第三中间会话管理实体。网络设备可以为接入管理实体或会话管理实体，第二中间会话管理实体和第三中间会话管理实体同时为PDU会话提供服务。
在第一方面的一种可能的实现方式中，数据传输模式为Mutilhoming模式，网络设备将上行分流策略和上行路由策略发送给第一中间会话管理实体；其中，上行分流策略用于控制UE锚定的分支点BP根据UE发送的数据包的源地址进行分流，上行路由策略用于控制UE使用锚定在锚点用户面实体的IP地址或锚定在本地锚点用户面实体的本地IP地址作为数据包的源地址；或网络设备将锚定在锚点用户面实体的IP地址和锚定在锚点用户面实体的IP地址对应的上行路由策略发送给第一中间会话管理实体；锚定在锚点用户面实体的IP地址用于使第一中间会话管理实体生成上行分流策略，锚定在锚点用户面实体的IP地址对应的上行路由策略用于使第一中间会话管理实体生成上行路由策略；上行分流策略 用于控制BP根据UE发送的数据包的源地址进行分流，上行路由策略用于指示UE使用锚定在锚点用户面实体的IP地址或使用锚定在本地锚点用户面实体的本地IP地址作为源地址发送数据。
在第一方面的一种可能的实现方式中，数据传输模式为ULCL模式，网络设备将上行转发策略发送给第一中间会话管理实体，上行转发策略用于控制UE锚定的ULCL根据UE发送的数据包的五元组和/或应用标识进行转发。
在第一方面的一种可能的实现方式中，在UE的切换流程中，UE由当前的服务基站切换到目标基站，在切换发生之前，UE已建立有PDU会话，网络设备保存有PDU会话的PDU会话需求信息，网络设备可根据来自目标基站的路径切换消息获知UE由当前的服务基站切换到目标基站，网络设备判断目标基站是没有位于当前的第一中间会话管理实体的管辖范围内，网络设备选择目标中间会话管理实体，目标中间会话管理实体为同时满足管辖范围包括UE切换到的目标基站和PDU会话需求信息的中间会话管理实体。其中，在不存在同时满足管辖范围包括目标基站和PDU会话需求信息的中间会话管理时，网络设备选择管辖范围包括目标基站的第二中间会话管理实体和满足PDU会话需求信息的第三中间会话管理实体，将第二中间会话管理实体和第三中间会话管理实体作为目标中间会话管理实体。
在第一方面的一种可能的实现方式中，网络设备为会话管理实体，会话管理实体根据UE的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：会话管理实体确定PDU会话需求信息，其中会话管理实体可根据PDU会话签约信息确定PDU会话需求信息；或者会话管理实体可根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息。会话管理实体根据PDU会话需求信息在会话管理实体的管辖范围内选择锚点用户面实体，例如：会话管理实体的管辖范围可以为一个省、一个市、一个数据中心或其他的范围，本申请不作限制，具体的管辖范围可由运营商进行配置。会话管理实体根据UE的位置信息确定UE的位置信息指示的服务基站，判断UE的位置信息指示的服务基站和上述选择的锚点用户面实体不相连时，会话管理功能根据UE的位置信息和PDU会话需求信息选择第一中间会话管理实体。需要说明的是，PDU会话策略信息表示PDU会话的相关策略，例如：QoS(Quality of Service，质量服务，简称QoS)。PDU会话期望信息表示UE请求的会话相关参数，例如PDU会话期望信息包括：本地DNN、PDU会话类型和SSC模式中的一种或多种。
在第一方面的一种可能的实现方式中，网络设备为会话管理实体，会话管理实体根据UE的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：会话管理实体根据PDU会话签约信息确定PDU会话需求信息；或者会话管理实体根据PDU会话期望信息和PDU会话策略信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息。PDU会话策略信息可以来自核心网的策略控制实体。PDU会话期望信息表示UE请求的PDU会话的相关参数，PDU会话期望信息包括PDU会话类型、SSC模式、本地DNN中的一种或多种。会话管理实体判断PDU会话需求信息包括的本地DNN指示的本地DN没有位于会话管理实体的管辖范围。
在第一方面的一种可能的实现方式中，网络设备为接入管理实体，网络设备根据UE 的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：接入管理实体选择会话管理实体，其中，接入管理实体可根据来自UE的本地DNN、网络切片信息和UE签约信息来选择会话管理实体。接入管理实体判断UE的位置信息指示的服务基站没有位于会话管理实体的管辖范围内，接入管理实体根据来自UE的本地DNN、网络切片信息和UE签约信息中的一种和多种和UE的位置信息选择第四中间会话管理实体，接入管理实体接收来自会话管理实体的PDU会话需求信息和重选指示消息，重选指示消息用于指示接入管理实体重新选择一个不同与第四中间会话管理实体的第一中间会话管理实体。
在第一方面的一种可能的实现方式中，网络设备为接入管理实体，网络设备根据UE的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：接入管理实体选择会话管理实体，其中，接入管理实体可根据来自UE的PDU会话建立请求中携带的本地DNN、网络切片信息中的一种或多种来选择会话管理实体。接入管理实体判断UE的位置信息指示的服务基站没有位于会话管理实体的管辖范围内，接入管理实体选择第四中间会话管理实体，接收来自会话管理实体的PDU会话需求信息，判断第四中间会话管理实体不满足PDU会话需求信息。
在第一方面的一种可能的实现方式中，网络设备为接入管理实体，PDU会话需求信息网络设备根据UE的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：当PDU会话的需求发生改变时，接入管理实体接收来自会话管理实体的新PDU会话需求信息和重选指示消息，重选指示消息用于指示接入管理实体重新选择一个中间会话管理实体。
在第一方面的一种可能的实现方式中，网络设备为接入管理实体，第一中间会话管理实体当前为PDU会话提供服务，当PDU会话的需求发生改变时，接入管理实体接收来自会话管理实体的新PDU会话需求信息，接入管理实体判断第一中间会话管理实体不满足新PDU会话需求信息，根据UE的位置信息和新PDU会话需求信息选择目标中间会话管理实体。
在第一方面的一种可能的实现方式中，网络设备为会话管理实体会话管理实体根据PDU会话签约信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息，会话管理实体判断接入管理实体选择的第四中间会话管理实体不满足PDU会话需求信息，会话管理实体根据UE的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体，会话管理实体将第一中间会话管理实体的标识信息发送给接入管理实体，标识信息用于唯一表示第一中间会话实体的身份，例如：第一中间会话管理实体的标识信息可以为地址信息、位置信息或ID(Identity，身份信息，简称ID)等。
第二方面，本申请提供了一种通信***，通信***包括网络设备和第一中间会话管理实体，网络设备可以是接入管理实体或会话管理实体，网络设备用于根据UE的位置信息和PDU会话需求信息为PDU会话选择第一中间会话管理实体。第一中间会话管理实体用于接收来自网络设备的PDU会话需求信息，根据UE的位置信息和PDU会话需求信息选择用户面实体。需要说明的是，会话管理实体和第一中间会话管理实体具有一定的管辖区 域，会话管理实体和第一中间会话管理实体的管辖区域不重合，第一中间会话管理实体负责管理管辖区域内的网元，例如：用户面实体，第一中间会话管理实体的管辖范围的大小可由运营商根据需要进行确定，例如：第一中间会话管理实体的管辖范围为一个省、一个市或一个数据中心，本申请不作限制。
实施第一方面的实施例，网络设备根据UE的位置信息和PDU会话需求信息选择中间会话管理实体，这样可以使靠近UE的中间会话管理实体为PDU会话提供服务，减少数据传输的时延。同时中间会话管理实体根据UE的位置信息和PDU需求信息选择用户面实体，中间会话管理实体只管理指定范围内的用户面实体，不需要管理整个PDU会话的用户面实体，减少管理的复杂性。
在第二方面的一种可能的实现方式中，第一中间会话管理实体，还用于接收来自网络设备的上行分流策略和上行路由策略，将上行分流策略配置到BP上，以及将上行路由策略配置到UE上；其中，上行分流策略用于控制BP根据UE发送的数据包的源地址进行分流，上行路由策略用于控制UE使用锚定在锚点用户面实体的IP地址或锚定在本地锚点用户面实体的本地IP地址作为数据包的源地址；或
第一中间会话管理实体，还用于将锚定在锚点用户面实体的IP地址和锚定在锚点用户面实体的IP地址对应的上行路由策略发送给第一中间会话管理实体；锚定在锚点用户面实体的IP地址用于使第一中间会话管理实体生成上行分流策略，锚定在锚点用户面实体的IP地址对应的上行路由策略用于使第一中间会话管理实体生成上行路由策略；上行分流策略用于控制BP根据UE发送的数据包的源地址进行分流，上行路由策略用于指示UE使用锚定在锚点用户面实体的IP地址或使用锚定在本地锚点用户面实体的本地IP地址作为源地址发送数据。
在第二方面的一种可能的实现方式中，数据传输模式为ULCL模式，第一中间会话管理实体用于在第一中间会话管理实体的管辖范围内根据UE的位置信息和PDU会话需求信息选择用户面实体具体为：为PDU会话选择本地锚点用户面实体，以及为PDU会话选择ULCL。需要说明的是，会话管理实体还为PDU会话选择锚点用户面实体，锚点用户面实体用于连接DN。ULCL对应两条传输链路：ULCL到锚点用户面实体之间的传输链路，以及ULCL到用户面实体之间的传输链路，ULCL根据来自UE的数据包的五元组和/或应用标识进行分流，五元组表示源IP地址、目的IP地址、源端口号、目的端口号和协议版本，应用标识表示UE上产生数据包的应用程序的标识信息。其中，ULCL根据预先设置的上行转发策略进行分流，上行转发策略表示传输链路标识与五元组和/或应标识之间的对应关系。
在第二方面的一种可能的实现方式中，第一中间会话管理实体，还用于接收网络设备发送的来自网络设备的上行转发策略，将上行转发策略配置到ULCL上。
在第二方面的一种可能的实现方式中，PDU会话需求信息还包括PDU会话类型，PDU会话类型为IP类型，第一中间会话管理实体还用于向会话管理实体发送本地锚点用户面实体的位置信息和本地DN的位置信息中的一种或多种，以及UE的本地IP地址，UE的本地IP地址表示第一中间会话管理实体分配的锚点在本地锚点用户面实体上的IP地址。
第三方面，本申请提供了一种装置，该装置具有实现上述方法中网络设备行为的功能。 所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
一种可能的实现方式中，所述装置包括：选择单元和收发单元。
选择单元，用于根据用户设备UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体。
收发单元，用于向所述第一中间会话管理实体发送所述UE的位置信息和所述PDU会话需求信息；其中，所述UE的位置信息和所述PDU会话需求信息用于选择用户面实体。
另一种可能的实现方式中，所述网络设备包括：收发器、存储器和处理器；其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行第一方面至第一方面各个可能的实现方式中的任意一种会话管理方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的终端设备的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第四方面，本申请提供了一种会话管理方法，包括：
所述网络设备根据本地网络数据名DNN为协议数据单元PDU会话选择第一中间会话管理实体；
所述网络设备向所述第一中间会话管理实体发送用户设备UE的位置信息；其中，所述UE的位置信息用于选择用户面实体。
在一种可能的设计中，所述网络设备根据本地DNN为PDU会话选择第一中间会话管理实体包括：
所述网络设备根据所述本地DNN和所述UE的位置信息选择第一中间会话管理实体；其中，选择支持所述本地DNN指示的本地数据网络DN、及管辖范围包括所述UE的位置信息指示的服务基站的第一中间会话管理实体。
在一种可能的设计中，所述网络设备根据本地DNN为PDU会话选择第一中间会话管理实体包括：
所述网络设备选择支持所述本地DNN指示的本地数据网络DN的中间会话管理实体作为第一中间会话管理实体。
在一种可能的设计中，所述网络设备为会话管理实体，所述方法还包括：
所述网络设备根据来自应用功能的信息确定本地DNN。
在一种可能的设计中，所述方法还包括：
所述网络设备将所述UE的位置信息发送给第一中间会话管理实体；其中，所述UE的位置信息用于指示所述第一中间会话管理实体选择支持UE位置的用户面实体，所述支持UE位置的用户面实体与UE连接的接入网接口。
在一种可能的设计中，所述方法还包括：
所述网络设备将本地DNN发送给第一中间会话管理实体；其中，所述本地DNN用于指示第一中间会话管理实体选择本地锚点用户面实体。
在一种可能的设计中，所述第一中间会话管理实体选择的用户面实体同时支持本地DNN和所述UE位置信息；或
在不存在同时支持本地DNN和所述UE位置信息的用户面实体的情况下，第一中间会话管理实体根据本地DNN选择支持本地DNN的用户面实体作为本地锚点用户面实体，以及根据所述UE位置信息选择支持所述UE位置信息的用户面实体用于与UE所连接的接入网接口，其中，所述本地锚点用户面实体用于与本地DN接口。
在一种可能的设计中，所述网络设备将数据传输模式发送给所述第一中间会话管理实体；其中，所述数据传输模式用于指示所述第一中间会话管理实体确定上行分流规则。
在一种可能的设计中，若数据传输模式为多归属Multihoming，则所述网络设备还将远端UE IP地址发送给所述第一中间会话管理实体；其中，所述远端UE IP用于指示所述第一中间会话管理实体确定上行分流规则。
在一种可能的设计中，若所数据传输模式为上行链路分类器ULCL，则所述网络设备还将应用信息发送给所述第一中间会话管理实体，其中，所述应用信息用于指示第一中间会话管理实体确定上行分流规则；所述应用信息为应用标识或应用对应的五元组中的至少一个。
在一种可能的设计中，所述网络设备将上行分流规则或上行转发规则发送给所述第一中间会话管理实体；其中，所述上行分流规则或上行转发规则用于指示第一中间会话管理实体对所述用户面实体进行配置，从而实现上行数据分流。
在一种可能的设计中，所述网络设备将本地锚点与本地DNN所标识的本地数据网络DN间的路由信息发送给所述第一中间会话管理实体，所述路由信息用于确定用户面实体与本地数据网络DN间的转发路径。
本申请又一方面提供了一种装置，该装置包括：存储器和处理器；其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行第四方面及第四方面中各个可能的实施方式。
第五方面，本申请提供了一种装置，该装置具有实现上述第四方面中各个可能的实施方法中网络设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
一种可能的实现方式中，所述装置包括：选择单元和收发单元。
本申请的又一方面提了供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请的又一方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
为了更清楚地说明本发明实施例或背景技术中的技术方案，下面将对本发明实施例或背景技术中所需要使用的附图进行说明。
图1a是本发明实施例提供的一种网络架构图；
图1b是基于图1a的下一代网络架构图；
图2a是本发明实施例提供的另一种网络架构图；
图2b是基于图2a的下一代网络架构图；
图3是本发明实施例提供的一种会话管理方法的流程示意图；
图4是本发明实施例提供的另一种会话管理方法的流程示意图；
图5是本发明实施例提供的另一种会话管理方法的流程示意图；
图6是本发明实施例提供的另一种会话管理方法的流程示意图；
图7是本发明实施例提供的一种装置的结构示意图；
图8是本发明实施例提供的一种网络设备的结构示意图；
图9是本发明实施例提供的另一种会话管理方法的流程示意图；
图10是本发明实施例提供的另一种会话管理方法的流程示意图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
图1a为本发明实施例涉及的一种通信***架构示意图。该通信***可以是全球移动通信***(Global System for Mobile Communication，GSM),码分多址(Code Division Multiple Access，CDMA)***、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)***，全球微波互联接入(Worldwide Interoperability for Microwave Access，WiMAX)***、长期演进(long term evolution，LTE)***，5G通信***(例如新空口(new radio，NR)***、多种通信技术融合的通信***(例如LTE技术和NR技术融合的通信***)，或者后续演进通信***。图1a所述通信***包括：接入网、接入管理实体、会话管理实体和第一中间会话管理实体，还可以包括策略控制实体。需要说明的是，图1a中的各个网元的形态和数量仅用于举例说明，并不构成对本发明实施例的限制。
其中，接入管理实体分别策略控制实体、接入网和策略控制实体进行互通，会话管理实体分别与策略控制实体、第一中间会话管理实体和锚点用户面实体进行互通，接入网分别与接入管理实体和用户面实体进行互通，第一中间会话管理实体分别与会话管理实体和用户面实体进行互通，锚点用户面实体和数据网络进行互通。接入管理实体与会话管理实体进行互通。
其中，接入管理实体主要负责接入和移动性管理，包括对用户进行认证、切换、位置更新等功能；会话管理实体主要负责会话管理，包括PDU会话的建立、修改释放等功能；策略控制实体主要负责用户测量的管理，包括移动性相关策略和PDU会话相关策略的生成，例如：PDU会话相关策略包括QoS(Quality of Service，服务质量，简称QoS)策略、计费策略等；用户面实体主要负责用户数据的转发，用户面实体分为普通用户面实体和锚点用户面实体，锚点用户面功能为与数据网络连接的用户面功能；数据网络是用户的PDU会话访问的目的地；第一中间会话管理实体主要负责管辖范围内的用户面实体的管理，包括用户面实体的负荷分担、用户面实体的选择、用户面实体上隧道的建立、用户面实体的转发规则的制定和配置。会话管理实体包括用户面隧道的建立、用户面实体的转发规则的配置等。需要说明的是，第一中间会话管理实体可单独部署，也可以集成在会话管理实体中，本申请不作限制。第一中间会话管理实体的管辖范围可由运营商在部署时根据需要确定，例如：第一中间会话管理实体的管辖范围为一个省或一个市或一个跟踪区域或一个数据中心，本发明实施例不作限制。
参见图1b，为5G通信***的架构图。其中，在5G通信***的架构图中，AMF(Access Management Function，接入管理功能，简称AMF)对应图1a中的接入管理实体，RAN对应图1a中的接入网，SMF对应图1a中的会话管理实体，ISMF(Intermediate Session Management Function，中间会话管理实体，简称ISMF)对应图1a中的第一中间会话管理实体，UPF对应图1a中的用户面实体，A-UPF(Anchor User Plane Function，锚点用户面功能，简称A-UPF)对应图1a中的锚点用户面实体，DN(Data Network，数据网络，简称DN)。
其中，如图1b所示，RAN和AMF之间通过N2接口进行互通。RAN和UPF之间通过N3接口进行互通。两个UPF之间通过N9接口进行互通，如图1b中的UPF和A-UPF之间通过N9接口进行互通。ISMF和UPF之间可通过N4接口进行互通，以及SMF和A-UPF之间也通过N4接口进行互通。A-UPF与DN之间通过N6接口进行互通。SMF与PCF之间通过N7接口进行互通。SMF和ISMF之间可通过N16接口进行互通。SMF和AMF之间通过N11接口进行互通。AMF和PCF之间通过N15接口进行互通。
参见图2a，为本发明实施例提供的通信***的另一种结构图，图2a所示的通信***的结构和图1a的通信***的结构的区别仅在于：接入管理实体和会话管理实体之间没有进行互通，接入管理实体与中间会话管理实体进行互通。图2a中各个网元的功能可参照图1a中的描述，此处不再赘述。
图2b为5G通信***的另一种架构图，其中，图2b中的网元和图2a中的网元的对应关系可参照图1b和图1a中的网元的对应关系，此处不再赘述。图2b的通信***的结构示意图和图1b的通信***的结构示意图的区别仅在于：AMF和SMF没有进行互通，AMF和ISMF通过N11接口进行互通。
其中，本申请中的接入网也可以称为基站设备，是一种部署在无线接入网用以提供无线通信功能的设备，包括但不限于：基站(例如：BTS(Base Transceiver Station，BTS)，节点B(NodeB，NB)，演进型基站B(Evolutional Node B，eNB或eNodeB)，NR***中的传输节点或收发点(transmission reception point，TRP或者TP)或者下一代节点B(generation nodeB，gNB)，未来通信网络中的基站或网络设备)、中继站、接入点、车载设备、可穿戴设备，无线保真(Wireless-Fidelity，Wi-Fi)的站点、无线回传节点、小站、微站等等。
在目前的用户面实体的管理方法中，一个PDU会话可能对应多个用户面实体，不同的用户面实体可能位于不同的位置，会话管理实体需要同时管理不同位置的用户面实体，这造成管理过程较为复杂。
鉴于此，基于图1a或图2a的网络架构，本发明实施例提供了一种通信***，包括：网络设备和第一中间会话管理实体。
网络设备用于根据用户设备UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体。本实施例中的网络设备为接入管理实体或会话管理实体。第一中间会话管理实体用于接收来自网络设备的PDU会话需求信息，根据UE的位置信息和PDU会话需求信息选择用户面实体。
可选的，基于图1a或图2a的网络架构，PDU会话需求信息包括数据传输模式和本地 数据网络名DNN。
可选的，基于图1a或图2a的网络架构，通信***还包括锚点用户面实体、本地锚点用户面实体(图中未画出)、服务基站和BP(图中未画出)，服务基站为接入网设备，数据传输模式为多归属Mutilhoming模式；
第一中间会话管理实体用于在第一中间会话管理实体的管辖范围内根据UE的位置信息和PDU会话需求信息选择用户面实体，具体为：为PDU会话选择本地锚点用户面实体，以及为PDU会话选择分支点BP；其中，BP用于对UE发送的数据包进行分流，本地锚点用户面实体与PDU会话需求信息包括的本地DNN指示的本地数据网络DN连接，BP与UE的位置信息指示的服务基站连接。
可选的，基于图1a或图2a的网络架构，第一中间会话管理实体还用于接收来自网络设备的上行分流策略和上行路由策略，将上行分流策略配置到BP上，以及将上行路由策略配置到UE上；其中，上行分流策略用于控制BP根据UE发送的数据包的源地址进行分流，上行路由策略用于控制UE使用锚定在锚点用户面实体的IP地址或锚定在本地锚点用户面实体的本地IP地址作为数据包的源地址；或
第一中间会话管理实体还用于将锚定在锚点用户面实体的IP地址和锚定在锚点用户面实体的IP地址对应的上行路由策略发送给所述第一中间会话管理实体；所述锚定在锚点用户面实体的IP地址用于使所述第一中间会话管理实体生成上行分流策略，所述锚定在锚点用户面实体的IP地址对应的上行路由策略用于使所述第一中间会话管理实体生成所述上行路由策略；所述上行分流策略用于控制所述BP根据所述UE发送的数据包的源地址进行分流，所述上行路由策略用于指示所述UE使用所述锚定在锚点用户面实体的IP地址或使用锚定在本地锚点用户面实体的本地IP地址作为源地址发送数据。
可选的，基于图1a或图2a的网络架构，通信***还包括ULCL和本地DN(图中未画出)，数据传输模式为ULCL模式，第一中间会话管理实体用于在第一中间会话管理实体的管辖范围内根据UE的位置信息和PDU会话需求信息选择用户面实体，具体为：为PDU会话选择本地锚点用户面实体，以及为PDU会话选择上行链路分类器ULCL；其中，ULCL用于对UE发送的数据包的应用标识和/五元组进行分流，本地锚点用户面实体与本地DNN指示的的本地DN连接，ULCL与UE的位置信息指示的服务基站连接。
可选的，基于图1a或图2a的网络架构，第一中间会话管理实体还用于接收来自网络设备的上行转发策略，将上行转发策略配置到ULCL上；其中，上行转发策略用于控制ULCL根据五元组和应用标识中的一种或多种进行分流。
可选的，基于图1a或图2a的网络架构，PDU会话需求信息还包括PDU会话类型，PDU会话类型为IP类型；
第一中间会话管理实体还用于向会话管理实体发送本地锚点用户面实体的位置信息和本地DN的位置信息中的一种或多种，以及UE的本地IP地址。
可选的，基于图1a或图2a的网络架构，PDU会话需求信息包括：会话和业务连续性SSC模式和PDU会话类型中的一种或多种。
可选的，基于图1a或图2a的网络架构，网络设备用于根据UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体具体为：选择同时满足 PDU会话需求信息且管辖范围包括UE的位置信息指示的服务基站的中间会话管理实体作为第一中间会话管理实体。网络设备可以为接入管理实体或会话管理实体。
可选的，基于图1a或图2a的网络架构，网络设备还用于若判断不存在同时满足PDU会话需求且管辖范围包括UE的位置信息指示的服务基站的中间会话管理实体；选择满足PDU会话需求信息的第二中间会话管理实体，以及选择管辖范围包括UE的位置信息指示的服务基站的第三中间会话管理实体。本实施例中的网络设备可以为接入管理实体或会话管理实体。
可选的，基于图1a或图2a的网络架构，网络设备用于根据UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体，具体为选择管辖范围包括UE的位置信息指示的服务基站和满足PDU会话需求信息包括的本地DNN指示的本地DN，以及支持数据传输模式的中间会话管理实体作为第一中间会话管理实体。本实施例中的网络设备可以为接入管理实体或会话管理实体。
可选的，网络设备还用于若判断不存在管辖范围包括UE的位置信息指示的服务基站和本地DNN指示的本地DN，以及支持数据传输模式的中间会话管理实体；选择管辖范围包括UE的位置信息指示的服务基站的第二中间会话管理实体，以及选择管辖范围包括本地DNN指示的本地DN且支持数据传输模式的第三中间会话管理实体。本实施例中的网络设备可以为接入管理实体或会话管理实体。
可选的，基于图1a的网络架构，通信***还包括接入管理实体和策略管理实体，网络设备为会话管理实体；接入管理实体用于选择会话管理实体。网络设备还用于根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；根据PDU会话需求信息为PDU会话选择锚点用户面实体；判断锚点用户面实体和UE的位置信息指示的服务基站不相连。网络设备从策略管理实体获取PDU会话需求信息。
可选的，基于图1a的网络架构，通信***包括接入管理实体，网络设备为会话管理实体。
接入管理实体用于选择会话管理实体。
会话管理实体还用于：根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；判断会话管理实体的管辖范围不包括本地DNN指示的本地DN。
可选的，基于图2a的网络架构，通信***还包括接入管理实体，网络设备为会话管理实体；
接入管理实体用于选择会话管理实体，在会话管理实体的管辖范围不包括UE的位置信息指示的服务基站时，选择第四中间会话管理实体(图2a中未画出)。会话管理实体还用于：根据PDU会话签约信息，或PDU会话策略信息和PDU会话期望信息中的一种或多种和PDU会话签约信息确定PDU会话需求信息，判断第四中间会话管理实体不满足PDU会话需求信息；会话管理实体，还用于将第一中间会话管理实体的标识信息发送给接入管理实体。
可选的，基于图2a的网络架构，通信***还包括会话管理实体，网络设备为接入管理 实体。会话管理实体用于根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；判断接入管理实体选择的第四中间会话管理实体不满足PDU会话需求信息，向接入管理实体发送PDU会话需求信息和重选指示消息，重选指示消息用于指示接入管理实体选择第一中间会话管理实体。接入管理实体，还用于选择会话管理实体，在会话管理实体的管辖范围不包括UE的位置信息指示的服务基站时，选择第四中间会话管理实体；接收来自会话管理实体的PDU会话需求信息和重选指示消息。
可选的，基于图2a的网络架构，通信***还包括会话管理实体，网络设备为接入管理实体。会话管理实体用于根据PDU会话签约信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息，向接入管理实体发送PDU会话需求信息。接入管理实体还用于选择会话管理实体，在会话管理实体的管辖范围不包括UE的位置信息指示的服务基站时，选择第四中间会话管理实体(图2a中未画出)，判断第四中间会话管理实体不满足来自会话管理实体的PDU会话需求信息。
实施本发明实施例，根据UE的位置信息和PDU会话需求信息选择中间会话管理实体，这样可以使靠近UE的中间会话管理实体为PDU会话提供服务，减少数据传输的时延。同时中间会话管理实体根据UE的位置信息和PDU需求信息选择用户面实体，中间会话管理实体只管理指定范围内的用户面实体，不需要管理整个PDU会话的用户面实体，减少管理的复杂性。
请参见图3，为本发明实施例提供的一种会话管理方法的流程示意图，在该实施例中会话管理方法基于图1a的网络架构，网络设备为接入管理实体。该方法包括但不限于以下步骤：
S301、用户设备向接入管理实体发送PDU会话建立请求，接入管理实体接收用户设备发送的PDU会话建立请求。
可选的，用户设备通过所属的服务基站(图中未画出)向接入管理实体发送PDU会话建立请求，PDU会话建立请求用于创建PDU会话，PDU会话建立请求中携带PDU会话期望信息和UE的位置信息，PDU会话期望信息为用户设备请求的PDU会话的相关参数要求，PDU会话期望信息包括本地DNN、网络切片信息、PDU会话类型、SSC模式中的一种或多种，网络切片信息用于描述网络切片的相关属性，例如：网络切片信息包括网络切片类型、网络切片标识和网络切片位置中的一种或多种。其中，PDU会话期望信息为NAS(Non-Access Stratum，非接入层)消息。UE的位置信息表示UE的接入网中的位置，UE的位置信息可以为UE的服务小区的标识或UE的服务基站的标识或UE的跟踪区标识。
S302、接入管理实体选择会话管理实体。
可选的，接入管理实体获取PDU会话建立请求中携带的可解析的参数，接入管理实体可解析的参数包括UE的位置信息、本地DNN和网络切片信息，接入管理实体根据UE的位置信息、本地DNN和网络切片信息中的一种或多种选择会话管理实体。其中，接入管理实体可以将UE的位置信息、本地DNN和网络切片信息中的一种或多种作为输入参数，根据输入参数本地配置的数据库中或者在NRF(Network Function Repository Function，网络功能存储功能，简称NRF)进行查询，得到选择的会话管理实体的标识。
S303、接入管理实体向会话管理实体发送PDU会话建立请求。
S304、会话管理实体接收接入管理实体发送的PDU会话请求消息，选择锚点用户面实体，判断需要选择第一中间会话管理实体。
其中，会话管理实体根据UE的位置信息和PDU会话需求信息选择第一中间会话管理实体。
可选的，会话管理实体解析PDU会话管理请求中携带UE的位置信息和PDU会话期望信息，会话管理实体从UDM(Unified Data Management，统一数据管理，简称UDM)中获取PDU会话签约信息，从策略控制实体中获取PDU会话策略信息，例如：PDU会话策略信息包括QoS(Quality of Service，服务质量，简称QoS)策略和计费策略等。会话管理实体可根据PDU会话签约信息确定PDU会话需求信息；或会话管理实体根据PDU会话期望信息和PDU会话策略信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息。PDU会话需求信息表示网络侧能接受的PDU会话的相关参数要求。PDU会话需求信息包括PDU会话类型、SSC模式、本地DNN和数据传输模式，传输模式模式为Mutilhoming模式或ULCL模式。会话管理实体预先设置有管辖范围，会话管理实体只能管理关系范围内的网元(例如：基站、用户面实体等)，管辖范围可以由运营商在部署时确定，管辖范围的大小不作限制，例如会话管理实体的管辖范围为一个省、一个市或一个数据中心。会话管理实体选择锚点用户面实体，锚点用户面实体用于和数据网络接口。
会话管理实体判断是否需要选择第一中间会话管理实体，判断的方法可以是：
a、会话管理实体判断UE的位置信息指示的服务基站是否与选择的锚点用户面实体相连，若为否，会话管理实体根据UE的位置信息和PDU会话需求信息选择第一中间会话管理实体。
b、在PDU会话需求信息包括本地DNN和传输模式时，会话管理实体判断自身的管辖范围是否包括本地DNN指示的数据网络，若为否，会话管理实体根据UE的位置信息和PDU会话需求信息选择第一中间会话管理实体。
可选的，会话管理实体选择第一中间会话管理实体的方法可以是：
会话管理实体将满足PDU会话需求信息且管辖范围包括UE的位置信息指示的服务基站的中间会话管理实体作为第一中间会话管理实体。
可选的，会话管理实体判断不存在满足PDU会话需求信息且管辖范围包括UE的位置信息指示的服务基站的中间会话管理实体时，选择满足PDU会话需求信息的第二中间会话管理实体，以及选择管辖范围包括UE的位置信息指示的服务基站的第三中间会话管理实体，第二中间会话管理实体和第三中间会话管理实体同时为PDU会话提供服务。
在PDU会话需求信息中包括传输模式和本地DNN时，会话管理实体将支持本地DNN指示的DN，且支持传输模式的中间会话管理实体作为第一中间会话管理实体。
可选的，会话管理实体判断不存在管辖范围包括UE的位置信息指示的服务基站和本地DNN指示的DN，以及支持传输模式的中间会话管理实体，会话管理实体选择管辖范围包括UE的位置信息指示的服务基站的的第二中间会话管理实体，以及选择覆盖范围包括本地DNN指示的本地DN且支持传输模式的第三中间会话管理实体，第二中间会话管理实体和第三中间会话管理实体同时为PDU会话提供服务。
S305、会话管理实体向第一中间会话管理实体发送PDU会话建立请求。
其中，PDU会话建立请求中携带UE的位置信息和PDU会话需求信息。会话管理实体可通过PDU会话建立请求将UE的位置信息和PDU会话需求信息发送给第一中间会话管理实体。
可选的，当数据传输模式为Mutilhoming模式时，会话管理实体将上行分流策略和上行路由策略发送给所述第一中间会话管理实体，上行分流策略用于控制所述UE锚定的分支点BP根据UE发送的数据包的源地址进行分流，上行路由策略用于控制UE使用锚定在锚点用户面实体的IP地址或锚定在本地锚点用户面实体的本地IP地址作为数据包的源地址。
可选的，数据传输模式为Mutilhoming模式，所述会话管理实体将锚定在锚点用户面实体的IP地址和锚定在锚点用户面实体的IP地址对应的上行路由策略发送给所述第一中间会话管理实体；所述锚定在锚点用户面实体的IP地址用于使所述第一中间会话管理实体生成上行分流策略，所述上行路由策略用于使所述第一中间会话管理实体生成所述上行路由策略；所述上行路由策略用于指示所述UE使用所述锚定在锚点用户面实体的IP地址或使用锚定在本地锚点用户面实体的本地IP地址作为源地址发送数据。
可选的，所述数据传输模式为上行链路分类器ULCL模式，所述会话管理实体将上行转发策略发送给所述第一中间会话管理实体，上行转发策略用于控制所述UE锚定的上行分类器ULCL根据所述UE发送的数据包的五元组和应用标识中的一种或多种进行转发。
S306、第一中间会话管理实体接收来自会话管理实体的PDU会话建立请求，第一中间会话管理实体选择BP和本地锚点用户面实体。S306为可选的步骤。
可选的，本实施例以传输模式为Mutilhoming模式进行举例，第一中间会话管理实体解析PDU会话建立请求中的UE的位置信息和PDU会话需求信息。第一中间会话管理实体为所述PDU会话选择本地锚点用户面实体，以及为PDU会话选择分支点BP；其中，BP用于对UE发送的数据包进行分流，本地锚点用户面实体与PDU会话需求信息包括的本地DNN指示的本地数据网络DN连接，BP与UE的位置信息指示的服务基站连接。
可选的，传输模式为ULCL模式时，第一中间会话管理实体为PDU会话选择本地锚点用户面实体，以及为PDU会话选择上行链路分类器ULCL；其中，ULCL用于对UE发送的数据包的应用标识和/或五元组进行分流，本地锚点用户面实体与本地DNN指示的的本地DN连接，ULCL与所述UE的位置信息指示的服务基站连接。
可选的，在第一中间会话管理实体的管辖范围包括UE的服务基站时，本地锚点用户面实体、与服务基站相连的用户面实体和BP/ULCL可以为同一个用户面实体。
S307、第一中间会话管理实体向选择的BP发送N4消息。S307为可选的步骤。
其中，本步骤中的N4消息表示通过N4接口传输的消息，第一中间会话管理实体分配N3上行隧道信息和N9下行隧道信息，N3上行隧道信息表示BP和用户设备的服务基站之间的隧道的标识信息，N9下行隧道信息表示BP和本地锚点用户面实体之间的隧道的标识信息，以及BP和锚点用户面实体之间的隧道的标识信息。第一中间会话管理实体通过N4消息将N3上行隧道信息和N9下行隧道信息发送给BP，BP接收来自第一中间会话管理实体的N3上行隧道信息和N9下行隧道信息，在本地路径上创建N3隧道和N9隧道。
需要说明的是，在传输模式为ULCL模式时，第一中间会话管理实体向ULCL发送N4消息，N4消息包括N3上行隧道信息和N9下行隧道信息，ULCL接收N4消息，创建N3隧道和N9隧道。
S308、第一中间会话管理实体向选择的本地锚点用户面实体发送N4消息。S308为可选的步骤。
其中，第一中间会话管理实体为本地锚点用户面实体分配本地IP地址和N9上下行隧道信息，第一中间会话管理实体通过N4消息向本地锚点用户面实体发送本地IP地址和N9上下行隧道信息，锚点用户面实体接收N4消息，创建本地路径的N9隧道。
S309、第一中间会话管理实体向会话管理实体发送响应消息。S309为可选的步骤。
其中，响应消息中可携带BP的N9下行隧道信息。另外，在PDU会话的会话类型为IP类型时，第一中间会话管理实体还可以将本地锚点用户面实体的位置信息和/或本地IP地址发送给会话管理实体。
S310、会话管理实体向锚点用户面实体发送N4消息。S310为可选的步骤。
其中，会话管理实体为PDU会话分配IP地址和锚点用户面实体的N9上下行隧道信息，通过N4消息向锚点用户面实体发送分配的IP地址和N9上下行隧道信息，锚点用户面实体接收N4消息，创建与BP之间的N9隧道。
S311、分配PDU会话的无线资源。S311为可选的步骤。
其中。会话管理实体请求接入网(图中为画出)创建用户面隧道以及为PDU会话分配空口资源，并将PDU会话的QoS策略配置到接入接入网，接入网将N3下行隧道信息发送给会话管理实体。
S312、会话管理实体向第一中间会话管理实体发送PDU会话更新请求。S312为可选的步骤。
其中，会话管理实体将N3下行隧道信息发送给第一中间会话管理实体。其中，在PDU会话的会话类型为IP类型时，会话管理实体还可以将会话管理实体分配的IP地址发送给第一中间会话管理实体。
S313、第一中间会话管理实体向BP发送PDU会话更新请求。S313为可选的步骤。
其中，PDU会话更新请求包括N3下行隧道信息、锚点用户面实体的N9上行隧道信息、本地锚点用户面实体的N9上行隧道信息。BP接收PDU会话更新请求，更新PDU会话。若需要更新上行分流策略，该PDU会话更新请求中还包括更新的上行分流策略。
S314、第一中间会话管理实体向会话管理实体发送响应消息。其中，响应消息表示完成PDU会话的更新。S314为可选的步骤。
S315、会话管理实体接收来自第一中间会话管理实体的响应消息，向接入管理实体发送响应消息。S315为可选的步骤。
S316、第一中间会话管理实体通过本地锚点用户面实体给用户设备发送路由通告。S316为可选的步骤。
其中，本步骤中传输模式为Mutilhoming模式，路由通告中携带上行路由策略和会话管理实体分配的IP地址，上行路由策略用于控制UE在发送数据包时选择会话管理实体分配的IP地址或第一中间会话管理实体分配的本地IP地址作为源地址。
需要说明的是，在用户面实体接收到下行数据时，用户面实体可以是任意类型的用户面实体。用户面实体判断没有下行N3隧道信息，用户面实体给第一中间会话管理实体发送下行数据通知，第一中间会话管理实体将接收到的下行数据通知转发给会话管理实体，会话管理实体触发寻呼流程。会话管理实体接收到UE的服务基站发送的下行N3隧道信息后，向第一中间会话管理实体发送PDU会话更新请求，第一中间会话管理实体接收PDU会话更新请求，从PDU会话更新请求中获知下行N3隧道信息，第一中间会话管理实体将下行N3隧道信息通知给用户面实体，用户面实体接收下行N3隧道信息，然后进行上行数据的发送。
实施本发明的实施例，会话管理实体和中间会话管理实体只负责管理管辖范围内的用户面实体，不需要管理整个PDU会话中所有的用户面实体，减少了和用户面实体中间的消息的数量以及减轻了工作负荷。
参见图4，为本发明实施例提供的一种会话管理方法的流程示意图，在本实施例为架构1a的切换流程的说明，在切换之前，UE的源接入网为服务基站(图中未画出)、源中间会话管理实体(第一中间会话管理实体)、源用户面实体和锚点用户面实体为PDU会话提供服务。在切换发生时，所述方法包括但不限于以下步骤：
S401、目标接入网通过接入管理实体向会话管理实体发送路径切换请求。S401为可选的步骤。
其中，在UE由源接入网切换到目标接入网后，目标接入网通过接入管理实体向会话管理实体发送路径切换请求，路径切换请求中携带UE的位置信息，UE的位置信息可以为UE的驻留的基站的标识或驻留的小区的标识。
S402、会话管理实体接收路径切换请求，根据UE的位置信息判断UE不在第一中间会话管理实体的管辖范围内，会话管理实体选择目标中间会话管理实体。
其中，会话管理实体保存有PDU会话的PDU会话需求信息，会话管理实体根据UE的位置信息和PDU会话需求信息选择目标中间会话管理实体，具体的选择过程可参照图3的S304的描述，此处不再赘述。
S403、会话管理实体向目标中间会话管理实体发送PDU会话建立请求。
其中，PDU会话建立请求中携带UE的位置信息和PDU会话需求信息。
S404、目标中间会话管理实体接收PDU会话建立请求，根据UE的位置信息和PDU会话需求信息选择目标用户面实体。S404为可选的步骤。其中，目标中间会话管理实体根据UE的位置信息和PDU会话需求信息选择目标用户面实体的具体过程可参照图3中S306的描述，此处不再赘述。
需要说明的是，目标中间会话管理实体向选择的目标用户面实体发送N4消息，目标用户面实体接收来自目标中间会话管理实体的N4消息，目标用户面实体创建与锚点用户面实体之间的N9隧道，以及创建与目标接入网之间的N3隧道。目标中间会话管理实体向会话管理实体发送响应消息，响应消息中携带上述创建的N3隧道的标识信息和N9隧道的标识信息，会话管理实体接收来自中间会话管理实体发送的N3隧道的标识信息和N9隧道的标识信息，更新锚点用户面实体的N9隧道的标识信息。会话管理实体向接入管理实体发送切换响应消息，接入管理实体接收来自会话管理实体的切换响应消息，获知完成隧道 的更新过程。
实施本发明的实施例，UE的位置发生更新时，会话管理实体选择靠近UE的中间会话管理实体和用户面实体为UE提供服务，在数据传输时减少时延，同时会话管理实体和中间会话管理实体只负责管理管辖范围内的用户面实体，不需要管理整个PDU会话中所有的用户面实体，减少了和用户面实体中间的消息的数量以及减轻了工作负荷。
参见图5，为本发明实施例提供的一种会话管理方法的流程示意图，本发明实施例适用于图2a的架构，所述方法包括但不限于：
S501、用户设备向接入管理实体发送PDU会话建立请求。S501为可选的步骤。
其中，用户设备通过所属的服务基站(图中未画出)向接入管理实体发送PDU会话建立请求，PDU会话建立请求用于创建PDU会话，PDU会话建立请求中携带PDU会话期望信息和UE的位置信息，PDU会话期望信息为用户设备请求的PDU会话的相关参数要求，PDU会话期望信息包括本地DNN、网络切片信息、PDU会话类型、SSC模式中的一种或多种，网络切片信息用于描述网络切片的相关属性，例如：网络切片信息包括网络切片类型、网络切片标识和网络切片位置中的一种或多种。其中，PDU会话期望信息为NAS(Non-Access Stratum，非接入层)消息。UE的位置信息表示UE的接入网中的位置，UE的位置信息可以为UE的服务小区的标识或UE的服务基站的标识。
S502、接入管理实体接收来自UE的PDU会话建立请求，选择会话管理实体，判断需要选择第四会话管理实体。S502为可选的步骤。
其中，接入管理实体获取PDU会话建立请求中携带的可解析的参数，接入管理实体可解析的参数包括UE的位置信息、本地DNN和网络切片信息，接入管理实体根据UE的位置信息、本地DNN和网络切片信息中的一种或多种选择会话管理实体。其中，接入管理实体可以将UE的位置信息、本地DNN和网络切片信息中的一种或多种作为输入参数，根据输入参数本地配置的数据库中或者在NRF(Network Function Repository Function，网络功能存储功能，简称NRF)进行查询，得到选择的会话管理实体的标识。接入管理实体判断选择的会话管理实体的管辖范围是否包括UE的位置信息指示的服务基站，若为否，接入管理实体判断需要初选一个第四中间会话管理实体，接入管理实体选择第四中间会话管理实体的方法可以是：根据UE的位置信息、本地DNN、网络切片信息中的一种或多种选择第四中间会话管理实体。
S503、接入管理实体向第四中间会话管理实体发送PDU会话建立请求。其中，PDU会话建立请求中还携带会话管理实体的标识信息。S503为可选的步骤。第一中间会话管理实体的标识信息可以为地址信息、位置信息或ID(Identity，身份信息，简称ID)。
S504、第四中间会话管理实体接收来自接入管理实体的PDU会话建立请求，选择用户面实体。S504为可选的步骤。
其中，第四中间会话管理实体获取PDU会话请求消息中携带的PDU会话期望信息、UE的位置信息和会话管理实体的标识信息，第四中间会话管理实体根据PDU会话期望信息和UE的位置信息选择用户面实体(图中未画出)。选择用户面实体的方法可以是：第四中间会话管理实体在管辖范围内选择用户面实体，选择的用户面实体和UE的服务基站相连接。第四中间会话管理实体向选择的用户面实体发送N4消息，用户面实体接收N4消息， 创建N3下行隧道和N9上行隧道。
S505、第四中间会话管理实体向会话管理实体发送PDU会话建立请求。S505为可选的步骤。
S506、会话管理实体接收来自第四中间会话管理实体的PDU会话建立请求，选择锚点用户面实体，判断需要选择第一中间会话管理实体。
其中，会话管理实体从UDM获取PDU会话签约信息，从策略控制实体获取PDU会话策略信息。会话管理实体可根据PDU会话签约信息确定PDU会话需求信息；或会话管理实体根据PDU会话期望信息和PDU会话策略信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息。PDU会话需求信息表示网络侧能接受的PDU会话的相关参数要求。PDU会话需求信息包括PDU会话类型、SSC模式、本地DNN和数据传输模式，传输模式模式为Mutilhoming模式或ULCL模式。会话管理实体预先设置有管辖范围，会话管理实体只能管理关系范围内的网元(例如：基站、用户面实体等)，管辖范围可以由运营商在部署时确定，管辖范围的大小不作限制，例如会话管理实体的管辖范围为一个省、一个市或一个数据中心。会话管理实体选择锚点用户面实体，锚点用户面实体用于和数据网络接口。
其中，会话管理实体判断第四中间会话管理实体是否满足PDU会话需求信息，若为否，会话管理实体根据UE的位置信息和PDU会话需求信息选择第一中间会话管理实体，判断是否选择第一中间会话管理实体和选择第一中间会话管理实体的方法可参照图3中的S304的描述，此处不再赘述。
会话管理实体选择第一中间会话管理实体后，将UE的位置信息和PDU会话需求信息通知给第一中间会话管理实体。可选的，会话管理实体向第一中间会话管理实体通知UE的位置信息和PDU会话需求信息可以为S507至S509的过程。
S507、会话管理实体向响应消息发送给第四中间会话管理实体。
其中，由于在S506重选第一中间会话实体，响应消息携带PDU会话需求信息、UE的位置信息和第一中间会话管理实体的标识信息。第一中间会话管理实体的标识信息可以为地址信息、位置信息或ID(Identity，身份信息，简称ID)。
S508、第四中间会话管理实体接收来自会话管理实体的响应消息，向接入管理实体发送响应消息。
其中，第四中间会话管理实体删除本地会话，响应消息中携带第一中间会话管理实体的标识信息和PDU会话需求信息。
S509、接入管理实体接收来自第四中间会话管理实体的响应消息，向第一中间会话管理实体发送PDU会话建立请求。其中PDU会话建立请求中携带UE的位置信息和PDU会话需求信息。
S510、第一中间会话管理实体接收来自接入管理实体的PDU会话建立请求，获取UE的位置信息和PDU会话需求信息，根据UE的位置信息和PDU会话需求信息选择用户面实体，选择用户面实体的过程可参照图3中S306的描述，此处不再赘述。
其中，第一中间会话管理实体向选择的用户面实体发送N4消息，用户面实体接收N4消息，根据N4消息的指示创建本地会话。第一中间会话管理实体向会话管理实体发送PDU 会话建立请求。会话管理实体将N4消息发送给锚点用户面实体，锚点用户面实体接收来自会话管理实体的N4消息，根据N4消息的指示创建会话。
可选的，在S509之后，第一中间会话管理实体发送PDU会话建立请求给会话管理实体，。
会话管理实体向选择的锚点用户面实体发送N4消息，锚点用户面实体接收该N4消息，创建本地会话，锚点用户面实体成功创建本地会话后，向会话管理实体发送响应消息，响应消息表示本地会话成功创建。会话管理实体接收该响应消息，将响应消息给第一中间会话管理实体，第一中间会话管理实体接收来自会话管理实体的响应消息，第一中间会话管理实体将接收到的响应消息发送给接入管理实体，接入管理实体接收来自第一中间会话管理实体的响应消息。
可选的，会话管理实体判断需要选择第一中间会话管理实体时，向接入管理实体发送重选指示消息和PDU会话需求信息，接入管理实体接收来自会话管理实体的重选指示消息和PDU会话需求信息，根据UE的位置信息和PDU会话需求信息选择第一中间会话管理实体，选择的方法可参照图3的S304的描述，此处不再赘述。
在另一种可选的实施方式中，接入管理实体接收来自会话管理实体的PDU会话需求信息，接入管理实体判断需要选择第一中间会话管理实体时，根据UE的位置信息和PDU会话需求信息选择第一中间会话管理实体。
可选的，会话管理实体判断不需要选择第一中间会话管理实体时，会话管理实体给选择的锚点用户面实体发送N4消息，锚点用户面实体接收N4消息，创建N3隧道和N9隧道。会话管理实体向第四中间会话管理实体发送响应消息，响应消息中携带PDU会话需求信息和UE的位置信息，第四中间会话管理实体接收来自会话管理实体的响应消息，获取PDU会话需求信息，第四中间会话管理实体判断S504选择的用户面实体是否满足PDU会话需求信息，若为否，第四中间会话管理实体根据UE的位置信息和PDU会话需求信息重选用户面实体，选择的方法可参照图3的S306的描述，此处不再赘述。
实施本发明的实施例，会话管理实体和中间会话管理实体只负责管理管辖范围内的用户面实体，不需要管理整个PDU会话中所有的用户面实体，减少了和用户面实体中间的消息的数量以及减轻了工作负荷。
参见图6，为本发明实施例提供的一种会话管理方法的流程示意图，在本实施例为架构2a的切换流程的说明，在切换之前，UE的源接入网为服务基站(图中未画出)、源中间会话管理实体(第一中间会话管理实体)、源用户面实体和锚点用户面实体为PDU会话提供服务。在切换发生时，所述方法包括但不限于以下步骤：
S601、目标接入网向接入管理实体发送路径切换请求。其中，路径切换请求中携带UE的位置信息。
S602、接入管理实体接收来自目标接入网的路径切换请求，判断UE不在第一中间会话管理实体的管辖范围内，选择目标中间会话管理实体。选择目标中间会话管理实体的方法可参照图4中S402的描述。
S603、接入管理实体向目标中间会话管理实体发送会话建立请求。
S604、目标中间会话管理实体接收来自接入管理实体的会话建立请求，选择目标用户 面实体。选择目标用户面实体的方法可参照图4中S404的描述。S604为可选的步骤。
可选的，接入管理实体接收来自会话管理实体发送的新PDU会话需求信息，会话管理实体将新PDU会话需求信息通过第一中间会话管理实体发送给接入管理实体，接入管理实体判断第一中间会话管理实体是否满足新PDU会话需求信息，若为否，接入管理实体选择目标中间会话管理实体，选择目标中间会话管理实体的方法可参照图4中S402的描述。
实施本发明的实施例，接入管理实体选择靠近UE的中间会话管理实体和用户面实体为UE提供服务，在数据传输时减少时延，同时会话管理实体和中间会话管理实体只负责管理管辖范围内的用户面实体，不需要管理整个PDU会话中所有的用户面实体，减少了和用户面实体中间的消息的数量以及减轻了工作负荷。
请参见图9，为本发明实施例提供的一种会话管理方法的流程示意图，在该实施例中会话管理方法基于图1a的网络架构，该实施例假设UE已经建立了一个PDU会话，该PDU会话由会话管理实体服务，且该PDU会话的用户面由锚点用户面实体提供服务。该方法包括但不限于以下步骤：
S901、会话管理实体选择第一中间会话管理实体。
具体的，PDU会话需求信息包括PDU会话类型、SSC模式、本地DNN和数据传输模式中的一个或多个，数据传输模式为Mutilhoming模式或ULCL模式。
其中，会话管理实体根据来自应用功能的信息和UE的位置信息确定PDU会话需求信息中的本地DNN，来自应用功能的信息包括应用的部属信息，例如：应用部署在哪些本地DN，该信息使用本地DNN标识。会话管理实体根据UE的位置和应用所部属的一个或多个本地DN，选择靠近UE位置的本地DN，将所选择的本地DN对应的本地DNN标识作为PDU会话需求信息中的本地DNN。需要说明的是，PDU会话需求信息中的其他信息，例如数据传输模式、PDU会话类型等信息等仍然采用S304中的方法确定，在此不再赘述。
其中，可选的，会话管理实体选择第一中间会话管理实体需要判断是否需要选择第一中间会话管理实体，会话管理实体判断是否需要选择第一中间会话管理实体，判断的方法可以是：
会话管理实体根据PDU会话需求信息判断，连接到该本地DN的UPF不由会话管理实体控制时，会话管理实体根据PDU会话需求信息选择(或者说：获取)第一中间会话管理实体。可选地，会话管理实体根据UE的位置信息和PDU会话需求信息获取第一中间会话管理实体。
可选的，会话管理实体选择第一中间会话管理实体的方法可以是：
a、会话管理实体将满足PDU会话需求信息的中间会话管理实体作为第一中间会话管理实体。
b、会话管理实体结合UE位置信息和PDU会话需求信息选择第一中间会话管理实体，会话管理实体将满足PDU会话需求信息且管辖范围包括UE的位置信息指示的服务基站的中间会话管理实体作为第一中间会话管理实体。
c、在PDU会话需求信息中包括传输模式和本地DNN时，会话管理实体将支持本地 DNN指示的DN，且支持传输模式的中间会话管理实体作为第一中间会话管理实体。
d、在PDU会话需求信息中只包括本地DNN时，会话管理实体将支持本地DNN指示的DN的中间会话管理实体作为第一中间会话管理实体。
e、在PDU会话需求信息中只包括传输模式时，会话管理实体将支持传输模式的中间会话管理实体作为第一中间会话管理实体。
可选地，会话管理实体结合UE位置信息和PDU会话需求信息，且PDU会话需求信息包括本地DNN和传输模式时，会话管理实体选择第一中间会话管理实体，例如：会话管理实体将管辖范围包括UE的位置信息指示的服务基站、支持本地DNN指示的DN，且支持所述传输模式的中间会话管理实体作为第一中间会话管理实体。根据其他组合方式选择第一中间会话管理实体的方法与上述方法相似，本发明不再赘述。
S902、会话管理实体向第一中间会话管理实体发送PDU会话建立请求，第一中间会话管理实体接收来自会话管理实体的PDU会话建立请求。
其中，PDU会话建立请求中携带UE的位置信息。会话管理实体可通过PDU会话建立请求将UE的位置信息发送给第一中间会话管理实体。会话管理实体根据UE的位置信息选择用户面实体，例如BP、本地锚点用户面实体等。
可选地，PDU会话建立请求中还携带数据传输模式，数据传输模式为Multihoming或ULCL模式。
可选的，当数据传输模式为Mutilhoming模式时，会话管理实体将上行分流策略发送给所述第一中间会话管理实体，上行分流策略用于控制所述UE锚定的分支点BP根据UE发送的数据包的源地址进行分流。
可选的，当数据传输模式为Mutilhoming模式时，会话管理实体将锚定在锚点用户面实体的UE IP地址(远端UE IP地址)发送给第一中间会话管理实体；锚定在锚点用户面实体的UE IP地址(远端UE IP地址)用于使第一中间会话管理实体生成上行分流策略，上行分流策略用于Branching Point UPF根据源地址转发收到的上行数据包。
可选的，当数据传输模式为上行链路分类器ULCL模式时，会话管理实体将上行转发策略发送给第一中间会话管理实体，上行转发策略用于控制UE锚定的上行分类器ULCL根据所述UE发送的数据包的五元组和应用标识中的一种或多种进行转发。
可选的，当数据传输模式为上行链路分类器ULCL模式时，会话管理实体将接入本地DN的应用信息发送给第一中间会话管理实体，应用信息为应用标识、应用对应的五元组中的至少一种，应用信息用于指示第一中间会话管理实体根据应用信息确定上行转发策略，上行转发策略用于控制所述UE锚定的上行分类器ULCL根据UE发送的数据包的五元组和应用标识中的一种或多种进行转发。
可选的，会话管理实体将从本地锚点用户面实体与本地DNN所标识的本地DN间的路由信息发送给第一中间会话管理实体，路由信息用于确定本地锚点用户面实体与本地DN间的转发路径，第一中间会话管理实体根据路由信息确定本地锚点用户面实体面向本地DN的接口上的转发规则。
可选的，会话管理实体还将PDU会话类型、本地DNN中的一个或多个发送给第一中间会话管理实体，用于第一中间会话管理实体根据PDU会话类型和/或本地DNN选择本地 用户面实体。
S903、第一中间会话管理实体选择本地用户面实体。
可选的，当传输模式为Mutilhoming模式时，第一中间会话管理实体解析PDU会话建立请求中的UE的位置信息。第一中间会话管理实体为所述PDU会话选择本地锚点用户面实体，以及为PDU会话选择BP；其中，BP用于对UE发送的数据包进行分流，本地锚点用户面实体与本地DNN指示的本地数据网络DN连接，BP与UE的位置信息指示的服务基站连接。
可选的，当传输模式为ULCL模式时，第一中间会话管理实体为PDU会话选择本地锚点用户面实体，以及为PDU会话选择上行链路分类器ULCL；其中，ULCL用于对UE发送的数据包的应用标识和/或五元组进行分流，本地锚点用户面实体与本地DNN指示的的本地DN连接，ULCL与所述UE的位置信息指示的服务基站连接。
可选的，在本地锚点用户面实体的管辖范围包括UE的服务基站时，本地锚点用户面实体、与服务基站相连的用户面实体BP/ULCL可以为同一个用户面实体。
第一中间会话管理实体根据UE的位置信息选择BP或ULCL：
第一中间会话管理实体选择与UE的位置所指示的服务基站连接的用户面实体作为BP或ULCL。
可选地，第一中间会话管理实体接收来自会话管理实体的PDU会话建立请求中包括传输模式、本地DNN、PDU会话类型的一种或多种时，第一中间会话管理实体还可根据传输模式、本地DNN、PDU会话类型的一种或多种选择本地会话锚点用户面实体：
可选地，第一中间会话管理实体根据数据传输模式选择本地会话锚点用户面实体，第一中间会话管理实体选择支持会话管理实体所指示的数据传输模式的用户面实体作为本地会话锚点用户面实体。
可选地，第一中间会话管理实体根据本地DNN选择本地会话锚点用户面实体，第一中间会话管理实体选择支持会话管理实体所指示的本地DNN的用户面实体作为本地会话锚点用户面实体。
可选地，第一中间会话管理实体根据PDU会话的类型选择本地会话锚点用户面实体，第一中间会话管理实体选择支持会话管理实体所指示的PDU会话的类型的用户面实体作为本地会话锚点用户面实体。
可选地，第一中间会话管理实体还可能根据数据传输模式、本地DNN、PDU会话类型中的任意两个或三个的组合选择本地会话锚点用户面实体，例如：第一中间会话管理实体根据传输模式和本地DNN选择本地会话锚点用户面实体，此时，第一中间会话管理实体选择支持会话管理实体所指示的数据传输模式和支持所述会话管理实体所指示的本地DNN的用户面实体作为本地会话锚点用户面实体。其他组合的选择方法可依次类推，在此不再赘述。可选地，若根据上述选择方法选出的本地会话锚点用户面实体支持与UE的位置所指示的服务基站连接，则可选择该用户面实体作为BP/ULCL和本地会话锚点用户面实体的合一体。
S904、第一中间会话管理实体向选择的BP或ULCL发送N4消息，BP/ULCL接收来自。该步骤同S307，此处不再赘述。
S905、第一中间会话管理实体向选择的本地锚点用户面实体发送N4消息。该步骤同S308，此处不再赘述。
S906、第一中间会话管理实体向会话管理实体发送响应消息，会话管理实体接收来自第一中间会话管理实体的响应消息。
其中，响应消息中可携带BP或ULCL的N9下行隧道信息。另外，当数据传输模式为Multihoming时，第一中间会话管理实体还可以将本地UE IP地址发送给会话管理实体。
S907、会话管理实体向锚点用户面实体发送N4消息，锚点用户面实体接收来自会话管理实体的N4消息。该步骤同S310。
S908、分配PDU会话的无线资源。该步骤同S311。
S909、会话管理实体向第一中间会话管理实体发送PDU会话更新请求，第一中间会话管理实体接收来自会话管理实体的PDU会话更新请求。该步骤同S312。
S910、第一中间会话管理实体向BP/UCLC发送PDU会话更新请求，BP/ULCL接收来自第一中间会话管理实体的PDU会话更新请求。该步骤同S313。
S911、第一中间会话管理实体向会话管理实体发送响应消息，会话管理实体接收来自第一中间会话管理实体的响应消息。其中，响应消息表示完成PDU会话的更新。该步骤同S314。
S912、第一中间会话管理实体通过本地锚点用户面实体给用户设备发送路由通告。
其中，本步骤中传输模式为Mutilhoming模式，路由通告中携带上行路由策略和第一中间会话管理实体分配的本地UE IP地址，上行路由策略用于控制UE在发送数据包时选择会话管理实体分配的远端UE IP地址或第一中间会话管理实体分配的本地UE IP地址作为源地址。可选地，会话管理实体根据需要也可以给用户设备发送路由通告，该路由通告用于指示UE选择远端UE IP地址或远端UE IP地址的规则。
参见图10，为本发明实施例提供的一种会话管理方法的流程示意图，在本实施例为架构1a的切换流程的说明，在切换之前，UE的源接入网为服务基站(图中未画出)、源中间会话管理实体(第一中间会话管理实体)、源用户面实体和锚点用户面实体为PDU会话提供服务。在切换发生时，所述方法包括但不限于以下步骤：
S1001、目标接入网通过接入管理实体向会话管理实体发送路径切换请求，会话管理实体接收来自目标接入网的路径切换请求。同S401的描述，此处不再赘述。
S1002、会话管理实体选择目标中间会话管理实体。
其中，会话管理实体根据UE的位置信息判断UE可以通过目标本地DN更方便地访问应用(如更近或更快的访问应用)，会话管理实体将目标本地DN对应的目标本地DNN作为PDU会话需求信息中的本地DNN，会话管理实体选择目标中间会话管理实体，具体的选择过程可参照图9的S901的描述，此处不再赘述。
S1003、会话管理实体向目标中间会话管理实体发送PDU会话建立请求，目标中间会话管理实体接收来自会话管理实体的。同S902的描述，此处不再赘述。
S1004、目标中间会话管理实体选择目标用户面实体。同S903的描述，此处不再赘述。
需要说明的是，目标中间会话管理实体向选择的目标用户面实体发送N4消息，目标 用户面实体接收来自目标中间会话管理实体的N4消息，目标用户面实体创建与锚点用户面实体之间的N9隧道，以及创建与目标接入网之间的N3隧道。目标中间会话管理实体向会话管理实体发送响应消息，响应消息中携带上述创建的N3隧道的标识信息和N9隧道的标识信息，会话管理实体接收来自中间会话管理实体发送的N3隧道的标识信息和N9隧道的标识信息，更新锚点用户面实体的N9隧道的标识信息。会话管理实体向接入管理实体发送切换响应消息，接入管理实体接收来自会话管理实体的切换响应消息，获知完成隧道的更新过程。
实施本发明的实施例，UE的位置发生更新时，会话管理实体选择靠近UE的中间会话管理实体和用户面实体为UE提供服务，在数据传输时减少时延，同时会话管理实体和中间会话管理实体只负责管理管辖范围内的用户面实体，不需要管理整个PDU会话中所有的用户面实体，减少了和用户面实体中间的消息的数量以及减轻了工作负荷。
需要说明的是，在一种可能的实施方式中，图7所示的装置7可以实现图3-7所示实施例的接入管理实体或会话管理实体，其中，装置7包括：选择单元701和收发单元702。
选择单元701，用于根据用户设备UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体。
收发单元702，用于向所述第一中间会话管理实体发送所述UE的位置信息和所述PDU会话需求信息；其中，所述UE的位置信息和所述PDU会话需求信息用于选择用户面实体。
可选的，所述PDU会话需求信息包括：会话和业务连续性SSC模式和PDU会话类型中的一种或多种。
可选的，选择单元701，用于根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体包括：选择同时满足所述PDU会话需求信息且管辖范围包括所述UE的位置信息指示的服务基站的中间会话管理实体作为所述第一中间会话管理实体。
可选的，装置7还包括判断单元；
判断单元，用于若所述网络设备判断不存在同时满足所述PDU会话需求且管辖范围包括所述UE的位置信息指示的服务基站的中间会话管理实体；
选择单元701，还用于选择满足所述PDU会话需求信息的第二中间会话管理实体，以及选择管辖范围包括所述UE的位置信息指示的服务基站的第三中间会话管理实体。
可选的，所述PDU会话需求信息包括数据传输模式和本地数据网络名DNN。
可选的，选择单元701，用于根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体包括：
选择同时满足管辖范围包括所述UE的位置信息指示的服务基站和所述PDU会话需求信息包括的所述本地DNN指示的本地数据网络DN，以及支持所述PDU会话需求信息中的所述数据传输模式的中间会话管理实体作为所述第一中间会话管理实体。
可选的，装置7还包括：判断单元；
判断单元，还用于若所述网络设备判断不存在管辖范围包括所述UE的位置信息指示的服务基站和所述本地DNN指示的本地DN，以及支持所述PDU会话需求信息中包括的 数据传输模式的中间会话管理实体；
选择单元701，还用于选择管辖范围包括所述UE的位置信息指示的服务基站的第二中间会话管理实体，以及选择管辖范围包括所述PDU会话需求信息中包括的本地DNN指示的本地DN且支持所述PDU会话需求信息中包括的数据传输模式的第三中间会话管理实体。
可选的，所述数据传输模式为多归属Mutilhoming模式，收发单元701还用于：
将上行分流策略和上行路由策略发送给所述第一中间会话管理实体；其中，所述上行分流策略用于控制所述UE锚定的分支点BP根据所述UE发送的数据包的源地址进行分流，所述上行路由策略用于控制所述UE使用锚定在锚点用户面实体的IP地址或锚定在本地锚点用户面实体的本地IP地址作为数据包的源地址；或
将锚定在锚点用户面实体的IP地址和锚定在锚点用户面实体的IP地址对应的上行路由策略发送给第一中间会话管理实体；锚定在锚点用户面实体的IP地址用于使第一中间会话管理实体生成上行分流策略，锚定在锚点用户面实体的IP地址对应的上行路由策略用于使第一中间会话管理实体生成上行路由策略；上行分流策略用于控制BP根据UE发送的数据包的源地址进行分流，上行路由策略用于指示UE使用锚定在锚点用户面实体的IP地址或使用锚定在本地锚点用户面实体的本地IP地址作为源地址发送数据。
可选的，所述数据传输模式为上行链路分类器ULCL模式，收发单元702还用于：
将上行转发策略发送给所述第一中间会话管理实体；其中，上行转发策略用于控制所述UE锚定的上行分类器ULCL根据所述UE发送的数据包的五元组和应用标识中的一种或多种进行转发。
可选的，选择单元701还用于：
在所述UE由当前的服务基站切换到目标基站时，且所述目标基站没有位于所述第一中间会话管理实体的管辖范围内，选择目标会话管理实体。
可选的，选择单元701用于选择目标会话管理实体包括：
若判断存在满足所述PDU会话需求信息且管辖范围包括所述UE切换到的目标基站的中间会话管理实体；选择同时满足管辖范围包括所述UE切换到的目标基站和所述PDU会话需求信息的中间会话管理实体作为目标中间会话管理实体；或
若判断不存在满足所述PDU会话需求信息且管辖范围包括所述UE切换到的目标基站的中间会话管理实体；所述网络设备分别选择满足所述PDU会话需求信息的第二中间会话管理实体和管辖范围包括所述UE切换到的目标基站的第三中间会话管理实体作为所述目标中间会话管理实体。
可选的，装置7为会话管理实体，装置7还包括确定单元，
确定单元，用于根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；
选择单元701，还用于根据所述PDU会话需求信息在所述会话管理实体的管辖范围内选择锚点用户面实体；
判断单元，还用于根据所述UE的位置信息判断所述UE的位置信息指示的服务基站 与所述锚点用户面实体不相连。
可选的，装置7为会话管理实体，会话管理装置7还包括确定单元。
所述确定单元,用于根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；PDU会话需求信息包括本地DNN；
判断单元，还用于判断所述PDU会话需求信息包括的本地DNN指示的本地DN没有位于所述会话管理实体的管辖范围内。
可选的，装置7为接入管理实体。
选择单元701，还用于选择会话管理实体。判断单元，还用于判断所述UE的位置信息指示的服务基站没有位于所述会话管理实体的管辖范围内。选择单元701，还用于选择第四中间会话管理实体。收发单元702，还用于接收来自所述会话管理实体的所述PDU会话需求和重选指示消息，所述重选指示消息用于指示所述接入管理实体选择所述第一中间会话管理实体。
可选的，装置7为接入管理实体。
选择单元701，还用于选择会话管理实体。
判断单元，还用于判断所述UE的位置信息指示的服务基站没有位于所述会话管理实体的管辖范围内。选择单元701还用于选择第四中间会话管理实体。收发单元702还用于接收来自所述会话管理实体的所述PDU会话需求信息。判断单元，还用于判断所述第四中间会话管理实体不满足所述PDU会话需求信息。
可选的，装置7为接入管理实体。
收发单元702还用于当所述PDU会话的需求发生改变时，接收来自会话管理实体的新PDU会话需求信息和重选指示消息，所述重选指示消息用于指示所述会话管理装置7选择所述第一中间会话管理实体。
可选的，所述网络设备为接入管理实体。收发单元，还用于当所述PDU会话的需求发生改变时，所述网络设备接收来自所述会话管理实体的新PDU会话需求信息；
判断单元，还用于判断所述第一中间会话管理实体不满足所述新PDU会话需求信息。选择单元701还用于根据所述UE的位置信息和所述新PDU会话需求信息选择目标中间会话管理实体。
可选的，装置7为会话管理实体，装置7还包括确定单元。确定单元，用于根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息。判断单元还用于判断接入管理实体选择的第四中间会话管理实体不满足所述PDU会话需求。收发单元702还用于将所述第一中间会话管理实体的标识信息发送给接入管理实体。
需要说明的是，在另一种可能的实施方式中，图7所示的装置7可以实现图9和图10所示实施例的会话管理实体，其中，装置7包括：选择单元701和收发单元702。
选择单元701，用于根据协议本地网络数据名DNN为协议数据单元PDU会话选择第一中间会话管理实体。
收发单元702，用于向所述第一中间会话管理实体发送用户设备UE的位置信息；其 中，所述UE的位置信息用于选择用户面实体。
可选的，选择单元701执行所述根据本地DNN为PDU会话选择第一中间会话管理实体包括：
根据所述本地DNN和所述UE的位置信息选择第一中间会话管理实体；其中，选择支持所述本地DNN指示的本地数据网络DN、及管辖范围包括所述UE的位置信息指示的服务基站的第一中间会话管理实体。
可选的，选择单元701执行所述根据本地DNN为PDU会话选择第一中间会话管理实体包括：
选择支持所述本地DNN指示的本地DN的中间会话管理实体作为第一中间会话管理实体。
可选的，所述网络设备为会话管理实体，选择单元701还用于：
根据来自应用功能的信息确定本地DNN。
可选的，收发单元702还用于：
将所述UE的位置信息发送给第一中间会话管理实体；其中，所述UE的位置信息用于指示所述第一中间会话管理实体选择支持UE位置的用户面实体，所述支持UE位置的用户面实体与UE连接的接入网接口。
可选的，收发单元702还用于：
将本地DNN发送给第一中间会话管理实体；其中，所述本地DNN用于指示第一中间会话管理实体选择本地锚点用户面实体。
可选的，所述第一中间会话管理实体选择的用户面实体同时支持本地DNN和所述UE位置信息；或
在不存在同时支持本地DNN和所述UE位置信息的用户面实体的情况下，第一中间会话管理实体根据本地DNN选择支持本地DNN的用户面实体作为本地锚点用户面实体，以及根据所述UE位置信息选择支持所述UE位置信息的用户面实体用于与UE所连接的接入网接口，其中，所述本地锚点用户面实体用于与本地DN接口。
可选的，收发单元702还用于：
将数据传输模式发送给所述第一中间会话管理实体；其中，所述数据传输模式用于指示所述第一中间会话管理实体确定上行分流规则。
可选的，收发单元702还用于：
若所数据传输模式为多归属Multihoming，将远端UE IP地址发送给所述第一中间会话管理实体；其中，所述远端UE IP用于指示所述第一中间会话管理实体确定上行分流规则。
可选的，收发单元702还用于：
若所数据传输模式为上行链路分类器ULCL，将应用信息发送给所述第一中间会话管理实体根据所述应用信息确定上行分流规则；其中，所述应用信息为应用标识或应用对应的五元组中的至少一个。
可选的，收发单元702还用于：
将上行分流规则或上行转发规则发送给所述第一中间会话管理实体；其中，所述上行 分流规则或上行转发规则用于指示第一中间会话管理实体对所述用户面实体进行配置，从而实现上行数据分流。
可选的，收发单元702还用于：
将本地锚点与本地DNN所标识的本地数据网络DN间的路由信息发送给所述第一中间会话管理实体，所述路由信息用于确定用户面实体与本地DN间的转发路径。
所述装置7可以为接入管理实体或会话管理实体，所述装置7也可以为实现相关功能的现场可编程门阵列(field-programmable gate array，FPGA)，专用集成芯片(application specific integrated circuit，ASIC)，***芯片(system on chip，SoC)，中央处理器(central processor unit，CPU)，网络处理器(network processor，NP)，数字信号处理电路(digital signal processor，DSP)，微控制器(micro controller unit，MCU)，还可以采用可编程控制器(programmable logic device，PLD)或其他集成芯片。
如图8所示，本发明实施例还提供了一种网络设备8。
该网络设备可以为接入管理实体或会话管理实体，包括：
存储器803，用于存储程序和数据；其中，该存储器可以为随机访问内存(英文：Random Access Memory，简称：RAM)或者只读内存(英文：Read Only Memory，简称：ROM)或者闪存，其中存储器803可以位于单独位于通信设备内，也可以位于处理器801的内部。
处理器801，用于执行所述存储器存储的所述程序，当所述程序被执行时，处理器801用于根据用户设备UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体。
收发器802，可以作为单独的芯片，也可以为处理器801内的收发电路或者作为输入输出接口。收发器802，用于向所述第一中间会话管理实体发送所述UE的位置信息和所述PDU会话需求信息；其中，所述UE的位置信息和所述PDU会话需求信息用于选择用户面实体。
需要说明的是，本实施例的网络设备和图7的会话管理装置，以及图3至图6以及图9和图10的方法流程基于同一构思，其带来的技术效果也相同，具体过程可参照图7的会话管理装置和图3至图6以及图9和图10的方法流程的描述，此处不再赘述。
收发器802、存储器803、处理器801之间可选地通过总线连接。
当网络设备8为芯片时，可以为实现相关功能的现场可编程门阵列(field-programmable gate array，FPGA)，专用集成芯片(application specific integrated circuit，ASIC)，***芯片(system on chip，SoC)，中央处理器(central processor unit，CPU)，网络处理器(network processor，NP)，数字信号处理电路(digital signal processor，DSP)，微控制器(micro controller unit，MCU)，还可以采用可编程控制器(programmable logic device，PLD)或其他集成芯片。
这些芯片可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生 按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State  Disk(SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (48)

  1. 一种会话管理方法，其特征在于，包括：
    网络设备根据用户设备UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体；
    所述网络设备向所述第一中间会话管理实体发送所述UE的位置信息和所述PDU会话需求信息；其中，所述UE的位置信息和所述PDU会话需求信息用于选择用户面实体。
  2. 如权利要求1所述的方法，其特征在于，所述PDU会话需求信息包括数据传输模式和本地数据网络名DNN。
  3. 如权利要求1所述的方法，其特征在于，所述网络设备根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体包括：
    所述网络设备选择同时满足管辖范围包括所述UE的位置信息指示的服务基站和所述PDU会话需求信息包括的所述本地DNN指示的本地数据网络DN，以及支持所述PDU会话需求信息中的所述数据传输模式的中间会话管理实体作为所述第一中间会话管理实体；或
    若所述网络设备判断不存在管辖范围包括所述UE的位置信息指示的服务基站和所述本地DNN指示的本地DN，以及支持所述PDU会话需求信息中包括的数据传输模式的中间会话管理实体；
    选择管辖范围包括所述UE的位置信息指示的服务基站的第二中间会话管理实体，以及选择管辖范围包括所述PDU会话需求信息中包括的本地DNN指示的本地DN且支持所述PDU会话需求信息中包括的数据传输模式的第三中间会话管理实体。
  4. 如权利要求1-3任意一项所述的方法，其特征在于，所述网络设备为会话管理实体；
    所述网络设备根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：
    所述网络设备根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；
    所述网络设备根据所述PDU会话需求信息在所述会话管理实体的管辖范围内选择锚点用户面实体；
    所述网络设备根据所述UE的位置信息判断所述UE的位置信息指示的服务基站与所述锚点用户面实体不相连。
  5. 如权利要求1-4任意一项所述的方法，其特征在于，所述网络设备为会话管理实体；
    所述网络设备根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：
    所述网络设备根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；PDU会话需求信息包括本地DNN；
    所述网络设备判断所述PDU会话需求信息包括的本地DNN指示的本地DN没有位于所述会话管理实体的管辖范围内。
  6. 如权利要求1-5任意一项所述的方法，其特征在于，所述网络设备为会话管理实体，
    所述网络设备根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体之前，还包括：
    所述网络设备根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；
    所述会话管理实体判断接入管理实体选择的第四中间会话管理实体不满足所述PDU会话需求；
    所述网络设备根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体之后，还包括：
    所述网络设备将所述第一中间会话管理实体的标识信息发送给接入管理实体。
  7. 一种通信***，其特征在于，包括网络设备和第一中间会话管理实体，其中，
    所述网络设备，用于根据用户设备UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体；
    所述第一中间会话管理实体，用于接收来自所述网络设备的所述PDU会话需求信息，根据所述UE的位置信息和所述PDU会话需求信息选择用户面实体。
  8. 如权利要求7所述的通信***，其特征在于，所述PDU会话需求信息包括数据传输模式和本地数据网络名DNN。
  9. 如权利要求7或8所述的通信***，所述数据传输模式为多归属Mutilhoming模式；
    所述第一中间会话管理实体用于在所述第一中间会话管理实体的管辖范围内根据所述UE的位置信息和PDU会话需求信息选择用户面实体，具体为：
    为所述PDU会话选择本地锚点用户面实体，以及为所述PDU会话选择分支点BP；其中，所述BP用于对所述UE发送的数据包进行分流，所述本地锚点用户面实体与所述PDU会话需求信息包括的本地DNN指示的本地数据网络DN连接，所述BP与所述UE的位置信息指示的服务基站连接。
  10. 如权利要求9所述的通信***，其特征在于，所述数据传输模式为ULCL模式，所述第一中间会话管理实体用于在所述第一中间会话管理实体的管辖范围内根据所述UE的位置信息和PDU会话需求信息选择用户面实体，具体为：
    为所述PDU会话选择本地锚点用户面实体，以及为所述PDU会话选择上行链路分类器ULCL；其中，所述ULCL用于对所述UE发送的数据包的应用标识和/五元组进行分流，所述本地锚点用户面实体与所述本地DNN指示的的本地DN连接，所述ULCL与所述UE的位置信息指示的服务基站连接。
  11. 如权利要求7所述的通信***，其特征在于，所述PDU会话需求信息包括：会话和业务连续性SSC模式和PDU会话类型中的一种或多种。
  12. 如权利要求11所述的通信***，其特征在于，所述网络设备，用于根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体，具体为：
    选择同时满足所述PDU会话需求信息且管辖范围包括所述UE的位置信息指示的服务基站的中间会话管理实体作为所述第一中间会话管理实体；或
    若判断不存在同时满足所述PDU会话需求且管辖范围包括所述UE的位置信息指示的服务基站的中间会话管理实体；
    选择满足所述PDU会话需求信息的第二中间会话管理实体，以及选择管辖范围包括所述UE的位置信息指示的服务基站的第三中间会话管理实体。
  13. 如权利要求8所述的通信***，其特征在于，所述网络设备，用于根据所述UE的 位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体，具体为：
    选择管辖范围包括所述UE的位置信息指示的服务基站和满足所述PDU会话需求信息包括的所述本地DNN指示的本地DN，以及支持所述数据传输模式的中间会话管理实体作为所述第一中间会话管理实体；或
    若判断不存在管辖范围包括所述UE的位置信息指示的服务基站和所述本地DNN指示的本地DN，以及支持所述数据传输模式的中间会话管理实体；
    选择管辖范围包括所述UE的位置信息指示的服务基站的第二中间会话管理实体，以及选择管辖范围包括所述本地DNN指示的本地DN且支持所述数据传输模式的第三中间会话管理实体。
  14. 如权利要求7-13任意一项所述的通信***，其特征在于，所述通信***还包括接入管理实体，所述网络设备为会话管理实体；
    所述接入管理实体，用于选择所述会话管理实体；
    所述网络设备，还用于根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；
    根据所述PDU会话需求信息为所述PDU会话选择锚点用户面实体；
    判断所述锚点用户面实体和所述UE的位置信息指示的服务基站不相连。
  15. 如权利要求7-14任意一项所述的通信***，其特征在于，所述通信***包括接入管理实体，所述网络设备为会话管理实体；
    所述接入管理实体，用于选择所述会话管理实体；
    所述网络设备，还用于：
    根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；
    判断所述会话管理实体的管辖范围不包括所述本地DNN指示的本地DN。
  16. 如权利要求7-15任意一项所述的通信***，其特征在于，所述通信***还包括接入管理实体，所述网络设备为会话管理实体；
    所述接入管理实体，用于选择所述会话管理实体，在所述会话管理实体的管辖范围不包括所述UE的位置信息指示的服务基站时，选择第四中间会话管理实体；
    所述网络设备，还用于：
    根据PDU会话签约信息，或PDU会话策略信息和PDU会话期望信息中的一种或多种和PDU会话签约信息确定所述PDU会话需求信息，判断所述第四中间会话管理实体不满足所述PDU会话需求信息；
    所述网络设备，还用于将所述第一中间会话管理实体的标识信息发送给所述接入管理实体。
  17. 如权利要求7-13任意一项所述的通信***，其特征在于，所述通信***还包括会话管理实体，所述网络设备为接入管理实体；
    所述会话管理实体，用于根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；判断所述接入管理实体选择的第四中间会话管理实体不满足所述PDU会话需求信 息，向所述接入管理实体发送所述PDU会话需求信息和重选指示消息，所述重选指示消息用于指示所述接入管理实体选择所述第一中间会话管理实体；
    所述接入管理实体，还用于：
    选择所述会话管理实体，在所述会话管理实体的管辖范围不包括所述UE的位置信息指示的服务基站时，选择所述第四中间会话管理实体；接收来自所述会话管理实体的PDU会话需求信息和所述重选指示消息。
  18. 如权利要求7-13任意一项所述的通信***，其特征在于，所述通信***还包括会话管理实体，所述网络设备为接入管理实体；
    所述会话管理实体，用于用于根据PDU会话签约信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息，向所述接入管理实体发送所述PDU会话需求信息；
    所述接入管理实体，还用于：
    选择所述会话管理实体，在所述会话管理实体的管辖范围不包括所述UE的位置信息指示的服务基站时，选择第四中间会话管理实体，判断所述第四中间会话管理实体不满足来自所述会话管理实体的所述PDU会话需求信息。
  19. 一种网络设备，其特征在于，包括：处理器和收发器；
    所述处理器，用于根据用户设备UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体；
    所述收发器，用于向所述第一中间会话管理实体发送所述UE的位置信息和所述PDU会话需求信息；其中，所述UE的位置信息和所述PDU会话需求信息用于选择用户面实体。
  20. 如权利要求19所述的网络设备，其特征在于，所述PDU会话需求信息包括数据传输模式和本地数据网络名DNN。
  21. 如权利要求20所述的网络设备，其特征在于，所述处理器，用于根据所述UE的位置信息和协议数据单元PDU会话需求信息为PDU会话选择第一中间会话管理实体，具体为：
    选择同时满足管辖范围包括所述UE的位置信息指示的服务基站和所述PDU会话需求信息包括的所述本地DNN指示的本地数据网络DN，以及支持所述PDU会话需求信息中的所述数据传输模式的中间会话管理实体作为所述第一中间会话管理实体；或
    若判断不存在管辖范围包括所述UE的位置信息指示的服务基站和所述本地DNN指示的本地DN，以及支持所述PDU会话需求信息中包括的数据传输模式的中间会话管理实体；
    选择管辖范围包括所述UE的位置信息指示的服务基站的第二中间会话管理实体，以及选择管辖范围包括所述PDU会话需求信息中包括的本地DNN指示的本地DN且支持所述PDU会话需求信息中包括的数据传输模式的第三中间会话管理实体。
  22. 如权利要求19-21任意一项所述的网络设备，其特征在于，所述网络设备为会话管理实体；
    所述处理器还用于：
    根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；
    根据所述PDU会话需求信息在所述会话管理实体的管辖范围内选择锚点用户面实体；
    根据所述UE的位置信息判断所述UE的位置信息指示的服务基站与所述锚点用户面实体不相连。
  23. 如权利要求19-22任意一项所述的网络设备，其特征在于，所述网络设备为会话管理实体；
    所述处理器还用于：
    根据PDU会话签约信息确定PDU会话需求信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；所述PDU会话需求信息包括本地DNN；
    判断所述PDU会话需求信息包括的本地DNN指示的本地DN没有位于所述会话管理实体的管辖范围内。
  24. 如权利要求19-23任意一项所述的网络设备，其特征在于，所述网络设备为会话管理实体，
    所述处理器，还用于根据PDU会话签约信息；或根据PDU会话策略信息和PDU会话期望信息中的一种或多种，以及PDU会话签约信息确定PDU会话需求信息；判断接入管理实体选择的第四中间会话管理实体不满足所述PDU会话需求；
    所述收发器，还用于将所述第一中间会话管理实体的标识信息发送给接入管理实体。
  25. 一种会话管理方法，其特征在于，包括：
    网络设备根据本地网络数据名DNN为协议数据单元PDU会话选择第一中间会话管理实体；
    所述网络设备向所述第一中间会话管理实体发送用户设备UE的位置信息；其中，所述UE的位置信息用于选择用户面实体。
  26. 如权利要求25所述的方法，其特征在于，所述网络设备根据本地DNN为PDU会话选择第一中间会话管理实体包括：
    所述网络设备根据所述本地DNN和所述UE的位置信息选择第一中间会话管理实体；其中，选择支持所述本地DNN指示的本地数据网络DN、及管辖范围包括所述UE的位置信息指示的服务基站的第一中间会话管理实体。
  27. 如权利要求25所述的方法，其特征在于，所述网络设备根据本地DNN为PDU会话选择第一中间会话管理实体包括：
    所述网络设备选择支持所述本地DNN指示的本地数据网络DN的中间会话管理实体作为第一中间会话管理实体。
  28. 如权利要求25-27任意一项所述的方法，其特征在于，所述网络设备为会话管理实体，所述方法还包括：
    所述网络设备根据来自应用功能的信息确定本地DNN。
  29. 如权利要求25所述的方法，其特征在于，所述方法还包括：
    所述网络设备将所述UE的位置信息发送给第一中间会话管理实体；其中，所述UE的位置信息用于指示所述第一中间会话管理实体选择支持UE位置的用户面实体，所述支持UE位置的用户面实体与UE连接的接入网接口。
  30. 如权利要求25-29任意一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备将本地DNN发送给第一中间会话管理实体；其中，所述本地DNN用于指示第一中间会话管理实体选择本地锚点用户面实体。
  31. 如权利要求29或30所述的方法，其特征在于，
    所述第一中间会话管理实体选择的用户面实体同时支持本地DNN和所述UE位置信息； 或
    在不存在同时支持本地DNN和所述UE位置信息的用户面实体的情况下，第一中间会话管理实体根据本地DNN选择支持本地DNN的用户面实体作为本地锚点用户面实体，以及根据所述UE位置信息选择支持所述UE位置信息的用户面实体用于与UE所连接的接入网接口，其中，所述本地锚点用户面实体用于与本地DN接口。
  32. 如权利要求25所述的方法，其特征在于，所述方法还包括：
    所述网络设备将数据传输模式发送给所述第一中间会话管理实体；其中，所述数据传输模式用于指示所述第一中间会话管理实体确定上行分流规则。
  33. 如权利要求32所述的方法，其特征在于，所述方法还包括：
    若数据传输模式为多归属Multihoming，则所述网络设备还将远端UE IP地址发送给所述第一中间会话管理实体；其中，所述远端UE IP用于指示所述第一中间会话管理实体确定上行分流规则。
  34. 如权利要求32所述的方法，其特征在于，所述方法还包括：
    若所数据传输模式为上行链路分类器ULCL，则所述网络设备还将应用信息发送给所述第一中间会话管理实体，其中，所述应用信息用于指示第一中间会话管理实体确定上行分流规则；所述应用信息为应用标识或应用对应的五元组中的至少一个。
  35. 如权利要求25-34任意一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备将上行分流规则或上行转发规则发送给所述第一中间会话管理实体；其中，所述上行分流规则或上行转发规则用于指示第一中间会话管理实体对所述用户面实体进行配置，从而实现上行数据分流。
  36. 如权利要求25-35任意一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备将本地锚点与本地DNN所标识的本地数据网络DN间的路由信息发送给所述第一中间会话管理实体，所述路由信息用于确定用户面实体与本地数据网络DN间的转发路径。
  37. 一种网络设备，其特征在于，包括：处理器和收发器；
    所述处理器，用于根据协议本地网络数据名DNN为协议数据单元PDU会话选择第一中间会话管理实体；
    所述收发器，用于向所述第一中间会话管理实体发送用户设备UE的位置信息；其中，所述UE的位置信息用于选择用户面实体。
  38. 如权利要求37所述的网络设备，其特征在于，所述处理器执行所述根据本地DNN为PDU会话选择第一中间会话管理实体包括：
    根据所述本地DNN和所述UE的位置信息选择第一中间会话管理实体；其中，选择支持所述本地DNN指示的本地数据网络DN、及管辖范围包括所述UE的位置信息指示的服务基站的第一中间会话管理实体。
  39. 如权利要求37所述的网络设备，其特征在于，所述处理器执行所述根据本地DNN为PDU会话选择第一中间会话管理实体包括：
    选择支持所述本地DNN指示的本地DN的中间会话管理实体作为第一中间会话管理实体。
  40. 如权利要求37-39任意一项所述的网络设备，其特征在于，所述网络设备为会话管理实体，所述处理器还用于：
    根据来自应用功能的信息确定本地DNN。
  41. 如权利要求37所述的网络设备，其特征在于，所述收发器还用于：
    将所述UE的位置信息发送给第一中间会话管理实体；其中，所述UE的位置信息用于指示所述第一中间会话管理实体选择支持UE位置的用户面实体，所述支持UE位置的用户面实体与UE连接的接入网接口。
  42. 如权利要求37-41任意一项所述的网络设备，其特征在于，所述收发器还用于：
    将本地DNN发送给第一中间会话管理实体；其中，所述本地DNN用于指示第一中间会话管理实体选择本地锚点用户面实体。
  43. 如权利要求41或42所述的网络设备，其特征在于，
    所述第一中间会话管理实体选择的用户面实体同时支持本地DNN和所述UE位置信息；或
    在不存在同时支持本地DNN和所述UE位置信息的用户面实体的情况下，第一中间会话管理实体根据本地DNN选择支持本地DNN的用户面实体作为本地锚点用户面实体，以及根据所述UE位置信息选择支持所述UE位置信息的用户面实体用于与UE所连接的接入网接口，其中，所述本地锚点用户面实体用于与本地DN接口。
  44. 如权利要求37所述的网络设备，其特征在于，所述收发器还用于：
    将数据传输模式发送给所述第一中间会话管理实体；其中，所述数据传输模式用于指示所述第一中间会话管理实体确定上行分流规则。
  45. 如权利要求44所述的网络设备，其特征在于，所述收发器还用于：
    若所数据传输模式为多归属Multihoming，将远端UE IP地址发送给所述第一中间会话管理实体；其中，所述远端UE IP用于指示所述第一中间会话管理实体确定上行分流规则。
  46. 如权利要求44所述的网络设备，其特征在于，所述收发器还用于：
    若所数据传输模式为上行链路分类器ULCL，将应用信息发送给所述第一中间会话管理实体根据所述应用信息确定上行分流规则；其中，所述应用信息为应用标识或应用对应的五元组中的至少一个。
  47. 如权利要求37-46任意一项所述的网络设备，其特征在于，所述收发器还用于：
    将上行分流规则或上行转发规则发送给所述第一中间会话管理实体；其中，所述上行分流规则或上行转发规则用于指示第一中间会话管理实体对所述用户面实体进行配置，从而实现上行数据分流。
  48. 如权利要求37-46任意一项所述的网络设备，其特征在于，所述收发器还用于：
    将本地锚点与本地DNN所标识的本地数据网络DN间的路由信息发送给所述第一中间会话管理实体，所述路由信息用于确定用户面实体与本地DN间的转发路径。
PCT/CN2018/085099 2017-05-05 2018-04-28 一种会话管理方法、网络设备和通信*** WO2018202008A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18793911.1A EP3606275B1 (en) 2017-05-05 2018-04-28 Session management method, network apparatus, and communication system
EP22164618.5A EP4090078A3 (en) 2017-05-05 2018-04-28 Session management method and related devices
US16/664,481 US11706704B2 (en) 2017-05-05 2019-10-25 Managing user plane entities at different locations in a PDU session

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710314201.2 2017-05-05
CN201710314201 2017-05-05
CN201810150678.6 2018-02-13
CN201810150678.6A CN108811011B (zh) 2017-05-05 2018-02-13 一种会话管理方法、网络设备和通信***

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/664,481 Continuation US11706704B2 (en) 2017-05-05 2019-10-25 Managing user plane entities at different locations in a PDU session

Publications (1)

Publication Number Publication Date
WO2018202008A1 true WO2018202008A1 (zh) 2018-11-08

Family

ID=64015888

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085099 WO2018202008A1 (zh) 2017-05-05 2018-04-28 一种会话管理方法、网络设备和通信***

Country Status (1)

Country Link
WO (1) WO2018202008A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475290A (zh) * 2019-07-23 2019-11-19 中国联合网络通信集团有限公司 一种会话切换方法及装置
CN111092937A (zh) * 2019-12-04 2020-05-01 中兴通讯股份有限公司 会话创建方法、控制方法、会话创建***、网元及介质
CN111615217A (zh) * 2019-02-25 2020-09-01 华为技术有限公司 一种会话建立方法及装置
CN112468529A (zh) * 2019-09-09 2021-03-09 ***通信有限公司研究院 一种会话管理方法及设备
CN113796156A (zh) * 2019-05-06 2021-12-14 株式会社Ntt都科摩 用于处理服务请求的通信网络组件和方法
US12040979B2 (en) 2019-04-28 2024-07-16 Huawei Technologies Co., Ltd. Communications method, apparatus, and system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009907A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 演进网络架构中隧道建立、释放方法及装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009907A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 演进网络架构中隧道建立、释放方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"System Architecture for the 5G System", 3GPP TS 23.501, V0.4.0, 20 April 2017 (2017-04-20), XP051268332 *
"Technical Specification Group Services and System Aspects; Procedures for the 5G System, Stage 2 (Release 15)", 3GPP TS 23.502, V0.3.0, 20 April 2017 (2017-04-20), XP055546054 *
See also references of EP3606275A4

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111615217A (zh) * 2019-02-25 2020-09-01 华为技术有限公司 一种会话建立方法及装置
CN111615217B (zh) * 2019-02-25 2023-11-21 华为技术有限公司 一种会话建立方法及装置
US12041135B2 (en) 2019-02-25 2024-07-16 Huawei Technologies Co., Ltd. Session establishment method and apparatus
US12040979B2 (en) 2019-04-28 2024-07-16 Huawei Technologies Co., Ltd. Communications method, apparatus, and system
CN113796156A (zh) * 2019-05-06 2021-12-14 株式会社Ntt都科摩 用于处理服务请求的通信网络组件和方法
CN113796156B (zh) * 2019-05-06 2024-03-19 株式会社Ntt都科摩 用于处理服务请求的通信网络组件和方法
CN110475290A (zh) * 2019-07-23 2019-11-19 中国联合网络通信集团有限公司 一种会话切换方法及装置
CN110475290B (zh) * 2019-07-23 2023-04-28 中国联合网络通信集团有限公司 一种会话切换方法及装置
CN112468529A (zh) * 2019-09-09 2021-03-09 ***通信有限公司研究院 一种会话管理方法及设备
CN112468529B (zh) * 2019-09-09 2022-08-23 ***通信有限公司研究院 一种会话管理方法及设备
CN111092937A (zh) * 2019-12-04 2020-05-01 中兴通讯股份有限公司 会话创建方法、控制方法、会话创建***、网元及介质

Similar Documents

Publication Publication Date Title
CN108811011B (zh) 一种会话管理方法、网络设备和通信***
WO2018202008A1 (zh) 一种会话管理方法、网络设备和通信***
US10911990B2 (en) Network handover method and related device
WO2020168840A1 (zh) 网络节点选择方法及装置
CN109156040B (zh) 一种通信控制的方法及相关网元
CN107734563B (zh) 切换场景下的QoS参数处理的方法及设备
US20190200266A1 (en) Access network switching method in heterogeneous radio access network and user equipment performing the same
EP3589037A1 (en) Method and user equipment for accessing network slices which are not mutually exclusive
JP2017500760A (ja) 通信システム
KR20190117747A (ko) 통신 방법, 코어 네트워크 디바이스 및 액세스 네트워크 디바이스
US10412640B2 (en) Switching control method, apparatus, and wireless communications network
CN108810988B (zh) 一种消息传输的方法及装置
JP7311022B2 (ja) Ａｍｆ、ａｍｆの通信方法、及び基地局装置
EP3886500B1 (en) Mobility management method and apparatus
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2019037500A1 (zh) 一种选择无线接入网设备的方法及装置
WO2021097858A1 (zh) 一种通信方法及装置
US11259218B2 (en) Systems and methods for handover of dual connectivity user equipment
WO2016045297A1 (zh) 终端的业务连续性处理方法及装置
WO2016090922A1 (zh) 一种lipa/sipto连接的建立方法和装置
WO2020211538A1 (zh) 一种数据传输方法及装置
US20220256407A1 (en) Handling of ue in cm-connected state with rrc inactive state
CN116868603A (zh) 针对af会话的外部参数提供的新方法
WO2023065865A1 (zh) 一种通信方法及设备
KR20190022292A (ko) 이종 접속 망 간의 트래픽 이동 방법 및 이를 수행하는 무선 통신 시스템

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018793911

Country of ref document: EP

Effective date: 20191030