[go: up one dir, main page]

WO2018126535A1 - 一种会话管理方法及装置 - Google Patents

一种会话管理方法及装置 Download PDF

Info

Publication number
WO2018126535A1
WO2018126535A1 PCT/CN2017/077363 CN2017077363W WO2018126535A1 WO 2018126535 A1 WO2018126535 A1 WO 2018126535A1 CN 2017077363 W CN2017077363 W CN 2017077363W WO 2018126535 A1 WO2018126535 A1 WO 2018126535A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
type
terminal
state
message
Prior art date
Application number
PCT/CN2017/077363
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 CN202110530649.4A priority Critical patent/CN113784418B/zh
Priority to CN201780009886.8A priority patent/CN108605269B/zh
Publication of WO2018126535A1 publication Critical patent/WO2018126535A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a session management method and apparatus.
  • Session In the fifth generation mobile communication technology (5G) system, session management is performed based on a PDU session flow (Session).
  • Session_ACTIVE or idle state Session_IDLE an independent state
  • the Service Request message sent by the UE carries the PDU Session ID required for the data transmission, so that when activated, only the PDU Session corresponding to the PDU Session ID is activated, so that the PDU Session ID corresponds to The PDU Session is converted from an idle state to an active state.
  • the embodiment of the present application provides a session management method and apparatus, so that a PDU session is converted from an active state to an idle state.
  • an embodiment of the present application provides a session management method, including:
  • the first message of the operation; the first message is that the second device detects no data transmission on the PDU session and continues until the timer expires.
  • Invalidating the operation of the PDU session may include converting the PDU session from an active state to an idle state or deleting the PDU session.
  • the identifier of the PDU session may be carried in the first message.
  • the first device is a first core network device
  • the second device is a second core network device, or is a base station, or is a terminal.
  • the first core network device may be a control plane network element on the core network side, such as an SMF.
  • the second core network device may be a user plane network element on the core network side, such as UPF.
  • the activation of the PDU session may be activated when the PDU session is established, or the PDU session is switched from the idle state to the active state, or the PDU session is activated when the cell handover is performed.
  • a timer is sent by the first device to the second device, so that the second device detects that there is no data transmission on the PDU session, and continues until the timer expires.
  • a trigger is provided to delete or convert the PDU session without data transmission into an idle state, thereby avoiding waste of resources caused by resources occupied by the PDU session without data transmission.
  • the first device acquires a timer corresponding to the PDU session, and may specifically be in one of the following manners.
  • the first device determines a timer of the PDU session based on slice information of a network slice to which the PDU session belongs.
  • the first device receives a timer of the PDU session sent by the third core network device.
  • the first device determines a timer of the PDU session based on a data network name (English: Data Network name, DNN for short) or an access point name (English: Access Point Name, APN for short).
  • a data network name English: Data Network name, DNN for short
  • an access point name English: Access Point Name, APN for short.
  • the method further includes:
  • the first device sends indication information to the second device, where the indication information is information used to indicate the operation of invalidating the PDU session.
  • the first device may send the indication information to the second device together with the timer, and may also be separately sent, which is not specifically limited in this embodiment of the present application.
  • the indication information may be sent by a third core network device. Specifically, after receiving the request message, the first device receives the indication information sent by the third core network device, where the indication information is information used to indicate the operation of invalidating the PDU session.
  • the first device may not send the indication information to the second device, so after the first device receives the first message, determining the invalidation station based on the indication information.
  • the operation of the PDU session is to convert the PDU session from an active state to an idle state or to delete the PDU session.
  • the identifier of the PDU session may be carried in the first message.
  • the first message may further carry a cause value, where the cause value is used to indicate that the timer of the PDU session times out.
  • the reason value is carried in the first message, so that when the first device is in the first message, it can know for what reason the second device wants to trigger the first message, and based on this, determine the next performed operation. .
  • the operation of invalidating the PDU session is to convert the PDU session from an active state to an idle state, and the method further includes:
  • the first device After receiving the first message, the first device sends a message to the second core network device to indicate that the information related to the base station corresponding to the PDN session is deleted. And after the second core network device receives the message for indicating to delete the information related to the base station corresponding to the PDN session, performing an operation of deleting information related to the base station corresponding to the PDN session.
  • the operation of invalidating the PDU session is to convert the PDU session from an active state to an idle state, and the method further includes:
  • the first device After receiving the first message, the first device sets the state of the PDU session to an idle state.
  • the first device saves the state of the PDU session, thereby performing subsequent PDUs on the terminal.
  • the state of the session is synchronized.
  • the operation of invalidating the PDU session is to delete the PDU session, and the method further includes:
  • the first device After receiving the first message, the first device sends a message to the second core network device to indicate that information related to the PDN session is deleted. Therefore, after the second core network device receives the message for instructing deletion of the information related to the PDN session, all information related to the PDU session saved by itself is deleted.
  • the operation of invalidating the PDU session is to delete the PDU session, and the method further includes:
  • the first device After receiving the first message, the first device sends a message to the terminal for instructing the terminal to delete information related to the PDN session. Therefore, after receiving the message for instructing the terminal to delete information related to the PDN session, the terminal deletes all information related to the PDU session saved by itself.
  • the first device after receiving the first message, sends a message to the base station to instruct the base station to release the context of the PDU session.
  • the base station After the base station receives the message indicating that the base station releases the context of the PDU session, the base station deletes or suspends the radio resource corresponding to the PDU session.
  • the method may further include:
  • the first device After receiving the first message, the first device sends a message to the fourth core network device to instruct the fourth core network device to set the state of the PDU session to an idle state. Therefore, after receiving the message for instructing the fourth core network device to set the state of the PDU session to the idle state, the fourth core network device performs setting the state of the PDU session saved by itself to be idle. state. When the fourth core network device subsequently performs an operation related to the PDU session, it is performed based on the state of the PDU session.
  • the first core network device receives the second message sent by the fourth core network device, where the second message carries the identifier of the PDU session of the user plane context to be updated;
  • the first device After receiving the second message, the first device updates the user plane context of the PDU session corresponding to the identifier of the PDU session.
  • the first core network device After receiving the second message sent by the fourth core network device, updates the user plane context of the PDU session corresponding to the identifier of the PDU session.
  • the embodiment of the present application further provides a session management method, including:
  • the base station Receiving, by the base station, a timer of the PDU session sent by the first core network device when the packet data unit PDU session is activated; the base station detects no data transmission on the PDU session, and continues until the timer expires Sending, to the first core network device, a first message invalidating the operation of the PDU session.
  • the first core network device when the PDU session is activated, the first core network device sends a timer to the base station, so that when the base station monitors the PDU session, it monitors that there is no data transmission on the PDU session, and continues to the When the timer expires, the first message is sent to the first core network device, so that after receiving the first message, the first core network device performs an operation of invalidating the PDU session. Based on this, a trigger is provided to invalidate the PDU session without data transmission, thereby avoiding waste of resources caused by the PDU session without data transmission occupying resources.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the method may further include:
  • the base station When the PDU session is activated, the base station receives the indication information sent by the first core network device, where the indication information is information used to indicate the operation of invalidating the PDU session.
  • an operation is provided that is triggered by the first core network device to indicate that the base station detects no data transmission on the PDU session, and continues to trigger the first core network device when the timer expires.
  • the first core network device may not send the indication information to the base station, so that after receiving the first message sent by the base station, the first core network device determines, by itself, the operation to be triggered.
  • the first message may carry an identification of the PDU session.
  • the first message may further carry a cause value, where the cause value is used to indicate that the timer of the PDU session times out.
  • the first core network device triggers the base station to release the context of the PDU session. Specifically, the base station receives the first message. A message sent by a core network device to instruct the base station to release a context of the PDU; the base station deletes or suspends a radio resource corresponding to the PDU session.
  • the base station after the base station receives the message sent by the first core network device to instruct the base station to release the context of the PDU, the base station saves the PDU session.
  • the status is set to idle.
  • the base station saves the state of the PDU session, so that the operation for the PDU session can be subsequently performed based on the state of the PDU session.
  • the method may further include:
  • the base station detects that there is no data transmission on the PDU session, and after the timer expires, deletes the mapping relationship between the quality of service QoS flow corresponding to the PDU session and the radio resource bearer DRB.
  • the base station may delete the mapping relationship between the quality of service QoS flow corresponding to the PDU session and the radio resource bearer DRB when receiving the first message sent by the first core network device.
  • the QoS flow corresponding to the QoS session may be deleted before the first core network device is sent to the first message after monitoring that there is no data transmission on the PDU session and after the timer expires.
  • the radio resource carries the mapping relationship between the DRBs.
  • the method may further include:
  • the base station detects that there is no data transmission on the PDU session, and after the timer expires, sends a message to the terminal to instruct the terminal to delete or suspend the radio resource corresponding to the PDU session.
  • the base station may send, to the terminal, a message for instructing the terminal to delete or suspend a radio resource corresponding to the PDU session.
  • the base station may further send, to the terminal, a message for instructing the terminal to delete or suspend the radio resource corresponding to the PDU session, before deleting or suspending the radio resource corresponding to the PDU session.
  • the base station may further send a message to the terminal to instruct the terminal to delete or suspend the radio resource corresponding to the PDU session.
  • the present application does not specifically limit the sequence of execution of the base station.
  • the message for instructing the terminal to delete or suspend the radio resource corresponding to the PDU session carries: an identifier of the radio resource bearer DRB to be deleted or suspended.
  • an embodiment of the present application provides a session management method, including:
  • the terminal receives a message sent by the base station to instruct the terminal to delete or suspend the radio resource corresponding to the PDU session; the terminal deletes or suspends the radio resource corresponding to the PDU session, and sets the state of the PDU session to Idle state.
  • the terminal After receiving the message sent by the base station, the terminal deletes or suspends the radio resource corresponding to the PDU session, and sets the state of the PDU session to an idle state. Thereby ensuring the DPU of the terminal and the base station The state of the session is synchronized.
  • the message sent by the base station to instruct the terminal to delete or suspend the radio resource corresponding to the PDU session is triggered when the timer that has no data transmission on the PDU session and continues to the PDU session timeout is monitored. Triggered in the process of performing an operation that invalidates the PDU session.
  • the trigger may be the base station, the second core network device, or the terminal.
  • the PDU session with no data transmission is invalid for a period of time, thereby avoiding waste of resources caused by resources occupied by the PDU session without data transmission.
  • the method before the state of the PDU session is set to the idle state, the method further includes:
  • the method before the terminal receives the message sent by the base station to instruct the terminal to delete or suspend the radio resource corresponding to the PDU session, the method further includes:
  • the terminal monitors that there is no data transmission on the PDU session, and when the timer expires, the first message that invalidates the operation of the PDU session is sent to the first core network device.
  • the foregoing provides a method for a terminal to trigger execution of invalidating the PDU session, so that the terminal triggers execution of invalidating the PDU session after monitoring that there is no data transmission on the PDU session and continues until the timer expires.
  • the operation avoids waste of resources caused by resources occupied by PDU sessions that continue to have no data transmission.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the method may further include:
  • the terminal When the PDU session is activated, the terminal receives the first indication information sent by the first core network device, where the first indication information is information used to indicate the operation of invalidating the PDU session.
  • the embodiment of the present application provides a session management method, including:
  • the second core network device receives the message sent by the first core network device, where the message carries the identifier of the PDU session to be deleted, and is used to indicate that the second core network device deletes the corresponding PDU session corresponding to the eNB.
  • the second core network device deletes information related to the base station corresponding to the PDU session or deletes information related to the PDU session.
  • the second core network device after receiving the message sent by the base station, performs information related to the base station corresponding to the PDU session or deletes information related to the PDU session.
  • the message sent by the first core network device is triggered in a process of triggering an operation of invalidating the PDU session when monitoring that there is no data transmission on the PDU session and the timer corresponding to the PDU session expires.
  • the monitoring trigger may be a base station, and may also be the second core network device, or may be the terminal.
  • the PDU session with no data transmission is invalid for a period of time, thereby avoiding waste of resources caused by resources occupied by the PDU session without data transmission.
  • the method may further include:
  • the second core network device monitors that there is no data transmission on the PDU session, and continues until the timer expires, sending a first message to the first core network device that invalidates the operation of the PDU session.
  • the above design provides a method for triggering execution of the invalid PDU session by the second core network device, thereby
  • the second core network device detects that there is no data transmission on the PDU session, and continues to perform the operation of invalidating the PDU session when the timer expires, thereby avoiding resources occupied by the PDU session that continues to have no data transmission. Waste of resources.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the method may further include:
  • the second core network device receives the indication information sent by the first core network device, where the indication information is information indicating that the operation of the PDU session is invalid.
  • the embodiment of the present application further provides a session management method in a cell handover process, including:
  • the fourth core network device receives the identifier of the PDU session sent by the base station;
  • the fourth core network device sends a message to the first core network device to notify the first core network device to update the user plane context of the PDU session.
  • the PDU session that needs to update the user context is determined, thereby notifying the first core network device to update the user plane context of these PDU sessions.
  • the PDU session that needs to update the user context is an active state PDU session, thereby ensuring PDU session update for the active state, and avoiding waste of resources caused by updating all PDU sessions of the terminal in the existing cell handover.
  • the method further includes:
  • the fourth core network device sets the state of the saved PDU session to an idle state, or deletes state information of the PDU session.
  • the state of the saved PDU session is set to an idle state, or the state information of the PDU session is deleted, when subsequent operations on the PDU session are performed, It may be performed based on the state of the PDU session.
  • the embodiment of the present application provides a session management method for synchronizing a PDU session.
  • the method includes:
  • the terminal determines that the uplink data arrives or receives the paging request; the terminal sends a request message to the network device, where the request message carries the identifier of the PDU session, and/or the first state information of the QoS flow corresponding to the PDU session.
  • the first state information indicates that the state of the QoS flow on the terminal is an active state or an inactive state, and is used by the network device to synchronize the state of the QoS flow with the terminal.
  • the terminal sends the status of the QoS flow corresponding to the PDU session to be synchronized to the network device when determining that there is uplink data arrival or receiving the paging request, and the network device synchronizes the QoS flow with the terminal. status.
  • the RRC state of the terminal is an RRC inactive connection state
  • the network device is a base station
  • the request message is used to indicate that the RRC connection of the terminal is restored.
  • the method may further include:
  • the terminal synchronizes a state of the QoS flow corresponding to the PDU session with the base station based on the second state information.
  • the base station After performing the QoS flow of the activated PDU session, the base station sends the status information of the activated PDU session to the terminal, so that the terminal and the base station synchronize the state of the QoS flow of the PDU session.
  • the terminal after the terminal sends a request message to the base station, the terminal receives a mapping relationship between the QoS flow corresponding to the PDU session and the DRB sent by the base station;
  • the terminal saves the mapping relationship.
  • connection management CM state of the terminal is an idle state
  • the network device is a fourth core network device
  • the request message is used to indicate that the terminal is converted from a CM idle state to a CM connection. status.
  • the method may further include:
  • the terminal synchronizes a state of the QoS flow corresponding to the PDU session with the first core network device based on the third flow state information.
  • the terminal when the network device is the fourth core network device, the terminal receives the third state information corresponding to the QoS flow corresponding to the PDU session sent by the first core network device, so that the terminal synchronizes the state of the QoS flow with the first core network device. To avoid data synchronization errors caused by state out of sync.
  • the embodiment of the present application provides a session management method, including:
  • the base station triggers a process of activating the PDU session.
  • the base station determines the PDU session to be activated, so as to perform the activation operation only for the required PDU session, and avoids the resources existing in the existing activation operation for all PDU sessions of the terminal. waste.
  • the parameter is an identifier of the PDU session to be activated, or an identifier of a radio resource bearer DRB corresponding to the PDU session to be activated.
  • the base station includes a correspondence between the PDU session and the radio resource bearer, so that the base station determines the PDU session to be activated according to the correspondence.
  • the state of the PDU session to be activated is an idle state.
  • the RRC connection recovery message further carries first state information of the quality of service QoS flow corresponding to the PDU session; the state information is used by the base station to synchronize the QoS with the terminal The state of the stream.
  • the active PDU session is also the QoS flow corresponding to the active PDU session.
  • the base station triggers a process of performing the activation of the PDU session, including:
  • the base station sends a message to the first core network device for triggering the conversion of the PDU session to an active state.
  • the method may further include:
  • the base station configures a mapping relationship between the QoS flow corresponding to the PDU session and the DRB.
  • the base station After the base station triggers the process of activating the PDU session, the PDU needs to be activated. Then, the base station configures a mapping relationship between the QoS flow corresponding to the PDU session and the DRB for the session.
  • the method may further include:
  • the base station sends the mapping relationship to the terminal. Therefore, the terminal receives the mapping relationship, and performs an operation corresponding to the PDU session based on the mapping relationship.
  • the method may further include:
  • the base station sends the second state information of the QoS flow corresponding to the PDU session to the terminal, to indicate that the terminal synchronizes the state of the QoS with the base station.
  • the above describes a way in which the terminal synchronizes the QoS status with the base station.
  • the method may further include:
  • the base station determines to perform cell handover for the terminal
  • the base station sends a handover request message to the fourth core network device, where the handover request message carries an identifier of the PDU session in which the state corresponding to the terminal is an active state, or the handover request carries the corresponding The identifier of the PDU session in which the base station holds the PDU session context.
  • the base station when performing the cell handover, the base station sends a handover request to the fourth core network device, and carries the identifier of the PDU session in the active state in the request, so that the fourth core network device indicates the SMF corresponding to the PDU session. Update the user plane context corresponding to the active PDU session.
  • the embodiment of the present application provides a session management method, including:
  • the first core network device performs a process of activating the PDU session based on the service request message.
  • the terminal sends the identifier of the PDU session to be activated to the first core network device, and the first core network device only needs to activate all PDU sessions of the terminal for the PDU session to be activated, thereby reducing resource occupation. .
  • the service request message carries first state information of a quality of service QoS flow corresponding to the PDU session; the first state information indicates that the QoS flow corresponding to the PDU session is at the terminal
  • the upper state is an active state or an inactive state, and is used by the first core network device to synchronize the state of the QoS flow with the terminal.
  • the first core network device sends the status of the QoS flow corresponding to the PDU session to the terminal, so that the terminal synchronizes the state of the QoS flow with the first core network device, thereby avoiding data transmission errors caused by state unsynchronization.
  • the method may further include:
  • the third state information indicates that the state of the QoS flow corresponding to the PDU session on the first core network device is an active state or an inactive state.
  • the terminal sends the status of the QoS flow corresponding to the PDU session to the first core network device, so that the first core network device and the terminal synchronize the state of the QoS flow, thereby avoiding data transmission errors caused by the state unsynchronization.
  • the embodiment of the present application further provides a session management apparatus, wherein the beneficial effects of the method and the device part are mutually related, and the details are not described herein again.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a first device, including:
  • a receiving module configured to receive a request message for activating a packet data unit PDU session
  • a sending module configured to send a timer of the PDU session to the second device
  • the receiving module is further configured to receive a first message initiated by the second device to invalidate an operation of the PDU session, where the first message is that the second device detects that no data transmission is performed on the PDU session. And continues until the timer expires.
  • the first device is a first core network device
  • the second device is a second core network device, or is a base station, or is a terminal.
  • the invalidating the PDU session includes: converting the PDU session from an active state to an idle state or deleting the PDU session.
  • it also includes:
  • a first determining module configured to determine, according to the slice information of the network slice to which the PDU session belongs, a timer of the PDU session before the sending module sends the timer to the second device.
  • the receiving module is further configured to receive a timer of the PDU session sent by the third core network device.
  • the sending module is further configured to send indication information to the second device, where the indication information is information used to indicate the operation of invalidating the PDU session.
  • the receiving module is further configured to: after receiving the request message, receive indication information sent by a third core network device, where the indication information is used to indicate that the PDU is invalid. Information about the operation of the session.
  • the second determining module is configured to, after the receiving module receives the first message, determine, according to the indication information, that the operation of invalidating the PDU session is to connect the PDU Transition from an active state to an idle state or to delete the PDU session.
  • the first message carries an identifier of the PDU session.
  • the first message further carries a cause value, and the cause value is used to indicate that the timer of the PDU session times out.
  • the operation of invalidating the PDU session is to convert the PDU session from an active state to an idle state
  • the receiving module is further configured to: after receiving the first message, The second core network device sends a message for indicating to delete information related to the base station corresponding to the PDN session.
  • the operation of invalidating the PDU session is to convert the PDU session from an active state to an idle state, and the apparatus further includes:
  • a processing module configured to set a state of the PDU session to an idle state after receiving the first message.
  • the operation of invalidating the PDU session is to delete the PDU session
  • the sending module is further configured to: after the receiving module receives the first message, to the first
  • the second core network device sends a message indicating the deletion of information related to the PDN session.
  • the operation of invalidating the PDU session is to delete the PDU session
  • the sending module is further configured to send, after receiving the first message, a The terminal deletes the message of the information related to the PDN session.
  • the sending module is further configured to: after the receiving module receives the first message, send a message to the base station to instruct the base station to release the context of the PDU session.
  • the sending module is further configured to send, after the receiving module receives the first message, a fourth core network device, to indicate that the fourth core network device The status of the PDU session is set to the idle state message.
  • the receiving module is further configured to receive a second message sent by the fourth core network device, where the second message carries an identifier of the PDU session of the user plane context to be updated;
  • the device also includes:
  • an update module configured to update a user plane context of the PDU session corresponding to the identifier of the PDU session.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a base station, including:
  • a receiving module configured to receive a timer of the PDU session sent by the first core network device when the packet data unit PDU session is activated
  • a processing module configured to detect that there is no data transmission on the PDU session, and continues until the timer expires
  • the sending module is configured to send, to the first core network device, a first message that invalidates an operation of the PDU session.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the receiving module is further configured to: when the PDU session is activated, receive the indication information sent by the first core network device, where the indication information is used to indicate that the PDU is invalid. Information about the operation of the session.
  • the first message carries an identification of the PDU session.
  • the first message further carries a cause value, where the cause value is used to indicate that the timer of the PDU session times out.
  • the receiving module is further configured to receive a message that is sent by the first core network device to instruct the base station to release a context of the PDU;
  • the processing module is further configured to delete or suspend a radio resource corresponding to the PDU session.
  • the processing module is further configured to:
  • the state of the saved PDU session is set to an idle state.
  • the processing module is further configured to: after monitoring that there is no data transmission on the PDU session, and after the timer expires, delete the quality of service QoS flow corresponding to the PDU session.
  • the mapping relationship with the radio resource bearer DRB is further configured to: after monitoring that there is no data transmission on the PDU session, and after the timer expires, delete the quality of service QoS flow corresponding to the PDU session.
  • the sending module is further configured to: when the processing module monitors that there is no data transmission on the PDU session, and after the timer expires, send the terminal to the terminal for sending The message indicating that the terminal deletes or suspends the radio resource corresponding to the PDU session.
  • the message for instructing the terminal to delete or suspend the radio resource corresponding to the PDU session carries: an identifier of the radio resource bearer DRB to be deleted or suspended.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a terminal, including:
  • a receiving module configured to receive, by the base station, a message for instructing the terminal to delete or suspend a radio resource corresponding to the PDU session;
  • a processing module configured to delete or suspend a radio resource corresponding to the PDU session, and set a state of the PDU session to an idle state.
  • the processing module is further configured to: after receiving, by the receiving module, a message that is sent by the base station to instruct the terminal to delete or suspend a radio resource corresponding to the PDU session, When all radio resources corresponding to the PDU session are deleted or suspended, the state of the PDU session is set to an idle state.
  • the receiving module is further configured to send, by the receiving base station, the terminal to be deleted. Receiving a timer of the PDU session sent by the first core network device, when the PDU session is activated, before the message of the radio resource corresponding to the PDU session is suspended;
  • the device also includes:
  • the sending module is further configured to: when the processing module monitors that there is no data transmission on the PDU session, and continues to send the invalid operation of the PDU session to the first core network device, when the timer expires The first message.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the receiving module is further configured to receive first indication information sent by the first core network device when the PDU session is activated, where the first indication information is used to indicate Information that invalidates the operation of the PDU session.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a second core network device, including:
  • a receiving module configured to receive a message sent by the first core network device, where the message carries an identifier of the PDU session to be deleted, and is used to indicate that the second core network device deletes the PDU session corresponding to the identifier and the base station Related information or deleting information related to the PDU session;
  • a processing module configured to delete information related to the base station corresponding to the PDU session or delete information related to the PDU session.
  • the receiving module is further configured to receive a timer of the PDU session sent by the first core network device when the PDU session is activated;
  • the device also includes:
  • a sending module configured to: when the processing module monitors that there is no data transmission on the PDU session, and continues until the timer expires, sending a first operation of invalidating the PDU session to the first core network device Message.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the receiving module is further configured to: when the PDU session is activated, receive the indication information sent by the first core network device, where the indication information is to indicate that the PDU session is invalid. Information about the operation.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a fourth core network device, including:
  • a receiving module configured to receive an identifier of a PDU session sent by the base station during a cell handover process
  • a processing module configured to determine, according to the identifier of the PDU session, a PDU session that needs to update a user plane context
  • a sending module configured to send, to the first core network device, a message for instructing the first core network device to update a user plane context of the PDU session.
  • the receiving module is further configured to:
  • the processing module is further configured to set the saved state of the PDU session to an idle state, or delete state information of the PDU session.
  • the embodiment of the present application provides a session management method, where the device is applied to a terminal, including:
  • a processing module configured to determine that uplink data arrives or receives a paging request
  • a sending module configured to send a request message to the network device, where the request message carries an identifier of the PDU session, And/or the first state information of the QoS flow corresponding to the PDU session, where the first state information indicates that the state of the QoS flow on the terminal is an active state or an inactive state, and is used by the network device and the The terminal synchronizes the state of the QoS flow.
  • the RRC state of the terminal is an RRC inactive connection state
  • the network device is a base station
  • the request message is used to indicate that the RRC connection of the terminal is restored.
  • the receiving module is further configured to receive second state information of the QoS flow corresponding to the PDU session sent by the base station, where the second state information indicates that the QoS flow is in the The state on the base station is an active state or an inactive state;
  • the processing module is further configured to synchronize, according to the second state information, the state of the QoS flow corresponding to the PDU session with the base station.
  • the receiving module is further configured to receive a mapping relationship between the QoS flow and the DRB corresponding to the PDU session sent by the base station;
  • the processing module is further configured to save the mapping relationship.
  • connection management CM state of the terminal is an idle state
  • the network device is a fourth core network device
  • the request message is used to indicate that the terminal is converted from a CM idle state to a CM connection. status.
  • the receiving module is further configured to receive third state information of the QoS flow corresponding to the PDU session sent by the first core network device, where the third state information indicates The state of the QoS flow corresponding to the PDU session on the first core network device is an active state or an inactive state;
  • the processing module is further configured to synchronize, according to the third flow state information, the state of the QoS flow corresponding to the PDU session with the first core network device.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a base station, including:
  • a receiving module configured to receive an RRC connection recovery message sent by the terminal, where the RRC connection recovery message carries a parameter
  • a processing module configured to determine, according to the parameter, a PDU session to be activated; and trigger a process of activating the PDU session.
  • the parameter is an identifier of the PDU session to be activated, or an identifier of a radio resource bearer DRB corresponding to the PDU session to be activated.
  • the state of the PDU session to be activated is an idle state.
  • the RRC connection recovery message further carries first state information of the quality of service QoS flow corresponding to the PDU session; the state information is used by the base station to synchronize the QoS with the terminal The state of the stream.
  • the device further includes:
  • a sending module configured to send, to the first core network device, a message for triggering to convert the PDU session to an active state.
  • the processing module is further configured to configure a mapping relationship between the QoS flow corresponding to the PDU session and the DRB.
  • it also includes:
  • the sending module is further configured to send the mapping relationship to the terminal.
  • the device further includes:
  • a sending module configured to send second state information of the QoS flow corresponding to the PDU session to the terminal, to indicate The terminal synchronizes the state of the QoS with a base station.
  • the processing module is further configured to determine to perform cell handover for the terminal;
  • a sending module configured to send, to the fourth core network device, a handover request message, where the handover request message carries an identifier of a PDU session in which the state corresponding to the terminal is an active state, or the handover request carries a corresponding The identity of the PDU session in which the base station holds the PDU session context.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a first core network device, including:
  • a receiving module configured to receive a service request message sent by the terminal, where the service request message carries an identifier of a PDU session to be activated;
  • a processing module configured to perform a process of activating the PDU session based on the service request message.
  • the service request message carries first state information of a quality of service QoS flow corresponding to the PDU session; the first state information indicates that the QoS flow corresponding to the PDU session is in the first
  • the state on a core network device is an active state or an inactive state, and is used by the first core network device to synchronize the state of the QoS flow with the terminal.
  • the device further includes:
  • a sending module configured to send third status information of the QoS flow corresponding to the PDU session to the terminal, to indicate that the terminal synchronizes with the first core network device to a state of a QoS flow corresponding to the PDU session;
  • the third state information indicates that the state of the QoS flow corresponding to the PDU session on the first core network device is an active state or an inactive state.
  • the embodiment of the present application further provides a first core network device, where the first core network device includes a communication interface, a processor, and a memory, where the communication interface is used for sending and receiving data, and the memory is used for storing a software program for reading a software program stored in the memory and implementing the method provided by the first aspect or any one of the above first aspects, or for implementing any of the eighth aspect or the eighth aspect A method provided by the design.
  • the first core network device includes a communication interface, a processor, and a memory
  • the communication interface is used for sending and receiving data
  • the memory is used for storing a software program for reading a software program stored in the memory and implementing the method provided by the first aspect or any one of the above first aspects, or for implementing any of the eighth aspect or the eighth aspect A method provided by the design.
  • the embodiment of the present application further provides a second core network device, where the second core network device includes a communication interface, a processor, and a memory, where the communication interface is used for sending and receiving data, and the memory is used for storing a software program for reading a software program stored in the memory and implementing the method provided by any one of the fourth aspect or the above fourth aspect.
  • the embodiment of the present application provides a fourth core network device, where the fourth core network device includes a communication interface, a processor, and a memory, where the communication interface is used for sending and receiving data, and the memory is used to store software. a program for reading a software program stored in the memory and implementing the method provided by any one of the fifth aspect or the fifth aspect.
  • the embodiment of the present application provides a terminal, where the terminal includes a transceiver, a processor, and a memory, the transceiver is configured to send and receive data, the memory is used to store a software program, and the processor is used to read Taking the software program stored in the memory and implementing the method provided by the third aspect or any one of the above third aspects, or the method provided by implementing the sixth aspect or any of the above sixth aspects.
  • an embodiment of the present application provides a base station, where the base station includes a transceiver, a processor, and a memory, where the transceiver is configured to send and receive data, and the memory is used to store a software program, where the processor is used to The software program stored in the memory is read and the method provided by the second aspect or any one of the above second aspects is implemented, or the method provided by the seventh aspect or any of the above seventh aspects is implemented.
  • the embodiment of the present application further provides a computer storage medium, where the software program stores a software program, and the software program can implement the first aspect to the first time when being read and executed by one or more processors A method provided by any one of the eight aspects or any one of the above first to eighth aspects.
  • the embodiment of the present application further provides a session management method, including:
  • the source base station currently accessed by the terminal receives a timer of the PDU session sent by the first core network device; if the source base station detects that there is no data on the PDU session The transmission continues until the timer expires, and the status of the PDU session is recorded as an inactive state;
  • the source base station monitors the timer of the PDU session of the terminal, and does not perform the handover procedure for the PDU with the timer timeout, and performs the handover only for the PDU session whose timer has not expired, thereby avoiding the resource occupied by the PDU session without data transmission. Waste of resources.
  • the source base station performs a handover procedure for the second type of PDU session, including:
  • the source base station sends a handover request to the target base station, where the handover request carries only the identifier of the second type PDU session;
  • the handover request carries an identifier of the first type of PDU session and an identifier of the second type of PDU session;
  • the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • the above provides an XN based switching method.
  • the method further includes:
  • the source base station sends a message to the terminal to instruct the terminal to perform an operation of invalidating the first type of PDU session.
  • the message for instructing the terminal to perform an operation of invalidating the first type of PDU session carries: an identifier of the first type of PDU session; or
  • the message for instructing the terminal to perform the operation of invalidating the first type of PDU session carries: an identifier of the activated PDU session of the terminal, and a first indication, where the first indication is used to identify the terminal The first type of PDU session in the active PDU session.
  • the invalidating the first type of PDU session comprises: converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • the source base station performs a handover procedure for the second type of PDU session, including:
  • the source base station sends a handover request to the fourth core network device, where the handover request carries only the identifier of the second type of PDU session;
  • the handover request carries an identifier of the first type of PDU session and an identifier of the second type of PDU session;
  • the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • the embodiment of the present application provides a session management method, including:
  • the target base station to be switched by the terminal receives the handover request sent by the source base station currently accessed by the terminal, where the handover request carries only the identifier of the second type of PDU session; or the handover request carries the first An identifier of the PDU-like session and an identifier of the second type of PDU session; or the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark the terminal The first type of PDU session in the identity of the activated PDU session;
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating; the first type of PDU session is a PDU session recorded as inactive; the record is inactive.
  • the PDU session refers to a PDU session that satisfies no data transmission until the corresponding timer expires; the second type of PDU session is a PDU session other than the PDU session marked as active in the activated PDU session of the terminal;
  • the target base station sends a message to the fourth core network device to instruct the fourth core network device to perform an operation of invalidating the first type PDU session.
  • the source base station monitors the timer of the PDU session of the terminal, and does not perform the handover procedure for the PDU with the timer timeout, and performs the handover only for the PDU session whose timer has not expired, thereby avoiding the resource occupied by the PDU session without data transmission. Waste of resources.
  • the message for instructing the fourth core network device to perform the operation of invalidating the second type of PDU session carries: an identifier of the first type of PDU session.
  • the invalidating the first type of PDU session comprises: converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • the embodiment of the present application provides a session management method, including:
  • the fourth core network device receives the identifier of the second type of PDU session sent by the source base station or the target base station in the process of the terminal switching from the source base station to the target base station;
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating, and the second type of PDU session is recorded as inactive in the activated PDU session of the terminal.
  • a PDU session other than the PDU session, the PDU session recorded as inactive refers to a PDU session that satisfies the no-data transmission duration until the corresponding timer expires;
  • the fourth core network device sends a message to the first core network device to notify the first core network device to update the context of the second type of PDU session.
  • the fourth core network only performs an update context for the second type of PDU session, thereby avoiding waste of resources caused by resources occupied by the PDU session without data transmission.
  • the fourth core network device receives the identifier of the second type of PDU session sent by the target base station, including:
  • the fourth core network device receives a path switch message sent by the target base station, where the path switch message carries an identifier of the second type of PDU session.
  • the fourth core network device receives the identifier of the second type of PDU session sent by the source base station, including:
  • the fourth core network device receives the handover request sent by the source base station, where the handover request carries the identifier of the second type of PDU session.
  • the method further includes:
  • the fourth core network device sends a message to the first core network device to indicate that an operation of invalidating the first type of PDU session is performed.
  • the invalidating the operation of the first type of PDU session includes converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • the method further includes:
  • the fourth core network device converts the state of the first type of PDU session from an active state to an idle state or deletes the first type of PDU session.
  • the method further includes:
  • the fourth core network device sends a message to the first core network device to indicate that an operation of invalidating the third type PDU session is performed.
  • the operation of invalidating the third type of PDU session includes:
  • the method further includes:
  • the fourth core network device converts the state of the third type of PDU session from an active state to an idle state or deletes the third type of PDU session.
  • the method further includes:
  • the fourth core network device sends the identifier of the third type of PDU session to the terminal, and is used to instruct the terminal to set the state of the third type of PDU session to an idle state.
  • the embodiment of the present application provides a session management method, including:
  • the terminal receives the operation sent by the source base station or the fourth core network device to indicate that the operation of the invalid first type packet data unit PDU session is performed.
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating; the first type of PDU session is a PDU session recorded as inactive; the record is inactive.
  • a PDU session refers to a PDU session that satisfies the no-data transmission duration until the corresponding timer expires;
  • the terminal performs an operation of invalidating the first type of PDU session based on the message.
  • the message for instructing the terminal to perform an operation of invalidating the first type of packet data unit PDU session carries: an identifier of the first type of PDU session.
  • the message for indicating an operation of invalidating the first type of packet data unit PDU session carries: an identifier of the activated PDU session of the terminal, and a first indication, the first indication a first type of PDU session in an activated PDU session for marking the terminal;
  • the performing, by the terminal, the operation of invalidating the first type of PDU session based on the message includes:
  • the operation of invalidating the first type of PDU session includes:
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a source base station, including:
  • a receiving module configured to receive a timer of the PDU session sent by the first core network device when the PDU session of the terminal is established or activated; if the source base station detects that no data transmission continues on the PDU session When the timer expires, the status of the PDU session is recorded as an inactive state;
  • a processing module configured to determine a first type of PDU session included in an activated PDU session of the terminal when performing a handover from the source base station to the target base station, where the first type of PDU session is a record
  • a handover procedure is performed for the second type of PDU session, the second type of PDU session being a PDU session of the terminal's PDU session other than the first type of session.
  • it also includes:
  • a sending module configured to send, by the processing module, a handover request to the target base station, where the handover request carries only the identifier of the second type of PDU session;
  • the handover request carries an identifier of the first type of PDU session and an identifier of the second type of PDU session;
  • the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • it also includes:
  • a sending module configured to send, to the terminal, a message for instructing the terminal to perform an operation of invalidating the first type PDU session in a process of performing handover for a second type of PDU session.
  • the message for instructing the terminal to perform an operation of invalidating the first type of PDU session carries: an identifier of the first type of PDU session; or
  • the message for instructing the terminal to perform the operation of invalidating the first type of PDU session carries: an identifier of the activated PDU session of the terminal, and a first indication, where the first indication is used to identify the terminal The first type of PDU session in the active PDU session.
  • the invalidating the first type of PDU session comprises: converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • it also includes:
  • the sending module is configured to: when the processing module performs a handover procedure for the second type of PDU session, send a handover request to the fourth core network device, where the handover request only carries the identifier of the second type of PDU session; or,
  • the handover request carries an identifier of the first type of PDU session and an identifier of the second type of PDU session;
  • the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • the embodiment of the present application provides a session management apparatus, where the apparatus applies a target base station, including:
  • the receiving module receives the handover request sent by the source base station currently accessed by the terminal, where the handover request carries only the identifier of the second type of PDU session; or the handover request carries the identifier of the first type of PDU session And an identifier of the second type of PDU session; or the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark an activated PDU session of the terminal The first category in the logo PDU session;
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating; the first type of PDU session is a PDU session recorded as inactive; the record is inactive.
  • the PDU session refers to a PDU session that satisfies no data transmission until the corresponding timer expires; the second type of PDU session is a PDU session other than the PDU session marked as active in the activated PDU session of the terminal;
  • a sending module configured to send, to the fourth core network device, a message for instructing the fourth core network device to perform an operation of invalidating the first type PDU session.
  • the message for instructing the fourth core network device to perform the operation of invalidating the second type of PDU session carries: an identifier of the first type of PDU session.
  • the invalidating the first type of PDU session comprises: converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a fourth core network device, including:
  • a receiving module configured to receive an identifier of a second type of PDU session sent by the source base station or the target base station in the process of the terminal switching from the source base station to the target base station;
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating, and the second type of PDU session is recorded as inactive in the activated PDU session of the terminal.
  • a PDU session other than the PDU session, the PDU session recorded as inactive refers to a PDU session that satisfies the no-data transmission duration until the corresponding timer expires;
  • a sending module configured to send, to the first core network device, a message for notifying the first core network device to update a context of the second type of PDU session.
  • the receiving module is configured to receive a path switch message sent by the target base station, where the path switch message carries an identifier of the second type of PDU session.
  • the receiving module is specifically configured to receive a handover request sent by the source base station, where the handover request carries an identifier of the second type of PDU session.
  • the device further includes:
  • a processing module configured to determine, according to the identifier of the second type of PDU session, a first type of PDU session, where the first type of PDU session is an activated PDU session of the terminal saved by the fourth core network device Defining a PDU session other than the second type of PDU session corresponding to the identifier;
  • the fourth core network device sends a message to the first core network device to indicate that an operation of invalidating the first type of PDU session is performed.
  • the invalidating the operation of the first type of PDU session includes converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • the processing module is further configured to convert the state of the first type of PDU session from an active state to an idle state after determining the first type of PDU session based on the identifier of the first type of PDU session. Or deleting the first type of PDU session.
  • the receiving module is further configured to receive an identifier of a third type of PDU session sent by the source base station or a target base station, where the third type of PDU session is inactive. PDU session;
  • the sending module is configured to send, to the first core network device, a message for indicating that an operation of invalidating the third type PDU session is performed.
  • the operation of invalidating the third type of PDU session includes:
  • the device further includes:
  • a processing module configured to: after the receiving module receives the identifier of the third type PDU session sent by the source base station or the target base station, convert the state of the third type PDU session from an active state to an idle state or delete the The third type of PDU session.
  • the sending module is further configured to: after the receiving module receives the identifier of the third type PDU session sent by the source base station or the target base station, The identifier is sent to the terminal, and is used to instruct the terminal to set the state of the third type of PDU session to an idle state.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a terminal, including:
  • a receiving module configured to receive, during a process of the terminal switching from the currently accessed source base station to the target base station, the source base station or the fourth core network device, configured to indicate that the invalid first type packet data unit PDU session is performed Operational message;
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating; the first type of PDU session is a PDU session recorded as inactive; the record is inactive.
  • a PDU session refers to a PDU session that satisfies the no-data transmission duration until the corresponding timer expires;
  • a processing module configured to perform an operation of invalidating the first type of PDU session based on the message.
  • the message for instructing the terminal to perform an operation of invalidating the first type of packet data unit PDU session carries: an identifier of the first type of PDU session.
  • the message for indicating an operation of invalidating the first type of packet data unit PDU session carries: an identifier of the activated PDU session of the terminal, and a first indication, the first indication a first type of PDU session in an activated PDU session for marking the terminal;
  • the performing, by the terminal, the operation of invalidating the first type of PDU session based on the message includes:
  • the operation of invalidating the first type of PDU session includes:
  • the embodiment of the present application further provides a fourth core network device, where the fourth core network device includes a communication interface, a processor, and a memory, where the communication interface is used for sending and receiving data, and the memory is used for A software program is stored, the processor being configured to read a software program stored in the memory and implement the method provided by any one of the twenty-fifth aspect or the twenty-fifth aspect.
  • the embodiment of the present application provides a terminal, where the terminal includes a transceiver, a processor, and a memory, the transceiver is configured to send and receive data, and the memory is used to store a software program, where the processor is used to The software program stored in the memory is read and the method provided by the twenty-sixth aspect or any one of the twenty-sixth aspects described above is implemented.
  • an embodiment of the present application provides a base station, where the base station includes a transceiver, a processor, and a memory, where the transceiver is configured to send and receive data, and the memory is used to store a software program, where the processor is used to Reading a software program stored in the memory and implementing the method provided by any one of the twenty-third aspect or the twenty-third aspect, or for implementing the twenty-fourth aspect or the twenty-fourth aspect Any of the methods provided by the design.
  • FIG. 1A is a schematic structural diagram of a system according to an embodiment of the present application.
  • FIG. 1B is a schematic diagram of another system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a state provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a session management method according to an embodiment of the present application.
  • FIG. 4A is a schematic diagram of a timer configuration method according to an embodiment of the present disclosure.
  • FIG. 4B is a schematic diagram of another timer configuration method according to an embodiment of the present disclosure.
  • 4C is a schematic diagram of still another timer configuration method according to an embodiment of the present application.
  • FIG. 5A is a schematic diagram of a timer triggering method according to an embodiment of the present disclosure.
  • FIG. 5B is a schematic diagram of another timer triggering method according to an embodiment of the present disclosure.
  • FIG. 5C is still another schematic diagram of a timer triggering method according to an embodiment of the present disclosure.
  • FIG. 6A is a schematic diagram of state synchronization according to an embodiment of the present application.
  • FIG. 6B is another schematic diagram of state synchronization according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a cell handover method according to an embodiment of the present application.
  • FIGS. 8A to 8C are schematic diagrams of a first core network device according to an embodiment of the present application.
  • FIGS. 9A to 9E are schematic diagrams of a base station according to an embodiment of the present application.
  • FIGS. 10A to 10D are schematic diagrams of terminals according to an embodiment of the present application.
  • 11A-11B are schematic diagrams of a second core network device according to an embodiment of the present application.
  • FIGS. 12A to 12C are schematic diagrams of a fourth core network device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a method for triggering a timer in a base station handover of a terminal according to an embodiment of the present disclosure
  • FIG. 14A to FIG. 14C are schematic diagrams of a method for handover of a base station of a terminal according to an embodiment of the present disclosure.
  • the embodiment of the present application can be applied to a 4G (fourth generation mobile communication system) evolution system, such as an LTE (Long Term Evolution) system, or can also be a 5G (fifth generation mobile communication system) system, such as adopting a new wireless system.
  • 4G fourth generation mobile communication system
  • LTE Long Term Evolution
  • 5G fifth generation mobile communication system
  • New RAT new radio access technology
  • CRAN Cloud Radio Access Network
  • FIG. 1A is a schematic diagram showing a system architecture applicable to an embodiment of the present application. It should be understood that the embodiment of the present application is not limited to the system shown in FIG. 1.
  • the device in FIG. 1A may be hardware, or may be functionally divided software or a combination of the two.
  • the system architecture provided by the embodiment of the present application includes a terminal, a base station, a first core network device, a second core network device, a third core network device, and a fourth core network device.
  • the terminal can communicate with the first core network device, the second core network device, and the fourth core network device by using the base station.
  • the first core network device communicates with the fourth core network device, and the first core network device and the fourth core network device may be collectively referred to as a control plane network element.
  • the fourth core network device and the third core network device are connected through a communication interface.
  • the control plane network element may include an authentication and mobility management entity (English: Authentication and Mobility Management Function, AMF), and a session management function entity (English: Session Management Function, referred to as :SMF), and SDN controller, gateway control plane (GW-C), mobility management entity (English Mobility Management Entity, MME for short) or all or part of the control function formed by merging the Internet elements.
  • the control plane network element is responsible for the mobility management and forwarding path management in the mobile network, such as sending a packet forwarding policy to the forwarding plane gateway (GW-U), instructing the GW-U to perform packet processing according to the packet forwarding policy. And forwarding.
  • the first core network device is an SMF
  • the fourth core network device is an AMF
  • the first core network device is an SMF
  • the fourth core network device is used.
  • AMF responsible for UE authentication and mobility management, NAS message routing, SMF selection, etc.
  • SMF responsible for session management, such as session creation, modification, deletion. UPF selection, UE IP address allocation, etc.
  • the second core network device may be a forwarding plane network element (English: User Plane Function, UPF for short), as shown in FIG. 1B.
  • the UPF is responsible for packet processing and forwarding. It may be a forwarding data function of a packet data network (English: packet method) (Gate Way, GW for short) and a forwarding surface of a service gateway (English: Serving Gate Way, S-GW for short). Physical or virtual forwarding devices such as functions, routers, and switches.
  • the third core network device may be a policy control function entity (Policy Rules Function, PCF for short) or a Policy and Charging Rules Function (PCRF). Among them, the PCF or PCRF is responsible for policy control decisions and flow-based charging control.
  • the third core network device may also be a user data management entity (English: Subscriber Data Management, SDM for short) or a home subscriber server (English: Home Subscriber Server, HSS for short).
  • the user data management entity English may also correspond to User Data Management, and the abbreviation may also correspond to UDM.
  • SDM, UDM or HSS are used to help operators achieve unified management of all user-related data.
  • the base station may also be referred to as an access node (English: Access Node, referred to as AN), as shown in FIG. 1B, and provides a wireless access service for the terminal.
  • the access node may be a Global System for Mobile communication (GSM) system or a base station in a code division multiple access (CDMA) system (English: Base Transceiver Station) , abbreviated as: BTS), may also be a base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station in an LTE system (English: Evolutional Node) B, referred to as: eNB or eNodeB), or base station equipment, small base station equipment, wireless access node (WiFi AP), and wireless interoperability for microwave access base station in the future 5G network (English: Worldwide Interoperability for Microwave Access Base Station, referred to as: WiMAX BS), etc., this application is not limited thereto.
  • GSM Global System for Mobile communication
  • a terminal may also be referred to as an access terminal, a user equipment (English: User Equipment, UE for short), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, and a wireless communication device. , user agent or user device, etc.
  • the UE is taken as an example in FIG. 1B.
  • the terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, and a personal digital processing (English: Personal Digital) Assistant, referred to as PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, IoT devices, such as fire detection sensors, smart water meters/meters, factories Monitor equipment and more.
  • SIP Session Initiation Protocol
  • WLL wireless local loop
  • PDA Personal Digital Processing
  • system architecture may also include a network application function (English: Application Function, abbreviated as AF), a user data management entity (English: Subscriber Data Management, SDM for short), and a data network (English: Data Network, DN for short).
  • AF Application Function
  • SDM Subscriber Data Management
  • DN Data Network
  • the data network (English: Data Network, DN for short) provides data transmission services for users. It can be a PDN network, such as the Internet (Internet) and IP Multimedia Service (English: IP Multi-media Service, IMS for short).
  • the AF mainly performs dynamic policy/billing control on forwarding plane behavior. These services require dynamic policy and charging control.
  • the AF transmits the dynamic session information required by the PCF, and receives the IP-CAN access network (IP-CAN) specific information and the IP-CAN bearer layer event confirmation.
  • IP-CAN IP-CAN access network
  • the plurality of items referred to in the present application mean two or more. "and/or", describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or” relationship.
  • first, second, third, etc. may be used to describe various messages, requests, devices, and core network devices in the embodiments of the present application, these messages, requests, devices, and core network devices are not. It should be limited to these terms. These terms are only used to distinguish messages, requests, devices, and core network devices from each other.
  • the PDU session in the embodiment of the present application involves two states: an idle state and an active state.
  • the status of the PDU session is used to describe the user plane connection status between the UE and the UPF of the PDU session.
  • the specific name may be a session management state, a session connection state, or other possible names describing the session state.
  • the specific name of the state of the PDU session is not limited in the present invention.
  • the state of the PDU session is stored in the UE and the SMF, and may also be stored in the AMF and the UPF.
  • the idle state means that the user plane connection between the UE and the UPF does not exist in the PDU session, and may be a combination of one or more of the following operations:
  • the UPF deletes or suspends the information of the corresponding base station side of the NG3 interface (for example, the IP address, tunnel identifier, port number, etc. of the base station, so that the UPF cannot be sent to the base station after the downlink data arrives at the UPF).
  • the information of the corresponding base station side of the NG3 interface for example, the IP address, tunnel identifier, port number, etc. of the base station, so that the UPF cannot be sent to the base station after the downlink data arrives at the UPF.
  • the base station may delete or suspend the radio resource corresponding to the PDU session.
  • the radio resource in the present invention may be a time-frequency resource for carrying data corresponding to the PDU session, or may be a radio resource configuration DRB or a combination of these conditions. Delete or suspend the NG3 interface.
  • the UE deletes or suspends the corresponding radio resource according to the configuration of the base station.
  • the active state refers to the existence of a user plane connection between the UE and the UPF in the PDU session, including the air interface connection between the UE and the base station and the NG3 interface between the base station and the UPF.
  • the session in the active state has uplink and downlink data arrives, Can be transmitted directly between the UE and the UPF.
  • the embodiment of the present application provides a session management method and device, and configures a timer for each PDU session, which is used to monitor the operation of invalidating the PDU session when no data transmission continues on the PDU session until the timer expires.
  • the operation of the invalid PDU session may be to perform the PDU session to enter the idle state, or to delete the PDU session, thereby providing an implementation manner of realizing the transition of the state of the PDU Session from the active state to the idle state.
  • the state of the PDU session is stored in the UE, the base station (AN), and the SMF in the core network side.
  • Each PDU session has a different state, and different SMFs manage different PDU sessions, as shown in FIG. 2, SMF A is used to manage session A and session B, and SMF B is used to manage session C.
  • the state of a PDU session is divided into two states, an idle state (IDLE) and an active state (ACTIVE).
  • FIG. 3 is a schematic flowchart diagram of a session management method according to an embodiment of the present application.
  • the SMF receives a request message for activating a PDU session.
  • the activation of the PDU session may be to establish the PDU session, or the PDU session may be switched from the idle state to the active state, or the PDU session may be created when the handover is performed (specifically, the UE may be from non-3GPP (non-3GPP)).
  • the network switches to the 3GPP network, it is mapped from the non-3GPP session to the PDU session created when the 3GPP session is).
  • the SMF sends a timer (Timer) of the PDU session to the second device.
  • the second device After receiving the timer of the PDU session, the second device detects that there is no data transmission on the PDU session, and continues to send the invalid PDU session to the first core network device when the timer expires. Operational The first message.
  • the timer can be enabled when there is no data transmission within a predetermined time after the data is transmitted in the PDU session, and no data transmission occurs during the period when the timer is turned on until the timeout expires, and the first message is triggered.
  • the timer can also be turned on after each transmission of the data in the PDU session, and then there is no data transmission during the period when the timer is turned on until the timeout expires, and the first message is triggered.
  • the timer is reset.
  • the second device in the embodiment of the present application may be a UPF, may be a base station, or may be a terminal. That is to say, the operation of triggering the invalidation of the PDU session may be performed by the second core network device, may also be performed by the base station, or may be performed by the terminal.
  • the operation of invalidating the PDU session may be to change the state of the PDU session from an active state to an idle state, or may be to delete the PDU session.
  • the following is an example of configuring a timer when a PDU session is established, that is, the request message is a PDU session establishment request message.
  • FIG. 4A is a schematic diagram of an SMF configuring a timer of a PDU session to an AN
  • FIG. 4B is a schematic diagram of an SMF configuring a timer of a PDU session to a UPF
  • FIG. 4C is a timer of a SMF to a PDU session. Schematic diagram of configuring to the UE.
  • the SMF configures the timer of the PDU session to the base station, as shown in Figure 4A:
  • the UE sends a PDU Session Setup Request message to the SMF.
  • the SMF and the SDM perform the PDU Session Authorization.
  • the SMF obtains session-related subscription information from the SDM, such as an access point name (English: Access Point Name, APN for short) information, a data network name (English: Data Network Name, DNN for short), and a continuous session and service.
  • Session and Service Continuity, SSC for short etc.
  • the PDU session requested by the UE is authenticated according to the subscription information.
  • the SMF obtains, from the PCF, a QoS policy, a charging policy, and the like corresponding to the PDU session.
  • Policy Retrieval Policy Retrieval
  • the SMF configures a timer for the PDU session.
  • the SMF is for a specific network slice.
  • the SMF is configured with a corresponding timer.
  • the timer may be called a Session inactive timer.
  • the network slice is a logical entity for the network to be allocated by the operator in the 5G to provide a customized network service, and may be divided according to the service type of the service, such as a slice supporting the mobile broadband (English: Mobile Broad Band, MBB) service. Support (English: Internet of Things, referred to as: IOT) slice. It can also be divided according to different network tenants, such as those provided for some large enterprises or organizations.
  • the timer may be configured by the PCF to configure a timer for the PDU session according to the policy information of the PDU session saved by the PCF, and send the timer to the SMF.
  • the timer is obtained by the SMF from the subscription information.
  • the SMF sends the timer to the AN.
  • the SMF may send the timer to the AN in a PDU Session Setup Request message or a PDU Session Setup Accept message, and the PDU session establishment accept message is taken as an example in FIG. 4A. Be explained.
  • the SMF may also obtain, from the PCF, indication information that is required to perform an operation of invalidating the PDU session, which is performed by a timer of the PDU session.
  • the SMF may also invalidate the obtained indication to invalidate the operation of the PDU session.
  • the indication information is sent to the AN, so that the AN can trigger a message to the SMF to indicate whether to convert the PDU session state to the idle state or delete the PDU session when monitoring that there is no data transmission on the PDU session.
  • the SMF may send the indication message to the AN in a PDU Session Setup Accept message.
  • the indication information may be used to indicate that the state of the PDU session is converted to an idle state (SM handling for session idle) or to indicate a delete PDU session (delete session).
  • the SMF transmits the invalid operation of the PDU session when the received AN detects no data transmission on the PDU session and continues until the timer expires. At the time of the message, it is determined whether to perform the conversion of the PDU session state to the idle state or the deletion of the PDU session according to the indication information acquired from the PCF.
  • S401b to S404b refer to S401a to S404a in FIG. 4A, and details are not described herein again.
  • the SMF sends the timer to the UPF.
  • the SMF may send the timer to the UPF in a session creation request (Create Session Request) message, and the session creation request is taken as an example in FIG. 4B.
  • session creation request Create Session Request
  • the SMF may also obtain, from the PCF, indication information that is required to perform an operation of invalidating the PDU session, which is performed by a timer of the PDU session.
  • the SMF may also send the obtained indication information indicating that the operation of the PDU session is invalid to the UPF, so that the UPF may trigger the sending to the SMF when monitoring that there is no data transmission on the PDU session.
  • the SMF may send the indication message to the AN in a PDU Session Setup Accept message.
  • the indication information may be used to indicate that the state of the PDU session is converted to an idle state (SM handling for session idle) or to indicate a delete PDU session (delete session).
  • the SMF when receiving the UPF, detects that there is no data transmission on the PDU session, and continues until the timer expires, the operation of invalidating the PDU session is sent. At the time of the message, it is determined whether to perform the conversion of the PDU session state to the idle state or the deletion of the PDU session according to the indication information acquired from the PCF.
  • S401c to S404c refer to S401a to S404a in FIG. 4A, and details are not described herein again.
  • the SMF sends a message to the UE for invalidating the operation of the PDU session through the AN.
  • S405c The SMF sends a Session Create Request (Message Session Setup) message or a PDU Session Setup Accept message to the AN. Take the session creation request message as an example in Figure 4C.
  • Session Create Request Message Session Setup
  • PDU Session Setup Accept message Take the session creation request message as an example in Figure 4C.
  • the Create Session Request carries a SPI session timer (Session Inactive timer).
  • the Create Session Request carries a timer of the PDU session and an indication information for indicating an operation of invalidating the PDU session.
  • the Create Session Request message carries an indication information indicating that the operation of the PDU session is invalid.
  • the AN sends the indication information to the UE.
  • the AN may send the timer and the indication information to the UE in an RRC Connection reconfiguration (RRC Connection reconfiguration) message or an RRC Connection direct transfer message.
  • RRC Connection message is taken as an example in FIG. 4C, and the RRC connection is reconfigured in FIG. 4C. For example.
  • the UE sends an RRC Connection Reconfiguration Response (RRC Connection Reconfiguration Response) message to the AN.
  • RRC Connection Reconfiguration Response RRC Connection Reconfiguration Response
  • S408c The AN sends a Session Setup Response (Session Setup Response) message to the SMF.
  • Session Setup Response Session Setup Response
  • the AN detects no data transmission on a certain PDU session and continues until the timer expires.
  • the AN receives the indication information sent by the SMF to indicate the invalid PDU session, if the indication information is the Session Idle, it is determined that the triggering execution of the PDU session is converted to the idle state, and if the indication information is the delete session, the trigger is determined to be triggered. Perform the deletion of the PDU session.
  • the indication information is Session Idle as an example.
  • the AN sends a first message to the SMF through the AMF to indicate that the PDU session is converted to an idle state.
  • the first message may be a PDU Session Inactive Request message or a Session Status Transition Request message.
  • the PDU Session Inactive Request is used as an example.
  • the PDU Session Inactive Request message carries the identifier of the PDU session.
  • the identifier of the PDU session may be the ID of the PDU session.
  • other information that can identify the PDU session is applicable to the present application.
  • the ID of the PDU session is taken as an example for description.
  • a cause value (cause) may also be carried in the PDU session Inactive Request message, and the cause value is used to indicate that the timer of the PDU session times out.
  • the first message may be a delete session request message, where the delete session request message may carry the identifier of the PDU session, and may also carry a cause value, and the cause value is used to indicate The timer of the PDU session expired.
  • the SMF obtains the first message triggered by the AN, and then obtains the information based on the slave PCF.
  • the indication information determines whether the state in which the PDU session is performed is converted to the idle state or the deletion of the PDU session is performed.
  • the SMF sends a message to the UPF to indicate that the information related to the AN corresponding to the PDN session is deleted.
  • the message for indicating that the information related to the PDN session is deleted may be a session-idle transition request (Session-idle Transition Request) message, or may be a Release Access Bearers Request message.
  • the Session-idle transition Request message carries the PDU Session ID.
  • the cause-idle transition request message may also carry a cause value, and the cause value indicates that the timer expires (Session Inactive timer expires).
  • a session enters a session-idle transition request (Session-idle transition Request) message as an example.
  • the UPF deletes the information related to the AN corresponding to the PDN session corresponding to the PDU session ID.
  • the UPF can also suspend the NG3 interface information corresponding to the PDU session.
  • step S504a the SMF sends a message to the UPF for instructing deletion of information related to the PDN session, such as delete session request. Message.
  • the UPF thus performs the deletion of information related to the PDN session.
  • it also includes:
  • the UPF sends a session to the SMF to enter a Session-idle Transition Response (Session-idle Transition Response) message.
  • Session-idle Transition Response Session-idle Transition Response
  • the SMF sends a message to the AMF indicating that the AMF sets the PDU session to idle.
  • the message instructing the AMF to set the PDU session to idle may be a session-idle transition Request Response message.
  • a session enters an idle-state transition request response (Session-idle transition Request Response) message.
  • the AMF sets the state of the PDU session to an idle state.
  • the SMF sets the state of the PDU session to an idle state (Session-IDLE).
  • the SMF sets the state of the PDU session to the idle state (Session-IDLE), and may also be after receiving the first message.
  • the AMF sends a message to the AN to instruct the AN to release the context of the PDU session.
  • the message for instructing the base station to release the context of the PDU session may be a session context release command (Session Context Release Command), and the session context release command is taken as an example in FIG. 5A.
  • the AN deletes or suspends the corresponding radio resource of the PDU session.
  • the AN deletes the mapping relationship between the data of the PDU session and the DRB, so that the specific DRB is no longer used to transmit the data of the PDU session in the IDLE state. .
  • the AN may delete the mapping relationship between the quality of service (English: Quality of Service, QoS for short) flow and the DRB.
  • the quality of service English: Quality of Service, QoS for short
  • the AN updates the access layer (English: Access Stratum, AS for example) filter (AS-level filter), and the filter is used by the AN to perform QoS flow to DRB mapping, and specifically, the AS-level filter can be The information related to the PDU session is deleted, or the information related to the PDU session in the AS-level filter is marked as inactive or idle.
  • AS-level filter access layer (English: Access Stratum, AS for example) filter
  • the AN sends a message to the UE for instructing the UE to delete or suspend the radio resource corresponding to the PDU session.
  • the message for instructing the UE to delete or suspend the radio resource corresponding to the PDU session may be an RRC Connection Reconfiguration message, and the RRC connection reconfiguration is taken as an example in FIG. 5A.
  • the message for instructing the UE to delete or suspend the radio resource corresponding to the PDU session may carry the identifier of the radio resource bearer DRB to be deleted or suspended.
  • S512a The UE deletes or suspends the DRB corresponding to the PDU session.
  • the UE may also set the state of the PDU session to an idle state.
  • the UE may also delete the mapping relationship between the QoS flow of the PDU session and the DRB.
  • the UE sets the state of the PDU session to an idle state, it is determined that all radio resources corresponding to the PDU session are deleted or suspended.
  • S513a The UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the AN.
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • the AN sends a Session Context Release Complete message to the AMF.
  • the UPF detects no data transmission on a certain PDU session and continues until the timer expires.
  • the UPF receives the indication information for indicating the invalid PDU session sent by the SMF, if the indication information is the SM handling for Session Idle, it is determined that the triggering execution of the PDU session is converted to the idle state, and if the indication information is Delete Session, it is determined that the triggering execution deletes the PDU session.
  • the indication information is the SM handling for Session Idle as an example.
  • the UPF sends a first message to the SMF to indicate that the PDU session is converted to an idle state.
  • the first message may be a PDU Session Inactive Request message, and the session inactivation request is taken as an example in FIG. 5B.
  • the PDU Session Inactive Request message carries the identifier of the PDU session.
  • the identifier of the PDU session may be the ID of the PDU session.
  • a cause value (cause) may also be carried in the PDU session Inactive Request message, and the cause value is used to indicate that the timer of the PDU session times out.
  • the first message may be a delete session request message.
  • the SMF receives the first message triggered by the UPF, and is based on the slave PCF.
  • the obtained indication information determines whether the state in which the PDU session is performed is converted to the idle state or the deletion of the PDU session is performed.
  • the SMF sends a message to the AN through the AMF to instruct the AN to release the context of the PDU session.
  • the message for instructing the AN to release the context of the PDU session may be a Session Context Release Command or may be a PDU Session Inactive Request message.
  • the identifier of the PDU session may be carried in the message indicating that the base station releases the context of the PDU session (in this application, the ID of the PDU session is taken as an example).
  • the AN deletes or suspends the corresponding radio resource of the PDU session.
  • mapping relationship between the data of the PDU session and the DRB is deleted.
  • the AN may also delete the mapping relationship between the QoS flow and the DRB corresponding to the PDU session.
  • the AN updates the AS-level filter, and the filter is used by the AN to perform mapping of the QoS flow to the DRB.
  • the information related to the PDU session in the AS-level filter may be deleted, or the AS-level filter may be in session with the PDU. Relevant information is marked as inactive or idle.
  • S506b The AN sends a message to the UE to instruct the UE to delete or suspend the radio resource corresponding to the PDU session.
  • the message for instructing the UE to delete or suspend the radio resource corresponding to the PDU session may be an RRC connection.
  • Reconfiguration RRC Connection Reconfiguration
  • the message for instructing the UE to delete or suspend the radio resource corresponding to the PDU session may carry the identifier of the radio resource bearer DRB to be deleted or suspended.
  • S507b The UE deletes or suspends the DRB corresponding to the PDU session.
  • the UE may also set the state of the PDU session to an idle state.
  • the UE may also delete the mapping relationship between the QoS flow of the PDU session and the DRB.
  • the UE sets the state of the PDU session to an idle state, it is determined that all radio resources corresponding to the PDU session are deleted or suspended.
  • S508b The UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the AN.
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • S509b The AN sends a message to the AMF to instruct the AMF to set the state of the PDU session to an idle state.
  • the message for indicating that the AMF sets the state of the PDU session to the idle state may be a PDU Session Inactive Response message.
  • the AMF sets a state of the PDU session to an idle state.
  • the AMF forwards a message for instructing the AMF to set the state of the PDU session to an idle state to the SMF.
  • the SMF sets a state of the PDU session to an idle state.
  • S513b The SMF sends a message to the UPF to indicate that the information related to the AN corresponding to the PDN session is deleted.
  • the message for indicating deletion of information related to the PDN session may be a PDU Session Inactive Response message.
  • the PDU Session Inactive response message carries the PDU Session ID.
  • the UPF deletes the AN-related information corresponding to the PDN session.
  • the UPF can also delete the NG3 interface information corresponding to the PDU session.
  • the timer of the PDU session is configured in the UPF, which can reduce the complexity of the AN based PDU session monitoring timer.
  • the AN can configure a timer for each UE separately, and the timers of the UE and the timers of the PDU sessions are independent of each other.
  • the UE detects no data transmission on a certain PDU session and continues until the timer expires.
  • the indication information is the SM handling for Session Idle as an example.
  • the UE sends, by the AN, a first message to the SMF to indicate that the PDU session is converted to an idle state.
  • the first message may be a PDU Session Inactive Request message.
  • the ID of the PDU session can be carried in the PDU Session Inactive Request message.
  • a cause value (cause) may also be carried in the PDU session Inactive Request message, and the cause value is used to indicate that the timer of the PDU session times out.
  • the first message may be a delete Session request message.
  • the SMF receives the first message triggered by the UE, and then obtains the information based on the information obtained from the PCF.
  • the indication information determines whether the state in which the PDU session is performed is transitioned to the idle state or the deletion of the PDU session is performed.
  • S504c The SMF sends a message to the UPF to indicate that the information related to the AN corresponding to the PDN session is deleted.
  • the message for indicating the deletion of the information related to the PDN session may be a PDU Session Inactive Request message, and the PDU session inactivation request is taken as an example in FIG. 5C.
  • the PDU Session Inactive Request message carries the PDU Session ID.
  • the PDU Session Inactive Request message may also carry a cause value, and the cause value indicates that the timer expires (Session Inactive timer expires).
  • the UPF deletes the information related to the AN corresponding to the PDN session.
  • the UPF can also delete the NG3 interface information corresponding to the PDU session.
  • it also includes:
  • S506c The UPF sends a PDU Session Inactive Request Response (PDU Session Inactive Request Response) message to the SMF.
  • PDU Session Inactive Request Response PDU Session Inactive Request Response
  • S507c The SMF sends a PDU Session Inactive Request Response (PDU Session Inactive Request Response) message to the AMF.
  • PDU Session Inactive Request Response PDU Session Inactive Request Response
  • the AMF sets the state of the PDU session to an idle state.
  • the SMF sets the state of the PDU session to an idle state (Session-IDLE).
  • the SMF sets the state of the PDU session to the idle state (Session-IDLE), and may also be after receiving the first message.
  • the AMF sends a message to the AN to instruct the AN to release the context of the PDU session.
  • the message for indicating that the base station releases the context of the PDU session may be a session context release command or a PDU session inactivity request response message.
  • S510c The AN deletes or suspends the corresponding radio resource of the PDU session.
  • mapping relationship between the data of the PDU session and the DRB is deleted.
  • the AN may also delete the mapping relationship between the QoS flow and the DRB corresponding to the PDU session.
  • the AN updates the AS-level filter, and the filter is used by the AN to perform mapping of the QoS flow to the DRB.
  • the information related to the PDU session in the AS-level filter may be deleted, or the AS-level filter may be in session with the PDU. Relevant information is marked as inactive or idle.
  • S511c The AN sends a message to the UE to instruct the UE to delete or suspend the radio resource corresponding to the PDU session.
  • the message for instructing the UE to delete or suspend the radio resource corresponding to the PDU session may be an RRC Connection Reconfiguration message.
  • the message for instructing the UE to delete or suspend the radio resource corresponding to the PDU session may carry the identifier of the radio resource bearer DRB to be deleted or suspended.
  • S512c The UE deletes or suspends the DRB corresponding to the PDU session.
  • the UE may also set the state of the PDU session to an idle state.
  • the UE may also delete the mapping relationship between the QoS flow of the PDU session and the DRB.
  • the UE sets the state of the PDU session to an idle state, it is determined that all radio resources corresponding to the PDU session are deleted or suspended.
  • S513c The UE sends an RRC Connection Reconfiguration Complete message to the AN.
  • S514c The AN sends a PDU session context release complete message to the AMF.
  • the state of the PDU session may be an idle state or an active state. Therefore, after the PDU session of the last active state on the UE is converted to the idle state, the UE transitions to the idle state.
  • the AN When the UE is in the RRC inactive connection state, after the PDU session enters the idle state, the AN sets the state of the PDU session to the idle state. Therefore, after the UE enters the RRC connected state, it needs to synchronize the state of the PDU session with the AN.
  • FIG. 6A it is a schematic diagram of a state synchronization process corresponding to the UE being in an RRC inactive connection state.
  • the UE determines that it is in an RRC inactive connection state.
  • S602a When uplink data arrives or a paging request is received, the UE sends a request message for instructing to restore the RRC connection of the UE to the AN.
  • the request message for indicating that the RRC connection of the UE is restored may be an RRC Connection Resume Request (RRC Connection Resume Request) message.
  • the request message for instructing to restore the RRC connection of the UE carries a parameter, and the parameter may include an identifier of the PDU session or an identifier of the DRB corresponding to the PDU session.
  • the parameter may further include first state information of the QoS flow corresponding to the PDU session, where the first state information indicates that the state of the QoS flow on the UE is an active state or an inactive state, and is used by the AN and the The UE synchronizes the state of the QoS flow.
  • the PDU session corresponding to the identifier of the PDU session may be a PDU session with data transmission requirements, or a PDU session to be activated.
  • the request message for indicating that the RRC connection of the UE is restored may also carry an PDU session status information (Established PDU Session Status) for indicating that the PDU session established by the AN is The state on the UE is an active state or an idle state.
  • PDU session status information (Established PDU Session Status) for indicating that the PDU session established by the AN is The state on the UE is an active state or an idle state.
  • the AN determines a PDU session to be activated according to the parameter carried in the foregoing request message for instructing to restore the RRC connection of the UE.
  • the state of the PDU session to be activated is an idle state.
  • the AN triggers a process of activating the PDU session.
  • the activation of the PDU session means that the user plane connection from the UE to the UPF corresponding to the PDU session is established.
  • the AN triggers the process of activating the PDU session, and specifically, the AN sends a message to the SMF to trigger the conversion of the PDU session to an active state.
  • the SMF After receiving the message for triggering the conversion of the PDU to an active state, the SMF performs a process of converting the PDU session to an active state.
  • the AN configures a mapping relationship between the QoS flow corresponding to the PDU session and the DRB.
  • the AN sends the configured mapping relationship to the UE.
  • the AN sends the second state information of the QoS flow corresponding to the PDU session to the terminal, to indicate that the terminal synchronizes the state of the QoS with the base station.
  • the second state information indicates that the state of the QoS flow corresponding to the PDU session on the AN is an active state or an inactive state (idle state).
  • step S607a and the steps S605a to S606a do not distinguish the order.
  • the AN may send the configured mapping relationship to the UE in an RRC connection recovery response message, where the RRC connection recovery response message is taken as an example in FIG. 6A.
  • the second state information of the QoS flow corresponding to the PDU session may also be carried in the RRC connection recovery response message and sent by the AN to the UE.
  • the UE synchronizes a state of the QoS flow corresponding to the PDU session with the AN according to the second state information, and the UE saves the mapping relationship.
  • the UE is in a connection management (CM) idle state.
  • CM connection management
  • S601b The UE sends a request message to the SMF through the AMF.
  • the request message may also be a service request (Service Request) message or may be an active session request (Active Session Request) message.
  • the Active Session Request message is used as an example in FIG. 6B.
  • the Active Session Request message carries a parameter, and the parameter may include an identifier of the PDU session or an identifier of the DRB corresponding to the PDU session.
  • the parameter may further include status information of the QoS flow corresponding to the PDU session, where the status information indicates that the status of the QoS flow on the UE is an active state or an inactive state, and the SMF is used to synchronize the QoS with the UE.
  • the state of the stream is used as an example in FIG. 6B.
  • the Active Session Request message carries a parameter, and the parameter may include an identifier of the PDU session or an identifier of the DRB corresponding to the PDU session.
  • the parameter may further include status information of the QoS flow corresponding to the PDU session
  • the PDU session corresponding to the identifier of the PDU session may be a PDU session with data transmission requirements, or a PDU session to be activated.
  • the Active Session Request message may further include an PDU session status of the PDU session, where the status of the PDU session established by the SMF is activated or Idle state. Thereby for state synchronization of the PDU session between the UE and the SMF.
  • the SMF After receiving the request message sent by the UE, the SMF completes activation of the QoS flow in the PDU session with the UPF.
  • the SMF determines a state of the QoS flow in the PDU session after the activation is completed.
  • the SMF After determining the state of the QoS flow in the PDU session after the activation is completed, the SMF sends the status information of the QoS flow in the PDU session to the UE.
  • the status information of the QoS flow in the PDU session indicates that the state of the QoS flow corresponding to the PDU session on the SMF is an active state or an inactive state.
  • the SMF sends the status information of the QoS flow in the PDU session to the UE by using the AMF and the AN.
  • the SMF may first send the status information of the QoS flow in the PDU session to the AMF by activating an Active Session Response message.
  • the AMF carries the status information of the QoS flow in the PDU session in a Session Context Update message, or carries the message to the AN in an Active Session Response message.
  • the AN may synchronize the state of the QoS flow in the PDU session with the SMF, and forward the state to the UE.
  • the AN may send the status information of the QoS flow in the PDU session to the UE by using an RRC Reconfiguration message.
  • the UE according to the status information sent by the SMF, is synchronized with the SMF to synchronize the PDU session.
  • the state of the QoS flow is synchronized with the SMF to synchronize the PDU session.
  • the method may further include:
  • S608b The UE sends an RRC Reconfiguration Response (RRC Reconfiguration Response) message to the AN.
  • RRC Reconfiguration Response RRC Reconfiguration Response
  • the AN sends a session context update response message to the AMF.
  • the AMF sends a session context update response message to the SMF.
  • the SMF sends an Update Session Response message to the AMF.
  • FIG. 7 is a schematic diagram of a cell handover procedure.
  • S-AN denotes a source AN
  • T-AN denotes a target AN.
  • the UE sends a measurement report to the S-AN.
  • the measurement report includes the measurement result of the serving cell and the measurement result of the neighboring cell.
  • the S-AN determines to perform cell handover based on the measurement report sent by the UE (English: Handover, referred to as HO).
  • the S-AN sends a handover request message (HO Required) to the AMF.
  • HO Required handover request message
  • the handover request message carries an identifier of a PDU session on the UE.
  • the state of the PDU session corresponding to the identifier of the PDU session is an active state.
  • the PDU session corresponding to the identifier of the PDU session is a PDU session corresponding to the UE and having a PDU session context saved in the S-AN.
  • the AMF determines, according to the identifier of the PDU session, a PDU session that needs to update a user plane context.
  • the AMF sends a message to the SMF to notify the SMF to update the user plane context of the PDU session.
  • the message for notifying the SMF to update the user plane context of the PDU session may be a HO Request message, and the handover request is taken as an example in FIG. 7 .
  • the HO Request message sent to the SMF carries the identifier (ID) of the PDU session.
  • the SMF sends a HO Request message to the T-AN through the AMF.
  • the HO Request message sent to the T-AN may carry related information (PDU session Info) of the PDU session. Specifically, it includes QoS information corresponding to the PDU session, NG3 tunnel information, and QoS flow ID.
  • the T-AN sends a HO Request Acknowledge to the AMF.
  • the AMF sends a handover command (HO command) to the UE through the S-AN.
  • HO command a handover command
  • the T-AN sends a handover notification (HO notify) to the SMF through the AMF.
  • HO notify handover notification
  • S711 The SMF sends a Modify Session Request message to the UPF to instruct the UPF to modify related information of the PDU session.
  • the UPF sends a Modify Session request response message to the SMF.
  • S-AN indicates the source AN that the terminal is currently accessing
  • T-AN indicates the target AN to which the UE is to be cut.
  • the S-AN configures a timer of the PDU session.
  • the S-AN currently accessed by the UE receives the timer of the PDU session sent by the SMF, and the S-AN configures a timer to the PDU session.
  • the S-AN After the S-AN receives the timer of the PDU session sent by the SMF, if the S-AN detects that no data transmission continues on the PDU session until the timer expires, the S-AN The status of the PDU session is recorded as inactive.
  • the PDU session is recorded as an inactive PDU session, or the PDU session ID is marked, etc., or the PDU session ID used to characterize the PDU session is inactive. .
  • the S-AN determines, when performing the handover from the S-AN to the T-AN for the UE, determining a first type of PDU session included in the activated PDU session of the UE, the first type of PDU session. Performing a handover procedure for the second type of PDU session, which is an inactive PDU session, the second type of PDU session being a PDU other than the first type of session in the PDU session of the terminal Session (active PDU session).
  • the S-AN receives a measurement report sent by the UE, and the S-AN determines, according to the measurement report, whether to perform handover from the S-AN to the T-AN for the UE. If it is determined that the handover from the S-AN to the T-AN is performed for the UE, it is determined that a PDU session recorded as an inactive state in all activated PDU sessions of the current terminal is determined, so that the first type of PDU session is not The handover procedure is performed, and the handover procedure is performed only for the second type of PDU session.
  • the performing, by the S-AN, the handover procedure for the second type of PDU session includes: the S-AN sending a handover request to the T-AN.
  • the handover request may only carry the identifier of the second type of PDU session, and does not carry the identifier of the first type of PDU session.
  • the handover request may be an identifier that carries the first type of PDU session and an identifier of the second type of PDU session.
  • the ID of the first type of PDU session is configured in array 1
  • the ID of the second type of PDU session is configured in array 2.
  • the handover request may further carry an identifier of all activated PDU sessions of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • all activated PDU session IDs of the terminal are placed in an array, and the first type of PDU session and the second type of PDU session are distinguished by different tags, for example, the first type of PDU session is marked as 0, and the second type of PDU session is marked. Marked as 1.
  • the identifier (ID) of the activated PDU session of the UE or the first type of PDU session ID or the second type of PDU session ID may be carried in the context of the active PDU session (active PDU session info), and may also be Carrying outside the active PDU session info.
  • the switch request can carry AS content.
  • the AS content may include the context of all activated PDU sessions of the terminal.
  • the ID of the activated PDU session of the terminal is included in the context of all the activated PDU sessions of the terminal, and the ID of the first type of PDU session is carried in the handover request, and the ID of the first type of PDU session is also carried in the handover request, or
  • the IDs of all activated PDU sessions and the first indication are also carried out outside the context of all active PDU sessions of the terminal and in the handover request.
  • the AS content in the handover request may include only the context of the second type of PDU session (active PDU session info), and the ID of the first type of PDU session (inactive PDU session IDs) other than the active PDU session info and the handover request. ).
  • the switch request carries only the active PDU session info.
  • the performing, by the S-AN, the handover procedure for the second type of PDU session includes: the S-AN sending a handover request to the AMF.
  • the handover request may only carry the identifier of the second type of PDU session, and does not carry the identifier of the first type of PDU session.
  • the switch please The request may be an identifier carrying the first type of PDU session and an identifier of the second type of PDU session.
  • the ID of the first type of PDU session is configured in array 1
  • the ID of the second type of PDU session is configured in array 2.
  • the handover request may further carry an identifier of all activated PDU sessions of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • all activated PDU session IDs of the terminal are placed in an array, and the first type of PDU session and the second type of PDU session are distinguished by different tags, for example, the first type of PDU session is marked as 0, and the second type of PDU session is marked. Marked as 1.
  • the identifier (ID) of the activated PDU session of the UE or the first type of PDU session ID or the second type of PDU session ID may be carried in the context of the active PDU session (active PDU session info), and may also be Carrying outside the active PDU session info.
  • the switch request can carry a transparent container (source to target transparent container).
  • the source to target transparent container may include the context of all activated PDU sessions of the terminal.
  • the ID of the activated PDU session of the terminal is included in the context of all the activated PDU sessions of the terminal, and the ID of the first type of PDU session is carried in the handover request, and the ID of the first type of PDU session is also carried in the handover request, or
  • the IDs of all activated PDU sessions and the first indication are also carried out outside the context of all active PDU sessions of the terminal and in the handover request.
  • the AS content in the handover request may include only the context of the second type of PDU session (active PDU session info), and the ID of the first type of PDU session (inactive PDU session IDs) other than the active PDU session info and the handover request. ), or, the switch request carries only the active PDU session info.
  • an interface switching based on Xn (an interface between AN and AN) is shown.
  • the active PDU session info is included in the AS content of the handover request
  • the ID of the first PDU session is included in the handover request. .
  • S901a When the PDU session of the terminal is established or activated, the S-AN configures a timer of the PDU session.
  • the S-AN currently accessed by the UE receives the timer of the PDU session sent by the SMF, and the S-AN configures a timer to the PDU session.
  • the PDU session is recorded as an inactive PDU session, or the PDU session ID is marked, etc., or the PDU session ID used to characterize the PDU session is inactive.
  • the UE sends a measurement report to the S-AN.
  • the S-AN receives a measurement report sent by the UE, and the S-AN determines, according to the measurement report, whether to perform handover from the S-AN to the T-AN for the UE.
  • the S-AN Determining, by the S-AN, a first type of PDU session included in an activated PDU session of the UE when determining to perform handover from the S-AN to the T-AN for the UE, the first type of PDU session is a record
  • a handover procedure is performed for the second type of PDU session, the second type of PDU session being a PDU session of the terminal's PDU session other than the first type of session.
  • the performing, by the S-AN, the handover process for the second type of PDU session includes:
  • the S-AN sends a handover request to the T-AN.
  • the T-AN sends a handover request ACK to the S-AN.
  • the handover request receipt may include a context of the second type of PDU session parsed by the T-AN from the As content and an ID of the first type of PDU session (inactive PDU session IDs).
  • the S-AN sends a message to the UE for instructing the terminal to perform an operation of invalidating the first type of PDU session.
  • the message for instructing the terminal to perform the operation of invalidating the first type of PDU session carries: an identifier of the first type of PDU session; or the indication that the terminal performs invalidation
  • the message of the operation of the first type of PDU session carries: an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to identify a first type of PDU session in the activated PDU session of the terminal .
  • the message for instructing the terminal to perform an operation of invalidating the first type of PDU session may be an RRC reconfiguration message, which is taken as an example in FIG. 14A.
  • the RRC reconfiguration (RRC reconfiguration) message carries the ID of the first type of PDU session.
  • the operation of invalidating the first type of PDU session in FIG. 14A is an example of converting the state of the first type of PDU session from an active state to an idle state.
  • the UE sends an RRC reconfiguration complete (RRC reconfiguration complete) message to the S-AN.
  • RRC reconfiguration complete RRC reconfiguration complete
  • S909a The UE updates the state corresponding to the first PDU session (inactive PDU session) in the RRC reconfiguration message to the idle state (session-IDLE).
  • S910a-S916a is a process for performing core network path switching for a second type of PDU session.
  • the T-AN sends an N2 path switch (N2path switch) message to the AMF, and the N2path switch carries the context of the second type of PDU session.
  • the N2path switch can also carry the identity of the first type of PDU session.
  • N2 is the interface between the base station and the AMF.
  • the N2path switch is used to instruct the AMF to transfer the path from the S-AN to the T-AN, updating the context of the second type of PDU session.
  • N11 N11 message
  • N11 is the interface between SMF and AMF. N11message is used to instruct the SMF to update the context of the second type of PDU session.
  • the SMF sends an N4 session modification to the UPF, and the N4 session modify carries the context of the second type of PDU session.
  • N4 is the interface between the SMF and the UPF.
  • the UPF sends an N4 session modify receipt (ACK) to the SMF.
  • ACK N4 session modify receipt
  • the SMF sends an N11session modify ACK to the AMF.
  • the AMF sends an N2path switch ACK to the T-AN.
  • the T-AN sends a UE context release message to the S-AN.
  • the AMF is based on the second The identity of the class PDU session determines the first type of PDU session.
  • the AMF stores the identity of all activated PDU sessions of the terminal, such that the AMF determines a saved PDU session of the activated PDU session of the terminal other than the second type of PDU session corresponding to the identity.
  • the AMF sends a message to the SMF to instruct the SMF to perform an operation of invalidating the first type of PDU session.
  • the message for the SMF to indicate that the operation of invalidating the first type of PDU session is performed may be N11message.
  • the SMF can be directly executed.
  • the SMF sends a message to the UPF to instruct the UPF to perform an operation that invalidates the first type of PDU session.
  • the message for the SMF to indicate that the operation of invalidating the first type of PDU session is performed may be an N4 session transition to a session-IDLE transition.
  • the UPF converts the state of the first type of PDU session to an idle state.
  • the operation of invalidating the first type of PDU session in FIG. 14A is an example of transitioning the state of the first type of PDU session to an idle state.
  • the UPF sends a message to the SMF to indicate that the operation of invalidating the first type of PDU session is performed.
  • the message for indicating the completion of the operation of invalidating the first type of PDU session may be an N4 session-IDLE transition complete message.
  • the SMF performs to convert the state of the first type of PDU session to an idle state.
  • the SMF sends a message to the AMF indicating that the operation of invalidating the first type of PDU session is performed.
  • a message indicating that the operation to complete the invalidation of the first type of PDU session is performed may pass the N11message ACK.
  • the AMF performs to convert the state of the first type of PDU session to an idle state.
  • an interface switching based on Xn an interface between AN and AN
  • the active PDU session info is included in the AS content of the handover request
  • the ID (inactive PDU session IDs) of the first type of PDU session is not included in the handover request.
  • S901b When the PDU session of the terminal is established or activated, the S-AN configures a timer of the PDU session.
  • the S-AN currently accessed by the UE receives the timer of the PDU session sent by the SMF, and the S-AN configures a timer to the PDU session.
  • the PDU session is recorded as an inactive PDU session, or the PDU session ID is marked, etc., or the PDU session ID used to characterize the PDU session is inactive.
  • S903b The UE sends a measurement report to the S-AN.
  • the S-AN receives a measurement report sent by the UE, and the S-AN determines, according to the measurement report, whether to perform handover from the S-AN to the T-AN for the UE.
  • the S-AN Determining, by the S-AN, a first type of PDU session included in an activated PDU session of the UE when determining to perform handover from the S-AN to the T-AN for the UE, the first type of PDU session is a record
  • a handover procedure is performed for the second type of PDU session, the second type of PDU session being a PDU session of the terminal's PDU session other than the first type of session.
  • the performing, by the S-AN, the handover process for the second type of PDU session includes:
  • the S-AN sends a handover request to the T-AN.
  • the T-AN sends a handover request ACK to the S-AN.
  • the handover request receipt may include the context of the second type of PDU session parsed by the T-AN from Ascontent.
  • the S-AN sends an RRC reconfiguration (RRC reconfiguration) message to the UE.
  • RRC reconfiguration RRC reconfiguration
  • S908b The UE sends an RRC reconfiguration complete (RRC reconfiguration complete) message to the S-AN.
  • S909b-S915b is a process of performing core network path switching for the second type of PDU session.
  • the T-AN sends an N2 path switch (N2path switch) message to the AMF, and the N2path switch carries the context of the second type of PDU session.
  • N2 is the interface between the base station and the AMF.
  • the N2path switch is used to instruct the AMF to transfer the path from the S-AN to the T-AN, updating the context of the second type of PDU session.
  • N11 N11 message
  • N11 is the interface between SMF and AMF. N11message is used to instruct the SMF to update the context of the second type of PDU session.
  • the SMF sends an N4 session modification to the UPF, and the N11path switch carries the context of the second type of PDU session.
  • N11 is the interface between SMF and AMF.
  • the UPF sends an N11 session modify acknowledgment (ACK) to the SMF.
  • ACK N11 session modify acknowledgment
  • the SMF sends an N11session modify ACK to the AMF.
  • the AMF sends an N2path switch ACK to the T-AN.
  • the T-AN sends a UE context release message to the S-AN.
  • the AMF determines the first type of PDU session based on the identifier of the second type of PDU session.
  • the AMF stores the identity of all activated PDU sessions of the terminal, such that the AMF determines a saved PDU session of the activated PDU session of the terminal other than the second type of PDU session corresponding to the identity.
  • the AMF sends a message to the SMF to instruct the SMF to perform an operation of invalidating the first type of PDU session.
  • a message for the SMF to indicate that the operation of invalidating the first type of PDU session is performed may be passed through N11message.
  • the SMF sends a message to the UPF to instruct the UPF to perform an operation of invalidating the first type of PDU session.
  • the message for instructing the UPF to perform an operation that invalidates the first type of PDU session may be an N4 session-IDLE transition.
  • the UPF converts the state of the first type of PDU session to an idle state.
  • the operation of invalidating the first type of PDU session in FIG. 14B is an example of transitioning the state of the first type of PDU session to an idle state.
  • the UPF sends a message to the SMF to indicate that the operation of invalidating the first type of PDU session is performed.
  • the SMF performs to convert the state of the first type of PDU session to an idle state.
  • the SMF sends a message to the AMF indicating that the operation of invalidating the first type of PDU session is performed.
  • a message indicating that the operation to complete the invalidation of the first type of PDU session is performed may pass the N11message ACK.
  • the AMF performs to convert the state of the first type of PDU session to an idle state.
  • the AMF sends a message to the UE for instructing the UE to perform an operation of invalidating the first type of PDU session.
  • the message for instructing the UE to perform the operation of invalidating the first type of PDU session may be an N1 session-IDLE transition request.
  • the N1 session-IDLE transition request carries the identifier of the first type of PDU session, or the identifier of the activated PDU session carrying the terminal and the first indication.
  • N1 is the interface between the AMF and the UE.
  • the UE updates the status of the first type of PDU session to an idle state.
  • S926b The UE sends a message to the AMF to indicate that an operation to invalidate the first type of PDU session is performed.
  • the message indicating that the operation to invalidate the first type of PDU session is completed may be an N1 session-IDLE transition response.
  • the source to target transparent container includes the context of the second type of PDU session (active PDU session info), and the ID of the first type of PDU session (inactive PDU) is included in the handover request. Session IDs) as an example.
  • S901c When the PDU session of the terminal is established or activated, the S-AN configures a timer of the PDU session.
  • the S-AN currently accessed by the UE receives the timer of the PDU session sent by the SMF, and the S-AN configures a timer to the PDU session.
  • the PDU session is recorded as an inactive PDU session, or the PDU session ID is marked, etc., or the PDU session ID used to characterize the PDU session is inactive.
  • S903c The UE sends a measurement report to the S-AN.
  • the S-AN receives a measurement report sent by the UE, and the S-AN determines, according to the measurement report, whether to perform handover from the S-AN to the T-AN for the UE.
  • the S-AN Determining, by the S-AN, a first type of PDU session included in an activated PDU session of the UE when determining to perform handover from the S-AN to the T-AN for the UE, the first type of PDU session is a record
  • a handover procedure is performed for the second type of PDU session, the second type of PDU session being a PDU session of the terminal's PDU session other than the first type of session.
  • the performing, by the S-AN, the handover process for the second type of PDU session includes:
  • the S-AN sends a handover request to the AMF.
  • the source to target transparent container includes the context of the second type of PDU session (active PDU session info), and the ID of the second type of PDU session is carried outside the active PDU session info (active) PDU session IDs).
  • the handover requirement is used to indicate that the handover operation is not performed for other PDU sessions (ie, the first type of PDU session) other than the second type of PDU session, that is, the operation of the other PDU session other than the invalid second type PDU session is performed. Invalidating the first type of PDU session to update the state of the first type of PDU session to an idle state or to delete the first type of PDU session
  • the AMF sends an N11 handover request (N2handover required) message to the SMF.
  • the SMF sends an N11 handover request (N11handover request) to the AMF, and the N11 handover request carries the context (PDU session info) of all activated PDU sessions of the terminal.
  • the AMF sends a handover request to the T-AN, the handover request carrying a transparent container (source to target transparent container).
  • the T-AN sends a handover request ACK to the AMF.
  • the handover request ACK carries a transparent container (source to target transparent container).
  • the AMF sends a handover request ACK to the SMF, where the handover request ACK carries the context of the PDU session.
  • the SMF sends an N11 handover command (N11handover command) to the AMF.
  • N11handover command N11handover command
  • the AMF sends a handover command to the UE through the S-AN.
  • S913c The UE sends a handover cofirm to the T-AN.
  • the T-AN sends a handover notify to the AMF.
  • a handover notify is used to instruct the AMF to convert the terminal's PDU session from the S-AN to the T-AN.
  • the AMF determines a first type of PDU session based on an identifier of the second type of PDU session.
  • the AMF holds the identity of all activated PDU sessions of the terminal, so that the AMF determines the saved activated PDU of the terminal.
  • the identifier of the second type PDU session is carried in the S-AN.
  • the AMF determines a first type of PDU session based on the identifier of the second type of PDU session, and then the AMF performs to update the status of the first type of PDU session to an idle state or delete the first type. PDU session.
  • the AMF sends a handover notify to the SMF.
  • the handover notify carries an identifier of the first type of PDU session, and is used to instruct the AMF to convert the PDU session of the terminal from the S-AN to the T-AN.
  • S917c Perform a PDU session modification between the SMF and the UPF.
  • the AMF After determining the first type of PDU session based on the identifier of the second type of PDU session, the AMF sends a message to the SMF to instruct the SMF to perform an operation of invalidating the first type of PDU session.
  • the message indicating that the SMF performs an operation that invalidates the first type of PDU session may be N11message.
  • the message indicating that the SMF performs the operation of invalidating the first type of PDU session may carry the identifier of the first type of PDU session.
  • the SMF sends a message to the UPF to instruct the UPF to perform an operation of invalidating the first type of PDU session.
  • the message for instructing the UPF to perform an operation that invalidates the first type of PDU session may be an N4 session-IDLE transition.
  • the UPF converts the state of the first type of PDU session to an idle state.
  • the UPF sends a message to the SMF to indicate that the operation of invalidating the first type of PDU session is performed.
  • the SMF performs to convert the state of the first type of PDU session to an idle state.
  • S923c The SMF sends a message to the AMF to indicate that the operation of invalidating the first type of PDU session is performed.
  • a message indicating that the operation to complete the invalidation of the first type of PDU session is performed may pass the N11message ACK.
  • the AMF performs to convert the state of the first type of PDU session to an idle state.
  • the AMF sends a message to the UE for instructing the UE to perform an operation of invalidating the first type of PDU session.
  • the message for instructing the UE to perform an operation that invalidates the first type of PDU session may be an N1 session-IDLE transition request.
  • N1 is the interface between the AMF and the UE.
  • the UE updates a status of the first type of PDU session to an idle state.
  • S927c The UE sends a message to the AMF to indicate that an operation to invalidate the first type of PDU session is performed.
  • the message indicating that the operation to invalidate the first type of PDU session is completed may be an N1 session-IDLE transition response.
  • the embodiment of the present application further provides a session management device. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method may be referred to each other, and the repeated description is not repeated.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a first core network device, including, as shown in FIG. 8A.
  • the receiving module 801a is configured to receive a request message for activating a packet data unit PDU session
  • a sending module 802a configured to send a timer of the PDU session to the second device
  • the receiving module 801a is further configured to receive a first message initiated by the second device to invalidate an operation of the PDU session, where the first message is that the second device detects that there is no data on the PDU session. Transmitted and continued until the timer expires.
  • the second device is a second core network device, or is a base station, or is a terminal.
  • the invalidating the PDU session includes: converting the PDU session from an active state to an idle state or deleting the PDU session.
  • it also includes:
  • the first determining module 803a is configured to determine a timer of the PDU session based on slice information of a network slice to which the PDU session belongs before the sending module 802a sends the timer to the second device.
  • the receiving module 801a is further configured to receive a timer of the PDU session sent by the third core network device.
  • the sending module 802a is further configured to send indication information to the second device, where the indication information is information used to indicate the operation of invalidating the PDU session.
  • the receiving module 801a is further configured to: after receiving the request message, receive indication information sent by a third core network device, where the indication information is used to indicate the invalidation. Information about the operation of the PDU session.
  • the second determining module 804a is configured to, after the receiving module 801a receives the first message, determine, according to the indication information, that the operation of invalidating the PDU session is to be The PDU session is transitioned from an active state to an idle state or to delete the PDU session.
  • the first message carries an identifier of the PDU session.
  • the first message further carries a cause value, and the cause value is used to indicate that the timer of the PDU session times out.
  • the operation of invalidating the PDU session is to convert the PDU session from an active state to an idle state
  • the receiving module 801a is further configured to: after receiving the first message, Sending, to the second core network device, a message indicating that the base station-related information corresponding to the PDN session is deleted.
  • the operation of invalidating the PDU session is to convert the PDU session from an active state to an idle state, and the apparatus further includes:
  • the processing module 805a is configured to set the state of the PDU session to an idle state after the receiving module 801a receives the first message.
  • the operation of invalidating the PDU session is to delete the PDU session
  • the sending module is further configured to: after the receiving module 801a receives the first message, to the The second core network device sends a message indicating the deletion of information related to the PDN session.
  • the operation of invalidating the PDU session is to delete the PDU session
  • the sending module is further configured to send, after receiving the first message, a The terminal deletes the message of the information related to the PDN session.
  • the sending module 802a is further configured to: after the receiving module 801a receives the first message, send a message to the base station to instruct the base station to release the context of the PDU session.
  • the sending module 802a is further configured to send, after the receiving module 801a receives the first message, a fourth core network device, to indicate that the fourth core network device The status of the PDU session is set to a message in an idle state.
  • the receiving module 801a is further configured to receive a second message sent by the fourth core network device, where the second message carries an identifier of the PDU session of the user plane context to be updated;
  • the device also includes:
  • the update module 806a is configured to update a user plane context of the PDU session corresponding to the identifier of the PDU session.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a first core network device, as shown in FIG. 8B, and includes:
  • the receiving module 801b is configured to receive a service request message sent by the terminal, where the service request message carries an identifier of the PDU session to be activated.
  • the processing module 802b is configured to perform a process of activating the PDU session based on the service request message.
  • the service request message carries first state information of a quality of service QoS flow corresponding to the PDU session; the first state information indicates that the QoS flow corresponding to the PDU session is in the first
  • the state on a core network device is an active state or an inactive state, and is used by the first core network device to synchronize the state of the QoS flow with the terminal.
  • the device further includes:
  • a sending module 803b configured to send third state information of the QoS flow corresponding to the PDU session to the terminal, to indicate that the terminal synchronizes with the first core network device to a state of the QoS flow corresponding to the PDU session
  • the third state information indicates that the state of the QoS flow corresponding to the PDU session on the first core network device is an active state or an inactive state.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the first core network device can include a processor 820.
  • the hardware of the entity corresponding to the module shown in FIG. 8A or 8B above may be the processor 820.
  • the processor 820 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing module or the like.
  • the first core network device can also include a communication interface 810 through which the processor 820 receives data or messages.
  • the apparatus also includes a memory 830 for storing programs executed by the processor 820.
  • the memory 830 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD), or a volatile memory (English: volatile) Memory), such as random access memory (English: random-access memory, abbreviation: RAM).
  • Memory 830 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the processor 820 is configured to execute the program code stored in the memory 830, specifically for executing the method performed by the first core network device in the embodiment shown in FIG. 3 to FIG. 7, FIG. 13, and FIG. 14A to FIG. 14C.
  • the method described in the embodiments shown in FIG. 3 to FIG. 7 , FIG. 13 , and FIG. 14A to FIG. 14C may be omitted.
  • connection medium between the communication interface 810, the processor 820, and the memory 830 is not limited in the embodiment of the present application.
  • the memory 830, the processor 820, and the communication interface 810 are connected by a bus 840 in FIG. 8C.
  • the bus is indicated by a thick line in FIG. 8C, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus 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 8C, but it does not mean that there is only one bus or one type of bus.
  • An embodiment of the present application provides a session management apparatus, where the apparatus is applied to a base station, as shown in FIG. 9A, include:
  • the receiving module 901a is configured to receive a timer of the PDU session sent by the first core network device when the packet data unit PDU session is activated;
  • the processing module 902a is configured to detect that there is no data transmission on the PDU session, and continues until the timer expires;
  • the sending module 903a is configured to send, to the first core network device, a first message that invalidates an operation of the PDU session.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the receiving module 901a is further configured to: when the PDU session is activated, receive the indication information sent by the first core network device, where the indication information is used to indicate the invalidation. Information about the operation of the PDU session.
  • the first message carries an identification of the PDU session.
  • the first message further carries a cause value, where the cause value is used to indicate that the timer of the PDU session times out.
  • the receiving module 901a is further configured to receive a message that is sent by the first core network device to instruct the base station to release a context of the PDU.
  • the processing module 902a is further configured to delete or suspend the radio resource corresponding to the PDU session.
  • processing module 902a is further configured to:
  • the state of the saved PDU session is set to an idle state.
  • the processing module 902a is further configured to: when monitoring no data transmission on the PDU session, and after the timer expires, deleting the quality of service QoS corresponding to the PDU session The mapping relationship between the flow and the radio resource bearer DRB.
  • the sending module 903a is further configured to: after the processing module 902a monitors that there is no data transmission on the PDU session, and after the timer expires, send the terminal to the terminal. A message for instructing the terminal to delete or suspend a radio resource corresponding to the PDU session.
  • the message for instructing the terminal to delete or suspend the radio resource corresponding to the PDU session carries: an identifier of the radio resource bearer DRB to be deleted or suspended.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the embodiment of the present application further provides a session management apparatus, where the apparatus is applied to a base station, as shown in FIG. 9B, and includes:
  • the receiving module 901b is configured to receive an RRC connection recovery message sent by the terminal, where the RRC connection recovery message carries a parameter;
  • the processing module 902b is configured to determine a PDU session to be activated according to the parameter; and trigger a process of activating the PDU session.
  • the parameter is an identifier of the PDU session to be activated, or an identifier of a radio resource bearer DRB corresponding to the PDU session to be activated.
  • the state of the PDU session to be activated is an idle state.
  • the RRC connection recovery message further carries first state information of the quality of service QoS flow corresponding to the PDU session; the state information is used by the base station to synchronize the QoS with the terminal The state of the stream.
  • the device further includes:
  • the sending module 903b is configured to send, to the first core network device, a message for triggering to convert the PDU session to an active state.
  • the processing module 902b is further configured to configure a mapping relationship between the QoS flow corresponding to the PDU session and the DRB.
  • it also includes:
  • the sending module 903b is further configured to send the mapping relationship to the terminal.
  • the device further includes:
  • the sending module 903b is configured to send second state information of the QoS flow corresponding to the PDU session to the terminal, to indicate that the terminal synchronizes the state of the QoS with the base station.
  • the processing module 902b is further configured to determine to perform cell handover for the terminal;
  • the sending module 903b is configured to send a handover request message to the fourth core network device, where the handover request message carries an identifier of a PDU session in which the state corresponding to the terminal is an active state, or the handover request carries a corresponding And the identifier of the PDU session in which the base station holds the PDU session context.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the embodiment of the present application further provides a session management apparatus, where the apparatus is applied to a source base station, as shown in FIG. 9D, and includes:
  • the receiving module 901d is configured to receive a timer of the PDU session sent by the first core network device when the PDU session of the terminal is established or activated; if the source base station detects that no data transmission continues on the PDU session If the timer expires, the status of the PDU session is recorded as an inactive state;
  • the processing module 902d is configured to determine, when performing the handover from the source base station to the target base station, the first type of PDU session included in the activated PDU session of the terminal, where the first type of PDU session is The PDU session recorded as an inactive state performs a handover procedure for the second type of PDU session, and the second type of PDU session is a PDU session of the terminal in the PDU session other than the first type of session.
  • the method further includes:
  • the sending module 903d is configured to send, by the processing module 902d, a handover request to the target base station for the second type of PDU session, where the handover request carries only the identifier of the second type of PDU session; or
  • the handover request carries an identifier of the first type of PDU session and an identifier of the second type of PDU session;
  • the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • the sending module 903d is configured to send, in the process of performing the handover for the second type of PDU session, an operation for instructing the terminal to perform the invalidation of the first type of PDU session. Message.
  • the message for indicating that the terminal performs the operation of invalidating the first type of PDU session carries: an identifier of the first type of PDU session; or
  • the message for instructing the terminal to perform the operation of invalidating the first type of PDU session carries: an identifier of the activated PDU session of the terminal, and a first indication, where the first indication is used to identify the terminal The first type of PDU session in the active PDU session.
  • the invalidating the first type of PDU session comprises: converting a state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • the sending module 903d in the device is configured to send a handover request to the fourth core network device when the processing module 902d performs a handover procedure for the second type of PDU session, where the handover The request carries only the identifier of the second type of PDU session; or,
  • the handover request carries an identifier of the first type of PDU session and an identifier of the second type of PDU session;
  • the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark a first type of PDU session in the activated PDU session of the terminal.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the embodiment of the present application further provides a session management apparatus, where the apparatus applies a target base station, as shown in FIG. 9E, and includes:
  • the receiving module 901e receives the handover request sent by the source base station currently accessed by the terminal, where the handover request carries only the identifier of the second type of PDU session; or the handover request carries the first type of PDU session. And an identifier of the second type of PDU session; or the handover request carries an identifier of the activated PDU session of the terminal and a first indication, where the first indication is used to mark the activated PDU of the terminal The first type of PDU session in the identity of the session;
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating; the first type of PDU session is a PDU session recorded as inactive; the record is inactive.
  • the PDU session refers to a PDU session that satisfies no data transmission until the corresponding timer expires; the second type of PDU session is a PDU session other than the PDU session marked as active in the activated PDU session of the terminal;
  • the sending module 902e is configured to send, to the fourth core network device, a message for instructing the fourth core network device to perform an operation of invalidating the first type PDU session.
  • the message for instructing the fourth core network device to perform the operation of invalidating the second type of PDU session carries: an identifier of the first type of PDU session.
  • the operation of invalidating the first type of PDU session includes: converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the base station may include the processor 920.
  • the hardware of the entity corresponding to the module shown in FIG. 9A or 9B or 9D or 9E may be the processor 920.
  • Processor 920 which may be a central processing unit (English: central processing unit, referred to as CPU), or a digital processing module, and the like.
  • the base station can also include a transceiver 910 that receives data, messages, through the transceiver 910.
  • the apparatus also includes a memory 930 for storing programs executed by the processor 920.
  • the memory 930 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD), or a volatile memory (English: volatile) Memory), such as random access memory (English: random-access memory, abbreviation: RAM).
  • Memory 930 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the processor 920 is configured to execute the program code stored in the memory 930, specifically for performing the method performed by the base station in the embodiment shown in FIG. 3 to FIG. 7, FIG. 13, and FIG. 14A to FIG. 14C.
  • the method described in the embodiments shown in FIG. 3 to FIG. 7 , FIG. 13 , and FIG. 14A to FIG. 14C may be omitted.
  • connection medium between the above transceiver 910, the processor 920, and the memory 930 is not limited in the embodiment of the present application.
  • the memory 930, the processor 920, and the transceiver 910 are connected by a bus 940 in FIG. 9C.
  • the bus is indicated by a thick line in FIG. 9C, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus 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 9C, but it does not mean that there is only one bus or one type of bus.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a terminal, as shown in FIG. 10A, the apparatus includes:
  • the receiving module 1001a is configured to receive, by the base station, a message, used by the base station, to instruct the terminal to delete or suspend a radio resource corresponding to the PDU session;
  • the processing module 1002a is configured to delete or suspend a radio resource corresponding to the PDU session, and set a state of the PDU session to an idle state.
  • the processing module 1002a is further configured to: after the receiving module 1001a receives the message sent by the base station to instruct the terminal to delete or suspend a radio resource corresponding to the PDU session, When it is determined that all radio resources corresponding to the PDU session are deleted or suspended, the state of the PDU session is set to an idle state.
  • the receiving module 1001a is further configured to: before receiving, by the base station, a message for instructing the terminal to delete or suspend a radio resource corresponding to the PDU session, when the PDU session is activated, Receiving a timer of the PDU session sent by the first core network device;
  • the device also includes:
  • the sending module 1003a is further configured to: when the processing module 1002a monitors that there is no data transmission on the PDU session, and continues to send the timer to timeout, send the PDU session invalid to the first core network device. The first message of the operation.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the receiving module 1001a is further configured to: when the PDU session is activated, receive the first indication information sent by the first core network device, where the first indication information is used to indicate The information that invalidates the operation of the PDU session.
  • each functional module in each embodiment of the present application may be integrated into one processing.
  • Device In addition, it may be physically present alone, or two or more modules may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a terminal, as shown in FIG. 10B, the apparatus includes:
  • the receiving module 1003b is configured to receive uplink data or receive a paging request.
  • the processing module 1001b is configured to determine that the receiving module receives the uplink data or receives the paging request.
  • the sending module 1002b is configured to send a request message to the network device, where the request message carries an identifier of the PDU session, and/or carries first state information of the QoS flow corresponding to the PDU session, where the first state information indicates the The state of the QoS flow on the terminal is an active state or an inactive state, and is used by the network device to synchronize the state of the QoS flow with the terminal.
  • the RRC state of the terminal is an RRC inactive connection state
  • the network device is a base station
  • the request message is used to indicate that the RRC connection of the terminal is restored.
  • the receiving module 1003a is further configured to receive second state information of the QoS flow corresponding to the PDU session sent by the base station, where the second state information indicates that the QoS flow is in the The state on the base station is an active state or an inactive state;
  • the processing module 1001b is further configured to synchronize, according to the second state information, the state of the QoS flow corresponding to the PDU session with the base station.
  • the receiving module 1003a is further configured to receive a mapping relationship between the QoS flow and the DRB corresponding to the PDU session sent by the base station;
  • the processing module 1001b is further configured to save the mapping relationship.
  • connection management CM state of the terminal is an idle state
  • the network device is a fourth core network device
  • the request message is used to indicate that the terminal is converted from a CM idle state to a CM connection. status.
  • the receiving module 1003a is further configured to receive third state information of the QoS flow corresponding to the PDU session sent by the first core network device, where the third state information indicates The state of the QoS flow corresponding to the PDU session on the first core network device is an active state or an inactive state;
  • the processing module 1001b is further configured to synchronize, according to the third flow state information, the state of the QoS flow corresponding to the PDU session with the first core network device.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a terminal, as shown in FIG. 10D, the apparatus includes:
  • the receiving module 1001d is configured to receive, during the process of the terminal switching from the currently accessed source base station to the target base station, the PDU session sent by the source base station or the fourth core network device to indicate that the first type of packet data unit is invalid. Message of operation
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating; the first type of PDU session is a PDU session recorded as inactive; the record is inactive.
  • a PDU session refers to a PDU session that satisfies the no-data transmission duration until the corresponding timer expires;
  • the processing module 1002d is configured to perform an operation of invalidating the first type of PDU session based on the message.
  • the message for instructing the terminal to perform an operation of invalidating the first type of packet data unit PDU session carries: an identifier of the first type of PDU session.
  • the message for indicating an operation of invalidating the first type of packet data unit PDU session carries: an identifier of the activated PDU session of the terminal, and a first indication, the first indication a first type of PDU session in an activated PDU session for marking the terminal;
  • the performing, by the terminal, the operation of invalidating the first type of PDU session based on the message includes:
  • the operation of invalidating the first type of PDU session includes:
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the terminal can include a processor 1020.
  • the hardware of the entity corresponding to the module shown in FIG. 10A or 10B or 10D may be the processor 1020.
  • the processor 1020 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing module or the like.
  • the terminal can also include a transceiver 1010 that receives data, messages through the transceiver 1010.
  • the apparatus also includes a memory 1030 for storing programs executed by the processor 1020.
  • the memory 1030 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD), or a volatile memory (English: volatile) Memory), such as random access memory (English: random-access memory, abbreviation: RAM).
  • Memory 1030 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the processor 1020 is configured to execute the program code stored in the memory 1030, specifically for executing the method performed by the terminal in the embodiment shown in FIG. 3 to FIG. 7, FIG. 13, and FIG. 13A to FIG. 13C.
  • the method described in the embodiments shown in FIG. 3 to FIG. 7 , FIG. 13 , and FIG. 14A to FIG. 14C may be omitted.
  • connection medium between the above transceiver 1010, the processor 1020, and the memory 1030 is not limited in the embodiment of the present application.
  • the memory 1030, the processor 1020, and the transceiver 1010 are connected by a bus 1040 in FIG. 10C.
  • the bus is indicated by a thick line in FIG. 10C, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus 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 10C, but it does not mean that there is only one bus or one type of bus.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a second core network device, as shown in FIG. 11A, and includes:
  • the receiving module 1101 is configured to receive a message sent by the first core network device, where the message carries an identifier of the PDU session to be deleted, and is used to indicate that the second core network device deletes the corresponding PDU session corresponding to the identifier.
  • the processing module 1102 is configured to delete information related to the base station corresponding to the PDU session or delete information related to the PDU session.
  • the receiving module 1101 is further configured to: when the PDU session is activated, receive a timer of the PDU session sent by the first core network device;
  • the device also includes:
  • the sending module 1103 is configured to: after the processing module 1102 monitors that there is no data transmission on the PDU session, and continues until the timer expires, sending an operation of invalidating the PDU session to the first core network device. The first message.
  • the invalidating the PDU session includes: converting the state of the PDU session from an active state to an idle state or deleting the PDU session.
  • the receiving module 1101 is further configured to: when the PDU session is activated, receive the indication information sent by the first core network device, where the indication information is to indicate that the PDU session is invalid. Information about the operation.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the second core network device can include a processor 1120.
  • the hardware of the entity corresponding to the module shown in FIG. 11A above may be the processor 1120.
  • the processor 1120 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing module or the like.
  • the second core network device may further include a communication interface 1110, and the processor 1120 receives data and messages through the communication interface 1110.
  • the apparatus also includes a memory 1130 for storing programs executed by the processor 1120.
  • the memory 1130 can be a non-volatile memory, such as a hard disk (English: hard disk drive, abbreviated as HDD) or a solid state drive (English: solid-state drive, abbreviation: SSD), and can also be a volatile memory (English: volatile Memory), such as random access memory (English: random-access memory, abbreviation: RAM).
  • Memory 1130 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the processor 1120 is configured to execute the program code stored by the memory 1130, specifically for performing the method performed by the second core network device in the embodiment shown in FIG. 3 to FIG. 7, FIG. 13, and FIG. 13A to FIG. 13C.
  • the processor 1120 is configured to execute the program code stored by the memory 1130, specifically for performing the method performed by the second core network device in the embodiment shown in FIG. 3 to FIG. 7, FIG. 13, and FIG. 13A to FIG. 13C.
  • the processor 1120 is configured to execute the program code stored by the memory 1130, specifically for performing the method performed by the second core network device in the embodiment shown in FIG. 3 to FIG. 7, FIG. 13, and FIG. 13A to FIG. 13C.
  • connection medium between the communication interface 1110, the processor 1120, and the memory 1130 is not limited in the embodiment of the present application.
  • the memory 1130, the processor 1120, and the communication interface 1110 are connected by a bus 1140 in FIG. 11B.
  • the bus is indicated by a thick line in FIG. 11B, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus 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 FIG. 11B, but it does not mean that there is only one bus or one type of bus.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a fourth core network device.
  • the apparatus includes:
  • the receiving module 1201 is configured to receive, in a cell handover process, an identifier of a PDU session sent by the base station;
  • the processing module 1202 is configured to determine, according to the identifier of the PDU session, a PDU session that needs to update a user plane context;
  • the sending module 1203 is configured to send, to the first core network device, a message for instructing the first core network device to update a user plane context of the PDU session.
  • the receiving module 1201 is further configured to:
  • Receiving sent by the first core network device, and used to indicate that the fourth core network device is to use the PDU session
  • the status is set to the idle state or the message of the PDU session is deleted
  • the processing module 1202 is further configured to set the saved state of the PDU session to an idle state, or delete state information of the PDU session.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the embodiment of the present application provides a session management apparatus, where the apparatus is applied to a fourth core network device, as shown in FIG. 12C, including
  • the receiving module 1201c is configured to: when the terminal switches from the source base station to the target base station, receive an identifier of the second type of PDU session sent by the source base station or the target base station;
  • Each activated PDU session of the terminal is configured with a corresponding timer when establishing or activating, and the second type of PDU session is recorded as inactive in the activated PDU session of the terminal.
  • a PDU session other than the PDU session, the PDU session recorded as inactive refers to a PDU session that satisfies the no-data transmission duration until the corresponding timer expires;
  • the sending module 1202c is configured to send, to the first core network device, a message for instructing the first core network device to update a context of the second type of PDU session.
  • the receiving module 1201c is specifically configured to receive a path switch message sent by the target base station, where the path switch message carries an identifier of the second type of PDU session.
  • the receiving module 1201c is specifically configured to receive a handover request sent by the source base station, where the handover request carries an identifier of the second type of PDU session.
  • the device further includes:
  • the processing module 1203c is configured to determine, according to the identifier of the second type of PDU session, a first type of PDU session, where the first type of PDU session is in the activated PDU session of the terminal saved by the fourth core network device. And identifying, by the PDU session other than the second type of PDU session;
  • the fourth core network device sends a message to the first core network device to indicate that an operation of invalidating the first type of PDU session is performed.
  • the invalidating the operation of the first type of PDU session includes converting the state of the first type of PDU session from an active state to an idle state or deleting the first type of PDU session.
  • the processing module 1203c is further configured to convert the state of the first type of PDU session from an active state to an idle state after determining the first type of PDU session based on the identifier of the first type of PDU session. State or delete the first type of PDU session.
  • the receiving module 1201c is further configured to receive an identifier of a third type of PDU session sent by the source base station or a target base station, where the third type of PDU session is inactive. PDU session;
  • the sending module 1202c is configured to send, to the first core network device, a message for indicating that an operation of invalidating the third type PDU session is performed.
  • the operation of invalidating the third type of PDU session includes:
  • the device further includes:
  • the processing module 1203c is configured to: after the receiving module 1201c receives the identifier of the third type PDU session sent by the source base station or the target base station, convert the state of the third type PDU session from an active state to an idle state or delete The third type of PDU session.
  • the sending module 1202c is further configured to: after the receiving module 1201c receives the identifier of the third type PDU session sent by the source base station or the target base station, the third type PDU The identifier of the session is sent to the terminal, and is used to instruct the terminal to set the state of the third type of PDU session to an idle state.
  • the fourth core network device can include a processor 1220.
  • the hardware of the entity corresponding to the module shown in FIG. 12A or FIG. 12C above may be the processor 1220.
  • the processor 1220 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing module or the like.
  • the fourth core network device can also include a communication interface 1210 through which the processor 1220 receives data and messages.
  • the apparatus also includes a memory 1230 for storing programs executed by the processor 1220.
  • the memory 1230 may be a non-volatile memory, such as a hard disk (English: hard disk drive, abbreviated as HDD) or a solid state drive (English: solid-state drive, abbreviated as SSD), or a volatile memory (English: volatile) Memory), such as random access memory (English: random-access memory, abbreviation: RAM).
  • Memory 1230 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the processor 1220 is configured to execute the program code stored in the memory 1230, specifically for executing the method performed by the fourth core network device in the embodiment shown in FIG. 3 to FIG. 7, FIG. 13, and FIG. 14A to FIG. 14C.
  • the method described in the embodiments shown in FIG. 3 to FIG. 7 , FIG. 13 , and FIG. 14A to FIG. 14C may be omitted.
  • connection medium between the communication interface 1210, the processor 1220, and the memory 1230 is not limited in the embodiment of the present application.
  • the memory 1230, the processor 1220, and the communication interface 1210 are connected by a bus 1240 in FIG. 12B.
  • the bus is indicated by a thick line in FIG. 12B, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus 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 12B, but it does not mean that there is only one bus or one type of bus.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that the computer Or performing a series of operational steps on other programmable devices to produce computer-implemented processing such that instructions executed on a computer or other programmable device are provided for implementing a block in a flow or a flow and/or block diagram of the flowchart Or the steps of the function specified in multiple boxes.

