[go: up one dir, main page]

WO2018126535A1 - Procédé et appareil de gestion de session - Google Patents

Procédé et appareil de gestion de session 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)
Chinese (zh)
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/fr

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

L'invention concerne un procédé et un appareil de gestion de session, qui sont utilisés pour convertir une session PDU d'un état activé à un état inactif. Le procédé comprend les étapes suivantes : un premier dispositif reçoit un message de demande d'activation d'une session PDU ; le premier dispositif envoie un temporisateur de la session PDU à un second dispositif ; le premier dispositif reçoit un premier message, initié par le second dispositif, d'une opération de désactivation de la session PDU, le premier message étant envoyé lorsque le second dispositif détecte qu'aucune donnée n'est transmise sur la session PDU et que cette situation perdure jusqu'à ce que le temporisateur expire. L'opération de désactivation de la session PDU peut comprendre la conversion de la session PDU d'un état activé à un état inactif, ou la suppression de la session PDU.
PCT/CN2017/077363 2017-01-09 2017-03-20 Procédé et appareil de gestion de session WO2018126535A1 (fr)

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 (fr) 2018-07-12

Family

ID=62788869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077363 WO2018126535A1 (fr) 2017-01-09 2017-03-20 Procédé et appareil de gestion de session

Country Status (2)

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

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 (fr) * 2020-06-15 2021-12-23 华为技术有限公司 Procédé et appareil de communication
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 (fr) 2021-12-22 2023-06-29 Nec Corporation Procédé d'appareil de communication, procédé d'équipement utilisateur (ue), appareil de communication, ue, procédé pour un premier appareil de réseau central, procédé pour un troisième appareil de réseau central et procédé pour un premier nœud de fonction de commande de tranche de réseau
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 (fr) * 2020-06-15 2021-12-23 华为技术有限公司 Procédé et appareil de communication
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 (fr) Procédé et appareil de gestion de session
US12349224B2 (en) UE behavior with rejection of resume request
KR102293232B1 (ko) 연결 재활성화 방법, 액세스 및 이동성 관리 기능 엔티티, 그리고 사용자 장비
CN109936878A (zh) 一种触发状态恢复的方法以及终端设备
CN109819485B (zh) 一种通信方法、装置及系统
WO2019137286A1 (fr) Procédé et appareil d'indication pour un réseau de données local
JP7104143B2 (ja) 通信方法および通信装置
CN110268760A (zh) 支持接入控制和移动性管理的方法和装置
WO2020034791A1 (fr) Procédé et dispositif de gestion de session de pdu en activité permanente
JP7125041B2 (ja) 通信方法及び通信装置
EP3799514B1 (fr) Procédés, dispositifs, programme informatique et système de régulation de débit
KR20180100381A (ko) 무선 단말, 무선국, 및 이들의 방법
CN109479253A (zh) 用于非活动用户设备的无线电接入网络中的ue上下文的存储的方法和设备
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2020001257A1 (fr) Procédé et dispositif de transmission de données
JP2020524451A (ja) 通信方法および通信装置
JP7507144B2 (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
CN113473564B (zh) 网络切片切换的方法、建立pdu会话的方法及装置
EP3577998A1 (fr) Commande d'utilisation de technologie radio par restriction d'ordonnancement
WO2016119267A1 (fr) Procédé de transition d'équipement utilisateur, dispositif de réseau principal, dispositif de réseau d'accès et système
WO2020034802A1 (fr) Procédé et dispositif d'activation de session pdu
WO2019219055A1 (fr) Procédé et dispositif d'indication d'informations, et support dde stockage informatique
WO2018130053A1 (fr) Procédé et dispositif de traitement de conflit de flux
GB2591499A (en) Informing changes in coverage enhancement usage
WO2018001301A1 (fr) Procédé, appareil et système de commande d'équipement d'utilisateur, et passerelle de réseau

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