WO2021147672A1 - 会话处理方法及通信装置 - Google Patents

会话处理方法及通信装置 Download PDF

Info

Publication number
WO2021147672A1
WO2021147672A1 PCT/CN2021/070442 CN2021070442W WO2021147672A1 WO 2021147672 A1 WO2021147672 A1 WO 2021147672A1 CN 2021070442 W CN2021070442 W CN 2021070442W WO 2021147672 A1 WO2021147672 A1 WO 2021147672A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
user plane
plane connection
terminal device
network element
Prior art date
Application number
PCT/CN2021/070442
Other languages
English (en)
French (fr)
Inventor
张成晨
舒林
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21744634.3A priority Critical patent/EP4075859A4/en
Publication of WO2021147672A1 publication Critical patent/WO2021147672A1/zh
Priority to US17/814,320 priority patent/US20220361286A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H04W36/28—Reselection being triggered by specific parameters by agreed or negotiated communication parameters involving a plurality of connections, e.g. multi-call or multi-bearer connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of communication technology, and in particular to a session processing method and communication device.
  • NB-IoT Narrow Band Internet of Things
  • NB-IoT is a low-power and wide-coverage network wireless technology standard.
  • NB-IoT has the advantages of low power consumption, wide coverage, low cost, and large capacity, and can be widely used In a variety of vertical industries.
  • terminal devices that access NB-IoT allow up to a certain number of sessions to have active user plane connections (User Plane connection, UP connection).
  • the activated user plane connection refers to the access network and the user plane core network element.
  • the various user plane resources established by the session are used to realize the transmission of user data through the established user resources.
  • the activated user plane connection includes various user plane resources established for the session such as Radio Access Network (RAN) and User Plane Function (UPF), including but not limited to RAN for the session For the established Data Radio Bearer (DRB), RAN and UPF are the N3 tunnels established for the session.
  • the activated user plane connection also includes the N3 interworking function network element (Non-3GPP InterWorking Function, N3IWF) or the trusted non-3GPP gateway function network element (Trusted Non-3GPP Gateway Function, TNGF) and the user plane function network element (User Plane Function).
  • N3 interworking function network element Non-3GPP InterWorking Function, N3IWF
  • TGF Trusted Non-3GPP Gateway Function
  • User Plane Function User Plane Function
  • UPF UPF
  • other user plane resources established for the session, including but not limited to the air interface tunnel established by N3IWF or TNGF for the session, and the N3 tunnel established by N3IWF or TNGF and UPF for the session.
  • the terminal device selects one or more sessions with active user plane connections to proceed. Release, thereby reducing the number of sessions with active user plane connections. If the session is released, the session needs to be re-established when the user plane connection of the session is used subsequently, which wastes signaling and increases the delay of service establishment.
  • the terminal device has the activation When the number of user-plane connection sessions reaches the number threshold and the terminal device expects to activate user-plane connections of other sessions, the terminal device selects one or more sessions with active user-plane connections to release, thereby reducing the number of active user-plane connections. The number of connected sessions. If the session is released, the session needs to be re-established when the user plane connection of the session is used subsequently, which wastes signaling and increases the delay of service establishment.
  • the embodiments of the present application provide a session processing method and a communication device, which can avoid the problems of signaling waste and service establishment delay increase caused by session reestablishment.
  • the embodiments of the present application provide a session processing method, where the method may be executed by a terminal device, or may be executed by a component of the terminal device (for example, a processor, a chip, or a chip system, etc.).
  • the session processing method may include: in the case that the terminal device has the number of active user plane connection sessions not less than the number threshold, the terminal device determines to deactivate the user plane connection of at least one first session, wherein there is an active user plane connection
  • the connected sessions include one less first session.
  • the terminal device when it determines at least one first session to be deactivated in a session with an activated user plane connection, it can make a selection according to the function of the session. For example, if a certain session with an activated user plane connection is used If the abnormal data report is sent, the terminal device cannot select the session to deactivate the user plane connection.
  • the terminal device sends a first request message to the first network element, where the first request message includes indication information, and the indication information is used to instruct to deactivate a user plane connection of at least one first session.
  • the session management network element deactivates the user plane connection of the first session according to the instruction information.
  • the user plane connection of at least one first session can be deactivated to reduce the terminal device's active user plane connections.
  • the terminal device determining to deactivate the user plane connection of at least one first session may include: When the terminal device has changed from accessing the network through a non-narrowband Internet of Things to accessing the network through a narrowband Internet of Things, and the number of sessions in which the terminal device has active user plane connections is greater than the number threshold, the terminal device determines to deactivate at least one first The user plane connection of a session.
  • the terminal device may use part of the sessions greater than the number threshold as the at least one first session to be deactivated, so that the at least one first session is deactivated After that, the number of sessions in which the terminal device has active user plane connections is equal to the number threshold. For example, if the number of sessions in which the terminal device has active user plane connections is 5, and the number threshold is 2, the terminal device may regard 3 sessions as the at least one first session described above, and connect the user planes of the three first sessions. go activate.
  • the terminal device can also deactivate the user plane connection of at least one first session, the number of sessions in which the terminal device has active user plane connections is less than the number threshold, which is not limited in this embodiment of the application.
  • the terminal device when the terminal device changes from accessing the network through a non-narrowband Internet of Things to accessing the network through a narrowband Internet of Things, when the number of sessions in which the terminal device has active user plane connections is greater than the number threshold, the The user plane connection of at least one first session is deactivated, so as to reduce the number of sessions in which the terminal device has active user plane connections.
  • the terminal device determining to deactivate the user plane connection of at least one first session may include: The number of sessions with active user plane connections is not less than the number threshold. For example, the number of sessions in which the terminal device has active user plane connections is greater than or equal to the number threshold, and the terminal device determines that at least one second session activates the user plane connection. In this case, the terminal device determines to deactivate the user plane connection of at least one first session, and the at least one second session is a session that does not have an active user plane connection.
  • the terminal device needs to deactivate the user plane connection of the first session to activate the user plane connection for the second session.
  • the end device changes from accessing the network through the non-narrowband Internet of Things to accessing the network through the narrowband Internet of Things.
  • the terminal device has an active user plane connection and the number of sessions is greater than the number threshold.
  • the terminal device can Deactivate the user plane connections of some of the sessions with active user plane connections that are greater than the number threshold. For example, if the number of sessions with active user plane connections on the terminal is 5 and the number threshold is 2, the terminal device can choose to deactivate 3 user plane connections for the first session. After the user plane connections of the three first sessions are deactivated, the number of sessions in which the terminal device has active user plane connections is 2, which is equal to the number threshold.
  • the terminal device receives an upper layer request for requesting to activate the user plane connection for at least one second session (for example, it may request to activate the user plane connection for two second sessions), and at this time, the terminal device further requests to deactivate at least one first session.
  • the user plane connection of the session (for example, you can request to deactivate the user plane connection of two first sessions, or you can also request to deactivate the user plane connection of more than two first sessions), so as to satisfy users who deactivate at least one first session
  • the number of sessions in which the terminal device has activated user plane connections is less than or equal to the number threshold.
  • the instruction method for indicating that the user plane connection of the at least one first session is deactivated by the instruction information includes but is not limited to: instructing to modify the at least one first session to a session optimized using the control plane, or instructing Modify the at least one first session to a session in which no user plane connection is established, and so on.
  • the user plane connection of the at least one first session can be deactivated by modifying the at least one first session to a session optimized using the control plane, thereby reducing the terminal device's ability to be activated.
  • the number of sessions connected to the user plane can be deactivated by modifying the at least one first session to a session optimized using the control plane, thereby reducing the terminal device's ability to be activated.
  • the terminal device may send the first request message to the mobility management network element, where the first request message may be a request message sent by the terminal device in the mobility management process, for example, the first request
  • the message can be a registration request message or a service request message.
  • the terminal device when the terminal device switches from accessing the network through the non-narrowband Internet of Things to accessing the network through the narrowband Internet of Things, the terminal device has an active user plane connection and the number of sessions is greater than the number threshold, the terminal device can send a registration A request message.
  • the registration request message may include indication information used to indicate to deactivate the user plane connection of the at least one first session.
  • the terminal device may send a service request message, the service request The message may include indication information used to indicate to deactivate the user plane connection of the at least one first session.
  • the aforementioned at least one first session may be a session managed by at least one session management network element, and the mobility management network element requests the corresponding session management network element to deactivate the user plane connection of the corresponding first session.
  • the terminal device requests to deactivate the user plane connection of session 1 and the user plane connection of session 2, the session management network element 1 is used to manage session 1, and the session management network element 2 is used to manage session 2, then the mobility management network element requests the session The management network element 1 deactivates the user plane connection of the session 1, and the mobility management network element requests the session management network element 2 to deactivate the user plane connection of the session 2.
  • the first request message can be sent in the mobility management process and request to deactivate the user interface of one or more first sessions.
  • the one first session or multiple first sessions may involve at least one session management network element, that is, through the mobility management process, a request can be made to deactivate the user plane connection of the first session managed by the multiple session management network elements to improve the user plane connection. Deactivation efficiency.
  • the terminal device may send the first request message to the session management network element, where the first request message may be a request message sent by the terminal device in the session management process, for example, the first request
  • the message may be a session modification request message or a session establishment request message. It can be understood that the first request message may also be another type of message in the session management process, which is not limited in the embodiment of the present application.
  • the terminal device requests the session management network element to deactivate the user plane connection of at least one first session, which reduces the processing flow of the mobility management network element and reduces the load of the mobility management network element.
  • the terminal device may access the network through a narrowband Internet of Things.
  • the at least one first session for deactivating the user plane connection does not include a session for sending an abnormal data report.
  • the embodiments of the present application provide a session processing method, wherein the method may be executed by a session management network element, or may be executed by a component (such as a processor, a chip, or a chip system, etc.) of the session management network element .
  • the session processing method may include: the session management network element receives a request message, the request message may be the first request message sent by the terminal device, or the mobility management network element sends the session to the session after receiving the first request message sent by the terminal device.
  • the second request message sent by the management network element may be executed by a session management network element, or may be executed by a component (such as a processor, a chip, or a chip system, etc.) of the session management network element .
  • the session processing method may include: the session management network element receives a request message, the request message may be the first request message sent by the terminal device, or the mobility management network element sends the session to the session after receiving the first request message sent by the terminal device.
  • the request message includes indication information, which is used to instruct the session management network element to deactivate the user plane connection of the first session.
  • the indication information may indicate to deactivate user plane connections of one first session or multiple first sessions.
  • the first session is a session in which the terminal device has an active user plane connection, wherein the number of sessions in which the terminal device has an active user plane connection is not less than the number threshold.
  • a terminal device changes from accessing the network through a non-narrowband Internet of Things to accessing the network through a narrowband Internet of Things, and the number of sessions in which the terminal device has active user plane connections is greater than the number threshold.
  • the terminal device has a number of sessions in which the user plane connection is activated is greater than or equal to the number threshold, and the terminal device determines that the user plane connection is activated for at least one second session.
  • the session management network element deactivates the user plane connection of the corresponding first session according to the instruction information.
  • the user plane connection of at least one first session can be deactivated to reduce the terminal device's active user plane connections.
  • the session management network element modifies the corresponding first session to a session optimized using the control plane according to the instruction information .
  • the user plane connection of the at least one first session can be deactivated by modifying the at least one first session to a session optimized using the control plane, thereby reducing the terminal device's ability to be activated.
  • the number of sessions connected to the user plane can be deactivated by modifying the at least one first session to a session optimized using the control plane, thereby reducing the terminal device's ability to be activated.
  • the request message may come from the mobility management network element, that is, after the mobility management network element receives the first request message from the terminal device, it sends a second request message to the session management network element.
  • the request message is the request message of this embodiment.
  • the request message includes indication information used to indicate to deactivate the user plane connection of the first session, which is a session managed by the session management network element.
  • the request message may be a session context update message.
  • the request message may come from a terminal device, and the terminal device may send a request message to the session management network element in the session management process, and the request message may be a request message type in the session management process.
  • the request message may be a session establishment request message or a session modification request message.
  • the method may further include: the session management network element according to the local policy, network location or user subscription data One or more of the following, determine to deactivate the user plane connection of the first session.
  • the session management network element may also determine that the user plane connection of the first session cannot be deactivated according to one or more of local policies, network locations, or user subscription data.
  • the first session is a session to be released by the session management network element, or the first session cannot be modified to use due to control plane congestion, the number of sessions using control plane optimization reaches the maximum, and the network does not support control plane optimization.
  • the session management network element determines to deactivate the user plane connections of other sessions, and so on.
  • the terminal device requests to deactivate the user plane connection of session 1, and the session management network element determines that the user plane connection of session 1 cannot be deactivated, but deactivates the user plane connection of session 2.
  • the session management network element can determine whether the user plane connection of the first session can be deactivated in a variety of ways, so as to meet the requirements of a variety of scenarios.
  • the session management network element sends a response message that includes the user plane connection deactivation result information of the first session, and the user plane connection deactivation result information indicates that the user plane connection deactivation of the first session is successful Or the deactivation was unsuccessful. It is understandable that if the terminal device requests to deactivate the user plane connections of the multiple first sessions, the response message may include the user plane connection deactivation result information of the multiple first sessions.
  • the session management network element may also send a response message multiple times, and one response message indicates the user plane connection deactivation result information of one first session.
  • the session management network element may send a response message to the mobility management network element, and the mobility management network element sends the user plane connection deactivation result information of the first session to the terminal device.
  • the response message may be a session context update response message.
  • the session management network element may also send a response message to the terminal device, where the response message includes user plane connection deactivation result information.
  • the response message may be a session modification response message or a session establishment response message, and so on.
  • the response message also includes the reason value information for the unsuccessful user plane connection deactivation.
  • the cause value information includes one or more of the following information: control plane congestion, the number of sessions using control plane optimization reaches the maximum, the network does not support control plane optimization, and users are not allowed to deactivate
  • the user-plane connection is the user-plane connection for the session to be released or to deactivate other sessions.
  • the terminal device can learn the reason why the user plane connection is not successfully deactivated.
  • an embodiment of the present application provides a communication device, including various modules or units for executing the method of the first aspect or the second aspect.
  • an embodiment of the present application provides a communication device including a processor.
  • the processor is coupled with the memory and can be used to execute instructions in the memory to implement the method of the first aspect or the second aspect described above.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • an embodiment of the present application provides a processor, including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method of the first aspect or the second aspect.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits, etc.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to the transmitter and transmitted by the transmitter
  • the circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • an embodiment of the present application provides a processing device, including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method of the first aspect or the second aspect.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • sending a request message may be a process of outputting a request message from the processor
  • receiving a message may be a process of receiving a message by the processor.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the receiver.
  • the transmitter and receiver can be collectively referred to as a transceiver.
  • the processing device in the sixth aspect described above may be one or more chips.
  • the processor in the processing device can be implemented by hardware or software.
  • the processor may be a logic circuit, integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory, and the memory may Integrated in the processor, can be located outside the processor, and exist independently.
  • the embodiments of the present application provide a computer program product.
  • the computer program product includes: a computer program (also called code, or instruction), which when the computer program is executed, causes the computer to execute the above-mentioned first One aspect or the second aspect of the method.
  • the embodiments of the present application provide a computer-readable storage medium that stores a computer program (also called code, or instruction) when it runs on a computer, causing the computer to execute The method of the first aspect or the second aspect described above.
  • a computer program also called code, or instruction
  • an embodiment of the present application provides a communication system, including the aforementioned terminal device and a session management network element.
  • the communication system may also include a mobility management network element.
  • a chip system in a tenth aspect, includes a processor and an interface.
  • the processor is used to call and run a computer program (also called code, or instruction) stored in the memory from the memory to implement the first
  • a computer program also called code, or instruction
  • the chip system further includes a memory, and the memory is used to store necessary program instructions and data.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • Figure 1 is a 5G system architecture diagram provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a session processing method provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of another session processing method provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a mobility management process for deactivating a user plane connection according to an embodiment of the present application
  • FIG. 5 is a schematic flowchart of a session management process for deactivating a user plane connection according to an embodiment of the present application
  • FIG. 6 is a schematic flowchart of another session management process for deactivating a user plane connection provided by an embodiment of the present application
  • FIG. 7 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of another communication device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • LTE long term evolution
  • UMTS universal mobile telecommunication system
  • 5G fifth generation
  • NR new radio
  • FIG. 1 shows a schematic diagram of a 5G system that can be applied to the present application.
  • the system can be divided into two parts: access network and core network.
  • the access network is used to implement functions related to wireless access, and mainly includes access network (AN) equipment 102.
  • the access network equipment includes radio access network (RAN) equipment and other radio access network (RAN) equipment and other radio access network equipment. Connected device (such as WiFi).
  • the core network mainly includes the following key logical network elements: user plane function (user plane function) 103, access and mobility management function (access and mobility management function, AMF) 105, session management function (session management function) 106, strategy Control function (policy control function, PCF) 107, unified data management function (unified data management) 109.
  • the system 100 may also include a user equipment (UE) 101, a data network (DN) 104, and an application function (AF) 108.
  • UE user equipment
  • DN data network
  • AF application function
  • the UE may also be called terminal equipment.
  • the terminal device can communicate with one or more core networks (core networks, CN) via the AN device.
  • the terminal device can be called an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user device.
  • the terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld with wireless communication function Devices, computing devices or other devices connected to wireless modems, in-vehicle devices, wearable devices or the Internet of Things, terminal devices in vehicle networks, and terminal devices of any form in future networks, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • AN equipment is a type of equipment that connects terminal equipment to a wireless network, and may specifically be a base station.
  • Base stations may include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, and access points. Specifically, it can be: access point (AP) in wireless local area network (WLAN), global system for mobile communications (GSM) or code division multiple access (code division multiple)
  • the base transceiver station (BTS) in access, CDMA can also be the base station (NodeB, NB) in wideband code division multiple access (WCDMA), or the evolved base station in LTE (Evolved Node B, eNB or eNodeB), or relay station or access point, or in-vehicle equipment, wearable equipment, and the next generation Node B (gNB) in the 5G system or the public land mobile network that will evolve in the future (public land mobile network, PLMN) base stations in the network.
  • AP access point
  • GSM global system for mobile communications
  • UDM has functions such as managing the user's contract data and generating user authentication information.
  • AMF is mainly responsible for UE registration management, UE connection management, UE reachability management, UE access authorization and access authentication, UE security functions, UE mobility management, network slice selection , SMF selection and other functions.
  • the AMF serves as the anchor point of the N1/N2 interface signaling connection and provides the N1/N2 interface session management (SM) message routing for the SMF, and maintains and manages the status information of the UE.
  • SM N1/N2 interface session management
  • AMF is a mobile management network element in the 5G system.
  • SMF is mainly responsible for all control plane functions of UE session management, including UPF selection and control, Internet protocol (IP) address allocation and management, session quality of service (QoS) management, from PCF Obtain policy and charging control (PCC) policies, etc.
  • SMF is also used as the termination point of the SM part in the non-access stratum (NAS) message.
  • PCF has functions such as providing policy rules to the control plane functional entities.
  • AF can be an application server, which can belong to an operator or a third party.
  • UPF is mainly responsible for processing user messages, such as forwarding, charging, etc., and can be used as the anchor point of the protocol data unit (PDU) session connection, that is, the PDU session anchor (PSA) ), responsible for data message filtering, data transmission/forwarding, rate control, billing information generation, user plane QoS processing, uplink transmission authentication, transmission level verification, downlink data packet buffering, and downlink data notification triggering.
  • PDU protocol data unit
  • PDU session anchor responsible for data message filtering, data transmission/forwarding, rate control, billing information generation, user plane QoS processing, uplink transmission authentication, transmission level verification, downlink data packet buffering, and downlink data notification triggering.
  • PDU protocol data unit
  • PDA PDU session anchor
  • UPF can also be used as a branch point for multi-homed PDU sessions.
  • DN a network that provides users with data transmission services, such as IP Multi-media Service (IMS), the Internet, and so on.
  • DN can include application server (AS).
  • AS is a software framework that provides an environment for running applications to provide applications with services such as security, data, transaction support, load balancing, and large-scale distributed system management.
  • the UE obtains application messages through communication with the AS. It should be noted that the aforementioned AF is the control plane of the AS.
  • a communication system to which the session management method of the embodiment of the present application can be applied may include more or fewer network elements or devices.
  • the device or network element in Figure 1 can be hardware, software that is functionally divided, or a combination of the two.
  • the devices or network elements in Figure 1 can communicate with other devices or network elements.
  • the user plane connection (UP connection) in the embodiment of this application can be called user plane resources (user-plane resources), air interface bearer resources (radio bearer resources), data radio resources (data radio resources), and data wireless resources.
  • Bearer data radio bearer
  • the user plane connection can be formed by DRB and/or N3 tunnel.
  • the DRB may refer to the data radio bearer between the access network device and the terminal device
  • the N3 tunnel may refer to the data transmission tunnel established between the access network device and the user plane function network element.
  • the user plane connection can be used to transmit data.
  • a session with an activated user plane connection can be understood as the session establishing a user plane connection.
  • Activating a user-plane connection for a session can be understood as establishing a user-plane connection for the session.
  • deactivation of the user plane connection of the session in the embodiment of the present application may be referred to as releasing the user plane connection of the session, where deactivating the user plane connection of the session can be understood as releasing the resources of the user plane connection of the session .
  • the session in the embodiment of the present application may be a protocol data unit (Protocol Data Unit, PDU) session, or may also be another session, which is not limited in the embodiment of the present application.
  • PDU Protocol Data Unit
  • the session optimized for the control plane in the embodiments of this application may be a PDU session established for CIoT optimization on the control plane (for example: PDU session(s) established for control plane CIoT Optimization) or a PDU session optimized for CIoT on the control plane (for example : Use Control Plane CIoT Optimization for the PDU session(s), or PDU session(s) using Control Plane CIoT Optimization), or it can also be a session that uses the control plane to transmit data.
  • the session optimized using the control plane does not establish a user plane connection, that is, the session optimized using the control plane does not use user plane resources for data transmission.
  • NB-IoT is a type of radio access technology (Radio Access Technology, RAT).
  • RAT Radio Access Technology
  • NB-IoT allows Evolved UTRA (Evolved UTRA, E-UTRA) access to the network through a channel bandwidth lower than 200kHZ.
  • the abnormal data report in the embodiment of the present application is an abnormal event report issued by a UE using the Cellular Internet of Things (CIoT) feature, and may also be referred to as an abnormal report.
  • CCIoT Cellular Internet of Things
  • the use of user plane CIoT optimization in the embodiments of this application means that when the UE enters the idle state, the radio resource control (Radio Resource Control, RRC) connection can be suspended, and the UE and the RAN save the Access Stratum (AS) context When the idle state enters the connected state, there is no need to establish the AS context.
  • RRC Radio Resource Control
  • AS Access Stratum
  • the UE in the connected state has a non-access stratum (NAS) signaling connection with the AMF established through the N1 interface.
  • the UE in the idle state has not established a NAS signaling connection with the AMF through the N1 interface.
  • the UE in the idle state has no AN signaling connection, N2 connection and N3 connection.
  • NAS non-access stratum
  • the terminal device may send a first request message to the mobility management network element, where the first request message includes instruction information, and the instruction information is used
  • the mobility management network element determines at least one session management network element for managing the at least one first session, and sends a second request to the corresponding session management network element Message (can also be referred to as a request message), the second request message includes indication information for instructing to deactivate the user plane connection of the first session, and accordingly, the session management network element
  • the user plane connection of a session is deactivated.
  • the terminal device may send a first request message to the session management network element, where the first request message includes instruction information, and the instruction information is used Yu instructs to deactivate the user plane connection of at least one first session.
  • the session management network element receives the first request message (which may also be referred to as a request message), and according to the instruction information, deactivates the user plane connection of the first session.
  • the first request message which may also be referred to as a request message
  • the instruction information deactivates the user plane connection of the first session.
  • FIG. 2 may be a terminal device sending a first request message to a mobility management network element for instructing to transfer at least one first session
  • the user plane connection is deactivated, for example, the terminal device requests to deactivate the user plane connection of at least one first session through the mobility management process.
  • FIG. 3 may be a terminal device sending a first request message to the session management network element to instruct the user plane connection of at least one first session to be deactivated. For example, the terminal device requests the deactivation of at least one first session through the session management process.
  • User plane connection may be a terminal device sending a first request message to the session management network element to instruct the user plane connection of at least one first session to be deactivated.
  • FIG. 2 is a schematic flowchart of a session processing method provided by an embodiment of this application.
  • the first network element may be a mobility management network element.
  • the session of the embodiment of this application The processing method includes but is not limited to the following steps:
  • the terminal device determines to deactivate the user plane connection of at least one first session, and the session with the active user plane connection Including the at least one first conversation;
  • the terminal device may access the network through a narrowband Internet of Things NB-IoT.
  • the number of sessions with activated user plane connections is not less than the number threshold.
  • the number of sessions with activated user plane connections is greater than the number threshold or equal to the number threshold.
  • the number threshold can be defined by the protocol defined by the terminal device passing the narrowband object.
  • the maximum allowed number of sessions with active user plane connections for example, can be 2 or 3, etc.
  • At least one of the first sessions for which the user plane connection is to be deactivated has an active user plane connection.
  • the upper layer request of the terminal device is at least one
  • the second session activates the user plane connection, and the at least one second session does not have an active user plane connection, and the terminal device determines to deactivate the user plane connection of the at least one first session.
  • the terminal device may determine the number of at least one first session to deactivate the user plane connection according to the number of sessions with activated user plane connections, the number of at least one second session, and the number threshold, so as to satisfy the requirement of activating at least one user plane connection. After the user plane connection of the second session and at least one user plane connection of the first session are deactivated, the number of sessions in which the terminal device has activated user plane connections is less than or equal to the number threshold.
  • the number of sessions in which the terminal device has active user plane connections is 3, and the number threshold is 3.
  • the user plane connections of the three first sessions can also be deactivated, so as to activate the user plane connections of at least one second session, and after deactivating the user plane connections of at least one first session, the terminal device has activated
  • the number of sessions connected to the user plane is 2, that is, less than the number threshold of 3, which is not limited in the embodiment of the present application.
  • the terminal device changes from accessing the network through the non-narrowband Internet of Things to accessing the network through the narrowband Internet of Things, the terminal device has an active user plane connection with a number of sessions greater than the number threshold, and the terminal The device may choose to deactivate the user plane connection of at least one first session, so that the number of sessions in which the terminal device has active user plane connections is less than or equal to the number threshold.
  • the terminal device may determine the number of the at least one first session to deactivate the user plane connection according to the number of sessions with activated user plane connections and the number threshold, so as to satisfy the deactivation of the user plane connection of the at least one first session After that, the number of sessions in which the terminal device has active user plane connections is less than or equal to the number threshold.
  • the user plane connection of one first session is deactivated to satisfy the requirement of deactivating the user plane connection of at least one first session
  • the number of sessions in which the terminal device has active user plane connections is 2, which is equal to the number threshold.
  • the user plane connections of the two first sessions can also be deactivated, so that after the user plane connection of at least one first session is deactivated, the number of sessions in which the terminal device has active user plane connections is 1, that is, It is less than the quantity threshold of 2, which is not limited in the embodiment of the present application.
  • the first optional implementation manner and the second optional implementation manner may be combined to determine the deactivated user plane connection of at least one first session. For example, if a terminal device changes from accessing the network through a non-narrowband Internet of Things to accessing the network through a narrowband Internet of Things, the terminal device has an active user plane connection and the number of sessions is greater than the number threshold, and the terminal device may have an active user plane.
  • the user plane connections of the part of the connected sessions that are greater than the number threshold are deactivated. For example, if the number of sessions in which the terminal has active user plane connections is 5 and the number threshold is 2, the terminal device can choose to deactivate the three first sessions. User plane connection.
  • the terminal device After the user plane connections of the three first sessions are deactivated, the number of sessions in which the terminal device has active user plane connections is 2, which is equal to the number threshold. Then, the terminal device receives an upper layer request for requesting to activate the user plane connection for at least one second session (for example, it may request to activate the user plane connection for two second sessions), and at this time, the terminal device further requests to deactivate at least one first session.
  • the user plane connection of the session (for example, it can be requested to deactivate the user plane connection of the two first sessions), so as to satisfy the deactivation of at least one user plane connection of the first session, and after activating the user plane connection of at least one second session, the The number of sessions in which the terminal device has active user plane connections is less than or equal to the number threshold.
  • the terminal device when it determines at least one first session to be deactivated in a session with an activated user plane connection, it can make a selection according to the function of the session. For example, if a certain session with an activated user plane connection is used If the abnormal data report is sent, the terminal device cannot select the session to deactivate the user plane connection.
  • the terminal device must choose to deactivate the user plane connection of one or more first sessions.
  • the session management network element may be based on local policies, network configuration, or user subscription data. Determine to release one or more sessions, and send a release instruction to the terminal device, where the release instruction indicates whether to rebuild the released session.
  • the session in which the terminal device has an active user plane connection may include the session determined to be released and rebuilt by the session management network element and the session reserved by the session management network element, and the session and session management determined to be released and rebuilt by the session management network element
  • the sessions reserved by the network element may all have active user plane connections.
  • the session reserved by the session management network element refers to a session that the session management network element determines not to release. It is understandable that, in this scenario, the at least one first session that is subsequently requested to be deactivated may be a session determined to be released and rebuilt by the session management network element and/or a session reserved by the session management network element.
  • the terminal device sends a first request message to a mobility management network element, where the first request message includes indication information, and the indication information is used to indicate to deactivate a user plane connection of the at least one first session.
  • the indication information may be the session user plane connection deactivation list information (List Of PDU Sessions To Be Deactivated), and the session user plane connection deactivation list information includes a session identifier (Identity, ID) list.
  • the session ID list includes at least one session ID of the first session, where the session ID list is used to indicate that the user plane connection of the corresponding session is deactivated.
  • the above-mentioned session user plane connection deactivation list information may be a newly added value in an existing cell, or may be a newly added cell.
  • the indication information may be bit information. If the user plane connection of a first session is to be deactivated, the indication information includes one bit. To deactivate the user plane connections of multiple first sessions, the indication information may include multiple bits, and the multiple bits may constitute a bit set or a bit list. Among them, one bit corresponds to one first session.
  • bit 0 may indicate that the user plane connection corresponding to the first session is not to be deactivated
  • bit 1 may indicate that the user plane connection corresponding to the first session is to be deactivated
  • bit 0 may also indicate that the user plane connection corresponding to the first session is to be deactivated
  • bit 1 indicates that the user plane connection corresponding to the first session is not to be deactivated, which is not limited in this embodiment of the application.
  • bit 0 indicates that the user plane connection corresponding to the first session is not to be deactivated
  • bit 1 indicates that the user plane connection corresponding to the first session is to be deactivated as an example.
  • a terminal device can have up to 15 sessions.
  • PDU Session Identity (PSI) (1) corresponds to a session with a session ID of 1
  • PSI (2) corresponds to a session ID Is 2 sessions, and so on.
  • the table The bit of PSI(1) in one is set to 1, optional, and the remaining bits are set to 0.
  • bit 0 can be the default value, and then the bit of PSI(1) can be set to 1.
  • the session ID of 1 is to be deactivated and the ID is For session 2, set the bits of PSI(1) and PSI(2) in Table 1 to 1, optional, and set the remaining bits to 0.
  • bit 0 may be the default value, and the bits of PSI(1) and PSI(2) may be set to 1.
  • the first request message may be a request message sent by the terminal device in a mobility management process.
  • the mobility management process includes but is not limited to a service request process and a registration update process, which are described below with examples.
  • the first request message may be a service request (service request) message in the service request process.
  • service request service request
  • the terminal device can choose to deactivate the user plane connection of one or more first sessions.
  • the terminal device initiates a service request process, that is, sends a service request message to the mobility management network element.
  • the service request message contains a user plane connection deactivation instruction (that is, instruction information), and the user plane connection deactivation instruction is used to instruct to deactivate the user plane connection.
  • the user plane connection deactivation instruction can be a new function in an existing Information element (IE) in the service request message, or it can be a newly added IE in the service request message, which is not done in this application. limited.
  • IE Information element
  • the first request message may be a registration request (registration request) message in a registration update process
  • the registration update process is also referred to as a mobility registration update process.
  • a terminal device when a terminal device switches from accessing the network through a non-narrowband Internet of Things to accessing the network through a narrowband Internet of Things, it can initiate a registration update process. If the number of sessions in which the terminal device has active user plane connections exceeds the number threshold, the terminal device can choose to deactivate the user plane connections of one or more first sessions, so that the terminal device has the number of sessions in which user plane connections are active. Less than or equal to the number threshold.
  • the terminal device sends a registration request message to the mobility management network element.
  • the registration request message may include a user-plane connection deactivation instruction (that is, indication information), and the user-plane connection deactivation instruction is used to instruct to deactivate one Or multiple user-plane connections of the first session.
  • the indication information used to indicate that the user plane connection of the at least one first session is deactivated includes, but is not limited to, indicating that the at least one first session is modified or rebuilt into a session optimized using the control plane; or, Instructing to modify or rebuild the at least one first session to a session without establishing a user plane connection, etc., is not limited in the embodiment of the present application.
  • modifying or rebuilding at least one first session as a session optimized using the control plane may be modifying or rebuilding the at least one first session as a session optimized using the control plane CIoT and not using N3 data transmission.
  • Sessions in which the terminal device has an active user plane connection may include but are not limited to the following sessions: sessions optimized using the control plane CIoT and using N3 data transmission, using user plane CIoT optimization or not using CIoT optimization.
  • N3 data transmission refers to not establishing a user plane connection for the corresponding session, and data corresponding to the corresponding session is transmitted through the control plane.
  • the mobility management network element sends a second request message to the session management network element, where the second request message includes indication information, and the indication information is used to indicate to deactivate the user plane connection of the first session.
  • the terminal device sends a first request message to the mobility management network element.
  • the mobility management network element receives the first request message and parses the first request message to obtain the terminal device to deactivate the user The session ID of at least one first session of the connection. Further, the mobility management network element determines at least one session management network element for managing the at least one first session, and sends a second request message to the corresponding session management network element.
  • the at least one first session for the terminal device to deactivate the user plane connection is session 1, session 2, session 3, and session 4.
  • session management network element 1 is used to manage session 1 and session 2
  • session management network element 2 Used to manage session 3 and session 4.
  • the mobility management network element sends a second request message for requesting to deactivate the user plane connection of the session 1 and the session 2 to the session management network element 1.
  • the mobility management network element sends to the session management network element 2 a second request message for requesting to deactivate the user plane connection of the session 3 and the session 4. It is understandable that the mobility management network element may request to activate one or more user-plane connections of the first session each time.
  • a user-plane connection of the first session may request to deactivate multiple users in multiple times.
  • User plane connection for the first session For example, the mobility management network element may request the session management network element 2 to deactivate the user plane connection of the session 3 and the user plane connection of the session 4 respectively.
  • the second request message includes indication information, which is used to indicate to deactivate the user plane connection of the first session.
  • one second request message may correspond to one first session.
  • the second request message may include the session ID of the first session.
  • the indication information in the second request message may be one bit information, and the bit information is used to indicate whether to deactivate the user plane connection of the first session.
  • bit 0 may indicate that the user plane connection for the first session is not to be deactivated, and bit 1 may indicate that the user plane connection for the first session is to be deactivated.
  • bit 0 may also indicate that the user plane connection of the first session is to be deactivated, and bit 1 indicates that the user plane connection of the first session is not to be deactivated, which is not limited in this embodiment of the application.
  • bit 0 indicates that the user plane connection for the first session is not to be deactivated, and bit 1 indicates that the user plane connection for the first session is to be deactivated as an example.
  • bit 0 may be the default value. When the user plane connection of the session is deactivated, this bit can be set to 1.
  • the second request message may also include reason value information for the deactivation of the user plane connection.
  • the reason value information includes but is not limited to: 1. The number of sessions in which the terminal device has activated user plane connections has reached the maximum value (with The number of activated user plane connection sessions is greater than or equal to the number threshold), and the upper layer of the terminal device requests to activate the user plane connection for at least one second session. 2. When the terminal device switches from accessing the network through the non-narrowband Internet of Things to accessing the network through the narrowband Internet of Things, the number of sessions in which the terminal device has active user plane connections is greater than the number threshold. 3. Other possible reasons why the terminal device expects to deactivate the user plane connection.
  • the second request message may be a session context update message (or may also be referred to as a session context update service operation request message), of course, it may also be another type of message, which is not limited in this application.
  • the mobility management network element may call the session context update (for example, UpdateSMContext) service operation of the servicing interface (for example: Nsmf_PDUSession) of the session management network element to send the session context update message.
  • the session context update message includes the session ID of at least one first session for which the user plane connection is to be deactivated.
  • the mobility management network element may also determine before sending the second request message Whether the at least one first session can be modified or reconstructed as a session optimized using the control plane. If it is determined that the at least one first session can be modified or reconstructed as a session optimized using the control plane, the mobility management network element sends a second request message to the session management network element and instructs to modify or reconstruct the first session to use the control plane Optimized session.
  • the mobility management network element determines that at least one of the first sessions cannot be modified or re-established as a session optimized using the control plane (optionally, the mobility management network element may determine some of the first sessions among the multiple first sessions requested by the terminal device).
  • the session cannot be modified or re-established as a session optimized using the control plane
  • the mobility management network element returns the information sent by the terminal device to the terminal device through a downlink NAS transmission message, and carries the reason value information that cannot be forwarded.
  • the reason value information includes but Not limited to: 1. Control plane congestion; 2. The number of sessions using control plane optimization has reached the maximum; 3. The network side does not support the use of control plane optimization; 4. Other possible causes. In this case, step S102 and step S103 are not executed.
  • the session management network element deactivates the user plane connection of the first session according to the instruction information.
  • the session management network element before the session management network element deactivates the user plane connection of the first session, it can also determine whether the requested data can be changed according to one or more of the local policy, network configuration, or user subscription data.
  • the user plane connection of the first session is deactivated. If the user plane connection of the first session can be deactivated, the user plane connection of the first session is deactivated according to the instruction information, that is, the user plane connection of the first session is successfully deactivated. If the user plane connection of the first session cannot be deactivated, the user plane connection of the first session is not deactivated, that is, the user plane connection of the first session is not successfully deactivated.
  • the unsuccessful deactivation of the user plane connection referred to in this application may also mean that the session management network element failed in the process of deactivating the user plane connection, resulting in unsuccessful deactivation of the user plane connection of the first session.
  • the deactivation of the user plane connection of the first session by the session management network element may refer to that the session management network element interacts with the user plane function network element (the user plane function network element is associated with the first session), thereby connecting the first session
  • the session management network element interacts with the user plane function network element (the user plane function network element is associated with the first session), thereby connecting the first session
  • the session management network element may also send a response message to the mobility management network element, where the response message includes the user plane connection deactivation result information of the first session.
  • the user plane connection deactivation result information indicates that the user plane connection deactivation of the first session is successful or unsuccessful. If the user plane connection deactivation result information indicates that the user plane connection deactivation of the first session is unsuccessful, the response message may also include the reason value information for the unsuccessful user plane connection deactivation.
  • the reason value information includes one or more of the following information: the first session is the session to be released, the control plane is congested, the number of sessions using control plane optimization reaches the maximum, the network does not support control plane optimization, and deactivation is not allowed
  • the user plane connection, or deactivation of the user plane connection of other sessions, etc. are not limited in the embodiment of the present application. The following is an example of each cause value information.
  • the first session is the session to be released.
  • the session management network element receives the first 2.
  • it is determined whether the first session requesting to activate the user plane connection is the session to be released by the session management network element. If the first session is the session to be released by the session management network element, the session management network element may refuse Deactivate the user plane connection of the first session, and return rejection reason value information.
  • the rejection reason value information includes but is not limited to: 1.
  • the first session is the session to be released; 2.
  • the first session is to be released and Third, other possible reasons for the reconstructed session.
  • the rejection reason value information may be sent to the mobility management network element through the above response message. For details, please refer to the description of the foregoing embodiment, which will not be repeated here.
  • the session management network element releases the first session, the user plane connection of the first session is also deactivated, and the session management network element does not need to connect the user plane of the first session to the instruction information. go activate. Therefore, it can be considered that the session management network element refuses to activate the user plane connection of the first session, and returns the value information of the reason for the rejection.
  • the control plane is congested, the number of sessions using control plane optimization reaches the maximum, and the network does not support control plane optimization.
  • the session management network element may determine whether to modify or rebuild the first session according to one or more of the local policy, network configuration, or user subscription data
  • the first session can be modified to a session optimized using the control plane. If the first session can be modified to a session optimized using the control plane, the first session is modified to a session optimized using the control plane according to the instruction information, so as to satisfy that the number of sessions in which the terminal device has active user plane connections is less than or equal to the number Threshold.
  • the first session cannot be modified to use the control plane optimization session, then return to the user plane connection to deactivate unsuccessful.
  • it can also carry the value information of the reason why the control plane optimization cannot be used.
  • the reason value information includes but is not limited to: 1. Control plane congestion; 2. The number of sessions using control plane optimization has reached the maximum; 3. The network side does not support control plane optimization; 4. Other possible causes.
  • the reason value information for the inability to use the control plane optimization may be sent to the mobility management network element through the above response message. For details, please refer to the description of the foregoing embodiment, and will not be repeated here.
  • the session management network element may also choose to connect the user plane of other sessions (not the at least one first session indicated by the mobility management network element) according to one or more of the local policy, network configuration, or user subscription data go activate.
  • the indication information is used to instruct the user plane connection of Session 1 and Session 3 to be deactivated.
  • the session management network element may determine that the user of Session 3 cannot be connected according to one or more of the local policy, network configuration, or user subscription data.
  • the user plane connection of session 4 can be deactivated.
  • the session management network element can deactivate the user plane connection of session 1 and the user plane connection of session 4, and return to the deactivated user plane connection of session 3. Success and the reason value information for the unsuccessful deactivation of the user plane connection, where the reason value information for the unsuccessful deactivation of the user plane connection can be the deactivation of the user plane connection of other sessions, or the user plane connection of the session is not allowed Deactivation, or other possible reasons.
  • the cause value information may be sent to the mobility management network element through the above response message. For details, please refer to the description of the foregoing embodiment, which will not be repeated here.
  • the response message in this embodiment may be a session context update response message.
  • the response message may also include N2 session management (session management, SM) information (where N2 SM information refers to Information about the session sent by the session management network element to the access network device), N2 SM information instructs the access network device to release resources related to the first session, and resources related to the first session include but are not limited to terminal equipment and access Data radio bearer resources between network devices and N3 tunnel resources between access network devices and user plane function network elements.
  • SM session management
  • the N2 SM information may not be included in the response message.
  • the mobility management network element receives the N2 SM information, and forwards the N2 SM information to the access network device through the N2 interface, for example, sends a resource release command to the access network device, and the resource release command includes the N2 SM information, and then The network access device releases resources related to the first session.
  • the resource release command can be an existing message type, such as a protocol data unit session resource release command message, or other existing or new types of messages in the future, which is not limited in this application.
  • the resource release command may also include the above-mentioned user plane connection deactivation result information, and/or information about the reason for the unsuccessful deactivation.
  • the mobility management network element may wait after receiving response messages sent by all session management network elements , Once again send a resource release command to the access network device.
  • the mobility management network element may also send a resource release command to the access network device multiple times.
  • the access network device After receiving the resource release command, the access network device performs the release of resources related to the first session through interaction with the terminal device, such as the release of resources on the Uu interface and N3 interface, that is, the release of data radio bearer resources and N3 tunnels resource. After the access network device releases the resources, it sends a resource release response to the mobility management network element. After receiving the resource release response, the mobility management network element may send a service response message or a registration response message to the terminal device, and the service response message or the registration response message indicates that the user plane of at least one first session of the user plane connection is to be deactivated. Connection deactivation result information (or can also be referred to as the user plane connection status of the at least one first session).
  • the user plane connection deactivation result information is used to indicate that the user plane connection deactivation of the at least one first session is successful or unsuccessful, if the deactivation result information indicates that the user plane connection deactivation of the at least one first session is unsuccessful .
  • the service response message or the registration response message may also contain the value information of the reason for the failure to deactivate successfully.
  • the mobility management network element may wait to receive the resource release response for all the first sessions before sending it to the terminal device.
  • Service response message or registration response message may be used to send the resource release response for all the first sessions before sending it to the terminal device.
  • the access network device interacts with the terminal device to perform the resource release process related to the first session, and can deactivate at least one user of the first session connected to the user plane
  • the face connection deactivation result information and/or the failure reason value information is sent to the terminal device, that is, the service response message or the registration response message can be sent to the terminal device during the resource release process between the access network device and the terminal device .
  • FIG. 3 is a schematic flowchart of another session processing method provided by an embodiment of this application.
  • the first network element may be a session management network element.
  • the session processing method includes but is not limited to the following steps:
  • the terminal device determines to deactivate user plane connections of at least one first session, and the session with active user plane connections Including the at least one first conversation;
  • step S200 in the embodiment of the present application please refer to step S100 in the embodiment of FIG. 2, which will not be repeated here.
  • the terminal device sends a first request message to a session management network element, where the first request message includes instruction information, and the instruction information is used to instruct to deactivate a user plane connection of the first session.
  • the first request message may be a request message sent by the terminal device in the session management process.
  • the first request message may be a session modification request message or a session establishment request message.
  • the first request message corresponds to a first session.
  • the first request message may include the corresponding session ID of the first session.
  • the indication information may be a newly added value in an existing cell.
  • the indication information may be a newly added reason value in the session modification reason value, and the reason value is used to indicate the The user plane connection of one session is deactivated, that is, the user plane connection of the first session is requested to be deactivated.
  • the indication information may also be a newly added information element, such as a user-plane connection deactivation request (User-plane Deactivation Requested, UPDR).
  • the information element may include a bit, the bit being 0 or 1, and the bit is used to indicate whether to deactivate the user plane connection of the first session, that is, whether to request to deactivate the user plane connection of the first session.
  • bit 0 may indicate that the user plane connection for the first session is not to be deactivated, and bit 1 may indicate that the user plane connection for the first session is to be deactivated.
  • bit 0 may also indicate that the user plane connection of the first session is to be deactivated, and bit 1 indicates that the user plane connection of the first session is not to be deactivated, which is not limited in this embodiment of the application.
  • bit 0 indicates that the user plane connection for the first session is not to be deactivated, and bit 1 indicates that the user plane connection for the first session is to be deactivated as an example.
  • bit 0 may be the default value. When the user plane connection of the session is deactivated, the bit of the cell is set to 1.
  • the instruction method for indicating that the user plane connection of the first session is deactivated by the instruction information includes but is not limited to: instructing to modify or rebuild the first session to a session optimized using the control plane; or, instructing the first session to Modification or reconstruction to a session that does not establish a user plane connection, etc., is not limited in the embodiment of the present application.
  • modifying or rebuilding the first session as a session optimized using the control plane may be modifying or rebuilding the first session as a session optimized using the control plane CIoT and not using N3 data transmission.
  • the terminal device has The activated user-plane connection sessions may include, but are not limited to, the following sessions: sessions optimized using the control plane CIoT and using N3 data transmission, using user plane CIoT optimization or not using CIoT optimization.
  • N3 data transmission refers to not establishing a user plane connection for the corresponding session, and data corresponding to the corresponding session is transmitted through the control plane.
  • the session management network element can be based on local policies, network configuration or user subscription data
  • it is determined to release one or more sessions, and a release instruction is sent to the terminal device, and the release instruction indicates whether to rebuild the released session.
  • the terminal device receives the release command, determines the number of sessions with user plane connections reserved by the session management network element and the session management network element to release and the number of reestablished sessions is greater than the number threshold, the terminal device receives the release indicating that the session is reestablished During the command, the session establishment process can be initiated.
  • the terminal device sends a session establishment request message (ie, the first request message).
  • the session establishment request message includes indication information, which is used to indicate that the user plane connection is not established for the first session. (It can also be referred to as deactivating the user plane connection of the first session) to satisfy that the number of sessions in which the terminal device has active user plane connections is not greater than the number threshold.
  • the first session may be a session determined to be released and rebuilt by the session management network element.
  • the terminal device may also initiate a session modification process.
  • the terminal device sends a session modification request (that is, a first request message), and the session modification request includes indication information, which is used to instruct to connect the user plane of the first session to activation.
  • the first session may be a session determined to be reserved by the session management network element.
  • the foregoing first session may be a session determined to be released and rebuilt by the session management network element and/or a session determined to be reserved by the session management network element, which is not limited in this application, and the foregoing is only an example.
  • the above-mentioned session modification request message or session establishment request message may be included in the uplink NAS transmission message and sent to the mobility management network element, and the mobility management network element invokes the session of the servicing interface (for example: Nsmf_PDUSession) of the session management network element
  • the context update (for example, UpdateSMContext) service operation sends a session context update message
  • the session context update message includes the above-mentioned session modification request message or session establishment request message.
  • the mobility management network element may also determine whether it can be used before sending the session context update message. Modify or rebuild the first session as a session optimized using the control plane. If it is determined that the first session can be modified or re-established as a session optimized using the control plane, the mobility management network element sends a session context update message to the session management network element, where the session context update message includes the above-mentioned session modification request message, or session establishment Request a message and instruct to modify or rebuild the first session as a session optimized using the control plane.
  • the mobility management network element determines that the first session cannot be modified or rebuilt into a session optimized using the control plane, the mobility management network element returns the information sent by the terminal device to the terminal device through a downlink NAS transmission message, and carries the reason why it cannot be forwarded Value information and cause Value information includes but is not limited to: 1. Control plane congestion; 2. The number of sessions using control plane optimization has reached the maximum; 3. The network side does not support the use of control plane optimization; 4. Other possible causes. In this case, step S202 is not executed, and of course the mobile management network element does not forward the session modification request message or the session establishment request message.
  • S202 The session management network element deactivates the user plane connection of the first session according to the instruction information.
  • the session management network element before the session management network element deactivates the user plane connection of the first session, it can also determine whether the requested data can be changed according to one or more of the local policy, network configuration, or user subscription data.
  • the user plane connection of the first session is deactivated. If the user plane connection of the first session can be deactivated, the user plane connection of the first session is deactivated according to the instruction information, that is, the user plane connection of the first session is successfully deactivated. If the user plane connection of the first session cannot be deactivated, the user plane connection of the first session is not deactivated, that is, the user plane connection of the first session is not successfully deactivated.
  • the unsuccessful deactivation of the user plane connection referred to in this application may also mean that the session management network element failed in the process of deactivating the user plane connection, resulting in unsuccessful deactivation of the user plane connection of the first session.
  • the deactivation of the user plane connection of the first session by the session management network element may refer to that the session management network element interacts with the user plane function network element (the user plane function network element is associated with the first session), thereby connecting the first session
  • the session management network element interacts with the user plane function network element (the user plane function network element is associated with the first session), thereby connecting the first session
  • the session management network element may also send a response message to the mobility management network element, where the response message includes the user plane connection deactivation result information of the first session.
  • the user plane connection deactivation result information indicates that the deactivation of the user plane connection of the first session is successful or unsuccessful. If the user plane connection deactivation result information indicates that the user plane connection deactivation of the first session is unsuccessful, the response message may also include the reason value information for the unsuccessful user plane connection deactivation.
  • the reason value information includes one or more of the following information: the first session is the session to be released, the control plane is congested, the number of sessions using control plane optimization reaches the maximum, the network does not support control plane optimization, and deactivation is not allowed
  • the user plane connection, or deactivation of the user plane connection of other sessions, etc. are not limited in the embodiment of the present application. The following is an example of each cause value information.
  • the first session is the session to be released.
  • the session management network element determines whether the first session that requests the deactivation of the user plane connection is to be released by the session management network element Session, if the first session is a session to be released by the session management network element, the session management network element may refuse to deactivate the user plane connection of the first session, and return rejection reason value information.
  • the rejection reason value information includes but not Limited to: 1. The first session is a session to be released; 2. The first session is a session to be released and rebuilt; 3. Other possible reasons. Wherein, the rejection reason value information may be sent to the mobility management network element through the above response message. For details, please refer to the description of the foregoing embodiment, which will not be repeated here.
  • the session management network element when the session management network element releases the first session, the user plane connection of the first session is also deactivated, and the session management network element does not need to connect the user plane of the first session to the instruction information. go activate. Therefore, it can be considered that the session management network element refuses to activate the user plane connection of the first session and returns a rejection message.
  • the control plane is congested, the number of sessions using control plane optimization reaches the maximum, and the network does not support control plane optimization.
  • the session management network element may determine whether to modify or rebuild the first session according to one or more of the local policy, network configuration, or user subscription data
  • the first session can be modified to a session optimized using the control plane. If the first session can be modified to a session optimized using the control plane, the first session is modified to a session optimized using the control plane according to the instruction information, so as to satisfy that the number of sessions in which the terminal device has active user plane connections is less than or equal to the number Threshold.
  • the first session cannot be modified to use the control plane optimization session, then return to the user plane connection to deactivate unsuccessful.
  • it can also carry the value information of the reason why the control plane optimization cannot be used.
  • the reason value information includes but is not limited to: 1. Control plane congestion; 2. The number of sessions using control plane optimization has reached the maximum; 3. The network side does not support control plane optimization; 4. Other possible causes.
  • the reason value information for the inability to use the control plane optimization may be sent to the mobility management network element through the above response message. For details, please refer to the description of the foregoing embodiment, and will not be repeated here.
  • the session management network element may also choose to deactivate the user plane connection of other sessions (not the first session indicated by the mobility management network element) according to one or more of the local policy, network configuration, or user subscription data .
  • the indication information is used to instruct the user plane connection of Session 1 and Session 3 to be deactivated.
  • the session management network element may determine that the user of Session 3 cannot be connected according to one or more of the local policy, network configuration, or user subscription data.
  • the user plane connection of session 4 can be deactivated.
  • the session management network element can deactivate the user plane connection of session 1 and the user plane connection of session 4, and return to the deactivated user plane connection of session 3. Success and the reason value information for the unsuccessful deactivation of the user plane connection, where the reason value information for the unsuccessful deactivation of the user plane connection can be the deactivation of the user plane connection of other sessions, or the user plane connection of the session is not allowed Deactivation, or other possible reasons.
  • the cause value information may be sent to the mobility management network element through the above response message. For details, please refer to the description of the foregoing embodiment, which will not be repeated here.
  • the above response message may be a session modification response message or a session establishment response message.
  • the session modification response message or the session establishment response message may be included in the session context update response message.
  • the session context update response message may include N1SM information (N1SM information refers to session-related information sent by the session management network element to the terminal device), and the N1SM information includes the above-mentioned session modification response message or Session establishment response message.
  • the session modification response message may include a session modification acceptance message or a session modification rejection message
  • the session establishment response message may include a session establishment acceptance message or a session establishment rejection message.
  • the session modification response message or the session establishment response message includes user plane connection deactivation result information, and the user plane connection deactivation result information is used to indicate that the user plane connection deactivation of the first session is successful or unsuccessful.
  • the N1SM information in the session context update response message may include a session modification acceptance message or a session establishment acceptance message, and the session modification acceptance message or session establishment
  • the acceptance message contains user-plane connection deactivation result information, which indicates that the user-plane connection of the first session is successfully deactivated (for example, a successful indication of rebuilding a session without a user-plane connection, or modifying the use of control plane optimization The successful indication of the session, or the successful indication of the reestablishment of the session optimized using the control plane, etc.).
  • the N1SM information may include a session modification rejection message or a session establishment rejection message, and the session modification rejection message or session establishment rejection message contains user plane connection deactivation result information.
  • the plane connection deactivation result information indicates that the user plane connection deactivation of the first session is unsuccessful.
  • the session modification rejection message or the session establishment rejection message may also include the reason value information for the unsuccessful user plane connection deactivation. For the reason value information, please refer to the description of the foregoing embodiment, which will not be repeated here.
  • the user plane connection deactivation result information may also be included in the session modification rejection message or the session establishment rejection message, and the user plane connection deactivation result information indicates that the user plane connection of the first session is successfully deactivated. Then the session modification acceptance message or the session establishment acceptance message includes user plane connection deactivation result information, and the user plane connection deactivation result information indicates that the user plane connection deactivation of the first session is not successful.
  • the embodiments of the present application are not limited, and the above are only examples.
  • the session context update response message may also include N2 session management (session management, SM) information (where N2 SM information It refers to the session-related information sent by the session management network element to the access network device), the N2 SM information instructs the access network device to release resources related to the first session, and the resources related to the first session include but are not limited to terminal devices and Data radio bearer resources between access network devices and N3 tunnel resources between access network devices and user plane function network elements.
  • N2 session management session management
  • the N2 SM information may not be included in the response message.
  • the mobility management network element receives the N2 SM information, and forwards the N2 SM information to the access network device through the N2 interface, for example, sends a resource release command to the access network device, and the resource release command includes the N2 SM information, and then The network access device releases resources related to the first session.
  • the resource release command can be an existing message type, such as a protocol data unit session resource release command message, or other existing or new types of messages in the future, which is not limited in this application.
  • the resource release command may also include the above-mentioned user plane connection deactivation result information, and/or information about the reason for the unsuccessful deactivation.
  • the access network device After receiving the resource release command, the access network device performs the release of resources related to the first session through interaction with the terminal device, such as the release of resources on the Uu interface and N3 interface, that is, the release of data radio bearer resources and N3 tunnels resource. After the access network device releases the resources, it sends a resource release response to the mobility management network element. After the mobile management network element receives the resource release response, it can send a session modification response message or a session establishment response message to the terminal device. The session modification response message or the session establishment response message indicates that the first session of the user plane connection is to be deactivated. User plane connection deactivation result information (or can also be referred to as the user plane connection state of the first session).
  • the user plane connection deactivation result information is used to indicate that the user plane connection deactivation of the first session is successful or unsuccessful. If the deactivation result information indicates that the user plane connection deactivation of the first session is unsuccessful, then the session The modification response message or the session establishment response message also contains the value information of the reason for the unsuccessful deactivation. For details, please refer to the description of the foregoing embodiment.
  • the access network When the device interacts with the terminal device to perform the resource release process on the Uu interface and the N3 interface, it can send the user plane connection deactivation result information of the first session to deactivate the user plane connection to the terminal device, that is, session modification
  • the response message or the session establishment response message may be sent to the terminal device during the resource release process between the access network device and the terminal device.
  • the terminal device is the UE
  • the mobility management network element is AMF
  • the access network device is RAN
  • the session management network element is SMF
  • the user plane function network element is UPF as an example for illustration.
  • the instruction information is referred to as a user plane connection deactivation instruction.
  • the UE sends a service request message or a registration request message to the AMF, where the service request message or the registration request message contains a user plane connection deactivation instruction, and the user
  • the plane connection deactivation indication is used to instruct to deactivate the user plane connection of one or more first sessions.
  • the user plane connection deactivation indication may be the session user plane connection deactivation list information (List Of PDU Sessions To Be Deactivated), and the session user plane connection deactivation list information includes the session identifier (Identity, ID). ) List, the session ID list includes at least one session ID of the first session, where the session ID list is used to deactivate the user plane connection of the corresponding session.
  • the above-mentioned session user plane connection deactivation list information may be a newly added value in an existing cell, or may be a newly added cell.
  • the user plane connection deactivation indication may be bit information. If the user plane connection of a first session is to be deactivated, the user plane connection deactivation instruction includes one bit. To deactivate the user plane connections of multiple first sessions, the user plane connection deactivation instruction may include multiple bits, and the multiple bits may constitute a bit set or a bit list. Among them, one bit corresponds to one first session.
  • bit 0 may indicate that the user plane connection corresponding to the first session is not to be deactivated
  • bit 1 may indicate that the user plane connection corresponding to the first session is to be deactivated
  • bit 0 may also indicate that the user plane connection corresponding to the first session is to be deactivated
  • bit 1 indicates that the user plane connection corresponding to the first session is not to be deactivated, which is not limited in this embodiment of the application.
  • bit 0 indicates that the user plane connection corresponding to the first session is not to be deactivated
  • bit 1 indicates that the user plane connection corresponding to the first session is to be deactivated as an example.
  • a terminal device can have up to 15 sessions.
  • PDU Session Identity (PSI) (1) corresponds to a session with a session ID of 1
  • PSI (2) corresponds to a session ID Is 2 sessions, and so on.
  • the table The bit of PSI(1) in one is set to 1, optional, and the remaining bits are set to 0.
  • bit 0 can be the default value, and then the bit of PSI(1) can be set to 1.
  • the session ID of 1 is to be deactivated and the ID is For session 2, set the bits of PSI(1) and PSI(2) in Table 2 to 1, if it is optional, set the remaining bits to 0.
  • bit 0 may be the default value, and the bits of PSI(1) and PSI(2) may be set to 1.
  • the AMF sends a session context update message to the SMF, where the session context update message includes a user plane connection deactivation instruction.
  • the session context update message may also include value information of the reason for the deactivation of the user plane connection.
  • the session context update message includes a user plane connection deactivation instruction, and the user plane connection deactivation instruction is used to instruct to deactivate the user plane connection of the first session.
  • one session context update message may correspond to one first session.
  • the session context update message may include the session ID of the first session.
  • the user plane connection deactivation indication in the second request message may be a bit of information, and the bit information is used to indicate whether to deactivate the user plane connection of the first session.
  • bit 0 may indicate that the user plane connection for the first session is not to be deactivated, and bit 1 may indicate that the user plane connection for the first session is to be deactivated.
  • bit 0 may also indicate that the user plane connection of the first session is to be deactivated, and bit 1 indicates that the user plane connection of the first session is not to be deactivated, which is not limited in this embodiment of the application.
  • bit 0 indicates that the user plane connection for the first session is not to be deactivated, and bit 1 indicates that the user plane connection for the first session is to be deactivated as an example.
  • bit 0 may be the default value. When the user plane connection of the session is deactivated, this bit can be set to 1.
  • the AMF sends a session context update message to the multiple SMFs to request the SMF to deactivate the corresponding first session.
  • the first session corresponding to the SMF may be a session managed by the SMF.
  • the SMF receives the session context update message, and deactivates the user plane connection of the first session according to the instruction information.
  • SMF is based on one of local policies, network configuration, or user subscription data Alternatively, it is determined to release the session. If the first session requested to be deactivated in the instruction information matches the session to be released by the SMF, the SMF may not deactivate the user plane connection of the first session according to the instruction information, but the first session. Once a session is released, subsequent steps will not be performed in this scenario.
  • the SMF determines that the user plane connection of the first session cannot be deactivated according to one or more of the local policy, network configuration, or user subscription data, and deactivates other sessions.
  • the SMF when the SMF deactivates the user plane connection of the first session, it can release the UPF as the N3 end point, or not release the UPF as the N3 end point.
  • the release of the UPF as the N3 end point means that after the release, the UPF as the N3 end point is released.
  • the N3 tunnel for a session no longer exists.
  • steps S303-S306 are executed; if the UPF of the N3 end point is not released, steps S307-S308 are executed, as described below.
  • S303 The SMF sends an N4 session release request to the UPF as the N3 end point.
  • S305-S306 The SMF initiates an N4 session modification process to the UPF of the non-N3 endpoint, and instructs the UPF of the non-N3 endpoint to remove the N9 tunnel information of the specified first session.
  • the SMF initiates an N4 session modification flow to the UPF as the N3 end point, and instructs the UPF as the N3 end point to remove the N3 tunnel information of the specified first session.
  • the SMF sends a session context update response message to the AMF, where the session context update response message includes user plane connection deactivation result information.
  • the user plane connection deactivation result information indicates that the requested user plane connection of the first session is successfully deactivated or unsuccessfully deactivated.
  • the session context update response message may also include N2 SM information (referring to information about the session sent by SMF to the RAN).
  • the N2 SM information instructs the RAN to release resources related to the first session, including the UE DRB between RAN and N3 tunnel between RAN and UPF.
  • the session context update response message may also carry information about the reason why the deactivation is not successful, for example, the SMF decides to release the session. It is understandable that if the SMF decides to release the conversation, the conversation context update response message does not include N2 SM information. Another example is to activate other sessions.
  • the AMF forwards the received N2 SM information to the RAN through the N2 interface, that is, sends a resource release command to the RAN. If the user plane connections of multiple sessions are to be deactivated and multiple SMFs are involved, the AMF can send PDU session resource release commands to the RAN multiple times without waiting for the session context update response messages sent by all SMFs. Of course, the AMF can also send a resource release command to the RAN again after receiving all the session context update response messages sent by the SMF. For the latter, the resource release command must specify multiple first sessions to release related resources.
  • the RAN After the RAN releases the resources, the RAN sends a resource release response to the AMF. If the resources of multiple sessions are to be released, the AMF can wait for the resource release response of all sessions to be received before sending it to the UE.
  • the AMF sends a service response message or a registration response message to the UE, and the service response message or the registration response message includes user plane connection deactivation result information.
  • the user plane connection deactivation result information indicates that the requested user plane connection of the at least one first session is successfully deactivated or unsuccessfully deactivated. If the deactivation is unsuccessful, the service response message or the registration response message also contains the reason value information for the unsuccessful deactivation, for example, the first session is the session to be released, the user plane connection is not allowed to be deactivated, or other sessions are deactivated Please refer to the description of the foregoing embodiment for specific user plane connection, etc., which will not be repeated here.
  • step S313 may also be integrated in steps S310 and S311, that is, during the resource release process of the RAN, the service response message or the registration response message is sent to the UE.
  • the embodiments of this application do not make limitations.
  • the terminal device is the UE
  • the mobility management network element is AMF
  • the access network device is RAN
  • the session management network element is SMF
  • the user plane function network element is UPF as an example.
  • the instruction information may be an instruction to deactivate a user plane connection, or an instruction to not establish a user plane connection.
  • the instruction information may be the use of control plane optimization instructions.
  • the use of control plane CIoT optimization and no N3 data transmission is used as an example of using control plane optimization. The following is respectively described in conjunction with FIG. 5 and FIG. 6.
  • the session processing method in this scenario includes but is not limited to the following steps:
  • the UE sends a session modification request message or a session establishment request message to the SMF.
  • the message may include indication information instructing SMF to re-establish the first session as a session that does not establish a user plane connection;
  • the message may include a user plane connection deactivation instruction, instructing SMF to deactivate Activate the user plane connection for the first session.
  • the session modification request message or the session establishment request message may correspond to a first session.
  • the session modification request message or the session establishment request message may include the corresponding session ID of the first session.
  • the indication information may be a newly added value in an existing cell.
  • the indication information may be a newly added reason value in the session modification reason value in the session modification request message.
  • the reason value Used to indicate to deactivate the user plane connection of the first session that is, request to deactivate the user plane connection of the first session.
  • the indication information may also be a newly added information element, such as a user-plane connection deactivation request (User-plane Deactivation Requested, UPDR).
  • the information element may include a bit, the bit being 0 or 1, and the bit is used to indicate whether to deactivate the user plane connection of the first session, that is, whether to request to deactivate the user plane connection of the first session.
  • bit 0 may indicate that the user plane connection for the first session is not to be deactivated, and bit 1 may indicate that the user plane connection for the first session is to be deactivated.
  • bit 0 may also indicate that the user plane connection of the first session is to be deactivated, and bit 1 indicates that the user plane connection of the first session is not to be deactivated, which is not limited in this embodiment of the application.
  • bit 0 indicates that the user plane connection for the first session is not to be deactivated, and bit 1 indicates that the user plane connection for the first session is to be deactivated as an example.
  • bit 0 may be the default value. When the user plane connection of the session is deactivated, the bit of the cell is set to 1.
  • the session modification request message or the session establishment request message may be included in the uplink non-access stratum (NAS) transmission message and sent to the AMF.
  • the AMF calls the SMF service interface (for example: Nsmf_PDUSession)
  • the session context update for example, UpdateSMContext service operation sends a session context update message to the SMF.
  • the session context update message includes the above-mentioned session modification request message or session establishment request message.
  • the SMF receives the session modification request message or the session establishment request message, and deactivates the user plane connection of at least one first session according to the instruction information.
  • SMF is based on one of local policies, network configuration, or user subscription data Or multiple types, it is determined to release the session. If the first session requested to be deactivated in the instruction information matches the session to be released by the SMF, the SMF may not deactivate the user plane connection of the first session according to the instruction information, but wait for the first session to be released. The first session is released, and subsequent steps are not executed in this scenario.
  • the SMF determines that the user plane connection of the first session cannot be deactivated according to one or more of the local policy, network configuration, or user subscription data, and deactivates other sessions.
  • the SMF when the SMF deactivates the user plane connection of the first session, it can release the UPF as the N3 end point or not release the UPF as the N3 end point.
  • the release of the UPF as the N3 end point means that after the release, the UPF as the N3 end point is released.
  • the N3 tunnel for a session no longer exists.
  • steps S402-S405 are executed; if the UPF of the N3 end point is not released, steps S406-S407 are executed, which are described below.
  • S402 The SMF sends an N4 session release request to the UPF as the N3 end point.
  • S404-S405 The SMF initiates an N4 session modification process to the UPF of the non-N3 endpoint, and instructs the UPF of the non-N3 endpoint to remove the N9 tunnel information of the specified first session.
  • S406-S407 The SMF initiates an N4 session modification flow to the UPF as the N3 end point, and instructs the UPF as the N3 end point to remove the N3 tunnel information of the specified first session.
  • the SMF sends a session context update response message to the AMF.
  • the session context update response message includes N1SM information (N1SM information refers to session-related information sent by the SMF to the UE), and the N1SM information includes user plane connection deactivation result information.
  • N1SM information refers to session-related information sent by the SMF to the UE
  • the N1SM information includes user plane connection deactivation result information.
  • the user plane connection deactivation result information indicates that the requested user plane connection of the first session is successfully deactivated or unsuccessfully deactivated.
  • the session context update response message includes N1SM information
  • the N1SM information includes a session modification accept message or a session establishment accept message
  • the session modification accept message or the session establishment accept message includes a user plane connection.
  • Activation result information where the user plane connection deactivation result information indicates that the requested user plane connection of the first session is successfully deactivated.
  • the session context update response message may also include N2 SM information (referring to information about the session sent by SMF to the RAN).
  • the N2 SM information instructs the RAN to release resources related to the first session, including the DRB and the DRB between the UE and the RAN. N3 tunnel between RAN and UPF.
  • the session context update response message includes N1SM information
  • the N1SM information includes a session modification rejection message
  • the session establishment rejection message, the session modification rejection message or the session establishment rejection message contains user plane connection deactivation result information
  • the user plane connection deactivation result information indicates that the requested user plane connection deactivation of the first session is unsuccessful.
  • the session modification rejection message or the session establishment rejection message may also contain the reason value information for the rejection of modification or rejection.
  • the reason value information may be that the first session is the session to be released, the user plane connection is not allowed to be deactivated, or the Activate the user plane connection of other sessions and so on.
  • the session modification rejection message or the session establishment rejection message may also contain the user plane connection deactivation result information indicating the success of the first session deactivation, and the session modification acceptance message or the session establishment acceptance message may contain information for The user plane connection deactivation result information indicating the unsuccessful deactivation of the first session is not limited in the embodiment of the present application.
  • S409 The AMF forwards the received N2 SM information to the RAN through the N2 interface, that is, sends a resource release command to the RAN.
  • the RAN After the RAN releases the resources, the RAN sends a resource release response to the AMF. If the resources of multiple sessions need to be released, the AMF can wait for the resource release response of all sessions to be received before sending it to the UE.
  • the AMF sends the received session modification acceptance message or session modification rejection message or session establishment acceptance message or session establishment rejection message to the UE.
  • the message includes the above-mentioned user plane connection deactivation result information, and if the above-mentioned user plane connection deactivation results
  • the information indicates that the user plane connection of the at least one first session has not been successfully deactivated, and the message may also contain information about the reason for the unsuccessful deactivation. For example, the first session is the session to be released and the user plane is not allowed to be deactivated. Connect, or deactivate the user plane connection of other sessions, etc.
  • step S412 can also be integrated in steps S409 and S410, that is, the resource release command sent by AMF to the RAN includes a session modification response message (session modification acceptance message or session modification rejection message) or a session establishment response message ( Session establishment acceptance message and session establishment rejection message), the RAN sends a session modification response message or a session establishment response message to the UE during the resource release process.
  • the resource release command sent by AMF to the RAN includes a session modification response message (session modification acceptance message or session modification rejection message) or a session establishment response message ( Session establishment acceptance message and session establishment rejection message), the RAN sends a session modification response message or a session establishment response message to the UE during the resource release process.
  • the resource release command sent by AMF to the RAN includes a session modification response message (session modification acceptance message or session modification rejection message) or a session establishment response message ( Session establishment acceptance message and session establishment rejection message), the RAN sends a session modification response message or a session establishment response message to the UE during the
  • the session processing method in this scenario includes but is not limited to the following steps:
  • the UE sends a session modification request message or a session establishment request message to the SMF.
  • the session establishment request message may include an instruction to optimize the use of the control plane (ie, instruction information), instructing the SMF to reconstruct the first session into a session optimized using the control plane CIoT and not using N3 data transmission;
  • the session modification request message may include a control plane optimization instruction (that is, instruction information), which instructs the SMF to modify the first session to a session that uses the control plane CIoT optimization and does not use N3 data transmission.
  • the session modification request message or the session establishment request message may correspond to a first session.
  • the session modification request message or the session establishment request message may include the corresponding session ID of the first session.
  • the use control plane optimization indication may be a newly added value in an existing cell.
  • the indication information may be a newly added reason value in the session modification reason value in the session modification request message.
  • the reason value is used to indicate that the first session is modified to a session optimized using the control plane.
  • the indication information may also be a newly added information element, such as a user-plane connection deactivation request (User-plane Deactivation Requested, UPDR).
  • the information element may include a bit, where the bit is 0 or 1, and the bit is used to indicate whether to modify or rebuild the first session into a session optimized using the control plane.
  • bit 0 may indicate that the first session is not to be modified or rebuilt to use the control plane optimization session, that is, the user plane connection of the first session is not to be deactivated
  • bit 1 may indicate that the first session is to be modified or rebuilt to use The control plane optimized session, that is, the user plane connection to the first session must be deactivated.
  • bit 0 indicates that the first session is modified or rebuilt as a session optimized using the control plane
  • bit 1 indicates that the first session is not modified or rebuilt as a session optimized using the control plane.
  • the embodiments of this application are not limited.
  • bit 0 indicates that the first session is not to be modified or rebuilt as a session optimized using the control plane
  • bit 1 indicates that the first session is modified or rebuilt as a session optimized using the control plane as an example.
  • bit 0 may be the default If the first session is to be modified or rebuilt as a session optimized using the control plane, the bit of the cell is set to 1.
  • the session modification request message or the session establishment request message may be included in the uplink NAS transmission message and sent to the AMF, and the AMF invokes the session context update (for example, UpdateSMContext) service operation of the SMF service interface (for example: Nsmf_PDUSession) to The SMF sends a session context update message, and the session context update message includes the above-mentioned session modification request message or session establishment request message.
  • the session context update for example, UpdateSMContext
  • the SMF service interface for example: Nsmf_PDUSession
  • the AMF can determine whether the first session can be modified or reconstructed into a session optimized using the control plane CIoT and not using N3 data transmission after receiving the control plane optimization instruction (ie, instruction information). If the control plane CIoT optimization can be used and N3 data transmission is not used, the control plane optimization instruction is sent to SMF. If the control plane CIoT optimization cannot be used and N3 data transmission is not used, the AMF sends the information sent by the UE to the UE through a downlink NAS transmission message, and carries the reason value information that cannot be forwarded.
  • the reason value information includes but is not limited to: 1. Control plane congestion. 2. The number of sessions using control plane optimization has reached the maximum. 3. The network side does not support control plane optimization. 4. Other possible causes.
  • the SMF receives the session modification request message or the session establishment request message, and according to the instruction information, modifies or reconstructs the first session into a session optimized using the control plane CIoT and not using N3 data transmission.
  • SMF is based on one of local policies, network configuration, or user subscription data Or multiple, determine to release the session, if the first session requested to be modified or rebuilt in the control plane optimization instruction (ie, instruction information) matches the session to be released by the SMF, the SMF may not modify or rebuild the first session according to the instruction information A session optimized for using the control plane CIoT and not using N3 data transmission, but waiting for the first session to be released.
  • control plane optimization instruction ie, instruction information
  • SMF determines whether the first session can be modified or reconstructed to use the control plane CIoT optimization and not use according to one or more of the local policy, network configuration, or user subscription data If it is determined that the N3 data transmission session is not possible, the SMF may not modify or rebuild the first session according to the instruction information to a session optimized using the control plane CIoT and not using N3 data transmission, and return that the first session cannot be modified Or reconstruct the cause value information of the session optimized using the control plane CIoT and not using N3 data transmission.
  • the cause value information can include but not limited to: 1. Control plane congestion; 2. The number of sessions optimized using control plane has reached the maximum 3. The network side does not support the use of control plane optimization. 4. Other possible reasons.
  • SMF determines that the user plane connection of the first session cannot be deactivated according to one or more of local policies, network configuration, or user subscription data, and deactivates other sessions.
  • the return value information of the reason why the user plane connection of the first session cannot be deactivated includes but is not limited to: 1. It is not allowed to deactivate the user plane connection, and 2. The user plane connection of other sessions is deactivated.
  • the UPF as the N3 end point can be released, or the UPF as the N3 end point will not be released.
  • the release of the UPF at the N3 end point means that after the release, the N3 tunnel of the first session no longer exists.
  • steps S502-S505 are executed; if the UPF of the N3 end point is not released, steps S506-S507 are executed, as described below.
  • S502 The SMF sends an N4 session release request to the UPF as the N3 end point.
  • the SMF initiates an N4 session modification process to the UPF of the non-N3 endpoint, and instructs the UPF of the non-N3 endpoint to remove the N9 tunnel information of the specified first session.
  • S506-S507 The SMF initiates an N4 session modification flow to the UPF as the N3 end point, and instructs the UPF as the N3 end point to remove the N3 tunnel information of the specified first session.
  • the SMF sends a session context update response message to the AMF.
  • the session context update response message contains N1SM information (N1SM information refers to session-related information sent by the SMF to the UE), and the N1SM information contains user plane connection deactivation result information.
  • the user plane connection deactivation result information indicates that the requested user plane connection of the first session is successfully deactivated or unsuccessfully deactivated.
  • successful deactivation can be understood as successfully modifying or rebuilding the first session into a session optimized using the control plane CIoT and not using N3 data transmission.
  • Unsuccessful deactivation can be understood as unsuccessful modification or reconstruction of the first session to a session optimized using the control plane CIoT and not using N3 data transmission.
  • the unsuccessful modification or reconstruction here can be understood as a local strategy.
  • User subscription data, network configuration, etc. cannot modify the first session to be reconstructed as a session optimized using the control plane CIoT and not using N3 data transmission.
  • a problem occurs in the process of modifying the first session to be reconstructed to a session optimized using the control plane CIoT and not using N3 data transmission, resulting in failure to modify or successful reconstruction.
  • the session context update response message includes N1SM information
  • the N1SM information includes a session modification accept message or a session establishment accept message
  • the session modification accept message or the session establishment accept message includes a user plane connection.
  • the user plane connection deactivation result information indicates that the requested first session is successfully modified or rebuilt into a session optimized using the control plane CIoT and not using N3 data transmission.
  • the session context update response message may also include N2 SM information (referring to information about the session sent by SMF to the RAN).
  • the N2 SM information instructs the RAN to release resources related to the first session, including the DRB and the DRB between the UE and the RAN. N3 tunnel between RAN and UPF.
  • the session context update response message includes N1SM information
  • the N1SM information includes a session modification rejection message Or session establishment rejection message, session modification rejection message or session establishment rejection message contains user plane connection deactivation result information
  • the user plane connection deactivation result information indicates that the requested first session was not successfully modified or rebuilt to use the control plane CIoT optimized sessions that do not use N3 data transmission.
  • the session modification rejection message or the session establishment rejection message may also contain the reason value information for the rejection modification or the rejection establishment.
  • the reason value information may include but is not limited to: 1. Control plane congestion; 2. Use control plane optimized sessions The number has reached the maximum. Third, the network side does not support the use of control plane optimization. Fourth, SMF must release the session. Fifth, it is not allowed to deactivate the user-plane connection. Sixth, the user-plane connection of other sessions is deactivated, etc.
  • the session modification rejection message or the session establishment rejection message may also contain the user plane connection deactivation result information indicating the success of the first session deactivation, and the session modification acceptance message or the session establishment acceptance message may contain information for The user plane connection deactivation result information indicating the unsuccessful deactivation of the first session is not limited in the embodiment of the present application.
  • the AMF forwards the received N2 SM information to the RAN through the N2 interface, that is, sends a resource release command to the RAN.
  • the RAN After the RAN releases the resources, the RAN sends a resource release response to the AMF. If the resources of multiple sessions need to be released, the AMF can wait for the resource release response of all sessions to be received before sending it to the UE.
  • the AMF sends the received session modification acceptance message or session modification rejection message or session establishment acceptance message or session establishment rejection message to the UE.
  • the message includes the above-mentioned user plane connection deactivation result information, and if the above-mentioned user plane connection deactivation results
  • the information indicates that the user plane connection of the first session has not been successfully deactivated, and the message may also contain information about the reason for the unsuccessful deactivation, for example, 1.
  • the control plane is congested; 2.
  • the number of sessions optimized using the control plane has been The maximum value is reached.
  • Third, the network side does not support the use of control plane optimization.
  • SMF must release the session. Fifth, it is not allowed to deactivate the user-plane connection. Sixth, the user-plane connection of other sessions is deactivated, and so on.
  • step S512 can also be integrated in steps S509 and S510, that is, the resource release command sent by AMF to the RAN includes a session modification response message (session modification acceptance message or session modification rejection message) or a session establishment response message ( Session establishment acceptance message and session establishment rejection message), the RAN sends a session modification response message or a session establishment response message to the UE during the resource release process.
  • the resource release command sent by AMF to the RAN includes a session modification response message (session modification acceptance message or session modification rejection message) or a session establishment response message ( Session establishment acceptance message and session establishment rejection message), the RAN sends a session modification response message or a session establishment response message to the UE during the resource release process.
  • the resource release command sent by AMF to the RAN includes a session modification response message (session modification acceptance message or session modification rejection message) or a session establishment response message ( Session establishment acceptance message and session establishment rejection message), the RAN sends a session modification response message or a session establishment response message to the UE during the resource
  • Fig. 7 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1700 may include a transceiving unit 1710 and a processing unit 1720.
  • the transceiver unit 1710 and the processing unit 1720 may be software, hardware, or a combination of software and hardware.
  • the transceiving unit 1710 may include a transmitting unit and a receiving unit.
  • the transmitting unit is used to implement the transmitting function
  • the receiving unit is used to implement the receiving function
  • the transmitting and receiving unit 1710 may implement the transmitting function and/or the receiving function.
  • the transceiver unit can also be described as a communication unit.
  • the transceiver unit 1710 may be used to receive information (or messages) sent by other devices, and may also be used to send information (or messages) to other devices.
  • the processing unit 1720 can be used to perform internal processing of the device.
  • the communication device 1700 may correspond to the terminal device (for example: UE) in the foregoing method embodiment.
  • the communication device 1700 may be a terminal device or a chip in the terminal device.
  • the communication device 1700 may include a unit for performing operations performed by the terminal device in the foregoing method embodiment, and each unit in the communication device 1700 is used to implement the operations performed by the terminal device in the foregoing method embodiment.
  • the processing unit 1720 is configured to determine to deactivate at least one user-plane connection of the first session when the number of sessions in which the terminal device has active user-plane connections is not less than the number threshold, and the user-plane connection with the active users
  • the connected session includes the at least one first session
  • the transceiver unit 1710 is configured to send a first request message to a first network element, where the first request message includes indication information, and the indication information is used to indicate to deactivate a user plane connection of the at least one first session.
  • the communication device 1700 may correspond to the session management network element (such as SMF) in the foregoing method embodiment.
  • the communication device 1700 may be a session management network element or a session management network element. Chip.
  • the communication device 1700 may include a unit for performing operations performed by the session management network element in the foregoing method embodiment, and each unit in the communication device 1700 is used to implement the operations performed by the session management network element in the foregoing method embodiment. Action performed.
  • the transceiver unit 1710 is configured to receive a request message, where the request message includes indication information, and the indication information is used to instruct the session management network element to deactivate the user plane connection of the first session, and the first The session belongs to a session in which a terminal device has an active user plane connection, and the number of sessions in which the terminal device has an active user plane connection is not less than a number threshold;
  • the processing unit 1720 is configured to deactivate the user plane connection of the first session according to the instruction information.
  • the communication device 1700 may correspond to the mobility management network element (for example, AMF) in the above method embodiment of FIG. 2.
  • the communication device 1700 may be a mobility management network element or a mobility management network. Yuan's chip.
  • the communication device 1700 may include a unit for performing the operations performed by the mobility management network element in the above-mentioned method embodiment in FIG. 2, and each unit in the communication device 1700 is used to implement the above-mentioned method embodiment by the mobility management network. The operation performed by the meta.
  • the communication apparatus 1700 may correspond to the access network equipment (for example, RAN) in the method embodiments of FIGS. 4 to 6, for example, the communication apparatus 1700 may be an access network equipment or The chip of the access network equipment.
  • the communication device 1700 may include a unit for performing the operations performed by the access network device in the above-mentioned method embodiments of FIGS. 4 to 6, and each unit in the communication device 1700 is used to implement the operations performed by the above-mentioned method embodiments. The operation performed by the access network device.
  • the transceiving unit 1710 in the communication device 1700 may correspond to the transceiver 2020 in the terminal device 2000 shown in FIG. 8, and the processing unit 1720 in the communication device 1700 may correspond to The processor 2010 in the terminal device 2000 is shown in FIG. 8.
  • the transceiver unit 1710 in the communication device 1700 may be an input/output interface.
  • the transceiver unit 1710 in the communication device 1700 may correspond to the communication interface 3010 shown in FIG. 9, and the processing unit 1720 may correspond to the communication interface 3010 shown in FIG.
  • the processor 3020 is shown.
  • FIG. 8 is a schematic structural diagram of a terminal device 2000 provided by an embodiment of the present application.
  • the terminal device 2000 can be applied to the system shown in FIG. 1 to perform the functions of the terminal device (or UE) in the foregoing method embodiment.
  • the terminal device 2000 includes a processor 2010 and a transceiver 2020.
  • the terminal device 2000 further includes a memory 2030.
  • the processor 2010, the transceiver 2002, and the memory 2030 can communicate with each other through internal connection paths to transfer control or data signals.
  • the memory 2030 is used to store computer programs, and the processor 2010 is used to call and transfer from the memory 2030. Run the computer program to control the transceiver 2020 to send and receive signals.
  • the terminal device 2000 may further include an antenna 2040 for transmitting the uplink data or uplink control signaling output by the transceiver 2020 through a wireless signal.
  • the above-mentioned processor 2010 and the memory 2030 may be combined into a processing device, and the processor 2010 is configured to execute the program code stored in the memory 2030 to realize the above-mentioned functions.
  • the memory 2030 may also be integrated in the processor 2010 or independent of the processor 2010.
  • the processor 2010 may correspond to the processing unit in FIG. 7.
  • the above-mentioned transceiver 2020 may correspond to the transceiver unit in FIG. 7.
  • the transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.
  • the terminal device 2000 shown in FIG. 8 can implement various processes involving the terminal device in any method embodiment of the foregoing method embodiments.
  • the operation or function of each module in the terminal device 2000 is to implement the corresponding process in the foregoing method embodiment.
  • the above-mentioned processor 2010 can be used to execute the actions described in the previous method embodiments implemented by the terminal device, and the transceiver 2020 can be used to execute the terminal device described in the previous method embodiments to send or receive from the network side. action.
  • the transceiver 2020 can be used to execute the terminal device described in the previous method embodiments to send or receive from the network side. action.
  • the aforementioned terminal device 2000 may further include a power supply 2050 for providing power to various devices or circuits in the terminal device.
  • the terminal device 2000 may also include one or more of an input unit 2060, a display unit 2070, an audio circuit 2080, a camera 2090, and a sensor 2100.
  • the audio circuit It may also include a speaker 2082, a microphone 2084, and so on.
  • FIG. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application. It should be understood that the communication device 3000 shown in FIG. 9 is only an example, and the communication device in the embodiment of the present application may also include other modules or units, or include modules with similar functions to the modules in FIG. All modules in 9.
  • the communication device 3000 includes a communication interface 3010 and at least one processor 3020.
  • the communication device 1900 may correspond to any network element among a session management network element, a mobility management network element, a terminal device, and an access network device.
  • At least one processor 3020 executes program instructions, so that the communication device 1900 implements the corresponding process of the method executed by the corresponding network element in the foregoing method embodiment.
  • the communication device 1900 may further include a memory.
  • the memory can store program instructions, and at least one processor 3020 can read the program instructions stored in the memory and execute the program instructions.
  • the communication device can be a chip or a chip system
  • the chip 900 shown in FIG. 10 includes a processor 901 and an interface 902.
  • the number of processors 901 may be one or more, and the number of interfaces 902 may be multiple.
  • the respective functions of the processor 901 and the interface 902 may be implemented through hardware design, may also be implemented through software design, or may be implemented through a combination of software and hardware, which is not limited here.
  • the processor 901 is used when the terminal device has the number of active user-plane connection sessions not less than the number threshold , Determining to deactivate the user plane connection of the at least one first session, and the session with the activated user plane connection includes the at least one first session.
  • the interface 902 is configured to send a first request message to the first network element, where the first request message includes instruction information, and the instruction information is used to instruct to deactivate the user plane connection of the at least one first session.
  • the chip further includes a memory 903, and the memory 903 is used to store necessary program instructions and data for the terminal device.
  • the interface 902 is used to receive a request message, the request message includes indication information, and the indication information is used to instruct the session management network element to
  • the user plane connection of a session is deactivated, the first session belongs to a session in which a terminal device has an active user plane connection, and the number of sessions in which the terminal device has an active user plane connection is not less than a number threshold.
  • the processor 901 is configured to deactivate the user plane connection of the first session according to the instruction information.
  • the chip further includes a memory 903, and the memory 903 is used to store program instructions and data necessary for the session management network element.
  • the processor in the embodiment of the present application may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), and application specific integrated circuits (application specific integrated circuits). integrated circuit, ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes any of the foregoing method embodiments The method on the terminal equipment side or the method on the access and mobility management network side or the method on the session management network element side.
  • a communication system in another embodiment, includes a terminal device and a session management network element.
  • the communication system includes a terminal device, a session management network element, and a mobility management network element.
  • the communication system includes a terminal device, a session management network element, a mobility management network element, and an access network device.
  • the terminal device may be the terminal device provided in FIG. 2 to FIG. 6, and is used to execute the steps of the terminal device in the session processing method provided in FIG. 2 to FIG. 6; and/or, the session management network element may be The session management network element provided in FIGS. 2 to 6 is used to perform the steps of the session management network element in the session processing method provided in FIGS. 2 to 6.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the method in any of the foregoing method embodiments.
  • the aforementioned processing device may be a chip.
  • the processing device may be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (digital signal processor, DSP), or an application specific integrated circuit (ASIC). , Ready-made programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, or system on chip (SoC), or central processing
  • the central processor unit (CPU) can also be a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (microcontroller unit, MCU) It can also be a programmable logic device (PLD) or other integrated chips.
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller unit
  • PLD programmable logic device
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disc), SSD)) etc.
  • the network equipment in each of the above-mentioned device embodiments corresponds completely to the network equipment or terminal equipment in the terminal equipment and method embodiments, and the corresponding modules or units execute the corresponding steps.
  • the communication unit executes the receiving or the terminal equipment in the method embodiments.
  • the processing unit executes the functions of specific units, refer to the corresponding method embodiments. Among them, there may be one or more processors.
  • a component may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, or a computer running on the processor.
  • the application running on the computing device and the computing device can be components.
  • One or more components can reside in a process or thread of execution, and the components can be located on one computer or distributed between two or more computers.
  • these components can be executed from various computer readable media having various data structures stored thereon.
  • a component can pass a local signal based on a signal having one or more data packets (for example, data from two components that interact with another component in a local system, a distributed system, or a network, such as the Internet that interacts with other systems through a signal). Or remote process to communicate.
  • a signal having one or more data packets for example, data from two components that interact with another component in a local system, a distributed system, or a network, such as the Internet that interacts with other systems through a signal.
  • remote process to communicate for example, data from two components that interact with another component in a local system, a distributed system, or a network, such as the Internet that interacts with other systems through a signal.
  • a corresponding to B means that B is associated with A, and B can be determined according to A.
  • determining B based on A does not mean that B is determined only based on A, and B can also be determined based on A and/or other information.
  • the session management network element and/or terminal device can perform some or all of the steps in the embodiment of this application. These steps or operations are only examples, and the embodiment of this application can also perform other operations or Variations of various operations. In addition, each step may be executed in a different order presented in the embodiments of the present application, and it may not be necessary to perform all the operations in the embodiments of the present application.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read only memory ROM, random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请实施例提供一种会话处理方法及装置，其中，会话处理方法包括：在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接，所述具有激活的用户面连接的会话包括所述至少一个第一会话；所述终端设备向第一网元发送第一请求消息，所述第一请求消息包括指示信息，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活。采用本申请实施例，可以减少信令浪费，缩短业务建立时延。