Landscapes

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

Abstract

一种会话管理方法及装置，从而实现了PDU会话由激活态转换为空闲态。该方法包括：第一设备接收激活PDU会话的请求消息；所述第一设备向第二设备发送所述PDU会话的定时器；所述第一设备接收所述第二设备发起的无效所述PDU会话的操作的第一消息；所述第一消息是所述第二设备检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时发出的。无效所述PDU会话的操作可以包括：将所述PDU会话由激活态转换为空闲态或者删除所述PDU会话。

Description

一种会话管理方法及装置
本申请要求在2017年1月9日提交中国专利局、申请号为PCT/CN2017/070684、发明名称为“一种会话管理方法及装置”’的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种会话管理方法及装置。
背景技术
在长期演进(英文：Long Term Evolution，简称：LTE)系统中，基于UE进行会话管理，会话中所有分组数据单元(Packet Data Unit，简称PDU)连接下的所有承载同时被激活或者被去激活。当执行S1释放流程后，用户设备(英文：User Equipment，简称：UE)与核心网之间的状态由连接态(ECM_Connected)转变为空闲态(ECM_IDLE)。在执行服务请求(Service request)流程后，所有的承载被激活，从而UE与核心网之间由空闲态转换为连接态(也可以称为激活态)。
在第五代移动通信技术(5G)系统中，基于PDU会话流(Session)进行会话管理。在UE触发多个PDU session时，每个PDU session分别有独立的状态(激活态Session_ACTIVE或者空闲态Session_IDLE)。在进行上下行数据传输时，UE发送的Service request消息中携带有数据传输所需求的PDU Session ID，从而在激活时，仅针对该PDU Session ID对应的PDU Session进行激活，从而该PDU Session ID对应的PDU Session由空闲态转换为激活态。
但现有技术中仅描述有PDU Session由空闲态转换为激活态，并没有实现PDU Session由激活态转换为空闲态的实现方式。
发明内容
本申请实施例提供了一种会话管理方法及装置，从而实现了PDU会话由激活态转换为空闲态。
第一方面，本申请实施例提供了一种会话管理方法，包括：
第一设备接收激活分组数据单元PDU会话的请求消息；所述第一设备向第二设备发送所述PDU会话的定时器；所述第一设备接收所述第二设备发起的无效所述PDU会话的操作的第一消息；所述第一消息是所述第二设备检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时发出的。无效所述PDU会话的操作可以包括：将所述PDU会话由激活态转换为空闲态或者删除所述PDU会话。
其中，所述第一消息中可以携带所述PDU会话的标识。
其中，所述第一设备为第一核心网设备，所述第二设备为第二核心网设备、或者为基站、或者为终端。第一核心网设备可以核心网侧的控制面网元，比如SMF。第二核心网设备可以是核心网侧的用户面网元，比如UPF。
需要说明的是，PDU会话的激活可以是建立PDU会话时激活，或者PDU会话由空闲态转换为激活态，或者执行小区切换时的PDU会话的激活。
通过上述方案，在PDU会话激活时，由第一设备向第二设备发送一个定时器，从而第二设备在检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时发出用于无效所述PDU会话的操作的消息。基于此，来提供一种触发将无数据传输的PDU会话删除或者转化为空闲态，从而避免了无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，所述第一设备向所述第二设备发送所述定时器之前，所述第一设备获取所述PDU会话对应的定时器，具体的可以通过如下方式中的一种来获取：
第一种实现方式：
所述第一设备基于所述PDU会话所属的网络切片的切片信息确定所述PDU会话的定时器。
第二种实现方式：
所述第一设备接收由第三核心网设备发送的所述PDU会话的定时器。
第三种实现方式：
所述第一设备基于数据网络名称(英文：Data Network name，简称：DNN)或者接入点名称(英文：Access Point Name，简称：APN)确定所述PDU会话的定时器。
在一种可能的设计中，所述方法还包括：
所述第一设备向所述第二设备发送指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
其中，第一设备可以将所述指示信息与定时器一起发送给第二设备，当然还可以分开发送，本申请实施例对此不作具体限定。
在一种可能的设计中，所述指示信息可以是由第三核心网设备发送来的。具体的，所述第一设备接收所述请求消息后，接收由第三核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
在一种可能的设计中，所述第一设备可以不向第二设备发送所述指示信息，从而所述第一设备接收到所述第一消息后，基于所述指示信息确定所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态或者为删除所述PDU会话。
在一种可能的设计中，所述第一消息中可以携带所述PDU会话的标识。
基于此，所述第一消息还可以携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
在上述设计中，将原因值携带在第一消息中，从而让第一设备在第一消息时，能够知道是由于什么原因第二设备要触发第一消息，基于此来确定接下来执行的操作。
在一种可能的设计中，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述方法还包括：
所述第一设备接收到所述第一消息后，向所述第二核心网设备发送用于指示删除所述PDN会话对应的与基站相关的信息的消息。从而在第二核心网设备接收到所述用于指示删除所述PDN会话对应的与基站相关的信息的消息后，执行删除所述PDN会话对应的与基站相关的信息的操作。
在一种可能的设计中，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述方法还包括：
所述第一设备接收到所述第一消息后，将所述PDU会话的状态设置为空闲态。
通过上述设计，所述第一设备保存所述PDU会话的状态，从而后续执行与终端上PDU 会话的状态同步。
在一种可能的设计中，所述无效所述PDU会话的操作为删除所述PDU会话，所述方法还包括：
所述第一设备接收到所述第一消息后，向所述第二核心网设备发送用于指示删除与所述PDN会话相关的信息的消息。从而在第二核心网设备接收到用于指示删除与所述PDN会话相关的信息的消息后，删除自身保存的所有与PDU会话相关的信息。
在一种可能的设计中，所述无效所述PDU会话的操作为删除所述PDU会话，所述方法还包括：
所述第一设备接收到所述第一消息后，向终端发送用于指示所述终端删除与所述PDN会话相关的信息的消息。从而终端在接收到所述用于指示所述终端删除与所述PDN会话相关的信息的消息后，删除自身保存的所有与PDU会话相关的信息。
在一种可能的设计中，所述第一设备接收到所述第一消息后，向基站发送用于指示基站将所述PDU会话的上下文释放的消息。从而在基站接收到所述指示基站将所述PDU会话的上下文释放的消息后，删除或者挂起所述PDU会话对应的无线资源。
在一种可能的设计中，所述方法还可以包括：
所述第一设备接收到所述第一消息后，向第四核心网设备发送用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态的消息。从而所述第四核心网设备在接收到用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态的消息后，执行将自身保存的所述PDU会话的状态设置为空闲态。在第四核心网设备后续执行与所述PDU会话相关的操作时，基于PDU会话的状态来执行。
在一种可能的设计中，第一核心网设备接收到第四核心网设备发送的第二消息，所述第二消息携带待更新用户面上下文的PDU会话的标识；
所述第一设备在接收到所述第二消息后，更新所述PDU会话的标识对应的所述PDU会话的用户面上下文。通过上述设计，在进行小区切换之前时，第一核心网设备接收到第四核心网设备发送的第二消息后，来更新所述PDU会话的标识对应的所述PDU会话的用户面上下文。
第二方面，本申请实施例还提供了一种会话管理方法，包括：
在分组数据单元PDU会话激活时，基站接收第一核心网设备发送的所述PDU会话的定时器；所述基站检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
通过上述设计，由第一核心网设备在PDU会话激活时，将定时器下发给基站，从而基站在对PDU会话进行监控时，监控到所述PDU会话上无数据传输，且持续到所述定时器超时时触发发送第一消息给第一核心网设备，从而第一核心网设备在接收到所述第一消息后，执行无效所述PDU会话的操作。基于此，来提供一种触发将无数据传输的PDU会话无效，从而避免了无数据传输的PDU会话占用资源导致的资源浪费。
其中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述方法还可以包括：
在PDU会话激活时，所述基站接收到所述第一核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
通过上述设计，提供一种由第一核心网设备来指示基站检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时，来触发第一核心网设备所需执行的操作。当然第一核心网设备还可以不将指示信息发送给基站，从而第一核心网设备接收到基站发送的第一消息后，由自身确定所需触发的操作。
在一种可能的设计中，所述第一消息可以携带所述PDU会话的标识。
另外，所述第一消息中还可以携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
在一种可能的设计中，基站在向第一核心网设备发送第一消息后，第一核心网设备会触发基站将所述PDU会话的上下文释放，具体的，所述基站接收到所述第一核心网设备发送的用于指示所述基站将所述PDU的上下文释放的消息；所述基站将所述PDU会话对应的无线资源删除或者挂起。
在一种可能的设计中，所述基站接收到所述第一核心网设备发送的用于指示所述基站将所述PDU的上下文释放的消息后，所述基站将保存的所述PDU会话的状态设置为空闲态。
通过上述设计，基站保存PDU会话的状态，从而后续可以基于PDU会话的状态，来执行针对该PDU会话的操作。
在一种可能的设计，所述方法还可以包括：
所述基站在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，删除所述PDU会话对应的服务质量QoS流与无线资源承载DRB之间的映射关系。
可选地，基站可以在接收到第一核心网设备发送的第一消息时，删除所述PDU会话对应的服务质量QoS流与无线资源承载DRB之间的映射关系。还可以在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，向第一核心网设备发送给第一消息之前，删除所述PDU会话对应的服务质量QoS流与无线资源承载DRB之间的映射关系。
在一种可能的设计中，所述方法还可以包括：
所述基站在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，向所述终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。
可选地，基站可以在将所述PDU会话对应的无线资源删除或者挂起后，向所述终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。基站还可以在将所述PDU会话对应的无线资源删除或者挂起之前，向终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。基站还可以在接收到第一核心网设备发送的第一消息后，向终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。针对基站执行的先后顺序，本申请对此不作具体限定。
在一种可能的设计中，所述用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息中携带：待删除或者挂起的无线资源承载DRB的标识。
第三方面，本申请实施例提供了一种会话管理方法，包括：
终端接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息；所述终端删除或者挂起所述PDU会话对应的无线资源，并将所述PDU会话的状态设置为空闲态。
通过上述设计，终端在接收到基站发送的消息后，执行删除或者挂起所述PDU会话对应的无线资源，并将所述PDU会话的状态设置为空闲态。从而保证终端与基站的DPU 会话的状态同步。其中，基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息，是在监控到在所述PDU会话上无数据传输且持续到PDU会话对应的定时器超时时，触发执行无效所述PDU会话的操作的流程中触发的。另外触发可以是所述基站，还可以是第二核心网设备，还可以是所述终端。另外，将一段时间内无数据传输的PDU会话无效，从而避免了无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，将所述PDU会话的状态设置为空闲态之前，所述方法还包括：
判断所述PDU会话对应的全部无线资源被删除或者挂起。通过上述一种方式，是在所述PDU会话的全部无线资源被删除或者挂起后，触发将所述PDU会话的状态设置为空闲态，从而能够后续针对PDU会话执行操作时，基于保存到所述PDU的状态来执行。
在一种可能的设计中，在所述终端接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息之前，所述方法还包括：
在所述PDU会话激活时，终端接收第一核心网设备发送的所述PDU会话的定时器；
所述终端监控到在所述PDU会话上无数据传输，且持续到所述定时器超时时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
上述提供了一种终端触发执行无效所述PDU会话的方法，从而终端在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时时，来触发执行无效所述PDU会话的操作，避免了持续无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述方法还可以包括：
在所述PDU会话激活时，所述终端接收所述第一核心网设备发送的第一指示信息，所述第一指示信息为用于指示所述无效所述PDU会话的操作的信息。
第四方面，本申请实施例提供了一种会话管理方法，包括：
第二核心网设备接收到第一核心网设备发送的消息，所述消息携带待删除的PDU会话的标识，用于指示所述第二核心网设备删除所述标识对应的PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息；
所述第二核心网设备删除所述PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息。
通过上述设计，第二核心网设备在接收到基站发送的消息后，执行PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息。其中，第一核心网设备发送的消息，是在监控到在所述PDU会话上无数据传输且持续到PDU会话对应的定时器超时时，触发执行无效所述PDU会话的操作的流程中触发的。另外监控触发可以是基站，还可以是所述第二核心网设备，还可以是所述终端。另外，将一段时间内无数据传输的PDU会话无效，从而避免了无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，所述方法还可以包括：
在所述PDU会话激活时，第二核心网设备接收第一核心网设备发送的所述PDU会话的定时器；
所述第二核心网设备监控到在所述PDU会话上无数据传输，且持续到所述定时器超时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
上述设计提供了一种由第二核心网设备触发执行无效所述PDU会话的方法，从而第 二核心网设备在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时时，来触发执行无效所述PDU会话的操作，避免了持续无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述方法还可以包括：
在PDU会话激活时，所述第二核心网设备接收到所述第一核心网设备发送的指示信息，所述指示信息为指示所述无效所述PDU会话的操作的信息。
第五方面，本申请实施例还提供了一种小区切换过程中的会话管理方法，包括：
在小区切换过程中，第四核心网设备接收基站发送的PDU会话的标识；
所述第四核心网设备基于所述PDU会话的标识确定需要更新用户面上下文的PDU会话；
所述第四核心网设备向第一核心网设备发送用于通知所述第一核心网设备更新所述PDU会话的用户面上下文的消息。
通过上述设计，在小区切换过程中，确定需要更新用户上下文的PDU会话，从而通知第一核心网设备更新这些PDU会话的用户面上下文。另外，需要更新用户上下文的PDU会话是为激活态的PDU会话，从而保证了针对激活态的PDU会话更新，避免了现有小区切换中，针对终端的所有的PDU会话均更新造成的资源浪费。
在一种可能的设计中，所述方法还包括：
所述第四核心网设备接收到第一核心网设备发送的，且用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态或者删除所述PDU会话的消息；
所述第四核心网设备将保存的所述PDU会话的状态设置为空闲态，或者删除所述PDU会话的状态信息。
通过上述设计，在无效所述PDU会话的流程中，将保存的所述PDU会话的状态设置为空闲态，或者删除所述PDU会话的状态信息，在后续针对所述PDU会话的执行操作时，可以基于所述PDU会话的状态来执行。
第六方面，本申请实施例提供了一种会话管理方法，用于PDU会话的同步。所述方法包括：
终端确定有上行数据到达或者接收到寻呼请求；所述终端向网络设备发送请求消息，所述请求消息中携带有PDU会话的标识，和/或携带PDU会话对应的QoS流的第一状态信息，所述第一状态信息指示所述QoS流在所述终端上的状态为激活态或者非激活态，用于所述网络设备与所述终端同步所述QoS流的状态。
通过上述设计，终端在确定有上行数据到达或者接收到寻呼请求时，向网络设备发送待同步的PDU会话对应的QoS流的状态，用于所述网络设备与所述终端同步所述QoS流的状态。
在一种可能的设计中，所述终端的无线资源控制RRC状态为RRC非激活连接状态，所述网络设备为基站，所述请求消息用于指示恢复所述终端的RRC连接。所述方法还可以包括：
所述终端接收所述基站发送的所述PDU会话对应的QoS流的第二状态信息，所述第二状态信息指示所述QoS流在所述基站上的状态为激活态或者非激活态；
所述终端基于所述第二状态信息与所述基站同步所述PDU会话对应的QoS流的状态。
通过上述设计，基站在执行激活PDU会话的QoS流后，将激活后的PDU会话的状态信息发送给终端，从而使得终端与基站同步所述PDU会话的QoS流的状态。
在一种可能的设计中，所述终端向基站发送请求消息后，所述终端接收所述基站发送的所述PDU会话对应的QoS流与DRB的映射关系；
所述终端保存所述映射关系。
在一种可能的设计中，所述终端的连接管理CM状态为空闲状态，所述网络设备为第四核心网设备，所述请求消息用于指示将所述终端从CM空闲状态转换为CM连接状态。所述方法还可以包括：
所述终端接收由所述第一核心网设备发送的所述PDU会话对应的QoS流的第三状态信息，所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态；
所述终端基于所述第三流状态信息与所述第一核心网设备同步所述PDU会话对应的QoS流的状态。
通过上述设计，在网络设备为第四核心网设备时，终端接收第一核心网设备发送的PDU会话对应的QoS流对应第三状态信息，从而终端与第一核心网设备来同步QoS流的状态，避免状态不同步导致数据传输错误。
第七方面，本申请实施例提供了一种会话管理方法，包括：
基站接收所述终端发送的RRC连接恢复消息，所述RRC连接恢复消息中携带参数；
所述基站根据所述参数确定待激活的PDU会话；
所述基站触发激活所述PDU会话的流程。
通过上述设计，基站在接收到RRC连接恢复消息后，确定需要激活的PDU会话，从而仅针对需要的PDU会话进行激活操作，避免了现有中针对终端所有PDU会话均执行激活操作带来的资源浪费。
在一种可能的设计中，所述参数为所述待激活的PDU会话的标识，或者所述待激活的PDU会话对应的无线资源承载DRB的标识。
基站中包括PDU会话与无线资源承载之间的对应关系，从而基站根据对应关系来确定待激活的PDU会话。
其中，所述待激活的PDU会话的状态为空闲态。
在一种可能的设计中，所述RRC连接恢复消息中还携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述状态信息用于所述基站与所述终端同步所述QoS流的状态。
其中，激活PDU会话也就是激活PDU会话对应的QoS流。
在一种可能的设计中，所述基站触发执行激活所述PDU会话的流程，包括：
所述基站向第一核心网设备发送用于触发将所述PDU会话转换为激活态的消息。
通过上述设计，提供一种通过发送用于触发将所述PDU会话转换为激活态的消息来触发执行激活所述PDU会话的流程，简单有效。
在一种可能的设计中，所述方法还可以包括：
所述基站配置所述PDU会话对应的QoS流与DRB之间的映射关系。
通过上述设计，所述基站触发执行激活所述PDU会话的流程后，即需要激活PDU会 话，从而基站为该会话配置所述PDU会话对应的QoS流与DRB之间的映射关系。
在一种可能的设计中，所述方法还可以包括：
所述基站将所述映射关系发送给所述终端。从而使得终端接收到所述映射关系，基于映射关系，执行所述PDU会话对应的操作。
在一种可能的设计中，所述方法还可以包括：
所述基站将所述PDU会话对应的QoS流的第二状态信息发送给终端，以指示所述终端与基站同步所述QoS的状态。
上述设计了一种终端与基站同步QoS状态的方式。
在一种可能的设计中，所述方法还可以包括：
基站确定针对终端执行小区切换；
所述基站向第四核心网设备发送切换请求消息，所述切换请求消息中携带所述终端对应的状态为激活态的PDU会话的标识或者所述切换请求中携带所述终端对应的且在所述基站保存有PDU会话上下文的PDU会话的标识。
通过上述设计，在执行小区切换时，基站向第四核心网设备发送切换请求，并将状态为激活态的PDU会话的标识携带在请求中，从而使得第四核心网设备指示PDU会话对应的SMF更新激活态的PDU会话对应的用户面上下文。
第八方面，本申请实施例提供了一种会话管理方法，包括：
第一核心网设备接收终端发送的服务请求消息，所述服务请求消息中携带待激活的PDU会话的标识；
所述第一核心网设备基于所述服务请求消息执行激活所述PDU会话的流程。
通过上述设计，终端将需要激活的PDU会话的标识发送给第一核心网设备，第一核心网设备仅针对需要激活的PDU会话，不需要激活终端的所有的PDU会话，从而减少了资源的占用。
在一种可能的设计中，所述服务请求消息中携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述第一状态信息指示所述PDU会话对应的QoS流在所述终端上的状态为激活态或者非激活态，用于所述第一核心网设备与所述终端同步所述QoS流的状态。
上述设计中，第一核心网设备将PDU会话对应的QoS流的状态发给终端，从而终端与第一核心网设备来同步QoS流的状态，避免状态不同步导致的数据传输错误。
在一种可能的设计中，所述方法还可以包括：
所述第一核心网设备向所述终端发送的所述PDU会话对应的QoS流的第三状态信息，以指示所述终端与所述第一核心网设备同步所述PDU会话对应的QoS流的状态；所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态。
上述设计中，终端将PDU会话对应的QoS流的状态发给第一核心网设备，从而第一核心网设备与终端来同步QoS流的状态，避免状态不同步导致的数据传输错误。
基于与方法实施例同样的发明构思，本申请实施例还提供了一种会话管理装置，其中方法与装置部分的有益效果相互参见，本申请在此不再赘述。
第九方面，本申请实施例提供了一种会话管理装置，所述装置应用于第一设备，包括：
接收模块，用于接收激活分组数据单元PDU会话的请求消息；
发送模块，用于向第二设备发送所述PDU会话的定时器；
所述接收模块，还用于接收所述第二设备发起的无效所述PDU会话的操作的第一消息；所述第一消息是所述第二设备检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时发出的。
在一种可能的设计中，所述第一设备为第一核心网设备，所述第二设备为第二核心网设备、或者为基站、或者为终端。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，还包括：
第一确定模块，用于在所述发送模块向所述第二设备发送所述定时器之前，基于所述PDU会话所属的网络切片的切片信息确定所述PDU会话的定时器。
在一种可能的设计中，所述接收模块，还用于接收由第三核心网设备发送的所述PDU会话的定时器。
在一种可能的设计中，所述发送模块，还用于向所述第二设备发送指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
在一种可能的设计中，所述接收模块，还用于在接收所述请求消息后，接收由第三核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
在一种可能的设计中，第二确定模块，用于在所述接收模块接收到所述第一消息后，基于所述指示信息确定所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态或者为删除所述PDU会话。
在一种可能的设计中，所述第一消息中携带所述PDU会话的标识。
在一种可能的设计中，所述第一消息还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
在一种可能的设计中，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述接收模块，还用于在接收到所述第一消息后，向所述第二核心网设备发送用于指示删除所述PDN会话对应的与基站相关的信息的消息。
在一种可能的设计中，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述装置还包括：
处理模块，用于在接收到所述第一消息后，将所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述无效所述PDU会话的操作为删除所述PDU会话，所述发送模块，还用于在所述接收模块接收到所述第一消息后，向所述第二核心网设备发送用于指示删除与所述PDN会话相关的信息的消息。
在一种可能的设计中，所述无效所述PDU会话的操作为删除所述PDU会话，所述发送模块，还用于在接收到所述第一消息后，向终端发送用于指示所述终端删除与所述PDN会话相关的信息的消息。
在一种可能的设计中，所述发送模块，还用于在所述接收模块接收到所述第一消息后，向基站发送用于指示基站将所述PDU会话的上下文释放的消息。
在一种可能的设计中，所述发送模块，还用于在所述接收模块接收到所述第一消息后，向第四核心网设备发送用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态的消息。
在一种可能的设计中，所述接收模块，还用于接收到第四核心网设备发送的第二消息，所述第二消息携带待更新用户面上下文的PDU会话的标识；
所述装置还包括：
更新模块，用于更新所述PDU会话的标识对应的所述PDU会话的用户面上下文。
第十方面，本申请实施例提供了一种会话管理装置，所述装置应用于基站，包括：
接收模块，用于在分组数据单元PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
处理模块，用于检测到在所述PDU会话上无数据传输，且持续到所述定时器超时；
所述发送模块，用于向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述接收模块，还用于在PDU会话激活时，接收到所述第一核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
在一种可能的设计中，所述第一消息携带所述PDU会话的标识。
在一种可能的设计中，所述第一消息中还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
在一种可能的设计中，所述接收模块，还用于接收到所述第一核心网设备发送的用于指示所述基站将所述PDU的上下文释放的消息；
所述处理模块，还用于将所述PDU会话对应的无线资源删除或者挂起。
在一种可能的设计中，所述处理模块，还用于：
将保存的所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述处理模块，还用于在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，删除所述PDU会话对应的服务质量QoS流与无线资源承载DRB之间的映射关系。
在一种可能的设计中，所述发送模块，还用于在所述处理模块监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，向所述终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。
在一种可能的设计中，所述用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息中携带：待删除或者挂起的无线资源承载DRB的标识。
第十一方面，本申请实施例提供了一种会话管理装置，所述装置应用于终端，包括：
接收模块，用于接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息；
处理模块，用于删除或者挂起所述PDU会话对应的无线资源，并将所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述处理模块，还用于在所述接收模块接收到所述基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息后，判断所述PDU会话对应的全部无线资源被删除或者挂起时，将所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述接收模块，还用于在接收基站发送的用于指示所述终端删 除或者挂起PDU会话对应的无线资源的消息之前，在所述PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
所述装置还包括：
发送模块，还用于在所述处理模块监控到在所述PDU会话上无数据传输，且持续到所述定时器超时时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述接收模块，还用于在所述PDU会话激活时，接收所述第一核心网设备发送的第一指示信息，所述第一指示信息为用于指示所述无效所述PDU会话的操作的信息。
第十二方面，本申请实施例提供了一种会话管理装置，所述装置应用于第二核心网设备，包括：
接收模块，用于接收到第一核心网设备发送的消息，所述消息携带待删除的PDU会话的标识，用于指示所述第二核心网设备删除所述标识对应的PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息；
处理模块，用于删除所述PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息。
在一种可能的设计中，所述接收模块，还用于在所述PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
所述装置还包括：
发送模块，用于在所述处理模块监控到在所述PDU会话上无数据传输，且持续到所述定时器超时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述接收模块，还用于在PDU会话激活时，接收到所述第一核心网设备发送的指示信息，所述指示信息为指示所述无效所述PDU会话的操作的信息。
第十三方面，本申请实施例提供了一种会话管理装置，所述装置应用于第四核心网设备，包括：
接收模块，用于在小区切换过程中，接收基站发送的PDU会话的标识；
处理模块，用于基于所述PDU会话的标识确定需要更新用户面上下文的PDU会话；
发送模块，用于向第一核心网设备发送用于通知所述第一核心网设备更新所述PDU会话的用户面上下文的消息。
在一种可能的设计中，所述接收模块还用于：
接收到第一核心网设备发送的，且用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态或者删除所述PDU会话的消息；
所述处理模块，还用于将保存的所述PDU会话的状态设置为空闲态，或者删除所述PDU会话的状态信息。
第十四方面，本申请实施例提供了一种会话管理方法，所述装置应用于终端，包括：
处理模块，用于确定有上行数据到达或者接收到寻呼请求；
发送模块，用于向网络设备发送请求消息，所述请求消息中携带有PDU会话的标识， 和/或携带PDU会话对应的QoS流的第一状态信息，所述第一状态信息指示所述QoS流在所述终端上的状态为激活态或者非激活态，用于所述网络设备与所述终端同步所述QoS流的状态。
在一种可能的设计中，所述终端的无线资源控制RRC状态为RRC非激活连接状态，所述网络设备为基站，所述请求消息用于指示恢复所述终端的RRC连接。
在一种可能的设计中，所述接收模块，还用于接收所述基站发送的所述PDU会话对应的QoS流的第二状态信息，所述第二状态信息指示所述QoS流在所述基站上的状态为激活态或者非激活态；
所述处理模块，还用于基于所述第二状态信息与所述基站同步所述PDU会话对应的QoS流的状态。
在一种可能的设计中，所述接收模块，还用于接收所述基站发送的所述PDU会话对应的QoS流与DRB的映射关系；
所述处理模块，还用于保存所述映射关系。
在一种可能的设计中，所述终端的连接管理CM状态为空闲状态，所述网络设备为第四核心网设备，所述请求消息用于指示将所述终端从CM空闲状态转换为CM连接状态。
在一种可能的设计中，所述接收模块，还用于接收由所述第一核心网设备发送的所述PDU会话对应的QoS流的第三状态信息，所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态；
所述处理模块，还用于基于所述第三流状态信息与所述第一核心网设备同步所述PDU会话对应的QoS流的状态。
第十五方面，本申请实施例提供了一种会话管理装置，所述装置应用于基站，包括：
接收模块，用于接收所述终端发送的RRC连接恢复消息，所述RRC连接恢复消息中携带参数；
处理模块，用于根据所述参数确定待激活的PDU会话；并触发激活所述PDU会话的流程。
在一种可能的设计中，所述参数为所述待激活的PDU会话的标识，或者所述待激活的PDU会话对应的无线资源承载DRB的标识。
在一种可能的设计中，所述待激活的PDU会话的状态为空闲态。
在一种可能的设计中，所述RRC连接恢复消息中还携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述状态信息用于所述基站与所述终端同步所述QoS流的状态。
在一种可能的设计中，所述装置还包括：
发送模块，用于向第一核心网设备发送用于触发将所述PDU会话转换为激活态的消息。
在一种可能的设计中，所述处理模块，还用于配置所述PDU会话对应的QoS流与DRB之间的映射关系。
在一种可能的设计中，还包括：
发送模块，还用于将所述映射关系发送给所述终端。
在一种可能的设计中，所述装置还包括：
发送模块，用于将所述PDU会话对应的QoS流的第二状态信息发送给终端，以指示 所述终端与基站同步所述QoS的状态。
在一种可能的设计中，所述处理模块，还用于确定针对终端执行小区切换；
发送模块，用于向第四核心网设备发送切换请求消息，所述切换请求消息中携带所述终端对应的状态为激活态的PDU会话的标识或者所述切换请求中携带所述终端对应的且在所述基站保存有PDU会话上下文的PDU会话的标识。
第十六方面，本申请实施例提供了一种会话管理装置，所述装置应用于第一核心网设备，包括：
接收模块，用于接收终端发送的服务请求消息，所述服务请求消息中携带待激活的PDU会话的标识；
处理模块，用于基于所述服务请求消息执行激活所述PDU会话的流程。
在一种可能的设计中，所述服务请求消息中携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述第一状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态，用于所述第一核心网设备与所述终端同步所述QoS流的状态。
在一种可能的设计中，所述装置还包括：
发送模块，用于向所述终端发送的所述PDU会话对应的QoS流的第三状态信息，以指示所述终端与所述第一核心网设备同步所述PDU会话对应的QoS流的状态；所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态。
第十七方面，本申请实施例还提供了一种第一核心网设备，该第一核心网设备包括通信接口、处理器以及存储器，所述通信接口用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第一方面或上述第一方面的任意一种设计提供的方法，或者用于实现第八方面或者第八方面的任意一种设计所提供的方法。
第十八方面，本申请实施例还提供了一种第二核心网设备，该第二核心网设备包括通信接口、处理器以及存储器，所述通信接口用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第四方面或上述第四方面的任意一种设计提供的方法。
第十九方面，本申请实施例提供了一种第四核心网设备，该第四核心网设备包括通信接口、处理器以及存储器，所述通信接口用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第五方面或上述第五方面的任意一种设计提供的方法。
第二十方面，本申请实施例提供了一种终端，所述终端包括收发器，处理器以及存储器，所述收发器用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第三方面或上述第三方面的任意一种设计提供的方法，或者用于实现第六方面或上述第六方面的任意一种设计提供的方法。
第二十一方面，本申请实施例提供了一种基站，所述基站包括收发器，处理器以及存储器，所述收发器用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第二方面或上述第二方面的任意一种设计提供的方法，或者用于实现第七方面或上述第七方面的任意一种设计提供的方法。
第二十二方面，本申请实施例中还提供一种计算机存储介质，该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现第一方面至第八方面任意一方面或上述第一方面至第八方面的任意一种设计提供的方法。
第二十三方面，本申请实施例还提供了一种会话管理方法，包括：
在终端的PDU会话建立或者激活时，所述终端当前接入的源基站接收第一核心网设备发送的所述PDU会话的定时器；若所述源基站检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态；
所述源基站在确定针对所述终端执行从所述源基站切换到目标基站时，确定所述终端的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
通过上述设计，源基站监控终端的PDU会话的定时器，针对定时器超时的PDU不执行切换流程，仅针对定时器未超时的PDU会话执行切换，从而避免了无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，所述源基站针对第二类PDU会话执行切换流程，包括：
所述源基站向所述目标基站发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
上述提供了一种基于XN的切换方式。
在一种可能的设计中，所述方法还包括：
在针对第二类PDU会话执行切换的过程中，所述源基站向所述终端发送用于指示所述终端执行无效所述第一类PDU会话的操作的消息。
在一种可能的设计中，所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述第一类PDU会话的标识；或者，
所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标识所述终端的激活的PDU会话中的第一类PDU会话。
在一种可能的设计中，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，所述源基站针对第二类PDU会话执行切换流程，包括：
所述源基站向第四核心网设备发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
第二十四方面，本申请实施例提供了一种会话管理方法，包括：
终端待切入的目标基站接收所述终端当前接入的源基站发送的切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话的标识中的第一类PDU会话；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；所述第二类PDU会话为所述终端的激活的PDU会话中除标记为活动状态的PDU会话以外的PDU会话；
所述目标基站向第四核心网设备发送用于指示所述第四核心网设备执行无效所述第第一类PDU会话的操作的消息。
通过上述设计，源基站监控终端的PDU会话的定时器，针对定时器超时的PDU不执行切换流程，仅针对定时器未超时的PDU会话执行切换，从而避免了无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，所述用于指示所述第四核心网设备执行无效所述第二类PDU会话的操作的消息中携带：所述第一类PDU会话的标识。
在一种可能的设计中，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
第二十五方面，本申请实施例提供了一种会话管理方法，包括：
在终端从源基站切换到目标基站的过程中，第四核心网设备接收源基站或者目标基站发送的第二类PDU会话的标识；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第二类PDU会话为所述终端的激活的PDU会话中除记录为不活动状态的PDU会话以外的PDU会话，记录为不活动状态的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
所述第四核心网设备向第一核心网设备发送用于通知所述第一核心网设备更新所述第二类PDU会话的上下文的消息。
通过上述设计，第四核心网仅针对第二类PDU会话执行更新上下文，从而避免了无数据传输的PDU会话占用资源导致的资源浪费。
在一种可能的设计中，第四核心网设备接收目标基站发送的所述第二类PDU会话的标识，包括：
所述第四核心网设备接收所述目标基站发送的路径转换消息，所述路径转换消息携带所述第二类PDU会话的标识。
在一种可能的设计中，所述第四核心网设备接收源基站发送的第二类PDU会话的标识，包括：
所述第四核心网设备接收所述源基站发送的切换请求，所述切换请求中携带所述第二类PDU会话的标识。
在一种可能的设计中，所述方法还包括：
所述第四核心网设备基于所述第二类PDU会话的标识确定第一类PDU会话，所述第一类PDU会话为所述第四核心网设备保存的所述终端的激活的PDU会话中除所述标识对 应的第二类PDU会话以外的PDU会话；
所述第四核心网设备向所述第一核心网设备发送用于指示执行无效所述第一类PDU会话的操作的消息。
在一种可能的设计中，所述无效所述第一类PDU会话的操作，包括将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，所述第四核心网设备基于所述第一类PDU会话的标识确定第一类PDU会话后，所述方法还包括：
所述第四核心网设备将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，所述方法还包括：
所述第四核心网设备接收所述源基站或者所述目标基站发送的第三类PDU会话的标识，所述第三类PDU会话为所述记录为不活动状态的PDU会话；
所述第四核心网设备向所述第一核心网设备发送用于指示执行无效所述第三类PDU会话的操作的消息。
在一种可能的设计中，所述无效所述第三类PDU会话的操作，包括：
将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
在一种可能的设计中，所述第四核心网设备接收所述源基站或者所述目标基站发送的第三类PDU会话的标识后，所述方法还包括：
所述第四核心网设备将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
在一种可能的设计中，所述第四核心网设备接收所述源基站或者目标基站发送的第三类PDU会话的标识后，所述方法还包括：
所述第四核心网设备将所述第三类PDU会话的标识发送给所述终端，用于指示所述终端将所述第三类PDU会话的状态设置为空闲态。
第二十六方面，本申请实施例提供了一种会话管理方法，包括：
在终端从当前接入的源基站切换到目标基站的过程中，所述终端接收到所述源基站或者第四核心网设备发送的用于指示执行无效第一类分组数据单元PDU会话的操作的消息；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
所述终端基于所述消息执行无效所述第一类PDU会话的操作。
在一种可能的设计中，所述用于指示所述终端执行无效第一类分组数据单元PDU会话的操作的消息中携带：第一类PDU会话的标识。
在一种可能的设计中，所述用于指示执行无效第一类分组数据单元PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话；
所述终端基于所述消息执行无效所述第一类PDU会话的操作，包括：
所述终端根据所述第一指示确定所述终端的激活的PDU会话中的第一类PDU会话，并执行无效所述第一类PDU会话的操作。
在一种可能的设计中，，所述无效所述第一类PDU会话的操作，包括：
将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
第二十七方面，本申请实施例提供了一种会话管理装置，所述装置应用于源基站，包括：
接收模块，用于在终端的PDU会话建立或者激活时，接收第一核心网设备发送的所述PDU会话的定时器；若所述源基站检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态；
处理模块，用于在确定针对所述终端执行从所述源基站切换到目标基站时，确定所述终端的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
在一种可能的设计中，还包括：
发送模块，用于在所述处理模块针对第二类PDU会话向所述目标基站发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
在一种可能的设计中，还包括：
发送模块，用于在针对第二类PDU会话执行切换的过程中，向所述终端发送用于指示所述终端执行无效所述第一类PDU会话的操作的消息。
在一种可能的设计中，所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述第一类PDU会话的标识；或者，
所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标识所述终端的激活的PDU会话中的第一类PDU会话。
在一种可能的设计中，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，还包括：
所述发送模块，用于在所述处理模块针对第二类PDU会话执行切换流程时，向第四核心网设备发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
第二十八方面，本申请实施例提供了一种会话管理装置，所述装置应用目标基站，包括：
接收模块，接收终端当前接入的源基站发送的切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话的标识中的第一类 PDU会话；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；所述第二类PDU会话为所述终端的激活的PDU会话中除标记为活动状态的PDU会话以外的PDU会话；
发送模块，用于向第四核心网设备发送用于指示所述第四核心网设备执行无效所述第第一类PDU会话的操作的消息。
在一种可能的设计中，所述用于指示所述第四核心网设备执行无效所述第二类PDU会话的操作的消息中携带：所述第一类PDU会话的标识。
在一种可能的设计中，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
第二十九方面，本申请实施例提供了一种会话管理装置，所述装置应用于第四核心网设备，包括：
接收模块，用于在终端从源基站切换到目标基站的过程中，接收源基站或者目标基站发送的第二类PDU会话的标识；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第二类PDU会话为所述终端的激活的PDU会话中除记录为不活动状态的PDU会话以外的PDU会话，记录为不活动状态的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
发送模块，用于向第一核心网设备发送用于通知所述第一核心网设备更新所述第二类PDU会话的上下文的消息。
在一种可能的设计中，所述接收模块，具体用于接收所述目标基站发送的路径转换消息，所述路径转换消息携带所述第二类PDU会话的标识。
在一种可能的设计中，所述接收模块，具体用于接收所述源基站发送的切换请求，所述切换请求中携带所述第二类PDU会话的标识。
在一种可能的设计中，所述装置还包括：
处理模块，用于基于所述第二类PDU会话的标识确定第一类PDU会话，所述第一类PDU会话为所述第四核心网设备保存的所述终端的激活的PDU会话中除所述标识对应的第二类PDU会话以外的PDU会话；
所述第四核心网设备向所述第一核心网设备发送用于指示执行无效所述第一类PDU会话的操作的消息。
在一种可能的设计中，所述无效所述第一类PDU会话的操作，包括将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，处理模块，还用于在基于所述第一类PDU会话的标识确定第一类PDU会话后，将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，所述接收模块，还用于接收所述源基站或者目标基站发送的第三类PDU会话的标识，所述第三类PDU会话为所述记录为不活动状态的PDU会话；
所述发送模块，用于向所述第一核心网设备发送用于指示执行无效所述第三类PDU会话的操作的消息。
在一种可能的设计中，所述无效所述第三类PDU会话的操作，包括：
将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
在一种可能的设计中，所述装置还包括：
处理模块，用于在所述接收模块接收所述源基站或者目标基站发送的第三类PDU会话的标识后，将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
在一种可能的设计中，所述发送模块，还用于：在所述接收模块接收所述源基站或者目标基站发送的第三类PDU会话的标识后，将所述第三类PDU会话的标识发送给所述终端，用于指示所述终端将所述第三类PDU会话的状态设置为空闲态。
第三十方面，本申请实施例提供了一种会话管理装置，所述装置应用于终端，包括：
接收模块，用于在终端从当前接入的源基站切换到目标基站的过程中，接收到所述源基站或者第四核心网设备发送的用于指示执行无效第一类分组数据单元PDU会话的操作的消息；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
处理模块，用于基于所述消息执行无效所述第一类PDU会话的操作。
在一种可能的设计中，所述用于指示所述终端执行无效第一类分组数据单元PDU会话的操作的消息中携带：第一类PDU会话的标识。
在一种可能的设计中，所述用于指示执行无效第一类分组数据单元PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话；
所述终端基于所述消息执行无效所述第一类PDU会话的操作，包括：
所述终端根据所述第一指示确定所述终端的激活的PDU会话中的第一类PDU会话，并执行无效所述第一类PDU会话的操作。
在一种可能的设计中，所述无效所述第一类PDU会话的操作，包括：
将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
第三十一方面，本申请实施例还提供了一种第四核心网设备，该第四核心网设备包括通信接口、处理器以及存储器，所述通信接口用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第二十五方面或上述第二十五方面的任意一种设计提供的方法。
第三十二方面，本申请实施例提供了一种终端，所述终端包括收发器，处理器以及存储器，所述收发器用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第二十六方面或上述第二十六方面的任意一种设计提供的方法。
第三十三方面，本申请实施例提供了一种基站，所述基站包括收发器，处理器以及存储器，所述收发器用于收发数据，所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序并实现第二十三方面或上述第二十三方面的任意一种设计提供的方法，或者用于实现第二十四方面或上述第二十四方面的任意一种设计提供的方法。
附图说明
图1A为本申请实施例提供的一种系统架构示意图；
图1B为本申请实施例提供的另一种系统架构示意图；
图2为本申请实施例提供的一种状态示意图；
图3为本申请实施例提供的会话管理方法示意图；
图4A为本申请实施例提供的一种定时器配置方法示意图；
图4B为本申请实施例提供的另一种定时器配置方法示意图；
图4C为本申请实施例提供的又一种定时器配置方法示意图；
图5A为本申请实施例提供的一种定时器触发方法示意图；
图5B为本申请实施例提供的另一种定时器触发方法示意图；
图5C为本申请实施例提供的又一种定时器触发方法示意图；
图6A为本申请实施例提供的一种状态同步示意图；
图6B为本申请实施例提供的另一种状态同步示意图；
图7为本申请实施例提供的小区切换方法示意图；
图8A～图8C为本申请实施例提供的第一核心网设备示意图；
图9A～图9E为本申请实施例提供的基站示意图；
图10A～图10D为本申请实施例提供的终端示意图；
图11A～图11B为本申请实施例提供的第二核心网设备示意图；
图12A～图12C为本申请实施例提供的第四核心网设备示意图；
图13为本申请实施例提供的终端的基站切换中定时器触发方法示意图；
图14A至图14C为本申请实施例提供的终端的基站切换方法示意图。
具体实施方式
本申请实施例可以适用于4G(第四代移动通信系统)演进系统，如LTE(Long Term Evolution，长期演进)系统，或者还可以为5G(第五代移动通信系统)系统，如采用新型无线接入技术(new radio access technology，New RAT)的接入网；CRAN(Cloud Radio Access Network，云无线接入网)等通信系统。
图1A示例性示出了本申请实施例适用的一种系统架构示意图。应理解，本申请实施例并不限于图1所示的系统中，此外，图1A中的装置可以是硬件，也可以是从功能上划分的软件或者以上二者结合后的结构。如图1A所示，本申请实施例提供的系统架构包括终端、基站、第一核心网设备、第二核心网设备、第三核心网设备以及第四核心网设备。其中，终端可以通过基站与第一核心网设备、第二核心网设备以及第四核心网设备通信。第一核心网设备与第四核心网设备之间进行通信，另外第一核心网设备与第四核心网设备之间可以统称为控制面网元。第四核心网设备与第三核心网设备通过通信接口连接。
控制面网元(英文：Control Plane，简称：CP)可以包括是鉴权与移动性管理实体(英文：Authentication and Mobility Management Function，简称：AMF)、会话管理功能实体(英文：Session Management Function，简称：SMF)、以及SDN控制器、网关控制面(GW-C)、移动性管理实体(英文Mobility Management Entity，简称MME)或以上网元融合后形成的控制功能的全部或部分。控制面网元负责移动网络中的移动性管理、转发路径管理，如向转发面网关(GW-U)下发报文转发策略，指示GW-U根据报文转发策略进行报文处理 和转发。其中，AMF，负责UE鉴权与移动性管理，NAS消息路由，SMF选择等；SMF，负责会话管理，如会话创建，修改，删除。UPF选择，UE IP地址分配等。参见图1B所示的具体系统架构，第一核心网设备为SMF，以及第四核心网设备为AMF为例，另外本申请后续描述中均以第一核心网设备为SMF，第四核心网设备为AMF为例进行说明。
第二核心网设备具体可以是转发面网元(英文：User Plane Function，简称：UPF)，如图1B所示。UPF负责报文处理与转发。可以是分组数据网(英文：packet data network，简称：PDN)网关(英文：Gate Way，简称：GW)的转发面功能、服务网关(英文：Serving Gate Way，简称：S-GW)的转发面功能、路由器、交换机等物理或虚拟的转发设备。
第三核心网设备具体可以是策略控制功能实体(英文：Policy Rules Function，简称：PCF)或者为策略计费控制功能实体(英文：Policy and Charging Rules Function，简称：PCRF)。其中，PCF或者PCRF负责策略控制决策和基于流计费控制。第三核心网设备还可以是用户数据管理实体(英文：Subscriber Data Management，简称：SDM)，或者归属签约用户服务器(英文：Home Subscriber Server，简称：HSS)。用户数据管理实体英文还可以对应于User Data Management，简称还可以对应于UDM。SDM、UDM或者HSS用于帮助运营商实现对所有与用户相关的数据的统一管理。
基站还可以称为接入节点(英文：Access Node，简称：AN)，如图1B所示，为终端提供无线接入服务。接入节点具体可以是全球移动通信(英文：Global System for Mobile communication，简称：GSM)系统或码分多址(英文：Code Division Multiple Access，简称：CDMA)系统中的基站(英文：Base Transceiver Station，简称：BTS)，也可以是宽带码分多址(英文：Wideband Code Division Multiple Access，简称：WCDMA)系统中的基站(NodeB)，还可以是LTE系统中的演进型基站(英文：Evolutional Node B，简称：eNB或eNodeB)，或者是未来5G网络中的基站设备、小基站设备、无线访问节点(WiFi AP)、无线互通微波接入基站(英文：Worldwide Interoperability for Microwave Access Base Station，简称：WiMAX BS)等，本申请对此并不限定。
终端，也可称为接入终端、用户设备(英文：User Equipment，简称：UE)，用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置等。图1B中以UE为例进行说明。终端可以是蜂窝电话、无绳电话、会话启动协议(英文：Session Initiation Protocol，简称：SIP)电话、无线本地环路(英文：Wireless Local Loop，简称：WLL)站、个人数字处理(英文：Personal Digital Assistant，简称：PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、物联网终端设备，比如火灾检测传感器、智能水表/电表、工厂监控设备等等。
另外系统架构中还可以包括网络应用功能(英文：Application Function，简称：AF)、用户数据管理实体(英文：Subscriber Data Management，简称：SDM)以及数据网络(英文：Data Network，简称：DN)，如图1B所示。
数据网络(英文：Data Network，简称：DN)，为用户提供数据传输服务，可以是PDN网络，如因特网(Internet)、IP多媒体业务(英文：IP Multi-media Service，简称：IMS)等。
AF，主要对转发面行为进行动态策略/计费控制。这些业务需要动态策略和计费控制。AF传送PCF需要的动态会话信息，接收IP连接接入网(IP-CAN)的特定信息和IP-CAN承载层事件的确认。
需要说明的是，本申请中涉及的多个，是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。同时，应当理解，尽管在本申请实施例中可能采用术语第一、第二、第三等来描述各种消息、请求、设备以及核心网设备，但这些消息、请求、设备以及核心网设备不应限于这些术语。这些术语仅用来将消息、请求、设备以及核心网设备彼此区分开。
另外，本申请实施例中PDU会话涉及两种状态：空闲态以及激活态。其中，PDU会话的状态用于描述PDU会话在UE与UPF之间的用户面连接状况。具体名称可以为会话管理状态，也可以为会话连接状态，或者为其他可能的描述会话状态的名称，本发明中对PDU会话的状态的具体名称不做限定。PDU会话的状态保存在UE与SMF里，还可能同时保存在AMF、UPF中。
空闲态是指PDU会话在UE与UPF之间的用户面连接不存在，具体可能为以下操作中的一项或者多项的组合：
1、UPF删除或者挂起NG3接口中对应基站侧的信息(例如基站的IP地址，隧道标识，端口号等，使得下行数据到达UPF后UPF无法发送到基站)。
2、基站可能删除或者挂起PDU会话对应的无线资源(本发明中的无线资源可以是用于承载PDU会话对应数据的时频资源，也可以是无线资源配置DRB或者是这些情况的组合)以及删除或者挂起NG3接口。
3、UE根据基站的配置删除或者挂起对应的无线资源。
激活态是指PDU会话在UE与UPF之间的用户面连接存在，包括UE与基站之间的空口连接和基站与UPF之间的NG3接口的连接，处于激活态的会话有上下行数据到达时，可以直接在UE与UPF之间传输。
本申请实施例提供了一种会话管理方法及装置，针对每个PDU会话配置一个定时器，用于监控在PDU会话上无数据传输持续到定时器超时时触发执行无效该PDU会话的操作，其中无效PDU会话的操作可以是执行该PDU会话进入空闲态，还可以是删除该PDU会话，从而提供一种实现PDU Session的状态由激活态转换为空闲态的实现方式。
其中，PDU会话(Session)的状态保存在UE、基站(AN)以及核心网侧的SMF中，每个PDU会话具有各自不同的状态，不同的SMF管理不同的PDU会话，如图2所示，SMF A用于管理会话A和会话B，SMF B用于管理会话C。PDU会话的状态分为两种状态，空闲态(IDLE)以及激活态(ACTIVE)。
下面结合附图对本申请实施例作具体说明。
参见图3所示为本申请实施例提供的一种会话管理方法的流程示意图。
S301，SMF接收激活PDU会话的请求消息。
需要说明的是，激活PDU会话可以是建立该PDU会话，还可以是PDU会话由空闲态转换到激活态，或者可以是执行切换时创建PDU会话(具体可以是UE从非3GPP(non-3GPP)网络切换到3GPP网络时，从non-3GPP会话映射到3GPP会话时创建的PDU会话)。
S302，SMF向第二设备发送所述PDU会话的定时器(Timer)。
S303，第二设备接收到所述PDU会话的定时器后，在检测到所述PDU会话上无数据传输，且持续到所述定时器超时时，向第一核心网设备发送无效所述PDU会话的操作的 第一消息。
需要说明的是，定时器可以在PDU会话每次传输数据后在预定时间内无数据传输时开启，在定时器开启直到超时的这段时间内均无数据传输，则触发发送第一消息。定时器还可以在PDU会话每次传输数据后开启，然后在定时器开启直到超时的这段时间内均无数据传输，则触发发送第一消息。另外，在开启到超时的这段时间内，若在该PDU会话上发送数据，则重置定时器。
本申请实施例中所述第二设备可以是UPF，还可以是基站，或者可以是终端。也就是说，触发无效所述PDU会话的操作可以由第二核心网设备执行，也可以由基站执行，还可以由终端执行。
其中，无效所述PDU会话的操作可以是将所述PDU会话的状态由激活态转换为空闲态，或者可以是删除所述PDU会话。
下面以PDU会话建立时配置定时器为例进行具体说明，即请求消息为PDU会话建立请求消息。
参见图4A～4C所示，图4A为SMF将PDU会话的定时器配置给AN的示意图，图4B为SMF将PDU会话的定时器配置给UPF的示意图，图4C为SMF将PDU会话的定时器配置给UE的示意图。
SMF将PDU会话的定时器配置给基站的流程，如图4A所示：
S401a，UE向SMF发送PDU会话建立请求(PDU session Setup Request)消息。
S402a，SMF与SDM进行所述PDU会话认证(PDU Session Authorization)。具体为SMF从SDM中获取到会话相关的签约信息，如接入点名称(英文：Access Point Name，简称：APN)信息，数据网络名称(英文：Data Network Name，简称DNN)，会话与服务连续性模式(英文：Session and Service Continuity，简称：SSC)等，根据签约信息对UE请求的PDU会话进行认证。
S403a，SMF与PCF之间进行策略检索(Policy Retrieval)。具体的，SMF向PCF获取所述PDU会话对应的QoS策略，计费策略等。
S404a，SMF为PDU会话配置定时器。例如：SMF是为特定的网络切片服务的，根据服务的网络切片，SMF配置了对应的定时器，定时器可以称为Session inactive timer。其中网络切片是5G中运营商为了提供定制化网络服务而对于网络划分的逻辑实体，具体可以根据服务的业务类型划分，如支持移动宽带(英文：Mobile broad band，简称：MBB)业务的切片，支持(英文：Internet of Things，简称：IOT)的切片。也可以是根据不同的网络租户来划分，比如专门为一些大型企业或者组织提供的网络。
可选的，定时器还可以由PCF根据自身保存的所述PDU会话所属策略信息为该PDU会话配置定时器，并发送给SMF。或者定时器是SMF从签约信息中获取到的。
S405a，SMF向AN发送所述定时器。
具体的，SMF可以将定时器可以携带在PDU会话建立请求(PDU Session Setup Request)消息或者PDU会话建立接受(PDU Session Setup Accept)消息中发送给AN，图4A中以PDU会话建立接受消息为例进行说明。
可选地，SMF还可以从PCF获取所述PDU会话的定时器超时所需执行的无效所述PDU会话的操作的指示信息。
一种可能的实现方式中，SMF还可以将获取到的指示无效所述PDU会话的操作的指 示信息发送给AN，从而AN在监控到在PDU会话上无数据传输时，可以触发向SMF发送用于指示将PDU会话状态转换为空闲态还是删除所述PDU会话的消息。具体的，SMF可以将所述指示消息携带在PDU Session Setup Accept消息中发送给AN。所述指示信息可以是用于指示将所述PDU会话的状态转换为空闲态(SM handling for session idle)或者指示删除PDU会话(delete Session)。
另外，在SMF未将指示信息发送给AN的情况下，SMF在接收到AN检测到所述PDU会话上无数据传输，且持续到所述定时器超时时，发送的无效所述PDU会话的操作的消息时，根据从PCF获取的指示信息确定执行将PDU会话状态转换为空闲态还是执行删除所述PDU会话。
下面具体描述SMF将PDU会话的定时器配置给UPF的流程，如图4B所示：
S401b～S404b参见图4A的S401a～S404a，本申请实施例在此不再赘述。
S405b，SMF向UPF发送所述定时器。
具体的，SMF可以将定时器可以携带在会话创建请求(Create Session Request)消息中发送给UPF，图4B中以会话创建请求为例。
可选地，SMF还可以从PCF获取所述PDU会话的定时器超时所需执行的无效所述PDU会话的操作的指示信息。
一种可能的实现方式中，SMF还可以将获取到的指示无效所述PDU会话的操作的指示信息发送给UPF，从而UPF在监控到在PDU会话上无数据传输时，可以触发向SMF发送用于指示将PDU会话状态转换为空闲态还是删除所述PDU会话的消息。具体的，SMF可以将所述指示消息携带在PDU Session Setup Accept消息中发送给AN。所述指示信息可以是用于指示将所述PDU会话的状态转换为空闲态(SM handling for session idle)或者指示删除PDU会话(delete Session)。
另外，在SMF未将指示信息发送给AN的情况下，SMF在接收到UPF检测到所述PDU会话上无数据传输，且持续到所述定时器超时时，发送的无效所述PDU会话的操作的消息时，根据从PCF获取的指示信息确定执行将PDU会话状态转换为空闲态还是执行删除所述PDU会话。
下面具体描述SMF将PDU会话的定时器配置给UE的流程，如图4C所示：
S401c～S404c参见图4A的S401a～S404a，本申请实施例在此不再赘述。
SMF通过AN向UE发送用于无效所述PDU会话的操作的消息。
具体的：
S405c，SMF向AN发送会话创建请求(Create Session Request)消息或者PDU会话建立接受(PDU Session Setup Accept)消息。图4C中以会话创建请求消息为例
一种可能的实现方式中，Create Session Request携带PDU会话的定时器(Session Inactive timer)。
另一种可能的实现方式中，Create Session Request中携带PDU会话的定时器以及用于指示无效所述PDU会话的操作的指示信息。
S406c，AN在接收所述Create Session Request消息后，将所述定时器发送给UE。
在Create Session Request消息携带用于指示无效所述PDU会话的操作的指示信息情况 下，AN将所述指示信息也发送给UE。
AN可以将定时器以及指示信息携带在RRC连接重配置(RRC Connection reconfiguration)消息，或者RRC Connection direct transfer消息中发送给UE，图4C中以RRC Connection消息为例，图4C中以RRC连接重配置为例。
S407c，UE向AN发送RRC连接重配置响应(RRC Connection reconfiguration response)消息。
S408c，AN向SMF发送会话建立响应(Session Setup Response)消息。
基于图4A对应的实施例所描述的方案，下面具体描述由AN触发无效所述PDU会话的流程，参见图5A所示。
S501a，AN检测到在某一PDU会话上无数据传输且持续到定时器超时。
配置PDU会话时候，若AN接收SMF发送的用于指示无效PDU会话的指示信息时，若指示信息为Session Idle，则确定触发执行PDU会话转换为空闲态，若指示信息为delete Session，则确定触发执行删除该PDU会话。图5A中，以指示信息为Session Idle为例进行说明。
S502a-S503a，AN通过AMF向SMF发送用于指示将PDU会话转换为空闲态的第一消息。
其中第一消息可以是PDU会话非激活请求(PDU Session Inactive Request)消息，或者会话状态传输请求(Session status transition request)消息。以PDU Session Inactive Request为例，PDU Session Inactive Request消息中可以携带该PDU会话的标识。PDU会话的标识可以是PDU会话的ID，当然其它可以标识PDU会话的信息均适用于本申请，本申请在此不再赘述。另外，本申请在后续涉及到PDU会话的标识时，均以PDU会话的ID为例说明。PDU Session Inactive Request消息中还可以携带原因值(cause)，原因值用于指示该PDU会话的定时器超时。
另外，若指示信息为delete Session，则第一消息可以是删除会话请求(delete session request)消息，其中delete session request消息中可以携带该PDU会话的标识，还可以携带原因值，原因值用于指示该PDU会话的定时器超时。
在一种可能的实现方式中，配置PDU会话时候，若AN未接收到SMF发送的用于指示无效PDU会话的指示信息时，则SMF接收到由AN触发的第一消息后，基于从PCF获取的指示信息确定执行PDU会话的状态转换为空闲态还是执行删除所述PDU会话。
S504a，SMF向UPF发送用于指示删除所述PDN会话对应的与AN相关的信息的消息。
其中，用于指示删除与所述PDN会话相关的信息的消息可以是会话进入空闲态传输请求(Session-idle transition Request)消息，也可以是释放接入承载请求(Release Access Bearers Request)消息等。该Session-idle transition Request消息中携带PDU Session ID。该Session-idle transition Request消息中还可以携带原因值，原因值指示定时器超时(Session Inactive timer超时)。图5A中以会话进入空闲态传输请求(Session-idle transition Request)消息为例。
S505a，UPF删除PDU Session ID对应的所述PDN会话对应的与AN相关的信息。其中UPF还可以挂起(suspend)PDU会话对应的NG3接口信息。
在一种可能的设计中，若第一消息指示的是删除所述PDU会话，则在步骤S504a中，SMF向UPF发送用于指示删除与所述PDN会话相关的信息的消息，如delete session request消息。从而UPF执行删除与所述PDN会话相关的信息。
可选地，还包括：
S506a，UPF向SMF发送会话进入空闲态传输响应(Session-idle transition Response)消息。
S507a，SMF向AMF发送用于指示AMF将所述PDU会话设置为空闲的消息。
指示AMF将所述PDU会话设置为空闲的消息可以是会话进入空闲态传输响应(Session-idle transition Request Response)消息。图5A中以会话进入空闲态传输响应(Session-idle transition Request Response)消息
可选的，AMF在接收到所述会话进入空闲态传输响应后，将所述PDU会话的状态设置为空闲态。
S508a，SMF将PDU会话的状态设置为空闲态(Session-IDLE)。
可选地，SMF将PDU会话的状态设置为空闲态(Session-IDLE)的时机，还可以是在接收到所述第一消息后。
另外，本申请实施例不限定步骤S508a与步骤S507a执行的先后顺序。
S509a，AMF向AN发送用于指示AN将所述PDU会话的上下文释放的消息。其中，用于指示基站将所述PDU会话的上下文释放的消息可以是会话上下文释放命令(Session Context Release Command)，图5A中以会话上下文释放命令为例。
S510a，AN将所述PDU会话的对应的无线资源删除或者挂起。
具体的，挂起(suspend)或者删除该PDU session对应的无线资源承载(英文：Data Radio Bearer，简称：DRB)或者删除为传输该PDU session的数据而分配的无线资源。
需要说明的是，在多个PDU会话复用DRB的情况下，AN会删除PDU会话的数据与DRB之间的映射关系，从而使特定的DRB不再用于传输处于IDLE状态的PDU session的数据。
具体地，AN可以删除所述PDU会话对应的服务质量(英文：Quality of Service，简称：QoS)流(flow)与DRB之间的映射关系。
可选地，AN更新接入层(英文：Access Stratum，简称：AS)过滤器(AS-level filter)，该filter用于AN执行QoS flow到DRB的映射，具体可以将AS-level filter中与PDU会话相关的信息删除，或者将AS-level filter中与PDU会话相关的信息标记为非激活(inactive)或者空闲。
若UE处于RRC非激活状态，则在执行S510a后，执行S514a，否则执行S511a。
S511a，AN向UE发送用于指示UE删除或者挂起PDU会话对应的无线资源的消息。
其中，用于指示UE删除或者挂起PDU会话对应的无线资源的消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，图5A中以RRC连接重配置为例。
用于指示UE删除或者挂起PDU会话对应的无线资源的消息中可以携带待删除或者挂起的无线资源承载DRB的标识。
S512a，UE删除或者挂起PDU会话对应的DRB。
UE还可以将所述PDU会话的状态设置为空闲态。
具体的，UE还可以删除该PDU session的QoS flow到DRB的映射关系。
可选地，UE将所述PDU会话的状态设置为空闲态之前，判断所述PDU会话对应的全部无线资源被删除或者挂起。
S513a，所述UE向AN发送RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息。
S514a，所述AN向AMF发送会话上下文释放完成(Session Context release Complete)消息。
基于图4B对应的实施例所描述的方案，下面具体描述由UPF触发无效所述PDU会话的流程，参见图5B所示。
S501b，UPF检测到在某一PDU会话上无数据传输且持续到定时器超时。
在配置所述PDU会话时候，若UPF接收SMF发送的用于指示无效PDU会话的指示信息时，若指示信息为SM handling for Session Idle，则确定触发执行PDU会话转换为空闲态，若指示信息为delete Session，则确定触发执行删除该PDU会话。图5B中，以指示信息为SM handling for Session Idle为例进行说明。
S502b，UPF向SMF发送用于指示将所述PDU会话转换为空闲态的第一消息。
其中第一消息可以是PDU会话非激活请求(PDU Session Inactive Request)消息，图5B中以会话非激活请求为例。PDU Session Inactive Request消息中可以携带该PDU会话的标识。PDU会话的标识可以是PDU会话的ID，当然其它可以标识PDU会话的信息均适用于本申请，本申请在此不再赘述。PDU Session Inactive Request消息中还可以携带原因值(cause)，原因值用于指示该PDU会话的定时器超时。
另外，若指示信息为delete Session，则第一消息可以是delete session request消息。
在一种可能的实现方式中，在配置PDU会话时候，若UPF未接收到SMF发送的用于指示无效PDU会话的指示信息时，则SMF接收到由UPF触发的第一消息后，基于从PCF获取的指示信息确定执行PDU会话的状态转换为空闲态还是执行删除所述PDU会话。
S503b～S504b，SMF通过AMF向AN发送用于指示AN将所述PDU会话的上下文释放的消息。其中，用于指示AN将所述PDU会话的上下文释放的消息可以是会话上下文释放命令(Session Context Release Command)或者可以是PDU会话非激活请求(PDU Session Inactive Request)消息。用于指示基站将所述PDU会话的上下文释放的消息中可以携带PDU会话的标识(本申请中以PDU会话的ID为例)。
S505b，AN将所述PDU会话的对应的无线资源删除或者挂起。
具体的，挂起(suspend)或者删除该PDU session对应的无线资源承载(英文：Data Radio Bearer，简称：DRB)。
需要说明的是，在多个PDU会话复用DRB的情况下，删除PDU会话的数据与DRB之间的映射关系。
另外，AN还可以删除所述PDU会话对应的QoS flow与DRB之间的映射关系。
具体的，AN更新AS-level filter，该filter用于AN执行QoS flow到DRB的映射，具体可以将AS-level filter中与PDU会话相关的信息删除，或者将将AS-level filter中与PDU会话相关的信息标记为非激活(inactive)或者空闲。
S506b，AN向UE发送用于指示UE删除或者挂起PDU会话对应的无线资源的消息。
其中，用于指示UE删除或者挂起PDU会话对应的无线资源的消息可以是RRC连接 重配置(RRC Connection Reconfiguration)消息。
用于指示UE删除或者挂起PDU会话对应的无线资源的消息中可以携带待删除或者挂起的无线资源承载DRB的标识。
S507b，UE删除或者挂起PDU会话对应的DRB。
UE还可以将所述PDU会话的状态设置为空闲态。
具体的，UE还可以删除该PDU session的QoS flow到DRB的映射关系。
可选地，UE将所述PDU会话的状态设置为空闲态之前，判断所述PDU会话对应的全部无线资源被删除或者挂起。
S508b，所述UE向AN发送RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息。
S509b，所述AN向AMF发送用于指示AMF将PDU会话的状态设置为空闲态的消息。
其中，用于指示AMF将PDU会话的状态设置为空闲态的消息可以是PDU会话非激活响应(PDU Session Inactive response)消息。
S510b，所述AMF将所述PDU会话的状态设置为空闲态。
S511b，所述AMF将接收到的用于指示AMF将PDU会话的状态设置为空闲态的消息转发给SMF。
S512b，所述SMF将所述PDU会话的状态设置为空闲态。
S513b，所述SMF向UPF发送用于指示删除所述PDN会话对应的与AN相关的信息的消息。
其中，用于指示删除与所述PDN会话相关的信息的消息可以是PDU会话非激活响应(PDU Session Inactive response)消息。该PDU Session Inactive response消息中携带PDU Session ID。
S514b，UPF删除所述PDN会话对应的与AN相关的信息。其中UPF还可以删除PDU会话对应的NG3接口信息。
通过上述方案，将PDU会话的定时器配置在UPF中，可以减少AN基于PDU会话监控定时器的复杂度。在该方案中，AN可以单独针对每个UE配置定时器，并且UE的定时器和PDU会话的定时器相互独立。
基于图4C对应的实施例描述的方案，下面具体描述由UE触发无效所述PDU会话的流程，参见图5C所示。
S501c，UE检测到在某一PDU会话上无数据传输且持续到定时器超时。
在配置PDU会话时候，若UE接收SMF发送的用于指示无效PDU会话的指示信息时，若指示信息为SM handling for Session Idle，则确定触发执行PDU会话转换为空闲态，若指示信息为delete Session，则确定触发执行删除该PDU会话。图5C中，以指示信息为SM handling for Session Idle为例进行说明。
S502c-S503c，UE通过AN向SMF发送用于指示将PDU会话转换为空闲态的第一消息。
其中第一消息可以是PDU会话非激活请求(PDU Session Inactive Request)消息。PDU Session Inactive Request消息中可以携带该PDU会话的ID。PDU Session Inactive Request消息中还可以携带原因值(cause)，原因值用于指示该PDU会话的定时器超时。
另外，若指示信息为delete Session，则第一消息可以是delete Session request消息。
在一种可能的实现方式中，配置PDU会话时候，若UE未接收到SMF发送的用于指示无效PDU会话的指示信息，则SMF接收到由UE触发的第一消息后，基于从PCF获取的指示信息确定执行PDU会话的状态转换为空闲态还是执行删除所述PDU会话。
S504c，SMF向UPF发送用于指示删除所述PDN会话对应的与AN相关的信息的消息。
其中，用于指示删除与所述PDN会话相关的信息的消息可以是PDU会话非激活请求(PDU Session Inactive Request)消息，图5C中以PDU会话非激活请求为例。该PDU Session Inactive Request消息中携带PDU Session ID。该PDU Session Inactive Request消息中还可以携带原因值，原因值指示定时器超时(Session Inactive timer超时)。
S505c，UPF删除所述PDN会话对应的与AN相关的信息。其中UPF还可以删除PDU会话对应的NG3接口信息。
可选地，还包括：
S506c，UPF向SMF发送PDU会话非激活请求响应(PDU Session Inactive Request Response)消息。
S507c，SMF向AMF发送PDU会话非激活请求响应(PDU Session Inactive Request Response)消息。
可选地，AMF在接收所述PDU会话非激活请求响应消息后，将所述PDU会话的状态设置为空闲态。
S508c，SMF将PDU会话的状态设置为空闲态(Session-IDLE)。
可选地，SMF将PDU会话的状态设置为空闲态(Session-IDLE)的时机，还可以是在接收到所述第一消息后。
S509c，AMF向AN发送用于指示AN将所述PDU会话的上下文释放的消息。其中，用于指示基站将所述PDU会话的上下文释放的消息可以是会话上下文释放命令(Session Context Release Command)或者是PDU会话非激活请求响应消息。
S510c，AN将所述PDU会话的对应的无线资源删除或者挂起。
具体的，挂起(suspend)或者删除该PDU session对应的DRB。
需要说明的是，在多个PDU会话复用DRB的情况下，删除PDU会话的数据与DRB之间的映射关系。
另外，AN还可以删除所述PDU会话对应的QoS flow与DRB之间的映射关系。
具体的，AN更新AS-level filter，该filter用于AN执行QoS flow到DRB的映射，具体可以将AS-level filter中与PDU会话相关的信息删除，或者将将AS-level filter中与PDU会话相关的信息标记为inactive或者空闲。
S511c，AN向UE发送用于指示UE删除或者挂起PDU会话对应的无线资源的消息。
其中，用于指示UE删除或者挂起PDU会话对应的无线资源的消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息。
用于指示UE删除或者挂起PDU会话对应的无线资源的消息中可以携带待删除或者挂起的无线资源承载DRB的标识。
S512c，UE删除或者挂起PDU会话对应的DRB。
UE还可以将所述PDU会话的状态设置为空闲态。
具体的，UE还可以删除该PDU session的QoS flow到DRB的映射关系。
可选地，UE将所述PDU会话的状态设置为空闲态之前，判断所述PDU会话对应的全部无线资源被删除或者挂起。
S513c，所述UE向AN发送RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息。
S514c，所述AN向AMF发送PDU会话上下文释放完成消息。
在UE处于RRC非激活连接状态时，PDU会话的状态可能是空闲态也可能是激活态。因此，需要在UE上最后一个激活态的PDU会话转换为空闲态之后，UE转换为空闲态。
当UE处于RRC非激活连接状态时，PDU会话进入到空闲态后，AN即将PDU会话的状态设置为空闲态。从而UE在此后进入到RRC连接态后，需要与AN进行PDU会话的状态同步。
下面具体说明状态同步的过程，参见图6A所示，为UE处于RRC非激活连接状态时对应的状态同步流程的示意图。
S601a，UE确定自身处于RRC非激活连接状态。
S602a，有上行数据到达或者接收到寻呼请求时，UE向AN发送用于指示恢复所述UE的RRC连接的请求消息。
其中，用于指示恢复所述UE的RRC连接的请求消息可以是RRC连接恢复请求(RRC Connection Resume Request)消息。用于指示恢复所述UE的RRC连接的请求消息中携带参数，参数可以包括PDU会话的标识或者包括PDU会话对应的DRB的标识。参数中还可以包括PDU会话对应的QoS流的第一状态信息，所述第一状态信息指示所述QoS流在所述UE上的状态为激活态或者非激活态，用于所述AN与所述UE同步所述QoS流的状态。
需要说明的是，PDU会话的标识对应的PDU会话可以是有数据传输需求的PDU会话，或者说是待激活的PDU会话。
可选地，所述用于指示恢复所述UE的RRC连接的请求消息中还可以携带有数据传输需求的PDU会话的状态信息(Established PDU Session Status)，用于指示AN所建立的PDU会话在UE上的状态为激活态或者为空闲态。
S603a，AN根据上述用于指示恢复所述UE的RRC连接的请求消息中携带的参数确定待激活的PDU会话。
其中，待激活的PDU会话的状态为空闲态。
S604a，AN触发激活所述PDU会话的流程。
需要说明的是，激活所述PDU会话也就是说建立PDU会话对应的从UE到UPF之间的用户面连接。
具体的，AN触发激活所述PDU会话的流程，具体可以为AN向SMF发送用于触发将所述PDU会话转换为激活态的消息。
SMF在接收到所述用于触发将所述PDU转换为激活态的消息后，执行将所述PDU会话转换为激活态的流程。
S605a，AN配置所述PDU会话对应的QoS流与DRB之间的映射关系。
S606a，AN将配置的所述映射关系发送给UE。
可选地，AN将所述PDU会话对应的QoS流的第二状态信息发送给终端，以指示所述终端与基站同步所述QoS的状态。所述第二状态信息指示所述PDU会话对应的QoS流在所述AN上的状态为激活态或者非激活态(空闲态)。
其中，步骤S607a与步骤S605a～S606a之间不区分先后顺序。
可选地，AN可以将配置的所述映射关系携带在RRC连接恢复响应消息中发送给UE，图6A中以RRC连接恢复响应消息为例。AN可以将所述PDU会话对应的QoS流的第二状态信息也携带在RRC连接恢复响应消息中发送给UE。
S607a，UE基于所述第二状态信息与所述AN同步所述PDU会话对应的QoS流的状态，并且所述UE保存所述映射关系。
参见图6B所述，为UE处于连接管理(CM)空闲状态。
S601b，UE通过AMF向SMF发送请求消息。
其中，请求消息还可以是服务请求(Service Request)消息或者可以是激活会话请求(Active Session Request)消息，图6B中以Active Session Request消息为例。Active Session Request消息中携带参数，参数可以包括PDU会话的标识或者包括PDU会话对应的DRB的标识。参数中还可以包括PDU会话对应的QoS流的状态信息，状态信息指示所述QoS流在所述UE上的状态为激活态或者非激活态，用于所述SMF与所述UE同步所述QoS流的状态。
需要说明的是，PDU会话的标识对应的PDU会话可以是有数据传输需求的PDU会话，或者说是待激活的PDU会话。
可选地，所述Active Session Request消息中还可以携带有数据传输需求的PDU会话的状态信息(Established PDU Session Status)，用于指示SMF所建立的PDU会话在UE上的状态为激活态或者为空闲态。从而用于UE与SMF之间的PDU会话的状态同步。
S602b，SMF接收到UE发送的请求消息后，与UPF之间完成激活所述PDU会话中的QoS流。
S603b，SMF确定完成激活后的所述PDU会话中的QoS流的状态。
SMF在确定完成激活后的所述PDU会话中的QoS流的状态后，将所述PDU会话中的QoS流的状态信息发送给UE。所述PDU会话中的QoS流的状态信息指示所述PDU会话对应的QoS流在所述SMF上的状态为激活态或者非激活态。
具体的，SMF通过AMF以及AN将所述PDU会话中的QoS流的状态信息发送给UE。
可选地，S604b，SMF可以通过激活会话请求响应(Active Session response)消息将PDU会话中的QoS流的状态信息先发给AMF。
S605b，AMF将PDU会话中的QoS流的状态信息携带在会话上下文更新(Session Context Update)消息中，或者携带在激活会话响应(Active Session response)消息中发送给AN。
另外，AN在接收到SMF发来的所述PDU会话中的QoS流的状态信息后，AN可以与SMF之间同步所述PDU会话中的QoS流的状态，并转发给UE。
S606b，AN可以将所述PDU会话中的QoS流的状态信息携带RRC重配置(RRC Reconfiguration)消息中发送给UE。
S607b，所述UE基于所述SMF发来的状态信息与所述SMF同步所述PDU会话对应 的QoS流的状态。
可选地，还可以包括：
S608b，UE向AN发送RRC重配置响应(RRC Reconfiguration response)消息。
S609b，AN向AMF发送会话上下文更新响应(Session context update response)消息。
S610b，AMF向SMF发送会话上下文更新响应(Session context update response)消息。
S611b，SMF与UPF之间进行执行更新会话的用户面(Update Session User Plane)。
S612b，SMF向AMF发送更新会话响应(Update Session response)消息。
下面具体描述在针对不同的PDU会话存在不同的状态的情况下，小区切换方法流程，参见图7所示为小区切换流程示意图。图7中S-AN表示源AN，T-AN表示目标AN。
S701，UE向S-AN发送测量报告。其中测量报告中包括服务小区的测量结果，以及邻小区的测量结果。
S702，S-AN基于UE发送的测量报告确定执行小区切换(英文：Handover，简称：HO)。
S703，S-AN向AMF发送切换请求消息(HO Required)。
所述切换请求消息中携带所述UE上的PDU会话的标识。其中所述PDU会话的标识对应的PDU会话的状态为激活态。所述PDU会话的标识对应的PDU会话为所述UE对应的且在所述S-AN保存有PDU会话上下文的PDU会话。
S704，AMF基于所述PDU会话的标识确定需要更新用户面上下文的PDU会话。
S705，AMF向SMF发送用于通知SMF更新所述PDU会话的用户面上下文的消息。
其中，用于通知SMF更新所述PDU会话的用户面上下文的消息可以是切换请求(HO Request)消息，图7中以切换请求为例。其中，向SMF发送的HO Request消息携带PDU会话的标识(ID)
S706，SMF通过AMF向T-AN发送HO Request消息。发给T-AN的HO Request消息中可以携带所述PDU会话的相关信息(PDU session Info)。具体包括PDU session对应的QoS信息，NG3隧道信息，QoS flow ID等。
S707，T-AN向AMF发送切换请求回执(HO Request Acknowledge)。
S708，AMF通过S-AN向UE发送切换命令(HO command)。
S709，UE完成切换后向T-AN发送切换确认(HO Confirm)。
S710，T-AN通过AMF向SMF发送切换通知(HO notify)。
S711，SMF向UPF发送修改会话请求(Modify Session request)消息，用于指示UPF修改所述PDU会话的相关信息。
S712，UPF向SMF发送修改会话请求响应(Modify Session request response)消息。
步骤S707～步骤S712中所涉及的消息的用途与现有技术中的消息用途相同，本申请在此不再赘述。
基于图4A对应的实施例描述的方案，下面具体描述在切换过程中由AN触发无效所述PDU会话的流程，参见图13所示。图13中S-AN表示终端当前接入的源AN，T-AN表示UE待切入的目标AN。
S801，在终端的PDU会话建立或者激活时，S-AN配置该PDU会话的定时器。
具体的，所述UE当前接入的S-AN接收SMF发送的所述PDU会话的定时器，则S-AN配置到该PDU会话的定时器。
S802，所述S-AN接收到SMF发送的所述PDU会话的定时器后，若所述S-AN检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态。
比如，将该PDU会话记录为inactive PDU session，或者针对该PDU Session ID进行标记，等等，或者更新用于表征所述PDU session为不活动状态的PDU session ID。。
S803，S-AN在确定针对所述UE执行从所述S-AN切换到T-AN时，确定所述UE的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话(inactive PDU session)，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话(active PDU session)。
具体的，所述S-AN接收到UE发送的测量报告(measurement report)，所述S-AN根据所述测量报告确定是否针对所述UE执行从所述S-AN切换到T-AN。若确定针对所述UE执行从所述S-AN切换到T-AN时，此时确定当前终端的所有激活的PDU会话中被记录为不活动状态的PDU会话，从而针对第一类PDU会话不执行切换流程，而仅针对第二类PDU会话执行切换流程。
一种可能的实现方式中，所述S-AN针对所述第二类PDU会话执行切换流程中包括：所述S-AN向所述T-AN发送切换请求(handover request)。
其中，所述切换请求中可以仅携带所述第二类PDU会话的标识，而不携带第一类PDU会话的标识。或者，所述切换请求中可以是携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识。比如第一类PDU会话的ID配置在数组1中，第二类PDU会话的ID配置在数组2中。或者，所述切换请求中还可以携带所述终端的所有激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。比如，终端所有的激活的PDU会话ID放在一个数组中，针对第一类PDU会话以及第二类PDU会话通过不同的标记进行区分，比如第一类PDU会话标记为0，第二类PDU会话标记为1。
需要说明的是，UE的激活的PDU会话的标识(ID)或者第一类PDU会话ID或者第二类PDU会话ID可以均携带在激活的PDU会话的上下文(active PDU session info)中，还可以携带在active PDU session info之外。
比如，切换请求中可以携带AS层内容(AS content)。AS content中可以包括终端所有的激活的PDU会话的上下文。终端所有的激活的PDU会话的上下文中包括有终端的激活的PDU会话的ID，并在终端所有的激活的PDU会话的上下文之外且在切换请求中还携带第一类PDU会话的ID，或者在终端所有的激活的PDU会话的上下文之外且在切换请求中还携带所有激活的PDU会话的ID以及第一指示。或者，切换请求中的AS content中可以仅包括第二类PDU会话的上下文(active PDU session info)，active PDU session info之外且在切换请求中携带第一类PDU会话的ID(inactive PDU session IDs)。或者，切换请求中仅携带active PDU session info。
另一种可能的实现方式中，所述S-AN针对所述第二类PDU会话执行切换流程中包括：所述S-AN向所述AMF发送切换请求(handover required)。其中，所述切换请求中可以仅携带所述第二类PDU会话的标识，而不携带第一类PDU会话的标识。或者，所述切换请 求中可以是携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识。比如第一类PDU会话的ID配置在数组1中，第二类PDU会话的ID配置在数组2中。或者，所述切换请求中还可以携带所述终端的所有激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。比如，终端所有的激活的PDU会话ID放在一个数组中，针对第一类PDU会话以及第二类PDU会话通过不同的标记进行区分，比如第一类PDU会话标记为0，第二类PDU会话标记为1。
需要说明的是，UE的激活的PDU会话的标识(ID)或者第一类PDU会话ID或者第二类PDU会话ID可以均携带在激活的PDU会话的上下文(active PDU session info)中，还可以携带在active PDU session info之外。
比如，切换请求中可以携带透明容器(source to target transparent container)。source to target transparent container中可以包括终端所有的激活的PDU会话的上下文。终端所有的激活的PDU会话的上下文中包括有终端的激活的PDU会话的ID，并在终端所有的激活的PDU会话的上下文之外且在切换请求中还携带第一类PDU会话的ID，或者在终端所有的激活的PDU会话的上下文之外且在切换请求中还携带所有激活的PDU会话的ID以及第一指示。或者，切换请求中的AS content中可以仅包括第二类PDU会话的上下文(active PDU session info)，active PDU session info之外且在切换请求中携带第一类PDU会话的ID(inactive PDU session IDs)，或者，切换请求中仅携带active PDU session info。
下面在图13的基础上，下面具体描述在切换过程中由AN触发无效所述PDU会话的流程，参见图14A～图14C所示。
参见图14A所示为基于Xn(AN与AN之间的接口)接口切换。以切换请求中的AS content中包括第二类PDU会话的上下文(active PDU session info)，active PDU session info之外且在切换请求中携带第一类PDU会话的ID(inactive PDU session IDs)为例。
S901a，在终端的PDU会话建立或者激活时，S-AN配置该PDU会话的定时器。
具体的，所述UE当前接入的S-AN接收SMF发送的所述PDU会话的定时器，则S-AN配置到该PDU会话的定时器。
S902a，所述S-AN接收到SMF发送的所述PDU会话的定时器后，若所述S-AN检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态。
比如，将该PDU会话记录为inactive PDU session，或者针对该PDU Session ID进行标记，等等，或者更新用于表征所述PDU session为不活动状态的PDU session ID。
S903a，UE向所述S-AN发送测量报告(measurement report)。
S904a，所述S-AN接收到UE发送的测量报告(measurement report)，所述S-AN根据所述测量报告确定是否针对所述UE执行从所述S-AN切换到T-AN。
S-AN在确定针对所述UE执行从所述S-AN切换到T-AN时，确定所述UE的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
具体的，所述S-AN针对所述第二类PDU会话执行切换流程中包括：
S905a，所述S-AN向所述T-AN发送切换请求(handover request)。
S906a，所述T-AN向所述S-AN发送切换请求回执(handover request ACK)。切换请求回执中可以包括由T-AN从As content中解析出的第二类PDU会话的上下文以及第一类PDU会话的ID(inactive PDU session IDs)。
S907a，S-AN向UE发送用于指示所述终端执行无效所述第一类PDU会话的操作的消息。
其中，所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述第一类PDU会话的标识；或者，所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标识所述终端的激活的PDU会话中的第一类PDU会话。
所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息可以是RRC重配置(RRC reconfiguration)消息，图14A中以此为例。RRC重配置(RRC reconfiguration)消息中携带所述第一类PDU会话的ID。图14A中以无效所述第一类PDU会话的操作为将所述第一类PDU会话的状态由激活态转换为空闲态为例。
S908a，所述UE向S-AN发送RRC重配置完成(RRC reconfiguration complete)消息。
S909a，UE将RRC重配置消息中第一类PDU会话(inactive PDU session)对应的状态更新为空闲态(session-IDLE)。
S910a-S916a为针对第二类PDU会话执行核心网路径切换的流程。
S910a，T-AN向AMF发送N2路径转换(N2path switch)消息，N2path switch携带第二类PDU会话的上下文。N2path switch还可以携带第一类PDU会话的标识。N2为基站与AMF之间的接口。N2path switch用于指示AMF将路径由S-AN转到T-AN，更新第二类PDU会话的上下文。
S911a，AMF向SMF发送N11message(N11消息)，N11message携带第二类PDU会话的上下文。N11为SMF与AMF之间的接口。N11message用于指示SMF更新所述第二类PDU会话的上下文。
S912a，SMF向UPF发送N4会话修改(N4session modify)，N4session modify携带第二类PDU会话的上下文。N4为SMF与UPF之间的接口。
S913a，UPF向SMF发送N4session modify回执(ACK)。
S914a，SMF向AMF发送N11session modify ACK。
S915a，AMF向T-AN发送N2path switch ACK。
S916a，T-AN向S-AN发送UE上下文释放消息(UE content release)。
S917a，在S910中所述AMF在接收到S-AN发送的N2路径转换(N2path switch)后，在N2path switch中没携带第一类PDU会话的标识的情况下，所述AMF基于所述第二类PDU会话的标识确定第一类PDU会话。在AMF保存有终端的所有激活的PDU会话的标识，从而AMF确定保存的所述终端的激活的PDU会话中除所述标识对应的第二类PDU会话以外的PDU会话。
S918a，所述AMF向SMF发送用于指示SMF执行无效所述第一类PDU会话的操作的消息。用于SMF指示执行无效所述第一类PDU会话的操作的消息可以为N11message。
若在S910a中所述AMF在接收到S-AN发送的N2路径转换(N2path switch)后，在N2path switch中携带了第一类PDU会话的标识的情况下，可以直接执行S918a。
S919a，SMF向UPF发送用于指示UPF执行无效所述第一类PDU会话的操作的消息。 用于SMF指示执行无效所述第一类PDU会话的操作的消息可以是N4会话转换为空闲态消息(session-IDLE transition)。
S920a，UPF将所述第一类PDU会话的状态转换为空闲态。图14A中以无效所述第一类PDU会话的操作为所述第一类PDU会话的状态转换为空闲态为例说明。
S921a，所述UPF向SMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。用于指示执行完成无效所述第一类PDU会话的操作的消息可以是N4会话转换为空闲态完成消息(N4session-IDLE transition complete)。
S922a，SMF执行将所述第一类PDU会话的状态转换为空闲态。
S923a，SMF向AMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。用于指示执行完成无效所述第一类PDU会话的操作的消息可以通过N11message ACK。
S924a，AMF执行将所述第一类PDU会话的状态转换为空闲态。
参见图14B所示为基于Xn(AN与AN之间的接口)接口切换。以切换请求中的AS content中包括第二类PDU会话的上下文(active PDU session info)，切换请求中不携带第一类PDU会话的ID(inactive PDU session IDs)为例。
S901b，在终端的PDU会话建立或者激活时，S-AN配置该PDU会话的定时器。
具体的，所述UE当前接入的S-AN接收SMF发送的所述PDU会话的定时器，则S-AN配置到该PDU会话的定时器。
S902b，所述S-AN接收到SMF发送的所述PDU会话的定时器后，若所述S-AN检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态。
比如，将该PDU会话记录为inactive PDU session，或者针对该PDU Session ID进行标记，等等，或者更新用于表征所述PDU session为不活动状态的PDU session ID。
S903b，UE向所述S-AN发送测量报告(measurement report)。
S904b，所述S-AN接收到UE发送的测量报告(measurement report)，所述S-AN根据所述测量报告确定是否针对所述UE执行从所述S-AN切换到T-AN。
S-AN在确定针对所述UE执行从所述S-AN切换到T-AN时，确定所述UE的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
具体的，所述S-AN针对所述第二类PDU会话执行切换流程中包括：
S905b，所述S-AN向所述T-AN发送切换请求(handover request)。
S906b，所述T-AN向所述S-AN发送切换请求回执(handover request ACK)。切换请求回执中可以包括由T-AN从Ascontent中解析出的第二类PDU会话的上下文。
S907b，S-AN向UE发送RRC重配置(RRC reconfiguration)消息。
S908b，所述UE向S-AN发送RRC重配置完成(RRC reconfiguration complete)消息。
S909b-S915b为针对第二类PDU会话执行核心网路径切换的流程。
S909b，T-AN向AMF发送N2路径转换(N2path switch)消息，N2path switch携带第二类PDU会话的上下文。N2为基站与AMF之间的接口。N2path switch用于指示AMF将路径由S-AN转到T-AN，更新第二类PDU会话的上下文。
S910b，AMF向SMF发送N11message(N11消息)，N11message携带第二类PDU会话的上下文。N11为SMF与AMF之间的接口。N11message用于指示SMF更新所述第二类PDU会话的上下文。
S911b，SMF向UPF发送N4会话修改(N11session modify)，N11path switch携带第二类PDU会话的上下文。N11为SMF与AMF之间的接口。
S912b，UPF向SMF发送N11session modify确认(ACK)。
S913b，SMF向AMF发送N11session modify ACK。
S914b，AMF向T-AN发送N2path switch ACK。
S915b，T-AN向S-AN发送UE上下文释放消息(UE content release)。
S916b，在S909b中所述AMF在接收到S-AN发送的N2路径转换(N2path switch)后，所述AMF基于所述第二类PDU会话的标识确定第一类PDU会话。在AMF保存有终端的所有激活的PDU会话的标识，从而AMF确定保存的所述终端的激活的PDU会话中除所述标识对应的第二类PDU会话以外的PDU会话。
S917b，所述AMF向SMF发送用于指示SMF执行无效所述第一类PDU会话的操作的消息。用于SMF指示执行无效所述第一类PDU会话的操作的消息可以通过N11message。
S918b，SMF向UPF发送用于指示UPF执行无效所述第一类PDU会话的操作的消息。用于指示UPF执行无效所述第一类PDU会话的操作的消息可以是N4session-IDLE transition。
S919b，UPF将所述第一类PDU会话的状态转换为空闲态。图14B中以无效所述第一类PDU会话的操作为所述第一类PDU会话的状态转换为空闲态为例说明。
S920ba，所述UPF向SMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。
S921b，SMF执行将所述第一类PDU会话的状态转换为空闲态。
S922b，SMF向AMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。用于指示执行完成无效所述第一类PDU会话的操作的消息可以通过N11message ACK。
S923b，AMF执行将所述第一类PDU会话的状态转换为空闲态。
S924b，AMF向UE发送用于指示UE执行无效所述第一类PDU会话的操作的消息。用于指示UE执行无效所述第一类PDU会话的操作的消息可以是N1会话转为空闲态请求(N1session-IDLE transition request)。N1session-IDLE transition request携带第一类PDU会话的标识，或者携带终端的激活的PDU会话的标识以及第一指示。N1为AMF与UE之间的接口。
S925b，所述UE将所述第一类PDU会话的状态更新为空闲态。
S926b，所述UE向所述AMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。用于指示执行完成无效所述第一类PDU会话的操作的消息可以是N1session-IDLE transition response。
参见图14C所示为基于X1(AN与核心网之间的接口)接口切换。切换请求中的透明容器(source to target transparent container)包括第二类PDU会话的上下文(active PDU session info)，active PDU session info之外且在切换请求中携带第一类PDU会话的ID(inactive PDU session IDs)为例。
S901c，在终端的PDU会话建立或者激活时，S-AN配置该PDU会话的定时器。
具体的，所述UE当前接入的S-AN接收SMF发送的所述PDU会话的定时器，则S-AN配置到该PDU会话的定时器。
S902c，所述S-AN接收到SMF发送的所述PDU会话的定时器后，若所述S-AN检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态。
比如，将该PDU会话记录为inactive PDU session，或者针对该PDU Session ID进行标记，等等，或者更新用于表征所述PDU session为不活动状态的PDU session ID。
S903c，UE向所述S-AN发送测量报告(measurement report)。
S904c，所述S-AN接收到UE发送的测量报告(measurement report)，所述S-AN根据所述测量报告确定是否针对所述UE执行从所述S-AN切换到T-AN。
S-AN在确定针对所述UE执行从所述S-AN切换到T-AN时，确定所述UE的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
具体的，所述S-AN针对所述第二类PDU会话执行切换流程中包括：
S905c，所述S-AN向所述AMF发送切换请求(handover required)。
该handover required中的透明容器(source to target transparent container)包括第二类PDU会话的上下文(active PDU session info)，active PDU session info之外且在切换请求中携带第二类PDU会话的ID(active PDU session IDs)。
该切换请求(handover required)用于指示针对第二类PDU会话以外的其它PDU会话(即第一类PDU会话)不执行切换操作，即执行无效第二类PDU会话以外的其它PDU会话的操作。无效第一类PDU会话的为将所述第一类PDU会话的状态更新为空闲态或者删除所述第一类PDU会话
S906c，AMF向SMF发送N11切换请求(N2handover required)消息。
S907c，SMF向AMF发送N11切换请求(N11handover request)，N11handover request携带终端的所有激活的PDU会话的上下文(PDU session info)。
S908c，AMF向T-AN发送切换请求(handover request)，该handover request携带透明容器(source to target transparent container)。
S909c，T-AN向AMF发送切换请求回执(handover request ACK)。该handover request ACK中携带透明容器(source to target transparent container)。
S910c，AMF向SMF发送切换请求回执(handover request ACK)，该handover request ACK携带PDU会话的上下文。
S911c，SMF向AMF发送N11切换命令(N11handover command)。
S912c，所述AMF通过S-AN向UE发送切换命令(handover command)。
S913c，所述UE向T-AN发送切换确认(handover cofirm)。
S914c，所述T-AN向AMF发送切换通知(handover notify)。切换通知(handover notify)用于指示AMF将终端的PDU会话由S-AN转换到T-AN。
S915c，所述AMF基于所述第二类PDU会话的标识确定第一类PDU会话。在AMF保存有终端的所有激活的PDU会话的标识，从而AMF确定保存的所述终端的激活的PDU 会话中除所述标识对应的第二类PDU会话以外的PDU会话。
具体的，在步骤S905c所述S-AN向所述AMF发来的切换请求(handover required)中携带有所述第二类PDU会话的标识。
可选地，所述AMF基于所述第二类PDU会话的标识确定第一类PDU会话，后所述AMF执行将所述第一类PDU会话的状态更新为空闲态或者删除所述第一类PDU会话。
S916c，所述AMF向SMF发送切换通知(handover notify)。切换通知(handover notify)携带第一类PDU会话的标识，用于指示AMF将终端的PDU会话由S-AN转换到T-AN。
S917c，所述SMF与UPF之间执行PDU会话修改(modify session)。
S918c，所述AMF基于所述第二类PDU会话的标识确定第一类PDU会话后，向SMF发送用于指示SMF执行无效所述第一类PDU会话的操作的消息。指示SMF执行无效所述第一类PDU会话的操作的消息可以是N11message。指示SMF执行无效所述第一类PDU会话的操作的消息中可以携带第一类PDU会话的标识。
S920c，所述SMF向UPF发送用于指示UPF执行无效所述第一类PDU会话的操作的消息。用于指示UPF执行无效所述第一类PDU会话的操作的消息可以是N4session-IDLE transition。
S920c，UPF将所述第一类PDU会话的状态转换为空闲态。
S921c，所述UPF向SMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。
S922c，SMF执行将所述第一类PDU会话的状态转换为空闲态。
S923c，SMF向AMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。用于指示执行完成无效所述第一类PDU会话的操作的消息可以通过N11message ACK。
S924c，AMF执行将所述第一类PDU会话的状态转换为空闲态。
S925c，AMF向UE发送用于指示UE执行无效所述第一类PDU会话的操作的消息。用于指示UE执行无效所述第一类PDU会话的操作的消息可以是N1session-IDLE transition request。N1为AMF与UE之间的接口。
S926c，所述UE将所述第一类PDU会话的状态更新为空闲态。
S927c，所述UE向所述AMF发送用于指示执行完成无效所述第一类PDU会话的操作的消息。用于指示执行完成无效所述第一类PDU会话的操作的消息可以是N1session-IDLE transition response。
基于与方法实施例同样的发明构思，本申请实施例还提供了会话管理装置，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本申请实施例提供了一种会话管理装置，所述装置应用于第一核心网设备，包括，参见图8A所示。
接收模块801a，用于接收激活分组数据单元PDU会话的请求消息；
发送模块802a，用于向第二设备发送所述PDU会话的定时器；
所述接收模块801a，还用于接收所述第二设备发起的无效所述PDU会话的操作的第一消息；所述第一消息是所述第二设备检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时发出的。
在一种可能的设计中，所述第二设备为第二核心网设备、或者为基站、或者为终端。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，还包括：
第一确定模块803a，用于在所述发送模块802a向所述第二设备发送所述定时器之前，基于所述PDU会话所属的网络切片的切片信息确定所述PDU会话的定时器。
在一种可能的设计中，所述接收模块801a，还用于接收由第三核心网设备发送的所述PDU会话的定时器。
在一种可能的设计中，所述发送模块802a，还用于向所述第二设备发送指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
在一种可能的设计中，所述接收模块801a，还用于在接收所述请求消息后，接收由第三核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
在一种可能的设计中，第二确定模块804a，用于在所述接收模块801a接收到所述第一消息后，基于所述指示信息确定所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态或者为删除所述PDU会话。
在一种可能的设计中，所述第一消息中携带所述PDU会话的标识。
在一种可能的设计中，所述第一消息还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
在一种可能的设计中，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述接收模块801a，还用于在接收到所述第一消息后，向所述第二核心网设备发送用于指示删除所述PDN会话对应的与基站相关的信息的消息。
在一种可能的设计中，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述装置还包括：
处理模块805a，用于在所述接收模块801a接收到所述第一消息后，将所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述无效所述PDU会话的操作为删除所述PDU会话，所述发送模块，还用于在所述接收模块801a接收到所述第一消息后，向所述第二核心网设备发送用于指示删除与所述PDN会话相关的信息的消息。
在一种可能的设计中，所述无效所述PDU会话的操作为删除所述PDU会话，所述发送模块，还用于在接收到所述第一消息后，向终端发送用于指示所述终端删除与所述PDN会话相关的信息的消息。
在一种可能的设计中，所述发送模块802a，还用于在所述接收模块801a接收到所述第一消息后，向基站发送用于指示基站将所述PDU会话的上下文释放的消息。
在一种可能的设计中，所述发送模块802a，还用于在所述接收模块801a接收到所述第一消息后，向第四核心网设备发送用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态的消息。
在一种可能的设计中，所述接收模块801a，还用于接收到第四核心网设备发送的第二消息，所述第二消息携带待更新用户面上下文的PDU会话的标识；
所述装置还包括：
更新模块806a，用于更新所述PDU会话的标识对应的所述PDU会话的用户面上下文。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例提供了一种会话管理装置，所述装置应用于第一核心网设备，参见图8B所示，包括：
接收模块801b，用于接收终端发送的服务请求消息，所述服务请求消息中携带待激活的PDU会话的标识；
处理模块802b，用于基于所述服务请求消息执行激活所述PDU会话的流程。
在一种可能的设计中，所述服务请求消息中携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述第一状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态，用于所述第一核心网设备与所述终端同步所述QoS流的状态。
在一种可能的设计中，所述装置还包括：
发送模块803b，用于向所述终端发送的所述PDU会话对应的QoS流的第三状态信息，以指示所述终端与所述第一核心网设备同步所述PDU会话对应的QoS流的状态；所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
如图8C所示，第一核心网设备可以包括处理器820。上述图8A或8B所示的模块对应的实体的硬件可以为处理器820。处理器820，可以是一个中央处理模块(英文：central processing unit，简称CPU)，或者为数字处理模块等等。第一核心网设备还可以包括通信接口810，处理器820通过通信接口810接收数据或者消息。该装置还包括：存储器830，用于存储处理器820执行的程序。存储器830可以是非易失性存储器，比如硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)等，还可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)。存储器830是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
处理器820用于执行存储器830存储的程序代码，具体用于执行图3至图7、图13、图14A～图14C所示实施例中第一核心网设备所执行的方法。可以参见图3至图7、图13、图14A～图14C所示实施例所述的方法，本申请在此不再赘述。
本申请实施例中不限定上述通信接口810、处理器820以及存储器830之间的具体连接介质。本申请实施例在图8C中以存储器830、处理器820以及通信接口810之间通过总线840连接，总线在图8C中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图8C中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例提供了一种会话管理装置，所述装置应用于基站，参见图9A所示，包 括：
接收模块901a，用于在分组数据单元PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
处理模块902a，用于检测到在所述PDU会话上无数据传输，且持续到所述定时器超时；
所述发送模块903a，用于向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述接收模块901a，还用于在PDU会话激活时，接收到所述第一核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
在一种可能的设计中，所述第一消息携带所述PDU会话的标识。
在一种可能的设计中，所述第一消息中还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
在一种可能的设计中，所述接收模块901a，还用于接收到所述第一核心网设备发送的用于指示所述基站将所述PDU的上下文释放的消息；
所述处理模块902a，还用于将所述PDU会话对应的无线资源删除或者挂起。
在一种可能的设计中，所述处理模块902a，还用于：
将保存的所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述处理模块902a，还用于在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，删除所述PDU会话对应的服务质量QoS流与无线资源承载DRB之间的映射关系。
在一种可能的设计中，所述发送模块903a，还用于在所述处理模块902a监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，向所述终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。
在一种可能的设计中，所述用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息中携带：待删除或者挂起的无线资源承载DRB的标识。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例还提供一种会话管理装置，所述装置应用于基站，参见图9B所示，包括：
接收模块901b，用于接收所述终端发送的RRC连接恢复消息，所述RRC连接恢复消息中携带参数；
处理模块902b，用于根据所述参数确定待激活的PDU会话；并触发激活所述PDU会话的流程。
在一种可能的设计中，所述参数为所述待激活的PDU会话的标识，或者所述待激活的PDU会话对应的无线资源承载DRB的标识。
在一种可能的设计中，所述待激活的PDU会话的状态为空闲态。
在一种可能的设计中，所述RRC连接恢复消息中还携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述状态信息用于所述基站与所述终端同步所述QoS流的状态。
在一种可能的设计中，所述装置还包括：
发送模块903b，用于向第一核心网设备发送用于触发将所述PDU会话转换为激活态的消息。
在一种可能的设计中，所述处理模块902b，还用于配置所述PDU会话对应的QoS流与DRB之间的映射关系。
在一种可能的设计中，还包括：
发送模块903b，还用于将所述映射关系发送给所述终端。
在一种可能的设计中，所述装置还包括：
发送模块903b，用于将所述PDU会话对应的QoS流的第二状态信息发送给终端，以指示所述终端与基站同步所述QoS的状态。
在一种可能的设计中，所述处理模块902b，还用于确定针对终端执行小区切换；
发送模块903b，用于向第四核心网设备发送切换请求消息，所述切换请求消息中携带所述终端对应的状态为激活态的PDU会话的标识或者所述切换请求中携带所述终端对应的且在所述基站保存有PDU会话上下文的PDU会话的标识。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例还提供一种会话管理装置，所述装置应用于源基站，参见图9D所示，包括：
接收模块901d，用于在终端的PDU会话建立或者激活时，接收第一核心网设备发送的所述PDU会话的定时器；若所述源基站检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态；
处理模块902d，用于在确定针对所述终端执行从所述源基站切换到目标基站时，确定所述终端的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
在一种可能的实现方式中，还包括：
发送模块903d，用于在所述处理模块902d针对第二类PDU会话向所述目标基站发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
在一种可能的实现方式中，发送模块903d，用于在针对第二类PDU会话执行切换的过程中，向所述终端发送用于指示所述终端执行无效所述第一类PDU会话的操作的消息。
可选的，所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述第一类PDU会话的标识；或者，
所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标识所述终端的激活的PDU会话中的第一类PDU会话。
可选的，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的实现方式中，所述装置中的发送模块903d，用于在所述处理模块902d针对第二类PDU会话执行切换流程时，向第四核心网设备发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例还提供一种会话管理装置，所述装置应用目标基站，参见图9E所示，包括：
接收模块901e，接收终端当前接入的源基站发送的切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话的标识中的第一类PDU会话；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；所述第二类PDU会话为所述终端的激活的PDU会话中除标记为活动状态的PDU会话以外的PDU会话；
发送模块902e，用于向第四核心网设备发送用于指示所述第四核心网设备执行无效所述第第一类PDU会话的操作的消息。
其中，所述用于指示所述第四核心网设备执行无效所述第二类PDU会话的操作的消息中携带：所述第一类PDU会话的标识。其中，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
如图9C所示，基站(基站可以是源基站或者可以是目标基站)可以包括处理器920。上述图9A或9B或者9D或者9E所示的模块对应的实体的硬件可以为处理器920。处理器 920，可以是一个中央处理模块(英文：central processing unit，简称CPU)，或者为数字处理模块等等。基站还可以包括收发器910，处理器920通过收发器910接收数据、消息。该装置还包括：存储器930，用于存储处理器920执行的程序。存储器930可以是非易失性存储器，比如硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)等，还可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)。存储器930是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
处理器920用于执行存储器930存储的程序代码，具体用于执行图3至图7、图13、图14A～图14C所示实施例中基站所执行的方法。可以参见图3至图7、图13、图14A～图14C所示实施例所述的方法，本申请在此不再赘述。
本申请实施例中不限定上述收发器910、处理器920以及存储器930之间的具体连接介质。本申请实施例在图9C中以存储器930、处理器920以及收发器910之间通过总线940连接，总线在图9C中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9C中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例提供了一种会话管理装置，所述装置应用于终端，参见图10A所示，所述装置包括：
接收模块1001a，用于接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息；
处理模块1002a，用于删除或者挂起所述PDU会话对应的无线资源，并将所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述处理模块1002a，还用于在所述接收模块1001a接收到所述基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息后，判断所述PDU会话对应的全部无线资源被删除或者挂起时，将所述PDU会话的状态设置为空闲态。
在一种可能的设计中，所述接收模块1001a，还用于在接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息之前，在所述PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
所述装置还包括：
发送模块1003a，还用于在所述处理模块1002a监控到在所述PDU会话上无数据传输，且持续到所述定时器超时时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述接收模块1001a，还用于在所述PDU会话激活时，接收所述第一核心网设备发送的第一指示信息，所述第一指示信息为用于指示所述无效所述PDU会话的操作的信息。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器 中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例提供了一种会话管理装置，所述装置应用于终端，参见图10B所示，所述装置包括：
接收模块1003b，用于接收上行数据或者接收到寻呼请求；
处理模块1001b，用于确定接收模块接收到上行数据或者接收到寻呼请求；
发送模块1002b，用于向网络设备发送请求消息，所述请求消息中携带有PDU会话的标识，和/或携带PDU会话对应的QoS流的第一状态信息，所述第一状态信息指示所述QoS流在所述终端上的状态为激活态或者非激活态，用于所述网络设备与所述终端同步所述QoS流的状态。
在一种可能的设计中，所述终端的无线资源控制RRC状态为RRC非激活连接状态，所述网络设备为基站，所述请求消息用于指示恢复所述终端的RRC连接。
在一种可能的设计中，所述接收模块1003a，还用于接收所述基站发送的所述PDU会话对应的QoS流的第二状态信息，所述第二状态信息指示所述QoS流在所述基站上的状态为激活态或者非激活态；
所述处理模块1001b，还用于基于所述第二状态信息与所述基站同步所述PDU会话对应的QoS流的状态。
在一种可能的设计中，所述接收模块1003a，还用于接收所述基站发送的所述PDU会话对应的QoS流与DRB的映射关系；
所述处理模块1001b，还用于保存所述映射关系。
在一种可能的设计中，所述终端的连接管理CM状态为空闲状态，所述网络设备为第四核心网设备，所述请求消息用于指示将所述终端从CM空闲状态转换为CM连接状态。
在一种可能的设计中，所述接收模块1003a，还用于接收由所述第一核心网设备发送的所述PDU会话对应的QoS流的第三状态信息，所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态；
所述处理模块1001b，还用于基于所述第三流状态信息与所述第一核心网设备同步所述PDU会话对应的QoS流的状态。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例提供了一种会话管理装置，所述装置应用于终端，参见图10D所示，所述装置包括：
接收模块1001d，用于在终端从当前接入的源基站切换到目标基站的过程中，接收到所述源基站或者第四核心网设备发送的用于指示执行无效第一类分组数据单元PDU会话的操作的消息；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
处理模块1002d，用于基于所述消息执行无效所述第一类PDU会话的操作。
在一种可能的设计中，所述用于指示所述终端执行无效第一类分组数据单元PDU会话的操作的消息中携带：第一类PDU会话的标识。
在一种可能的设计中，所述用于指示执行无效第一类分组数据单元PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话；
所述终端基于所述消息执行无效所述第一类PDU会话的操作，包括：
所述终端根据所述第一指示确定所述终端的激活的PDU会话中的第一类PDU会话，并执行无效所述第一类PDU会话的操作。
在一种可能的设计中，所述无效所述第一类PDU会话的操作，包括：
将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
如图10C所示，终端可以包括处理器1020。上述图10A或10B或者10D所示的模块对应的实体的硬件可以为处理器1020。处理器1020，可以是一个中央处理模块(英文：central processing unit，简称CPU)，或者为数字处理模块等等。终端还可以包括收发器1010，处理器1020通过收发器1010接收数据、消息。该装置还包括：存储器1030，用于存储处理器1020执行的程序。存储器1030可以是非易失性存储器，比如硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)等，还可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)。存储器1030是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
处理器1020用于执行存储器1030存储的程序代码，具体用于执行图3至图7、图13、图13A至图13C所示实施例中终端所执行的方法。可以参见图3至图7、图13、图14A至图14C所示实施例所述的方法，本申请在此不再赘述。
本申请实施例中不限定上述收发器1010、处理器1020以及存储器1030之间的具体连接介质。本申请实施例在图10C中以存储器1030、处理器1020以及收发器1010之间通过总线1040连接，总线在图10C中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图10C中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例提供了一种会话管理装置，所述装置应用于第二核心网设备，参见图11A所示，包括：
接收模块1101，用于接收到第一核心网设备发送的消息，所述消息携带待删除的PDU会话的标识，用于指示所述第二核心网设备删除所述标识对应的PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息；
处理模块1102，用于删除所述PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息。
在一种可能的设计中，所述接收模块1101，还用于在所述PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
所述装置还包括：
发送模块1103，用于在所述处理模块1102监控到在所述PDU会话上无数据传输，且持续到所述定时器超时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
在一种可能的设计中，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
在一种可能的设计中，所述接收模块1101，还用于在PDU会话激活时，接收到所述第一核心网设备发送的指示信息，所述指示信息为指示所述无效所述PDU会话的操作的信息。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
如图11B所示，第二核心网设备可以包括处理器1120。上述图11A所示的模块对应的实体的硬件可以为处理器1120。处理器1120，可以是一个中央处理模块(英文：central processing unit，简称CPU)，或者为数字处理模块等等。第二核心网设备还可以包括通信接口1110，处理器1120通过通信接口1110接收数据、消息。该装置还包括：存储器1130，用于存储处理器1120执行的程序。存储器1130可以是非易失性存储器，比如硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)等，还可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)。存储器1130是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
处理器1120用于执行存储器1130存储的程序代码，具体用于执行图3至图7、图13、图13A至图13C所示实施例中第二核心网设备所执行的方法。可以参见图3至图7、图13、图13A至图13C所示实施例所述的方法，本申请在此不再赘述。
本申请实施例中不限定上述通信接口1110、处理器1120以及存储器1130之间的具体连接介质。本申请实施例在图11B中以存储器1130、处理器1120以及通信接口1110之间通过总线1140连接，总线在图11B中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例提供了一种会话管理装置，所述装置应用于第四核心网设备，参见图12A所示，该装置包括：
接收模块1201，用于在小区切换过程中，接收基站发送的PDU会话的标识；
处理模块1202，用于基于所述PDU会话的标识确定需要更新用户面上下文的PDU会话；
发送模块1203，用于向第一核心网设备发送用于通知所述第一核心网设备更新所述PDU会话的用户面上下文的消息。
在一种可能的设计中，所述接收模块1201还用于：
接收到第一核心网设备发送的，且用于指示所述第四核心网设备将所述PDU会话的 状态设置为空闲态或者删除所述PDU会话的消息；
所述处理模块1202，还用于将保存的所述PDU会话的状态设置为空闲态，或者删除所述PDU会话的状态信息。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例提供了一种会话管理装置，所述装置应用于第四核心网设备，参见12C所示，包括
接收模块1201c，用于在终端从源基站切换到目标基站的过程中，接收源基站或者目标基站发送的第二类PDU会话的标识；
其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第二类PDU会话为所述终端的激活的PDU会话中除记录为不活动状态的PDU会话以外的PDU会话，记录为不活动状态的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
发送模块1202c，用于向第一核心网设备发送用于通知所述第一核心网设备更新所述第二类PDU会话的上下文的消息。
在一种可能的设计中，所述接收模块1201c，具体用于接收所述目标基站发送的路径转换消息，所述路径转换消息携带所述第二类PDU会话的标识。
在一种可能的设计中，所述接收模块1201c，具体用于接收所述源基站发送的切换请求，所述切换请求中携带所述第二类PDU会话的标识。
在一种可能的设计中，所述装置还包括：
处理模块1203c，用于基于所述第二类PDU会话的标识确定第一类PDU会话，所述第一类PDU会话为所述第四核心网设备保存的所述终端的激活的PDU会话中除所述标识对应的第二类PDU会话以外的PDU会话；
所述第四核心网设备向所述第一核心网设备发送用于指示执行无效所述第一类PDU会话的操作的消息。
在一种可能的设计中，所述无效所述第一类PDU会话的操作，包括将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，处理模块1203c，还用于在基于所述第一类PDU会话的标识确定第一类PDU会话后，将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
在一种可能的设计中，所述接收模块1201c，还用于接收所述源基站或者目标基站发送的第三类PDU会话的标识，所述第三类PDU会话为所述记录为不活动状态的PDU会话；
所述发送模块1202c，用于向所述第一核心网设备发送用于指示执行无效所述第三类PDU会话的操作的消息。
在一种可能的设计中，所述无效所述第三类PDU会话的操作，包括：
将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
在一种可能的设计中，所述装置还包括：
处理模块1203c，用于在所述接收模块1201c接收所述源基站或者目标基站发送的第三类PDU会话的标识后，将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
在一种可能的设计中，所述发送模块1202c，还用于：在所述接收模块1201c接收所述源基站或者目标基站发送的第三类PDU会话的标识后，将所述第三类PDU会话的标识发送给所述终端，用于指示所述终端将所述第三类PDU会话的状态设置为空闲态。
如图12B所示，第四核心网设备可以包括处理器1220。上述图12A或图12C所示的模块对应的实体的硬件可以为处理器1220。处理器1220，可以是一个中央处理模块(英文：central processing unit，简称CPU)，或者为数字处理模块等等。第四核心网设备还可以包括通信接口1210，处理器1220通过通信接口1210接收数据、消息。该装置还包括：存储器1230，用于存储处理器1220执行的程序。存储器1230可以是非易失性存储器，比如硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)等，还可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)。存储器1230是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
处理器1220用于执行存储器1230存储的程序代码，具体用于执行图3至图7、图13、图14A至图14C所示实施例中第四核心网设备所执行的方法。可以参见图3至图7、图13、图14A至图14C所示实施例所述的方法，本申请在此不再赘述。
本申请实施例中不限定上述通信接口1210、处理器1220以及存储器1230之间的具体连接介质。本申请实施例在图12B中以存储器1230、处理器1220以及通信接口1210之间通过总线1240连接，总线在图12B中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (157)

  1. 一种会话管理方法，其特征在于，包括：
    第一设备接收激活分组数据单元PDU会话的请求消息；
    所述第一设备向第二设备发送所述PDU会话的定时器；
    所述第一设备接收所述第二设备发起的无效所述PDU会话的操作的第一消息；所述第一消息是所述第二设备检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时发出的。
  2. 如权利要求1所述的方法，其特征在于，所述第一设备为第一核心网设备，所述第二设备为第二核心网设备、或者为基站、或者为终端。
  3. 如权利要求1或2所述的方法，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话由激活态转换为空闲态或者删除所述PDU会话。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述第一设备向所述第二设备发送所述定时器之前，所述方法还包括：
    所述第一设备基于所述PDU会话所属的网络切片的切片信息确定所述PDU会话的定时器；或者，
    所述第一设备接收由第三核心网设备发送的所述PDU会话的定时器。
  5. 如权利要求1至4任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备向所述第二设备发送指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
  6. 如权利要求1至5任一项所述的方法，其特征在于，所述方法还包括：
    第一设备接收所述请求消息后，接收由第三核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收到所述第一消息后，基于所述指示信息确定所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态或者为删除所述PDU会话。
  8. 如权利要求1至7任一项所述的方法，其特征在于，所述第一消息中携带所述PDU会话的标识。
  9. 如权利要求8所述的方法，其特征在于，所述第一消息还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
  10. 如权利要求1至9任一项所述的方法，其特征在于，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述方法还包括：
    所述第一设备接收到所述第一消息后，向所述第二核心网设备发送用于指示删除所述PDN会话对应的与基站相关的信息的消息。
  11. 如权利要求1至10任一项所述的方法，其特征在于，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述方法还包括：
    所述第一设备接收到所述第一消息后，将所述PDU会话的状态设置为空闲态。
  12. 如权利要求1至9任一项所述的方法，其特征在于，所述无效所述PDU会话的操作为删除所述PDU会话，所述方法还包括：
    所述第一设备接收到所述第一消息后，向所述第二核心网设备发送用于指示删除与所述PDN会话相关的信息的消息。
  13. 如权利要求1至9、12任一项所述的方法，其特征在于，所述无效所述PDU会话的操作为删除所述PDU会话，所述方法还包括：
    所述第一设备接收到所述第一消息后，向终端发送用于指示所述终端删除与所述PDN会话相关的信息的消息。
  14. 如权利要求1至13任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收到所述第一消息后，向基站发送用于指示基站将所述PDU会话的上下文释放的消息。
  15. 如权利要求1至14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收到所述第一消息后，向第四核心网设备发送用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态的消息。
  16. 如权利要求1至15任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收到第四核心网设备发送的第二消息，所述第二消息携带待更新用户面上下文的PDU会话的标识；
    所述第一设备更新所述PDU会话的标识对应的所述PDU会话的用户面上下文。
  17. 一种会话管理方法，其特征在于，包括：
    在分组数据单元PDU会话激活时，基站接收第一核心网设备发送的所述PDU会话的定时器；
    所述基站检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
  18. 如权利要求17所述的方法，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
  19. 如权利要求17或18所述的方法，其特征在于，所述方法还包括：
    在PDU会话激活时，所述基站接收到所述第一核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
  20. 如权利要求17至19任一项所述的方法，其特征在于，所述第一消息携带所述PDU会话的标识。
  21. 如权利要求20所述的方法，其特征在于，所述第一消息中还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
  22. 如权利要求17至21任一项所述的方法，其特征在于，所述方法还包括：
    所述基站接收到所述第一核心网设备发送的用于指示所述基站将所述PDU的上下文释放的消息；
    所述基站将所述PDU会话对应的无线资源删除或者挂起。
  23. 如权利要求22所述的方法，其特征在于，所述方法还包括：
    所述基站将保存的所述PDU会话的状态设置为空闲态。
  24. 如权利要求17至23任一项所述的方法，其特征在于，所述方法还包括：
    所述基站在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，删除所述PDU会话对应的服务质量QoS流与无线资源承载DRB之间的映射关系。
  25. 如权利要求17至24任一项所述的方法，其特征在于，所述方法还包括：
    所述基站在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，向所述终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。
  26. 如权利要求25所述的方法，其特征在于，所述用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息中携带：待删除或者挂起的无线资源承载DRB的标识。
  27. 一种会话管理方法，其特征在于，包括：
    终端接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息；
    所述终端删除或者挂起所述PDU会话对应的无线资源，并将所述PDU会话的状态设置为空闲态。
  28. 如权利要求27所述的方法，其特征在于，所述方法还包括：
    所述终端接收到所述基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息后，判断所述PDU会话对应的全部无线资源被删除或者挂起时，将所述PDU会话的状态设置为空闲态。
  29. 如权利要求27或28所述的方法，其特征在于，在所述终端接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息之前，所述方法还包括：
    在所述PDU会话激活时，终端接收第一核心网设备发送的所述PDU会话的定时器；
    所述终端监控到在所述PDU会话上无数据传输，且持续到所述定时器超时时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
  30. 如权利要求29所述的方法，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
  31. 如权利要求29或30所述的方法，其特征在于，所述方法还包括：
    在所述PDU会话激活时，所述终端接收所述第一核心网设备发送的第一指示信息，所述第一指示信息为用于指示所述无效所述PDU会话的操作的信息。
  32. 一种会话管理方法，其特征在于，包括：
    第二核心网设备接收到第一核心网设备发送的消息，所述消息携带待删除的PDU会话的标识，用于指示所述第二核心网设备删除所述标识对应的PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息；
    所述第二核心网设备删除所述PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息。
  33. 如权利要求32所述的方法，其特征在于，所述方法还包括：
    在所述PDU会话激活时，第二核心网设备接收第一核心网设备发送的所述PDU会话的定时器；
    所述第二核心网设备监控到在所述PDU会话上无数据传输，且持续到所述定时器超时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
  34. 如权利要求33所述的方法，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
  35. 如权利要求33或34所述的方法，其特征在于，所述方法还包括：
    在PDU会话激活时，所述第二核心网设备接收到所述第一核心网设备发送的指示信息，所述指示信息为指示所述无效所述PDU会话的操作的信息。
  36. 一种会话管理方法，其特征在于，包括：
    在小区切换过程中，第四核心网设备接收基站发送的PDU会话的标识；
    所述第四核心网设备基于所述PDU会话的标识确定需要更新用户面上下文的PDU会 话；
    所述第四核心网设备向第一核心网设备发送用于通知所述第一核心网设备更新所述PDU会话的用户面上下文的消息。
  37. 如权利要求36所述的方法，其特征在于，所述方法还包括：
    所述第四核心网设备接收到第一核心网设备发送的，且用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态或者删除所述PDU会话的消息；
    所述第四核心网设备将保存的所述PDU会话的状态设置为空闲态，或者删除所述PDU会话的状态信息。
  38. 一种会话管理方法，其特征在于，包括：
    终端确定有上行数据到达或者接收到寻呼请求；
    所述终端向网络设备发送请求消息，所述请求消息中携带有PDU会话的标识，和/或携带PDU会话对应的QoS流的第一状态信息，所述第一状态信息指示所述QoS流在所述终端上的状态为激活态或者非激活态，用于所述网络设备与所述终端同步所述QoS流的状态。
  39. 如权利要求38所述的方法，其特征在于，所述终端的无线资源控制RRC状态为RRC非激活连接状态，所述网络设备为基站，所述请求消息用于指示恢复所述终端的RRC连接。
  40. 如权利要求39所述的方法，其特征在于，所述方法还包括：
    所述终端接收所述基站发送的所述PDU会话对应的QoS流的第二状态信息，所述第二状态信息指示所述QoS流在所述基站上的状态为激活态或者非激活态；
    所述终端基于所述第二状态信息与所述基站同步所述PDU会话对应的QoS流的状态。
  41. 如权利要求39或40所述的方法，其特征在于，所述方法还包括：
    所述终端接收所述基站发送的所述PDU会话对应的QoS流与DRB的映射关系；
    所述终端保存所述映射关系。
  42. 如权利要求38所述的方法，其特征在于，所述终端的连接管理CM状态为空闲状态，所述网络设备为第四核心网设备，所述请求消息用于指示将所述终端从CM空闲状态转换为CM连接状态。
  43. 如权利要求42所述的方法，其特征在于，所述方法还包括：
    所述终端接收由所述第一核心网设备发送的所述PDU会话对应的QoS流的第三状态信息，所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态；
    所述终端基于所述第三流状态信息与所述第一核心网设备同步所述PDU会话对应的QoS流的状态。
  44. 一种会话管理方法，其特征在于，包括：
    基站接收所述终端发送的RRC连接恢复消息，所述RRC连接恢复消息中携带参数；
    所述基站根据所述参数确定待激活的PDU会话；
    所述基站触发激活所述PDU会话的流程。
  45. 如权利要求44所述的方法，其特征在于，所述参数为所述待激活的PDU会话的标识，或者所述待激活的PDU会话对应的无线资源承载DRB的标识。
  46. 如权利要求44或45所述的方法，其特征在于，所述待激活的PDU会话的状态 为空闲态。
  47. 如权利要求44至46任一项所述的方法，其特征在于，所述RRC连接恢复消息中还携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述状态信息用于所述基站与所述终端同步所述QoS流的状态。
  48. 如权利要求44至47任一项所述的方法，其特征在于，所述基站触发执行激活所述PDU会话的流程，包括：
    所述基站向第一核心网设备发送用于触发将所述PDU会话转换为激活态的消息。
  49. 如权利要求44至48任一项所述的方法，其特征在于，所述方法还包括：
    所述基站配置所述PDU会话对应的QoS流与DRB之间的映射关系。
  50. 如权利要求49所述的方法，其特征在于，所述方法还包括：
    所述基站将所述映射关系发送给所述终端。
  51. 如权利要求44至50任一项所述的方法，其特征在于，所述方法还包括：
    所述基站将所述PDU会话对应的QoS流的第二状态信息发送给终端，以指示所述终端与基站同步所述QoS的状态。
  52. 如权利要求44至51任一项所述的方法，其特征在于，所述方法还包括：
    基站确定针对终端执行小区切换；
    所述基站向第四核心网设备发送切换请求消息，所述切换请求消息中携带所述终端对应的状态为激活态的PDU会话的标识或者所述切换请求中携带所述终端对应的且在所述基站保存有PDU会话上下文的PDU会话的标识。
  53. 一种会话管理方法，其特征在于，包括：
    第一核心网设备接收终端发送的服务请求消息，所述服务请求消息中携带待激活的PDU会话的标识；
    所述第一核心网设备基于所述服务请求消息执行激活所述PDU会话的流程。
  54. 如权利要求53所述的方法，其特征在于，所述服务请求消息中携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述第一状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态，用于所述第一核心网设备与所述终端同步所述QoS流的状态。
  55. 如权利要求53或54所述的方法，其特征在于，所述方法还包括：
    所述第一核心网设备向所述终端发送的所述PDU会话对应的QoS流的第三状态信息，以指示所述终端与所述第一核心网设备同步所述PDU会话对应的QoS流的状态；所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态。
  56. 一种会话管理装置，其特征在于，所述装置应用于第一设备，包括：
    接收模块，用于接收激活分组数据单元PDU会话的请求消息；
    发送模块，用于向第二设备发送所述PDU会话的定时器；
    所述接收模块，还用于接收所述第二设备发起的无效所述PDU会话的操作的第一消息；所述第一消息是所述第二设备检测到在所述PDU会话上无数据传输，且持续到所述定时器超时时发出的。
  57. 如权利要求56所述的装置，其特征在于，所述第一设备为第一核心网设备，所述第二设备为第二核心网设备、或者为基站、或者为终端。
  58. 如权利要求56或57所述的装置，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话由激活态转换为空闲态或者删除所述PDU会话。
  59. 如权利要求56至58任一项所述的装置，其特征在于，还包括：
    第一确定模块，用于在所述发送模块向所述第二设备发送所述定时器之前，基于所述PDU会话所属的网络切片的切片信息确定所述PDU会话的定时器。
  60. 如权利要求56至59任一项所述的装置，其特征在于，所述接收模块，还用于接收由第三核心网设备发送的所述PDU会话的定时器。
  61. 如权利要求56至60任一项所述的装置，其特征在于，所述发送模块，还用于向所述第二设备发送指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
  62. 如权利要求56至61任一项所述的装置，其特征在于，所述接收模块，还用于在接收所述请求消息后，接收由第三核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
  63. 如权利要求62所述的装置，其特征在于，还包括：第二确定模块，用于在所述接收模块接收到所述第一消息后，基于所述指示信息确定所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态或者为删除所述PDU会话。
  64. 如权利要求56至63任一项所述的装置，其特征在于，所述第一消息中携带所述PDU会话的标识。
  65. 如权利要求64所述的装置，其特征在于，所述第一消息还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
  66. 如权利要求56至65任一项所述的装置，其特征在于，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述接收模块，还用于在接收到所述第一消息后，向所述第二核心网设备发送用于指示删除所述PDN会话对应的与基站相关的信息的消息。
  67. 如权利要求56至66任一项所述的装置，其特征在于，所述无效所述PDU会话的操作为将所述PDU会话由激活态转换为空闲态，所述装置还包括：
    处理模块，用于在接收到所述第一消息后，将所述PDU会话的状态设置为空闲态。
  68. 如权利要求56至65任一项所述的装置，其特征在于，所述无效所述PDU会话的操作为删除所述PDU会话，所述发送模块，还用于在所述接收模块接收到所述第一消息后，向所述第二核心网设备发送用于指示删除与所述PDN会话相关的信息的消息。
  69. 如权利要求56至64、67任一项所述的装置，其特征在于，所述无效所述PDU会话的操作为删除所述PDU会话，所述发送模块，还用于在接收到所述第一消息后，向终端发送用于指示所述终端删除与所述PDN会话相关的信息的消息。
  70. 如权利要求56至69任一项所述的装置，其特征在于，所述发送模块，还用于在所述接收模块接收到所述第一消息后，向基站发送用于指示基站将所述PDU会话的上下文释放的消息。
  71. 如权利要求56至70任一项所述的装置，其特征在于，所述发送模块，还用于在所述接收模块接收到所述第一消息后，向第四核心网设备发送用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态的消息。
  72. 如权利要求56至71任一项所述的装置，其特征在于，所述接收模块，还用于接 收到第四核心网设备发送的第二消息，所述第二消息携带待更新用户面上下文的PDU会话的标识；
    所述装置还包括：
    更新模块，用于更新所述PDU会话的标识对应的所述PDU会话的用户面上下文。
  73. 一种会话管理装置，其特征在于，所述装置应用于基站，包括：
    接收模块，用于在分组数据单元PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
    处理模块，用于检测到在所述PDU会话上无数据传输，且持续到所述定时器超时；
    所述发送模块，用于向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
  74. 如权利要求73所述的装置，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
  75. 如权利要求73或74所述的装置，其特征在于，所述接收模块，还用于在PDU会话激活时，接收到所述第一核心网设备发送的指示信息，所述指示信息为用于指示所述无效所述PDU会话的操作的信息。
  76. 如权利要求73至75任一项所述的装置，其特征在于，所述第一消息携带所述PDU会话的标识。
  77. 如权利要求76所述的装置，其特征在于，所述第一消息中还携带原因值，所述原因值用于指示所述PDU会话的定时器超时。
  78. 如权利要求73至77任一项所述的装置，其特征在于，所述接收模块，还用于接收到所述第一核心网设备发送的用于指示所述基站将所述PDU的上下文释放的消息；
    所述处理模块，还用于将所述PDU会话对应的无线资源删除或者挂起。
  79. 如权利要求78所述的装置，其特征在于，所述处理模块，还用于：
    将保存的所述PDU会话的状态设置为空闲态。
  80. 如权利要求73至79任一项所述的装置，其特征在于，所述处理模块，还用于在监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，删除所述PDU会话对应的服务质量QoS流与无线资源承载DRB之间的映射关系。
  81. 如权利要求73至80任一项所述的装置，其特征在于，所述发送模块，还用于在所述处理模块监控到在所述PDU会话上无数据传输，且持续到所述定时器超时后，向所述终端发送用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息。
  82. 如权利要求81所述的装置，其特征在于，所述用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息中携带：待删除或者挂起的无线资源承载DRB的标识。
  83. 一种会话管理装置，其特征在于，所述装置应用于终端，包括：
    接收模块，用于接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息；
    处理模块，用于删除或者挂起所述PDU会话对应的无线资源，并将所述PDU会话的状态设置为空闲态。
  84. 如权利要求83所述的装置，其特征在于，所述处理模块，还用于在所述接收模块接收到所述基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息后，判断所述PDU会话对应的全部无线资源被删除或者挂起时，将所述PDU会话的状 态设置为空闲态。
  85. 如权利要求83或84所述的装置，其特征在于，所述接收模块，还用于在接收基站发送的用于指示所述终端删除或者挂起PDU会话对应的无线资源的消息之前，在所述PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
    所述装置还包括：
    发送模块，还用于在所述处理模块监控到在所述PDU会话上无数据传输，且持续到所述定时器超时时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
  86. 如权利要求85所述的装置，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
  87. 如权利要求85或86所述的装置，其特征在于，所述接收模块，还用于在所述PDU会话激活时，接收所述第一核心网设备发送的第一指示信息，所述第一指示信息为用于指示所述无效所述PDU会话的操作的信息。
  88. 一种会话管理装置，其特征在于，所述装置应用于第二核心网设备，包括：
    接收模块，用于接收到第一核心网设备发送的消息，所述消息携带待删除的PDU会话的标识，用于指示所述第二核心网设备删除所述标识对应的PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息；
    处理模块，用于删除所述PDU会话对应的与基站相关的信息或者删除与所述PDU会话相关的信息。
  89. 如权利要求88所述的装置，其特征在于，所述接收模块，还用于在所述PDU会话激活时，接收第一核心网设备发送的所述PDU会话的定时器；
    所述装置还包括：
    发送模块，用于在所述处理模块监控到在所述PDU会话上无数据传输，且持续到所述定时器超时，向所述第一核心网设备发送无效所述PDU会话的操作的第一消息。
  90. 如权利要求89所述的装置，其特征在于，所述无效所述PDU会话的操作包括：将所述PDU会话的状态由激活态转换为空闲态或者删除所述PDU会话。
  91. 如权利要求89或90所述的装置，其特征在于，所述接收模块，还用于在PDU会话激活时，接收到所述第一核心网设备发送的指示信息，所述指示信息为指示所述无效所述PDU会话的操作的信息。
  92. 一种会话管理装置，其特征在于，所述装置应用于第四核心网设备，包括：
    接收模块，用于在小区切换过程中，接收基站发送的PDU会话的标识；
    处理模块，用于基于所述PDU会话的标识确定需要更新用户面上下文的PDU会话；
    发送模块，用于向第一核心网设备发送用于通知所述第一核心网设备更新所述PDU会话的用户面上下文的消息。
  93. 如权利要求92所述的装置，其特征在于，所述接收模块还用于：
    接收到第一核心网设备发送的，且用于指示所述第四核心网设备将所述PDU会话的状态设置为空闲态或者删除所述PDU会话的消息；
    所述处理模块，还用于将保存的所述PDU会话的状态设置为空闲态，或者删除所述PDU会话的状态信息。
  94. 一种会话管理装置，其特征在于，所述装置应用于终端，包括：
    接收模块，用于接收上行数据或者接收寻呼请求；
    处理模块，用于确定接收模块接收到上行数据到达或者接收到寻呼请求；
    发送模块，用于向网络设备发送请求消息，所述请求消息中携带有PDU会话的标识，和/或携带PDU会话对应的QoS流的第一状态信息，所述第一状态信息指示所述QoS流在所述终端上的状态为激活态或者非激活态，用于所述网络设备与所述终端同步所述QoS流的状态。
  95. 如权利要求94所述的装置，其特征在于，所述终端的无线资源控制RRC状态为RRC非激活连接状态，所述网络设备为基站，所述请求消息用于指示恢复所述终端的RRC连接。
  96. 如权利要求95所述的装置，其特征在于，所述接收模块，还用于接收所述基站发送的所述PDU会话对应的QoS流的第二状态信息，所述第二状态信息指示所述QoS流在所述基站上的状态为激活态或者非激活态；
    所述处理模块，还用于基于所述第二状态信息与所述基站同步所述PDU会话对应的QoS流的状态。
  97. 如权利要求95或96所述的装置，其特征在于，所述接收模块，还用于接收所述基站发送的所述PDU会话对应的QoS流与DRB的映射关系；
    所述处理模块，还用于保存所述映射关系。
  98. 如权利要求94所述的装置，其特征在于，所述终端的连接管理CM状态为空闲状态，所述网络设备为第四核心网设备，所述请求消息用于指示将所述终端从CM空闲状态转换为CM连接状态。
  99. 如权利要求98所述的装置，其特征在于，所述接收模块，还用于接收由所述第一核心网设备发送的所述PDU会话对应的QoS流的第三状态信息，所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态；
    所述处理模块，还用于基于所述第三流状态信息与所述第一核心网设备同步所述PDU会话对应的QoS流的状态。
  100. 一种会话管理装置，其特征在于，所述装置应用于基站，包括：
    接收模块，用于接收所述终端发送的RRC连接恢复消息，所述RRC连接恢复消息中携带参数；
    处理模块，用于根据所述参数确定待激活的PDU会话；并触发激活所述PDU会话的流程。
  101. 根据权利要求100所述的装置，其特征在于，所述参数为所述待激活的PDU会话的标识，或者所述待激活的PDU会话对应的无线资源承载DRB的标识。
  102. 如权利要求100或101所述的装置，其特征在于，所述待激活的PDU会话的状态为空闲态。
  103. 如权利要求100至102任一项所述的装置，其特征在于，所述RRC连接恢复消息中还携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述状态信息用于所述基站与所述终端同步所述QoS流的状态。
  104. 如权利要求100至103任一项所述的装置，其特征在于，所述装置还包括：
    发送模块，用于向第一核心网设备发送用于触发将所述PDU会话转换为激活态的消息。
  105. 如权利要求100至104任一项所述的装置，其特征在于，所述处理模块，还用 于配置所述PDU会话对应的QoS流与DRB之间的映射关系。
  106. 如权利要求105所述的装置，其特征在于，还包括：
    发送模块，还用于将所述映射关系发送给所述终端。
  107. 如权利要求100至106任一项所述的装置，其特征在于，所述装置还包括：
    发送模块，用于将所述PDU会话对应的QoS流的第二状态信息发送给终端，以指示所述终端与基站同步所述QoS的状态。
  108. 如权利要求100至107任一项所述的装置，其特征在于，所述处理模块，还用于确定针对终端执行小区切换；
    发送模块，用于向第四核心网设备发送切换请求消息，所述切换请求消息中携带所述终端对应的状态为激活态的PDU会话的标识或者所述切换请求中携带所述终端对应的且在所述基站保存有PDU会话上下文的PDU会话的标识。
  109. 一种会话管理装置，其特征在于，所述装置应用于第一核心网设备，包括：
    接收模块，用于接收终端发送的服务请求消息，所述服务请求消息中携带待激活的PDU会话的标识；
    处理模块，用于基于所述服务请求消息执行激活所述PDU会话的流程。
  110. 如权利要求109所述的装置，其特征在于，所述服务请求消息中携带所述PDU会话对应的服务质量QoS流的第一状态信息；所述第一状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态，用于所述第一核心网设备与所述终端同步所述QoS流的状态。
  111. 如权利要求109或110所述的装置，其特征在于，所述装置还包括：
    发送模块，用于向所述终端发送的所述PDU会话对应的QoS流的第三状态信息，以指示所述终端与所述第一核心网设备同步所述PDU会话对应的QoS流的状态；所述第三状态信息指示所述PDU会话对应的QoS流在所述第一核心网设备上的状态为激活态或者非激活态。
  112. 一种会话管理方法，其特征在于，包括：
    在终端的PDU会话建立或者激活时，所述终端当前接入的源基站接收第一核心网设备发送的所述PDU会话的定时器；若所述源基站检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态；
    所述源基站在确定针对所述终端执行从所述源基站切换到目标基站时，确定所述终端的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
  113. 如权利要求112所述的方法，其特征在于，所述源基站针对第二类PDU会话执行切换流程，包括：
    所述源基站向所述目标基站发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
  114. 如权利要求112或者113所述的方法，其特征在于，所述方法还包括：
    在针对第二类PDU会话执行切换的过程中，所述源基站向所述终端发送用于指示所述终端执行无效所述第一类PDU会话的操作的消息。
  115. 如权利要求114所述的方法，其特征在于，所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述第一类PDU会话的标识；或者，
    所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标识所述终端的激活的PDU会话中的第一类PDU会话。
  116. 如权利要求114或115所述的方法，其特征在于，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  117. 如权利要求112所述的方法，其特征在于，所述源基站针对第二类PDU会话执行切换流程，包括：
    所述源基站向第四核心网设备发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
  118. 一种会话管理方法，其特征在于，包括：
    终端待切入的目标基站接收所述终端当前接入的源基站发送的切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话的标识中的第一类PDU会话；
    其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；所述第二类PDU会话为所述终端的激活的PDU会话中除所述第一类DPU会话以外的PDU会话；
    所述目标基站向第四核心网设备发送用于指示所述第四核心网设备执行无效所述第第一类PDU会话的操作的消息。
  119. 如权利要求118所述的方法，其特征在于，所述用于指示所述第四核心网设备执行无效所述第二类PDU会话的操作的消息中携带：所述第一类PDU会话的标识。
  120. 如权利要求118或119所述的方法，其特征在于，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  121. 一种会话管理方法，其特征在于，包括：
    在终端从源基站切换到目标基站的过程中，第四核心网设备接收源基站或者目标基站发送的第二类PDU会话的标识；
    其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定 时器；所述第二类PDU会话为所述终端的激活的PDU会话中除记录为不活动状态的PDU会话以外的PDU会话，记录为不活动状态的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
    所述第四核心网设备向第一核心网设备发送用于通知所述第一核心网设备更新所述第二类PDU会话的上下文的消息。
  122. 如权利要求121所述的方法，其特征在于，第四核心网设备接收目标基站发送的所述第二类PDU会话的标识，包括：
    所述第四核心网设备接收所述目标基站发送的路径转换消息，所述路径转换消息携带所述第二类PDU会话的标识。
  123. 如权利要求121所述的方法，其特征在于，所述第四核心网设备接收源基站发送的第二类PDU会话的标识，包括：
    所述第四核心网设备接收所述源基站发送的切换请求，所述切换请求中携带所述第二类PDU会话的标识。
  124. 如权利要求121至123任一项所述的方法，其特征在于，所述方法还包括：
    所述第四核心网设备基于所述第二类PDU会话的标识确定第一类PDU会话，所述第一类PDU会话为所述第四核心网设备保存的所述终端的激活的PDU会话中除所述标识对应的第二类PDU会话以外的PDU会话；
    所述第四核心网设备向所述第一核心网设备发送用于指示执行无效所述第一类PDU会话的操作的消息。
  125. 如权利要求124所述的方法，其特征在于，所述无效所述第一类PDU会话的操作，包括将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  126. 如权利要求124或125所述的方法，其特征在于，所述第四核心网设备基于所述第一类PDU会话的标识确定第一类PDU会话后，所述方法还包括：
    所述第四核心网设备将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  127. 如权利要求121至123任一项所述的方法，其特征在于，所述方法还包括：
    所述第四核心网设备接收所述源基站或者所述目标基站发送的第三类PDU会话的标识，所述第三类PDU会话为所述记录为不活动状态的PDU会话；
    所述第四核心网设备向所述第一核心网设备发送用于指示执行无效所述第三类PDU会话的操作的消息。
  128. 如权利要求127所述的方法，其特征在于，所述无效所述第三类PDU会话的操作，包括：
    将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
  129. 如权利要求127或128所述的方法，其特征在于，所述第四核心网设备接收所述源基站或者所述目标基站发送的第三类PDU会话的标识后，所述方法还包括：
    所述第四核心网设备将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
  130. 如权利要求127至129任一项所述的方法，其特征在于，所述第四核心网设备接收所述源基站或者目标基站发送的第三类PDU会话的标识后，所述方法还包括：
    所述第四核心网设备将所述第三类PDU会话的标识发送给所述终端，用于指示所述终端将所述第三类PDU会话的状态设置为空闲态。
  131. 一种会话管理方法，其特征在于，包括：
    在终端从当前接入的源基站切换到目标基站的过程中，所述终端接收到所述源基站或者第四核心网设备发送的用于指示执行无效第一类分组数据单元PDU会话的操作的消息；
    其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
    所述终端基于所述消息执行无效所述第一类PDU会话的操作。
  132. 如权利要求131所述的方法，其特征在于，所述用于指示所述终端执行无效第一类分组数据单元PDU会话的操作的消息中携带：第一类PDU会话的标识。
  133. 如权利要求131所述的方法，其特征在于，所述用于指示执行无效第一类分组数据单元PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话；
    所述终端基于所述消息执行无效所述第一类PDU会话的操作，包括：
    所述终端根据所述第一指示确定所述终端的激活的PDU会话中的第一类PDU会话，并执行无效所述第一类PDU会话的操作。
  134. 如权利要求131至133任一项所述的方法，其特征在于，所述无效所述第一类PDU会话的操作，包括：
    将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  135. 一种会话管理装置，其特征在于，所述装置应用于源基站，包括：
    接收模块，用于在终端的PDU会话建立或者激活时，接收第一核心网设备发送的所述PDU会话的定时器；若所述源基站检测到在所述PDU会话上无数据传输持续到所述定时器超时，则将所述PDU会话的状态记录为不活动状态；
    处理模块，用于在确定针对所述终端执行从所述源基站切换到目标基站时，确定所述终端的激活的PDU会话中包括的第一类PDU会话，所述第一类PDU会话为记录为不活动状态的PDU会话，针对第二类PDU会话执行切换流程，所述第二类PDU会话为所述终端的PDU会话中除所述第一类会话以外的PDU会话。
  136. 如权利要求135所述的装置，其特征在于，还包括：
    发送模块，用于在所述处理模块针对第二类PDU会话向所述目标基站发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
  137. 如权利要求135或者136所述的装置，其特征在于，还包括：
    发送模块，用于在针对第二类PDU会话执行切换的过程中，向所述终端发送用于指示所述终端执行无效所述第一类PDU会话的操作的消息。
  138. 如权利要求137所述的装置，其特征在于，所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述第一类PDU会话的标识；或者，
    所述用于指示所述终端执行无效所述第一类PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标识所述终端的激活的PDU会话中的第一类PDU会话。
  139. 如权利要求138或137所述的装置，其特征在于，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  140. 如权利要求135所述的装置，其特征在于，还包括：
    所述发送模块，用于在所述处理模块针对第二类PDU会话执行切换流程时，向第四核心网设备发送切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，
    所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话。
  141. 一种会话管理装置，其特征在于，所述装置应用目标基站，包括：
    接收模块，接收终端当前接入的源基站发送的切换请求，所述切换请求中仅携带所述第二类PDU会话的标识；或者，所述切换请求中携带所述第一类PDU会话的标识以及所述第二类PDU会话的标识；或者，所述切换请求中携带所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话的标识中的第一类PDU会话；
    其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；所述第二类PDU会话为所述终端的激活的PDU会话中除所述第一类PDU会话以外的PDU会话；
    发送模块，用于向第四核心网设备发送用于指示所述第四核心网设备执行无效所述第第一类PDU会话的操作的消息。
  142. 如权利要求141所述的装置，其特征在于，所述用于指示所述第四核心网设备执行无效所述第二类PDU会话的操作的消息中携带：所述第一类PDU会话的标识。
  143. 如权利要求141或142所述的装置，其特征在于，所述无效所述第一类PDU会话的操作包括：将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  144. 一种会话管理装置，其特征在于，所述装置应用于第四核心网设备，包括：
    接收模块，用于在终端从源基站切换到目标基站的过程中，接收源基站或者目标基站发送的第二类PDU会话的标识；
    其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第二类PDU会话为所述终端的激活的PDU会话中除记录为不活动状态的PDU会话以外的PDU会话，记录为不活动状态的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
    发送模块，用于向第一核心网设备发送用于通知所述第一核心网设备更新所述第二类PDU会话的上下文的消息。
  145. 如权利要求144所述的装置，其特征在于，所述接收模块，具体用于接收所述 目标基站发送的路径转换消息，所述路径转换消息携带所述第二类PDU会话的标识。
  146. 如权利要求144所述的装置，其特征在于，所述接收模块，具体用于接收所述源基站发送的切换请求，所述切换请求中携带所述第二类PDU会话的标识。
  147. 如权利要求144至146任一项所述的装置，其特征在于，所述装置还包括：
    处理模块，用于基于所述第二类PDU会话的标识确定第一类PDU会话，所述第一类PDU会话为所述第四核心网设备保存的所述终端的激活的PDU会话中除所述标识对应的第二类PDU会话以外的PDU会话；
    所述第四核心网设备向所述第一核心网设备发送用于指示执行无效所述第一类PDU会话的操作的消息。
  148. 如权利要求147所述的装置，其特征在于，所述无效所述第一类PDU会话的操作，包括将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  149. 如权利要求147或148所述的装置，其特征在于，处理模块，还用于在基于所述第一类PDU会话的标识确定第一类PDU会话后，将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
  150. 如权利要求144至146任一项所述的装置，其特征在于，所述接收模块，还用于接收所述源基站或者目标基站发送的第三类PDU会话的标识，所述第三类PDU会话为所述记录为不活动状态的PDU会话；
    所述发送模块，用于向所述第一核心网设备发送用于指示执行无效所述第三类PDU会话的操作的消息。
  151. 如权利要求150所述的装置，其特征在于，所述无效所述第三类PDU会话的操作，包括：
    将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
  152. 如权利要求151或152所述的装置，其特征在于，所述装置还包括：
    处理模块，用于在所述接收模块接收所述源基站或者目标基站发送的第三类PDU会话的标识后，将所述第三类PDU会话的状态由激活态转换为空闲态或者删除所述第三类PDU会话。
  153. 如权利要求150至152任一项所述的装置，其特征在于，所述发送模块，还用于：在所述接收模块接收所述源基站或者目标基站发送的第三类PDU会话的标识后，将所述第三类PDU会话的标识发送给所述终端，用于指示所述终端将所述第三类PDU会话的状态设置为空闲态。
  154. 一种会话管理装置，其特征在于，所述装置应用于终端包括：
    接收模块，用于在终端从当前接入的源基站切换到目标基站的过程中，接收到所述源基站或者第四核心网设备发送的用于指示执行无效第一类分组数据单元PDU会话的操作的消息；
    其中，所述终端的每一激活的PDU会话在建立或者激活时分别被配置一个相应的定时器；所述第一类PDU会话为记录为不活动状态的PDU会话；所述记录为不活动的PDU会话是指满足无数据传输持续到相应的定时器超时的PDU会话；
    处理模块，用于基于所述消息执行无效所述第一类PDU会话的操作。
  155. 如权利要求154所述的装置，其特征在于，所述用于指示所述终端执行无效第 一类分组数据单元PDU会话的操作的消息中携带：第一类PDU会话的标识。
  156. 如权利要求154所述的装置，其特征在于，所述用于指示执行无效第一类分组数据单元PDU会话的操作的消息中携带：所述终端的激活的PDU会话的标识以及第一指示，所述第一指示用于标记所述终端的激活的PDU会话中的第一类PDU会话；
    所述终端基于所述消息执行无效所述第一类PDU会话的操作，包括：
    所述终端根据所述第一指示确定所述终端的激活的PDU会话中的第一类PDU会话，并执行无效所述第一类PDU会话的操作。
  157. 如权利要求154至156任一项所述的装置，其特征在于，所述无效所述第一类PDU会话的操作，包括：
    将所述第一类PDU会话的状态由激活态转换为空闲态或者删除所述第一类PDU会话。
