WO2018068216A1 - 会话管理方法及网元 - Google Patents

会话管理方法及网元 Download PDF

Info

Publication number
WO2018068216A1
WO2018068216A1 PCT/CN2016/101834 CN2016101834W WO2018068216A1 WO 2018068216 A1 WO2018068216 A1 WO 2018068216A1 CN 2016101834 W CN2016101834 W CN 2016101834W WO 2018068216 A1 WO2018068216 A1 WO 2018068216A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
network element
session
control plane
user equipment
Prior art date
Application number
PCT/CN2016/101834
Other languages
English (en)
French (fr)
Inventor
吴义壮
熊春山
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2019519710A priority Critical patent/JP6829308B2/ja
Priority to PCT/CN2016/101834 priority patent/WO2018068216A1/zh
Priority to CN201680089433.6A priority patent/CN109792599B/zh
Priority to EP16918734.1A priority patent/EP3512223B1/en
Publication of WO2018068216A1 publication Critical patent/WO2018068216A1/zh
Priority to US16/380,444 priority patent/US11483898B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point

Definitions

  • the embodiments of the present invention relate to the field of wireless communications, and in particular, to a session management method and a network element.
  • the context of the session needs to be synchronized between the user equipment and the network side, that is, the bearer context in the session needs to be synchronized.
  • the establishment, modification, and deletion of the bearer context may be initiated by the user equipment or initiated by the network side.
  • the network side needs to notify the user equipment (User Equipment, UE for short) of the information of the session (deleting the bearer, modifying the bearer, or establishing the bearer). So that the UE side synchronizes with the network side session information.
  • the network initiates the foregoing process, if the UE is in an idle state, the network initiates a paging procedure to enable the UE to enter a connected state, and synchronize the modified session information to the UE.
  • an asynchronous session management process is proposed.
  • the network side initiates a session modification, the initiated session modification may not be immediately synchronized to the UE, and when the UE is in an idle state, the network The side node does not initiate a paging procedure to the UE, and records the initiated session modification request as waiting for processing, and saves the session modification request message. If the UE initiates the location update process to the network side during the period when the session modification request information is not sent to the UE, the network side processes the message waiting to be processed, and there is currently no corresponding session management method.
  • the embodiment of the present invention provides a session management method and a network element, so as to implement session management in a scenario in which a control plane connection of a user equipment changes.
  • the embodiment of the present invention provides a session management method, including: a first control plane network element receives a user equipment UE context response message from a second control plane network element, where the UE context response message carries a first session The message that the first session message is a session message to be processed; the first control plane network element sends a second session message to the user equipment according to the UE context response message.
  • the first control plane network element acquires the UE context response message from the second control plane network element, where the first session message is carried in the UE context response message, the first session The message is the session message to be processed; the first control plane network element sends a second session message to the user equipment according to the received UE context response message, thereby sending the session message to be processed to the user equipment, thereby
  • the management of the session is implemented in the scenario where the control plane connection changes.
  • the first session message and the second session message are the same.
  • the first control plane network element after receiving the UE context response message, the first control plane network element sends the to-be-processed session message carried in the context response message to the user equipment as the second session message.
  • the second session message is generated based on the first session message.
  • the first control plane network element after receiving the UE context response message, the first control plane network element generates a second session message according to the first session message carried in the UE context response message, and uses the second session message as the to-be-processed session. The message is sent to the user device.
  • the second session message is a session management message
  • the first control plane network element sends the second session message to the user equipment according to the UE context response message, including:
  • the second session message is a session management message
  • the first control plane network element sends the second session message to the user equipment according to the UE context response message, including:
  • the first control plane network element sends a location update accept message to the user equipment according to the first session message, where the location update accept message carries the session management message.
  • the second session message is a session management message
  • the first control plane network element sends the second session message to the user equipment according to the UE context response message, including:
  • the first control plane network element sends a context establishment request message to the access network element accessed by the user equipment according to the first session message, where the context establishment request message carries the session management message, And causing the access network element to send the session management message to the user equipment by using a radio resource control RRC reconfiguration.
  • the second session message is a session management message
  • the first control plane network element sends the second session message to the user equipment according to the UE context response message, including:
  • the first control plane network element sends a PDU session update response message to the user equipment according to the first session message, where the PDU session update response message carries the session management message.
  • the first control plane network element sends the second session message to the user equipment, including:
  • the first control plane network element sends a second session message corresponding to the communication link in an activated state to the user equipment.
  • the method before the first control plane network element receives the UE context response message from the second control plane network element, the method further includes:
  • the first control plane network element receives the location update request message sent by the user equipment; the location update request message carries information for deriving the second control plane network element address.
  • the method before the first control plane network element receives the UE context response message from the second control plane network element, the method further includes:
  • the first control plane network element receives the PDU session relocation request message sent by the MM network element; the PDU session relocation request message carries information for deriving the second control plane network element address.
  • the method before the first control plane network element receives the UE context response message from the second control plane network element, the method further includes:
  • the first control plane network element receives the PDU session update request message sent by the user equipment; the PDU session update request message carries information used to derive the second control plane network element address.
  • the first control plane network element receives the UE context response message from the second control plane network element, including:
  • the first control plane network element receives the UE context response message sent by the second control plane network element according to the context request message.
  • the first control plane network element is a destination SM
  • the second control plane network element is a source SM
  • the UE context response message is an SM context response message.
  • the method further includes:
  • the first control plane network element sends a PDU session synchronization notification message to the policy function PF network element.
  • the embodiment of the present invention provides a session management network element, where the network element has the function of realizing the behavior of the first control plane network element in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the network element is deployed in the first control plane network element, and includes: a receiving unit and a sending unit, where the receiving unit is configured to receive a user equipment UE context response from the second control plane network element.
  • the message that the UE session response message carries the first session message, the first session message is a session message to be processed, and the sending unit is configured to send the second session message to the user equipment according to the UE context response message.
  • the sending unit is further configured to perform the sending step involved in the foregoing method embodiment, where the receiving unit is further configured to perform the receiving step involved in the foregoing method embodiment.
  • the session management network element is deployed in the first control plane network element, and includes: a transmitter, a receiver, and a processor, where the receiver is configured to be under the control of the processor.
  • the second control plane network element receives the UE context response message, where the UE context response message carries the first session message, the first session message is a pending session message, and the transmitter is used by the processor. Controlling, according to the UE context response message, the second session message is sent to the user equipment.
  • the transmitter is further configured to perform the sending step involved in the foregoing method embodiment, where the receiver is further configured to perform the receiving step involved in the foregoing method embodiment.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the session management network element, including a program designed to perform the above aspects.
  • the session management method and the network element in the embodiment of the present invention can implement session management in a scenario in which the control plane connection of the user equipment changes.
  • FIG. 1 is a schematic diagram of a possible application scenario of the present invention
  • FIG. 2 is a schematic diagram of another possible application scenario of the present invention.
  • FIG. 3 is a flowchart of a session management method according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a second session management method according to Embodiment 2 of the present invention.
  • FIG. 5 is a flowchart of a third session management method according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a fourth session management method according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a fifth session management method according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a sixth session management method according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a session management network element according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another session management network element according to an embodiment of the present invention.
  • the session management solution provided by the embodiment of the present invention can be applied to the session management of various communication systems, and can be applied to the session management in which the network element of the control plane connected to the user equipment changes.
  • the solution of the embodiment of the present invention can be applied to a communication system such as an EPS system or a 5G network.
  • FIG. 1 is a schematic diagram of a possible application scenario of the present invention.
  • the UE the access network (English: Access Network, AN for short), the user plane (English: User Plane, UP) network element, and the control plane (English: Control Plane) , referred to as: CP) network element and policy function (English: Policy Function, referred to as: PF) network element.
  • the access network English: Access Network, AN for short
  • the user plane English: User Plane, UP
  • CP Control Plane
  • Policy Function referred to as: Policy Function
  • FIG. 2 is a schematic diagram of another possible application scenario of the present invention.
  • the scenario shown in Figure 2 further divides the CP network element into mobile management (English: Mobility Management, MM for short) network element and session management (English: Session Management, SM for short) as shown in Figure 1.
  • the CP function (function) and the UP function in the core network are separated.
  • the CP network element and the UP network element may be multiple, the CP network element is used for signaling interaction, and the UP network element is used for data transmission.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present invention.
  • the application scenario includes a user equipment, an access network device, and a control plane function network element, a user plane function network element, and a policy function network element of the core network.
  • the control plane function network element may include a mobility management network element and a session management network element.
  • the user equipment may be a mobile phone, a tablet computer, a notebook computer, a personal computer (English name: personal computer, PC), a super mobile personal computer (English name: Ultra-mobile Personal Computer, UMPC), a netbook, a personal digital assistant. (English full name: Personal Digital Assistant, PDA), user equipment such as in-vehicle equipment.
  • the access network device may be an access device in an evolved UMTS terrestrial radio access network (E-UTRAN), such as an eNB (evolved Node B), or Access network equipment in the NextGen Access Network (NG AN).
  • E-UTRAN evolved UMTS terrestrial radio access network
  • eNB evolved Node B
  • NG AN NextGen Access Network
  • the control plane function network element is used to implement the control plane function, and is specifically used for signaling interaction.
  • the control plane function network element may include a mobility management network element and a session management network element
  • the mobility management network element is configured to perform the user equipment registration management, the reachability detection, the control plane, and the user plane.
  • the process of network function allocation, mobility management, addressing, and identity management, the session management network element is used to manage the establishment of the IP service and the non-IP service connection of the UE and manage the user plane corresponding to the connection.
  • the user plane function network element is used to implement a user plane function, and is specifically used for transmission of user data.
  • the policy function network element is used for policy decision, policy provision, event reporting, and the like.
  • the policies include, for example, a QoS control policy, a charging policy, a session management policy, a mobility management policy, and the like.
  • control plane network elements in FIG. 1 may be more than one, and the number of session management network elements in FIG. 2 may also be more than one.
  • FIG. 3 is a flowchart of a session management method according to an embodiment of the present invention.
  • the method of Figure 3 can be performed based on Figure 1, Figure 2 or other similar scenarios.
  • the control plane network element connected after the UE control plane connection is changed is referred to as a first CP network element
  • the source CP connected by the UE before the control plane connection changes is referred to as a second CP.
  • the control plane network element that is connected after the UE control plane connection is changed is referred to as the destination SM network element
  • the control plane network element that the UE connects before the control plane connection changes It is called a source SM network element.
  • FIG. 1 the control plane network element connected after the UE control plane connection is changed
  • the destination SM network element the control plane network element that the UE connects before the control plane connection changes. It is called a source SM network element.
  • the executor of the method of the embodiment of the present invention is the first CP network element.
  • the execution entity of the method of the embodiment of the present invention is used as the destination SM network element.
  • the first CP network element is used as an execution subject.
  • the processing steps of the method in the embodiment of the present invention include:
  • the first CP network element receives the UE context response message from the second CP network element; the UE context response message carries the first session message, and the first session message is a session message to be processed.
  • step S202 the first CP network element sends a second session message to the UE according to the UE context response message.
  • the first session message may be a session management message, for example, the first session message includes an unprocessed session management message received by the second CP network element and/or a session management message that the second CP network element is not sent to the UE, and Specifically, the first session message may be a session management message of the NAS layer generated by the second CP network element according to the received unprocessed session management message, and further, the session management message may include a pending session. information.
  • the second session message is the same as the first session message, for example, the second session message is the same session management message as the first session message.
  • the second session message is generated according to the first session message, for example, the first session message is a first session management message, and the second session message is a second session management message; Transmitting the second session message to the UE according to the UE context response message, the method includes: the first CP network element generates a second session management message according to the first session management message; and the first CP network element sends the second session management message to the UE .
  • the first session management message is a session management message of the NAS layer
  • the second session message is a session management request message generated according to the session management message of the NAS layer.
  • the first CP network element after receiving the context response message, the first CP network element needs to further determine whether the session message to be processed needs to be sent to the UE, where the specific manner includes: determining, by the first CP network element, from the second CP network Receiving, in the UE context response message, whether the first session message is included, if yes, the first CP network element performing the step of sending the second session message to the second CP network element, for example, the first CP network element directly directly connects the first session The message is sent to the UE as the second session message; or the second session message is generated according to the first session message and sent to the UE.
  • the first CP network element acquires state information of the session communication link established between the UE and the network in advance from the UE; after the first CP network element receives the UE context response message, the first CP Determining, by the network element, whether there is a communication link in an active state and a session message corresponding to the communication link in an active state in the first session message, if yes, the first CP network element is The session message corresponding to the communication link in the activated state is sent to the UE as the second session message; or the first CP network element generates the second session message according to the session message corresponding to the communication link in the activated state, and the second session is to be The message is sent to the UE.
  • both the first session message and the second session message may include pending session information.
  • the UE context response message received by the first CP network element is used for the purpose of sending the session context that the second CP network element is not sent to the UE to the UE through the first CP network element.
  • the pending session information that needs to be synchronized to the UE may be directly sent, and the corresponding first CP network element sends the pending session information in the UE context response message to the UE.
  • the pending session information mentioned above may include the original pending session information received by the second CP network element, and the first CP network element needs to parse, convert, and the like to receive the original pending session information; further, the pending session information. It may also include session information that can be sent directly to the UE without conversion. More specifically, the pending session information includes context information corresponding to one or more communication links in the session established between the UE and the network, for example, the pending session information includes the identifier of the one or more communication links. Information, status information, QoS information, and business flow information.
  • FIG. 4 is a flowchart of a second session management method according to Embodiment 2 of the present invention.
  • the method shown in FIG. 4 is performed based on the scene shown in FIG. 1.
  • the control plane network element that is connected after the UE control plane connection is changed is referred to as a first CP network element
  • the source CP that the UE connects before the connection of the control plane changes is referred to as a second CP network element.
  • the processing steps of the method shown in Figure 4 include:
  • step S301 the UE sends a location update request message to the first CP network element.
  • the UE when the UE is in an idle state and needs to initiate a location update, the UE sends a location update request message to the first CP network element.
  • the location update request message may be a Tracking Area Update (TAU) message (TAU request message).
  • TAU request message may carry information for deriving the second CP network element address that the UE connects before the CP connection change, and the user equipment allocated by the second CP network element to the UE. Identification information, such as Globally Unique Temporary UE Identity (GUTI). Further, the TAU request message may further carry status information of the session communication link established between the UE and the network, such as bearer status information.
  • TAU Tracking Area Update
  • the TAU request message may carry information for deriving the second CP network element address that the UE connects before the CP connection change, and the user equipment allocated by the second CP network element to the UE. Identification information, such as Globally Unique Temporary UE Identity (GUTI).
  • GUI Globally Unique Temporary UE Identity
  • the TAU request message may further carry status information of the session communication link established between the UE and the network, such as bearer status information.
  • step S302 the first CP network element sends a context request message to the second CP network element.
  • the first CP network element derives the address of the second CP network element according to the information carried in the TAU request message.
  • the first CP network element sends a context request message to the second CP network element.
  • step S303 the second CP network element sends a UE context response message to the first CP network element.
  • the UE context response message carries the first session message, and the specific format and content of the first session message are described in the first embodiment, and details are not described herein.
  • step S304 the first CP network element sends a context acknowledgement message (Context Acknowledge message) to the second CP network element.
  • Context Acknowledge message Context Acknowledge message
  • the first CP network element after receiving the UE context response message, the first CP network element sends a context acknowledgement receiving message to the second CP network element to notify the second CP network element that the first CP network element has received the UE context response message. Further, the second CP network element may delete the context information of the UE or mark the UE context information as invalid or unavailable.
  • the first CP network element further determines whether the first session message in the UE context response message needs to be sent to the UE, where the determining method is as shown in Embodiment 1, when the first When the CP network element determines that the first session message needs to be sent to the UE, the first CP network element performs all subsequent steps of the embodiment. If the first CP network element determines that the first session message is not required to be sent to the UE, the first CP The network element then performs the steps in steps S305, S310, and S310.
  • step S305 the first CP network element sends a location update complete message, such as a TAU Accept message, to the UE.
  • step S305 may be located at any time after step S304. As in other possible embodiments, step S305 may also be located after step S312 described in the embodiment of the present invention, and is not limited herein.
  • step S306 the first CP network element sends a context setup request message to the AN network element.
  • the second session message is carried in the context establishment request message.
  • the second session message is a session management message.
  • the second session message is a session management message.
  • the session management message includes context information corresponding to multiple communication links in the session established between the UE and the network.
  • the session information may include an identifier of the communication link, QoS information used by the communication link, service flow information, and the like.
  • the session information may include updated communication link information determined according to the pending session.
  • the context establishment request message may further include one or more pending session management requests, where the pending session management request includes context information corresponding to the modified communication link in the session established between the UE and the network.
  • the specific information may include QoS information, service flow information, and the like.
  • the first CP network element when the first session message needs to be updated to the UE, for example, when the pending session information carried in the first session message needs to be updated to the UE, the first CP network element sends a context establishment request message to the access network device.
  • multiple pending sessions may be placed in one session management message or included in multiple session management messages.
  • the foregoing context establishment request message may also be a context modification request message or another request message for session management.
  • step S307 the AN network element sends a Radio Resource Control (RRC) reconfiguration message (RRC reconfig message) to the UE.
  • RRC Radio Resource Control
  • the RRC reconfiguration message includes one or more session management messages.
  • the AN network element after receiving the context setup request message, the AN network element sends an RRC reconfiguration message including one or more session management messages to the UE.
  • the UE After receiving the session management message, the UE performs a process of sending the pening session to the UE.
  • step S308 the UE sends an RRC reconfig response message to the AN network element.
  • the RRC reconfiguration response message includes a session management response message.
  • the session management response message includes the result value of the session synchronization of the UE, such as the synchronization success or the synchronization failure.
  • the failure cause value is carried, for example, the communication link has been deleted.
  • the UE after receiving the RRC reconfiguration message, the UE updates the session information on the UE according to the session management request in the RRC reconfiguration message, and generates an RRC reconfiguration response message including the session management response message according to the RRC reconfiguration message.
  • the session management response message is a response message of the UE to the session management request.
  • step S309 the AN network element sends a context setup response message to the first CP network element.
  • the context establishment response message includes a session management response message.
  • the AN network element after receiving the RRC reconfiguration response message, the AN network element sends a context setup response message to the first CP network element.
  • step S310 the first CP network element sends a protocol data unit (PDU: PDU session update message) to the UP network element.
  • PDU protocol data unit
  • the first CP network element sends a PDU session update message to the user plane function network element to instruct the UP network element to perform a synchronization update process of the session context. If the PDU session update message indicates that the UE has deleted the session information, the PDU session update message indicates that the UP network element deletes the corresponding session information; if the PDU session update message indicates that the UE has performed the session synchronization process, the PDU session update message indicates that the UP network element performs The corresponding session synchronization process. After completing the session update process, the UP network element optionally performs step 311.
  • step S311 the UP network element sends a PDU session update response message to the first CP network element.
  • the session management method shown in FIG. 4 may further include the step S312, where the UE sends the session management response message to the first CP network element.
  • the UE After receiving the RRC reconfiguration message sent by the AN network element, the UE generates a session management response message according to the session management request in the RRC reconfiguration message, and sends the indicated session management response message to the first CP network element.
  • the session management response message is not included in the RRC reconfiguration response message in step S308 and the context establishment response message in step S309.
  • S310 and S311 are a PDU session establishment request message and a PDU session establishment response message.
  • the session management method shown in FIG. 4 may further include the step S313, the first CP network element sends a pending PDU session synchronization notification message to the PF network element. Message). After receiving the pending PDU session synchronization notification message, the PF network element sets the session to the synchronization state.
  • first session message and the second session message in the embodiment of the present invention may be the same message.
  • the second session message may also be a message generated according to the first session message, and the specific generation method may be See implementation one.
  • the specific generation method may be See implementation one.
  • the newly connected CP of the UE can obtain the session context to be updated from the source CP, and execute the update process of the pending session. Further, if the UE has deleted the session information, the UE instructs the CP to initiate a process of updating the session to the UP.
  • FIG. 5 is a flowchart of a third session management method according to an embodiment of the present invention.
  • the method shown in Fig. 5 is performed based on the scene shown in Fig. 1.
  • the control plane network element connected after the UE control plane connection is changed is called The first CP network element, the source CP that the UE connects before the control plane connection changes, is called the second CP network element.
  • the processing steps of the method shown in Figure 5 include:
  • step S401 the UE sends a sending location update request message to the first CP network element.
  • the UE when the UE is in an idle state and needs to initiate a location update, the UE sends a location update request message to the first CP network element.
  • the location update request message may be a Tracking Area Update (TAU) message (TAU request message).
  • TAU request message may carry information for deriving the second CP network element address that the UE connects before the CP connection change, and the user equipment allocated by the second CP network element to the UE. Identification information, such as Globally Unique Temporary UE Identity (GUTI). Further, the TAU request message may further carry bearer status information of the session communication link established between the UE and the network.
  • TAU Tracking Area Update
  • GUI Globally Unique Temporary UE Identity
  • step S402 the first CP network element sends a context request message to the second CP network element.
  • the first CP network element derives the address of the second CP network element according to the information carried in the TAU request message.
  • the first CP network element sends a context request message to the second CP network element.
  • step S403 the second CP network element sends a UE context response message to the first CP network element.
  • the UE context response message carries the first session message, and the specific format and content of the first session message are described in the first embodiment, and details are not described herein.
  • step S404 the first CP network element sends a context acknowledgement message (Context Acknowledge message) to the second CP network element.
  • Context Acknowledge message Context Acknowledge message
  • the first CP network element after receiving the UE context response message, the first CP network element further determines whether the first session message needs to be sent to the UE, where the method for determining is determined by using the first CP network element.
  • the first CP network element performs all subsequent steps of the embodiment. If the first CP network element determines that the first session message does not need to be sent to the UE, the first CP network element performs the steps. S405 and S407.
  • step S405 the first CP network element sends a location update complete message, such as a TAU Accept message, to the UE.
  • the TAU accept message carries the second session message.
  • the second session message is a session management message.
  • the second session message is a session management message.
  • the session management message includes context information corresponding to multiple communication links in the session established between the UE and the network.
  • the session information may include an identifier of the communication link, QoS information used by the communication link, service flow information, and the like.
  • the session information may include updated communication link information determined according to the pending session.
  • the context establishment request message may further include one or more pending session management requests, where the pending session management request includes context information corresponding to the modified communication link in the session established between the UE and the network.
  • the specific information may include QoS information, service flow information, and the like.
  • the first CP network element sends a TAU reception message to the UE.
  • step S406 the UE sends a location update complete message, such as a TAU Complete message, to the first CP network element.
  • a location update complete message such as a TAU Complete message
  • the TAU completion message includes a session management response message.
  • the session management response message includes the result value of the session synchronization of the UE, such as the synchronization success or the synchronization failure.
  • the failure cause value is carried, for example, the communication link has been deleted.
  • the UE after receiving the TAU receiving message, the UE performs a session synchronization process according to the session management message in the TAU receiving message, and generates a TAU completion message including the session management response message after the session synchronization process is completed.
  • the session management response message is a response of the UE to the session management message.
  • step S407 the first CP network element sends a PDU session update message to the UP network element.
  • the first CP network element sends a PDU session update message to the user plane function network element to instruct the UP network element to perform a synchronous update process of the session context. If the PDU session update message indicates that the UE has deleted the session information, the PDU session update message indicates that the UP network element deletes the corresponding session information; if the PDU session update message indicates that the UE has performed the session synchronization process, the PDU session update message indicates that the UP network element performs The corresponding session synchronization process. After completing the session update process, the UP network element optionally performs step S408.
  • step S408 the UP network element sends a PDU session update response message to the first CP network element.
  • S407 and S408 are a PDU session establishment request message and a PDU session establishment response message.
  • the session management method shown in FIG. 5 may further include the steps. S409.
  • the first CP network element sends a Pending PDU session synchronized notification message to the PF network element. After receiving the pending PDU session synchronization notification message, the PF network element sets the session to the synchronization state.
  • first session message and the second session message in the embodiment of the present invention may be the same message.
  • the second session message may also be a message generated according to the first session message, and the specific generation method may be See implementation one.
  • the first session message and the second session message may be referred to in the first embodiment.
  • the newly connected CP of the UE can obtain the session context to be updated from the source CP, and execute the update process of the pending session. Further, if the UE has deleted the session information, the UE instructs the CP to initiate a process of updating the session to the UP.
  • FIG. 6 is a flowchart of a fourth session management method according to an embodiment of the present invention.
  • the method shown in Fig. 6 is performed based on the scene shown in Fig. 2.
  • the SM network element that is connected after the UE control plane connection is changed is referred to as the destination SM network element, and the SM that the UE connects before the connection change is referred to as the source SM network element.
  • the processing steps of the method shown in Figure 6 include:
  • step S501 the UE sends a location update request message to the MM network element.
  • the UE when the UE is in an idle state and needs to initiate a location update, the UE sends a Location Update Request message to the MM network element.
  • the location update request message may be a TAU request message.
  • the information of the destination SM network element is carried in the TAU request message.
  • step S502 the MM network element sends a PDU session relocation request message to the destination SM network element.
  • the MM network element After receiving the TAU request message from the MM, the MM network element determines the destination SM network element as the target session management network element according to the information of the destination SM in the TAU request message, and sends a PDU session relocation to the destination SM network element. Request message.
  • the PDU session relocation request message includes information for deriving the source SM network element address, and temporary user equipment identification information that the source SM network element allocates for the UE, such as a Globally Unique Temporary UE Identity (GUTI).
  • GUI Globally Unique Temporary UE Identity
  • the source SM network element here is a session management network element that previously manages the UE session context.
  • the TAU request message may further carry bearer status information of the session communication link established between the UE and the network.
  • step S503 the destination SM network element sends an SM Context Request message (SM Context) to the source SM network element. Request message).
  • SM Context SM Context Request message
  • the destination SM network element After the destination SM network element receives the PDU session relocation request message, the destination SM network element determines the address of the source SM network element according to the PDU session relocation request message. Then, the destination SM network element sends an SM Context Request message to the source SM network element.
  • step S504 the source SM network element sends an SM Context Response message to the destination SM network element.
  • the first session message is carried in the SM context response message.
  • the specific format and content of the first session message refer to the first embodiment, and details are not described herein.
  • step S505 the destination SM network element sends an SM Context Acknowledge message to the source SM network element.
  • the destination SM network element after receiving the SM context response message, the destination SM network element sends an SM context acknowledgement receiving message to the source SM network element to notify the source SM network element that the destination SM network element has received the SM context response message, and then the source SM The network element may delete the context information of the UE or mark the terminal context information as invalid or unavailable.
  • the destination SM network element after receiving the SM context response message, the destination SM network element further determines whether the first session message in the SM context response message needs to be sent to the UE, where the method for determining is as follows: When the network element determines that the first session message needs to be sent to the UE, the destination SM network element performs all subsequent steps of the embodiment. If the destination SM network element determines that the first session message does not need to be sent to the UE, the destination SM network element performs Possible steps such as steps S506, S512, S513, and S515.
  • step S506 the destination SM network element sends a PDU session relocation response message to the MM.
  • step 506 may be performed after step 504.
  • step S507 the MM sends a location update response message, such as a TAU response message, to the UE.
  • step S507 may be performed after step S501.
  • step S508 the destination SM network element sends a context setup request message to the AN network element (Context Setup Request message).
  • the context establishment request message carries the second session message.
  • the second session message is a session management message.
  • the second session message is a session management message.
  • the second session message includes context information corresponding to multiple communication links in the session established between the UE and the network.
  • the session information may include an identifier of the communication link, QoS information used by the communication link, service flow information, and the like.
  • the session information may include updated communication link information determined according to the pending session.
  • the context establishment request message includes one or more pending session management requests
  • the pending session management request includes context information corresponding to the modified communication link in the session established between the UE and the network.
  • the specific information may include QoS information, service flow information, and the like.
  • the destination SM network element sends a context establishment request message to the AN network element.
  • step S509 the AN network element sends an RRC reconfiguration message to the UE.
  • the RRC reconfiguration message includes one or more pending session management messages.
  • the AN network element after receiving the context setup request message, the AN network element sends an RRC reconfiguration message including one or more session management messages to the UE.
  • step S510 the UE sends an RRC reconfig response message to the AN network element.
  • the RRC reconfiguration response message includes one or more pending session management response messages.
  • the pending session management response message includes the result value of the UE performing the pending session synchronization, such as the synchronization success or the synchronization failure; further, when the synchronization fails, the failure cause value is included, for example, the communication link is deleted.
  • the UE after receiving the RRC reconfiguration message, the UE performs a session synchronization process according to the session management request in the RRC reconfiguration message, and generates an RRC reconfiguration response message including the session management response according to the RRC reconfiguration message.
  • the session management response message is a response message of the UE to the session management request.
  • step S511 the AN network element sends a context setup response message to the destination SM network element.
  • the context establishment response message includes a session management response message.
  • the AN network element after receiving the RRC reconfiguration response message, the AN network element sends a context setup response message to the destination SM network element.
  • the RRC reconfiguration response message includes a session management response message.
  • the session management response message includes the result value of the session synchronization of the UE, such as the synchronization success or the synchronization failure.
  • the failure cause value is carried, for example, the communication link has been deleted.
  • step S512 the destination SM network element sends a PDU session update message to the UP network element.
  • the destination SM network element sends a PDU session update message to the UP network element to instruct the UP network element to perform a synchronous update process of the session context. If the PDU session update message indicates that the UE has deleted the session information, the PDU session update message indicates that the UP network element deletes the corresponding session information; if the PDU session update message indicates that the UE has performed the session synchronization process, the PDU session update message indicates that the UP network element performs The corresponding session synchronization process. After completing the session update process, the UP network element optionally performs step S513.
  • step S513 the UP network element sends a PDU session update response message to the destination SM network element.
  • the session management method shown in FIG. 6 may further include the step 514, where the UE sends the session management response message to the destination SM network element.
  • the UE After receiving the RRC reconfiguration message sent by the AN network element, the UE generates a session management response message according to the session management request in the RRC reconfiguration message, and sends the session management response message to the destination SM network element. At this time, the session management response message is not included in the RRC reconfiguration response message and the context setup response message.
  • the session management method shown in FIG. 6 may further include the step S515, the destination SM network element sends a pending PDU session synchronized notification message to the PF network element. ). After receiving the pending PDU session synchronization notification message, the PF network element sets the session to the synchronization state.
  • first session message and the second session message in the embodiment of the present invention may be the same message.
  • the second session message may also be a message generated according to the first session message, and the specific generation method may be See implementation one.
  • the first session message and the second session message may be referred to in the first embodiment.
  • the embodiment of the present invention provides an SM and MM separation scenario.
  • the newly connected SM of the UE can obtain the session context to be updated from the source SM, and execute the update process of the pending session. Further, if the UE has deleted the session information, the UE instructs the SM to initiate a process of updating the session to the UP.
  • FIG. 7 is a flowchart of a fifth session management method according to an embodiment of the present invention.
  • the method shown in Fig. 7 is performed based on the scene shown in Fig. 2.
  • the SM network element that is connected after the UE control plane connection is changed is referred to as the destination SM network element, and the SM that the UE connects before the connection change is referred to as the source SM network element.
  • the processing steps of the method shown in Figure 7 include:
  • step S601 the UE sends a location update request message to the MM network element.
  • the UE when the UE is in an idle state and needs to initiate a location update, the UE sends a Location Update Request message to the MM network element.
  • the location update request message may be a TAU request message.
  • the information of the destination SM network element is carried in the TAU request message.
  • step S602 the MM network element sends a PDU session relocation request message to the destination SM network element.
  • the MM network element After receiving the TAU request message from the MM, the MM network element determines the destination SM network element as the target session management network element according to the information of the destination SM in the TAU request message, and sends a PDU session relocation to the destination SM network element. Request message.
  • the PDU session relocation request message includes information for deriving the address of the source SM network element, and the temporary user equipment identification information that the source SM network element allocates for the UE, such as a Globally Unique Temporary UE Identity (GUTI). .
  • the source SM network element here is a session management network element that previously manages the UE session context.
  • step S603 the destination SM network element sends an SM Context request message to the source SM network element.
  • the destination SM network element After the destination SM network element receives the PDU session relocation request message, the destination SM network element determines the address of the source SM network element according to the PDU session relocation request message. Then, the destination SM network element sends an SM Context Request message to the source SM network element.
  • step S604 the source SM network element sends an SM Context Response message to the destination SM network element.
  • the first session message is carried in the SM context response message.
  • the specific format and content of the first session message refer to the first embodiment, and details are not described herein.
  • step S605 the destination SM network element sends a Context Acknowledge message to the source SM network element.
  • the destination SM network element after receiving the SM context response message, the destination SM network element sends an SM context acknowledgement receiving message to the source SM network element to notify the source SM network element that the destination SM network element has received the SM context response message, and then the source SM The network element may delete the context information of the UE or mark the terminal context information as invalid or unavailable.
  • the destination SM network element may further determine whether the first session message needs to be sent to the UE, and the method for determining the method is as follows: When the first session message is sent to the UE, the destination SM network element performs all subsequent steps of the embodiment. If the destination SM network element determines that the first session message does not need to be sent to the UE, the destination SM network element performs steps S606 and S609. And the possible steps following S609.
  • step S606 the destination SM network element sends a PDU session relocation response message to the MM network element.
  • the PDU session relocation response message carries the second session message.
  • the second session message is a session management message.
  • the second session message is a session management message.
  • one or more session management messages are included in the session management message.
  • the one or more session management messages include context information corresponding to one or more communication links modified in the session established between the UE and the network.
  • the session management request gap may include updated session information, such as QoS information, service flow information, and the like.
  • the destination SM network element sends a PDU session relocation response message to the UE.
  • step S606 may be performed after step S604.
  • step S607 the MM network element sends a location update response message, such as a TAU response message, to the UE.
  • the TAU response message includes one or more session management messages.
  • the MM network element after receiving the PDU session relocation response message, the MM network element sends a TAU response message to the UE.
  • step S608 the UE sends a location update complete message, such as a TAU complete message, to the destination SM network element.
  • the TAU completion message includes one or more session management response messages.
  • the one or more session management response messages include the result value of the UE session synchronization, such as the synchronization success or the synchronization failure.
  • the failure cause value is carried, such as the communication link has been deleted.
  • the UE after receiving the TAU response message, the UE performs a session synchronization process according to the session management request in the TAU response message, and generates a TAU completion message including the session management response message after the session synchronization process is completed.
  • the session management response message is a response message of the UE to the session management request.
  • the UE sends a bit update completion message to the destination SM network element, and may forward the message to the destination SM through the MM network element.
  • step S609 the destination SM network element sends a PDU session update message to the UP network element.
  • the destination SM network element sends a PDU session update message to the UP network element to instruct the UP network element to perform a synchronous update process of the session context. If the PDU session update message indicates that the UE has deleted the session information, the PDU session update message indicates that the UP network element deletes the corresponding session information; if the PDU session update message indicates that the UE has performed the session synchronization process, the PDU session update message indicates that the UP network element performs The corresponding session synchronization process. After completing the session update process, the UP network element optionally performs step S610.
  • step S610 the UP network element sends a PDU session update response message to the destination SM network element.
  • the session management method shown in FIG. 7 may further include the step S611, the destination SM network element sends a pending PDU session synchronized notification message to the PF network element. After receiving the pending PDU session synchronization notification message, the PF network element sets the session to the synchronization state.
  • first session message and the second session message in the embodiment of the present invention may be the same message.
  • the second session message may also be a message generated according to the first session message, and the specific generation method may be See implementation one.
  • the specific generation method may be See implementation one.
  • the embodiment of the present invention provides an SM and MM separation scenario.
  • the newly connected SM of the UE can obtain the session context to be updated from the source SM, and execute the update process of the pending session. Further, if the UE has deleted the session information, the UE instructs the SM to initiate a process of updating the session to the UP.
  • FIG. 8 is a flowchart of a fifth session management method according to an embodiment of the present invention.
  • the method shown in Fig. 8 is performed based on the scene shown in Fig. 2.
  • the SM network element that is connected after the UE control plane connection is changed is referred to as the destination SM network element, and the SM that the UE connects before the connection is changed is referred to as the source SM network element.
  • the processing steps of the method include:
  • step S701 the UE sends a location update request message to the MM network element.
  • the UE when the UE is in an idle state and needs to initiate a location update, the UE sends a Location Update Request message to the MM network element.
  • the location update request message may be a TAU request message.
  • the information of the destination SM network element is carried in the TAU request message.
  • step S702 the MM network element sends a location update response message, such as a TAU response message, to the UE.
  • the MM network element determines the destination SM network element as the target session management network element, and carries the information of the destination SM network element to the UE in the TAU response message.
  • step S703 the UE sends a PDU session update request message to the destination SM network element.
  • the information about the source SM network element address is carried in the PDU session update request message.
  • the UE after receiving the TAU response message, the UE sends a PDU session update request message to the destination SM network element.
  • the PDU session update request message includes information for deriving the source SM network element address, and the information may be a temporary user equipment identity assigned by the source SM network element to the UE, such as a Globally Unique Temporary UE Identity (GUTI). ).
  • the source SM network element here is a session management network element that previously manages the UE session context. Further, the PDU session update request message may further carry bearer status information of the session communication link established between the UE and the network.
  • step S704 the destination SM network element sends an SM Context request message to the source SM network element.
  • the destination SM network element After the destination SM network element receives the PDU session relocation request message, the destination SM network element determines the address of the source SM network element according to the PDU session relocation request message. Then, the destination SM network element sends an SM Context Request message to the source SM network element.
  • step S705 the source SM network element sends an SM Context Response message to the destination SM network element.
  • the first session message is carried in the SM context response message.
  • the specific format and content of the first session message refer to the first embodiment, and details are not described herein.
  • step S706 the destination SM network element sends an SM context acknowledgement receiving message (Context) to the source SM network element. Acknowledge message).
  • Context SM context acknowledgement receiving message
  • the destination SM network element after receiving the SM context response message, the destination SM network element sends an SM context acknowledgement receiving message to the source SM network element to notify the source SM network element that the destination SM network element has received the SM context response message, and then the source SM The network element may delete the context information of the UE or mark the terminal context information as invalid or unavailable.
  • the destination SM network element may further determine whether the first session message needs to be sent to the UE, and the method for determining the method is as follows: When the first session message is sent to the UE, the destination SM network element performs all subsequent steps of the embodiment. If the destination SM network element determines that the first session message does not need to be sent to the UE, the destination SM network element performs steps S707 and S708. .
  • step S707 the destination SM network element sends a PDU session update message to the UP network element.
  • the destination SM network element sends a PDU session update message to the UP network element to instruct the UP network element to perform a synchronous update process of the session context. If the PDU session update message indicates that the UE has deleted the session information, the PDU session update message indicates that the UP network element deletes the corresponding session information; if the PDU session update message indicates that the UE has performed the session synchronization process, the PDU session update message indicates that the UP network element performs The corresponding session synchronization process. After completing the session update process, the UP network element optionally performs step 708.
  • step S708 the UP network element sends a PDU session update response message to the destination SM network element.
  • step S709 the destination SM network element sends a PDU session update response message to the UE.
  • the PDU session update response message carries the second session message.
  • the second session message is a session management message.
  • the second session message is a session management message.
  • the session management message may include one or more pending session management messages.
  • the one or more session management messages include context information corresponding to multiple communication links in the session established between the UE and the network.
  • the session information may be included in the session management message. Such as QoS information, business flow information, etc.
  • the destination SM network element sends a PDU session update response message to the UE.
  • step S710 the UE sends a PDU session update complete message to the destination SM network element.
  • the PDU session update completion message includes one or session management response information.
  • the session management response information includes the synchronization result of the UE, such as the synchronization success or the synchronization failure of each session, when the synchronization is lost. In the event of a failure, the cause of the failure is carried, such as the communication link has been deleted.
  • the UE after receiving the PDU session update response message, the UE performs a session synchronization process according to the session management request in the PDU session update response message, and generates a PDU session update completion information including session management response information after the session synchronization process is completed.
  • the session management response information is response information of the UE to the session management request.
  • the session management method shown in FIG. 8 may further include the step S711, the destination SM network element sends a pending PDU session synchronized notification message to the PF network element. After receiving the pending PDU session synchronization notification message, the PF network element sets the session to the synchronization state.
  • first session message and the second session message in the embodiment of the present invention may be the same message.
  • the second session message may also be a message generated according to the first session message, and the specific generation method may be See implementation one.
  • the specific generation method may be See implementation one.
  • the embodiment of the present invention provides an SM and MM separation scenario.
  • the newly connected SM of the UE can obtain the session context to be updated from the source SM, and execute the update process of the pending session. Further, if the UE has deleted the session information, the UE instructs the SM to initiate a process of updating the session to the UP.
  • FIG. 9 is a schematic structural diagram of a session management network element according to an embodiment of the present invention.
  • the session management network element may be used to perform Embodiments 1 to 6 and FIG. 3 to FIG. 8 executed by the control plane network element connected after the UE control plane connection is changed in each of the foregoing method embodiments.
  • the session management method for example, the session management network element may be the first CP network element in the first to third embodiments.
  • the session management network element may perform the foregoing embodiment 1 to And the steps performed by the first CP network element in FIG. 3 to FIG.
  • the session management network element may be the destination SM network element in Embodiments 4 to 6 when the session management network element is the destination SM network.
  • the session management network element may perform the steps performed by the target SM network element in Embodiments 4 to 6 and FIG. 6 to FIG. 8.
  • the main functions of the session management network element are introduced in the following. One to six and Figures 3 to 8.
  • the session management network element includes:
  • the receiving unit 801 is configured to receive a user equipment UE context response message from the second control plane network element, where the UE context response message carries a first session message, where the first session message is a session message to be processed;
  • the sending unit 803 is configured to send the second session message to the user equipment according to the UE context response message.
  • the first session message and the second session message are the same.
  • the second session message is generated based on the first session message.
  • the second session message is a session management message
  • the sending unit 803 sends the second session message to the user equipment according to the UE context response message, which specifically includes:
  • the second session message is a session management message
  • the sending unit 803 sends the second session message to the user equipment according to the UE context response message, which specifically includes:
  • the second session message is a session management message
  • the sending unit 803 sends the second session message to the user equipment according to the UE context response message, which specifically includes:
  • the session management message is sent to the user equipment by radio resource control RRC reconfiguration.
  • the sending unit 803 sends the second session message to the user equipment according to the UE context response message, which specifically includes:
  • the processing unit 802 is configured to determine, according to the communication link bearer state information of the user equipment that is acquired in advance, a communication link that is in an activated state;
  • the sending unit 803 sends the second session message to the user equipment, which specifically includes:
  • the receiving unit 801 is further used to: before receiving the UE context response message from the second control plane network element:
  • the receiving unit 801 is further used to: before receiving the UE context response message from the second control plane network element:
  • the PDU session relocation request message carries information for deriving the address of the second control plane network element.
  • the receiving unit 801 is further used to: before receiving the UE context response message from the second control plane network element:
  • the PDU session update request message carries information for deriving the address of the second control plane network element.
  • the sending unit 803 is further configured to send a context request message to the second control plane network element;
  • the receiving, by the receiving unit 801, the UE context response message from the second control plane network element specifically includes: receiving, by the second control plane network element, the UE context response message sent according to the context request message.
  • the first control plane network element is a destination SM
  • the second control plane network element is a source SM
  • the UE context response message is an SM context response message.
  • the sending unit 803 is further configured to send a PDU session synchronization notification message to the policy function PF network element.
  • the session management network element in the embodiment of the present invention can implement the session management method in the foregoing method embodiment, and can implement session management in a scenario in which the control plane connection of the user equipment changes.
  • FIG. 10 is a schematic structural diagram of another session management network element according to an embodiment of the present invention.
  • the session management network element shown in FIG. 10 may be used to perform the first to sixth embodiments and the session management in FIG. 3 to FIG. 8 performed by the control plane network element connected after the UE control plane connection is changed in each of the foregoing method embodiments.
  • the method for example, the session management network element may be the first CP network element in the first to third embodiments.
  • the session management network element may perform the foregoing embodiments 1 to 3 and the figure. 3 to the steps performed by the first CP network element in FIG. 5; for example, the session management network element may be the destination SM network element in the fourth embodiment to the sixth embodiment.
  • the session management network element may perform the steps performed by the target SM network element in Embodiments 4 to 6 and FIG. 6 to FIG. 8.
  • the following describes the main functions of the session management network element in combination with the specific structure of the session management network element, which is not involved. See Sections 1 through 6 and Figures 3 through 8 for details.
  • the session management network element may be composed of a processor 901, a memory 902, a transceiver 903, and the like.
  • the processor 901, the memory 902, and the transceiver 903 may be previously connected by one or more buses.
  • Said The bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • the communication bus 1004 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the transceiver 903 is configured to implement the functions of the transmitting unit 803 and the receiving unit 801 in FIG. 8, and the memory 902 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 902 may include a random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage.
  • the processor 901 executes the program stored in the memory 902, and specifically includes:
  • the transceiver 903 receives the user equipment UE context response message from the second control plane network element under the control of the processor 901, where the UE context response message carries the first session message, and the first session message is the to-be-processed session. And the transceiver 903 sends the second session message to the user equipment according to the UE context response message under the control of the processor 901.
  • the first session message and the second session message are the same.
  • the second session message is generated based on the first session message.
  • the second session message is a session management message
  • the transceiver 903 sends the second session message to the user equipment according to the UE context response message under the control of the processor 901, which specifically includes:
  • the second session message is a session management message
  • the transceiver 903 sends the second session message to the user equipment according to the UE context response message under the control of the processor 901, which specifically includes:
  • the second session message is a session management message
  • the transceiver 903 sends the second session message to the user equipment according to the UE context response message under the control of the processor 901, which specifically includes:
  • the transceiver 903 sends the second session message to the user equipment according to the UE context response message under the control of the processor 901, including:
  • the processor 901 is further configured to determine, according to the communication link bearer state information of the user equipment that is acquired in advance, the communication link that is in an active state;
  • the transceiver 903 sends the second session message to the user equipment under the control of the processor 901, which specifically includes:
  • the transceiver 903 is further used to: before receiving the UE context response message from the second control plane network element under the control of the processor 901:
  • the transceiver 903 is further used to: before receiving the UE context response message from the second control plane network element under the control of the processor 901:
  • the PDU session relocation request message carries information for deriving the address of the second control plane network element.
  • the transceiver 903 is further used to: before receiving the UE context response message from the second control plane network element under the control of the processor 901:
  • the PDU session update request message carries information for deriving the address of the second control plane network element.
  • the transceiver 903 is further configured to send a context request message to the second control plane network element under the control of the processor 901;
  • the first control plane network element is a destination SM
  • the second control plane network element is a source SM
  • the UE context response message is an SM context response message.
  • the transceiver 903 is also used to control the strategy under the control of the processor 901.
  • the PF network element can send a PDU session synchronization notification message.
  • the session management network element in the embodiment of the present invention can implement the session management method in the foregoing method embodiment, and can implement session management in a scenario in which the control plane connection of the user equipment changes.
  • the processor 901 may be composed of an integrated circuit (IC), for example, may be composed of a single packaged IC, or may be composed of a plurality of packaged ICs having the same function or different functions.
  • the processor 901 may include only a central processing unit (CPU), or may be a GPU, a digital signal processor (DSP), and a control chip in the transceiver 903 (for example, A combination of baseband chips).
  • the CPU may be a single operation core, and may also include multiple operation cores.
  • the transceiver 903 is configured to establish a communication channel, so that the session management network element is connected to the receiving device through the communication channel, thereby implementing data transmission between the session management network elements.
  • the transceiver 903 may include a wireless local area network (WLAN) module, a Bluetooth module, a base band module, and the like, and a radio frequency (RF) circuit corresponding to the communication module.
  • WLAN wireless local area network
  • RF radio frequency
  • WCDMA wideband code division multiple access
  • HSDPA high speed downlink packet access
  • the transceiver 903 is used to control communication of components in the session management network element and can support direct memory access.
  • transceivers in transceiver 903 are typically in the form of integrated circuit chips and can be selectively combined without necessarily including all transceivers and corresponding antenna groups.
  • transceiver 903 may include only baseband chips, radio frequency chips, and corresponding antennas to provide communication functionality in a cellular communication system.
  • the session management network element can be connected to a cellular network or the Internet via a wireless communication connection established by the transceiver, such as wireless local area network access or WCDMA access.
  • a communication module, such as a baseband module, in the transceiver may be integrated into the processor, typically an APQ+MDM series platform such as that provided by Qualcomm.
  • the radio frequency circuit is used for receiving and transmitting signals during information transmission and reception or during a call. For example, after the downlink information of the network device is received, it is processed by the processor; in addition, the data designed for the uplink is sent to the network device.
  • radio frequency circuits include well-known circuits for performing these functions, including but not limited to antenna systems, radio frequency transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codecs (codec A chipset, a Subscriber Identity Module (SIM) card, memory, and the like.
  • the RF circuit can communicate with the network and other devices through wireless communication.
  • Wireless communication can use any communication standard or protocol, including but not limited to global system of mobile communication (GSM), general packet radio General packet radio service (gprs), code division multiple access (CDMA), wideband code division multiple access (WCDMA), high-speed uplink packet access technology (high speed uplink packet access, referred to as HSUPA), long term evolution (LTE), e-mail, short messaging service (SMS), and the like.
  • GSM global system of mobile communication
  • gprs general packet radio General packet radio service
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • HSUPA high-speed uplink packet access technology
  • LTE long term evolution
  • SMS short messaging service
  • the present invention further provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in various embodiments of the calling method provided by the present invention.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (English: read-only memory, abbreviated as: ROM) or a random access memory (English: random access memory, abbreviation: RAM).
  • the techniques in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution in the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM. , a disk, an optical disk, etc., including a number of instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform portions of various embodiments or embodiments of the present invention.
  • a computer device which may be a personal computer, server, or network device, etc.

Landscapes

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

Abstract

本发明实施例涉及无线通信领域，尤其涉及一种会话管理方法及网元。所述会话管理方法，包括：第一控制面网元从第二控制面网元接收用户设备UE上下文响应消息，所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备。本发明实施例的会话管理方法及网元，能够在用户设备的控制面连接发生变更的场景中实现会话的管理。

Description

会话管理方法及网元 技术领域
本发明实施例涉及无线通信领域，尤其涉及一种会话管理方法及网元。
背景技术
演进分组系统(英文：Evolved Packet System，简称：EPS)的会话管理中，用户设备和网络侧之间需要同步会话的上下文，即会话中的承载上下文需要同步。其中，承载上下文的建立、修改和删除可由用户设备发起或者由网络侧发起。目前，当网络侧发起承载上下文的建立、修改和删除流程时，网络侧需要立即将该会话的信息(删除承载、修改承载或者建立承载)通知给用户设备(英文：User Equipment，简称：UE)，使得UE侧与网络侧会话信息同步。当网络侧发起上述流程时，若UE处于空闲状态，则网络会发起寻呼流程使得UE进入连接态，并将修改的会话信息同步给UE。为了尽可能的减少空口信令的开销，提出了一种异步的会话管理流程，即当网络侧发起会话修改时，发起的会话修改可以不立即同步给UE，则当UE处于空闲态时，网络侧节点不向UE发起寻呼流程，并将发起的会话修改请求记录为等待处理，保存该会话修改请求消息。若在会话修改请求的信息未发送到UE的期间UE向网络侧发起位置更新流程时，网络侧如何处理该等待处理的消息，目前还没有对应的会话管理方法。
发明内容
本发明实施例提供了会话管理方法及网元，以在用户设备的控制面连接发生变更的场景中实现会话的管理。
第一方面，本发明实施例提供了一种会话管理方法，包括：第一控制面网元从第二控制面网元接收用户设备UE上下文响应消息，所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备。
在本发明实施例方案中，当用户设备的控制面连接发生改变并且用户设备的源控制面网元(对应第二控制面网元)上存在需要同步给用户设备的待处理会话消息时， 第一控制面网元(用户设备新连接至的控制面网元)从第二控制面网元上获取UE上下文响应消息，其中在UE上下文响应消息中携第一会话消息，所述第一会话消息是上述待处理的会话消息；第一控制面网元根据接收到的UE上下文响应消息向用户设备发送第二会话消息，由此以将待处理的会话消息发送给用户设备，从而在用户设备的控制面连接发生变更的场景中实现会话的管理。
在一种可能的设计中，所述第一会话消息和第二会话消息相同。在此种实现方式下，第一控制面网元接收到UE上下文响应消息后，将上下文响应消息中携带的待处理会话消息作为第二会话消息发送给用户设备。
在一种可能的设计中，第二会话消息是根据第一会话消息生成的。在此种实现方式中，第一控制面网元接收到UE上下文响应消息后，根据UE上下文响应消息中携带的第一会话消息生成第二会话消息，并且将第二会话消息作为待处理的会话消息发送给用户设备。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
所述第一控制面网元根据所述第一会话消息，向移动管理MM网元发送协议数据单元PDU会话重新定位响应消息，所述PDU会话重新定位响应消息中携带所述会话管理消息，以使所述MM网元将所述会话管理消息发送给所述用户设备。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
所述第一控制面网元根据所述第一会话消息，向所述用户设备发送位置更新接受消息，所述位置更新接受消息中携带所述会话管理消息。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
所述第一控制面网元根据所述第一会话消息，向所述用户设备接入的接入网网元发送上下文建立请求消息，所述上下文建立请求消息中携带所述会话管理消息，以使得所述接入网网元通过无线资源控制RRC重新配置将所述会话管理消息发送给所述用户设备。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
所述第一控制面网元根据所述第一会话消息，向所述用户设备发送PDU会话更新响应消息，所述PDU会话更新响应消息中携带所述会话管理消息。
在一种可能的设计中，所述第一控制面网元将所述第二会话消息发送给所述用户设备，包括：
所述第一控制面网元根据预先获取的所述用户设备的通信链路承载状态信息，确定处于激活状态的通信链路；
所述第一控制面网元将与处于激活状态的通信链路所对应的第二会话消息发送给所述用户设备。
在一种可能的设计中，所述第一控制面网元从第二控制面网元接收UE上下文响应消息之前，所述方法还包括：
所述第一控制面网元接收所述用户设备发送的位置更新请求消息；所述位置更新请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述第一控制面网元从第二控制面网元接收UE上下文响应消息之前，所述方法还包括：
所述第一控制面网元接收MM网元发送的PDU会话重新定位请求消息；所述PDU会话重新定位请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述第一控制面网元从第二控制面网元接收UE上下文响应消息之前，所述方法还包括：
所述第一控制面网元接收所述用户设备发送的PDU会话更新请求消息；所述PDU会话更新请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述第一控制面网元从第二控制面网元接收UE上下文响应消息，包括：
所述第一控制面网元向所述第二控制面网元发送上下文请求消息；
所述第一控制面网元接收所述第二控制面网元根据所述上下文请求消息发送的所述UE上下文响应消息。
在一种可能的设计中，所述第一控制面网元为目的SM，所述第二控制面网元为源SM，所述UE上下文响应消息为SM上下文响应消息。
在一种可能的设计中，所述方法还包括：
所述第一控制面网元向策略功能PF网元发送PDU会话同步通知消息。
另一方面，本发明实施例提供了一种会话管理网元，该网元具有实现上述方法实际中第一控制面网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，所述网元部署于第一控制面网元中，包括：接收单元和发送单元；所述接收单元，用于从第二控制面网元接收用户设备UE上下文响应消息，所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；发送单元，用于根据所述UE上下文响应消息，将第二会话消息发送给用户设备。
本发明实施例方案中，所述发送单元还用于执行上述方法实施例中所涉及的发送步骤，所述接收单元还用于执行上述方法实施例中所涉及的接收步骤。
在一种可能的设计中，所述会话管理网元部署于第一控制面网元中，包括：发送器、接收器和处理器，所述接收器用于在所述处理器的控制下从第二控制面网元接收UE上下文响应消息；所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；所述发送器，用于在所述处理器的控制下根据所述UE上下文响应消息，将第二会话消息发送给用户设备。
本发明实施例方案中，所述发送器还用于执行上述方法实施例中所涉及的发送步骤，所述接收器还用于执行上述方法实施例中所涉及的接收步骤。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述会话管理网元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
本发明实施例的会话管理方法及网元，能够在用户设备的控制面连接发生变更的场景中实现会话的管理。
附图说明
为了更清楚地说明本发明的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，对于本领域普通技术人员而言，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本发明的一种可能的应用场景示意图；
图2是本发明的另一种可能的应用场景示意图；
图3是本发明实施例一会话管理方法的流程图；
图4是本发明实施例二会话管理方法的流程图；
图5是本发明实施例三会话管理方法的流程图；
图6是本发明实施例四会话管理方法的流程图；
图7是本发明实施例五会话管理方法的流程图；
图8是本发明实施例六会话管理方法的流程图；
图9是本发明实施例提供的一种会话管理网元的结构示意图；
图10是本发明实施例提供的另一种会话管理网元的结构示意图。
具体实施方式
本发明实施例提供的会话管理方案可以应用于各类通信系统的会话管理中，尤其可以应用在用户设备连接的控制面网元发生改变的会话管理中。例如，本发明实施例方案可以应用在EPS系统、5G网络等通信系统中。
以下将结合具体系统场景对本发明实施例的会话管理方法进行详细说明。需要指出的是，本发明实施例描述的系统场景是为了更加清楚地说明本发明实施例的技术方案，并不构成对本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
图1是本发明的一种可能的应用场景示意图。在图1所示的场景中，包括UE、接入网(英文：Access Network，简称:AN)网元、用户面(英文：User Plane，简称：UP)网元、控制面(英文：Control Plane，简称：CP)网元和策略功能(英文：Policy Function，简称：PF)网元。
图2是本发明的另一种可能的应用场景示意图。图2所示场景在图1的基础上将CP网元进一步分为移动管理(英文：Mobility Management，简称：MM)网元和会话管理(英文：Session Management，简称：SM)如图1所示，核心网中的CP功能(function)和UP功能分离，可选的，CP网元和UP网元可以分别为多个，CP网元用于信令的交互，UP网元用于数据传输。
为方便理解，首先结合附图对本发明实施例的应用场景进行说明。参见图1，为本发明实施例提供的一种应用场景示意图。该应用场景中包括用户设备，接入网设备，以及核心网的控制面功能网元、用户面功能网元、策略功能网元。其中，如图2所示，在一些实施例中，所述控制面功能网元可以包括移动性管理网元和会话管理网元。
其中，所述用户设备可以为手机、平板电脑、笔记本电脑、个人计算机(英文全称：personal computer，PC)、超级移动个人计算机(英文全称：Ultra-mobile Personal Computer，UMPC)、上网本、个人数字助理(英文全称：Personal Digital Assistant，PDA)、车载设备等用户设备。为方便描述，本申请中，上面提到的设备统称为用户设备或UE。所述接入网设备可以为演进的通用移动通信系统陆地无线接入网(英文：evolved UMTS terrestrial radio access network，简称：E-UTRAN)中的接入设备，如eNB(evolved Node B)，或者下一代接入网络(NextGen Access Network，NG AN)中的接入网设备。所述控制面功能网元用于实现控制面功能，具体用于信令的交互。当所述控制面功能网元可以包括移动性管理网元和会话管理网元时，所述移动性管理网元用于执行所述用户设备注册管理、可达性检测、控制面和用户面的网络功能的分配、移动性管理、寻址和标识管理等过程，所述会话管理网元用于管理UE的IP业务和非IP业务连接的建立和管理该连接对应的用户面。所述用户面功能网元用于实现用户面功能，具体用于用户数据的传输。所述策略功能网元用于策略决策、策略提供、事件上报等。所述策略包括，如QoS控制策略、计费策略、会话管理策略、移动性管理策略等。
需要说明的是，在实际应用部署中，图1中的控制面网元的数目可以不止一个，图2中的会话管理网元的数目也可以不止一个。
下述会话管理方法的实施例以所述用户设备为UE为例进行说明。
实施例一
图3是本发明实施例一会话管理方法的流程图。图3所示方法可以基于图1、图2或其它相似的场景中执行。例如在图1所示的场景中，UE控制面连接发生改变之后连接的控制面网元称为第一CP网元，UE在所述控制面连接发生改变之前连接的源CP称为第二CP网元；又例如在图2所示的场景中，UE控制面连接发生改变之后连接的控制面网元称为目的SM网元，UE在所述控制面连接发生改变之前连接的控制面网元称为源SM网元。在图1的场景中，执行本发明实施例方法的执行主体为第一CP网元，在图2的场景中，执行本发明实施例方法的执行主体为目的SM网元，为便于说明，本实施例方案中，以第一CP网元作为执行主体进行说明。
如图3所示，本发明实施例方法的处理步骤包括：
在步骤S201：第一CP网元从第二CP网元接收UE上下文响应消息；所述UE上下文响应消息中携带第一会话消息，所述第一会话消息是待处理的会话消息。
在步骤S202：第一CP网元根据UE上下文响应消息，将第二会话消息发送给所述UE。
上述第一会话消息可以是会话管理消息，例如，第一会话消息包括第二CP网元接收到的未处理的会话管理消息和/或第二CP网元未发送给UE的会话管理消息，更为具体的，第一会话消息可以是第二CP网元根据接收到的未处理的会话管理消息生成的NAS层的会话管理消息，进一步，在该会话管理消息中可以包含待处理(pending)会话信息。
在一种可能的实现方式中，第二会话消息与第一会话消息相同，例如，第二会话消息是与第一会话消息相同的会话管理消息。
在另一种可能的实现方式中，第二会话消息是根据第一会话消息生成的，例如第一会话消息是第一会话管理消息，第二会话消息是第二会话管理消息；第一CP网元根据UE上下文响应消息，将第二会话消息发送给UE，包括：第一CP网元根据第一会话管理消息生成第二会话管理消息；第一CP网元将第二会话管理消息发送给UE。例如第一会话管理消息是NAS层的会话管理消息，第二会话消息是根据NAS层的会话管理消息生成的会话管理请求消息。
在本发明实施例方案中，第一CP网元接收到上下文响应消息后，还需要进一步确定是否需要向UE发送待处理的会话消息，具体方式包括：第一CP网元确定从第二CP网元接收到UE上下文响应消息中是否包含第一会话消息，如果包含，则第一CP网元执行向第二CP网元发送第二会话消息的步骤，例如第一CP网元直接将第一会话消息作为第二会话消息发送给UE；或者根据第一会话消息生成第二会话消息，并发送给UE。
在另一种可能的方式中：第一CP网元预先从UE处获取UE与网络之间建立的会话通信链路的状态信息；第一CP网元接收到UE上下文响应消息后，第一CP网元根据所述状态信息确定是否存在处于激活状态的通信链路以及第一会话消息中是否有与处于激活状态的通信链路对应的会话消息，如果有，则第一CP网元将与处于激活状态的通信链路对应的会话消息作为第二会话消息发送给UE；或者，第一CP网元根据与处于激活状态的通信链路对应的会话消息生成第二会话消息，并且将第二会话消息发送给UE。
在本发明实施例方案中，第一会话消息和第二会话消息中均可以包含pending会话信息。
在另外一种可能的实施例中，为了实现将第二CP网元未发送到UE的会话上下文经过第一CP网元发送到UE的目的，第一CP网元接收到的UE上下文响应消息中可以直接携带需要同步到UE的pending会话信息，对应的第一CP网元将UE上下文响应消息中的pending会话信息发送给UE。
其中，上文所涉及的pending会话信息可以包括第二CP网元接收到的原始pending会话信息，第一CP网元接收到该原始pending会话信息需要解析、转化等处理；进一步，上述pending会话信息还可以包括无需转化可以直接发送给UE的会话信息。更为具体的，上述pending会话信息包括UE和网络间建立的会话中的一个或者多个通信链路所对应的上下文信息，例如，pending会话信息中包括所述一个或者多个通信链路的标识信息、状态信息、Qos信息和业务流信息等。
实施例二
图4是本发明实施例二会话管理方法的流程图。图4所示方法基于图1所示场景执行。在本发明实施例方案中，UE控制面连接发生改变之后连接的控制面网元称为第一CP网元，UE在所述控制面连接发生改变之前连接的源CP称为第二CP网元。图4所示方法的处理步骤包括：
在步骤S301中，UE向第一CP网元发送位置更新请求消息。
例如，当UE处于空闲状态并且需要发起位置更新时，UE向第一CP网元发送位置更新请求消息。
所述位置更新请求消息可以是跟踪区更新(英文：Tracking Area Update，简称：TAU)请求消息(TAU request message)。当位置更新请求消息是TAU请求消息时，TAU请求消息中可以携带用于推演UE在CP连接改变之前所连接的第二CP网元地址的信息，以及第二CP网元为UE分配的用户设备标识信息，如全球唯一临时UE标识(英文：Globally Unique Temporary UE Identity，简称：GUTI)。进一步，在TAU请求消息中还可以携带UE与网络之间建立的会话通信链路的状态信息，如承载状态信息。
在步骤S302中，第一CP网元向第二CP网元发送上下文请求消息(Context request message)。
在该步骤中，第一CP网元根据TAU请求消息中所携带的信息推演出第二CP网元的地址。第一CP网元向第二CP网元发送上下文请求消息。
在步骤S303中，第二CP网元向第一CP网元发送UE上下文响应消息(Context response message)。
所述UE上下文响应消息中携带第一会话消息，第一会话消息的具体格式和内容，参见实施例一，不再赘述。
在步骤S304中，第一CP网元向第二CP网元发送上下文确认接收消息(Context Acknowledge message)。
具体地，第一CP网元在接收到UE上下文响应消息后，向第二CP网元发送上下文确认接收消息，以告知第二CP网元第一CP网元已接到到UE上下文响应消息，进而第二CP网元可删除UE的上下文信息或者标记UE上下文信息为无效的或者不可用的。
可选的，第一CP网元在接收到UE上下文响应消息后，还进一步确定是否需要将UE上下文响应消息中的第一会话消息发送给UE，其中确定的方法参见实施例一，当第一CP网元确定需要将第一会话消息发送到UE时，第一CP网元执行本实施例的后续所有步骤，如果第一CP网元确定不需要第一会话消息发送到UE，则第一CP网元则执行步骤S305、S310以及S310中可能的步骤。
在步骤S305中，第一CP网元向UE发送位置更新完成消息，如TAU接收消息(TAU Accept message)。
需要说明的是，步骤S305可以位于步骤S304之后任意时候，如在其它可能的实施例方案中，步骤S305也可位于本发明实施例所述的步骤S312之后，此处不做限制。
在步骤S306中，第一CP网元向AN网元发送上下文建立请求消息(Context Setup request message)。
其中，在上下文建立请求消息中携带第二会话消息，可选的，第二会话消息为会话管理消息，例如，第二会话消息为会话管理消息。具体的，在会话管理消息中包括UE和网络间建立的会话中的多个通信链路对应的上下文信息。具体地，会话信息中可以包括通信链路的标识，通信链路使用的Qos信息，业务流信息等。该会话信息可以包含根据pending会话确定的更新的通信链路信息。
进一步的，上下文建立请求消息中还可以包含一个或者多个pending会话管理请求，pending会话管理请求中包含UE和网络间建立的会话中的被修改的通信链路对应的上下文信息。具体的信息可以包含QoS信息，业务流信息等。
具体地，当第一会话消息需要更新到UE时，例如第一会话消息中携带的pending会话信息需要更新到UE时，第一CP网元向接入网设备发送上下文建立请求消息。
其中，当第一会话消息中有多个pending会话时，可以是多个pending会话放在一个会话管理消息中，或者分别包含在多个会话管理消息中。
进一步可选的，上述上下文建立请求消息也可以为上下文修改请求消息或者其它的用于会话管理的请求消息。
在步骤S307中，AN网元向UE发送无线资源控制(英文：Radio Resource Control，简称：RRC)重新配置消息(RRC reconfig message)。
其中，RRC重新配置消息中包括一个或者多个会话管理消息。
具体地，AN网元在接收到上下文建立请求消息后，向UE发送包括一个或者多个会话管理消息的RRC重新配置消息。
UE接收到会话管理消息后，执行将pengding会话发送到UE的过程。
在步骤S308中，UE向AN网元中发送RRC重新配置响应消息(RRC reconfig response message)。
其中，RRC重新配置响应消息中包括会话管理响应消息。会话管理响应消息中包括UE的会话同步的结果值，如同步成功或者同步失败，当同步失败时，会携带失败的原因值，如通信链路已被删除等。
具体地，UE在接收到RRC重新配置消息后，根据RRC重新配置消息中的会话管理请求更新UE上的会话信息，并根据RRC重新配置消息生成包括会话管理响应消息的RRC重新配置响应消息。会话管理响应消息为UE对会话管理请求的响应消息。
在步骤S309中，AN网元向第一CP网元发送上下文建立响应消息(Context Setup response message)。
其中，上下文建立响应消息中包括会话管理响应消息。
具体地，AN网元在接收到RRC重新配置响应消息后，向第一CP网元发送上下文建立响应消息。
在步骤S310中，第一CP网元向UP网元发送协议数据单元(英文：Protocol Data Unit，简称：PDU)会话更新消息(PDU session update message)。
具体地，第一CP网元向用户面功能网元发送PDU会话更新消息，以指示UP网元执行将会话上下文的同步更新流程。如PDU会话更新消息表明UE已删除会话信息，则PDU会话更新消息指示UP网元删除相应的会话信息；如PDU会话更新消息表明UE已进行会话同步过程，则PDU会话更新消息指示UP网元执行相应的会话同步过程。UP网元在完成会话更新流程后，可选的执行步骤311。
在步骤S311中，UP网元向第一CP网元发送PDU会话更新响应消息(PDU session update response message)。
在本发明实施例的一种具体实施方式中，图4所示会话管理方法还可以包括步骤S312，UE将会话管理响应消息发送给第一CP网元。
具体地，UE在接收到AN网元发送的RRC重新配置消息后，根据RRC重新配置消息中的会话管理请求生成会话管理响应消息，并将所示会话管理响应消息发送给第一CP网元。此时，在步骤S308中的RRC重配响应消息和步骤S309上下文建立响应消息中不包括会话管理响应消息。
若第一功能网元选择了新的用户面网元为新的，则S310和S311为PDU会话建立请求消息和PDU会话建立响应消息。
此外，在本发明实施例的一种具体实施方式中，图4所示会话管理方法还可以包括步骤S313，第一CP网元向PF网元发送pending PDU会话同步通知消息(Pending PDU session synchronized notification message)。PF网元接收到pending PDU会话同步通知消息后，设置会话为同步状态。
需要说明的是，本发明实施例中所涉及的第一会话消息和第二会话消息可以是相同的消息，另外，第二会话消息也可以是根据第一会话消息生成的消息，具体生成方法可以参见实施一。另外本实施例中关于第一会话消息和第二会话消息的在本实施例未说明的部分可以参见实施例一。
本发明实施例方案，在UE所连接的CP发生变化时，UE新连接的CP能够从源CP上获取待更新的会话上下文，执行pending会话的更新流程。进一步的如果UE已经删除会话信息，则UE会指示CP向UP发起会话的更新流程。
实施例三
图5是本发明实施例三会话管理方法的流程图。图5所示方法基于图1所示场景执行。在本发明实施例方案中，UE控制面连接发生改变之后连接的控制面网元称为 第一CP网元，UE在所述控制面连接发生改变之前连接的源CP称为第二CP网元。图5所示方法的处理步骤包括：
在步骤S401中，UE向第一CP网元发送发送位置更新请求消息。
例如，当UE处于空闲状态并且需要发起位置更新时，UE向第一CP网元发送位置更新请求消息。
所述位置更新请求消息可以是跟踪区更新(英文：Tracking Area Update，简称：TAU)请求消息(TAU request message)。当位置更新请求消息是TAU请求消息时，TAU请求消息中可以携带用于推演UE在CP连接改变之前所连接的第二CP网元地址的信息，以及第二CP网元为UE分配的用户设备标识信息，如全球唯一临时UE标识(英文：Globally Unique Temporary UE Identity，简称：GUTI)。进一步，在TAU请求消息中还可以携带UE与网络之间建立的会话通信链路的承载状态信息。
在步骤S402中，第一CP网元向第二CP网元发送上下文请求消息(Context request message)。
在该步骤中，第一CP网元根据TAU请求消息中所携带的信息推演出第二CP网元的地址。第一CP网元向第二CP网元发送上下文请求消息。
在步骤S403中，第二CP网元向第一CP网元发送UE上下文响应消息(Context response message)。
所述UE上下文响应消息中携带第一会话消息，第一会话消息的具体格式和内容，参见实施例一，不再赘述。
在步骤S404中，第一CP网元向第二CP网元发送上下文确认接收消息(Context Acknowledge message)。
可选的，第一CP网元在接收到UE上下文响应消息后，还进一步确定是否需要将第一会话消息发送到UE中，其中确定的方法参见实施例一，当第一CP网元确定需要将第一会话消息发送到UE时，第一CP网元执行本实施例的后续所有步骤，如果第一CP网元确定不需要将第一会话消息发送到UE，则第一CP网元执行步骤S405和S407。
在步骤S405中，第一CP网元向UE发送位置更新完成消息，如TAU接受消息(TAU Accept message)。
其中，TAU接受消息中携带第二会话消息，可选的，第二会话消息为会话管理消息，例如，第二会话消息为会话管理消息。具体的，在会话管理消息中包括UE和网络间建立的会话中的多个通信链路对应的上下文信息。具体地，会话信息中可以包括通信链路的标识，通信链路使用的Qos信息，业务流信息等。该会话信息可以包含根据pending会话确定的更新的通信链路信息。
进一步的，上下文建立请求消息中还可以包含一个或者多个pending会话管理请求，pending会话管理请求中包含UE和网络间建立的会话中的被修改的通信链路对应的上下文信息。具体的信息可以包含QoS信息，业务流信息等。
具体地，当pending会话信息需要更新到UE时，第一CP网元向UE发送TAU接收消息。
在步骤S406中，UE向第一CP网元发送位置更新完成消息，如TAU完成消息(TAU Complete message)。
其中，TAU完成消息中包括会话管理响应消息。会话管理响应消息中包括UE的会话同步的结果值，如同步成功或者同步失败，当同步失败时，会携带失败的原因值，如通信链路已被删除等。
具体地，UE在接收到TAU接收消息后，根据TAU接收消息中的会话管理消息执行会话同步过程，并在会话同步过程执行完成后生成包括会话管理响应消息的TAU完成消息。会话管理响应消息为UE对会话管理消息的响应。
在步骤S407中，第一CP网元向UP网元发送PDU会话更新消息。
具体地，第一CP网元向用户面功能网元发送PDU会话更新消息，以指示UP网元执行会话上下文的同步更新流程。如PDU会话更新消息表明UE已删除会话信息，则PDU会话更新消息指示UP网元删除相应的会话信息；如PDU会话更新消息表明UE已进行会话同步过程，则PDU会话更新消息指示UP网元执行相应的会话同步过程。UP网元在完成会话更新流程后，可选的执行步骤S408。
在步骤S408中，UP网元向第一CP网元发送PDU会话更新响应消息(PDU session update response message)。
若第一功能网元选择了的UP网元为新的，则S407和S408为PDU会话建立请求消息和PDU会话建立响应消息。
在本发明实施例的一种具体实施方式中，图5所示会话管理方法还可以包括步骤 S409，第一CP网元向PF网元发送pending PDU会话同步通知消息(Pending PDU session synchronized notification message)。PF网元接收到pending PDU会话同步通知消息后，设置会话为同步状态。
需要说明的是，本发明实施例中所涉及的第一会话消息和第二会话消息可以是相同的消息，另外，第二会话消息也可以是根据第一会话消息生成的消息，具体生成方法可以参见实施一。另外本实施例中关于第一会话消息和第二会话消息在本实施例中未说明的部分可以参见实施例一。
本发明实施例方案，在UE所连接的CP发生变化时，UE新连接的CP能够从源CP上获取待更新的会话上下文，执行pending会话的更新流程。进一步的如果UE已经删除会话信息，则UE会指示CP向UP发起会话的更新流程。
实施例四
图6是本发明实施例四会话管理方法的流程图。图6所示方法基于图2所示场景执行。在本发明实施例方案中，UE控制面连接发生改变之后连接的SM网元称为目的SM网元，UE在所述连接发生改变之前连接的SM称为源SM网元。图6所示方法的处理步骤包括：
在步骤S501中，UE向MM网元发送位置更新请求消息。
例如，当UE处于空闲状态并且需要发起位置更新时，UE向MM网元发送位置更新请求消息。所述位置更新请求消息可以是TAU请求消息(TAU request message)。其中，在TAU请求消息中携带目的SM网元的信息。
在步骤S502中，MM网元向目的SM网元发送PDU会话重新定位请求消息(PDU session relocation request message)。
其中，MM网元接收到来自MM的TAU请求消息后，根据TAU请求消息中的目的SM的信息，将目的SM网元确定为目标会话管理网元，并向目的SM网元发送PDU会话重新定位请求消息。PDU会话重新定位请求消息中包括用于推演源SM网元地址的信息，以及源SM网元为UE分配的临时用户设备标识信息，如GUTI(Globally Unique Temporary UE Identity，全球唯一临时UE标识)。这里的源SM网元为之前管理UE会话上下文的会话管理网元。进一步，在TAU请求消息中还可以携带UE与网络之间建立的会话通信链路的承载状态信息。
在步骤S503中，目的SM网元向源SM网元发送SM上下文请求消息(SM Context  request message)。
在该步骤中，目的SM网元在接收到PDU会话重新定位请求消息后，目的SM网元根据PDU会话重新定位请求消息中确定出源SM网元的地址。然后，目的SM网元向源SM网元发送SM上下文请求消息。
在步骤S504中，源SM网元向目的SM网元发送SM上下文响应消息(SM Context response message)。
在SM上下文响应消息中携带第一会话消息，第一会话消息的具体格式和内容，参见实施例一，不再赘述。
在步骤S505中，目的SM网元向源SM网元发送SM上下文确认接收消息(SM Context Acknowledge message)。
具体地，目的SM网元在接收到SM上下文响应消息后，向源SM网元发送SM上下文确认接收消息，以告知源SM网元目的SM网元已接到到SM上下文响应消息，进而源SM网元可删除UE的上下文信息或者标记终端上下文信息为无效的或者不可用的。
可选的，目的SM网元在接收到SM上下文响应消息后，还进一步确定是否需要将SM上下文响应消息中的第一会话消息发送到UE中，其中确定的方法参见实施例一，当目的SM网元确定需要将第一会话消息发送到UE时，目的SM网元执行本实施例的后续所有步骤，如果目的SM网元确定不需要将第一会话消息发送到UE，则目的SM网元执行步骤S506、S512、S513以及S515等可能的步骤。
在步骤S506中，目的SM网元向MM发送PDU会话重新定位响应消息(PDU session relocation response message)。
需要说明的是，在本发明实施例具体实施的过程中，步骤506在步骤504之后即可。
在步骤S507中，MM向UE发送位置更新响应消息，如TAU响应消息(TAU response message)。
需要说明的是，在本发明实施例具体实施的过程中，步骤S507在步骤S501之后即可。
在步骤S508中，目的SM网元向AN网元发送上下文建立请求消息(Context Setup  request message)。
其中，上下文建立请求消息中携带第二会话消息，可选的，第二会话消息为会话管理消息，例如，第二会话消息为会话管理消息。具体的，在第二会话消息中包括UE和网络间建立的会话中的多个通信链路对应的上下文信息。具体地，会话信息中可以包括通信链路的标识，通信链路使用的的Qos信息，业务流信息等。该会话信息可以包含根据pending会话确定的更新的通信链路信息。
进一步的，上下文建立请求消息中包含一个或者多个pending会话管理请求，pending会话管理请求中包含UE和网络间建立的会话中的被修改的通信链路对应的上下文信息。具体的信息可以包含QoS信息，业务流信息等。
具体地，当pending会话信息需要更新到UE时，目的SM网元向AN网元发送上下文建立请求消息。
在步骤S509中，AN网元向UE发送RRC重新配置消息(RRC reconfig message)。
其中，其中，RRC重新配置消息中包括一个或者多个pending会话管理消息。
具体地，AN网元在接收到上下文建立请求消息后，向UE发送包括一个或者多个会话管理消息的RRC重新配置消息。
在步骤S510中，UE向AN网元中发送RRC重新配置响应消息(RRC reconfig response message)。
其中，RRC重新配置响应消息中包括一个或者多个pending会话管理响应消息。pending会话管理响应消息中包括UE的执行pending会话同步的结果值，如同步成功，或者同步失败；进一步的当同步失败时，包含失败的原因值，如通信链路被删除。
具体地，UE在接收到RRC重新配置消息后，UE根据RRC重新配置消息中的会话管理请求执行会话同步过程，并根据RRC重新配置消息生成包括会话管理响应的RRC重新配置响应消息。会话管理响应消息为UE对会话管理请求的响应消息。
在步骤S511中，AN网元向目的SM网元发送上下文建立响应消息(Context Setup response message)。
其中，上下文建立响应消息中包括会话管理响应消息。
具体地，AN网元在接收到RRC重新配置响应消息后，向目的SM网元发送上下文建立响应消息。
其中，RRC重新配置响应消息中包括会话管理响应消息。会话管理响应消息中包括UE的会话同步的结果值，如同步成功或者同步失败，当同步失败时，会携带失败的原因值，如通信链路已被删除等。
在步骤S512中，目的SM网元向UP网元发送PDU会话更新消息。
具体地，目的SM网元向UP网元发送PDU会话更新消息，以指示UP网元执行会话上下文的同步更新流程。如PDU会话更新消息表明UE已删除会话信息，则PDU会话更新消息指示UP网元删除相应的会话信息；如PDU会话更新消息表明UE已进行会话同步过程，则PDU会话更新消息指示UP网元执行相应的会话同步过程。UP网元在完成会话更新流程后，可选的执行步骤S513。
在步骤S513中，UP网元向目的SM网元发送PDU会话更新响应消息(PDU session update response message)。
在本发明实施例的一种具体实施方式中，图6所示会话管理方法还可以包括步骤514，UE将会话管理响应消息发送给目的SM网元。
具体地，UE在接收到AN网元发送的RRC重新配置消息后，UE根据RRC重新配置消息中的会话管理请求生成会话管理响应消息，并将所示会话管理响应消息发送给目的SM网元。此时，在RRC重配响应消息和上下文建立响应消息中不包括会话管理响应消息。
此外，在本发明实施例的一种具体实施方式中，图6所示会话管理方法还可以包括步骤S515，目的SM网元向PF网元发送pending PDU会话同步通知消息(Pending PDU session synchronized notification message)。PF网元接收到pending PDU会话同步通知消息后，设置会话为同步状态。
需要说明的是，本发明实施例中所涉及的第一会话消息和第二会话消息可以是相同的消息，另外，第二会话消息也可以是根据第一会话消息生成的消息，具体生成方法可以参见实施一。另外本实施例中关于第一会话消息和第二会话消息在本实施例中未说明的部分可以参见实施例一。
本发明实施例提供了一种SM和MM分离场景下，当UE所连接的SM发生变化时，UE新连接的SM能够从源SM上获取待更新的会话上下文，执行pending会话的更新流程。进一步的如果UE已经删除会话信息，则UE会指示SM向UP发起会话的更新流程。
实施例五
图7是本发明实施例五会话管理方法的流程图。图7所示方法基于图2所示场景执行。在本发明实施例方案中，UE控制面连接发生改变之后连接的SM网元称为目的SM网元，UE在所述连接发生改变之前连接的SM称为源SM网元。图7所示方法的处理步骤包括：
在步骤S601中，UE向MM网元发送位置更新请求消息。
例如，当UE处于空闲状态并且需要发起位置更新时，UE向MM网元发送位置更新请求消息。所述位置更新请求消息可以是TAU请求消息(TAU request message)。其中，在TAU请求消息中携带目的SM网元的信息。
在步骤S602中，MM网元向目的SM网元发送PDU会话重新定位请求消息(PDU session relocation request message)。
其中，MM网元接收到来自MM的TAU请求消息后，根据TAU请求消息中的目的SM的信息，将目的SM网元确定为目标会话管理网元，并向目的SM网元发送PDU会话重新定位请求消息。PDU会话重新定位请求消息中包括用于推演源SM网元的地址的信息，以及源SM网元为UE分配的临时用户设备标识信息，如GUTI(Globally Unique Temporary UE Identity，全球唯一临时UE标识)。这里的源SM网元为之前管理UE会话上下文的会话管理网元。
在步骤S603中，目的SM网元向源SM网元发送SM上下文请求消息(SM Context request message)。
在该步骤中，目的SM网元在接收到PDU会话重新定位请求消息后，目的SM网元根据PDU会话重新定位请求消息中确定出源SM网元的地址。然后，目的SM网元向源SM网元发送SM上下文请求消息。
在步骤S604中，源SM网元向目的SM网元发送SM上下文响应消息(SM Context response message)。
在SM上下文响应消息中携带第一会话消息，第一会话消息的具体格式和内容，参见实施例一，不再赘述。
在步骤S605中，目的SM网元向源SM网元发送SM上下文确认接收消息(Context Acknowledge message)。
具体地，目的SM网元在接收到SM上下文响应消息后，向源SM网元发送SM上下文确认接收消息，以告知源SM网元目的SM网元已接到到SM上下文响应消息，进而源SM网元可删除UE的上下文信息或者标记终端上下文信息为无效的或者不可用的。
进一步地，目的SM网元在接收到SM上下文响应消息后，目的SM网元可进一步确定是否需要将第一会话消息发送到UE，其中确定的方法参见实施例一，当目的SM网元确定需要将第一会话消息发送到UE时，目的SM网元执行本实施例的后续所有步骤，如果目的SM网元确定不需要将第一会话消息发送到UE，则目的SM网元执行步骤S606、S609以及S609后续可能的步骤。
在步骤S606中，目的SM网元向MM网元发送会话重新定位响应消息(PDU session relocation response message)。
其中，PDU会话重新定位响应消息中携带第二会话消息，可选的，第二会话消息为会话管理消息，例如，第二会话消息为会话管理消息。具体的，在会话管理消息中包括一个或者多个会话管理消息。一个或者多个会话管理消息中包括UE和网络间建立的会话中被修改一个或者多个通信链路对应的上下文信息。具体地，会话管理请求罅隙中可以包括更新的会话信息，如QoS信息，业务流信息等。
具体地，当pending会话信息需要更新到UE时，目的SM网元向UE发送PDU会话重定位响应消息。
需要说明的是，在本发明实施例具体实施的过程中，步骤S606在步骤S604之后即可。
在步骤S607中，MM网元向UE发送位置更新响应消息，如TAU响应消息(TAU response message)。
其中，TAU响应消息中包括一个或者多个会话管理消息。
具体地，MM网元在接收到PDU会话重新定位响应消息后，向UE发送TAU响应消息。
在步骤S608中，UE向目的SM网元发送位置更新完成消息，如TAU完成消息。
其中，TAU完成消息中包括一个或者多个会话管理响应消息。一个或多个会话管理响应消息中包括UE会话同步的结果值，如同步成功或者同步失败，当同步失败时，会携带失败的原因值，如通信链路已被删除等。
具体地，UE在接收到TAU响应消息后，根据TAU响应消息中的会话管理请求执行会话同步过程，并在会话同步过程执行完成后生成包括会话管理响应消息的TAU完成消息。会话管理响应消息为UE对会话管理请求的响应消息。
具体地，UE向目的SM网元发送位的置更新完成消息，可以经MM网元转发至目的SM。
在步骤S609中，目的SM网元向UP网元发送PDU会话更新消息。
具体地，目的SM网元向UP网元发送PDU会话更新消息，以指示UP网元执行会话上下文的同步更新流程。如PDU会话更新消息表明UE已删除会话信息，则PDU会话更新消息指示UP网元删除相应的会话信息；如PDU会话更新消息表明UE已进行会话同步过程，则PDU会话更新消息指示UP网元执行相应的会话同步过程。UP网元在完成会话更新流程后，可选的执行步骤S610。
在步骤S610中，UP网元向目的SM网元发送PDU会话更新响应消息(PDU session update response message)。
在本发明实施例的一种具体实施方式中，图7所示会话管理方法还可以包括步骤S611，目的SM网元向PF网元发送pending PDU会话同步通知消息(Pending PDU session synchronized notification message)。PF网元接收到pending PDU会话同步通知消息后，设置会话为同步状态。
需要说明的是，本发明实施例中所涉及的第一会话消息和第二会话消息可以是相同的消息，另外，第二会话消息也可以是根据第一会话消息生成的消息，具体生成方法可以参见实施一。另外本实施例中关于第一会话消息和第二会话消息的在本实施例未说明的部分可以参见实施例一。
本发明实施例提供了一种SM和MM分离场景下，当UE所连接的SM发生变化时，UE新连接的SM能够从源SM上获取待更新的会话上下文，执行pending会话的更新流程。进一步的如果UE已经删除会话信息，则UE会指示SM向UP发起会话的更新流程。
实施例六
图8是本发明实施例五会话管理方法的流程图。图8所示方法基于图2所示场景执行。在本发明实施例方案中，UE控制面连接发生改变之后连接的SM网元称为目的SM网元，UE在所述连接发生改变之前连接的SM称为源SM网元。图8所示方 法的处理步骤包括：
在步骤S701中，UE向MM网元发送位置更新请求消息。
例如，当UE处于空闲状态并且需要发起位置更新时，UE向MM网元发送位置更新请求消息。所述位置更新请求消息可以是TAU请求消息(TAU request message)。其中，在TAU请求消息中携带目的SM网元的信息。
在步骤S702中，MM网元向UE发送位置更新响应消息，如TAU响应消息(TAU response message)。
具体地，MM网元在接收到来自UE的TAU请求消息后，将目的SM网元确定为目标会话管理网元，并将目的SM网元的信息携带在TAU响应消息总发送给UE。
在步骤S703中，UE向目的SM网元发送PDU会话更新请求消息(PDU session update request message)。
其中，在PDU会话更新请求消息中携带用于确定源SM网元地址的信息。
具体地，UE在接收到TAU响应消息后，向目的SM网元发送PDU会话更新请求消息。PDU会话更新请求消息中包括用于推演源SM网元地址的信息，该信息可以为源SM网元为UE分配的临时用户设备身份标识，如GUTI(Globally Unique Temporary UE Identity，全球唯一临时UE标识)。这里的源SM网元为之前管理UE会话上下文的会话管理网元。进一步，在PDU会话更新请求消息中还可以携带UE与网络之间建立的会话通信链路的承载状态信息。
在步骤S704中，目的SM网元向源SM网元发送SM上下文请求消息(SM Context request message)。
在该步骤中，目的SM网元在接收到PDU会话重新定位请求消息后，目的SM网元根据PDU会话重新定位请求消息中确定出源SM网元的地址。然后，目的SM网元向源SM网元发送SM上下文请求消息。
在步骤S705中，源SM网元向目的SM网元发送SM上下文响应消息(SM Context response message)。
在SM上下文响应消息中携带第一会话消息，第一会话消息的具体格式和内容，参见实施例一，不再赘述。
在步骤S706中，目的SM网元向源SM网元发送SM上下文确认接收消息(Context  Acknowledge message)。
具体地，目的SM网元在接收到SM上下文响应消息后，向源SM网元发送SM上下文确认接收消息，以告知源SM网元目的SM网元已接到到SM上下文响应消息，进而源SM网元可删除UE的上下文信息或者标记终端上下文信息为无效的或者不可用的。
进一步地，目的SM网元在接收到SM上下文响应消息后，目的SM网元可进一步确定是否需要将第一会话消息发送到UE，其中确定的方法参见实施例一，当目的SM网元确定需要将第一会话消息发送到UE时，目的SM网元执行本实施例的后续所有步骤，如果目的SM网元确定不需要将第一会话消息发送到UE，则目的SM网元执行步骤S707和S708。
在步骤S707中，目的SM网元向UP网元发送PDU会话更新消息。
具体地，目的SM网元向UP网元发送PDU会话更新消息，以指示UP网元执行会话上下文的同步更新流程。如PDU会话更新消息表明UE已删除会话信息，则PDU会话更新消息指示UP网元删除相应的会话信息；如PDU会话更新消息表明UE已进行会话同步过程，则PDU会话更新消息指示UP网元执行相应的会话同步过程。UP网元在完成会话更新流程后，可选的执行步骤708。
在步骤S708中，UP网元向目的SM网元发送PDU会话更新响应消息(PDU session update response message)。
在步骤S709中，目的SM网元向UE发送PDU会话更新响应消息。
其中，PDU会话更新响应消息中携带第二会话消息，可选的，第二会话消息为会话管理消息，例如，第二会话消息为会话管理消息。具体的，在会话管理消息可以包括一个或者多个pending会话管理消息。所述一个或多个会话管理消息中包括UE和网络间建立的会话中的多个通信链路对应的上下文信息。具体地，会话管理消息中可以包括更新的会话信息。如Qos信息，业务流信息等。
具体地，当pending会话信息需要更新到UE时，目的SM网元向UE发送PDU会话更新响应消息。
在步骤S710中，UE向目的SM网元发送PDU会话更新完成消息。
其中，PDU会话更新完成消息中包括一个或者会话管理响应信息。会话管理响应信息中包括UE的的同步结果，，如每个会话的同步成功或者同步失败，当同步失 败时，会携带失败的原因值，如通信链路已被删除。
具体地，UE在接收到PDU会话更新响应消息后，根据PDU会话更新响应消息中的会话管理请求执行会话同步过程，并在会话同步过程执行完成后生成包括会话管理响应信息的PDU会话更新完成信息。会话管理响应信息为UE对会话管理请求的响应信息。
在本发明实施例的一种具体实施方式中，图8所示会话管理方法还可以包括步骤S711，目的SM网元向PF网元发送pending PDU会话同步通知消息(Pending PDU session synchronized notification message)。PF网元接收到pending PDU会话同步通知消息后，设置会话为同步状态。
需要说明的是，本发明实施例中所涉及的第一会话消息和第二会话消息可以是相同的消息，另外，第二会话消息也可以是根据第一会话消息生成的消息，具体生成方法可以参见实施一。另外本实施例中关于第一会话消息和第二会话消息的在本实施例未说明的部分可以参见实施例一。
本发明实施例提供了一种SM和MM分离场景下，当UE所连接的SM发生变化时，UE新连接的SM能够从源SM上获取待更新的会话上下文，执行pending会话的更新流程。进一步的如果UE已经删除会话信息，则UE会指示SM向UP发起会话的更新流程。
图9是本发明实施例提供的一种会话管理网元的结构示意图。如图9所示，所述会话管理网元可以用于执行上述各方法实施例中UE控制面连接发生改变之后所连接的控制面网元所执行的实施例一至六以及图3至图8中的会话管理方法，例如，所述会话管理网元可以是实施例一至三中的第一CP网元，当会话管理网元是第一CP网元时，会话管理网元可以执行上述实施例一至三以及图3至图5中第一CP网元所执行的步骤；又例如，所述会话管理网元可以是实施例四至图六中的目的SM网元，当会话管理网元是目的SM网元时，会话管理网元可以执行实施例四至图六以及图6至图8中目的SM网元所执行的步骤，以下将对会话管理网元的主要功能进行介绍，未涉及部分可以参见实施例一至六以及图3至图8。
具体的，会话管理网元包括：
接收单元801，用于从第二控制面网元接收用户设备UE上下文响应消息，所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；
发送单元803，用于根据所述UE上下文响应消息，将第二会话消息发送给用户设备。
在一种可能的设计中，所述第一会话消息和第二会话消息相同。
在一种可能的设计中，第二会话消息是根据第一会话消息生成的。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述发送单元803根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向移动管理MM网元发送协议数据单元PDU会话重新定位响应消息，所述PDU会话重新定位响应消息中携带所述会话管理消息，以使所述MM网元将所述会话管理消息发送给所述用户设备。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述发送单元803根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向所述用户设备发送位置更新接受消息，所述位置更新接受消息中携带所述会话管理消息。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述发送单元803根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向所述用户设备接入的接入网网元发送上下文建立请求消息，所述上下文建立请求消息中携带所述会话管理消息，以使得所述接入网网元通过无线资源控制RRC重新配置将所述会话管理消息发送给所述用户设备。
在一种可能的设计中，所述发送单元803根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向所述用户设备发送PDU会话更新响应消息，所述PDU会话更新响应消息中携带所述第二会话消息。
在一种可能的设计中，处理单元802，用于根据预先获取的所述用户设备的通信链路承载状态信息，确定处于激活状态的通信链路；
所述发送单元803将所述第二会话消息发送给所述用户设备，具体包括执行：
将与处于激活状态的通信链路所对应的第二会话消息发送给所述用户设备。
在一种可能的设计中，所述接收单元801从第二控制面网元接收UE上下文响应消息之前还用于：
接收所述用户设备发送的位置更新请求消息；所述位置更新请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述接收单元801从第二控制面网元接收UE上下文响应消息之前还用于：
接收MM网元发送的PDU会话重新定位请求消息；所述PDU会话重新定位请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述接收单元801从第二控制面网元接收UE上下文响应消息之前还用于：
接收所述用户设备发送的PDU会话更新请求消息；所述PDU会话更新请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述发送单元803还用于向所述第二控制面网元发送上下文请求消息；
所述接收单元801从第二控制面网元接收UE上下文响应消息，具体包括执行：接收所述第二控制面网元根据所述上下文请求消息发送的所述UE上下文响应消息。
在一种可能的设计中，所述第一控制面网元为目的SM，所述第二控制面网元为源SM，所述UE上下文响应消息为SM上下文响应消息。
在一种可能的设计中，所述发送单元803，还用于向策略功能PF网元发送PDU会话同步通知消息。
本发明实施例的会话管理网元能够实现上述方法实施例中的会话管理方法，能够在用户设备的控制面连接发生变更的场景中实现会话的管理。
图10是本发明实施例的另一种会话管理网元的结构示意图。图10所示的会话管理网元可以用于执行上述各方法实施例中UE控制面连接发生改变之后所连接的控制面网元所执行的实施例一至六以及图3至图8中的会话管理方法，例如，所述会话管理网元可以是实施例一至三中的第一CP网元，当会话管理网元是第一CP网元时，会话管理网元可以执行上述实施例一至三以及图3至图5中第一CP网元所执行的步骤；又例如，所述会话管理网元可以是实施例四至图六中的目的SM网元，当会话管理网元是目的SM网元时，会话管理网元可以执行实施例四至图六以及图6至图8中目的SM网元所执行的步骤，以下将结合会话管理网元的具体结构对会话管理网元的主要功能进行介绍，未涉及部分可以参见实施例一至六以及图3至图8。
如图10所示，会话管理网元可以由处理器901、存储器902及收发器903等组成，处理器901、存储器902与收发器903之前可以通过一条或多条总线连接。所述 总线可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。通信总线1004可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
收发器903用于实现图8中发送单元803和接收单元801的功能，存储器902，用于存放程序。具体地，程序可以包括程序代码，程序代码包括计算机操作指令。存储器902可能包含随机存取存储器(random access memory，简称RAM)，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。处理器901执行存储器902中所存放的程序，具体包括：
收发器903在处理器901的控制下，从第二控制面网元接收用户设备UE上下文响应消息，所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；以及收发器903在处理器901的控制下，根据所述UE上下文响应消息，将第二会话消息发送给用户设备。
在一种可能的设计中，所述第一会话消息和第二会话消息相同。
在一种可能的设计中，第二会话消息是根据第一会话消息生成的。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述收发器903在处理器901的控制下根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向移动管理MM网元发送协议数据单元PDU会话重新定位响应消息，所述PDU会话重新定位响应消息中携带所述会话管理消息，以使所述MM网元将所述会话管理消息发送给所述用户设备。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述收发器903在处理器901的控制下根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向所述用户设备发送位置更新接受消息，所述位置更新接受消息中携带所述会话管理消息。
在一种可能的设计中，所述第二会话消息为会话管理消息；
所述收发器903在处理器901的控制下根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向所述用户设备接入的接入网网元发送上下文建立请求 消息，所述上下文建立请求消息中携带所述会话管理消息，以使得所述接入网网元通过无线资源控制RRC重新配置将所述会话管理消息发送给所述用户设备。
在一种可能的设计中，所述收发器903在处理器901的控制下根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
根据所述第一会话消息，向所述用户设备发送PDU会话更新响应消息，所述PDU会话更新响应消息中携带所述第二会话消息。
在一种可能的设计中，处理器901还用于根据预先获取的所述用户设备的通信链路承载状态信息，确定处于激活状态的通信链路；
所述收发器903在处理器901的控制下将所述第二会话消息发送给所述用户设备，具体包括执行：
将与处于激活状态的通信链路所对应的第二会话消息发送给所述用户设备。
在一种可能的设计中，所述收发器903在处理器901的控制下从第二控制面网元接收UE上下文响应消息之前还用于：
接收所述用户设备发送的位置更新请求消息；所述位置更新请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述收发器903在处理器901的控制下从第二控制面网元接收UE上下文响应消息之前还用于：
接收MM网元发送的PDU会话重新定位请求消息；所述PDU会话重新定位请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述收发器903在处理器901的控制下从第二控制面网元接收UE上下文响应消息之前还用于：
接收所述用户设备发送的PDU会话更新请求消息；所述PDU会话更新请求消息中携带用于推演所述第二控制面网元地址的信息。
在一种可能的设计中，所述收发器903在处理器901的控制下还用于向所述第二控制面网元发送上下文请求消息；
所述收发器903在处理器901的控制下从第二控制面网元接收UE上下文响应消息，具体包括执行：接收所述第二控制面网元根据所述上下文请求消息发送的所述UE上下文响应消息。
在一种可能的设计中，所述第一控制面网元为目的SM，所述第二控制面网元为源SM，所述UE上下文响应消息为SM上下文响应消息。
在一种可能的设计中，所述收发器903在处理器901的控制下，还用于向策略功 能PF网元发送PDU会话同步通知消息。
本发明实施例的会话管理网元能够实现上述方法实施例中的会话管理方法，能够在用户设备的控制面连接发生变更的场景中实现会话的管理。
上述处理器901可以由集成电路(integrated circuit，简称IC)组成，例如可以由单颗封装的IC所组成，也可以由连接多颗相同功能或不同功能的封装IC而组成。举例来说，处理器901可以仅包括中央处理器(central processing unit，简称CPU)，也可以是GPU、数字信号处理器(digital signal processor，简称DSP)、及收发器903中的控制芯片(例如基带芯片)的组合。在本发明实施方式中，CPU可以是单运算核心，也可以包括多运算核心。
收发器903用于建立通信信道，使会话管理网元通过通信信道以连接至接收设备，从而实现会话管理网元之间的数据传输。收发器903可以包括无线局域网(wireless local area network，简称WLAN)模块、蓝牙模块、基带(base band)模块等通信模块，以及通信模块对应的射频(radio frequency，简称RF)电路，用于进行无线局域网络通信、蓝牙通信、红外线通信及/或蜂窝式通信系统通信，例如宽带码分多重接入(wideband code division multiple access，简称WCDMA)及/或高速下行封包存取(high speed downlink packet access，简称HSDPA)。收发器903用于控制会话管理网元中的各组件的通信，并且可以支持直接内存存取(direct memory access)。
在本发明的不同实施方式中，收发器903中的各种收发器一般以集成电路芯片(integrated circuit chip)的形式出现，并可进行选择性组合，而不必包括所有收发器及对应的天线组。例如，收发器903可以仅包括基带芯片、射频芯片以及相应的天线以在一个蜂窝通信系统中提供通信功能。经由收发器建立的无线通信连接，例如无线局域网接入或WCDMA接入，会话管理网元可以连接至蜂窝网(cellular network)或因特网(internet)。在本发明的一些可选实施方式中，收发器中的通信模块，例如基带模块可以集成到处理器中，典型的如高通(qualcomm)公司提供的APQ+MDM系列平台。射频电路用于信息收发或通话过程中接收和发送信号。例如，将网络设备的下行信息接收后，给处理器处理；另外，将设计上行的数据发送给网络设备。通常，射频电路包括用于执行这些功能的公知电路，包括但不限于天线系统、射频收发机、一个或多个放大器、调谐器、一个或多个振荡器、数字信号处理器、编解码(codec)芯片组、用户身份模块(SIM)卡、存储器等等。此外，射频电路还可以通过无线通信与网络和其他设备通信。无线通信可以使用任一通信标准或协议，包括但不限于全球移动通讯系统(global system of mobile communication，简称GSM)、通用分组无线 服务(general packet radio service，简称gprs)、码分多址(code division multiple access，简称CDMA)、宽带码分多址(wideband code division multiple access，简称WCDMA)、高速上行行链路分组接入技术(high speed uplink packet access，简称HSUPA)、长期演进(long term evolution，简称LTE)、电子邮件、短消息服务(short messaging service，简称SMS)等。
具体实现中，本发明还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时可包括本发明提供的呼叫方法的各实施例中的部分或全部步骤。的存储介质可为磁碟、光盘、只读存储记忆体(英文：read-only memory，简称：ROM)或随机存储记忆体(英文：random access memory，简称：RAM)等。
本领域的技术人员可以清楚地了解到本发明实施例中的技术可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本发明实施例中的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例或者实施例的某些部分的方法。
本说明书中各个实施例之间相同相似的部分互相参见即可。尤其，对于会话管理网元实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例中的说明即可。以上的本发明实施方式并不构成对本发明保护范围的限定。

Claims (28)

  1. 一种会话管理方法，其特征在于，包括：
    第一控制面网元从第二控制面网元接收用户设备UE上下文响应消息，所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；
    所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备。
  2. 根据权利要求1所述的方法，其特征在于，所述第一会话消息和第二会话消息相同。
  3. 根据权利要求1所述的方法，其特征在于，所述第二会话消息是根据所述第一会话消息生成的。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第二会话消息为会话管理消息；
    所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
    所述第一控制面网元根据所述第一会话消息，向移动管理MM网元发送协议数据单元PDU会话重新定位响应消息，所述PDU会话重新定位响应消息中携带所述会话管理消息，以使所述MM网元将所述会话管理消息发送给所述用户设备。
  5. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第二会话消息为会话管理消息；
    所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
    所述第一控制面网元根据所述第一会话消息，向所述用户设备发送位置更新接受消息，所述位置更新接受消息中携带所述会话管理消息。
  6. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第二会话消息为会话管理消息；
    所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
    所述第一控制面网元根据所述第一会话消息，向所述用户设备接入的接入网网元发送上下文建立请求消息，所述上下文建立请求消息中携带所述会话管理消 息，以使得所述接入网网元通过无线资源控制RRC重新配置将所述会话管理消息发送给所述用户设备。
  7. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第二会话消息为会话管理消息；
    所述第一控制面网元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，包括：
    所述第一控制面网元根据所述第一会话消息，向所述用户设备发送PDU会话更新响应消息，所述PDU会话更新响应消息中携带所述会话管理消息。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述第一控制面网元将所述第二会话消息发送给所述用户设备，包括：
    所述第一控制面网元根据预先获取的所述用户设备的通信链路承载状态信息，确定处于激活状态的通信链路；
    所述第一控制面网元将与处于激活状态的通信链路所对应的第二会话消息发送给所述用户设备。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第一控制面网元从第二控制面网元接收UE上下文响应消息之前，所述方法还包括：
    所述第一控制面网元接收所述用户设备发送的位置更新请求消息；所述位置更新请求消息中携带用于推演所述第二控制面网元地址的信息。
  10. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第一控制面网元从第二控制面网元接收UE上下文响应消息之前，所述方法还包括：
    所述第一控制面网元接收MM网元发送的PDU会话重新定位请求消息；所述PDU会话重新定位请求消息中携带用于推演所述第二控制面网元地址的信息。
  11. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第一控制面网元从第二控制面网元接收UE上下文响应消息之前，所述方法还包括：
    所述第一控制面网元接收所述用户设备发送的PDU会话更新请求消息；所述PDU会话更新请求消息中携带用于推演所述第二控制面网元地址的信息。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述第一控制面网元从第二控制面网元接收UE上下文响应消息，包括：
    所述第一控制面网元向所述第二控制面网元发送上下文请求消息；
    所述第一控制面网元接收所述第二控制面网元根据所述上下文请求消息发送的所述UE上下文响应消息。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述第一控制面网元为目的SM，所述第二控制面网元为源SM，所述UE上下文响应消息为SM上下文响应消息。
  14. 根据权利要求1至13中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一控制面网元向策略功能PF网元发送PDU会话同步通知消息。
  15. 一种会话管理网元，其特征在于，所述网元部署于第一控制面网元中，包括：
    接收单元，用于从第二控制面网元接收用户设备UE上下文响应消息，所述UE上下文响应消息中携带第一会话消息，所述第一会话消息为待处理的会话消息；
    发送单元，用于根据所述UE上下文响应消息，将第二会话消息发送给用户设备。
  16. 根据权利要求15所述的网元，其特征在于，所述第一会话消息和第二会话消息相同。
  17. 根据权利要求15所述的网元，其特征在于，所述第二会话消息是根据所述第一会话消息生成的。
  18. 根据权利要求15至17中任一项所述的网元，其特征在于，所述第二会话消息为会话管理消息；
    所述发送单元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
    根据所述第一会话消息，向移动管理MM网元发送协议数据单元PDU会话重新定位响应消息，所述PDU会话重新定位响应消息中携带所述会话管理消息，以使所述MM网元将所述会话管理消息发送给所述用户设备。
  19. 根据权利要求15至17中任一项所述的网元，其特征在于，所述第二会话消息为会话管理消息；
    所述发送单元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
    根据所述第一会话消息，向所述用户设备发送位置更新接受消息，所述位置更新接受消息中携带所述会话管理消息。
  20. 根据权利要求15至17中任一项所述的网元，其特征在于，所述第二会话消息为会话管理消息；
    所述发送单元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
    根据所述第一会话消息，向所述用户设备接入的接入网网元发送上下文建立请求消息，所述上下文建立请求消息中携带所述会话管理消息，以使得所述接入网网元通过无线资源控制RRC重新配置将所述会话管理消息发送给所述用户设备。
  21. 根据权利要求15至17中任一项所述的方法，其特征在于，所述第二会话消息为会话管理消息；
    所述发送单元根据所述UE上下文响应消息，将第二会话消息发送给用户设备，具体包括执行：
    根据所述第一会话消息，向所述用户设备发送PDU会话更新响应消息，所述PDU会话更新响应消息中携带所述会话管理消息。
  22. 根据权利要求15至21中任一项所述的网元，其特征在于，所述网元还包括：第二处理单元，用于根据预先获取的所述用户设备的通信链路承载状态信息，确定处于激活状态的通信链路；
    所述发送单元将所述第二会话消息发送给所述用户设备，具体包括执行：
    将与处于激活状态的通信链路所对应的第二会话消息发送给所述用户设备。
  23. 根据权利要求15至22中任一项所述的网元，其特征在于，所述接收单元从第二控制面网元接收UE上下文响应消息之前还用于：
    接收所述用户设备发送的位置更新请求消息；所述位置更新请求消息中携带用于推演所述第二控制面网元地址的信息。
  24. 根据权利要求15至22中任一项所述的网元，其特征在于，所述接收单元从第二控制面网元接收UE上下文响应消息之前还用于：
    接收MM网元发送的PDU会话重新定位请求消息；所述PDU会话重新定位请求消息中携带用于推演所述第二控制面网元地址的信息。
  25. 根据权利要求15至22中任一项所述的网元，其特征在于，所述接收单元从第二控制面网元接收UE上下文响应消息之前还用于：
    接收所述用户设备发送的PDU会话更新请求消息；所述PDU会话更新请求消息中携带用于推演所述第二控制面网元地址的信息。
  26. 根据权利要求15至25中任一项所述的网元，其特征在于，所述发送单元还用于向所述第二控制面网元发送上下文请求消息；
    所述接收单元从第二控制面网元接收UE上下文响应消息，具体包括执行： 接收所述第二控制面网元根据所述上下文请求消息发送的所述UE上下文响应消息。
  27. 根据权利要求15至26中任一项所述的网元，其特征在于，所述第一控制面网元为目的SM，所述第二控制面网元为源SM，所述UE上下文响应消息为SM上下文响应消息。
  28. 根据权利要求15至27中任一项所述的网元，其特征在于，所述发送单元，还用于向策略功能PF网元发送PDU会话同步通知消息。
PCT/CN2016/101834 2016-10-12 2016-10-12 会话管理方法及网元 WO2018068216A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2019519710A JP6829308B2 (ja) 2016-10-12 2016-10-12 セッション管理方法及びセッション管理ネットワーク要素
PCT/CN2016/101834 WO2018068216A1 (zh) 2016-10-12 2016-10-12 会话管理方法及网元
CN201680089433.6A CN109792599B (zh) 2016-10-12 2016-10-12 会话管理方法及网元
EP16918734.1A EP3512223B1 (en) 2016-10-12 2016-10-12 Session management method and network element
US16/380,444 US11483898B2 (en) 2016-10-12 2019-04-10 Session management method and session management network element

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/101834 WO2018068216A1 (zh) 2016-10-12 2016-10-12 会话管理方法及网元

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/380,444 Continuation US11483898B2 (en) 2016-10-12 2019-04-10 Session management method and session management network element

Publications (1)

Publication Number Publication Date
WO2018068216A1 true WO2018068216A1 (zh) 2018-04-19

Family

ID=61905067

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/101834 WO2018068216A1 (zh) 2016-10-12 2016-10-12 会话管理方法及网元

Country Status (5)

Country Link
US (1) US11483898B2 (zh)
EP (1) EP3512223B1 (zh)
JP (1) JP6829308B2 (zh)
CN (1) CN109792599B (zh)
WO (1) WO2018068216A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020104023A1 (en) * 2018-11-20 2020-05-28 Nokia Technologies Oy Packet data unit (pdu) session continuity in ultra-reliable low-latency communications (urllc) scenarios
CN111436057A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 一种会话管理方法及装置
RU2796232C2 (ru) * 2019-01-15 2023-05-18 Хуавей Текнолоджиз Ко., Лтд. Способ и устройство управления сеансом

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11262979B2 (en) 2019-09-18 2022-03-01 Bank Of America Corporation Machine learning webpage accessibility testing tool
CN113055535B (zh) * 2019-12-26 2022-06-24 中国电信股份有限公司 用于生成5g端到端话单的方法和系统
KR20210144213A (ko) * 2020-05-21 2021-11-30 삼성전자주식회사 통신 시스템에서 동기화 정보를 전송하기 위한 장치 및 방법

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101400148A (zh) * 2007-09-26 2009-04-01 华为技术有限公司 缺省承载建立过程中专有承载建立的控制方法和设备
CN101572943A (zh) * 2008-04-28 2009-11-04 大唐移动通信设备有限公司 Mme释放isr情况下空闲态ue上下文的方法、装置及系统
CN102348252A (zh) * 2010-08-04 2012-02-08 电信科学技术研究院 一种跟踪区列表更新方法及设备
CN102413561A (zh) * 2011-11-25 2012-04-11 大唐移动通信设备有限公司 一种注册状态下附着消息处理方法及装置
CN102523573A (zh) * 2011-12-06 2012-06-27 大唐移动通信设备有限公司 一种实现跟踪区位置更新的方法及装置

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1870630A (zh) * 2005-10-25 2006-11-29 华为技术有限公司 一种利用会话初始化协议建立呼叫的方法
CN101478743B (zh) * 2008-01-03 2010-08-25 大唐移动通信设备有限公司 一种eps承载管理的方法和装置
US8200196B2 (en) * 2008-01-28 2012-06-12 Comverse Ltd. Method and a system for enabling multimedia ring-back-within the context of a voice-call
CN101600192B (zh) * 2008-06-06 2011-04-27 大唐移动通信设备有限公司 用户上下文同步方法、设备及系统
US8719046B2 (en) * 2008-11-25 2014-05-06 General Electric Company Systems and methods for interruption workflow management
US20120057574A1 (en) * 2010-03-05 2012-03-08 Qualcomm Incorporated Method and apparatus to control local internet protocol access for devices
CN101969634B (zh) * 2010-06-12 2014-09-10 中兴通讯股份有限公司 一种用户数据的同步方法和系统
EP3544326B1 (en) * 2011-01-21 2020-11-04 BlackBerry Limited Network apparatus and process to determine the connection context for connections used for (local) offloading
CN102740270B (zh) * 2011-04-07 2017-06-16 南京中兴软件有限责任公司 一种移动性管理、及为终端创建上下文和建立通道的方法
CN102217360B (zh) * 2011-04-29 2013-09-11 华为技术有限公司 Isr激活场景中移动管理设备故障的处理方法及设备
US20130039287A1 (en) * 2011-08-12 2013-02-14 Venkata Ratnakar Rao Rayavarapu Simplified ue + enb messaging
CN102624584B (zh) * 2012-03-01 2018-02-23 中兴通讯股份有限公司 链路检测方法及装置
CN102932769B (zh) * 2012-11-26 2015-11-25 华为技术有限公司 策略控制方法、实体和系统
US9060308B2 (en) * 2013-01-11 2015-06-16 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Avoiding network address translation in a mobile data network
US10051507B2 (en) 2013-07-03 2018-08-14 Mediatek Inc. Traffic shaping mechanism for UE power saving in idle mode
WO2016114611A1 (ko) * 2015-01-14 2016-07-21 엘지전자(주) 무선 통신 시스템에서 영역 업데이트 방법 및 이를 위한 장치
CN106162705B (zh) * 2015-03-31 2020-02-04 电信科学技术研究院 一种控制用户面承载建立的方法及设备
WO2017198663A1 (en) * 2016-05-16 2017-11-23 Telefonaktiebolaget Lm Ericsson (Publ) Evolved packet system (eps) bearer identity based active flag extension for cellular internet of things (ciot) devices

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101400148A (zh) * 2007-09-26 2009-04-01 华为技术有限公司 缺省承载建立过程中专有承载建立的控制方法和设备
CN101572943A (zh) * 2008-04-28 2009-11-04 大唐移动通信设备有限公司 Mme释放isr情况下空闲态ue上下文的方法、装置及系统
CN102348252A (zh) * 2010-08-04 2012-02-08 电信科学技术研究院 一种跟踪区列表更新方法及设备
CN102413561A (zh) * 2011-11-25 2012-04-11 大唐移动通信设备有限公司 一种注册状态下附着消息处理方法及装置
CN102523573A (zh) * 2011-12-06 2012-06-27 大唐移动通信设备有限公司 一种实现跟踪区位置更新的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3512223A4 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020104023A1 (en) * 2018-11-20 2020-05-28 Nokia Technologies Oy Packet data unit (pdu) session continuity in ultra-reliable low-latency communications (urllc) scenarios
CN111436057A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 一种会话管理方法及装置
WO2020147756A1 (zh) * 2019-01-15 2020-07-23 华为技术有限公司 一种会话管理方法及装置
KR20210110705A (ko) * 2019-01-15 2021-09-08 후아웨이 테크놀러지 컴퍼니 리미티드 세션 관리 방법 및 장치
CN111436057B (zh) * 2019-01-15 2022-06-28 华为技术有限公司 一种会话管理方法及装置
RU2796232C2 (ru) * 2019-01-15 2023-05-18 Хуавей Текнолоджиз Ко., Лтд. Способ и устройство управления сеансом
US11930393B2 (en) 2019-01-15 2024-03-12 Huawei Technologies Co., Ltd. Session management method and apparatus
KR102648031B1 (ko) * 2019-01-15 2024-03-14 후아웨이 테크놀러지 컴퍼니 리미티드 세션 관리 방법 및 장치

Also Published As

Publication number Publication date
JP6829308B2 (ja) 2021-02-10
EP3512223B1 (en) 2021-07-28
JP2019534636A (ja) 2019-11-28
CN109792599A (zh) 2019-05-21
CN109792599B (zh) 2021-05-07
US20190239281A1 (en) 2019-08-01
EP3512223A4 (en) 2019-09-04
EP3512223A1 (en) 2019-07-17
US11483898B2 (en) 2022-10-25

Similar Documents

Publication Publication Date Title
CN112187643B (zh) 报文转发的方法、控制面网关和用户面网关
US11937319B2 (en) Integrity protection handling at the gNB-CU-UP
US11019463B2 (en) Communication method and communications apparatus
US11483898B2 (en) Session management method and session management network element
WO2019185062A1 (zh) 一种通信方法及装置
WO2021018073A1 (zh) 传输数据的方法、通信装置和通信系统
EP3611946B1 (en) User plane link building methods, base stations and computer readable storage medium
WO2018032909A1 (zh) 一种网络切片选择方法及相关设备
WO2017193286A1 (zh) 移动性管理方法和装置
JP7250114B2 (ja) サービスノードの更新方法、端末機器、および、ネットワーク側機器
CN111586735B (zh) 一种通信方法及装置
US10772160B2 (en) RAN server, wireless communications system, and terminal attach method
WO2020154868A1 (zh) 一种参数配置方法及装置、网络设备
CN110169121B (zh) 切换的方法、接入网设备、终端设备
TW202007199A (zh) 一種核心網選擇方法及裝置、終端設備、網路設備
CN112291845A (zh) 一种寻呼方法及通信装置
TW202025815A (zh) 無線通訊方法和基站
US11540252B2 (en) Data transmission method, network device
JP2020503739A (ja) データ処理方法及び装置
US11026132B2 (en) Communication method, core network device, access network device, terminal device, and communication system
WO2020223898A1 (zh) 一种信息传输方法及装置、网络设备
WO2021081711A1 (zh) 一种通信方法、装置及设备
US20180270886A1 (en) Link setup method and device
CN111901899A (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 16918734

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019519710

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016918734

Country of ref document: EP

Effective date: 20190411