Description

会话处理方法及通信装置
本申请要求于2020年1月23日提交中国专利局、申请号为202010077054.3、申请名称为“会话处理方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种会话处理方法及通信装置。
背景技术
窄带物联网(Narrow Band Internet of Things，NB-IoT)是一种低功耗广覆盖网络无线技术标准，NB-IoT具有低功耗、广覆盖、低成本、大容量等优势，可以广泛的应用于多种垂直行业。通常接入NB-IoT的终端设备最多允许一定数量的会话具有激活的用户面连接(User Plane connection，UP connection)，激活的用户面连接指的是接入网和用户面核心网网元为该会话建立的各种用户面资源，用来实现用户数据通过所建立的用户资源进行传输。激活的用户面连接包括无线接入网(Radio Access Network，RAN)和用户面功能网元(User Plane Function，UPF)等为该会话建立的各种用户面资源，包括但不限于RAN为该会话建立的数据无线承载(Data Radio Bearer，DRB)，RAN和UPF为该会话建立的N3隧道。激活的用户面连接还包括N3互通功能网元(Non-3GPP InterWorking Function，N3IWF)或可信非3GPP网关功能网元(Trusted Non-3GPP Gateway Function，TNGF)和用户面功能网元(User Plane Function，UPF)等为该会话建立的各种用户面资源，包括但不限于N3IWF或TNGF为该会话建立的空口隧道，N3IWF或TNGF和UPF为该会话建立的N3隧道。现有技术中，终端设备具有激活的用户面连接的会话的数量达到数量阈值且终端设备期望激活其他会话的用户面连接时，则终端设备选择一个或多个具有激活的用户面连接的会话进行释放，从而降低具有激活的用户面连接的会话的数量。将会话释放，则后续再使用该会话的用户面连接时还需要重新建立会话，浪费信令，增加业务建立的时延。
除了窄带物联网，在其它商用的蜂窝网络或无线网络中，基于运营商对于空口资源的限制，也存在针对终端设备的最大激活的用户面连接的会话的数量的限制需求，在终端设备具有激活的用户面连接的会话的数量达到数量阈值且终端设备期望激活其他会话的用户面连接时，则终端设备选择一个或多个具有激活的用户面连接的会话进行释放，从而降低具有激活的用户面连接的会话的数量。将会话释放，则后续再使用该会话的用户面连接时还需要重新建立会话，浪费信令，增加业务建立的时延。
发明内容
本申请实施例提供了一种会话处理方法及通信装置，能够避免重建会话所导致的信令浪费和业务建立时延增加的问题。
第一方面，本申请实施例提供了一种会话处理方法，其中，该方法可以由终端设备执行，也可以由终端设备的部件(例如处理器、芯片、或芯片系统等)执行。该会话处理方 法可以包括：在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，该终端设备确定去激活至少一个第一会话的用户面连接，其中，具有激活的用户面连接的会话包括少一个第一会话。
可选的，终端设备在具有激活的用户面连接的会话中确定去激活的至少一个第一会话时，可以根据会话的功能进行选择，例如，如果某个具有激活的用户面连接的会话是用于发送异常数据报告的，则终端设备不能选择该会话进行用户面连接去激活。
终端设备向第一网元发送第一请求消息，该第一请求消息包括指示信息，指示信息用于指示将至少一个第一会话的用户面连接去激活。
相应的，会话管理网元根据该指示信息，将第一会话的用户面连接去激活。
通过实施本申请实施例，在终端设备具有激活的用户面连接的会话的数量不小于数量阈值时，可以通过去激活至少一个第一会话的用户面连接的方式，降低终端设备具有激活的用户面连接的会话的数量，而如果通过去激活会话的方式来降低终端设备具有激活的用户面连接的数量，再次使用该会话的用户面连接来传输数据时，不仅要激活用户面连接，还要重建会话，导致信令浪费，增加业务建立的时延，因此，采用本申请实施例的去激活用户面连接的方式可以避免去激活会话所导致的信令浪费和业务建立时延增加的问题。
在一种可能的设计中，该终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，终端设备确定去激活至少一个第一会话的用户面连接，可以包括：在所述终端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络，且终端设备具有激活的用户面连接的会话的数量大于数量阈值的情况下，该终端设备确定去激活至少一个第一会话的用户面连接。
可选的，终端设备具有激活的用户面连接的会话的数量大于数量阈值，则终端设备可以将大于数量阈值的部分会话作为去激活的至少一个第一会话，从而使得去激活至少一个第一会话后，该终端设备具有激活的用户面连接的会话的数量等于数量阈值。例如，终端设备具有激活的用户面连接的会话的数量为5，数量阈值为2，则终端设备可以将3个会话作为上述至少一个第一会话，并将该3个第一会话的用户面连接去激活。
可以理解的是，终端设备也可以将至少一个第一会话的用户面连接去激活之后，该终端设备具有激活的用户面连接的会话的数量小于数量阈值，本申请实施例不作限定。
通过实施本申请实施例，可以在终端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络场景下，终端设备具有激活的用户面连接的会话的数量大于数量阈值时，将至少一个第一会话的用户面连接去激活，达到降低该终端设备具有激活的用户面连接的会话的数量。
在一种可能的设计中，该终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，终端设备确定去激活至少一个第一会话的用户面连接，可以包括：在终端设备具有激活的用户面连接的会话的数量不小于数量阈值，例如，终端设备具有激活的用户面连接的会话的数量大于或者等于数量阈值，且终端设备确定为至少一个第二会话激活用户面连接的情况下，该终端设备确定去激活至少一个第一会话的用户面连接，该至少一个第二会话为不具有激活的用户面连接的会话。
可选的，若该第二会话是用于发送异常数据报告的会话，则终端设备要去激活第一会 话的用户面连接，以为第二会话激活用户面连接。
在一种可能的设计中，端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络，该终端设备具有激活的用户面连接的会话的数量大于数量阈值，该终端设备可以将具有激活的用户面连接的会话中大于数量阈值的部分会话的用户面连接去激活，例如，终端具有激活的用户面连接的会话数量为5，数量阈值为2，则终端设备可以选择去激活3个第一会话的用户面连接。去激活3个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量为2，即等于数量阈值。然后，终端设备接收到上层请求，用于请求为至少一个第二会话激活用户面连接(例如可以请求为2个第二会话激活用户面连接)，此时终端设备进一步请求去激活至少一个第一会话的用户面连接(例如可以请求去激活2个第一会话的用户面连接，或者也可以请求去激活大于2个第一会话的用户面连接)，从而满足去激活至少一个第一会话的用户面连接，以及激活至少一个第二会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量小于或者等于数量阈值。
在一种可能的设计中，指示信息指示将至少一个第一会话的用户面连接去激活的指示方式包括但不限于：指示将该至少一个第一会话修改为使用控制面优化的会话，或者指示将该至少一个第一会话修改为不建立用户面连接的会话等等。
通过实施本申请实施例，可以通过将至少一个第一会话修改为使用控制面优化的会话的方式，达到去激活该至少一个第一会话的用户面连接的目的，从而降低该终端设备具有激活的用户面连接的会话的数量。
在一种可能的设计中，终端设备可以向移动管理网元发送该第一请求消息，其中，该第一请求消息可以是终端设备在移动管理流程中发送的请求消息，例如，该第一请求消息可以为注册请求消息或者服务请求消息。
可选的，在终端设备从通过非窄带物联网接入网络切换为通过窄带物联网接入网络时，该终端设备具有激活的用户面连接的会话的数量大于数量阈值，该终端设备可以发送注册请求消息，该注册请求消息可以包括指示信息，该指示信息用于指示将至少一个第一会话的用户面连接去激活。
可选的，终端设备具有激活的用户面连接的会话的数量大于或者等于数量阈值，且终端设备确定为至少一个第二会话激活用户面连接时，该终端设备可以发送服务请求消息，该服务请求消息可以包括指示信息，该指示信息用于指示将至少一个第一会话的用户面连接去激活。
可以理解的是，上述至少一个第一会话可以是至少一个会话管理网元管理的会话，移动管理网元向对应的会话管理网元请求去激活相应的第一会话的用户面连接。例如，终端设备请求去激活会话1的用户面连接和会话2的用户面连接，会话管理网元1用于管理会话1，会话管理网元2用于管理会话2，则移动管理网元请求会话管理网元1去激活会话1的用户面连接，移动管理网元请求会话管理网元2去激活会话2的用户面连接。
通过实施本申请实施例，可以在移动管理流程中发送第一请求消息，并请求去激活一个或者多个第一会话的用户面连。该一个第一会话或者多个第一会话可以涉及至少一个会话管理网元，即通过移动管理流程可以请求去激活多个会话管理网元管理的第一会话的用户面连接，提高用户面连接的去激活效率。
在一种可能的设计中，终端设备可以向会话管理网元发送该第一请求消息，其中，该第一请求消息可以是终端设备在会话管理流程中发送的请求消息，例如，该第一请求消息可以为会话修改请求消息或者会话建立请求消息。可以理解的是，第一请求消息也可以是会话管理流程中的其他类型消息，本申请实施例不作限定。
通过实施本申请实施例，终端设备向会话管理网元请求去激活至少一个第一会话的用户面连接，减少移动管理网元的处理流程，减轻移动管理网元的负载。
在一种可能的设计中，该终端设备可以是通过窄带物联网接入网络。
在一种可能的设计中，去激活用户面连接的至少一个第一会话中不包括用于发送异常数据报告的会话。
第二方面，本申请实施例提供了一种会话处理方法，其中，该方法可以由会话管理网元执行，也可以由会话管理网元的部件(例如处理器、芯片、或芯片系统等)执行。该会话处理方法可以包括：会话管理网元接收请求消息，该请求消息可以是终端设备发送的第一请求消息，或者是移动管理网元在接收到终端设备发送的第一请求消息后，向会话管理网元发送的第二请求消息。
请求消息中包括指示信息，该指示信息用于指示会话管理网元将第一会话的用户面连接去激活。可选的，该指示信息可以指示将一个第一会话或者多个第一会话的用户面连接去激活。
该第一会话是属于终端设备具有激活的用户面连接的会话，其中，该终端设备具有激活的用户面连接的会话的数量不小于数量阈值。例如，终端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络，该终端设备具有激活的用户面连接的会话的数量大于数量阈值。或者，终端设备具有激活的用户面连接的会话的数量大于或者等于数量阈值，该终端设备确定为至少一个第二会话激活用户面连接。
会话管理网元，根据指示信息，将相应的第一会话的用户面连接去激活。
通过实施本申请实施例，在终端设备具有激活的用户面连接的会话的数量不小于数量阈值时，可以通过去激活至少一个第一会话的用户面连接的方式，降低终端设备具有激活的用户面连接的会话的数量，而如果通过去激活会话的方式来降低终端设备具有激活的用户面连接的数量，再次使用该会话的用户面连接来传输数据时，不仅要激活用户面连接，还要重建会话，导致信令浪费，增加业务建立的时延，因此，采用本申请实施例的去激活用户面连接的方式可以避免去激活会话所导致的信令浪费和业务建立时延增加的问题。
在一种可能的设计中，若指示信息用于指示将第一会话修改为使用控制面优化的会话，则会话管理网元根据指示信息，将相应的第一会话修改为使用控制面优化的会话。
通过实施本申请实施例，可以通过将至少一个第一会话修改为使用控制面优化的会话的方式，达到去激活该至少一个第一会话的用户面连接的目的，从而降低该终端设备具有激活的用户面连接的会话的数量。
在一种可能的设计中，该请求消息可以是来自于移动管理网元，即移动管理网元接收到终端设备的第一请求消息后，向会话管理网元发送第二请求消息，该第二请求消息即是该实施例的请求消息。该请求消息包括指示信息，该指示信息用于指示将第一会话的用户面连接去激活，该第一会话是该会话管理网元所管理的会话。
可选的，该请求消息可以是会话上下文更新消息。
在一种可能的设计中，该请求消息可以是来自于终端设备，终端设备可以在会话管理流程中向会话管理网元发送请求消息，该请求消息可以是会话管理流程中的请求消息类型。
可选的，该请求消息可以为会话建立请求消息或者会话修改请求消息。
在一种可能的设计中，会话管理网元根据指示信息，将第一会话的用户面连接去激活之前，该方法还可以包括：该会话管理网元根据本地策略、网络位置或用户签约数据中的一种或多种，确定将第一会话的用户面连接去激活。
可选的，会话管理网元也可能根据本地策略、网络位置或用户签约数据中的一种或多种，确定不能将第一会话的用户面连接去激活。例如，该第一会话是会话管理网元要释放的会话，或者，由于控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化导致不能将第一会话修改为使用控制面优化的会话，或者该第一会话不能去激活，会话管理网元确定将其他会话的用户面连接去激活等等。示例性的，终端设备请求将会话1的用户面连接去激活，而会话管理网元确定不能将会话1的用户面连接去激活，而将会话2的用户面连接去激活。
通过实施本申请实施例，会话管理网元可以通过多种方式确定是否能够将第一会话的用户面连接去激活，从而满足多种场景需求。
在一种可能的设计中，会话管理网元发送响应消息，该响应消息包括第一会话的用户面连接去激活结果信息，用户面连接去激活结果信息指示第一会话的用户面连接去激活成功或者去激活未成功。可以理解的是，若终端设备请求去激活多个第一会话的用户面连接，则该响应消息可以包括多个第一会话的用户面连接去激活结果信息。
可选的，若终端设备请求去激活多个第一会话的用户面连接，会话管理网元也可以分多次发送响应消息，一个响应消息指示一个第一会话的用户面连接去激活结果信息。
示例性的，会话管理网元可以向移动管理网元发送响应消息，并由移动管理网元向终端设备发送该第一会话的用户面连接去激活结果信息。该场景下响应消息可以是会话上下文更新响应消息。
示例性的，会话管理网元也可以向终端设备发送响应消息，该响应消息包括用户面连接去激活结果信息。该场景下响应消息可以是会话修改响应消息或者会话建立响应消息等等。
在一种可能的设计中，若用户面连接去激活结果信息指示第一会话的用户面连接去激活未成功，该响应消息还包括用户面连接去激活未成功的原因值信息。
在一种可能的设计中，原因值信息包括以下信息中的一种或者多种：控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化、不允许去激活用户面连接、为要释放的会话或者去激活其它会话的用户面连接。
通过实施本申请实施例，可以让终端设备获知用户面连接未去激活成功的原因。
第三方面，本申请实施例提供了一种通信装置，包括用于执行第一方面或者第二方面的方法的各个模块或单元。
第四方面，本申请实施例提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面或者第二方面的方法。可选地，该通信 装置还包括存储器。可选地，该通信装置还包括通信接口，处理器与通信接口耦合。
第五方面，本申请实施例提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面或者第二方面的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第六方面，本申请实施例提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面或者第二方面的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送请求消息可以为从处理器输出请求消息的过程，接收消息可以为处理器接收消息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第六方面中的处理装置可以是一个或多个芯片。该处理装置中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第七方面，本申请实施例提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面或者第二方面的方法。
第八方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面或者第二方面的方法。
第九方面，本申请实施例提供了一种通信系统，包括前述终端设备和会话管理网元。
可选的，该通信系统还可以包括移动管理网元。
第十方面，提供了一种芯片系统，该芯片系统包括处理器和接口，处理器用于从存储器中调用并运行存储器中存储的计算机程序(也可以称为代码，或指令)，以实现第一方面或者第二方面所涉及的功能，在一种可能的设计中，该芯片系统还包括存储器，存储器用于保存必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分 立器件。
附图说明
图1是本申请实施例提供的一种5G系统架构图；
图2是本申请实施例提供的一种会话处理方法的流程示意图；
图3是本申请实施例提供的另一种会话处理方法的流程示意图；
图4是本申请实施例提供的一种移动管理流程去激活用户面连接的示意性流程图；
图5是本申请实施例提供的一种会话管理流程去激活用户面连接的示意性流程图；
图6是本申请实施例提供的另一种会话管理流程去激活用户面连接的示意性流程图；
图7是本申请实施例提供的通信装置的示意性框图；
图8是本申请实施例提供的终端设备的结构示意图；
图9是本申请实施例提供的另一通信装置的示意性框图；
图10是本申请实施例提供的一种芯片的结构示意图。
具体实施方式
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、通用移动通信系统(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)系统、新无线(new radio，NR)以及随着技术的发展出现的其他新的系统等。
图1示出了一种可以应用于本申请的5G系统的示意图。如图1所示，该系统可以分为接入网和核心网两部分。接入网用于实现无线接入有关的功能，主要包括接入网络(access network，AN)设备102，接入网络设备包括了无线接入网络(radio access network，RAN)设备以及其它通过空口接入的设备(比如WiFi)。核心网主要包括以下几个关键逻辑网元：用户面功能(user plane function)103、接入及移动管理功能(access and mobility management function，AMF)105、会话管理功能(session management function)106、策略控制功能(policy control function，PCF)107、统一数据管理功能(unified data management)109。该系统100还可以包括用户设备(user equipment，UE)101、数据网络(data network，DN)104和应用功能(application function，AF)108。各网元之间的接口如图1中所示。应理解，网元之间还可以采用服务化接口进行通信。
UE，也可以称为终端设备。终端设备可以经AN设备与一个或多个核心网(core network，CN)进行通信。终端设备可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置。终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless localloop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备或物联网、车辆网中的终端设备以及未来网络中的任意形态的终端设备等。
AN设备，是一种将终端设备接入到无线网络的设备，具体可以为基站。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。具体可以为： 无线局域网(wireless local area network，WLAN)中的接入点(access point，AP)，全球移动通信系统(global system for mobile communications，GSM)或码分多址接入(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolved Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及5G系统中的下一代节点B(the next generation Node B，gNB)或者未来演进的公用陆地移动网(public land mobile network，PLMN)网络中的基站等。
UDM，具备管理用户的签约数据，生成用户的认证信息等功能。
AMF，主要负责UE的注册管理、UE的连接管理、UE的可达性管理、UE的接入授权和接入鉴权、UE的安全功能，UE的移动性管理，网络切片(network slice)选择，SMF选择等功能。AMF作为N1/N2接口信令连接的锚点并为SMF提供N1/N2接口会话管理(session management，SM)消息的路由，维护和管理UE的状态信息。AMF是5G系统中的一种移动管理网元。
SMF，主要负责UE会话管理的所有控制面功能，包括UPF的选择与控制，网络互连协议(internet protocol，IP)地址分配及管理，会话的服务质量(quality of service，QoS)管理，从PCF获取策略与计费控制(policy and charging control，PCC)策略等。SMF还作为非接入层(non-access stratum，NAS)消息中SM部分的终结点。
PCF，具备向控制面功能实体提供策略规则等功能。
AF，可以是应用服务器，其可以属于运营商，也可以属于第三方。
UPF，主要负责对用户报文进行处理，如转发、计费等，可以作为协议数据单元(protocol data unit，PDU)会话(session)连接的锚定点，即PDU会话锚点(PDU session anchor，PSA)，负责对UE的数据报文过滤、数据传输/转发、速率控制、生成计费信息、用户面QoS处理、上行传输认证、传输等级验证、下行数据包缓存及下行数据通知触发等。UPF还可以作为多宿主(multi-homed)PDU会话的分支点。
DN，为用户提供数据传输服务的网络，例如，IP多媒体业务(IP Multi-media service,IMS)、互联网等。DN中可以包括应用服务器(application server，AS)，AS是一种软件框架，提供一个应用程序运行的环境，用于为应用程序提供安全、数据、事务支持、负载平衡大型分布式系统管理等服务。UE通过与AS通信获取应用报文。需要说明的是，上述AF为AS的控制面。
应理解，本申请实施例并不限定只应用于图1所示的系统架构中。例如，可以应用本申请实施例的会话管理方法的通信系统中可以包括更多或更少的网元或设备。图1中的设备或网元可以是硬件，也可以是从功能上划分的软件或者以上二者的结合。图1中的设备或网元之间可以通过其他设备或网元通信。
在详细介绍本申请的方法之前，首先对本申请涉及的一些概念作简单介绍。
本申请实施例的用户面连接(User Plane connection，UP connection)可以被称为用户面资源(user-plane resources)，空口承载资源(radio bearer resources)，数据无线资源(data radio resources)、数据无线承载(data radio bearer)等等，指终端设备和UPF之间建立的资 源。可选的，用户面连接可以由DRB和/或N3隧道构成。DRB可以是指接入网设备与终端设备之间的数据无线承载，N3隧道可以是指接入网设备与用户面功能网元之间所建立的数据传输隧道。其中，用户面连接可以用于传输数据。
本申请实施例中，具有激活的用户面连接的会话可以理解为该会话建立了用户面连接。为会话激活用户面连接可以理解为给该会话建立用户面连接。
本申请实施例的将会话的用户面连接去激活可以称为将会话的用户面连接释放(release)，其中，将会话的用户面连接去激活可以理解为将该会话的用户面连接的资源释放。
本申请实施例中的会话可以是协议数据单元(Protocol Data Unit，PDU)会话，还可以是其他会话，本申请实施例不作限定。
本申请实施例中的使用控制面优化的会话可以是为控制面CIoT优化建立的PDU会话(例如：PDU session(s)established for control plane CIoT Optimization)或者是使用控制面CIoT优化的PDU会话(例如：use Control Plane CIoT Optimization for the PDU session(s)，或者,PDU session(s)using Control Plane CIoT Optimization)，或者还可以是使用控制面传输数据的会话。其中，使用控制面优化的会话不建立用户面连接，即使用控制面优化的会话不使用用户面资源进行数据传输。
窄带物联网NB-IoT是一种无线接入技术(Radio Access Technology，RAT)类型。NB-IoT允许通过低于200kHZ的信道带宽的演进的UTRA(Evolved UTRA，E-UTRA)接入网络。
本申请实施例中的异常数据报告是使用蜂窝物联网(CellularInternet of Things，CIoT)特性的UE发出的一种异常事件报告，也可称为异常报告。
本申请实施例中的使用用户面CIoT优化是指UE在进入空闲态时，无线资源控制(Radio Resource Control，RRC)连接可以被挂起，UE和RAN保存接入层(Access Stratum，AS)上下文等信息，当空闲态进入连接态时，不需要建立AS上下文。
其中，处于连接态的UE具有通过N1接口建立的与AMF之间的非接入层(Non Access Stratum，NAS)信令连接。处于空闲态的UE没有通过N1接口建立的与AMF之间的NAS信令连接。处于空闲态的UE没有AN信令连接，N2连接和N3连接。
可选的，终端设备具有激活的用户面连接的会话的数量不小于数量阈值时，该终端设备可以向移动管理网元发送第一请求消息，该第一请求消息包括指示信息，该指示信息用于指示将至少一个第一会话的用户面连接去激活，该移动管理网元确定用于管理该至少一个第一会话的至少一个会话管理网元，并向对应的会话管理网元发送第二请求消息(也可以被称为请求消息)，该第二请求消息包括指示信息，该指示信息用于指示将第一会话的用户面连接去激活，相应的，会话管理网元根据指示信息，将第一会话的用户面连接去激活。具体请参照后续图2实施例的描述，暂不赘述。
可选的，终端设备具有激活的用户面连接的会话的数量不小于数量阈值时，该终端设备可以向会话管理网元发送第一请求消息，该第一请求消息包括指示信息，该指示信息用于指示将至少一个第一会话的用户面连接去激活。相应的，会话管理网元接收该第一请求 消息(也可以被称为请求消息)，并根据指示信息，将第一会话的用户面连接去激活。具体请参照后续图3实施例的描述，暂不赘述。
下面分别结合附图2和附图3对本申请实施例的会话处理方法进行阐述，其中，图2可以是终端设备向移动管理网元发送第一请求消息，用于指示将至少一个第一会话的用户面连接去激活，例如，终端设备通过移动管理流程请求去激活至少一个第一会话的用户面连接。图3可以是终端设备向会话管理网元发送第一请求消息，用于指示将至少一个第一会话的用户面连接去激活，例如，终端设备通过会话管理流程请求去激活至少一个第一会话的用户面连接。
请参照图2，为本申请实施例提供的一种会话处理方法的流程示意图，在本申请实施例中，第一网元可以是移动管理网元，如图所示，本申请实施例的会话处理方法包括但不限于以下步骤：
S100，在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接，所述具有激活的用户面连接的会话包括所述至少一个第一会话；
在一个实施例中，终端设备可以是通过窄带物联网NB-IoT接入网络。其中，具有激活的用户面连接的会话的数量不小于数量阈值可以是，具有激活的用户面连接的会话的数量大于数量阈值，或者等于数量阈值，数量阈值可以是协议定义的终端设备通过窄带物联网接入网络时，最多允许的具有激活的用户面连接的会话的数量，例如，可以是2或者3等等。要去激活用户面连接的至少一个第一会话具有激活的用户面连接。
在第一种可选的实施方式中，终端设备具有激活的用户面连接的会话的数量已经达到最大值(例如可以是等于数量阈值，或者大于数量阈值)时，终端设备的上层请求为至少一个第二会话激活用户面连接，该至少一个第二会话不具有激活的用户面连接，则终端设备确定去激活至少一个第一会话的用户面连接。可选的，终端设备可以根据具有激活的用户面连接的会话的数量、至少一个第二会话的数量以及数量阈值，确定去激活用户面连接的至少一个第一会话的数量，以满足激活至少一个第二会话的用户面连接，以及去激活至少一个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量小于或者等于数量阈值。
例如，终端设备具有激活的用户面连接的会话的数量为3，数量阈值是3，要激活2个第二会话的用户面连接，则可以将2个第一会话的用户面连接去激活，以满足激活至少一个第二会话的用户面连接，以及去激活至少一个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量为3，即等于数量阈值3。或者，也可以将3个第一会话的用户面连接去激活，以满足激活至少一个第二会话的用户面连接，以及去激活至少一个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量为2，即小于数量阈值3，对此本申请实施例不作限定。
在第二种可选的实施方式中，终端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络，该终端设备具有激活的用户面连接的会话的数量大于数量阈值，终端设备可以选择去激活至少一个第一会话的用户面连接，从而使得该终端设备具有激活的用户面连接的会话的数量小于或等于数量阈值。可选的，终端设备可以根据具有激活的用户面 连接的会话的数量以及数量阈值，确定去激活用户面连接的至少一个第一会话的数量，以满足去激活至少一个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量小于或者等于数量阈值。
例如，终端设备具有激活的用户面连接的会话的数量为3，数量阈值是2，则将1个第一会话的用户面连接去激活，以满足去激活至少一个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量为2，即等于数量阈值。或者，也可以将2个第一会话的用户面连接的去激活，以满足去激活至少一个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量为1，即小于数量阈值2，对此本申请实施例不作限定。
在一些可能的场景中，可以结合第一种可选的实施方式和第二种可选的实施方式，确定去激活的至少一个第一会话的用户面连接。例如，终端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络，该终端设备具有激活的用户面连接的会话的数量大于数量阈值，该终端设备可以将具有激活的用户面连接的会话中大于数量阈值的部分会话的用户面连接去激活，例如，终端具有激活的用户面连接的会话数量为5，数量阈值为2，则终端设备可以选择去激活3个第一会话的用户面连接。去激活3个第一会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量为2，即等于数量阈值。然后，终端设备接收到上层请求，用于请求为至少一个第二会话激活用户面连接(例如可以请求为2个第二会话激活用户面连接)，此时终端设备进一步请求去激活至少一个第一会话的用户面连接(例如可以请求去激活2个第一会话的用户面连接)，从而满足去激活至少一个第一会话的用户面连接，以及激活至少一个第二会话的用户面连接之后，该终端设备具有激活的用户面连接的会话的数量小于或者等于数量阈值。
可选的，终端设备在具有激活的用户面连接的会话中确定去激活的至少一个第一会话时，可以根据会话的功能进行选择，例如，如果某个具有激活的用户面连接的会话是用于发送异常数据报告的，则终端设备不能选择该会话进行用户面连接去激活。
可选的，如果要建立用户面连接(或者要激活用户面连接)的第二会话是用于发送异常数据报告的，则终端设备必须选择去激活一个或多个第一会话的用户面连接。
示例性的，在一些可能的场景中，例如终端设备从通过非窄带物联网接入网络切换为通过窄带物联网接入网络时，会话管理网元可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定释放一个或多个会话，并向终端设备发送释放指令，该释放指令指示是否重建所释放的会话。本申请实施例中，终端设备具有激活的用户面连接的会话可以包括会话管理网元确定释放且重建的会话和会话管理网元保留的会话，会话管理网元确定释放且重建的会话和会话管理网元保留的会话可以均具有激活的用户面连接。其中，会话管理网元保留的会话是指会话管理网元确定不释放的会话。可以理解的是，在该场景下，后续请求去激活的至少一个第一会话可以是会话管理网元确定释放且重建的会话和/或会话管理网元保留的会话。
S101，所述终端设备向移动管理网元发送第一请求消息，所述第一请求消息包括指示信息，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活。
一种可能的设计中，该指示信息可以是会话用户面连接去激活列表信息(List Of PDU  Sessions To Be Deactivated)，该会话用户面连接去激活列表信息包括会话标识(Identity，ID)列表，该会话ID列表包括至少一个第一会话的会话ID，其中，该会话ID列表用于表示去激活对应会话的用户面连接。其中，上述会话用户面连接去激活列表信息可以是已有信元中新增加的值，也可以是新增加的一种信元。
在另一种可能的设计中，该指示信息可以是比特信息。若要去激活一个第一会话的用户面连接，则该指示信息包括一个比特。若要去激活多个第一会话的用户面连接，则该指示信息可以包括多个比特，该多个比特可以构成比特集合或者比特列表。其中，一个比特对应一个第一会话。
可选的，比特0可以指示对应第一会话的用户面连接不去激活，比特1可以指示对应第一会话的用户面连接要去激活。当然，也可以是比特0指示对应第一会话的用户面连接要去激活，比特1表示对应第一会话的用户面连接不去激活，本申请实施例不作限定。
下面以比特0指示对应第一会话的用户面连接不去激活，比特1指示对应第一会话的用户面连接要去激活作为举例。例如，在5G系统中，终端设备最多可以有15个会话，如表一所示，PDU会话ID(PDU Session Identity，PSI)(1)对应会话ID为1的会话，PSI(2)对应会话ID为2的会话，以此类推。若终端设备具有激活的用户面连接的会话的数量是3，数量阈值是2，若UE请求去激活一个第一会话的用户面连接，例如，要去激活会话ID为1的会话，则将表一中的PSI(1)的比特设置为1，可选的，其余比特设置为0。示例性的，比特0可以是默认值，则可以将PSI(1)的比特设置为1即可。若终端设备具有激活的用户面连接的会话的数量是5，数量阈值是3，若UE请求去激活两个第一会话的用户面连接，例如，要去激活会话ID为1的会话和ID为2的会话，则将表一中的PSI(1)和PSI(2)的比特设置为1，可选的，其余比特设置为0。示例性的，比特0可以是默认值，则可以将PSI(1)和PSI(2)的比特设置为1即可。
表一
PSI(7) PSI(6) PSI(5) PSI(4) PSI(3) PSI(2) PSI(1) PSI(0)
PSI(15) PSI(14) PSI(13) PSI(12) PSI(11) PSI(10) PSI(9) PSI(8)
其中，第一请求消息可以是终端设备在移动管理流程中发送的请求消息，移动管理流程包括但不限于服务请求流程和注册更新(registration update)流程，下面分别举例阐述。
示例性的，第一请求消息可以是服务请求流程中的服务请求(service request)消息。例如，终端设备具有激活的用户面连接的会话的数量已经达到最大值(即具有激活的用户面连接的会话的数量等于或者大于数量阈值)时，该终端设备的上层请求为至少一个第二会话激活用户面连接，终端设备可以选择去激活一个或多个第一会话的用户面连接。此时，终端设备发起服务请求流程，即向移动管理网元发送服务请求消息，该服务请求消息中包含用户面连接去激活指示(即指示信息)，该用户面连接去激活指示用于指示去激活一个或多个第一会话的用户面连接。可以理解的是，该用户面连接去激活指示可以是服务请求消息中已有的信息元素(Information element，IE)中的新功能，也可以是服务请求消息中新增加的IE，本申请不做限定。
示例性的，第一请求消息可以是注册更新流程中的注册请求(registration request)消息，注册更新流程也称为移动注册更新(mobility registration update)流程。例如，终端设备从 通过非窄带物联网接入网络切换为通过窄带物联网接入网络时，可以发起注册更新流程。若终端设备具有激活的用户面连接的会话的数量超过了数量阈值，终端设备可以选择去激活一个或多个第一会话的用户面连接，从而使得终端设备具有激活的用户面连接的会话的数量小于或等于数量阈值。终端设备在注册更新流程中，向移动管理网元发送注册请求消息，该注册请求消息中可以包括用户面连接去激活指示(即指示信息)，该用户面连接去激活指示用于指示去激活一个或多个第一会话的用户面连接。
可选的，指示信息用于指示将至少一个第一会话的用户面连接去激活的指示方式包括但不限于，指示将该至少一个第一会话修改或者重建为使用控制面优化的会话；或者，指示将该至少一个第一会话修改或者重建为不建立用户面连接的会话，等等，本申请实施例不做限定。其中，将至少一个第一会话修改或者重建为使用控制面优化的会话可以是将该至少一个第一会话修改或者重建为使用控制面CIoT优化且不使用N3数据传输的会话，该种实施方式中，终端设备具有激活的用户面连接的会话可以包括但不限于以下会话：使用控制面CIoT优化且使用N3数据传输的会话、使用用户面CIoT优化或不使用CIoT优化。
应理解，不使用N3数据传输指的是不为相应的会话建立用户面连接，相应会话对应的数据通过控制面传输。
S102，移动管理网元向会话管理网元发送第二请求消息，该第二请求消息包括指示信息，该指示信息用于指示将第一会话的用户面连接去激活。
在一个实施例中，终端设备向移动管理网元发送第一请求消息，相应的，移动管理网元接收该第一请求消息，并对该第一请求消息进行解析，获得终端设备要去激活用户面连接的至少一个第一会话的会话ID。进一步的，该移动管理网元确定用于管理该至少一个第一会话的至少一个会话管理网元，并向对应的会话管理网元发送第二请求消息。
例如，终端设备要去激活用户面连接的至少一个第一会话为会话1、会话2、会话3以及会话4，其中，会话管理网元1用于管理会话1和会话2，会话管理网元2用于管理会话3和会话4。则移动管理网元向会话管理网元1发送用于请求去激活会话1和会话2的用户面连接的第二请求消息。移动管理网元向会话管理网元2发送用于请求去激活会话3和会话4的用户面连接的第二请求消息。可以理解的，移动管理网元可以每次请求去激活一个或者多个第一会话的用户面连接，如果每次请求去激活一个第一会话的用户面连接，则可以分多次请求去激活多个第一会话的用户面连接。例如，移动管理网元可以分两次分别向会话管理网元2请求去激活会话3的用户面连接和会话4的用户面连接。
该第二请求消息包括指示信息，该指示信息用于指示将第一会话的用户面连接去激活。可选的，一个第二请求消息可以对应一个第一会话，例如，该第二请求消息可以包括该第一会话的会话ID。该第二请求消息中的指示信息可以是一个比特信息，该比特信息用于指示是否将第一会话的用户面连接去激活。
可选的，比特0可以指示对第一会话的用户面连接不去激活，比特1可以指示对第一会话的用户面连接要去激活。当然，也可以是比特0指示对第一会话的用户面连接要去激活，比特1表示对第一会话的用户面连接不去激活，本申请实施例不作限定。这里以比特0指示对第一会话的用户面连接不去激活，比特1指示对第一会话的用户面连接要去激活作为举例，示例性的，比特0可以是默认值，若要将第一会话的用户面连接去激活，则将 该比特设置为1即可。
进一步可选的，第二请求消息还可以包括用户面连接去激活的原因值信息，原因值信息包括但不限于：一、终端设备具有激活的用户面连接的会话的数量已经达到最大值(具有激活的用户面连接的会话的数量大于或者等于数量阈值)，且终端设备上层请求为至少一个第二会话激活用户面连接。二、终端设备从通过非窄带物联网接入网络切换为通过窄带物联网接入网络时，该终端设备具有激活的用户面连接的会话的数量大于数量阈值。三、其他可能的终端设备期望去激活用户面连接的原因。
可选的，第二请求消息可以是会话上下文更新消息(或者也可以称为会话上下文更新服务操作请求消息)，当然也可以是其他类型的消息，本申请不作限定。若第二消息是会话上下文更新消息，移动管理网元可以调用会话管理网元的服务化接口(例如：Nsmf_PDUSession)的会话上下文更新(例如UpdateSMContext)服务操作，发送会话上下文更新消息。该会话上下文更新消息中包括要去激活用户面连接的至少一个第一会话的会话ID。
示例性的，若第一请求消息中的指示信息是用于指示将该至少一个第一会话修改或者重建为使用控制面优化的会话，移动管理网元在发送第二请求消息之前，还可以判断是否能够将该至少一个第一会话修改或重建为使用控制面优化的会话。若确定能够将该至少一个第一会话修改或重建为使用控制面优化的会话，则移动管理网元向会话管理网元发送第二请求消息，并指示将第一会话修改或重建为使用控制面优化的会话。
若移动管理网元确定不能够将至少一个第一会话修改或重建为使用控制面优化的会话(可选的，移动管理网元可以确定终端设备所请求的多个第一会话中的部分第一会话不能够修改或重建为使用控制面优化的会话)，则移动管理网元将终端设备发送的信息通过下行NAS传输消息返回给终端设备，并携带不能转发的原因值信息，原因值信息包括但不限于：一、控制面拥塞，二、使用控制面优化的会话的数量已经达到最大值，三、网络侧不支持使用控制面优化，四、其他可能的原因。在这种情况下，则不执行步骤S102和步骤S103。
S103，会话管理网元根据指示信息，将第一会话的用户面连接去激活。
在一些可能的场景中，会话管理网元在将第一会话的用户面连接去激活之前，还可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定是否能将所请求的第一会话的用户面连接去激活。若能将第一会话的用户面连接去激活，则根据指示信息，将第一会话的用户面连接去激活，即第一会话的用户面连接去激活成功。若不能够将第一会话的用户面连接去激活，则不将第一会话的用户面连接去激活，即第一会话的用户面连接去激活未成功，具体原因值信息可以参照后续实施例的描述，暂不赘述。可以理解的是，本申请中所指的用户面连接去激活未成功也可以指会话管理网元在去激活用户面连接过程中失败，导致未成功去激活第一会话的用户面连接。
其中，会话管理网元将第一会话的用户面连接去激活可以是指，会话管理网元与用户面功能网元(该用户面功能网元与该第一会话关联)进行交互，从而将第一会话的N3隧道资源释放，具体请参照后续实施例的描述，在此暂不赘述。
进一步可选的，该会话管理网元还可以向移动管理网元发送响应消息，该响应消息包括第一会话的用户面连接去激活结果信息。用户面连接去激活结果信息指示第一会话的用 户面连接去激活成功或者去激活未成功。若所述用户面连接去激活结果信息指示所述第一会话的用户面连接去激活未成功，响应消息中还可以包括用户面连接去激活未成功的原因值信息。原因值信息包括以下信息中的一种或者多种：第一会话为要释放的会话、控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化、不允许去激活用户面连接、或者去激活其它会话的用户面连接等等，本申请实施例不作限定。下面对各个原因值信息进行举例阐述。
1、第一会话为要释放的会话。例如，在终端设备从通过非窄带物联网接入网络切换为通过窄带物联网接入网络时，即第一请求消息是移动管理流程中的注册请求消息的情况下，会话管理网元接收到第二请求消息后，确定请求去激活用户面连接的第一会话是否为该会话管理网元要释放的会话，若该第一会话是会话管理网元要释放的会话，则会话管理网元可以拒绝将第一会话的用户面连接去激活，并返回拒绝原因值信息，该拒绝原因值信息包括但不限于：一、该第一会话为要释放的会话；二、该第一会话为要释放且重建的会话，三、其他可能的原因。其中，拒绝原因值信息可以是通过上述响应消息发送给移动管理网元，具体请参照前述实施例的描述，在此不再赘述。
可以理解的是，该会话管理网元释放该第一会话时，该第一会话的用户面连接也就被去激活，会话管理网元可以不用针对该指示信息，将第一会话的用户面连接去激活。因此可以认为会话管理网元拒绝去激活第一会话的用户面连接，并返回拒绝原因值信息。
2、控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化。又例如，若指示信息是用于指示将第一会话修改或者重建为使用控制面优化的会话，会话管理网元可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定是否能够将该第一会话修改为使用控制面优化的会话。若能够将第一会话修改为使用控制面优化的会话，则根据指示信息将第一会话修改为使用控制面优化的会话，从而满足终端设备具有激活的用户面连接的会话的数量小于或者等于数量阈值。若不能将第一会话修改为使用控制面优化的会话，则返回用户面连接去激活未成功，可选的，还可以携带不能使用控制面优化的原因值信息，其中，不能使用控制面优化的原因值信息包括但不限于：一、控制面拥塞，二、使用控制面优化的会话的数量已经达到最大值，三、网络侧不支持控制面优化，四、其他可能的原因。其中，不能使用控制面优化的原因值信息可以是通过上述响应消息发送给移动管理网元，具体请参照前述实施例的描述，在此不再赘述。
3、不允许去激活用户面连接、或者去激活其它会话的用户面连接。又例如，会话管理网元还可以根据本地策略、网络配置或用户签约数据中的一种或者多种，选择将其他会话(不是移动管理网元所指示的至少一个第一会话)的用户面连接去激活。例如，指示信息用于指示将会话1和会话3的用户面连接去激活，会话管理网元可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定不能将会话3的用户面连接去激活，可以将会话4的用户面连接去激活，因此会话管理网元可以将会话1的用户面连接和会话4的用户面连接去激活，并返回会话3的用户面连接去激活未成功，以及用户面连接去激活未成功的原因值信息，其中，该用户面连接去激活未成功的原因值信息可以是去激活其他会话的用户面连接，或者不允许将该会话的用户面连接去激活，或者其他可能的原因。其中，该原因值信息可以是通过上述响应消息发送给移动管理网元，具体请参照前述实施例的描 述，在此不再赘述。
示例性的，该实施例中响应消息可以是会话上下文更新响应消息。若上述响应消息中的用户面连接去激活结果信息指示第一会话的用户面连接去激活成功，则该响应消息还可以包括N2会话管理(session management,SM)信息(其中，N2 SM信息是指会话管理网元发送给接入网设备的关于会话的信息)，N2 SM信息指示接入网设备释放与第一会话相关的资源，与第一会话相关的资源包括但不限于终端设备和接入网设备之间的数据无线承载资源以及接入网设备和用户面功能网元之间的N3隧道资源。
可以理解的是，若用户面连接去激活结果信息指示第一会话的用户面连接去激活未成功，则该响应消息中可以不包括N2 SM信息。
相应的，移动管理网元接收N2 SM信息，并将该N2 SM信息通过N2接口转发给接入网设备，例如，向接入网设备发送资源释放命令，该资源释放命令包括N2 SM信息，接入网设备释放与该第一会话相关的资源。可以理解的是，所述资源释放命令可以是已存在的消息类型，例如协议数据单元会话资源释放命令消息，也可以是其他的已存在或未来新的类型的消息，本申请对此不做限定。可选的，该资源释放命令还可以包括上述用户面连接去激活结果信息，和/或，去激活未成功的原因值信息。
示例性的，若移动管理网元向多个会话管理网元分别请求去激活不同的第一会话的用户面连接，该移动管理网元可以等收到所有的会话管理网元发送的响应消息后，再一次向接入网设备发送资源释放命令。或者，该移动管理网元也可以多次向接入网设备发送资源释放命令。
接入网设备接收资源释放命令之后，通过与终端设备之间的交互，执行与第一会话相关的资源的释放，如Uu接口和N3接口上的资源释放，即释放数据无线承载资源和N3隧道资源。在接入网设备释放资源后，向移动管理网元发送资源释放响应。移动管理网元接收到资源释放响应后，可以向终端设备发送服务响应消息或者注册响应消息，在该服务响应消息或者注册响应消息中指示要去激活用户面连接的至少一个第一会话的用户面连接去激活结果信息(或者也可称为该至少一个第一会话的用户面连接状态)。该用户面连接去激活结果信息用于指示该至少一个第一会话的用户面连接去激活成功或者去激活未成功，若去激活结果信息指示该至少一个第一会话的用户面连接去激活未成功，则该服务响应消息或者注册响应消息中还可以包含未能去激活成功的原因值信息。
可选的，若请求去激活用户面连接的至少一个第一会话为两个或者两个以上，则移动管理网元可以等收到关于所有第一会话的资源释放响应后，再给终端设备发送服务响应消息或者注册响应消息。
在另一种可能的实现方式中，若移动管理网元向接入网设备发送的资源释放命令中包括要去激活用户面连接的至少一个第一会话的用户面连接去激活结果信息，和/或未激活成功的原因值信息，该接入网设备在与终端设备之间交互，以执行与第一会话相关的资源释放过程中，可以将要去激活用户面连接的至少一个第一会话的用户面连接去激活结果信息和/或未激活成功的原因值信息发送给终端设备，即服务响应消息或者注册响应消息可以在接入网设备在与终端设备之间执行资源释放过程中发送给终端设备。
请参照图3，为本申请实施例提供的另一种会话处理方法的流程示意图，在本申请实 施例中，第一网元可以是会话管理网元，如图所示，本申请实施例的会话处理方法包括但不限于以下步骤：
S200，在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接，所述具有激活的用户面连接的会话包括所述至少一个第一会话；
本申请实施例步骤S200请参照图2实施例的步骤S100，在此不再赘述。
S201，所述终端设备向会话管理网元发送第一请求消息，所述第一请求消息包括指示信息，所述指示信息用于指示将第一会话的用户面连接去激活。
在一个实施例中，其中，第一请求消息可以是终端设备在会话管理流程中发送的请求消息。例如，第一请求消息可以是会话修改请求消息或者会话建立请求消息。该第一请求消息对应一个第一会话，例如，该第一请求消息可以包括所对应的第一会话的会话ID。
一种可能的设计中，该指示信息可以是已有信元中新增加的一个值，例如，该指示信息可以是会话修改原因值中新增加的一个原因值，该原因值用于指示对第一会话的用户面连接去激活，也即请求去激活第一会话的用户面连接。
在另一种可能的设计中，该指示信息也可以是新增加的一个信元，例如用户面连接去激活请求(User-plane Deactivation Requested，UPDR)。该信元中可以包括一个比特，该比特为0或者1，该比特用于指示是否对该第一会话的用户面连接去激活,也即是否请求去激活第一会话的用户面连接。
可选的，比特0可以指示对第一会话的用户面连接不去激活，比特1可以指示对第一会话的用户面连接要去激活。当然，也可以是比特0指示对第一会话的用户面连接要去激活，比特1表示对第一会话的用户面连接不去激活，本申请实施例不作限定。这里以比特0指示对第一会话的用户面连接不去激活，比特1指示对第一会话的用户面连接要去激活作为举例，示例性的，比特0可以是默认值，若要将第一会话的用户面连接去激活，则将该信元的比特设置为1即可。
可选的，指示信息指示将第一会话的用户面连接去激活的指示方式包括但不限于：指示将该第一会话修改或者重建为使用控制面优化的会话；或者，指示将该第一会话修改或者重建为不建立用户面连接的会话，等等，本申请实施例不做限定。
其中，将第一会话修改或者重建为使用控制面优化的会话可以是将该第一会话修改或者重建为使用控制面CIoT优化且不使用N3数据传输的会话，该种实施方式中，终端设备具有激活的用户面连接的会话可以包括但不限于以下会话：使用控制面CIoT优化且使用N3数据传输的会话、使用用户面CIoT优化或不使用CIoT优化。
应理解，不使用N3数据传输指的是不为相应的会话建立用户面连接，相应会话对应的数据通过控制面传输。
示例性的，在一些可能的应用场景中，例如终端设备从通过非窄带物联网接入网络切换为通过窄带物联网接入网络时，会话管理网元可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定释放一个或多个会话，并向终端设备发送释放指令，该释放指令指示是否重建所释放的会话。终端设备接收释放命令，确定会话管理网元保留的具有用户面连接的会话的数量和会话管理网元要释放且重建的会话的数量大于数量阈值时，则 终端设备在接收到指示重建会话的释放命令时，可以发起会话建立流程，例如，终端设备发送会话建立请求消息(即第一请求消息)，该会话建立请求消息包括指示信息，该指示信息用于指示对第一会话不建立用户面连接(也可以称为将第一会话的用户面连接去激活)，以满足终端设备具有激活的用户面连接的会话的数量不大于数量阈值。其中，该第一会话可以是会话管理网元确定释放且重建的会话。或者，终端设备也可以发起会话修改流程，例如，终端设备发送会话修改请求(即第一请求消息)，该会话修改请求包括指示信息，该指示信息用于指示将第一会话的用户面连接去激活。其中，该第一会话可以是会话管理网元确定保留的会话。
可以理解的是，上述第一会话可以是会话管理网元确定释放且重建的会话和/或会话管理网元确定保留的会话，本申请不作限定，上述仅为举例。
可选的，上述会话修改请求消息或者会话建立请求消息可以包含在上行NAS传输消息中发送给移动管理网元，该移动管理网元调用会话管理网元的服务化接口(例如：Nsmf_PDUSession)的会话上下文更新(例如UpdateSMContext)服务操作，发送会话上下文更新消息，该会话上下文更新消息包括上述会话修改请求消息或者会话建立请求消息。
示例性的，若第一请求消息中的指示信息是用于指示将该第一会话修改或者重建为使用控制面优化的会话，移动管理网元在发送会话上下文更新消息之前，还可以判断是否能够将该第一会话修改或重建为使用控制面优化的会话。若确定能够将该第一会话修改或重建为使用控制面优化的会话，则移动管理网元向会话管理网元发送会话上下文更新消息，该会话上下文更新消息包括上述会话修改请求消息，或者会话建立请求消息，并指示将第一会话修改或重建为使用控制面优化的会话。
若移动管理网元确定不能够将第一会话修改或重建为使用控制面优化的会话，则移动管理网元将终端设备发送的信息通过下行NAS传输消息返回给终端设备，并携带不能转发的原因值信息，原因值信息包括但不限于：一、控制面拥塞，二、使用控制面优化的会话的数量已经达到最大值，三、网络侧不支持使用控制面优化，四、其他可能的原因。在这种情况下，则不执行步骤S202，当然移动管理网元也不转发会话修改请求消息或者会话建立请求消息。
S202，会话管理网元根据指示信息，将第一会话的用户面连接去激活。
在一些可能的场景中，会话管理网元在将第一会话的用户面连接去激活之前，还可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定是否能将所请求的第一会话的用户面连接去激活。若能将第一会话的用户面连接去激活，则根据指示信息，将第一会话的用户面连接去激活，即第一会话的用户面连接去激活成功。若不能够将第一会话的用户面连接去激活，则不将第一会话的用户面连接去激活，即第一会话的用户面连接去激活未成功，具体原因值信息可以参照后续实施例的描述，暂不赘述。可以理解的是，本申请中所指的用户面连接去激活未成功也可以指会话管理网元在去激活用户面连接过程中失败，导致未成功去激活第一会话的用户面连接。
其中，会话管理网元将第一会话的用户面连接去激活可以是指，会话管理网元与用户面功能网元(该用户面功能网元与该第一会话关联)进行交互，从而将第一会话的N3隧道资源释放，具体请参照后续实施例的描述，在此暂不赘述。
进一步可选的，该会话管理网元还可以向移动管理网元发送响应消息，该响应消息包括第一会话的用户面连接去激活结果信息。用户面连接去激活结果信息指示第一会话的用户面连接去激活成功或者去激活未成功。若所述用户面连接去激活结果信息指示所述第一会话的用户面连接去激活未成功，响应消息中还可以包括用户面连接去激活未成功的原因值信息。原因值信息包括以下信息中的一种或者多种：第一会话为要释放的会话、控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化、不允许去激活用户面连接、或者去激活其它会话的用户面连接等等，本申请实施例不作限定。下面对各个原因值信息进行举例阐述。
1、第一会话为要释放的会话。例如，在终端设备从通过非窄带物联网接入网络切换为通过窄带物联网接入网络时，会话管理网元确定请求去激活用户面连接的第一会话是否为该会话管理网元要释放的会话，若该第一会话是会话管理网元要释放的会话，则会话管理网元可以拒绝将第一会话的用户面连接去激活，并返回拒绝原因值信息，该拒绝原因值信息包括但不限于：一、该第一会话为要释放的会话；二、该第一会话为要释放且重建的会话，三、其他可能的原因。其中，拒绝原因值信息可以是通过上述响应消息发送给移动管理网元，具体请参照前述实施例的描述，在此不再赘述。
可以理解的是，该会话管理网元释放该第一会话时，该第一会话的用户面连接也就被去激活，会话管理网元可以不用针对该指示信息，将第一会话的用户面连接去激活。因此可以认为会话管理网元拒绝去激活第一会话的用户面连接，并返回拒绝消息。
2、控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化。又例如，若指示信息是用于指示将第一会话修改或者重建为使用控制面优化的会话，会话管理网元可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定是否能够将该第一会话修改为使用控制面优化的会话。若能够将第一会话修改为使用控制面优化的会话，则根据指示信息将第一会话修改为使用控制面优化的会话，从而满足终端设备具有激活的用户面连接的会话的数量小于或者等于数量阈值。若不能将第一会话修改为使用控制面优化的会话，则返回用户面连接去激活未成功，可选的，还可以携带不能使用控制面优化的原因值信息，其中，不能使用控制面优化的原因值信息包括但不限于：一、控制面拥塞，二、使用控制面优化的会话的数量已经达到最大值，三、网络侧不支持控制面优化，四、其他可能的原因。其中，不能使用控制面优化的原因值信息可以是通过上述响应消息发送给移动管理网元，具体请参照前述实施例的描述，在此不再赘述。
3、不允许去激活用户面连接、或者去激活其它会话的用户面连接。又例如，会话管理网元还可以根据本地策略、网络配置或用户签约数据中的一种或者多种，选择将其他会话(不是移动管理网元所指示的第一会话)的用户面连接去激活。例如，指示信息用于指示将会话1和会话3的用户面连接去激活，会话管理网元可以根据本地策略、网络配置或用户签约数据中的一种或者多种，确定不能将会话3的用户面连接去激活，可以将会话4的用户面连接去激活，因此会话管理网元可以将会话1的用户面连接和会话4的用户面连接去激活，并返回会话3的用户面连接去激活未成功，以及用户面连接去激活未成功的原因值信息，其中，该用户面连接去激活未成功的原因值信息可以是去激活其他会话的用户面连接，或者不允许将该会话的用户面连接去激活，或者其他可能的原因。其中，该原因值 信息可以是通过上述响应消息发送给移动管理网元，具体请参照前述实施例的描述，在此不再赘述。
示例性的，在该实施例中，上述响应消息可以是会话修改响应消息或者会话建立响应消息。该会话修改响应消息或者会话建立响应消息可以是被包含在会话上下文更新响应消息中。在一种可能的设计中，该会话上下文更新响应消息可以包含N1SM信息(N1SM信息是指会话管理网元发送给终端设备的与会话相关的信息)，该N1SM信息中包含上述会话修改响应消息或者会话建立响应消息。
可选的，会话修改响应消息可以包括会话修改接受消息或者会话修改拒绝消息，会话建立响应消息可以包括会话建立接受消息或者会话建立拒绝消息。该会话修改响应消息或者会话建立响应消息包括用户面连接去激活结果信息，该用户面连接去激活结果信息用于指示第一会话的用户面连接去激活成功或者未成功。
在一种可能的设计中，若第一会话的用户面连接去激活成功，则会话上下文更新响应消息中的N1SM信息可以包含会话修改接受消息或会话建立接受消息，该会话修改接受消息或会话建立接受消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示第一会话的用户面连接去激活成功(例如重建没有用户面连接的会话的成功指示，或者修改使用控制面优化的会话的成功指示，或者重建使用控制面优化的会话的成功指示等等)。若第一会话的用户面连接去激活未成功，则N1SM信息中可以包含会话修改拒绝消息或者会话建立拒绝消息，会话修改拒绝消息或者会话建立拒绝消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示第一会话的用户面连接去激活未成功。进一步，可选的，该会话修改拒绝消息或者会话建立拒绝消息还可以包括用户面连接去激活未成功的原因值信息，原因值信息请参照前述实施例的描述，在此不再赘述。
可以理解的是，也可以是在会话修改拒绝消息或者会话建立拒绝消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示第一会话的用户面连接去激活成功。则会话修改接受消息或者会话建立接受消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示第一会话的用户面连接去激活未成功。本申请实施例不作限定，上述仅为举例。
示例性的，若用户面连接去激活结果信息指示第一会话的用户面连接去激活成功，则会话上下文更新响应消息中还可以包括N2会话管理(session management,SM)信息(其中，N2 SM信息是指会话管理网元发送给接入网设备的关于会话的信息)，N2 SM信息指示接入网设备释放与第一会话相关的资源，与第一会话相关的资源包括但不限于终端设备和接入网设备之间的数据无线承载资源以及接入网设备和用户面功能网元之间的N3隧道资源。
可以理解的是，若用户面连接去激活结果信息指示第一会话的用户面连接去激活未成功，则该响应消息中可以不包括N2 SM信息。
相应的，移动管理网元接收N2 SM信息，并将该N2 SM信息通过N2接口转发给接入网设备，例如，向接入网设备发送资源释放命令，该资源释放命令包括N2 SM信息，接入网设备释放与该第一会话相关的资源。可以理解的是，所述资源释放命令可以是已存在的消息类型，例如协议数据单元会话资源释放命令消息，也可以是其他的已存在或未来新的 类型的消息，本申请对此不做限定。可选的，该资源释放命令还可以包括上述用户面连接去激活结果信息，和/或，去激活未成功的原因值信息。
接入网设备接收资源释放命令之后，通过与终端设备之间的交互，执行与第一会话相关的资源的释放，如Uu接口和N3接口上的资源释放，即释放数据无线承载资源和N3隧道资源。在接入网设备释放资源后，向移动管理网元发送资源释放响应。移动管理网元接收到资源释放响应后，可以向终端设备发送会话修改响应消息或者会话建立响应消息，在该会话修改响应消息或者会话建立响应消息中指示要去激活用户面连接的第一会话的用户面连接去激活结果信息(或者也可称为该第一会话的用户面连接状态)。该用户面连接去激活结果信息用于指示该第一会话的用户面连接去激活成功或者去激活未成功，若去激活结果信息指示该第一会话的用户面连接去激活未成功，则该会话修改响应消息或者会话建立响应消息中还包含去激活未成功的原因值信息，具体请参照前述实施例的描述。
在另一种可能的实现方式中，若移动管理网元向接入网设备发送的资源释放命令中包括要去激活用户面连接的第一会话的用户面连接去激活结果信息，该接入网设备在与终端设备之间交互，以执行Uu接口和N3接口上的资源释放过程中，可以将要去激活用户面连接的第一会话的用户面连接去激活结果信息发送给终端设备，即会话修改响应消息或者会话建立响应消息可以在接入网设备在与终端设备之间执行资源释放过程中发送给终端设备。
结合图4，对图2所示的方法进行更详细的介绍。为便于理解，图4中以终端设备为UE，移动管理网元为AMF，接入网设备为RAN，会话管理网元为SMF，用户面功能网元为UPF为例进行说明。在后续实施例中，将指示信息称为用户面连接去激活指示。
S301，在UE具有激活的用户面连接的会话的数量不小于数量阈值时，UE向AMF发送服务请求消息或者注册请求消息，该服务请求消息或者注册请求消息包含用户面连接去激活指示，该用户面连接去激活指示用于指示去激活一个或多个第一会话的用户面连接。
一种可能的设计中，该用户面连接去激活指示可以是会话用户面连接去激活列表信息(List Of PDU Sessions To Be Deactivated)，该会话用户面连接去激活列表信息包括会话标识(Identity，ID)列表，该会话ID列表包括至少一个第一会话的会话ID，其中，该会话ID列表用于表示去激活对应会话的用户面连接。其中，上述会话用户面连接去激活列表信息可以是已有信元中新增加的值，也可以是新增加的一种信元。
在另一种可能的设计中，该用户面连接去激活指示可以是比特信息。若要去激活一个第一会话的用户面连接，则该用户面连接去激活指示包括一个比特。若要去激活多个第一会话的用户面连接，则该用户面连接去激活指示可以包括多个比特，该多个比特可以构成比特集合或者比特列表。其中，一个比特对应一个第一会话。
可选的，比特0可以指示对应第一会话的用户面连接不去激活，比特1可以指示对应第一会话的用户面连接要去激活。当然，也可以是比特0指示对应第一会话的用户面连接要去激活，比特1表示对应第一会话的用户面连接不去激活，本申请实施例不作限定。
下面以比特0指示对应第一会话的用户面连接不去激活，比特1指示对应第一会话的用户面连接要去激活作为举例。例如，在5G系统中，终端设备最多可以有15个会话，如 表二所示，PDU会话ID(PDU Session Identity，PSI)(1)对应会话ID为1的会话，PSI(2)对应会话ID为2的会话，以此类推。若终端设备具有激活的用户面连接的会话的数量是3，数量阈值是2，若UE请求去激活一个第一会话的用户面连接，例如，要去激活会话ID为1的会话，则将表一中的PSI(1)的比特设置为1，可选的，其余比特设置为0。示例性的，比特0可以是默认值，则可以将PSI(1)的比特设置为1即可。若终端设备具有激活的用户面连接的会话的数量是5，数量阈值是3，若UE请求去激活两个第一会话的用户面连接，例如，要去激活会话ID为1的会话和ID为2的会话，则将表二中的PSI(1)和PSI(2)的比特设置为1，可选的，其余比特设置为0。示例性的，比特0可以是默认值，则可以将PSI(1)和PSI(2)的比特设置为1即可。
表二
PSI(7) PSI(6) PSI(5) PSI(4) PSI(3) PSI(2) PSI(1) PSI(0)
PSI(15) PSI(14) PSI(13) PSI(12) PSI(11) PSI(10) PSI(9) PSI(8)
S302，AMF向SMF发送会话上下文更新消息，该会话上下文更新消息包括用户面连接去激活指示。可选的，该会话上下文更新消息还可以包括用户面连接去激活的原因值信息。
该会话上下文更新消息包括用户面连接去激活指示，该用户面连接去激活指示用于指示将第一会话的用户面连接去激活。可选的，一个会话上下文更新消息可以对应一个第一会话，例如，该会话上下文更新消息可以包括该第一会话的会话ID。该第二请求消息中的用户面连接去激活指示可以是一个比特信息，该比特信息用于指示是否将第一会话的用户面连接去激活。
可选的，比特0可以指示对第一会话的用户面连接不去激活，比特1可以指示对第一会话的用户面连接要去激活。当然，也可以是比特0指示对第一会话的用户面连接要去激活，比特1表示对第一会话的用户面连接不去激活，本申请实施例不作限定。这里以比特0指示对第一会话的用户面连接不去激活，比特1指示对第一会话的用户面连接要去激活作为举例，示例性的，比特0可以是默认值，若要将第一会话的用户面连接去激活，则将该比特设置为1即可。
需要说明的是，如果UE要去激活用户面连接的会话不止一个，且涉及到多个SMF，则AMF向多个SMF分别发送会话上下文更新消息，用于请求SMF去激活对应的第一会话，其中，与SMF对应的第一会话可以是由该SMF管理的会话。
相应的，SMF接收会话上下文更新消息，并根据指示信息将第一会话的用户面连接去激活。可选的，在一些可选的场景中，例如，UE接入的RAN的RAT类型从非NB-IoT变为NB-IoT的场景，SMF根据本地策略、网络配置或用户签约数据中的一种或者多种，确定释放会话，若指示信息中请求去激活的第一会话与SMF要释放的会话匹配，则SMF可以不根据指示信息将第一会话的用户面连接去激活，而是将该第一会话释放，该种场景则不执行后续步骤。
可选的，在一些可选的场景中，SMF根据本地策略、网络配置或用户签约数据中的一种或者多种，确定不能将第一会话的用户面连接去激活，而去激活其他会话。
其中，SMF在去激活第一会话的用户面连接时，可以将作为N3终点的UPF释放，或 者将作为N3终点的UPF不释放，其中，将作为N3终点的UPF释放是指释放后，该第一会话的N3隧道不再存在。该实施例中，若释放N3终点的UPF，则执行步骤S303-S306；若不释放N3终点的UPF，则执行步骤S307-S308，下面分别阐述。
S303，SMF向作为N3终点的UPF发送N4会话释放请求。
S304，N3终点的UPF在释放N3终点后，向SMF发送N4会话释放响应。
S305-S306，SMF向非N3终点的UPF发起N4会话修改流程，指示非N3终点的UPF移除指定的第一会话的N9隧道信息。
S307-S308，SMF向作为N3终点的UPF发起N4会话修改流，指示作为N3终点的UPF移除指定的第一会话的N3隧道信息。
S309，SMF向AMF发送会话上下文更新响应消息，该会话上下文更新响应消息中包含用户面连接去激活结果信息。该用户面连接去激活结果信息指示请求的第一会话的用户面连接去激活成功或者去激活未成功。
可选的，若去激活成功，该会话上下文更新响应消息中还可以包含N2 SM信息(指SMF发送给RAN的关于会话的信息)，N2 SM信息指示RAN释放第一会话相关的资源，包括UE和RAN之间的DRB以及RAN和UPF之间的N3隧道。
若去激活未成功，(例如，SMF要释放该第一会话)，该会话上下文更新响应消息还可能携带未去激活成功的原因值信息，比如SMF决定释放会话。可以理解的是，若SMF决定释会放话，会话上下文更新响应消息中不包含N2 SM信息。又比如，去激活其他会话。
S310，AMF将收到的N2 SM信息通过N2接口转发给RAN，即向RAN发送资源释放命令。若多个会话的用户面连接要去激活，且涉及到多个SMF，则AMF可以多次向RAN发送PDU会话资源释放命令，而不用等收到所有的SMF发来的会话上下文更新响应消息。当然，AMF也可以等收到所有的SMF发来的会话上下文更新响应消息后，再一次向RAN发送资源释放命令。对于后者，资源释放命令中要指定多个第一会话要释放相关资源。
S311，RAN收到PDU资源释放命令后，执行Uu接口和N3接口上的资源释放，即释放DRB和N3隧道信息。
S312，RAN释放资源后，RAN向AMF发送资源释放响应。若要释放多个会话的资源，则AMF可以等收到所有会话的资源释放响应后再发送给UE。
S313，AMF向UE发送服务响应消息或注册响应消息，在服务响应消息或注册响应消息中包括用户面连接去激活结果信息。该用户面连接去激活结果信息指示请求的至少一个第一会话的用户面连接去激活成功或者去激活未成功。若去激活未成功，则服务响应消息或注册响应消息中还包含去激活未成功的原因值信息，例如，第一会话为要释放的会话、不允许去激活用户面连接、或者去激活其它会话的用户面连接等等，具体请参照前述实施例的描述，在此不再赘述。
可以理解的是，步骤S313还可以是融合在步骤S310和S311中，即RAN进行资源释放过程中，将服务响应消息或注册响应消息发送给UE。本申请实施例不做限定。
结合图5和图6，对图3所示的方法进行更详细的介绍。为便于理解，图5和图6中以终端设备为UE，移动管理网元为AMF，接入网设备为RAN，会话管理网元为SMF，用 户面功能网元为UPF为例进行说明。在图5中，指示信息可以是用户面连接去激活指示，或者不建立用户面连接指示。图6中，指示信息可以是使用控制面优化指示，图6中以使用控制面CIoT优化且不使用N3数据传输作为一种使用控制面优化举例说明。下面结合图5和图6分别阐述。
请参照图5所示，该场景下的会话处理方法包括但不限于以下步骤：
S401，在UE具有激活的用户面连接的会话的数量不小于数量阈值时，UE向SMF发送会话修改请求消息或会话建立请求消息。对于会话建立请求消息，该消息中可以包括指示信息，指示SMF将第一会话重建为不建立用户面连接的会话；对于会话修改请求消息，消息中可以包括用户面连接去激活指示，指示SMF去激活第一会话的用户面连接。
其中，会话修改请求消息或会话建立请求消息可以对应一个第一会话，例如，该会话修改请求消息或会话建立请求消息可以包括所对应的第一会话的会话ID。
一种可能的设计中，该指示信息可以是已有信元中新增加的一个值，例如，该指示信息可以是会话修改请求消息中会话修改原因值中新增加的一个原因值，该原因值用于指示对第一会话的用户面连接去激活，也即请求去激活第一会话的用户面连接。
在另一种可能的设计中，该指示信息也可以是新增加的一个信元，例如用户面连接去激活请求(User-plane Deactivation Requested，UPDR)。该信元中可以包括一个比特，该比特为0或者1，该比特用于指示是否对该第一会话的用户面连接去激活,也即是否请求去激活第一会话的用户面连接。
可选的，比特0可以指示对第一会话的用户面连接不去激活，比特1可以指示对第一会话的用户面连接要去激活。当然，也可以是比特0指示对第一会话的用户面连接要去激活，比特1表示对第一会话的用户面连接不去激活，本申请实施例不作限定。这里以比特0指示对第一会话的用户面连接不去激活，比特1指示对第一会话的用户面连接要去激活作为举例，示例性的，比特0可以是默认值，若要将第一会话的用户面连接去激活，则将该信元的比特设置为1即可。
可选的，会话修改请求消息或会话建立请求消息可以包含在上行非接入层(non-access stratum，NAS)传输消息中发送给AMF，该AMF调用SMF的服务化接口(例如：Nsmf_PDUSession)的会话上下文更新(例如UpdateSMContext)服务操作，向SMF发送会话上下文更新消息，该会话上下文更新消息包括上述会话修改请求消息或者会话建立请求消息。
相应的，SMF接收会话修改请求消息或会话建立请求消息，并根据指示信息将至少一个第一会话的用户面连接去激活。
可选的，在一些可选的场景中，例如，UE接入的RAN的RAT类型从非NB-IoT变为NB-IoT的场景，SMF根据本地策略、网络配置或用户签约数据中的一种或者多种，确定释放会话，若指示信息中请求去激活的第一会话与SMF要释放的会话匹配，则SMF可以不根据指示信息将第一会话的用户面连接去激活，而是等将该第一会话释放，该种场景则不执行后续步骤。
可选的，在一些可选的场景中，SMF根据本地策略、网络配置或用户签约数据中的一种或者多种，确定不能将第一会话的用户面连接去激活，而去激活其他会话。
其中，SMF在去激活第一会话的用户面连接时，可以将作为N3终点的UPF释放，或者将作为N3终点的UPF不释放，其中，将作为N3终点的UPF释放是指释放后，该第一会话的N3隧道不再存在。该实施例中，若释放N3终点的UPF，则执行步骤S402-S405；若不释放N3终点的UPF，则执行步骤S406-S407，下面分别阐述。
S402，SMF向作为N3终点的UPF发送N4会话释放请求。
S403，N3终点的UPF在释放N3终点后，向SMF发送N4会话释放响应。
S404-S405，SMF向非N3终点的UPF发起N4会话修改流程，指示非N3终点的UPF移除指定的第一会话的N9隧道信息。
S406-S407，SMF向作为N3终点的UPF发起N4会话修改流，指示作为N3终点的UPF移除指定的第一会话的N3隧道信息。
S408，SMF向AMF发送会话上下文更新响应消息，会话上下文更新响应消息中包含N1SM信息(N1SM信息是指SMF发送给UE的与会话相关的信息)，N1SM信息中包含用户面连接去激活结果信息。该用户面连接去激活结果信息指示请求的第一会话的用户面连接去激活成功或者去激活未成功。
可选的，若去激活成功，该会话上下文更新响应消息包含N1SM信息，该N1SM信息中包含会话修改接受消息或者会话建立接受消息，该会话修改接受消息或者会话建立接受消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示请求的第一会话的用户面连接去激活成功。
进一步的，该会话上下文更新响应消息还可以包含N2 SM信息(指SMF发送给RAN的关于会话的信息)，N2 SM信息指示RAN释放第一会话相关的资源，包括UE和RAN之间的DRB以及RAN和UPF之间的N3隧道。
可选的，若去激活未成功，例如终端设备请求去激活用户面连接的第一会话与SMF决定释放的会话匹配，该会话上下文更新响应消息包含N1SM信息，该N1SM信息中包含会话修改拒绝消息或会话建立拒绝消息，会话修改拒绝消息或会话建立拒绝消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示请求的第一会话的用户面连接去激活未成功。
进一步的，会话修改拒绝消息或会话建立拒绝消息中还可以包含拒绝修改或拒绝建立的原因值信息，原因值信息可以是第一会话为要释放的会话、不允许去激活用户面连接、或者去激活其它会话的用户面连接等等。
可以理解的是，也可以是会话修改拒绝消息或会话建立拒绝消息中包含用于指示第一会话去激活成功的用户面连接去激活结果信息，会话修改接受消息或者会话建立接受消息中包含用于指示第一会话去激活未成功的用户面连接去激活结果信息，本申请实施例不作限定。
S409，AMF将收到的N2 SM信息通过N2接口转发给RAN，即向RAN发送资源释放命令。
S410，RAN收到PDU资源释放命令后，执行Uu接口和N3接口上的资源释放，即释放DRB和N3隧道资源。
S411，RAN释放资源后，RAN向AMF发送资源释放响应。若需要释放多个会话的资 源，则AMF可以等收到所有会话的资源释放响应后再发送给UE。
S412，AMF将收到的会话修改接受消息或会话修改拒绝消息或会话建立接受消息或会话建立拒绝消息发送给UE，消息中包括上述用户面连接去激活结果信息，若上述用户面连接去激活结果信息指示该至少一个第一会话的用户面连接去激活未成功，则该消息中还可以包含去激活未成功的原因值信息，例如，第一会话为要释放的会话、不允许去激活用户面连接、或者去激活其它会话的用户面连接等等。
可以理解的是，步骤S412还可以是融合在步骤S409和S410中，即AMF发送给RAN的资源释放命令中包含会话修改响应消息(会话修改接受消息或会话修改拒绝消息)或者会话建立响应消息(会话建立接受消息和会话建立拒绝消息)，RAN进行资源释放过程中，将会话修改响应消息或者会话建立响应消息发送给UE。本申请实施例不做限定。
请参照图6所示，该场景下的会话处理方法包括但不限于以下步骤：
S501，在UE具有激活的用户面连接的会话的数量不小于数量阈值时，UE向SMF发送会话修改请求消息或会话建立请求消息。对于会话建立请求消息，该会话建立请求消息中可以包括使用控制面优化指示(即指示信息)，指示SMF将第一会话重建为使用控制面CIoT优化且不使用N3数据传输的会话；对于会话修改请求消息，会话修改请求消息中可以包括使用控制面优化指示(即指示信息)，指示SMF将第一会话修改为使用控制面CIoT优化且不使用N3数据传输的会话。
其中，会话修改请求消息或会话建立请求消息可以对应一个第一会话，例如，该会话修改请求消息或会话建立请求消息可以包括所对应的第一会话的会话ID。
一种可能的设计中，该使用控制面优化指示可以是已有信元中新增加的一个值，例如，该指示信息可以是会话修改请求消息中会话修改原因值中新增加的一个原因值，该原因值用于指示将第一会话修改为使用控制面优化的会话。
在另一种可能的设计中，该指示信息也可以是新增加的一个信元，例如用户面连接去激活请求(User-plane Deactivation Requested，UPDR)。该信元中可以包括一个比特，该比特为0或者1，该比特用于指示是否将该第一会话修改或重建为使用控制面优化的会话。
可选的，比特0可以指示不将第一会话修改或重建为使用控制面优化的会话，即对第一会话的用户面连接不去激活，比特1可以指示将第一会话修改或重建为使用控制面优化的会话，即对第一会话的用户面连接要去激活。当然，也可以是比特0指示将第一会话修改或重建为使用控制面优化的会话，比特1指示不将第一会话修改或重建为使用控制面优化的会话。本申请实施例不作限定。这里以比特0指示不将第一会话修改或重建为使用控制面优化的会话，比特1指示将第一会话修改或重建为使用控制面优化的会话作为举例，示例性的，比特0可以是默认值，若要将第一会话修改或重建为使用控制面优化的会话，则将该信元的比特设置为1即可。
可选的，会话修改请求消息或会话建立请求消息可以包含在上行NAS传输消息中发送给AMF，该AMF调用SMF的服务化接口(例如：Nsmf_PDUSession)的会话上下文更新(例如UpdateSMContext)服务操作，向SMF发送会话上下文更新消息，该会话上下文更新消息包括上述会话修改请求消息或者会话建立请求消息。
在一种可能的实现中，AMF在接收到使用控制面优化指示(即指示信息)后，可以确定是否能够将第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话。若可以使用控制面CIoT优化且不使用N3数据传输，则将控制面优化指示发送给SMF。若不可以使用控制面CIoT优化且不使用N3数据传输，则AMF将UE发送的信息通过下行NAS传输消息发送给UE，并携带不能转发的原因值信息，原因值信息包括但不限于：一、控制面拥塞，二、使用控制面优化的会话的数量已经达到最大值，三、网络侧不支持控制面优化，四、其他可能的原因。
相应的，SMF接收会话修改请求消息或会话建立请求消息，并根据指示信息将第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话。
可选的，在一些可选的场景中，例如，UE接入的RAN的RAT类型从非NB-IoT变为NB-IoT的场景，SMF根据本地策略、网络配置或用户签约数据中的一种或者多种，确定释放会话，若使用控制面优化指示(即指示信息)中请求修改或重建的第一会话与SMF要释放的会话匹配，则SMF可以不根据指示信息将第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话，而是等将该第一会话释放。
可选的，在一些可选的场景中，SMF根据本地策略、网络配置或用户签约数据中的一种或者多种，确定是否能将第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话，若确定不能够，则SMF也可以不根据指示信息将第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话，并返回不能够将第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话的原因值信息，原因值信息可以包括但不限于：一、控制面拥塞，二、使用控制面优化的会话的数量已经达到最大值，三、网络侧不支持使用控制面优化，四、其他可能的原因。
可选的，在一些可选的场景中，SMF根据本地策略、网络配置或用户签约数据中的一种或者多种，确定不能将第一会话的用户面连接去激活，而去激活其他会话，返回不能去激活第一会话的用户面连接的原因值信息包括但不限于：一、不允许去激活用户面连接，二、去激活其他会话的用户面连接。
其中，SMF在将第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话时，可以将作为N3终点的UPF释放，或者将作为N3终点的UPF不释放，其中，将作为N3终点的UPF释放是指释放后，该第一会话的N3隧道不再存在。该实施例中，若释放N3终点的UPF，则执行步骤S502-S505；若不释放N3终点的UPF，则执行步骤S506-S507，下面分别阐述。
S502，SMF向作为N3终点的UPF发送N4会话释放请求。
S503，N3终点的UPF在释放N3终点后，向SMF发送N4会话释放响应。
S504-S505，SMF向非N3终点的UPF发起N4会话修改流程，指示非N3终点的UPF移除指定的第一会话的N9隧道信息。
S506-S507，SMF向作为N3终点的UPF发起N4会话修改流，指示作为N3终点的UPF移除指定的第一会话的N3隧道信息。
S508，SMF向AMF发送会话上下文更新响应消息，会话上下文更新响应消息中包含N1SM信息(N1SM信息是指SMF发送给UE的与会话相关的信息)，N1SM信息中包含 用户面连接去激活结果信息。该用户面连接去激活结果信息指示请求的第一会话的用户面连接去激活成功或者去激活未成功。在该实施例中，去激活成功可以理解为成功将该第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话。去激活未成功可以理解为未成功将该第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话，需要说明的是，这里的未成功修改或重建可以理解为根据本地策略、用户签约数据、网络配置等不能将该第一会话修改为重建为使用控制面CIoT优化且不使用N3数据传输的会话。当然也可以理解为，在将该第一会话修改为重建为使用控制面CIoT优化且不使用N3数据传输的会话过程中出现问题，导致不能修改或重建成功。
可选的，若去激活成功，该会话上下文更新响应消息包含N1SM信息，该N1SM信息中包含会话修改接受消息或者会话建立接受消息，该会话修改接受消息或者会话建立接受消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示成功将所请求的第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话。
进一步的，该会话上下文更新响应消息还可以包含N2 SM信息(指SMF发送给RAN的关于会话的信息)，N2 SM信息指示RAN释放第一会话相关的资源，包括UE和RAN之间的DRB以及RAN和UPF之间的N3隧道。
可选的，若去激活未成功，例如终端设备请求去激活用户面连接的第一会话与SMF决定释放的会话匹配，该会话上下文更新响应消息包含N1SM信息，该N1SM信息中包含会话修改拒绝消息或会话建立拒绝消息，会话修改拒绝消息或会话建立拒绝消息中包含用户面连接去激活结果信息，该用户面连接去激活结果信息指示未成功将所请求的第一会话修改或重建为使用控制面CIoT优化且不使用N3数据传输的会话。
进一步的，会话修改拒绝消息或会话建立拒绝消息中还可以包含拒绝修改或拒绝建立的原因值信息，原因值信息可以包括但不限于：一、控制面拥塞，二、使用控制面优化的会话的数量已经达到最大值，三、网络侧不支持使用控制面优化，四、SMF要释放会话，五、不允许去激活用户面连，六、去激活其它会话的用户面连接，等等。
可以理解的是，也可以是会话修改拒绝消息或会话建立拒绝消息中包含用于指示第一会话去激活成功的用户面连接去激活结果信息，会话修改接受消息或者会话建立接受消息中包含用于指示第一会话去激活未成功的用户面连接去激活结果信息，本申请实施例不作限定。
S509，AMF将收到的N2 SM信息通过N2接口转发给RAN，即向RAN发送资源释放命令。
S510，RAN收到资源释放命令后，执行Uu接口和N3接口上的资源释放，即释放DRB和N3隧道资源。
S511，RAN释放资源后，RAN向AMF发送资源释放响应。若需要释放多个会话的资源，则AMF可以等收到所有会话的资源释放响应后再发送给UE。
S512，AMF将收到的会话修改接受消息或会话修改拒绝消息或会话建立接受消息或会话建立拒绝消息发送给UE，消息中包括上述用户面连接去激活结果信息，若上述用户面连接去激活结果信息指示该第一会话的用户面连接去激活未成功，则该消息中还可以包含去激活未成功的原因值信息，例如，一、控制面拥塞，二、使用控制面优化的会话的数量已 经达到最大值，三、网络侧不支持使用控制面优化，四、SMF要释放会话，五、不允许去激活用户面连，六、去激活其它会话的用户面连接，等等。
可以理解的是，步骤S512还可以是融合在步骤S509和S510中，即AMF发送给RAN的资源释放命令中包含会话修改响应消息(会话修改接受消息或会话修改拒绝消息)或者会话建立响应消息(会话建立接受消息和会话建立拒绝消息)，RAN进行资源释放过程中，将会话修改响应消息或者会话建立响应消息发送给UE。本申请实施例不做限定。
以上，结合图2至图6详细说明了本申请实施例提供的方法。以下，结合图7至图10详细说明本申请实施例提供的装置。
图7是本申请实施例提供的通信装置的示意性框图。如图7所示，该通信装置1700可以包括收发单元1710和处理单元1720。收发单元1710和处理单元1720可以是软件，也可以是硬件，或者是软件和硬件结合。
其中，收发单元1710可包括发送单元和接收单元，发送单元用于实现发送功能，接收单元用于实现接收功能，收发单元1710可以实现发送功能和/或接收功能。收发单元也可以描述为通信单元。
可选的，收发单元1710可以用于接收其他装置发送的信息(或消息)，还可以用于向其他装置发送信息(或消息)。处理单元1720可以用于进行装置的内部处理。
在一种可能的设计中，该通信装置1700可对应于上述方法实施例中的终端设备(例如：UE)，如该通信装置1700可以是终端设备，也可以是终端设备中的芯片。该通信装置1700可以包括用于执行上述方法实施例中由终端设备所执行的操作的单元，并且，该通信装置1700中的各单元分别为了实现上述方法实施例中由终端设备所执行的操作。
示例性的，处理单元1720，用于在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，确定去激活至少一个第一会话的用户面连接，所述具有激活的用户面连接的会话包括所述至少一个第一会话；
收发单元1710，用于向第一网元发送第一请求消息，所述第一请求消息包括指示信息，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活。
在一种可能的设计中，该通信装置1700可对应于上述方法实施例中的会话管理网元(例如SMF)，如该通信装置1700可以是会话管理网元，也可以是会话管理网元中的芯片。该通信装置1700可以包括用于执行上述方法实施例中由会话管理网元所执行的操作的单元，并且，该通信装置1700中的各单元分别为了实现上述方法实施例中由会话管理网元所执行的操作。
示例性的，收发单元1710，用于接收请求消息，所述请求消息包括指示信息，所述指示信息用于指示所述会话管理网元将第一会话的用户面连接去激活，所述第一会话属于终端设备具有激活的用户面连接的会话，所述终端设备具有激活的用户面连接的会话的数量不小于数量阈值；
处理单元1720，用于根据所述指示信息，将所述第一会话的用户面连接去激活。
在一种可能的设计中，该通信装置1700可对应于上述图2方法实施例中的移动管理网元(例如AMF)，如该通信装置1700可以是移动管理网元，也可以是移动管理网元的芯片。该通信装置1700可以包括用于执行上述图2方法实施例中由移动管理网元所执行的操作的 单元，并且，该通信装置1700中的各单元分别为了实现上述方法实施例中由移动管理网元所执行的操作。
在一种可能的设计中，该通信装置1700可对应于上述图4至图6方法实施例中的接入网设备(例如RAN)，如该通信装置1700可以是接入网设备，也可以是接入网设备的芯片。该通信装置1700可以包括用于执行上述图4至图6方法实施例中由接入网设备所执行的操作的单元，并且，该通信装置1700中的各单元分别为了实现上述方法实施例中由接入网设备所执行的操作。
应理解，该通信装置1700为UE时，该通信装置1700中的收发单元1710可对应于图8中示出的终端设备2000中的收发器2020，该通信装置1700中的处理单元1720可对应于图8中示出的终端设备2000中的处理器2010。
还应理解，该通信装置1700为配置于UE中的芯片时，该通信装置1700中的收发单元1710可以为输入/输出接口。
应理解，该通信装置1700对应会话管理网元、移动管理网元时，该通信装置1700中的收发单元1710可对应于图9中示出的通信接口3010，处理单元1720可对应于图9中示出的处理器3020。
图8是本申请实施例提供的终端设备2000的结构示意图。该终端设备2000可应用于如图1所示的系统中，执行上述方法实施例中终端设备(或UE)的功能。如图8所示，该终端设备2000包括处理器2010和收发器2020。可选地，该终端设备2000还包括存储器2030。其中，处理器2010、收发器2002和存储器2030之间可以通过内部连接通路互相通信，传递控制或数据信号，该存储器2030用于存储计算机程序，该处理器2010用于从该存储器2030中调用并运行该计算机程序，以控制该收发器2020收发信号。可选地，终端设备2000还可以包括天线2040，用于将收发器2020输出的上行数据或上行控制信令通过无线信号发送出去。
上述处理器2010可以和存储器2030可以合成一个处理装置，处理器2010用于执行存储器2030中存储的程序代码来实现上述功能。具体实现时，该存储器2030也可以集成在处理器2010中，或者独立于处理器2010。该处理器2010可以与图7中的处理单元对应。
上述收发器2020可以与图7中的收发单元对应。收发器2020可以包括接收器(或称接收机、接收电路)和发射器(或称发射机、发射电路)。其中，接收器用于接收信号，发射器用于发射信号。
应理解，图8所示的终端设备2000能够实现上述方法实施例中任一方法实施例中涉及终端设备的各个过程。终端设备2000中的各个模块的操作或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详细描述。
上述处理器2010可以用于执行前面方法实施例中描述的由终端设备内部实现的动作，而收发器2020可以用于执行前面方法实施例中描述的终端设备向网络侧发送或从网络侧接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
可选地，上述终端设备2000还可以包括电源2050，用于给终端设备中的各种器件或 电路提供电源。
除此之外，为了使得终端设备的功能更加完善，该终端设备2000还可以包括输入单元2060、显示单元2070、音频电路2080、摄像头2090和传感器2100等中的一个或多个，所述音频电路还可以包括扬声器2082、麦克风2084等。
图9是本申请一个实施例的通信装置的示意性结构图。应理解，图9示出的通信装置3000仅是示例，本申请实施例的通信装置还可包括其他模块或单元，或者包括与图9中的各个模块的功能相似的模块，或者并非要包括图9中所有模块。
通信装置3000包括通信接口3010和至少一个处理器3020。
该通信装置1900可以对应会话管理网元、移动管理网元、终端设备、接入网设备中的任一网元。至少一个处理器3020执行程序指令，使得通信装置1900实现上述方法实施例中由对应网元所执行的方法的相应流程。
可选地，通信装置1900还可以包括存储器。该存储器可以存储程序指令，至少一个处理器3020可以读取存储器所存储的程序指令并执行该程序指令。
对于通信装置可以是芯片或芯片系统的情况，可参见图10所示的芯片的结构示意图。图10所示的芯片900包括处理器901和接口902。其中，处理器901的数量可以是一个或多个，接口902的数量可以是多个。需要说明的，处理器901、接口902各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
在一种可能的设计中，对于芯片用于实现本申请实施例中终端设备的功能的情况：处理器901用于在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，确定去激活至少一个第一会话的用户面连接，所述具有激活的用户面连接的会话包括所述至少一个第一会话。
接口902用于向第一网元发送第一请求消息，所述第一请求消息包括指示信息，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活。
可选的，芯片还包括存储器903，存储器903用于存储终端设备必要的程序指令和数据。
对于芯片用于实现本申请实施例中会话管理网元的功能的情况：接口902用于接收请求消息，所述请求消息包括指示信息，所述指示信息用于指示所述会话管理网元将第一会话的用户面连接去激活，所述第一会话属于终端设备具有激活的用户面连接的会话，所述终端设备具有激活的用户面连接的会话的数量不小于数量阈值。
处理器901用于根据所述指示信息，将所述第一会话的用户面连接去激活。
可选的，芯片还包括存储器903，存储器903用于存储会话管理网元必要的程序指令和数据。
本申请实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件 等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行前述任一方法实施例中终端设备侧的方法或者接入及移动管理网侧的方法或会话管理网元侧的方法。
本申请的另一实施例中，还提供一种通信系统，该通信系统包括终端设备和会话管理网元。或者，该通信系统包括终端设备、会话管理网元以及移动管理网元。或者，该通信系统包括终端设备、会话管理网元、移动管理网元以及接入网设备。示例性的，终端设备可以为图2至图6所提供的终端设备，且用于执行图2至图6所提供的会话处理方法中终端设备的步骤；和/或，会话管理网元可以为图2至图6所提供的会话管理网元，且用于执行图2至图6所提供的会话处理方法中会话管理网元的步骤。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM， SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中网络设备与终端设备和方法实施例中的网络设备或终端设备完全对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程或执行线程中，部件可位于一个计算机上或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地或远程进程来通信。
应理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
应理解，在本申请实施例中，编号“第一”、“第二”…仅仅为了区分不同的对象，比如为了区分不同的网络设备，并不对本申请实施例的范围构成限制，本申请实施例并不限于此。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下网元会做出相应的处理，并非是限定时间，且也不要求网元实现时一定要有判断的动作，也不意味着存在其它限定。
还应理解，在本申请各实施例中，“A对应的B”表示B与A相关联，根据A可以确定 B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请中出现的类似于“项目包括如下中的一项或多项：A，B，以及C”表述的含义，如无特别说明，通常是指该项目可以为如下中任一个：A；B；C；A和B；A和C；B和C；A，B和C；A和A；A，A和A；A，A和B；A，A和C，A，B和B；A，C和C；B和B，B，B和B，B，B和C，C和C；C，C和C，以及其他A，B和C的组合。以上是以A，B和C共3个元素进行举例来说明该项目的可选用条目，当表达为“项目包括如下中至少一种：A，B，……，以及X”时，即表达中具有更多元素时，那么该项目可以适用的条目也可以按照前述规则获得。
可以理解的，本申请实施例中，会话管理网元和/或终端设备可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计 算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种会话处理方法，其特征在于，包括：
    在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接，所述具有激活的用户面连接的会话包括所述至少一个第一会话；
    所述终端设备向第一网元发送第一请求消息，所述第一请求消息包括指示信息，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活。
  2. 如权利要求1所述的方法，其特征在于，所述在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接，包括：
    在所述终端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络，且所述终端设备具有激活的用户面连接的会话的数量大于数量阈值的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接。
  3. 如权利要求1或2所述的方法，其特征在于，所述在终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接，包括：
    在所述终端设备具有激活的用户面连接的会话的数量不小于数量阈值，且所述终端设备确定为至少一个第二会话激活用户面连接的情况下，所述终端设备确定去激活至少一个第一会话的用户面连接，所述至少一个第二会话为不具有激活的用户面连接的会话。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活，包括：所述指示信息用于指示将所述至少一个第一会话修改为使用控制面优化的会话。
  5. 如权利要求1-4任一项所述的方法，其特征在于，所述第一网元为移动管理网元，所述第一请求消息为注册请求消息或者服务请求消息。
  6. 如权利要求1-4任一项所述的方法，其特征在于，所述第一网元为会话管理网元，所述第一请求消息为会话建立请求消息或会话修改请求消息。
  7. 如权利要求1或2所述的方法，其特征在于，所述终端设备通过窄带物联网接入网络。
  8. 如权利要求1所述的方法，其特征在于，所述第一会话不包括用于发送异常数据报告的会话。
  9. 一种会话处理方法，其特征在于，包括：
    会话管理网元接收请求消息，所述请求消息包括指示信息，所述指示信息用于指示所述会话管理网元将第一会话的用户面连接去激活，所述第一会话属于终端设备具有激活的用户面连接的会话，所述终端设备具有激活的用户面连接的会话的数量不小于数量阈值；
    所述会话管理网元根据所述指示信息，将所述第一会话的用户面连接去激活。
  10. 如权利要求9所述的方法，其特征在于，所述会话管理网元根据所述指示信息，将所述第一会话的用户面连接去激活，包括：
    所述会话管理网元根据所述指示信息，将所述第一会话修改为使用控制面优化的会话。
  11. 如权利要求9或10所述的方法，其特征在于，所述会话管理网元根据所述指示信息，将所述第一会话的用户面连接去激活之前，还包括：
    所述会话管理网元根据本地策略、网络配置或用户签约数据中的一种或者多种，确定将所述第一会话的用户面连接去激活。
  12. 如权利要求9或11所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元发送响应消息，所述响应消息包括所述第一会话的用户面连接去激活结果信息，所述用户面连接去激活结果信息指示所述第一会话的用户面连接去激活成功或者去激活未成功。
  13. 如权利要求12所述的方法，其特征在于，若所述用户面连接去激活结果信息指示所述第一会话的用户面连接去激活未成功，所述响应消息还包括用户面连接去激活未成功的原因值信息。
  14. 如权利要求13所述的方法，其特征在于，所述原因值信息包括以下信息中的一种或者多种：控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化、不允许去激活用户面连接、或者去激活其它会话的用户面连接。
  15. 一种通信装置，其特征在于，应用于终端设备，所述装置包括：
    处理单元，用于在所述终端设备具有激活的用户面连接的会话的数量不小于数量阈值的情况下，确定去激活至少一个第一会话的用户面连接，所述具有激活的用户面连接的会话包括所述至少一个第一会话；
    收发单元，用于向第一网元发送第一请求消息，所述第一请求消息包括指示信息，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活。
  16. 如权利要求15所述的装置，其特征在于，所述处理单元用于在所述终端设备从通过非窄带物联网接入网络转变为通过窄带物联网接入网络，且所述终端设备具有激活的用 户面连接的会话的数量大于数量阈值的情况下，确定去激活至少一个第一会话的用户面连接。
  17. 如权利要求15或16所述的装置，其特征在于，所述处理单元用于在所述终端设备具有激活的用户面连接的会话的数量不小于数量阈值，且所述终端设备确定为至少一个第二会话激活用户面连接的情况下，确定去激活至少一个第一会话的用户面连接，所述至少一个第二会话为不具有激活的用户面连接的会话。
  18. 如权利要求15-17任一项所述的装置，其特征在于，所述指示信息用于指示将所述至少一个第一会话的用户面连接去激活，包括：所述指示信息用于指示将所述至少一个第一会话修改为使用控制面优化的会话。
  19. 如权利要求15或16所述的装置，其特征在于，所述终端设备通过窄带物联网接入网络。
  20. 一种通信装置，其特征在于，应用于会话管理网元，所述装置包括：
    收发单元，用于接收请求消息，所述请求消息包括指示信息，所述指示信息用于指示所述会话管理网元将第一会话的用户面连接去激活，所述第一会话属于终端设备具有激活的用户面连接的会话，所述终端设备具有激活的用户面连接的会话的数量不小于数量阈值；
    处理单元，用于根据所述指示信息，将所述第一会话的用户面连接去激活。
  21. 如权利要求20所述的装置，其特征在于，所述处理单元用于根据所述指示信息，将所述第一会话修改为使用控制面优化的会话。
  22. 如权利要求20或21所述的装置，其特征在于，所述请求消息来自于移动管理网元，所述请求消息为会话上下文更新消息。
  23. 如权利要求20或21所述的装置，其特征在于，所述请求消息来自于所述终端设备，所述请求消息为会话建立请求消息或会话修改请求消息。
  24. 如权利要求20-23任一项所述的装置，其特征在于，所述处理单元还用于根据本地策略、网络配置或用户签约数据中的一种或者多种，确定将所述第一会话的用户面连接去激活。
  25. 如权利要求20或24所述的装置，其特征在于，所述收发单元还用于发送响应消息，所述响应消息包括所述第一会话的用户面连接去激活结果信息，所述用户面连接去激活结果信息指示所述第一会话的用户面连接去激活成功或者去激活未成功。
  26. 如权利要求25所述的装置，其特征在于，若所述用户面连接去激活结果信息指示所述第一会话的用户面连接去激活未成功，所述响应消息还包括用户面连接去激活未成功的原因值信息。
  27. 如权利要求26所述的装置，其特征在于，所述原因值信息包括以下信息中的一种或者多种：控制面拥塞、使用控制面优化的会话的数量达到最大值、网络不支持控制面优化、不允许去激活用户面连接、或者去激活其它会话的用户面连接。
  28. 一种通信装置，其特征在于，包括：处理器，当所述处理器调用存储器中的计算机程序或指令时，如权利要求1至8或者如权利要求9至14任一项所述的方法被执行。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质包括计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得计算机执行如权利要求1至8或者如权利要求9至14任一项所述的方法。
  30. 一种通信装置，其特征在于，包括处理器、存储器和通信接口；
    所述通信接口，用于接收信息或者发送信息；
    所述存储器，用于存储程序代码；
    所述处理器，用于从所述存储器调用所述程序代码执行如权利要求1至8或者如权利要求9至14任一项所述的方法。
PCT/CN2021/070442 2020-01-23 2021-01-06 会话处理方法及通信装置 WO2021147672A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21744634.3A EP4075859A4 (en) 2020-01-23 2021-01-06 SESSION PROCESSING METHOD AND COMMUNICATION DEVICE
US17/814,320 US20220361286A1 (en) 2020-01-23 2022-07-22 Session Processing Method and Communication Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010077054.3A CN113163514B (zh) 2020-01-23 2020-01-23 会话处理方法及通信装置
CN202010077054.3 2020-01-23

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/814,320 Continuation US20220361286A1 (en) 2020-01-23 2022-07-22 Session Processing Method and Communication Apparatus

Publications (1)

Publication Number Publication Date
WO2021147672A1 true WO2021147672A1 (zh) 2021-07-29

Family

ID=76882098

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070442 WO2021147672A1 (zh) 2020-01-23 2021-01-06 会话处理方法及通信装置

Country Status (4)

Country Link
US (1) US20220361286A1 (zh)
EP (1) EP4075859A4 (zh)
CN (1) CN113163514B (zh)
WO (1) WO2021147672A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115150870B (zh) * 2022-06-30 2023-03-21 广州爱浦路网络技术有限公司 会话残留处理方法、装置、会话管理功能实体及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102084705A (zh) * 2008-11-17 2011-06-01 思达伦特网络有限责任公司 通信网络中的动态负载平衡
CN105391968A (zh) * 2015-11-03 2016-03-09 浙江大华技术股份有限公司 一种视频会话分配方法及装置
CN110519775A (zh) * 2018-05-22 2019-11-29 华为技术有限公司 会话管理方法、装置和系统
CN112188608A (zh) * 2019-07-04 2021-01-05 华为技术有限公司 一种同步pdu会话状态的方法、装置、系统及芯片
CN112188643A (zh) * 2020-10-09 2021-01-05 哲库科技(北京)有限公司 Pdu会话的建立方法、装置、终端及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090034472A1 (en) * 2007-08-03 2009-02-05 Research In Motion Limited System and Method for Handing Over Sessions Between Networks
KR102327639B1 (ko) * 2017-03-10 2021-11-17 삼성전자 주식회사 Mobile Initiated Communication Only mode 단말의 연결을 유지시키는 방법
US10251147B2 (en) * 2017-03-20 2019-04-02 Samsung Electronics Co., Ltd. Method for supporting efficient PDU session activation and deactivation in cellular networks
CN109673046B (zh) * 2017-10-16 2021-02-09 华为技术有限公司 移动性管理的方法、终端及核心网设备
EP3487217B1 (en) * 2017-11-20 2019-12-04 Ntt Docomo, Inc. Core network of a mobile radio communication network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102084705A (zh) * 2008-11-17 2011-06-01 思达伦特网络有限责任公司 通信网络中的动态负载平衡
CN105391968A (zh) * 2015-11-03 2016-03-09 浙江大华技术股份有限公司 一种视频会话分配方法及装置
CN110519775A (zh) * 2018-05-22 2019-11-29 华为技术有限公司 会话管理方法、装置和系统
CN112188608A (zh) * 2019-07-04 2021-01-05 华为技术有限公司 一种同步pdu会话状态的方法、装置、系统及芯片
CN112188643A (zh) * 2020-10-09 2021-01-05 哲库科技(北京)有限公司 Pdu会话的建立方法、装置、终端及存储介质

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP4075859A4 (en) 2023-08-09
US20220361286A1 (en) 2022-11-10
CN113163514A (zh) 2021-07-23
EP4075859A1 (en) 2022-10-19
CN113163514B (zh) 2022-12-06

Similar Documents

Publication Publication Date Title
EP3952449B1 (en) Method and apparatus for moving between communications systems
WO2018202094A1 (zh) 一种参数的确定方法及通信实体
US20220060935A1 (en) Communications Method and Apparatus
WO2019184651A1 (zh) 一种通信方法及装置
US10893574B2 (en) Packet data unit session release method and network entity performing the same
WO2019196643A1 (zh) 通信的方法和通信装置
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2019192445A1 (zh) 一种组播组创建、组播组加入方法及装置
WO2019137194A1 (zh) 一种用户面数据安全保护方法及装置
WO2020177632A1 (zh) 一种安全保护方法及装置
WO2022016948A1 (zh) 一种通信方法及装置
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2022028041A1 (zh) 用户终端与网络进行通信的方法、终端、网络设备及装置
WO2023016006A1 (zh) 一种通信控制方法和通信设备
CN110431866B (zh) 控制面连接管理方法和装置
WO2022073491A1 (zh) 切换方法、装置、终端设备、网络设备及存储介质
JP2023547904A (ja) アプリケーションプログラム制御方法および装置、デバイス、並びに記憶媒体
WO2021147672A1 (zh) 会话处理方法及通信装置
WO2024037611A1 (zh) 注册信息同步方法、装置、设备及介质
WO2020098760A1 (zh) 消息发送及其控制方法及装置
WO2023087965A1 (zh) 一种通信方法及装置
WO2022042652A1 (zh) 上行数据处理方法、装置、网络设备、终端设备及介质
WO2020233496A1 (zh) 安全会话方法和装置
WO2019196668A1 (zh) 一种信息发送方法、密钥生成方法以及装置
WO2021147662A1 (zh) 通信方法和通信装置

Legal Events

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

Ref document number: 21744634

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021744634

Country of ref document: EP

Effective date: 20220713

NENP Non-entry into the national phase

Ref country code: DE