PCT/CN2017/077363 2017-01-09 2017-03-20 一种会话管理方法及装置 WO2018126535A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110530649.4A CN113784418B (zh) 2017-01-09 2017-03-20 一种会话管理方法及装置
CN201780009886.8A CN108605269B (zh) 2017-01-09 2017-03-20 一种会话管理方法及装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2017/070684 2017-01-09
CN2017070684 2017-01-09

Publications (1)

Publication Number Publication Date
WO2018126535A1 true WO2018126535A1 (zh) 2018-07-12

Family

ID=62788869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077363 WO2018126535A1 (zh) 2017-01-09 2017-03-20 一种会话管理方法及装置

Country Status (2)

Country Link
CN (3) CN113784418B (zh)
WO (1) WO2018126535A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111225401A (zh) * 2018-11-23 2020-06-02 中兴通讯股份有限公司 一种实现容灾的方法及相关设备
CN112913283A (zh) * 2018-08-24 2021-06-04 诺基亚技术有限公司 配置路由选择策略
CN112956277A (zh) * 2018-11-16 2021-06-11 夏普株式会社 用户装置、控制装置以及通信控制方法
US20210377807A1 (en) * 2017-10-31 2021-12-02 Sk Telecom Co., Ltd. Data transmission/reception apparatus and operation method for data transmission/reception apparatus
WO2021254238A1 (zh) * 2020-06-15 2021-12-23 华为技术有限公司 一种通信方法及装置
CN113973266A (zh) * 2020-07-23 2022-01-25 维沃移动通信有限公司 信息接收方法、发送方法、会话建立方法、装置和设备
CN114071787A (zh) * 2020-07-31 2022-02-18 维沃移动通信有限公司 建立连接的方法、装置及设备
CN114071658A (zh) * 2020-07-29 2022-02-18 大唐移动通信设备有限公司 一种终端设备的注册方法及装置

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11212720B2 (en) * 2018-10-16 2021-12-28 Mediatek Inc. 5GSM handling on invalid PDU session
CN111935853B (zh) 2018-10-31 2022-03-11 Oppo广东移动通信有限公司 协议数据单元会话状态指示方法、终端设备及存储介质
US11399308B2 (en) 2018-11-12 2022-07-26 Mediatek Inc. Error handling on missing configuration for inter-system change in mobile communications
US11159976B2 (en) 2018-11-19 2021-10-26 Mediatek Inc. Handling of mapped EPS bearer context for invalid QoS flow description
CN111586774B (zh) * 2019-02-19 2021-06-29 华为技术有限公司 通信方法和通信装置
US11134371B2 (en) 2019-02-19 2021-09-28 Huawei Technologies Co., Ltd. Communication method and communications apparatus
CN113825181B (zh) * 2020-06-18 2023-08-15 中国移动通信有限公司研究院 切片管理方法、装置、接入网设备及核心网设备
CN112770412B (zh) * 2020-12-29 2022-09-02 紫光展锐(重庆)科技有限公司 一种分组数据网pdn激活方法及其装置
CN113573344B (zh) * 2021-06-21 2024-06-18 深圳震有科技股份有限公司 一种基于5g的smf会话检测方法及终端
WO2023120046A1 (en) 2021-12-22 2023-06-29 Nec Corporation Method of communication apparatus, method of user equipment (ue), communication apparatus, ue, method for first core network apparatus, method for third core network apparatus and method for first network slice control function node
CN115150870B (zh) * 2022-06-30 2023-03-21 广州爱浦路网络技术有限公司 会话残留处理方法、装置、会话管理功能实体及存储介质
CN117676923B (zh) * 2024-01-31 2024-04-02 成都爱瑞无线科技有限公司 用于通信系统中会话建立的管理方法、装置及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104853372A (zh) * 2014-02-17 2015-08-19 中兴通讯股份有限公司 一种减少ue释放次数的方法、装置及基站
CN106304248A (zh) * 2015-05-15 2017-01-04 上海贝尔股份有限公司 设置激活/去激活媒体接入控制控制单元的方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572955B (zh) * 2008-04-29 2011-10-05 电信科学技术研究院 一种删除承载的方法与装置
CN101895986A (zh) * 2009-05-21 2010-11-24 中兴通讯股份有限公司 本地ip接入中实现寻呼的方法及系统
KR101479895B1 (ko) * 2011-04-29 2015-01-06 엘지전자 주식회사 세션 관리 및 이동성 관리에 관련된 데이터를 처리하는 방법
CN105101293A (zh) * 2014-04-30 2015-11-25 夏普株式会社 Pdcp发送实体、辅基站、用户设备及其方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104853372A (zh) * 2014-02-17 2015-08-19 中兴通讯股份有限公司 一种减少ue释放次数的方法、装置及基站
CN106304248A (zh) * 2015-05-15 2017-01-04 上海贝尔股份有限公司 设置激活/去激活媒体接入控制控制单元的方法和装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Study on Architecture for Next Generation System (Release 14)", 3 GPP TR23.799 V14.0.0., 31 December 2016 (2016-12-31), XP055514501 *
NEC: "Updates to Solution 4.22", 3GPP SA WG2 , S2-166727, vol. 8, 18 November 2016 (2016-11-18), pages 2 - 118, XP051185277 *
NTT DOCOMO ET AL.: "Selective Deactivation of User Plane Connections", SA WG2 MEETING #119, S2-171171, 17 February 2017 (2017-02-17), pages 2 - 171171, XP051217285 *

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210377807A1 (en) * 2017-10-31 2021-12-02 Sk Telecom Co., Ltd. Data transmission/reception apparatus and operation method for data transmission/reception apparatus
US11963044B2 (en) * 2017-10-31 2024-04-16 Sk Telecom Co., Ltd. Data transmission/reception apparatus and operation method for data transmission/reception apparatus
CN112913283A (zh) * 2018-08-24 2021-06-04 诺基亚技术有限公司 配置路由选择策略
CN112956277A (zh) * 2018-11-16 2021-06-11 夏普株式会社 用户装置、控制装置以及通信控制方法
US11963240B2 (en) 2018-11-16 2024-04-16 Sharp Kabushiki Kaisha User device, control device, and communication control method
US11889330B2 (en) 2018-11-23 2024-01-30 Zte Corporation Methods and related devices for implementing disaster recovery
CN111225401B (zh) * 2018-11-23 2022-12-20 中兴通讯股份有限公司 一种实现容灾的方法及相关设备
CN111225401A (zh) * 2018-11-23 2020-06-02 中兴通讯股份有限公司 一种实现容灾的方法及相关设备
WO2021254238A1 (zh) * 2020-06-15 2021-12-23 华为技术有限公司 一种通信方法及装置
CN113973266A (zh) * 2020-07-23 2022-01-25 维沃移动通信有限公司 信息接收方法、发送方法、会话建立方法、装置和设备
CN113973266B (zh) * 2020-07-23 2023-12-19 维沃移动通信有限公司 信息接收方法、发送方法、会话建立方法、装置和设备
CN114071658B (zh) * 2020-07-29 2023-09-01 大唐移动通信设备有限公司 一种终端设备的注册方法及装置
CN114071658A (zh) * 2020-07-29 2022-02-18 大唐移动通信设备有限公司 一种终端设备的注册方法及装置
CN114071787A (zh) * 2020-07-31 2022-02-18 维沃移动通信有限公司 建立连接的方法、装置及设备

Also Published As

Publication number Publication date
CN113784418A (zh) 2021-12-10
CN108605269B (zh) 2021-05-18
CN113784417A (zh) 2021-12-10
CN108605269A (zh) 2018-09-28
CN113784418B (zh) 2022-11-18

Similar Documents

Publication Publication Date Title
WO2018126535A1 (zh) 一种会话管理方法及装置
US12349224B2 (en) UE behavior with rejection of resume request
KR102293232B1 (ko) 연결 재활성화 방법, 액세스 및 이동성 관리 기능 엔티티, 그리고 사용자 장비
CN109936878A (zh) 一种触发状态恢复的方法以及终端设备
CN109819485B (zh) 一种通信方法、装置及系统
WO2019137286A1 (zh) 一种本地数据网络的指示方法及装置
JP7104143B2 (ja) 通信方法および通信装置
CN110268760A (zh) 支持接入控制和移动性管理的方法和装置
WO2020034791A1 (zh) 一种持续在线pdu会话的管理方法及装置
JP7125041B2 (ja) 通信方法及び通信装置
EP3799514B1 (en) Rate control methods, devices, computer program and system
KR20180100381A (ko) 무선 단말, 무선국, 및 이들의 방법
CN109479253A (zh) 用于非活动用户设备的无线电接入网络中的ue上下文的存储的方法和设备
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2020001257A1 (zh) 一种数据传输方法及装置
JP2020524451A (ja) 通信方法および通信装置
JP7507144B2 (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
CN113473564B (zh) 网络切片切换的方法、建立pdu会话的方法及装置
EP3577998A1 (en) Control of radio technology usage by scheduling restriction
WO2016119267A1 (zh) 一种用户设备迁移方法、核心网设备、接入网设备及系统
WO2020034802A1 (zh) 一种激活pdu会话的方法及设备
WO2019219055A1 (zh) 一种信息指示方法及装置、计算机存储介质
WO2018130053A1 (zh) 一种流程冲突处理方法及装置
GB2591499A (en) Informing changes in coverage enhancement usage
WO2018001301A1 (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: 17889605

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17889605

Country of ref document: EP

Kind code of ref document: A1