WO2019134657A1 - 会话控制方法、网络设备及终端 - Google Patents

会话控制方法、网络设备及终端 Download PDF

Info

Publication number
WO2019134657A1
WO2019134657A1 PCT/CN2019/070215 CN2019070215W WO2019134657A1 WO 2019134657 A1 WO2019134657 A1 WO 2019134657A1 CN 2019070215 W CN2019070215 W CN 2019070215W WO 2019134657 A1 WO2019134657 A1 WO 2019134657A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
information
terminal
network
network unit
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/070215
Other languages
English (en)
French (fr)
Inventor
柯小婉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2019134657A1 publication Critical patent/WO2019134657A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a session control method, a network device, and a terminal.
  • CIOT Cellular Internet of Things
  • the user plane CIOT means that when the terminal (User Equipment, UE) needs to be released or is inactive, the terminal can be connected to the network by suspending the terminal, and the context of the terminal is maintained in the radio access network. When the terminal needs to resume the connection with the network, it is not necessary to re-establish the context of the terminal in the radio access network.
  • the terminal may also not need to send a service request to the core network, thereby achieving the effect of saving signaling of connection establishment and reducing delay.
  • the connection between the terminal and the network may refer to a Radio Resource Control (RRC) connection between the terminal and the access network, and a connection between the access network and the core network about the terminal.
  • RRC Radio Resource Control
  • the connection establishment signaling and the reduced delay can be saved during the connection recovery, but for the suspended PDU session, especially the radio access network (RAN) If the PDU session is suspended on the side, it is impossible to decide whether to restore or not to recover the radio bearer according to the wishes of the terminal. If all PDU sessions are restored by default, restoring the PDU session that the terminal does not want to recover is wasted radio resources for establishing the radio bearer.
  • RAN radio access network
  • Some embodiments of the present disclosure provide a session control method, a network device, and a terminal, to solve the problem of complicated signaling and low resource utilization in a PDU session recovery process in a 5G system.
  • some embodiments of the present disclosure provide a session control method, which is applied to a first network element side, and includes:
  • the operation request information includes at least one of the following information: the PDU session information requested by the terminal, the PDU session information requested by the terminal, and the PDU session information requested by the terminal;
  • the PDU session processing is performed according to the operation request information.
  • some embodiments of the present disclosure further provide a network device, which is applied to the first network unit side, and includes:
  • a first obtaining module configured to obtain operation request information of the packet data unit PDU session information;
  • the operation request information includes at least one of the following information: the PDU session information requested by the terminal, the PDU session information requested by the terminal, and the terminal request to hang PDU session information;
  • the first processing module is configured to perform PDU session processing according to the operation request information.
  • some embodiments of the present disclosure provide a session control method, which is applied to a first network element side, and includes:
  • the operation request information includes at least one of the following information: the second network unit requests the restored PDU session information, the second network unit requests to release the PDU session information, and the second network unit request Suspended PDU session information;
  • the PDU session processing is performed according to the operation request information.
  • some embodiments of the present disclosure further provide a network device, which is applied to the first network unit side, and includes:
  • a second obtaining module configured to obtain operation request information of the packet data unit PDU session information;
  • the operation request information includes at least one of the following information: the second network unit requests the restored PDU session information, and the second network unit requests to release the PDU session The information and the second network element request the suspended PDU session information;
  • the second processing module is configured to perform PDU session processing according to the operation request information.
  • some embodiments of the present disclosure provide a session control method, which is applied to a second network element side, and includes:
  • the operation request information includes at least one of the following information: the PDU session information requested by the terminal, the PDU session information requested by the terminal, and the PDU session information requested by the terminal.
  • the PDU session processing is performed according to the operation request information.
  • some embodiments of the present disclosure provide a network device, which is applied to a second network unit side, and includes:
  • a third obtaining module configured to obtain operation request information of the packet data unit PDU session information;
  • the operation request information includes at least one of the following information: the PDU session information requested by the terminal, the PDU session information requested by the terminal, and the terminal request to hang PDU session information, PDU session recovery result information of the first network element, PDU session information requested by the third network element, third network element requesting release of PDU session information, third network element requesting suspended PDU session information, PDU session information with downlink data transmission requirements and PDU session information for receiving downlink data notifications;
  • the third processing module is configured to perform PDU session processing according to the operation request information.
  • some embodiments of the present disclosure provide a session control method, which is applied to a terminal side, and includes:
  • the PDU session processing is performed according to the PDU session operation response information.
  • some embodiments of the present disclosure further provide a terminal, including:
  • a third sending module configured to send, by the first network unit, operation request information of the packet data unit PDU session information
  • a second receiving module configured to receive PDU session operation response information that is sent by the first network unit according to the operation request information
  • the fourth processing module is configured to process the PDU session according to the PDU session operation response information.
  • some embodiments of the present disclosure provide a network device including a processor, a memory, and a computer program stored on the memory and executable on the processor, the processor implementing the above-described session when executing the computer program The steps of the control method.
  • some embodiments of the present disclosure provide a terminal, the terminal including a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor to implement the session control described above The steps of the method.
  • some embodiments of the present disclosure provide a computer readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the steps of the session control method described above.
  • the session control method, the network device, and the terminal of some embodiments of the present disclosure acquire operation request information of the packet data unit PDU session information; and perform PDU session processing according to the operation request information.
  • the operation request information includes at least one of the following information: PDU session information requested by the terminal, PDU session information requested by the terminal, PDU session information requested by the terminal, PDU session information requested by the second network unit, The second network element requests to release the PDU session information, and the second network element requests the suspended PDU session information.
  • the suspended terminal can recover the PDU session according to the PDU session information that needs to be restored in the operation request information when the connection is restored, thereby saving
  • the resources of the radio access network reduce signaling overhead.
  • FIG. 1 shows one of the flow diagrams of a session control method applied to a first network element of some embodiments of the present disclosure
  • FIG. 2 is a block diagram showing a module structure of a network device of a first network unit according to some embodiments of the present disclosure
  • FIG. 3 is a second schematic flowchart of a session control method applied to a first network element according to some embodiments of the present disclosure
  • FIG. 4 shows a second block diagram of a modular structure of a network device of a first network element of some embodiments of the present disclosure
  • FIG. 5 is a flow chart showing a session control method applied to a second network element according to some embodiments of the present disclosure
  • FIG. 6 is a block diagram showing a block structure of a network device of a second network unit according to some embodiments of the present disclosure
  • Figure 7 is a block diagram showing the structure of a network device of some embodiments of the present disclosure.
  • FIG. 8 is a schematic flowchart diagram of a session control method applied to a terminal according to some embodiments of the present disclosure
  • FIG. 9 is a block diagram showing the structure of a terminal of some embodiments of the present disclosure.
  • Figure 10 is a block diagram showing the structure of a terminal of some embodiments of the present disclosure.
  • FIG. 11 shows a schematic diagram of a network architecture of some embodiments of the present disclosure.
  • FIG. 12 is a flowchart showing a first example of a session control method of the present disclosure
  • FIG. 13 is a flow chart showing a second example of the session control method of the present disclosure.
  • FIG. 14 is a flow chart showing a third example of the session control method of the present disclosure.
  • 15 is a flow chart showing a fourth example of the session control method of the present disclosure.
  • 16 is a flow chart showing a fifth example of the session control method of the present disclosure.
  • FIG. 17 is a flow chart showing a sixth example of the session control method of the present disclosure.
  • FIG. 18 is a flow chart showing a seventh example of the session control method of the present disclosure.
  • Some embodiments of the present disclosure provide a session control method, which is applied to a first network element side, where the first network element includes at least one of the following: a radio access network device, a radio access network node, and a radio access network functional unit.
  • Centralized Unit CU
  • Distributed Unit DU
  • Base Station eNB
  • gNB Non-3GPP InterWorking Function
  • Access Controller AC
  • AP access point
  • WLAN Wireless Local Area Networks
  • the second network element includes at least one of the following: a core network device, a core network node, a core network functional unit, and a mobility management Entity (Mobility Management Entity, MME), Access Management Function (AMF), Session Management Function (SMF), SGW, PGW, User Plane Function UPF.
  • MME mobility management Entity
  • AMF Access Management Function
  • SGW Session Management Function
  • PGW User Plane Function UPF.
  • the user plane CIOT may be named other names, but does not affect the present disclosure.
  • suspend/release indicates suspend and/or release
  • restoring a PDU session may also be embodied as an active PDU session.
  • the session control method of some embodiments of the present disclosure specifically includes the following steps 11-12.
  • Step 11 Acquire operation request information of the packet data unit PDU session information.
  • the operation request information may include at least one of the following information: the PDU session information that the terminal requests to recover, the PDU session information that the terminal requests to release, and the PDU session information that the terminal requests to suspend.
  • the PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and QoS flow information in a PDU session.
  • the bit position in the PDU session bit map represents a PDU session identifier (eg, the PDU session identifier represented by the Nth bit is N).
  • the Nth bit position may indicate whether the operation (e.g., request recovery, request release, request suspension, suspend success) PDU session with the PDU session ID N.
  • the Nth bit indicates 1, and may indicate that one of the following session operations is performed on the corresponding PDU session: request activation, request recovery, request release, request suspension, confirmation recovery, recovery success, release success, and suspension success.
  • the Nth bit indicates 0, and may indicate that one of the following session operations is performed on the corresponding PDU session: the request is not activated, the request is not resumed, the request is not released, the request is not suspended, the confirmation cannot be restored, the recovery fails, the release fails, and the connection is suspended. Failed. It is not difficult to understand that the bytes of information that need to be transmitted can be saved by the PDU session bit map.
  • the PDU session bit map may indicate which PDU session requests the session. For example, the session can be requested by setting the Nth bit to 1 to indicate that the PDU session identifier is N.
  • the PDU session bit map may indicate which PDU session requests are released.
  • the PDU session request release indicating that the PDU session identifier is N can be set by setting the Nth bit to 1.
  • the PDU session bit map may indicate which PDU session requests are pending. For example, a PDU session request indicating that the PDU session identifier is N can be suspended by setting the Nth bit to 1.
  • the PDU session bit map may indicate which PDU session acknowledgment recovery and/or which PDU session acknowledgments cannot be recovered. For example, the recovery can be confirmed by setting the Nth bit to 1 to indicate that the PDU session identifier is N. For example, the PDU session request indicating that the PDU session identifier is N can be unrecoverable by setting the Nth bit to 0.
  • the PDU session bit map may indicate which PDU session recovery was successful and/or which PDU session confirmation recovery failed.
  • the PDU session indicating that the PDU session identifier is N can be successfully restored by setting the Nth bit to 1.
  • the PDU session recovery failure indicating that the PDU session identifier is N can be set by setting the Nth bit to 0.
  • the PDU session identification information may include QoS flow identification information.
  • the PDU session identification bit map information may include QoS flow identification bit map information, and the QoS flow information may include radio bearer information of the QoS flow mapping.
  • a PDU session can contain multiple QoS flows. Only when there is at least one QoS flow request recovery, the PDU session of its corresponding PDU needs to be restored.
  • Step 12 Perform PDU session processing according to the operation request information.
  • step 12 may include at least one of the following (1)-(3):
  • the operation request information is the PDU session information that the terminal requests to restore
  • the following operations may be performed: performing a recovery operation on the PDU session requested by the terminal, and performing a recovery operation on all the PDU sessions suspended by the terminal; All PDU sessions are resumed and, when resources are insufficient, the PDU session requested by the terminal is restored.
  • the resources mentioned herein may include various resources such as a radio resource, a CPU inside the first network unit, and a memory.
  • priority refers to assuming that the PDU session requested by the UE is PDU session 1 and PDU session 2, but the PDU session suspended by the terminal has PDU session 1, PDU session 2, PDU session 3, and PDU session 4. And PDU session 5.
  • the first network element recovers all resources when resources are sufficient, but when the resources are insufficient, the PDU session 1 and the PDU session 2 are preferentially restored. If there are additional resources after the PDU session 1 and the PDU session 2 are restored, the PDU session 3 can be further restored. , PDU session 4, etc.
  • the operation request information includes the PDU session information that the terminal requests to release
  • the PDU session requested by the terminal may be released.
  • the terminal may request the suspended operation of the suspended PDU session.
  • the step of performing a recovery operation on the PDU session may be: performing at least one of the following operations on the PDU session: restoring the context of the PDU session; restoring the radio bearer corresponding to the PDU session; and determining the QoS of the PDU session.
  • the flow allocates and/or maps radio bearer resources; recovers the connection between the first network element and the second network element with respect to the terminal.
  • step 12 may further include at least one of: sending PDU session information to the terminal to confirm recovery and/or confirming that the system cannot recover; and transmitting the PDU session recovery result information of the first network element to the second network unit. That is, the first network unit may generate PDU session information that confirms recovery and/or confirms that cannot be recovered according to the processing result and feeds back to the terminal according to the processing result; Simultaneously or after processing the PDU session, the PDU session recovery result of the first network element may be generated according to the processing result and sent to the second network element.
  • the embodiments of the present disclosure do not limit the relationship between the two steps (the foregoing one and two), and do not limit the relationship between the processing process and the processing result.
  • the processing may be performed while processing, or may be processed all. Send it together after the end.
  • the PDU session recovery result information of the first network unit may include at least one of the following information: recovering successful PDU session information, recovering failed PDU session information, requesting release of PDU session information, and requesting suspended PDU session information. .
  • the successfully restored PDU session information may be used to indicate that both the terminal and the first network unit recover a successful PDU session
  • the failed PDU session information may be used to indicate that the terminal or the first network unit recovers the failed PDU session
  • the PDU session information requested to be released may be used to indicate at least one of a PDU session in which the terminal recovers the failure, a PDU session in which the first network unit recovers, and a PDU session requested by the terminal to be released;
  • the PDU session information requesting suspension may be used to indicate at least one of a PDU session in which the terminal recovers failed, a PDU session in which the first network unit recovers, and a PDU session in which the terminal requests suspension;
  • the recovered PDU session information can be used to indicate at least one of a PDU session in which a PDU session context exists, a PDU session capable of allocating or mapping radio bearer resources, a first network element and a second network element confirming a recoverable PDU session ;
  • the PDU session that is confirmed to be unrecoverable may include: a PDU session without a PDU session context, a PDU session that cannot allocate or map radio bearer resources, a PDU session that the first network element confirms cannot be recovered, and a PDU that the second network element confirms cannot recover At least one item in the conversation.
  • the method further includes: receiving the PDU recovery result information of the terminal fed back by the terminal.
  • the PDU recovery result information of the terminal may include: at least one of the PDU session information that the terminal recovers successfully and the PDU session information that the terminal recovers.
  • the step of sending the PDU session recovery result information of the first network unit to the second network unit may further include: sending, to the second network unit, a session operation request that carries the PDU session recovery result information of the first network unit; The second network unit restores the PDU session recovery result information of the second network element according to the session operation request.
  • the PDU session recovery result information of the second network unit may include at least one of the following information: recovering successful PDU session information, recovering failed PDU session information, requesting restored PDU session information, requesting release of the PDU session. Information and PDU session information requested to be suspended.
  • the successfully restored PDU session information may be used to indicate that both the first network unit and the second network unit recover a successful PDU session
  • the failed PDU session information may be used to indicate that the second network element recovers the failed PDU session
  • the PDU session information requested by the second network unit may be used to indicate that the first network element is suspended but the second network element requests the restored PDU session, the first network element is not resumed, but the second network element requests to recover. At least one of the PDU sessions;
  • the PDU session information requested by the second network unit may be used to indicate at least one of the PDU session in which the second network element recovers the failed PDU session, the first network element recovers successfully, but the second network element requests to release the PDU session;
  • the second network element requesting the suspended PDU session information may be used to indicate at least one of the PDU session in which the terminal recovers the failed PDU session, the first network element recovers successfully, but the second network element requests the release.
  • the step of receiving the PDU session recovery result information of the second network unit returned by the second network unit according to the session operation request may further include: processing the PDU session of the terminal according to the PDU session recovery result information of the second network unit.
  • An example is that the first network element recovers the PDU sessions 1 and 2 of the terminal, but the second network element recovers successfully for PDU session 1, and fails to recover from PDU session 2. At this time, it is not difficult to understand that for the PDU session 2 that failed to recover, the second network element may indicate that the PDU session 2 fails to recover, requests to release the PDU session 2, or requests to suspend the PDU session 2.
  • the specific content of the step of processing the PDU session of the terminal according to the PDU session recovery result information of the second network unit is as follows, and details are not described herein again.
  • step 12 may include: when the operation request information includes the PDU session information requested by the terminal to be restored, performing: transmitting, to the second network unit, the PDU session information that the terminal requests to recover.
  • the method further includes: receiving, by the second network unit, the PDU session recovery result information of the second network unit that is fed back according to the PDU session information that is requested by the terminal;
  • the PDU session recovery result information of the second network unit may process the PDU session of the terminal.
  • the PDU session recovery result information of the foregoing second network unit may include at least one of the following information: the second network unit recovers successful PDU session information, the second network unit recovers failed PDU session information, and the second The network unit requests the restored PDU session information, the second network element requests the released PDU session information, and the second network element requests the suspended PDU session information.
  • the successfully restored PDU session information may be used to indicate that both the first network unit and the second network unit recover a successful PDU session
  • the failed PDU session information may be used to indicate that the second network element recovers the failed PDU session
  • the PDU session information requested by the second network unit may be used to indicate that the first network element is suspended but the second network element requests the restored PDU session, the first network element is not resumed, but the second network element requests to recover. At least one of the PDU sessions;
  • the PDU session information requested by the second network unit may be used to indicate at least one of the PDU session in which the second network element recovers the failed PDU session, the first network element recovers successfully, but the second network element requests to release the PDU session;
  • the second network element requesting the suspended PDU session information may be used to indicate at least one of the PDU session in which the terminal recovers the failed PDU session, the first network element recovers successfully, but the second network element requests the release.
  • the first network element recovers the PDU session 1, 2, 3 of the terminal and the terminal requests to recover the PDU session 1.
  • the second network element successfully restores the PDU session 1 requested by the terminal.
  • the second network element simultaneously discovers the PDU session 2 with the downlink data transmission requirement, and the recovery of the PDU session 2 is unsuccessful.
  • the second network element may indicate a request to release PDU session 3 or request to suspend PDU session 3.
  • the first network element sends a terminal request to the second network element to resume PDU session 1.
  • the second network element successfully restores the PDU session 1 requested by the terminal.
  • the second network element simultaneously discovers the PDU session 2 with the downlink data transmission requirement, and the recovery of the PDU session 2 is unsuccessful.
  • the second network element can indicate that the successful PDU sessions 1 and 2 are restored and sent to the first network element.
  • the first network element corresponds to the recovery PDU sessions 1 and 2.
  • the first network element also instructs the UE to resume PDU sessions 1 and 2.
  • the step of processing the PDU session of the terminal according to the PDU session recovery result information of the second network unit may include:
  • the PDU session that the second network unit recovers successfully may perform at least one of the following operations:
  • the PDU session indicated by the PDU session information that the second network unit recovers successfully has not been restored, and the PDU session may be restored to the PDU session (the recovery operation of the PDU session is as above, and details are not described herein again);
  • the request information for requesting release or suspension of the PDU session may be sent to the second network unit;
  • the PDU session that fails the second network element recovery may perform at least one of the following operations:
  • the second network element may request the restored PDU session to perform at least one of the following operations:
  • the PDU session requested by the second network unit may perform at least one of the following operations:
  • the second network element may request the suspended PDU session to perform at least one of the following operations:
  • step 12 can include at least one of the following:
  • the operation request information includes the PDU session information that the second network unit requests to recover, at least one of: sending the acquired PDU session information requested by the acquired second network unit to the terminal;
  • the first network unit may include at least one of the following: a radio access network device, a radio access network node, a radio access network function unit, a central unit CU, a distributed unit DU, a base station, an eNB, a gNB, an N3 IWF, and an access control.
  • a radio access network device a radio access network node
  • a radio access network function unit a radio access network function unit
  • a central unit CU a distributed unit DU
  • a base station an eNB, a gNB, an N3 IWF, and an access control.
  • Node AC access point AP device, or wireless LAN WLAN node.
  • the second network element may include at least one of the following: a core network device, a core network node, a core network functional unit, an MME, an AMF, an SMF, an SGW, a PGW, and a user plane function UPF.
  • the first network unit performs PDU session processing according to the PDU session information that the terminal requests to recover, release, and/or suspend.
  • the first network unit acquires operation request information of the PDU session information, and performs PDU session processing according to the operation request information.
  • the operation request information may include: PDU session information that the terminal requests to recover, release, and/or suspend.
  • the first network unit may obtain the PDU session information that the terminal requests to recover, release, and/or suspend by receiving a Radio Resource Control (RRC) recovery request (ie, operation request information) sent by the terminal.
  • RRC Radio Resource Control
  • the first network unit may perform a recovery operation on the PDU session that the terminal requests to restore.
  • the PDU session requested by the terminal may be released.
  • the terminal may request the suspended PDU session to suspend.
  • the first network unit may further generate, according to the processing result, PDU session information that confirms recovery and/or confirms that the PDU session cannot be recovered, and the PDU session of the first network element. Restore at least one of the result information.
  • the first network unit may send the PDU session information to the terminal to confirm the recovery and/or confirm the unrecoverable. After sending the PDU session information to the terminal to confirm the recovery and/or confirm the unrecoverable, the PDU recovery of the terminal fed back by the terminal may be received. Result information.
  • the first network unit may further send the PDU session recovery result information of the first network unit to the second network unit, and specifically send, to the second network unit, a session operation request that carries the PDU session recovery result information of the first network unit; After the session operation request is sent, the PDU session recovery result information of the second network element returned by the second network unit according to the session operation request may be received, and then the PDU session of the terminal is performed according to the PDU session recovery result information of the second network element. deal with. It should be noted that some embodiments of the present disclosure do not limit the order of the two steps.
  • the PDU session recovery result information of the second network unit may include at least one of the following information: the second network unit recovers the successfully PDU session information, the second network unit recovers the failed PDU session information, and the second network unit requests The recovered PDU session information, the PDU session information requested by the second network element, and the second network element request the suspended PDU session information.
  • the step of processing the PDU session of the terminal by the first network unit according to the PDU session recovery result information of the second network unit may be implemented by referring to the following manner:
  • the PDU session recovery result information of the second network unit is the PDU session information that the second network unit recovers successfully
  • the PDU session that the second network unit recovers successfully cannot be recovered on the first network unit or the terminal side
  • the The second network unit sends a request message requesting to release or suspend the PDU session
  • the PDU session that fails the second network element recovery may perform at least one of the following operations:
  • the PDU session requested by the second network element may perform at least one of the following operations:
  • the PDU session requested to be released by the second network element may perform at least one of the following operations:
  • requesting the suspended PDU session from the second network element may perform at least one of the following operations:
  • the first network unit may perform a recovery operation on all PDU sessions suspended by the terminal.
  • the example considers system resources. Specifically, when the RRC recovery request carries the PDU session information that the terminal requests to recover, the first network unit may perform recovery operations on all PDU sessions suspended by the terminal. When the resources are insufficient, the PDU session requested by the terminal is restored.
  • the first network unit may directly forward the operation request information to the second network unit, and receive the PDU session information feedback that the second network unit restores according to the terminal request.
  • the PDU session recovery result information of the second network unit; according to the PDU session recovery result information of the second network element, the PDU session of the terminal may be processed.
  • the first network unit acquires operation request information of the packet data unit PDU session information; according to the operation request information, PDU session processing may be performed.
  • the operation request information may include at least one of the following information: the PDU session information that the terminal requests to recover, the PDU session information that the terminal requests to release, and the PDU session information that the terminal requests to suspend.
  • the network device 200 of some embodiments of the present disclosure can implement operation request information for acquiring packet data unit PDU session information in the foregoing embodiment, and perform details of the PDU session processing method according to the operation request information.
  • the network device 200 can include the following functional modules:
  • the first obtaining module 210 is configured to obtain operation request information of the packet data unit PDU session information.
  • the operation request information may include at least one of the following information: the PDU session information requested by the terminal, the PDU session information requested by the terminal, and the terminal. Requesting pending PDU session information;
  • the first processing module 220 can be configured to perform PDU session processing according to the operation request information.
  • the first processing module 210 can include:
  • the first processing sub-module may be configured to: when the operation request information is the PDU session information requested by the terminal, perform at least one of: recovering the PDU session requested by the terminal, and recovering all the PDU sessions suspended by the terminal. And recovering all the PDU sessions suspended by the terminal and performing a recovery operation on the PDU session that the terminal requests to restore when the resources are insufficient;
  • the second processing sub-module may be configured to perform a release operation on the PDU session requested by the terminal when the operation request information is the PDU session information requested by the terminal to be released;
  • the third processing sub-module may be configured to suspend the PDU session that the terminal requests to suspend when the operation request information is the PDU session information requested by the terminal.
  • the recovery operation on the PDU session may be:
  • the first processing module may further include at least one of the following:
  • the first sending submodule may be configured to send, to the terminal, PDU session information that confirms recovery and/or confirms that the system cannot be restored;
  • the second sending submodule may be configured to send the PDU session recovery result information of the first network unit to the second network unit, where the PDU session recovery result information of the first network unit may include at least one of the following information: the recovery is successful. PDU session information, recovery of failed PDU session information, request release of PDU session information, and request for suspended PDU session information.
  • the successfully restored PDU session information may be used to indicate that the terminal and the first network unit recover the successful PDU session
  • the failed PDU session information may be used to indicate that the terminal or the first network unit recovers the failed PDU session
  • the PDU session information requested to be released may be used to indicate at least one of a PDU session in which the terminal recovers the failure, a PDU session in which the first network unit recovers, and a PDU session requested by the terminal to be released;
  • the PDU session information requesting suspension may be used to indicate at least one of a PDU session in which the terminal recovers failed, a PDU session in which the first network unit recovers, and a PDU session in which the terminal requests suspension;
  • the recovered PDU session information can be used to indicate at least one of a PDU session in which a PDU session context exists, a PDU session capable of allocating or mapping radio bearer resources, a first network element and a second network element confirming a recoverable PDU session ;
  • the PDU session that is confirmed to be unrecoverable may include: a PDU session without a PDU session context, a PDU session that cannot allocate or map radio bearer resources, a PDU session that the first network element confirms cannot be recovered, and a PDU that the second network element confirms cannot recover At least one item in the conversation.
  • the first processing module may further include:
  • the first receiving sub-module may be configured to receive the PDU recovery result information of the terminal fed back by the terminal, where the PDU recovery result information of the terminal may include: at least one of the PDU session information of the terminal recovery success and the PDU session information of the terminal recovery failure. item.
  • the second sending submodule may include:
  • the first sending unit may be configured to send, to the second network unit, a session operation request that carries the PDU session recovery result information of the first network unit;
  • the first receiving unit may be configured to receive PDU session recovery result information of the second network unit returned by the second network unit according to the session operation request.
  • the first processing module may further include:
  • the processing submodule is configured to process the PDU session of the terminal according to the PDU session recovery result information of the second network unit.
  • the first processing module may include:
  • the fourth processing sub-module may be configured to: when the operation request information includes the PDU session information that the terminal requests to restore, send the PDU session information that the terminal requests to restore to the second network unit.
  • the first processing module may further include:
  • a second receiving submodule configured to receive PDU session recovery result information of the second network unit that is fed back by the second network unit according to the PDU session information that is requested by the terminal;
  • the processing submodule is configured to process the PDU session of the terminal according to the PDU session recovery result information of the second network unit.
  • the PDU session recovery result information of the second network unit may include at least one of the following information: the second network unit recovers successful PDU session information, the second network unit recovers the failed PDU session information, and the second network unit requests recovery.
  • the PDU session information, the PDU session information requested by the second network element, and the second network element request the suspended PDU session information.
  • the processing submodule may include:
  • the first processing unit may be configured to: if the PDU session recovery result information of the second network unit is the PDU session information that is successfully recovered by the second network unit, the PDU session that is successfully recovered by detecting the second network unit cannot be in the first network unit or When the terminal side recovers, sending, to the second network unit, request information for requesting release or suspension of the PDU session;
  • the second processing unit may be configured to: if the PDU session recovery result information of the second network unit is the PDU session information that the second network unit fails to recover, perform the following operations on the PDU session in which the second network unit fails to recover. :
  • the third processing unit may be configured to: if the PDU session recovery result information of the second network unit is the PDU session information requested by the second network unit, the PDU session requested by the second network unit may perform at least one of the following operations. :
  • the fourth processing unit may be configured to: if the PDU session recovery result information of the second network unit is the PDU session information requested by the second network unit, the PDU session requested to be released by the second network unit may perform at least one of the following operations. :
  • the fifth processing unit may be configured to: if the PDU session recovery result information of the second network unit requests the suspended PDU session information for the second network unit, requesting the suspended PDU session for the second network unit may perform at least one of the following operations One:
  • the PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and QoS flow information in a PDU session.
  • the first network unit may include at least one of the following: a radio access network device, a radio access network node, a radio access network function unit, a central unit CU, a distributed unit DU, a base station, a non-3GPP interoperation function N3IWF, Access control node AC, access point AP device or wireless local area network WLAN node;
  • the second network unit may include at least one of the following: a core network device, a core network node, a core network function unit, a mobility management entity MME, an access management function AMF, a session management function SMF, an SGW, a PGW, and a user plane function UPF.
  • the network device of some embodiments of the present disclosure performs operation request information by acquiring packet data unit PDU session information; and performs PDU session processing according to the operation request information.
  • the operation request information may include at least one of the following information: the PDU session information that the terminal requests to recover, the PDU session information that the terminal requests to release, and the PDU session information that the terminal requests to suspend.
  • the suspended terminal can recover the PDU session according to the PDU session information that needs to be restored in the operation request information when the connection is restored, thereby saving
  • the resources of the radio access network reduce signaling overhead.
  • the session control method is applied to the first network element, as shown in FIG. 3, and further includes the following steps 31-32.
  • Step 31 Acquire operation request information of packet data unit PDU session information.
  • the operation request information may include at least one of the following information: the second network unit requests the restored PDU session information, the second network unit requests to release the PDU session information, and the second network unit requests the suspended PDU session information.
  • the PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and QoS flow information in a PDU session.
  • the bit position in the PDU session bit map may represent a PDU session identifier (eg, the PDU session identifier represented by the Nth bit is N).
  • the Nth bit position may indicate whether the operation (such as request recovery, request release, request suspension, suspend success) PDU session with the PDU session identifier N.
  • the Nth bit indicates 1, and may indicate that one of the following session operations is performed on the corresponding PDU session: request activation, request recovery, request release, request suspension, confirm recovery, recovery success, release success, and suspend success.
  • the Nth bit indicates 0, and may indicate that one of the following session operations is performed on the corresponding PDU session: the request is not activated, the request is not resumed, the request is not released, the request is not suspended, the confirmation cannot be restored, the recovery fails, the release fails, and the connection is suspended. Failed. It is not difficult to understand that the bytes of information that need to be transmitted can be saved by the PDU session bit map.
  • the PDU session bit map may indicate which PDU session requests the session. For example, the session can be requested by setting the Nth bit to 1 to indicate that the PDU session identifier is N.
  • the PDU session bit map may indicate which PDU session requests are released.
  • the PDU session request release indicating that the PDU session identifier is N can be set by setting the Nth bit to 1.
  • the PDU session bit map may indicate which PDU session requests are pending. For example, a PDU session request indicating that the PDU session identifier is N can be suspended by setting the Nth bit to 1.
  • the PDU session bit map may indicate which PDU session acknowledgment recovery and/or which PDU session acknowledgments cannot be recovered. For example, the recovery can be confirmed by setting the Nth bit to 1 to indicate that the PDU session identifier is N. For example, the PDU session request indicating that the PDU session identifier is N can be unrecoverable by setting the Nth bit to 0.
  • the PDU session bit map may indicate which PDU session recovery was successful and/or which PDU session confirmation recovery failed.
  • the PDU session indicating that the PDU session identifier is N can be successfully restored by setting the Nth bit to 1.
  • the PDU session recovery failure indicating that the PDU session identifier is N can be set by setting the Nth bit to 0.
  • the PDU session information may include at least one of the following information: QoS flow identification information, recovery indication information, suspension indication information, release indication information, QoS flow identification bit map information, and radio bearer information of the QoS flow mapping.
  • a PDU session can contain multiple QoS flows. Only when there is at least one QoS flow request recovery, the PDU session of its corresponding PDU needs to be restored.
  • Step 32 Perform PDU session processing according to the operation request information.
  • step 32 may include at least one of the following (1)-(3):
  • the recovery operation may be performed on the PDU session requested by the second network unit
  • the release operation may be performed on the PDU session requested by the second network unit
  • the second network unit may request the suspended PDU session to suspend operation.
  • the step of performing a recovery operation on the PDU session may be: performing at least one of the following operations on the PDU session: restoring the context of the PDU session; restoring the radio bearer corresponding to the PDU session; and determining the QoS of the PDU session.
  • the flow allocates and/or maps radio bearer resources; recovers the connection between the first network element and the second network element with respect to the terminal.
  • step 32 may further include: sending operation request information to the terminal.
  • the operation request information includes the PDU session information requested by the second network unit to be restored, at least one of: transmitting, to the terminal, the PDU session information requested by the second network unit to be restored; when the operation request information includes When the second network unit requests the released PDU session information, at least one of: sending the second network unit to the terminal to request release of the PDU session information; and when the operation request information includes the second network element requesting the suspended PDU session information, At least one of the following may be performed: sending, to the terminal, the PDU session information requested by the second network element to be suspended.
  • step 31 may be: receiving a paging message or a notification message sent by the second network unit.
  • the operation request information is carried in a paging message or a notification message.
  • Sending the operation request information to the terminal may be: sending the received paging message or notification message to the terminal;
  • the paging message or the notification message may carry at least one of the information indicating the PDU session requested by the second network unit to be restored, the second network unit requesting to release the PDU session information, and the second network unit requesting the suspended PDU session information. .
  • the first network unit may perform PDU session processing according to the PDU session information that the second network unit requests to recover, release, and/or suspend.
  • the first network unit may receive a paging message or a notification message (ie, operation request information) sent by the second network unit, and send the received paging message or notification message to the terminal.
  • the paging message or the notification message may carry at least one of PDU session information indicating that the second network unit requests to be restored, the second network element requesting to release the PDU session information, and the second network element requesting the suspended PDU session information.
  • the paging message or the notification message includes the PDU session information that the second network unit requests to recover, at least one of: transmitting the PDU session information requested by the second network unit to the terminal to the terminal;
  • the paging message or the notification message includes the PDU session information requested by the second network unit to be released, at least one of: sending the second network unit to the terminal to request release of the PDU session information;
  • the paging message or the notification message includes the second network element requesting the suspended PDU session information
  • at least one of the following may be performed: sending, to the terminal, the PDU session information requested by the second network element to be suspended.
  • the step of performing a recovery operation on the PDU session is to perform at least one of the following operations on the PDU session: restoring the context of the PDU session; and recovering the radio bearer corresponding to the PDU session; Allocating and/or mapping radio bearer resources for the QoS flow of the PDU session; restoring the connection with the terminal between the first network element and the second network element.
  • the step of suspending the PDU session is to perform at least one of the following operations on the PDU session: suspending the context of the PDU session, suspending the radio bearer context corresponding to the PDU session, releasing the radio bearer resource corresponding to the PDU session, and The terminal sends PDU session information.
  • the step of releasing the PDU session may be performed by performing at least one of the following operations: releasing the context of the PDU session, releasing the radio bearer context corresponding to the PDU session, releasing the radio bearer resource corresponding to the PDU session, and transmitting the PDU to the terminal. Session information.
  • the first network unit may acquire operation request information of the packet data unit PDU session information; according to the operation request information, PDU session processing may be performed.
  • the operation request information may include at least one of the following information: the second network unit requests the restored PDU session information, the second network unit requests to release the PDU session information, and the second network unit requests the suspended PDU session information.
  • the network device 400 of some embodiments of the present disclosure can implement the operation request information for acquiring the packet data unit PDU session information in the foregoing embodiment, and perform the PDU session processing method according to the operation request information, and achieve For the same effect, the network device 400 can include the following functional modules:
  • the second obtaining module 410 is configured to acquire operation request information of the packet data unit PDU session information;
  • the operation request information may include at least one of the following information: the second network unit requests the restored PDU session information, and the second network unit requests to release PDU session information, and the second network element requests the suspended PDU session information;
  • the second processing module 420 is configured to perform PDU session processing according to the operation request information.
  • the second processing module 420 can include at least one of the following:
  • the fifth processing sub-module may be configured to perform a recovery operation on the PDU session requested by the second network unit when the operation request information is the PDU session information requested by the second network unit;
  • the sixth processing sub-module may be configured to perform a release operation on the PDU session requested by the second network unit when the operation request information is the PDU session information requested by the second network unit to be released;
  • the seventh processing submodule may be configured to: when the operation request information requests the second network unit to request the suspended PDU session information, perform a suspend operation on the second network unit requesting the suspended PDU session.
  • the second processing module 420 may further include:
  • the third sending submodule is configured to send operation request information to the terminal.
  • the second obtaining module 410 is further configured to: receive a paging message or a notification message sent by the second network unit;
  • the third sending submodule may further perform: sending the received paging message or notification message to the terminal;
  • the paging message or the notification message may carry at least one of the information indicating the PDU session requested by the second network unit to be restored, the second network unit requesting to release the PDU session information, and the second network unit requesting the suspended PDU session information. .
  • the first network unit acquires operation request information of the packet data unit PDU session information; according to the operation request information, PDU session processing may be performed.
  • the operation request information may include at least one of the following information: the second network unit requests the restored PDU session information, the second network unit requests to release the PDU session information, and the second network unit requests the suspended PDU session information.
  • Some embodiments of the present disclosure provide a session control method, which is applied to a second network element side, where the first network element may include at least one of the following: a radio access network device, a radio access network node, and a radio access network function. a unit, a centralized unit CU, a distributed unit DU, a base station, an eNB, a gNB, a non-3GPP interworking function N3IWF, an access control AC node, an access point AP device, or a wireless local area network WLAN node; the second network element may include at least the following A: core network device, core network node, core network function unit, mobility management entity MME, access management function AMF, session management function SMF, service gateway SGW, PDN gateway PGW, user plane function UPF.
  • the first network element may include at least one of the following: a radio access network device, a radio access network node, and a radio access network function.
  • the third network unit includes at least one of the following: a core network device, a core network node, a core network function unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, and a user plane function.
  • a core network device a core network node, a core network function unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, and a user plane function.
  • UPF User Plane Radio Function
  • the session control method of some embodiments of the present disclosure may include the following steps 51-52.
  • Step 51 Acquire operation request information of the packet data unit PDU session information.
  • the operation request information may include at least one of the following information: the PDU session information requested by the terminal to be restored, the PDU session information requested by the terminal, the PDU session information requested by the terminal, and the PDU session recovery result information of the first network element.
  • the third network unit requests the restored PDU session information, the third network unit requests to release the PDU session information, the third network unit requests the suspended PDU session information, the PDU session information with the downlink data transmission requirement, and the downlink data notification received. PDU session information.
  • the PDU session recovery result information of the first network unit may include: at least one of recovering successful PDU session information, recovering failed PDU session information, requesting release of PDU session information, and requesting suspended PDU session information. ;
  • the PDU session information that the terminal requests to restore may be the PDU session information that is forwarded by the first network unit or requested by the terminal to be restored.
  • the interface message is sent to the second network unit through an interface message such as S1/NG.
  • the terminal directly requests the restored PDU session information through the NAS message.
  • the PDU session information that the terminal requests to release may be the PDU session information that is forwarded by the first network unit or requested by the terminal to be released by the terminal;
  • the PDU session information that the terminal requests to suspend may be PDU session information that is forwarded by the first network unit or requested by the terminal to be restored by the terminal.
  • the PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and QoS flow information in a PDU session.
  • Step 52 Perform PDU session processing according to the operation request information.
  • step 52 can include at least one of the following:
  • the PDU session that needs to perform the recovery operation may include: the PDU session recovery result information of the first network unit indicates the PDU session that is successfully restored, the PDU session indicated by the PDU session information requested by the terminal, and the PDU session requested by the third network unit.
  • the PDU session indicated by the information, the PDU session indicated by the PDU session information with the downlink data transmission requirement, the PDU session indicated by the PDU session information receiving the downlink data notification, and the PDU session recovery result information of the first network element indicate that the recovery is successful and the third
  • the PDU session requested by the network unit, the PDU session recovery result information of the first network unit, the PDU session indicated by the PDU session information that the recovery is successful and has the downlink data transmission requirement, and the PDU session recovery result information of the first network element indicate that the recovery is successful and
  • the PDU session indicated by the PDU session information that receives the downlink data notification, and at least one of the PDU sessions that the terminal requests to recover and the PDU session recovery result information of the first network element indicates that the recovery is successful.
  • the at least one of the PDU session indicated by the PDU session information requested by the terminal and the PDU session indicated by the first network element requesting to release the PDU session information may perform the following operations: releasing the terminal and/or the PDU requested by the second network unit to release Conversation.
  • the at least one of the PDU session indicated by the terminal requesting the suspended PDU session information and the PDU session indicated by the first network element requesting to suspend the PDU session information may perform the following operations: suspending the terminal and/or the second network element request Released PDU session.
  • At least one of the following operations may be performed:
  • the request user plane function deletes the PDU session that failed to recover.
  • the method may further include:
  • the PDU session recovery result information of the second network unit may include at least one of the following information: the second network unit recovers successful PDU session information, the second network unit recovers the failed PDU session information, and the second network unit requests recovery. PDU session information, PDU session information requested by the second network element, and PDU session information requested by the second network element;
  • the PDU session information that the second network requests to recover may include: at least one of PDU session information of the downlink data transmission requirement, a PDU session that receives the downlink data notification, and a PDU session that the third network unit requests to recover;
  • the second network requesting the suspended PDU session information may include: a PDU session in which the second network recovery fails, a PDU session in which the first network unit recovers successfully but the second network recovery fails, the first network unit and the terminal recover successfully but the second network Recovering at least one of the failed PDU sessions;
  • the PDU session information requested by the second network may include: a PDU session in which the second network recovery fails, a PDU session in which the first network unit recovers successfully but the second network fails to recover, the first network unit and the terminal recover successfully but the second network recovers. At least one of the failed PDU sessions.
  • step 52 may include: when the operation request information is the third network unit requesting the restored PDU session information, the third network unit requests to release the PDU session information, and the third network unit requests the suspended PDU session information.
  • the PDU that the third network unit requests to recover may be sent to the first network unit by using a paging request or a notification message.
  • the session information third network unit requests at least one of releasing the PDU session information, the third network element requesting the suspended PDU session information, the PDU session information having the downlink data transmission requirement, and the PDU session information receiving the downlink data notification.
  • the first network unit obtains a RRC session request information (ie, operation request information) sent by the terminal, and acquires PDU session information that the terminal requests to restore, release, and/or suspend, and Resume, release, and/or suspend processing of the corresponding PDU session.
  • the first network unit may further recover the result information of the PDU session of the first network unit according to the processing result, and send the information to the second network unit (such as AMF).
  • the second network unit such as AMF
  • the PDU session recovery result information of the first network element may include at least one of the following information: the terminal requests recovery, release, and/or suspension of PDU session information, recovery of successful PDU session information, recovery of failed PDU session information, request Released PDU session information and requested pending PDU session information.
  • the second network unit may also acquire PDU session information requested to be restored, released, and/or suspended by the third network element (eg, SMF, user plane function, etc.), and PDU session information and/or reception with downlink data transmission requirements. PDU session information to the downstream data notification.
  • the third network element eg, SMF, user plane function, etc.
  • the second network unit (such as the SMF) may perform the following operations:
  • the PDU session recovery result information of the first network unit indicates that the PDU session is successfully restored, the PDU session indicated by the PDU session information requested by the terminal, and the PDU session information indication requested by the third network unit are restored.
  • the PDU session, the PDU session indicated by the PDU session information with the downlink data transmission requirement, the PDU session indicated by the PDU session information receiving the downlink data notification, and the PDU session recovery result information of the first network element indicate that the recovery is successful and the third network element
  • the PDU session requesting recovery, the PDU session recovery result information of the first network unit, the PDU session indicated by the PDU session information indicating that the recovery is successful and having the downlink data transmission requirement, and the PDU session recovery result information of the first network element indicate that the recovery is successful and received
  • At least one of the following operations may be performed by at least one of a PDU session indicated by the PDU session information of the downlink data notification and a PDU session recovery result information of the first network element that is restored by the terminal and indicating that the PDU session is successfully restored:
  • the at least one of the PDU session indicated by the PDU session information requested by the terminal and the PDU session indicated by the first network element requesting to release the PDU session information may perform the following operations: releasing the terminal and/or the PDU requested by the second network unit to release Conversation
  • the at least one of the PDU session indicated by the terminal requesting the suspended PDU session information and the PDU session indicated by the first network element requesting to suspend the PDU session information may perform the following operations: suspending the terminal and/or the second network element request Released PDU session;
  • At least one of the following operations may be performed:
  • the user plane function entity is requested to delete the PDU session that failed to recover.
  • the second network unit may further include: generating PDU session recovery result information of the second network unit, and sending the PDU session recovery result information of the second network unit to the first The network unit and/or is transmitted to the terminal via the first network element.
  • the first network unit can further process the PDU session according to the PDU session recovery result information of the second network unit.
  • the first network unit may directly forward the operation request information to the second network unit after receiving the operation request information sent by the terminal, and the second network unit directly processes the PDU session of the terminal according to the operation request.
  • the operation request information may include: PDU session information that the terminal requests to recover, release, and/or suspend.
  • the second network unit in addition to processing the PDU session, may acquire the PDU session information requested to be restored, released, and/or suspended by the third network unit (such as SMF, user plane function, etc.), as in scenario 4.
  • PDU session information with downstream data transmission requirements and/or PDU session information for receiving downlink data notification For the processing of the corresponding PDU session by the second network unit, refer to scenario 4, and therefore no further details are provided herein.
  • the second network unit acquires PDU session information requested to be restored, released, and/or suspended by the third network element (such as SMF, user plane function, etc.), and PDU session information and/or PDU session information with downlink data transmission requirements.
  • the third network element such as SMF, user plane function, etc.
  • PDU session information and/or PDU session information with downlink data transmission requirements.
  • the second network unit performs operation request information by acquiring packet data unit PDU session information; and performs PDU session processing according to the operation request information.
  • the operation request information may include at least one of the following information: the operation request information includes at least one of the following information: the PDU session information requested by the terminal to be restored, the PDU session information requested by the terminal, and the pending PDU session requested by the terminal.
  • the suspended terminal can recover the PDU session according to the PDU session information that needs to be restored in the operation request information when the connection is restored, thereby saving
  • the resources of the radio access network reduce signaling overhead.
  • the network device 60 of some embodiments of the present disclosure can implement the operation request information for acquiring the packet data unit PDU session information in the foregoing embodiment, and perform the PDU session processing method according to the operation request information, and achieve For the same effect, the network device 600 specifically includes the following functional modules:
  • the third obtaining module 610 may be configured to obtain operation request information of the packet data unit PDU session information.
  • the operation request information may include at least one of the following information: the PDU session information that the terminal requests to be restored, the PDU session information that the terminal requests to release, The terminal requests the suspended PDU session information, the PDU session recovery result information of the first network unit, the PDU session information requested by the third network unit, the third network unit requests to release the PDU session information, and the third network unit requests the suspended PDU. Session information, PDU session information with downlink data transmission requirements, and PDU session information for receiving downlink data notifications;
  • the third processing module 620 can be configured to perform PDU session processing according to the operation request information.
  • the PDU session recovery result information of the first network unit may include at least one of the following information: recovering successful PDU session information, recovering failed PDU session information, requesting release of PDU session information, and requesting suspended PDU session information. ;
  • the PDU session information requested by the terminal may be the PDU session information that is forwarded by the first network unit or requested by the terminal to be restored by the terminal;
  • the PDU session information that the terminal requests to release may be the PDU session information that is forwarded by the first network unit or requested by the terminal to be released by the terminal;
  • the PDU session information that the terminal requests to suspend may be PDU session information that is forwarded by the first network unit or requested by the terminal to be restored by the terminal.
  • the third processing module 620 can include at least one of the following:
  • the eighth processing submodule is configured to perform at least one of the following operations on the PDU session that needs to be restored:
  • the PDU session that needs to perform the recovery operation may include: the PDU session recovery result information of the first network unit indicates the PDU session that is successfully restored, the PDU session indicated by the PDU session information requested by the terminal, and the PDU session requested by the third network unit.
  • the PDU session indicated by the information, the PDU session indicated by the PDU session information with the downlink data transmission requirement, the PDU session indicated by the PDU session information receiving the downlink data notification, and the PDU session recovery result information of the first network element indicate that the recovery is successful and the third
  • the PDU session requested by the network unit, the PDU session recovery result information of the first network unit, the PDU session indicated by the PDU session information that the recovery is successful and has the downlink data transmission requirement, and the PDU session recovery result information of the first network element indicate that the recovery is successful and At least one of a PDU session indicated by the PDU session information that receives the downlink data notification, and a PDU session that the terminal requests to recover and the PDU session recovery result information of the first network element indicates that the recovery is successful.
  • the ninth processing submodule may be configured to: at least one of a PDU session indicated by the PDU session information requested by the terminal to be released and a PDU session indicated by the first network element requesting release of the PDU session information, to perform the following operations: releasing the terminal and/or The second network element requests the released PDU session;
  • the tenth processing submodule may be configured to: at least one of a PDU session indicated by the terminal requesting the suspended PDU session information and a PDU session indicated by the first network element to suspend the PDU session information, and performing the following operations: suspending the terminal And/or the PDU session requested by the second network element to be released;
  • the eleventh processing submodule may be used to recover the failed PDU session indicated by the PDU session recovery result information of the first network unit, and may perform at least one of the following operations:
  • the user plane function entity is requested to delete the PDU session that failed to recover.
  • the network device 600 may further include:
  • the first generating module may be configured to generate PDU session recovery result information of the second network unit, where the PDU session recovery result information of the second network unit may include at least one of the following information: the second network unit recovers the successfully PDU The session information, the PDU session information of the second network unit recovery failure, the PDU session information requested by the second network unit, the PDU session information requested by the second network unit, and the suspended PDU session information by the second network unit;
  • the second sending module may be configured to send the PDU session recovery result information of the second network unit to the first network unit and/or to the terminal by using the first network unit.
  • the PDU session information that the second network requests to recover may include at least one of the following: PDU session information of the downlink data transmission requirement, a PDU session that receives the downlink data notification, and a PDU session that the third network unit requests to recover;
  • the second network requesting the suspended PDU session information may include at least one of the following: a PDU session in which the second network recovery fails, a PDU session in which the first network unit recovers successfully but the second network fails to recover, the first network unit, and the terminal recovers successfully. But the second network recovers the failed PDU session;
  • the PDU session information requested by the second network may include at least one of the following: a PDU session in which the second network recovery fails, a PDU session in which the first network unit recovers successfully but the second network fails to recover, the first network unit, and the terminal recovers successfully but The second network recovers the failed PDU session.
  • the third processing module 620 may further include:
  • the twelfth processing submodule may be configured to: when the operation request information is the third network unit requesting the restored PDU session information, the third network unit requests to release the PDU session information, the third network unit requests the suspended PDU session information, and has the downlink And transmitting, by the paging request or the notification message, the PDU session information requested by the third network unit to be restored by the paging request or the notification message, by using at least one of the PDU session information of the data transmission requirement and the PDU session information of the downlink data notification.
  • the network unit requests at least one of releasing the PDU session information, the third network element requesting the suspended PDU session information, the PDU session information having the downlink data transmission requirement, and the PDU session information receiving the downlink data notification.
  • the PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and QoS flow information in a PDU session.
  • the first network unit may include at least one of the following: a radio access network device, a radio access network node, a radio access network function unit, a central unit CU, a distributed unit DU, a base station, an eNB, a gNB, an N3IWF, and an AC. , an access point AP device or a wireless local area network WLAN node;
  • the second network unit may include at least one of the following: a core network device, a core network node, a core network functional unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, and a user plane.
  • Function UPF Function UPF
  • the third network unit may include at least one of the following: a core network device, a core network node, a core network function unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, a user plane.
  • Function UPF a core network device, a core network node, a core network function unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, a user plane.
  • Function UPF Function
  • the network device of some embodiments of the present disclosure performs operation of the PDU session according to the operation request information by acquiring operation request information of the packet data unit PDU session information.
  • the operation request information may include at least one of the following information: the operation request information may include at least one of the following information: the PDU session information requested by the terminal to be restored, the PDU session information requested by the terminal to be released, and the PDU requested by the terminal to be suspended. Session information, PDU session recovery result information of the first network element, PDU session information requested by the third network element, third network element requesting release of PDU session information, third network element requesting suspended PDU session information, and downlink data Transmitting required PDU session information and PDU session information for receiving downlink data notification.
  • the suspended terminal can recover the PDU session according to the PDU session information that needs to be restored in the operation request information when the connection is restored, thereby saving
  • the resources of the radio access network reduce signaling overhead.
  • an embodiment of the present disclosure further provides a network device, including a processor, a memory, and a computer program stored on the memory and operable on the processor, the processor executing the computer program
  • a network device including a processor, a memory, and a computer program stored on the memory and operable on the processor, the processor executing the computer program
  • Some embodiments of the present disclosure also provide a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps of the session control method as above.
  • the computer readable storage medium of the present disclosure may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memory.
  • the network device 700 can include an antenna 71, a radio frequency device 72, and a baseband device 73.
  • the antenna 71 is connected to the radio frequency device 72.
  • the radio frequency device 72 receives information through the antenna 71 and transmits the received information to the baseband device 73 for processing.
  • the baseband device 73 processes the information to be transmitted and transmits it to the radio frequency device 72.
  • the radio frequency device 72 processes the received information and transmits it via the antenna 71.
  • the above-described band processing device may be located in the baseband device 73, and the method performed by the network device in the above embodiment may be implemented in the baseband device 73, which includes the processor 74 and the memory 75.
  • the baseband device 73 may include, for example, at least one baseband board having a plurality of chips disposed thereon, as shown in FIG. 7, one of which is, for example, a processor 74, coupled to the memory 75 to invoke a program in the memory 75 to execute The network device operation shown in the above method embodiment.
  • the baseband device 73 can also include a network interface 76 for interacting with the radio frequency device 72, such as a common public radio interface (CPRI).
  • a network interface 76 for interacting with the radio frequency device 72, such as a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the processor here may be a processor or a collective name of multiple processing elements.
  • the processor may be a CPU, an ASIC, or one or more configured to implement the method performed by the above network device.
  • An integrated circuit such as one or more microprocessor DSPs, or one or more field programmable gate array FPGAs.
  • the storage element can be a memory or a collective name for a plurality of storage elements.
  • Memory 75 can be either volatile memory or non-volatile memory, or can include both volatile and non-volatile memory.
  • the non-volatile memory may be a Read-Only Memory (ROM), a Programmable ROM (Programmable ROM), or an Erasable PROM (EPROM). , electrically erasable programmable read only memory (EEPROM) or flash memory.
  • the volatile memory may be a Random Access Memory (RAM), which is used as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous).
  • DRAM double data rate synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM Synchlink DRAM
  • DRRAM Direct Memory Bus
  • the network device of some embodiments of the present disclosure further includes a computer program stored on the memory 75 and operable on the processor 74, and the processor 74 calls the computer program in the memory 75 to execute FIG. 2, FIG. 4 or FIG. The method performed by each module shown in 6.
  • the network device in some embodiments of the present disclosure performs operation request information by acquiring packet data unit PDU session information; and performs PDU session processing according to the operation request information.
  • the suspended terminal can recover the PDU session according to the PDU session information that needs to be restored in the operation request information when the connection is restored, thereby saving
  • the resources of the radio access network reduce signaling overhead.
  • the session control method of some embodiments of the present disclosure is applied to the terminal side, and specifically includes the following steps 81-83.
  • Step 81 Send operation request information of the packet data unit PDU session information to the first network unit.
  • the operation request information may include at least one of the following: the PDU session information requested by the terminal itself, the PDU session information requested by the second network, and the PDU session information requested by the first network.
  • Step 82 Receive PDU session operation response information sent by the first network unit according to the operation request information.
  • the PDU session operation response information information includes: confirming recovery and/or confirming that the PDU session information cannot be recovered.
  • Step 83 Process the PDU session according to the PDU session operation response information information.
  • the step of processing the PDU session according to the information of confirming the recovery and/or confirming the PDU session that cannot be recovered may include at least one of: recovering the confirmed PDU session according to the information of the PDU session confirmed to be restored; Confirm the information of the PDU session that cannot be recovered, release or suspend the PDU session that cannot be recovered.
  • the method may further include: generating PDU session information requesting recovery. After the PDU session information requested to be restored is generated, the PDU session information that is requested to be restored is sent to the first network unit, and specifically, may be sent by using an RRC recovery request.
  • the method may further include: receiving the PDU session information that is requested by the first network unit to be restored. Specifically, the PDU session information that is requested to be recovered by the first network unit may be received by paging.
  • the method may further include: receiving, by the first network unit, the PDU session information that is requested by the second network unit to be restored. Specifically, the PDU session information requested by the second network unit sent by the first network unit may be received by paging.
  • the method may further include: receiving, by using the notification message, the PDU session information that the second unit requests to recover.
  • the method may further include: after recovering or confirming the information of the PDU session that cannot be recovered according to the confirmation; after the step of processing the PDU session, the method may further include: after generating the PDU session processing
  • the PDU session recovery result information of the terminal is fed back to the first network element.
  • the PDU recovery result information of the terminal may include at least one of the following information: the PDU session information that the terminal recovers successfully, the PDU session information that the terminal recovers failed, the PDU session information that the terminal releases successfully, and the PDU session information that the terminal suspends.
  • the foregoing PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and PDU session.
  • Medium QoS flow information The bit position in the PDU session identification bit map represents the PDU session identification, and a bit position indicates whether to restore whether the PDU session represented by the bit is restored.
  • the foregoing first network unit may include at least one of the following: a radio access network device, a radio access network node, a radio access network function unit, a central unit CU, a distributed unit DU, a base station, an eNB, a gNB, an N3 IWF, and an access.
  • the second network unit may include at least one of the following: a core network device, a core network node, a core network functional unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, and a user plane.
  • Function UPF Function
  • Some embodiments of the present disclosure by cooperation of the terminal, the first network unit, and the second network unit, can suspend the PDU session as needed when the connection is restored, save resources of the radio access network, and reduce signaling overhead. .
  • the terminal 900 of some embodiments of the present disclosure can implement the details of the method for sending a packet data unit PDU session information requesting to be restored to the first network unit in the foregoing embodiment, and achieve the same effect, the terminal 900
  • the following functional modules can be included:
  • the third sending module 910 is configured to send, to the first network unit, operation request information of the packet data unit PDU session information;
  • the second receiving module 920 is configured to receive PDU session recovery result information of the first network unit that is sent by the first network unit according to the operation request information;
  • the fourth processing module 930 is configured to process the PDU session according to the PDU session recovery result information of the first network unit.
  • the operation request information includes at least one of the following:
  • the PDU session information requested by the terminal itself the PDU session information requested by the second network, and the PDU session information requested by the first network.
  • the terminal 900 may further include at least one of the following:
  • a second generation module configured to generate PDU session information that is requested to be restored
  • a third receiving module configured to receive, by the first network unit, the PDU session information that is requested to be restored
  • the fourth sending module is configured to receive, by using the first network unit, the PDU session information that is requested by the second network unit to be restored.
  • the PDU session recovery result information of the first network unit may include: confirming recovery and/or confirming PDU session information that cannot be recovered;
  • the fourth processing module 930 can include at least one of the following:
  • the thirteenth processing sub-module may be configured to process the PDU session according to the information of the PDU session that confirms recovery and/or confirms that the unrecoverable PDU session.
  • the thirteenth processing submodule may be configured to: resume confirming the restored PDU session according to the information of the PDU session that is confirmed to be restored;
  • the PDU session that cannot be recovered is released or suspended according to the information of the PDU session that is confirmed to be unrecoverable.
  • the fourth processing module 930 may further include:
  • the feedback sub-module may be used to generate the PDU session recovery result information of the terminal after the PDU session is processed and fed back to the first network unit.
  • the PDU recovery result information of the terminal may include at least one of the following information: the terminal is successfully restored.
  • the PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and QoS flow information in the PDU session. .
  • the first network unit may include at least one of the following: a radio access network device, a radio access network node, a radio access network function unit, a central unit CU, a distributed unit DU, a base station, an eNB, a gNB, an N3 IWF, and a connection.
  • a radio access network device a radio access network node
  • a radio access network function unit a central unit CU
  • a distributed unit DU a base station
  • an eNB a gNB
  • N3 IWF an N3 IWF
  • the second network unit may include at least one of the following: a core network device, a core network node, a core network functional unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, and a user plane.
  • Function UPF Function
  • some embodiments of the present disclosure by cooperation of the terminal, the first network unit, and the second network unit, can suspend the PDU session as needed when the connection is restored, thereby saving resources of the radio access network. , reducing signaling overhead.
  • each module of the above network device and terminal is only a division of logical functions. In actual implementation, it may be integrated into one physical entity in whole or in part, or may be physically separated. And these modules can all be implemented by software in the form of processing component calls; or all of them can be implemented in hardware form; some modules can be realized by processing component calling software, and some modules are realized by hardware.
  • the determining module may be a separately set processing element, or may be integrated in one of the above-mentioned devices, or may be stored in the memory of the above device in the form of program code, by a processing element of the above device. Call and execute the functions of the above determination module.
  • the implementation of other modules is similar.
  • each step of the above method or each of the above modules may be completed by an integrated logic circuit of hardware in the processor element or an instruction in a form of software.
  • the above modules may be one or more integrated circuits configured to implement the above method, such as one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors ( For example, digital signal processor (DSP), or one or more Field Programmable Gate Array (FPGA).
  • ASICs Application Specific Integrated Circuits
  • DSP digital signal processor
  • FPGA Field Programmable Gate Array
  • the processing component may be a general purpose processor, such as a central processing unit (CPU) or other processor that can call the program code.
  • CPU central processing unit
  • these modules can be integrated and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • FIG. 10 is a schematic diagram of a hardware structure of a terminal that implements various embodiments of the present disclosure.
  • the terminal 100 includes, but is not limited to, a radio frequency unit 101, a network module 102, and an audio output unit 103.
  • the terminal structure shown in FIG. 10 does not constitute a limitation to the terminal, and the terminal may include more or less components than those illustrated, or some components may be combined, or different component arrangements.
  • the terminal includes, but is not limited to, a mobile phone, a tablet, a notebook, a palmtop, an in-vehicle terminal, a wearable device, a pedometer, and the like.
  • the radio frequency unit 101 can be configured to send, to the first network unit, packet data unit PDU session information that is requested to be restored under the control of the processor 1010.
  • the PDU session information requested to be restored may include at least one of the following:
  • the PDU session information requested by the terminal itself the PDU session information requested by the second network, and the PDU session information requested by the first network.
  • the processor 1010 may be configured to perform at least one of the following before sending the requested packet data unit PDU session information to the first network unit:
  • the processor 1010 is further configured to: receive acknowledgment restored PDU session information fed back by the first network unit, and/or confirm information of the PDU session that cannot be recovered;
  • the PDU session is processed according to the information confirming the recovery or confirmation of the PDU session that cannot be recovered.
  • the processor 1010 is further configured to: resume confirming the restored PDU session according to the information of the PDU session that is confirmed to be restored;
  • the PDU session that cannot be recovered is released or suspended according to the information of the PDU session that is confirmed to be unrecoverable.
  • the processor 1010 is further configured to: generate PDU session recovery result information of the terminal after the PDU session processing and feed back to the first network unit; where the PDU recovery result information of the terminal may include at least one of the following information: The successful PDU session information, the PDU session information that the terminal recovers failed, the PDU session information that the terminal releases successfully, and the PDU session information that the terminal suspends.
  • the PDU session information may include at least one of the following information: PDU session identification information, recovery indication information, recovery indication information, suspension indication information, release indication information, PDU session identification bit map information, and QoS flow in the PDU session. information.
  • the foregoing first network unit may include at least one of the following: a radio access network device, a radio access network node, a radio access network function unit, a central unit CU, a distributed unit DU, a base station, an eNB, a gNB, and an N3 IWF.
  • the second network unit may include at least one of the following: a core network device, a core network node, a core network functional unit, a mobility management entity MME, an access management function AMF, a session management function SMF, a serving gateway SGW, a PDN gateway PGW, and a user plane.
  • Function UPF Function
  • the terminal generates a PDU session recovery requirement
  • the terminal sends the PDU session information requested to be restored;
  • the terminal sends the PDU session information requesting recovery to the first network unit.
  • the terminal receives the PDU session information that confirms the restoration
  • the terminal performs a PDU recovery operation according to the PDU session information confirmed to be restored.
  • the terminal also sends PDU session information requesting recovery before receiving the confirmed PDU session information.
  • Some embodiments of the present disclosure by cooperation of the terminal, the first network unit, and the second network unit, can suspend the PDU session as needed when the connection is restored, save resources of the radio access network, and reduce signaling overhead. .
  • the radio frequency unit 101 may be configured to receive and transmit signals during or after receiving or transmitting information, and specifically, after receiving downlink data from the base station, processing the processor 1010; Send the uplink data to the base station.
  • radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio unit 101 can also communicate with the network and other devices through a wireless communication system.
  • the terminal provides the user with wireless broadband Internet access through the network module 102, such as helping the user to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 103 can convert the audio data received by the radio frequency unit 101 or the network module 102 or stored in the memory 109 into an audio signal and output as sound. Moreover, the audio output unit 103 can also provide audio output (eg, call signal reception sound, message reception sound, etc.) related to a specific function performed by the terminal 100.
  • the audio output unit 103 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 104 is for receiving an audio or video signal.
  • the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042 that images an still picture or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode.
  • the data is processed.
  • the processed image frame can be displayed on the display unit 106.
  • the image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio unit 101 or the network module 102.
  • the microphone 1042 can receive sound and can process such sound as audio data.
  • the processed audio data can be converted to a format output that can be transmitted to the mobile communication base station via the radio unit 101 in the case of a telephone call mode.
  • Terminal 100 also includes at least one type of sensor 105, such as a light sensor, motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can close the display panel 1061 and/or when the terminal 100 moves to the ear. Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity.
  • sensor 105 may also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be described here.
  • the display unit 106 is for displaying information input by the user or information provided to the user.
  • the display unit 106 can include a display panel 1061.
  • the display panel 1061 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • the user input unit 107 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal.
  • the user input unit 107 includes a touch panel 1071 and other input devices 1072.
  • the touch panel 1071 also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 1071 or near the touch panel 1071. operating).
  • the touch panel 1071 may include two parts of a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 1010 receives the commands from the processor 1010 and executes them.
  • the touch panel 1071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the user input unit 107 may also include other input devices 1072.
  • the other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which are not described herein.
  • the touch panel 1071 can be overlaid on the display panel 1061. After the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits to the processor 1010 to determine the type of the touch event, and then the processor 1010 according to the touch. The type of event provides a corresponding visual output on display panel 1061.
  • the touch panel 1071 and the display panel 1061 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated. The input and output functions of the terminal are implemented, and are not limited herein.
  • the interface unit 108 is an interface in which an external device is connected to the terminal 100.
  • the external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, and an audio input/output. (I/O) port, video I/O port, headphone port, and more.
  • the interface unit 108 can be configured to receive input from an external device (eg, data information, power, etc.) and transmit the received input to one or more components within the terminal 100 or can be used at the terminal 100 and external devices Transfer data between.
  • Memory 109 can be used to store software programs as well as various data.
  • the memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.).
  • the memory 109 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
  • the processor 1010 is a control center of the terminal, which connects various parts of the entire terminal using various interfaces and lines, and executes by executing or executing software programs and/or modules stored in the memory 109, and calling data stored in the memory 109.
  • the processor 1010 may include one or more processing units; optionally, the processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application, etc., and a modulation solution
  • the processor mainly handles wireless communication. It will be appreciated that the above described modem processor may also not be integrated into the processor 1010.
  • the terminal 100 may further include a power source 1011 (such as a battery) for supplying power to various components.
  • a power source 1011 such as a battery
  • the power source 1011 may be logically connected to the processor 1010 through a power management system to manage charging, discharging, and power management through the power management system. And other functions.
  • the terminal 100 includes some functional modules not shown, and details are not described herein again.
  • some embodiments of the present disclosure further provide a terminal, including a processor 1010, a memory 109, a computer program stored on the memory 109 and executable on the processor 1010, when the computer program is executed by the processor 1010.
  • the terminal may be a wireless terminal or a wired terminal, and the wireless terminal may be a device that provides voice and/or other service data connectivity to the user, a handheld device with a wireless connection function, or other processing device connected to the wireless modem. .
  • the wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a mobile terminal.
  • RAN Radio Access Network
  • the computer for example, can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with the wireless access network.
  • PCS Personal Communication Service
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal digital assistant
  • the wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal.
  • the access terminal, the user terminal (User Terminal), the user agent (User Agent), and the user device (User Device or User Equipment) are not limited herein.
  • Some embodiments of the present disclosure also provide a computer readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement various processes of the foregoing session control method embodiment, and achieving the same The technical effect, in order to avoid duplication, will not be repeated here.
  • the computer readable storage medium of the present disclosure may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memory. Such as read-only memory (Read-Only Memory, ROM for short), Random Access Memory (RAM), disk or optical disk.
  • the foregoing describes different processing manners of the session control method of some embodiments of the present disclosure from the first network unit, the second network unit, and the terminal, respectively.
  • the following disclosure uses the PDU session recovery operation as an example to control the session in different scenarios. Do further explanation.
  • the network architecture of some embodiments of the present disclosure includes: a terminal, a first network unit (taking a radio access network as an example), and a second network unit (taking a core network as an example), where the core network includes Access management function AMF, session management function SMF and user plane function.
  • the radio access network receives the PDU session information that is requested by the UE to be restored, and recovers according to the PDU session that the UE requests to recover, wherein the radio access network restores all PDU sessions of the UE in the case of the PDU session requested by the UE, and thereafter,
  • the radio access network sends the PDU session information requested by the UE to the core network.
  • the UE sends the PDU session information that is requested to be restored to the radio access network, and the radio access network may recover the PDU session that is requested by the UE, and notify the core network to recover the PDU session as a result of the PDU session recovery.
  • the core network receives the result of the PDU session recovery sent by the radio access network to recover the PDU session, and notifies the radio access network of the result of the recovery of the core network PDU session.
  • the UE performs PDU session recovery according to the PDU session confirmed by the radio access network.
  • the example is a recovery operation
  • the PDU session recovery sequence is that the radio access network and the UE recover first, and the core network side further restores the PDU session according to the PDU session recovery result of the UE and the radio access network.
  • the advantage is that the UE can send uplink data after the PDU session of the UE and the radio access network side is restored.
  • the radio access network performs PDU session recovery based on the PDU session information requested by the UE. As shown in FIG. 12, the example specifically includes the following steps:
  • Step 121 The UE sends an RRC recovery request to the radio access network.
  • the RRC restoration request corresponds to the above operation request information.
  • at least one of the following may be indicated in the operation request information: information of the PDU session requesting the restoration.
  • the radio access network may continue to hang or release.
  • the radio access network may perform a PDU session recovery operation according to the request of the UE, including at least one of the following:
  • not all PDU sessions requested by the UE can be allocated radio resources due to radio resource shortages. Therefore, the radio access network can transmit information confirming the recovered PDU session to the UE.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 122 The radio access network sends an RRC recovery to the UE, where the RRC recovery carries the PDU session recovery result information.
  • the RRC recovery indication is at least one of the following: confirming the restored PDU session information, and confirming the unrecoverable PDU session. information.
  • the UE performs PDU session recovery according to the indicated "confirmed restored PDU session information and/or acknowledgment of unrecoverable PDU session information".
  • Step 123 The UE sends an RRC recovery completion to the radio access network.
  • RRC recovery completion at least one of the following may be indicated in the RRC recovery completion: the UE recovers the information of the successful PDU session, and the UE side recovers the information of the failed PDU session.
  • the UE side may not be able to recover the PDU session for unpredictable reasons.
  • the PDU session recovery result information of the UE is required to return to the UE to confirm the recovery result of the PDU session on the UE.
  • Step 124 The radio access network sends a recovery request to the access mobility management function.
  • the PDU session recovery result information of the radio access network is carried in the recovery request, and the information may be at least one of the following: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered successful PDU session information indicates that the radio access network confirms the information of the PDU session recovered on the UE and the radio access network according to the UE request.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 125 The access mobility management function sends a recovery request to the session management function of the PDU session of the UE.
  • At least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered successful PDU session information indicates that the radio access network confirms the information of the PDU session recovered on the UE and the radio access network according to the UE request.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • the session management function may perform at least one of: restoring the PDU session context of the UE, and transmitting the downlink transmission address of the PDU session of the UE (ie, the transmission of the radio access network to the PDU session of the UE) The address) sends the user plane function, activates the PDU session of the UE to the user plane function, and sets the PDU session state of the UE to be activated.
  • the session management function may perform at least one of the following: continue to suspend the PDU session of the UE, delete the PDU session of the UE, request the user plane function to delete UE's PDU session.
  • continuing to suspend or delete a PDU session of a UE that failed to recover depends on the reason for the failure to recover. For example, the recovery failure caused by insufficient resources on the radio access network side can continue to hang. For example, if the PDU session requesting recovery is an unknown PDU session description information is inconsistent, it should be deleted.
  • the session management function may perform at least one of the following: continue to suspend the PDU session of the UE.
  • the session management function may perform at least one of the following: deleting the PDU session of the UE, requesting the user plane function to delete the PDU session of the UE.
  • Step 126 The session management function sends a recovery response to the access mobility management function, where the recovery response corresponds to the PDU session recovery result information of the second network element.
  • the recovery response corresponds to the PDU session recovery result information of the second network element.
  • at least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered PDU session information indicates that the session management function restores the information of the successful PDU session on the core network side.
  • Step 127 The access mobility management function sends a recovery response to the radio access network, corresponding to the PDU session recovery result information of the second network unit.
  • the access mobility management function sends a recovery response to the radio access network, corresponding to the PDU session recovery result information of the second network unit.
  • at least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered PDU session information indicates that the session management function restores the information of the successful PDU session on the core network side.
  • the radio access network may perform one of the following: suspending the PDU session context, suspending the context of the mapped radio bearer of the PDU session, releasing the bearer resources, and saving the uplink transport address of the PDU session ( That is, the user plane function allocates the transmission address of the UE's PDU session, sets the UE's PDU session state to suspend, requests the UE to suspend the PDU session, deletes the PDU session context, and requests the UE to delete the PDU session.
  • This example is a recovery operation.
  • the recovery sequence is that the radio access network side restores the PDU session with the UE first; the core network side restores the PDU session according to the PDU session recovery result of the UE and the radio access side.
  • the advantage is that the UE can send uplink data after completing the PDU session recovery between the UE and the radio access network.
  • the network recovers according to the PDU session information requested by the UE and the PDU session information requested by the second network element, such as PDU session information with data transmission requirements.
  • the example specifically includes the following steps:
  • Step 131 The UE sends an RRC recovery request to the radio access network.
  • at least one of the following may be indicated in the request: information requesting the restored PDU session.
  • the radio access network may continue to hang or release.
  • the radio access network may perform a PDU session recovery operation according to the request of the UE, including at least one of the following:
  • not all PDU sessions requested by the UE can be allocated radio resources due to radio resource shortages. Therefore, the radio access network needs to be able to send information confirming the recovered PDU session to the UE.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 132 The radio access network sends an RRC recovery to the UE.
  • the RRC recovery indicates at least one of the following: confirming the information of the restored PDU session, and confirming the information of the PDU session that cannot be recovered.
  • the UE performs PDU session recovery according to the indicated "confirming the information of the restored PDU session and/or confirming the information of the PDU session that cannot be recovered.”
  • Step 133 The UE sends an RRC recovery completion to the radio access network.
  • RRC recovery completion at least one of the following may be indicated in the RRC recovery completion: the UE recovers the information of the successful PDU session, and the UE side recovers the information of the failed PDU session.
  • the UE side may not be able to recover the PDU session for unpredictable reasons.
  • the UE needs to return the PDU session recovery result of the UE.
  • Step 134 The radio access network sends a recovery request to the access mobility management function.
  • At least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered successful PDU session information indicates that the radio access network confirms the information of the PDU session recovered on the UE and the radio access network according to the UE request.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 135 The access mobility management function sends a recovery request to the session management function of the PDU session of the UE.
  • At least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered successful PDU session information indicates that the radio access network confirms the information of the PDU session recovered on the UE and the radio access network according to the UE request.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • the session management function may perform at least one of: restoring the PDU session context of the UE, and transmitting the downlink transmission address of the PDU session of the UE (ie, the transmission of the radio access network to the PDU session of the UE) The address) sends the user plane function, activates the PDU session of the UE to the user plane function, and sets the PDU session state of the UE to be activated.
  • the session management function may perform at least one of the following: continue to suspend the PDU session of the UE, delete the PDU session of the UE, request the user plane function to delete UE's PDU session.
  • continuing to suspend or delete a PDU session of a UE that failed to recover depends on the reason for the failure to recover. For example, the recovery failure caused by insufficient resources on the radio access network side can continue to hang. For example, if the PDU session requesting recovery is an unknown PDU session description information is inconsistent, it should be deleted.
  • the session management function may perform at least one of the following: continue to suspend the PDU session of the UE.
  • the session management function may perform at least one of the following: deleting the PDU session of the UE, requesting the user plane function to delete the PDU session of the UE.
  • the session management function may perform at least one of: restoring the PDU session of the UE, transmitting information about the PDU session for which the PDU session is required to be recovered.
  • Step 136 The session management function sends a recovery response to the access mobility management function.
  • at least one of the following may be indicated in the request: recovering information of a successful PDU session, recovering information of a failed PDU session, and information of a PDU session that the core network requests to recover.
  • the recovered PDU session information indicates that the session management function restores the information of the successful PDU session on the core network side.
  • the information of the PDU session that is required to be restored indicates that the session management function additionally requests information on the recovered PDU session.
  • Step 137 The access mobility management function sends a recovery response to the radio access network.
  • at least one of the following may be indicated in the request: information for recovering a successful PDU session, information for recovering a failed PDU session, and information for a PDU session that the core network requests to recover.
  • the recovered PDU session information indicates that the session management function restores the information of the successful PDU session on the core network side.
  • the radio access network may perform one of the following: suspending the PDU session context, suspending the context of the mapped radio bearer of the PDU session, releasing the bearer resources, and saving the uplink transport address of the PDU session ( That is, the user plane function allocates the transmission address of the UE's PDU session, sets the UE's PDU session state to suspend, requests the UE to suspend the PDU session, deletes the PDU session context, and requests the UE to delete the PDU session.
  • the radio access network may perform one of the following: restoring the PDU session of the UE, requesting the UE to resume the PDU session.
  • the UE may be requested by the RRC reconfiguration message containing the specified recovered PDU session.
  • the radio access network can perform one of the following:
  • the radio access network sends an RRC reconfiguration request message to the UE.
  • the message may include information about the PDU session that is required to be restored.
  • the UE performs recovery of the specified PDU session according to the received information of the PDU session that is required to be restored.
  • the UE returns an RRC reconfiguration message response message to the radio access network.
  • the UE recovers the information of the successful PDU session, and the UE side recovers the information of the failed PDU session.
  • the example is a recovery operation.
  • the PDU session recovery sequence is that the radio access network side restores the PDU session with the UE first, and the core network side performs the PDU according to the PDU session recovery result of the UE and the radio access network, and the PDU session information requested by the UE. Recovery of the session.
  • the advantage is that the UE can send uplink data after the PDU session of the UE and the radio access network side is restored.
  • the radio access network attempts to recover all pending PDU sessions of the UE, and preferentially restores the PDU session information requested by the UE when resources are insufficient.
  • the session management function network recovers according to the PDU session information requested by the UE and the PDU session information with data transmission requirements.
  • the radio access network suspends/releases resources of the unnecessary PDU session according to the information of the PDU session that the session management function finally needs to recover.
  • the example specifically includes the following steps:
  • Step 141 The UE sends an RRC recovery request to the radio access network.
  • the UE may indicate at least one of the following in step 141 or step 143: the UE requests information of the restored PDU session.
  • the radio access network performs the PDU session recovery operation, and may include at least one of the following:
  • not all PDU sessions requested by the UE can be allocated radio resources due to radio resource shortages.
  • the radio access network may preferentially restore the PDU session that the UE requests to activate.
  • the radio access network may transmit information confirming the recovered PDU session to the UE.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 142 The radio access network sends an RRC recovery to the UE.
  • the RRC recovery indicates at least one of the following: confirming the information of the restored PDU session.
  • confirming that the recovered PDU session information may be a PDU session in which the wireless access side recovers successfully.
  • the UE performs PDU session recovery according to the indicated "confirm information of the recovered PDU session".
  • Step 143 The UE sends an RRC recovery completion to the radio access network.
  • the RRC session recovery result information of the UE may be indicated in the RRC recovery completion, including at least one of the following: information that the UE recovers the successful PDU session, and information that the UE side recovers the failed PDU session.
  • some PDU sessions may fail to recover on the UE side due to unpredictable reasons.
  • the radio access network may perform one of the following: release/suspend the PDU session, request the core network to release/suspend the PDU session.
  • Step 144 The radio access network sends a recovery request to the access mobility management function.
  • the request carries the PDU session recovery result information of the radio access network and the PDU session information that the terminal requests to recover, and may specifically indicate at least one of the following: recovering information of a successful PDU session, and recovering the failed PDU session.
  • Information information of the PDU session that the UE requests to recover.
  • the recovered successful PDU session information indicates that the radio access network confirms the information of the PDU session recovered on the UE and the radio access network according to the UE request.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 145 The access mobility management function sends a recovery request to the session management function of the PDU session of the UE.
  • At least one of the following may be indicated in the request: recovering information of a successful PDU session, recovering information of the failed PDU session, and information of the PDU session requested by the UE.
  • the recovered PDU session information may be information of a PDU session in which both the radio access network and the UE side recover successfully.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • the session management function may perform at least one of the following: restore the PDU session context of the UE, and send the user plane function to the downlink transmission address of the PDU session of the UE, that is, the transmission address allocated by the radio access network to the PDU session of the UE.
  • the user plane function activates the PDU session of the UE and sets the PDU session state of the UE to active.
  • a PDU session with downstream data transfer requirements is not necessarily in the PDU session in which the UE requests activation.
  • the session management function may perform at least one of the following: continue to suspend the PDU session of the UE, delete the PDU session of the UE, request the user plane function to delete UE's PDU session.
  • continuing to suspend or delete a PDU session of a UE that failed to recover depends on the reason for the failure to recover. For example, the recovery failure caused by insufficient resources on the radio access network side can continue to hang. For example, if the PDU session requesting recovery is an unknown PDU session description information is inconsistent, it should be deleted.
  • the session management function may perform at least one of: suspending/releasing the PDU session, requesting user plane management function, for the PDU session that the radio access network side recovers successfully but is neither the UE requests the activated PDU session nor the downlink data transmission requirement. Suspend/release the PDU session, request the radio access network to suspend/release the PDU session, and request the UE to suspend/release the PDU session.
  • the session management function may perform at least one of the following: continue to suspend the PDU session.
  • the session management function may perform at least one of the following: release the PDU session, requesting the user plane function to release the PDU session.
  • Step 146 The session management function sends a recovery response to the access mobility management function.
  • at least one of the following may be indicated in the request: information of recovering a successful PDU session, information of recovering a failed PDU session, information of a PDU session requiring release/suspension.
  • the recovered PDU session information may indicate that the core network side recovers the information of the successful PDU session.
  • the information requesting the released/suspended PDU session indicates information of the PDU session that the session management function requires to release/restore.
  • Step 147 The access mobility management function sends a recovery response to the radio access network.
  • at least one of the following may be indicated in the request: information of recovering a successful PDU session, information of recovering a failed PDU session, information of a PDU session requiring release/suspension.
  • the recovered PDU session information may indicate that the core network side recovers the information of the successful PDU session.
  • the radio access network may perform one of the following: suspending the PDU session context, suspending the context of the mapped radio bearer of the PDU session, releasing the bearer resources, and saving the uplink transport address of the PDU session ( That is, the user plane function allocates the transmission address of the UE's PDU session, sets the UE's PDU session state to suspend, requests the UE to suspend the PDU session, deletes the PDU session context, and requests the UE to delete the PDU session.
  • the radio access network may perform one of the following:
  • the radio access network sends an RRC reconfiguration message to the UE.
  • the message includes information about the PDU session that is required to be released/suspended.
  • the UE performs suspension/release of the specified PDU session according to the received information of the PDU session requested to be released/suspended.
  • the UE sends the PDU session information requested to be restored to the radio access network
  • the radio access network sends the PDU session information requested by the UE to the core network
  • the PDU session information requested by the core network and the PDU session information requested by the core network itself is sent by the core network.
  • the radio access network then performs the PDU session according to the recovery result of the PDU session requested by the UE according to the core network. restore.
  • the example specifically includes the following steps:
  • Step 151 The UE sends an RRC recovery request to the radio access network.
  • at least one of the following may be indicated in the request: information that the UE requests the restored PDU session.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 152 The radio access network sends a recovery request to the access mobility management function.
  • At least one of the following may be indicated in the request: information that the UE requests the restored PDU session.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • Step 153 The access mobility management function sends a recovery request to the session management function of the PDU session of the UE.
  • At least one of the following may be indicated in the request: information that the UE requests the restored PDU session.
  • At least one of the following may be indicated in the request: requesting the suspended PDU session information, and requesting the released PDU session information.
  • the session management function can continue to hang or release.
  • the session management function may perform at least one of: restoring the PDU session context of the UE, the PDU of the UE.
  • the downlink transmission address of the session (that is, the transmission address allocated by the radio access network for the PDU session of the UE) transmits the user plane function, activates the PDU session of the UE to the user plane function, and sets the PDU session state of the UE to be activated.
  • the PDU session required by the downlink data transmission is not necessarily in the PDU session in which the UE requests activation.
  • the session management function may perform at least one of the following: continue to suspend the PDU session of the UE.
  • the session management function may perform at least one of the following: deleting the PDU session of the UE, requesting the user plane function to delete the PDU session of the UE.
  • Step 154 The session management function sends a recovery response to the access mobility management function.
  • at least one of the following may be indicated in the request: information of recovering a successful PDU session, information of recovering a failed PDU session, information of a PDU session requiring release/suspension.
  • the recovered PDU session information indicates that the session management function restores the information of the successful PDU session on the core network side.
  • the information requesting the released/suspended PDU session indicates information of the PDU session that the session management function requires to release/restore.
  • Step 155 The access mobility management function sends a recovery response to the radio access network.
  • at least one of the following may be indicated in the request: information of recovering a successful PDU session, information of recovering a failed PDU session, information of a PDU session requiring release/suspension.
  • the recovered PDU session information indicates that the session management function restores the information of the successful PDU session on the core network side.
  • the radio access network For the PDU session indicating successful recovery, the radio access network performs a PDU session recovery operation, which may include at least one of the following:
  • the radio access network may perform one of the following: suspending the PDU session context, suspending the context of the mapped radio bearer of the PDU session, releasing the bearer resources, and saving the uplink transport address of the PDU session ( That is, the user plane function allocates the transmission address of the UE's PDU session, sets the UE's PDU session state to suspend, requests the UE to suspend the PDU session, deletes the PDU session context, and requests the UE to delete the PDU session.
  • the radio access network may perform one of the following: suspending/releasing the context of the specified PDU session, suspending the radio bearer context mapped by the PDU session of the UE, and releasing the designated PDU. Session allocation or mapping of radio bearers, sending information to the UE requesting release/suspend PDU sessions
  • not all PDU sessions requested by the UE can be allocated radio resources due to radio resource shortages.
  • the radio access network performs at least one of the following: requesting the core network (such as access mobility management function, session management function, user plane function, etc.) to release/suspend PDU session where the core network recovers successfully but the radio access network fails to recover.
  • Step 156 The radio access network sends an RRC recovery to the UE.
  • the RRC recovery indicates at least one of the following: confirming the information of the restored PDU session.
  • the information confirming the recovered PDU session includes a PDU session that is a PDU session in which both the core network recovery and the radio access network are successfully restored.
  • the UE performs PDU session recovery according to the indicated "confirm information of the recovered PDU session".
  • Step 157 The UE sends an RRC recovery completion to the radio access network.
  • RRC recovery completion at least one of the following may be indicated in the RRC recovery completion: the UE recovers the information of the successful PDU session, and the UE side recovers the information of the failed PDU session.
  • some PDU sessions may fail to recover on the UE side due to unpredictable reasons.
  • the radio access network may perform one of the following: release/suspend the PDU session, request the core network to release/suspend the PDU session.
  • the example is a recovery operation, and the order of PDU recovery is still that the radio access network side and the UE first recover the PDU session, and the core network side further restores the PDU session according to the PDU session recovery result of the UE and the radio access network, and the advantage is that the completion is completed.
  • the UE can send uplink data.
  • the radio access network attempts to recover all PDU sessions suspended by the UE. As shown in FIG. 16, the example specifically includes the following steps:
  • Step 161 The UE sends an RRC recovery request to the radio access network.
  • the radio access network performs a PDU session recovery operation, and may include at least one of the following:
  • not all PDU sessions requested by the UE can be allocated radio resources due to radio resource shortages.
  • the radio access network may preferentially restore the PDU session that the UE requests to activate.
  • the radio access network may transmit information confirming the recovered PDU session to the UE.
  • Step 162 The radio access network sends an RRC recovery to the UE.
  • the RRC recovery indication is at least one of the following: confirming the information of the restored PDU session.
  • confirming that the recovered PDU session information may be a PDU session in which the wireless access side recovers successfully.
  • the UE performs PDU session recovery according to the indicated "confirm information of the recovered PDU session".
  • Step 163 The UE sends an RRC recovery completion to the radio access network.
  • RRC recovery completion at least one of the following may be indicated in the RRC recovery completion: the UE recovers the information of the successful PDU session, and the UE side recovers the information of the failed PDU session.
  • some PDU sessions may fail to recover on the UE side due to unpredictable reasons.
  • the radio access network may perform one of the following: release/suspend the PDU session, request the core network to release/suspend the PDU session.
  • Step 164 The radio access network sends a recovery request to the access mobility management function.
  • At least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered successful PDU session information indicates that the radio access network confirms the information of the PDU session recovered on the UE and the radio access network according to the UE request.
  • Step 165 The access mobility management function sends a recovery request to the session management function of the PDU session of the UE.
  • At least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the session management function may perform at least one of the following: restoring the PDU session context of the UE, and downlink the transmission address of the PDU session of the UE (ie, the radio access network is the PDU session of the UE)
  • the assigned transport address sends a user plane function, activates the UE's PDU session to the user plane function, and sets the UE's PDU session state to active.
  • a PDU session with downstream data transfer requirements is not necessarily in the PDU session in which the UE requests activation.
  • the session management function may perform at least one of the following: continue to suspend the PDU session of the UE, delete the PDU session of the UE, and request the user plane function to delete the PDU session of the UE.
  • continuing to suspend or delete a PDU session of a UE that failed to recover depends on the reason for the failure to recover. For example, the recovery failure caused by insufficient resources on the radio access network side can continue to hang. For example, if the PDU session requesting recovery is an unknown PDU session description information is inconsistent, it should be deleted.
  • Step 166 The session management function sends a recovery response to the access mobility management function.
  • at least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered PDU session information may indicate that the core network side recovers the information of the successful PDU session.
  • Step 167 The access mobility management function sends a recovery response to the radio access network.
  • at least one of the following may be indicated in the request: recovering information of a successful PDU session, and recovering information of the failed PDU session.
  • the recovered PDU session information may indicate that the core network side recovers the information of the successful PDU session.
  • the radio access network may perform one of the following: suspending the PDU session context, suspending the context of the mapped radio bearer of the PDU session, releasing the bearer resources, and saving the uplink transport address of the PDU session ( That is, the user plane function allocates the transmission address of the UE's PDU session, sets the UE's PDU session state to suspend, requests the UE to suspend the PDU session, deletes the PDU session context, and requests the UE to delete the PDU session.
  • the radio access network sends an RRC reconfiguration message to the UE.
  • the message includes information about the PDU session that is required to be released/suspended.
  • the UE performs suspension/release of the specified PDU session according to the received information of the PDU session requested to be released/suspended.
  • mobility management and session management are further split and reorganized, and the mobility management function in the MME is attributed to the AMF.
  • the session management function in the MME is integrated with the session management function in the SGW and the PGW into an SMF, and the user plane functions in the SGW and the PGW are integrated into the AMF.
  • This example is the PDU session suspension process. As shown in Figure 17, the example includes the following steps:
  • Step 171 The radio access network decides to suspend the UE, and then sends a suspend request to the access mobility management function.
  • Step 172 The access mobility management function sends a suspension request to the session management function of the PDU session of the UE.
  • the session management functions of PDU sessions of different UEs may be different.
  • the session management function may perform at least one of the following: saving the PDU session context of the UE, saving the downlink transmission address of the PDU session of the UE (that is, the transmission address allocated by the radio access network for the PDU session of the UE), and sending the PDU session to the UPF to deactivate Set the PDU session state of the UE to hang.
  • Step 173 The session management function sends a suspension response to the access mobility management function.
  • the access mobility management function may perform one of the following: saving the mobile context of the UE, and storing UE session related information (PDU session identifier, PDU session state, address of session management function, slice information)
  • Step 174 The access mobility management function sends a suspension response to the radio access network.
  • the response may include at least one of the following: suspending information of the PDU session of the successful UE, and suspending information of the PDU session of the failed UE.
  • the access mobility management function can wait until the session management function of the PDU session of all UEs returns a suspend response and initiate a suspend response to the radio access network.
  • the radio access network may perform one of the following: suspending the PDU session context of the UE, suspending the mapping of the radio bearer of the PDU session of the UE, releasing the bearer resource, and saving the uplink transmission address of the PDU session of the UE (ie, the user plane function) The transmission address assigned to the PDU session of the UE), setting the PDU session state of the UE to suspend, suspending the connection between the radio access network and the core network control plane (AMF, MME, etc.) regarding the UE.
  • AMF core network control plane
  • the radio access network only performs a suspend operation on a PDU session that specifies a suspend success.
  • the radio access network releases the PDU session that failed to suspend.
  • Step 175 The radio access network sends an RRC suspension or RRC release message to the UE.
  • the message may include at least one of the following: information about the PDU session of the suspended UE, and information of the PDU session of the deleted UE.
  • the UE underlay may perform a suspend operation, including at least one of: suspending the PDU session context of the UE, suspending the context of the mapped radio bearer of the PDU session of the UE, releasing the bearer resource, and releasing the PDU of the UE
  • the session state is set to suspend, and the UE upper layer (or the NAS layer) is notified to suspend the PDU session context of the UE, suspend the connection between the radio access network and the core network control plane (AMF, MME, etc.) regarding the UE.
  • AMF radio access network
  • MME core network control plane
  • the radio access network performs a suspend operation only on the specified suspended PDU session.
  • the radio access network releases the PDU session designated for deletion.
  • the core network side may receive downlink data notification about the terminal individual PDU session. For these sessions, recovery is required to transfer data to the terminal. However, there is no such information in the paging message. Then, in the terminal service request, if there is no PDU session with the downlink data transmission requirement, the activated PDU session requested by the terminal is less than the part of the PDU session. Similarly, if the terminal adopting the user plane CIOT, if it is in the idle state, there is no information of the PDU session required for the downlink data transmission in the paging message, and the UE may also lack this part of the PDU session if it requests to restore the PDU session as needed.
  • This example is a paging operation/notification operation, which is applicable to a scenario in which PDU session processing is performed based on a PDU session that the core network requests to recover. As shown in Figure 18, the example includes the following steps:
  • Step 181 When the user plane function of the core network needs to transmit downlink data, determine the PDU session information requested to be restored, and the user plane function of the core network sends a downlink data notification to the SMF.
  • Step 182 The SMF sends the downlink data notification to the AMF.
  • Step 183a The AMF sends a paging message or a notification message to the radio access network, where the paging message carries the PDU session information that the core network requests to recover.
  • Step 184 The radio access network forwards the paging message to the terminal.
  • Step 183b The AMF notifies the UE of the message.
  • the notification message may carry the PDU session information that the core network requests to recover.
  • the notification message of the PDU session information that is requested to be restored by the back core network is sent to the UE through the 3GPP access network.
  • Step 185a After receiving the paging message, the terminal starts a PDU session recovery process, and sends a service request message to the core network.
  • the message may carry the PDU session information that the core network requests to recover.
  • step 185b After receiving the paging message, the terminal starts a PDU session recovery process, and sends an RRC recovery request message to the radio access network.
  • the message may carry the PDU session information that the core network requests to recover.
  • the acquisitions involved in some embodiments of the present disclosure may be received, configured, or known by themselves.
  • the PDU session required for data transmission may be a PDU session with downstream data transmission requirements, a PDU session with downlink data notification, and the like.
  • a PDU session with data transmission requirements is not necessarily included in the PDU session information requesting recovery. Because the UE does not know that the network device has a PDU session for downlink data transmission when transmitting the information of the PDU session requesting recovery.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division.
  • multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the present disclosure.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the objects of the present disclosure can also be achieved by running a program or a set of programs on any computing device.
  • the computing device can be a well-known general purpose device.
  • the objects of the present disclosure may also be realized by merely providing a program product including program code for implementing a method or apparatus. That is to say, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure.
  • the storage medium may be any known storage medium or any storage medium developed in the future.
  • various components or steps may be decomposed and/or recombined.

Landscapes

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

Abstract

本公开公开了一种会话控制方法、网络设备及终端。该会话控制方法方法包括：获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，进行PDU会话处理。

Description

会话控制方法、网络设备及终端
相关申请的交叉引用
本申请主张在2018年1月4日在中国提交的中国专利申请号No.201810009027.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种会话控制方法、网络设备及终端。
背景技术
蜂窝物联(Cellular Internet of Things，CIOT)是一种数据传送的优化方法，包括控制面板CIOT和用户面CIOT。其中，用户面CIOT是指在终端(User Equipment，UE)需要被释放或者不活跃时，可以通过挂起终端与网络连接方式，在无线接入网保持终端的上下文。当终端需要恢复与网络的连接时，不需要重新在无线接入网建立终端的上下文。终端也可以不需要向核心网发送服务请求，从而达到节省连接建立的信令和减少时延的效果。其中，终端与网络连接连接可以是指终端与接入网之间的无线资源控制(Radio Resource Control，RRC)连接，接入网与核心网之间关于终端的连接。
对采用了用户面CIOT的终端，在连接恢复时可节省服务请求过程中连接建立的信令和减少时延，但对于被挂起的PDU会话，特别是无线接入网(Radio Access Network，RAN)侧被挂起的PDU会话，就不能够根据终端的意愿来决定是否恢复，是否恢复无线承载。若默认恢复所有的PDU会话，恢复对于终端不想恢复的PDU会话则浪费了建立无线承载的无线资源。
发明内容
本公开的一些实施例提供了一种会话控制方法、网络设备及终端，以解决5G系统中PDU会话恢复过程中信令复杂、无限资源利用率低的问题。
第一方面，本公开的一些实施例提供了一种会话控制方法，应用于第一 网络单元侧，包括：
获取分组数据单元PDU会话信息的操作请求信息；操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息和终端请求挂起的PDU会话信息；
根据操作请求信息，进行PDU会话处理。
第二方面，本公开的一些实施例还提供了一种网络设备，应用于第一网络单元侧，包括：
第一获取模块，用于获取分组数据单元PDU会话信息的操作请求信息；操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息和终端请求挂起的PDU会话信息；
第一处理模块，用于根据操作请求信息，进行PDU会话处理。
第三方面，本公开的一些实施例提供了一种会话控制方法，应用于第一网络单元侧，包括：
获取分组数据单元PDU会话信息的操作请求信息；操作请求信息包括以下信息中的至少一项：第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息和第二网络单元请求挂起的PDU会话信息；
根据操作请求信息，进行PDU会话处理。
第四方面，本公开的一些实施例还提供了一种网络设备，应用于第一网络单元侧，包括：
第二获取模块，用于获取分组数据单元PDU会话信息的操作请求信息；操作请求信息包括以下信息中的至少一项：第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息和第二网络单元请求挂起的PDU会话信息；
第二处理模块，用于根据操作请求信息，进行PDU会话处理。
第五方面，本公开的一些实施例提供了一种会话控制方法，应用于第二网络单元侧，包括：
获取分组数据单元PDU会话信息的操作请求信息；操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复 结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息；
根据操作请求信息，进行PDU会话处理。
第六方面，本公开的一些实施例提供了一种网络设备，应用于第二网络单元侧，包括：
第三获取模块，用于获取分组数据单元PDU会话信息的操作请求信息；操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息；
第三处理模块，用于根据操作请求信息，进行PDU会话处理。
第七方面，本公开的一些实施例提供了一种会话控制方法，应用于终端侧，包括：
向第一网络单元发送分组数据单元PDU会话信息的操作请求信息；
接收所述第一网络单元根据操作请求信息发送的PDU会话操作响应信息；
根据PDU会话操作响应信息，进行PDU会话处理。
第八方面，本公开的一些实施例还提供了一种终端，包括：
第三发送模块，用于向第一网络单元发送分组数据单元PDU会话信息的操作请求信息；
第二接收模块，用于接收所述第一网络单元根据操作请求信息发送的PDU会话操作响应信息；
第四处理模块，用于根据PDU会话操作响应信息，对PDU会话进行处理。
第九方面，本公开的一些实施例提供了一种网络设备，网络设备包括处理器、存储器以及存储于存储器上并可在处理器上运行的计算机程序，处理 器执行计算机程序时实现上述的会话控制方法的步骤。
第十方面，本公开的一些实施例提供了一种终端，终端包括处理器、存储器以及存储于存储器上并可在处理器上运行的计算机程序，计算机程序被处理器执行时实现上述的会话控制方法的步骤。
第十一方面，本公开的一些实施例提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，计算机程序被处理器执行时实现上述的会话控制方法的步骤。
这样，本公开的一些实施例的会话控制方法、网络设备及终端，获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，进行PDU会话处理。其中，操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢复，从而节省无线接入网的资源，减少信令开销。
附图说明
为了更清楚地说明本公开的一些实施例的技术方案，下面将对本公开的一些实施例的描述中所需要使用的附图作简单地介绍。显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1表示本公开的一些实施例的应用于第一网络单元的会话控制方法的流程示意图之一；
图2表示本公开的一些实施例的第一网络单元的网络设备的模块结构示意图之一；
图3表示本公开的一些实施例的应用于第一网络单元的会话控制方法的流程示意图之二；
图4表示本公开的一些实施例的第一网络单元的网络设备的模块结构示 意图之二；
图5表示本公开的一些实施例的应用于第二网络单元的会话控制方法的流程示意图；
图6表示本公开的一些实施例的第二网络单元的网络设备的模块结构示意图；
图7表示本公开的一些实施例的网络设备的结构框图；
图8表示本公开的一些实施例的应用于终端的会话控制方法的流程示意图；
图9表示本公开的一些实施例的终端的模块结构示意图；
图10表示本公开的一些实施例的终端的结构框图；
图11表示本公开的一些实施例的网络架构示意图；
图12表示本公开的会话控制方法的第一示例的流程示意图；
图13表示本公开的会话控制方法的第二示例的流程示意图；
图14表示本公开的会话控制方法的第三示例的流程示意图；
图15表示本公开的会话控制方法的第四示例的流程示意图；
图16表示本公开的会话控制方法的第五示例的流程示意图；
图17表示本公开的会话控制方法的第六示例的流程示意图；以及
图18表示本公开的会话控制方法的第七示例的流程示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
本公开的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本公开的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或 单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本公开的一些实施例提供了一种会话控制方法，应用于第一网络单元侧，第一网络单元包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元(Centralized Unit，CU)、分布式单元(Distributed Unit，DU)、基站、eNB、gNB、非3GPP互操作功能(Non-3GPP InterWorking Function，N3IWF)、接入控制(Access Controller，AC)节点、接入点(Access Point，AP)设备或无线局域网(Wireless Local Area Networks，WLAN)节点；第二网络单元包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体(Mobility Management Entity，MME)、接入管理功能(Access Management Function，AMF)、会话管理功能(Session Management Function，SMF)、SGW、PGW、用户平面功能UPF。其中，本公开的一些实施例仅以第一网络单元为无线接入网，第二网络单元为核心网为例进行说明。
值得指出的是，在5G移动通信系统中，用户面CIOT可能会被命名为其他名称，但不影响本公开。
在本公开的一些实施例中，挂起/释放表示挂起和/或释放，恢复PDU会话还可以体现为激活PDU会话。
如图1所示，本公开的一些实施例的会话控制方法具体包括以下步骤11-12。
步骤11：获取分组数据单元PDU会话信息的操作请求信息。
其中，操作请求信息可以包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息和终端请求挂起的PDU会话信息。
其中，PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
可选的，在PDU会话比特地图中的比特位置代表PDU会话标识(比如第N比特代表的PDU会话标识是N)。第N比特位置可以指示是否操作(比 如请求恢复、请求释放、请求挂起、挂起成功)PDU会话标识为N的PDU会话。比如第N比特指示为1，可以指示对相应的PDU会话执行以下会话操作之一：请求激活、请求恢复、请求释放、请求挂起、确认恢复、恢复成功、释放成功、挂起成功。
比如第N比特指示为0，可以指示对相应的PDU会话执行以下会话操作之一：请求不激活、请求不恢复、请求不释放、请求不挂起、确认不能恢复、恢复失败、释放失败、挂起失败。不难理解、通过PDU会话比特地图可以节省需要传输的信息的字节。
-当请求恢复的PDU会话信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话请求会话。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求会话。
-当请求释放的PDU会话信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话请求释放。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求释放。
-当请求挂起的PDU会话信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话请求挂起。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求挂起。
-当确认恢复的PDU会话信息或确认不能恢复的PDU会话包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话确认恢复和/或哪些PDU会话确认不能恢复。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求确认恢复。比如可以通过将第N比特设置为0指示PDU会话标识为N的PDU会话请求确认不能恢复。
-当PDU会话恢复结果信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话恢复成功和/或哪些PDU会话确认恢复失败。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话恢复成功。比如可以通过将第N比特设置为0指示PDU会话标识为N的PDU会话恢复失败。
可选的，PDU会话标识信息可以包括QoS流标识信息PDU会话标识比特地图信息可以包括QoS流标识比特地图信息，QoS流信息可以包括QoS流 映射的无线承载信息。一般来说，一个PDU会话可以包含多个QoS流。只有存在至少一个QoS流请求恢复，其对应的PDU的PDU会话就需要请求恢复。
步骤12：根据操作请求信息，进行PDU会话处理。
一种实施方式中，步骤12可以包括以下(1)-(3)至少一项：
(1)当操作请求信息为终端请求恢复的PDU会话信息时，可以执行以下至少一项：对终端请求恢复的PDU会话进行恢复操作；对终端挂起的所有PDU会话进行恢复操作；对终端挂起的所有PDU会话进行恢复操作且在资源不足时，优先对终端请求恢复的PDU会话进行恢复操作。其中，这里所说的资源可以包括无线资源、第一网络单元内部的CPU、内存等各种资源。一种实施方式中，优先指的是，假设UE请求恢复的PDU会话为PDU会话1和PDU会话2，但终端挂起的PDU会话有PDU会话1、PDU会话2、PDU会话3、PDU会话4和PDU会话5。第一网络单元在资源充足是全部恢复，但在资源不足时，优先恢复PDU会话1和PDU会话2，若恢复完PDU会话1和PDU会话2后还有额外资源的话，可进一步恢复PDU会话3、PDU会话4等。
(2)当操作请求信息包含终端请求释放的PDU会话信息时，可以对终端请求释放的PDU会话进行释放操作。
(3)当操作请求信息包含终端请求挂起的PDU会话信息时，可以对终端请求挂起的PDU会话进行挂起操作。
其中，值得说明的是，对PDU会话进行恢复操作的步骤可以为：对PDU会话可以执行以下操作中的至少一项：恢复PDU会话的上下文；恢复PDU会话对应的无线承载；为PDU会话的QoS流分配和/或映射无线承载资源；恢复第一网络单元与第二网络单元之间关于终端的连接。
进一步地，步骤12还可以包括以下至少一项：向终端发送确认恢复和/或确认不能恢复的PDU会话信息；向第二网络单元发送第一网络单元的PDU会话恢复结果信息。也就是说，一、第一网络单元在对PDU会话进行处理的同时或之后，还可根据处理结果生成确认恢复和/或确认不能恢复的PDU会话信息并反馈至终端；二、第一网络单元在对PDU会话进行处理的同时或之 后，可以根据处理结果生成第一网络单元的PDU会话恢复结果并发送至第二网络单元。其中，本公开的一些实施例并不限定这两个步骤(上述一和二)之间先后关系，亦不限定处理过程与处理结果发送的先后关系，既可以边处理边发送，亦可以全部处理完后一并发送。
其中，第一网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息。
可选地，恢复成功的PDU会话信息可以用于指示终端和第一网络单元均恢复成功的PDU会话；
恢复失败的PDU会话信息可以用于指示终端或第一网络单元恢复失败的PDU会话；
请求释放的PDU会话信息可以用于指示终端恢复失败的PDU会话、第一网络单元恢复失败的PDU会话以及终端请求释放的PDU会话中的至少一项；
请求挂起的PDU会话信息可以用于指示终端恢复失败的PDU会话、第一网络单元恢复失败的PDU会话以及终端请求挂起的PDU会话中的至少一项；
确认恢复的PDU会话信息可以用于指示存在PDU会话上下文的PDU会话、能够分配或映射无线承载资源的PDU会话、第一网络单元和第二网络单元都确认能够恢复的PDU会话中的至少一项；
确认不能恢复的PDU会话可以包括：不存在PDU会话上下文的PDU会话、不能够分配或映射无线承载资源的PDU会话、第一网络单元确认不能恢复的PDU会话、第二网络单元确认不能恢复的PDU会话中的至少一项。
可选地，在向终端发送确认恢复和/或确认不能恢复的PDU会话信息的步骤之后，还可以包括：接收终端反馈的终端的PDU恢复结果信息。其中，终端的PDU恢复结果信息可以包括：终端恢复成功的PDU会话信息和终端恢复失败的PDU会话信息中的至少一项。
可选的，向第二网络单元发送第一网络单元的PDU会话恢复结果信息的步骤还可以包括：向第二网络单元发送携带有第一网络单元的PDU会话恢复 结果信息的会话操作请求；接收第二网络单元根据会话操作请求返回的第二网络单元的PDU会话恢复结果信息。
可选的，第二网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求恢复的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息。
具体地，恢复成功的PDU会话信息可以用于指示第一网络单元和第二网络单元均恢复成功的PDU会话；
恢复失败的PDU会话信息可以用于指示第二网络单元恢复失败的PDU会话；
第二网络单元请求恢复的PDU会话信息可以用于指示第一网络单元挂起的但第二网络单元请求恢复的PDU会话、第一网络单元没有恢复失败仍然挂起的但第二网络单元请求恢复的PDU会话中的至少一项；
第二网络单元请求释放的PDU会话信息可以用于指示第二网络单元恢复失败的PDU会话、第一网络单元恢复成功但第二网络单元请求释放的PDU会话中的至少一项；
第二网络单元请求挂起的PDU会话信息可以用于指示终端恢复失败的PDU会话、第一网络单元恢复成功但第二网络单元请求释放的PDU会话中的至少一项。
其中，接收第二网络单元根据会话操作请求返回的第二网络单元的PDU会话恢复结果信息的步骤之后还可以包括：根据第二网络单元的PDU会话恢复结果信息，对终端的PDU会话进行处理。一个例子是：第一网络单元恢复终端的PDU会话1和2，但是第二网络单元对PDU会话1恢复成功，对PDU会话2恢复失败。此时，不难理解，对恢复失败的PDU会话2，第二网络单元可以指示PDU会话2恢复失败、请求释放PDU会话2或者请求挂起PDU会话2。
可选的，根据第二网络单元的PDU会话恢复结果信息，对终端的PDU会话进行处理的步骤的具体内容，如下，此处不再赘述。
在另一种实施方式中，步骤12可以包括：当操作请求信息包括终端请求恢复的PDU会话信息时，可以执行：向第二网络单元发送终端请求恢复的 PDU会话信息。
其中，向第二网络单元发送终端请求恢复的PDU会话信息的步骤之后，还可以包括：接收第二网络单元根据终端请求恢复的PDU会话信息反馈的第二网络单元的PDU会话恢复结果信息；根据第二网络单元的PDU会话恢复结果信息，可以对终端的PDU会话进行处理。
值得指出的是，上述第二网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息、第二网络单元请求挂起的PDU会话信息。
具体地，恢复成功的PDU会话信息可以用于指示第一网络单元和第二网络单元均恢复成功的PDU会话；
恢复失败的PDU会话信息可以用于指示第二网络单元恢复失败的PDU会话；
第二网络单元请求恢复的PDU会话信息可以用于指示第一网络单元挂起的但第二网络单元请求恢复的PDU会话、第一网络单元没有恢复失败仍然挂起的但第二网络单元请求恢复的PDU会话中的至少一项；
第二网络单元请求释放的PDU会话信息可以用于指示第二网络单元恢复失败的PDU会话、第一网络单元恢复成功但第二网络单元请求释放的PDU会话中的至少一项；
第二网络单元请求挂起的PDU会话信息可以用于指示终端恢复失败的PDU会话、第一网络单元恢复成功但第二网络单元请求释放的PDU会话中的至少一项。
一个例子是：第一网络单元恢复终端的PDU会话1、2、3且终端请求恢复的是PDU会话1。第二网络单元对终端请求的PDU会话1恢复成功。第二网络单元同时发现有下行数据传输需求的PDU会话2，对PDU会话2恢复失成功。此时，不难理解，对多余恢复的PDU会话3，第二网络单元可以指示请求释放PDU会话3或者请求挂起PDU会话3。
另一个例子是：第一网络单元向第二网络单元发送终端请求恢复PDU会 话1。第二网络单元对终端请求的PDU会话1恢复成功。第二网络单元同时发现有下行数据传输需求的PDU会话2，对PDU会话2恢复失成功。此时，不难理解，对多余恢复的PDU会话3，第二网络单元可以指示恢复成功PDU会话1和2并发送给第一网络单元。第一网络单元则对应恢复PDU会话1和2。第一网络单元也会指示UE恢复PDU会话1和2。
根据第二网络单元的PDU会话恢复结果信息，对终端的PDU会话进行处理的步骤，可以包括：
若第二网络单元的PDU会话恢复结果信息为第二网络单元恢复成功的PDU会话信息，对第二网络单元恢复成功的PDU会话可以执行以下操作中的至少一项：
第二网络单元恢复成功的PDU会话信息指示的PDU会话还没有被恢复，可以对PDU会话进行对PDU会话进行恢复操作(对PDU会话进行恢复操作如上，此处不再赘述)；
在检测到第二网络单元恢复成功的PDU会话无法在第一网络单元或终端侧恢复时，可以向第二网络单元发送请求释放或挂起该PDU会话的请求信息；
若第二网络单元的PDU会话恢复结果信息为第二网络单元恢复失败的PDU会话信息，对第二网络单元恢复失败的PDU会话可以执行以下操作中的至少一项：
挂起第二网络单元恢复失败的PDU会话上下文、
挂起第二网络单元恢复失败的PDU会话对应的无线承载的上下文、
释放第二网络单元恢复失败的PDU会话对应的承载资源、
保存第二网络单元恢复失败的PDU会话的上行传输地址、
将第二网络单元恢复失败的PDU会话状态设置为挂起、
请求终端挂起第二网络单元恢复失败的PDU会话、
请求终端删除第二网络单元恢复失败的PDU会话上下文、
请求终端删除第二网络单元恢复失败的PDU会话；
若第二网络单元的PDU会话恢复结果信息为第二网络单元请求恢复的PDU会话信息，可以对第二网络单元请求恢复的PDU会话执行以下操作中 的至少一项：
恢复第二网络单元请求恢复的PDU会话的上下文、
恢复第二网络单元请求恢复的PDU会话对应的无线承载、
为第二网络单元请求恢复的PDU会话分配或映射无线承载资源、
恢复与第二网络单元之间关于终端的连接；
若第二网络单元的PDU会话恢复结果信息为第二网络单元请求释放的PDU会话信息，可以对第二网络单元请求释放的PDU会话执行以下操作中的至少一项：
释放第二网络单元请求释放的PDU会话的上下文、
释放第二网络单元请求释放的PDU会话对应的无线承载上下文、
释放第二网络单元请求释放的PDU会话对应的无线承载资源、
向终端发送第二网络单元请求释放的PDU会话信息；
若第二网络单元的PDU会话恢复结果信息为第二网络单元请求挂起的PDU会话信息，可以对第二网络单元请求挂起的PDU会话执行以下操作中的至少一项：
挂起第二网络单元请求挂起的PDU会话的上下文、
挂起第二网络单元请求挂起的PDU会话对应的无线承载上下文、
释放第二网络单元请求挂起的PDU会话对应的无线承载资源、
向终端发送第二网络单元请求挂起的PDU会话信息。
在另一种实施方式中，步骤12可以包括至少以下之一：
当操作请求信息包括第二网络单元请求恢复的PDU会话信息时，可以执行以下至少一项：向终端发送获取的第二网络单元请求恢复的PDU会话信息；
第一网络单元可以包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元CU、分布式单元DU、基站、eNB、gNB、N3IWF、接入控制节点AC、接入点AP设备或无线局域网WLAN节点。
第二网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、MME、AMF、SMF、SGW、PGW、用户平面功能UPF。
以上介绍了会话控制方法中，第一网络单元的具体操作流程，下面本公开将结合具体场景对其做进一步说明。
场景一、
第一网络单元根据终端请求恢复、释放和/或挂起的PDU会话信息，进行PDU会话处理。
示例一、
第一网络单元获取PDU会话信息的操作请求信息，根据该操作请求信息进行PDU会话处理。其中，该操作请求信息可以包括：终端请求恢复、释放和/或挂起的PDU会话信息。
具体地，第一网络单元可以通过接收终端发送的无线资源控制(Radio Resource Control，RRC)恢复请求(即操作请求信息)，获取终端请求恢复、释放和/或挂起的PDU会话信息。
当RRC恢复请求中携带有终端请求恢复的PDU会话信息时，第一网络单元可以对终端请求恢复的PDU会话进行恢复操作。
当RRC恢复请求中携带有终端请求释放的PDU会话信息时，可以对终端请求释放的PDU会话进行释放操作。
当RRC恢复请求中携带有终端请求挂起的PDU会话信息时，可以对终端请求挂起的PDU会话进行挂起操作。
在对终端请求恢复的PDU会话进行恢复、释放和挂起的过程中，第一网络单元还可以根据处理结果生成确认恢复和/或确认不能恢复的PDU会话信息，以及第一网络单元的PDU会话恢复结果信息中的至少一项。其中，第一网络单元可以向终端发送确认恢复和/或确认不能恢复的PDU会话信息，在向终端发送确认恢复和/或确认不能恢复的PDU会话信息之后，可以接收终端反馈的终端的PDU恢复结果信息。进一步地，第一网络单元还可以向第二网络单元发送第一网络单元的PDU会话恢复结果信息，具体向第二网络单元发送携带有第一网络单元的PDU会话恢复结果信息的会话操作请求；在发送会话操作请求后，还可以接收第二网络单元根据会话操作请求返回的第二网络单元的PDU会话恢复结果信息，再根据第二网络单元的PDU会话恢复结果信息，对终端的PDU会话进行处理。值得指出的是，本公开的一些实施例并不限定这两个步骤的先后关系。
进一步地，第二网络单元的PDU会话恢复结果信息可以包括以下信息中 的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息、第二网络单元请求挂起的PDU会话信息。第一网络单元根据第二网络单元的PDU会话恢复结果信息，对终端的PDU会话进行处理的步骤可参照以下方式实现：
若第二网络单元的PDU会话恢复结果信息为第二网络单元恢复成功的PDU会话信息，在检测到第二网络单元恢复成功的PDU会话无法在第一网络单元或终端侧恢复时，可以向第二网络单元发送请求释放或挂起该PDU会话的请求信息；
若第二网络单元的PDU会话恢复结果信息为第二网络单元恢复失败的PDU会话信息，对第二网络单元恢复失败的PDU会话可以执行以下操作中的至少一项：
挂起第二网络单元恢复失败的PDU会话上下文、
挂起第二网络单元恢复失败的PDU会话对应的无线承载的上下文、
释放第二网络单元恢复失败的PDU会话对应的承载资源、
保存第二网络单元恢复失败的PDU会话的上行传输地址、
将第二网络单元恢复失败的PDU会话状态设置为挂起、
请求终端挂起第二网络单元恢复失败的PDU会话、
请求终端删除第二网络单元恢复失败的PDU会话上下文、
请求终端删除第二网络单元恢复失败的PDU会话；
若第二网络单元的PDU会话恢复结果信息为第二网络单元请求恢复的PDU会话信息，对第二网络单元请求恢复的PDU会话可以执行以下操作中的至少一项：
恢复第二网络单元请求恢复的PDU会话的上下文、
恢复第二网络单元请求恢复的PDU会话对应的无线承载、
为第二网络单元请求恢复的PDU会话分配或映射无线承载资源、
恢复与第二网络单元之间关于终端的连接；
若第二网络单元的PDU会话恢复结果信息为第二网络单元请求释放的PDU会话信息，对第二网络单元请求释放的PDU会话可以执行以下操作中 的至少一项：
释放第二网络单元请求释放的PDU会话的上下文、
释放第二网络单元请求释放的PDU会话对应的无线承载上下文、
释放第二网络单元请求释放的PDU会话对应的无线承载资源、
向终端发送第二网络单元请求释放的PDU会话信息；
若第二网络单元的PDU会话恢复结果信息为第二网络单元请求挂起的PDU会话信息，对第二网络单元请求挂起的PDU会话可以执行以下操作中的至少一项：
挂起第二网络单元请求挂起的PDU会话的上下文、
挂起第二网络单元请求挂起的PDU会话对应的无线承载上下文、
释放第二网络单元请求挂起的PDU会话对应的无线承载资源、
向终端发送第二网络单元请求挂起的PDU会话信息。
示例二、
与示例一不同的是，当RRC恢复请求中携带有终端请求恢复的PDU会话信息时，第一网络单元可以对终端挂起的所有PDU会话进行恢复操作。
示例三、
与示例二不同的是，该示例考虑了系统资源，具体地，当RRC恢复请求中携带有终端请求恢复的PDU会话信息时，第一网络单元可以对终端挂起的所有PDU会话进行恢复操作且在资源不足时，优先对终端请求恢复的PDU会话进行恢复操作。
场景二、
与场景一不同的是，第一网络单元在接收到终端发送的操作请求信息后，可以直接将该操作请求信息转发给第二网络单元，接收第二网络单元根据终端请求恢复的PDU会话信息反馈的第二网络单元的PDU会话恢复结果信息；根据第二网络单元的PDU会话恢复结果信息，可以对终端的PDU会话进行处理。
本公开的一些实施例的会话控制方法中，第一网络单元获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，可以进行PDU会话处理。其中，操作请求信息可以包括以下信息中的至少一项：终端请求恢复 的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢复，从而节省无线接入网的资源，减少信令开销。
以上实施例分别详细介绍了不同场景下的会话控制方法，下面本公开将结合附图对其对应的网络设备做进一步介绍。
如图2所示，本公开的一些实施例的网络设备200，能实现上述实施例中获取分组数据单元PDU会话信息的操作请求信息，根据操作请求信息，进行PDU会话处理方法的细节，并达到相同的效果，该网络设备200可以包括以下功能模块：
第一获取模块210，用于获取分组数据单元PDU会话信息的操作请求信息；操作请求信息可以包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息和终端请求挂起的PDU会话信息；
第一处理模块220，可以用于根据操作请求信息，进行PDU会话处理。
其中，第一处理模块210可以包括：
第一处理子模块，可以用于当操作请求信息为终端请求恢复的PDU会话信息时，执行以下至少一项：对终端请求恢复的PDU会话进行恢复操作；对终端挂起的所有PDU会话进行恢复操作；以及对终端挂起的所有PDU会话进行恢复操作且在资源不足时，优先对终端请求恢复的PDU会话进行恢复操作；
第二处理子模块，可以用于当操作请求信息为终端请求释放的PDU会话信息时，对终端请求释放的PDU会话进行释放操作；
第三处理子模块，可以用于当操作请求信息为终端请求挂起的PDU会话信息时，对终端请求挂起的PDU会话进行挂起操作。
其中，对PDU会话进行恢复操作可以为：
对PDU会话执行以下操作中的至少一项：
恢复PDU会话的上下文；
恢复PDU会话对应的无线承载；
为PDU会话的QoS流分配和/或映射无线承载资源；
恢复第一网络单元与第二网络单元之间关于终端的连接。
其中，第一处理模块还可以包括以下至少一项：
第一发送子模块，可以用于向终端发送确认恢复和/或确认不能恢复的PDU会话信息；
以及，
第二发送子模块，可以用于向第二网络单元发送第一网络单元的PDU会话恢复结果信息；其中，第一网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息。
其中，恢复成功的PDU会话信息可以用于指示终端和第一网络单元均恢复成功的PDU会话；
恢复失败的PDU会话信息可以用于指示终端或第一网络单元恢复失败的PDU会话；
请求释放的PDU会话信息可以用于指示终端恢复失败的PDU会话、第一网络单元恢复失败的PDU会话以及终端请求释放的PDU会话中的至少一项；
请求挂起的PDU会话信息可以用于指示终端恢复失败的PDU会话、第一网络单元恢复失败的PDU会话以及终端请求挂起的PDU会话中的至少一项；
确认恢复的PDU会话信息可以用于指示存在PDU会话上下文的PDU会话、能够分配或映射无线承载资源的PDU会话、第一网络单元和第二网络单元都确认能够恢复的PDU会话中的至少一项；
确认不能恢复的PDU会话可以包括：不存在PDU会话上下文的PDU会话、不能够分配或映射无线承载资源的PDU会话、第一网络单元确认不能恢复的PDU会话、第二网络单元确认不能恢复的PDU会话中的至少一项。
其中，第一处理模块还可以包括：
第一接收子模块，可以用于接收终端反馈的终端的PDU恢复结果信息；其中，终端的PDU恢复结果信息可以包括：终端恢复成功的PDU会话信息和终端恢复失败的PDU会话信息中的至少一项。
其中，第二发送子模块可以包括：
第一发送单元，可以用于向第二网络单元发送携带有第一网络单元的PDU会话恢复结果信息的会话操作请求；
第一接收单元，可以用于接收第二网络单元根据会话操作请求返回的第二网络单元的PDU会话恢复结果信息。
其中，第一处理模块还可以包括：
处理子模块，可以用于根据第二网络单元的PDU会话恢复结果信息，对终端的PDU会话进行处理。
其中，第一处理模块可以包括：
第四处理子模块，可以用于当操作请求信息包括终端请求恢复的PDU会话信息时，可以执行：向第二网络单元发送终端请求恢复的PDU会话信息。
其中，第一处理模块还可以包括：
第二接收子模块，可以用于接收第二网络单元根据终端请求恢复的PDU会话信息反馈的第二网络单元的PDU会话恢复结果信息；
处理子模块，可以用于根据第二网络单元的PDU会话恢复结果信息，对终端的PDU会话进行处理。
其中，第二网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息和第二网络单元请求挂起的PDU会话信息。
其中，处理子模块可以包括：
第一处理单元，可以用于若第二网络单元的PDU会话恢复结果信息为第二网络单元恢复成功的PDU会话信息，在检测到第二网络单元恢复成功的PDU会话无法在第一网络单元或终端侧恢复时，向第二网络单元发送请求释放或挂起该PDU会话的请求信息；
第二处理单元，可以用于若第二网络单元的PDU会话恢复结果信息为第二网络单元恢复失败的PDU会话信息，对第二网络单元恢复失败的PDU会话可以执行以下操作中的至少一项：
挂起第二网络单元恢复失败的PDU会话上下文、
挂起第二网络单元恢复失败的PDU会话对应的无线承载的上下文、
释放第二网络单元恢复失败的PDU会话对应的承载资源、
保存第二网络单元恢复失败的PDU会话的上行传输地址、
将第二网络单元恢复失败的PDU会话状态设置为挂起、
请求终端挂起第二网络单元恢复失败的PDU会话、
请求终端删除第二网络单元恢复失败的PDU会话上下文、
请求终端删除第二网络单元恢复失败的PDU会话；
第三处理单元，可以用于若第二网络单元的PDU会话恢复结果信息为第二网络单元请求恢复的PDU会话信息，对第二网络单元请求恢复的PDU会话可以执行以下操作中的至少一项：
恢复第二网络单元请求恢复的PDU会话的上下文、
恢复第二网络单元请求恢复的PDU会话对应的无线承载、
为第二网络单元请求恢复的PDU会话分配或映射无线承载资源、
恢复与第二网络单元之间关于终端的连接；
第四处理单元，可以用于若第二网络单元的PDU会话恢复结果信息为第二网络单元请求释放的PDU会话信息，对第二网络单元请求释放的PDU会话可以执行以下操作中的至少一项：
释放第二网络单元请求释放的PDU会话的上下文、
释放第二网络单元请求释放的PDU会话对应的无线承载上下文、
释放第二网络单元请求释放的PDU会话对应的无线承载资源、
向终端发送第二网络单元请求释放的PDU会话信息；
第五处理单元，可以用于若第二网络单元的PDU会话恢复结果信息为第二网络单元请求挂起的PDU会话信息，对第二网络单元请求挂起的PDU会话可以执行以下操作中的至少一项：
挂起第二网络单元请求挂起的PDU会话的上下文、
挂起第二网络单元请求挂起的PDU会话对应的无线承载上下文、
释放第二网络单元请求挂起的PDU会话对应的无线承载资源、
向终端发送第二网络单元请求挂起的PDU会话信息。
其中，PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信 息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
其中，第一网络单元可以包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元CU、分布式单元DU、基站、非3GPP互操作功能N3IWF、接入控制节点AC、接入点AP设备或无线局域网WLAN节点；
第二网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、SGW、PGW、用户平面功能UPF。
值得指出的是，本公开的一些实施例的网络设备，通过获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，进行PDU会话处理。其中，操作请求信息可以包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢复，从而节省无线接入网的资源，减少信令开销。
在实施例中，该会话控制方法应用于第一网络单元，如图3所示，还包括以下步骤31-32。
步骤31：获取分组数据单元PDU会话信息的操作请求信息。
其中，操作请求信息可以包括以下信息中的至少一项：第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息。
其中，PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
可选的，在PDU会话比特地图中的比特位置可以代表PDU会话标识(比如第N比特代表的PDU会话标识是N)。第N比特位置可以指示是否操作(比如请求恢复、请求释放、请求挂起、挂起成功)PDU会话标识为N的PDU会话。比如第N比特指示为1，可以指示对相应的PDU会话执行以下会话操 作之一：请求激活、请求恢复、请求释放、请求挂起、确认恢复、恢复成功、释放成功、挂起成功。
比如第N比特指示为0，可以指示对相应的PDU会话执行以下会话操作之一：请求不激活、请求不恢复、请求不释放、请求不挂起、确认不能恢复、恢复失败、释放失败、挂起失败。不难理解、通过PDU会话比特地图可以节省需要传输的信息的字节。
-当请求恢复的PDU会话信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话请求会话。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求会话。
-当请求释放的PDU会话信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话请求释放。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求释放。
-当请求挂起的PDU会话信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话请求挂起。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求挂起。
-当确认恢复的PDU会话信息或确认不能恢复的PDU会话包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话确认恢复和/或哪些PDU会话确认不能恢复。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话请求确认恢复。比如可以通过将第N比特设置为0指示PDU会话标识为N的PDU会话请求确认不能恢复。
-当PDU会话恢复结果信息包含PDU会话比特地图时，PDU会话比特地图可以指示哪些PDU会话恢复成功和/或哪些PDU会话确认恢复失败。比如可以通过将第N比特设置为1指示PDU会话标识为N的PDU会话恢复成功。比如可以通过将第N比特设置为0指示PDU会话标识为N的PDU会话恢复失败。
可选的，PDU会话信息可以包括以下信息中的至少一项：QoS流标识信息、恢复指示信息、挂起指示信息、释放指示信息、QoS流标识比特地图信息、QoS流映射的无线承载信息。一般来说，一个PDU会话可以包含多个QoS流。只有存在至少一个QoS流请求恢复，其对应的PDU的PDU会话就 需要请求恢复。
步骤32：根据操作请求信息，进行PDU会话处理。
一种实施方式中，步骤32可以包括以下(1)-(3)至少一项：
(1)当操作请求信息包含第二网络单元请求恢复的PDU会话信息时，可以对第二网络单元请求恢复的PDU会话进行恢复操作；
(2)当操作请求信息包含第二网络单元请求释放的PDU会话信息时，可以对第二网络单元请求释放的PDU会话进行释放操作；
(3)当操作请求信息包含第二网络单元请求挂起的PDU会话信息时，可以对第二网络单元请求挂起的PDU会话进行挂起操作。
其中，值得说明的是，对PDU会话进行恢复操作的步骤可以为：对PDU会话可以执行以下操作中的至少一项：恢复PDU会话的上下文；恢复PDU会话对应的无线承载；为PDU会话的QoS流分配和/或映射无线承载资源；恢复第一网络单元与第二网络单元之间关于终端的连接。
可选地，步骤32还可以包括：向终端发送操作请求信息。在一种实施例中，当操作请求信息包括第二网络单元请求恢复的PDU会话信息时，可以执行以下至少一项：向终端发送第二网络单元请求恢复的PDU会话信息；当操作请求信息包括第二网络单元请求释放的PDU会话信息时，可以执行以下至少一项：向终端发送第二网络单元请求释放PDU会话信息；当操作请求信息包括第二网络单元请求挂起的PDU会话信息时，可以执行以下至少一项：向终端发送第二网络单元请求挂起的PDU会话信息。
可选地，步骤31可以为：接收第二网络单元发送的寻呼消息或通知消息。操作请求信息携带于寻呼消息或通知消息中。向终端发送操作请求信息可以为：向终端发送接收的寻呼消息或通知消息；
其中，寻呼消息或通知消息中可以携带有指示第二网络单元请求恢复的PDU会话的信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息中至少一项。
场景三、
与场景一和场景二不同的是，第一网络单元可以根据第二网络单元请求恢复、释放和/或挂起的PDU会话信息，进行PDU会话处理。
具体地，第一网络单元可以接收第二网络单元发送的寻呼消息或通知消息(即操作请求信息)，并向终端发送接收的寻呼消息或通知消息。其中，寻呼消息或通知消息中可以携带有指示第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息中至少一项。
当寻呼消息或通知消息包括第二网络单元请求恢复的PDU会话信息时，可以执行以下至少一项：向终端发送第二网络单元请求恢复的PDU会话信息；
当寻呼消息或通知消息包括第二网络单元请求释放的PDU会话信息时，可以执行以下至少一项：向终端发送第二网络单元请求释放PDU会话信息；
当寻呼消息或通知消息包括第二网络单元请求挂起的PDU会话信息时，可以执行以下至少一项：向终端发送第二网络单元请求挂起的PDU会话信息。
其中，值得指出的是，场景一和场景二中，对PDU会话进行恢复操作的步骤为对PDU会话可以执行以下操作中的至少一项：恢复PDU会话的上下文；恢复PDU会话对应的无线承载；为PDU会话的QoS流分配和/或映射无线承载资源；恢复第一网络单元与第二网络单元之间关于终端的连接。
对PDU会话进行挂起操作的步骤为对PDU会话可以执行以下操作中的至少一项：挂起PDU会话的上下文、挂起PDU会话对应的无线承载上下文、释放PDU会话对应的无线承载资源、向终端发送PDU会话信息。
对PDU会话进行释放操作的步骤为对PDU会话可以执行以下操作中的至少一项：释放PDU会话的上下文、释放PDU会话对应的无线承载上下文、释放PDU会话对应的无线承载资源、向终端发送PDU会话信息。
本公开的一些实施例的会话控制方法中，第一网络单元可以获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，可以进行PDU会话处理。其中，操作请求信息可以包括以下信息中的至少一项：第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢复，从而节省无线接入网的资源，减少信令开销。
以上实施例分别详细介绍了不同场景下的会话控制方法，下面的实施例将结合附图对其对应的网络设备做进一步介绍。
如图4所示，本公开的一些实施例的网络设备400，能实现上述实施例中获取分组数据单元PDU会话信息的操作请求信息，根据操作请求信息，进行PDU会话处理方法的细节，并达到相同的效果，该网络设备400可以包括以下功能模块：
第二获取模块410，用于获取分组数据单元PDU会话信息的操作请求信息；操作请求信息可以包括以下信息中的至少一项：第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息；
第二处理模块420，用于根据操作请求信息，进行PDU会话处理。
其中，第二处理模块420可以包括以下至少一项：
第五处理子模块，可以用于当操作请求信息为第二网络单元请求恢复的PDU会话信息时，对第二网络单元请求恢复的PDU会话进行恢复操作；
第六处理子模块，可以用于当操作请求信息为第二网络单元请求释放的PDU会话信息时，对第二网络单元请求释放的PDU会话进行释放操作；
第七处理子模块，可以用于当操作请求信息为第二网络单元请求挂起的PDU会话信息时，对第二网络单元请求挂起的PDU会话进行挂起操作。
其中，第二处理模块420还可以包括：
第三发送子模块，用于向终端发送操作请求信息。
可选地，第二获取模块410还可以执行：接收第二网络单元发送的寻呼消息或通知消息；
第三发送子模块还可以执行：向终端发送接收的寻呼消息或通知消息；
其中，寻呼消息或通知消息中可以携带有指示第二网络单元请求恢复的PDU会话的信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息中至少一项。
本公开的一些实施例的网络设备，第一网络单元获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，可以进行PDU会话处理。其中，操作请求信息可以包括以下信息中的至少一项：第二网络单元请求恢复 的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢复，从而节省无线接入网的资源，减少信令开销。
以上实施例从第一网络单元侧介绍了本公开的会话控制方法，下面本公开将结合附图对第二网络单元侧的会话控制方法做进一步介绍。
本公开的一些实施例提供了一种会话控制方法，应用于第二网络单元侧，第一网络单元可以包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元CU、分布式单元DU、基站、eNB、gNB、非3GPP互操作功能N3IWF、接入控制AC节点、接入点AP设备或无线局域网WLAN节点；第二网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、服务网关SGW、PDN网关PGW、用户平面功能UPF。第三网络单元包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、服务网关SGW、PDN网关PGW、用户平面功能UPF。其中，本公开的一些实施例仅以第一网络单元为无线接入网，第二网络单元为核心网中的AMF和SMF为例进行说明。比如：第二网络单元是MME时，第三网络单元可以是SGW。第二网络单元是AMF时，第三网络单元可以是SMF。第二网络单元是SGW时，第三网络单元可以是PGW。第二网络单元是SMF时，第三网络单元可以是UPF。
如图5所示，本公开的一些实施例的会话控制方法可以包括以下步骤51-52。
步骤51：获取分组数据单元PDU会话信息的操作请求信息。
其中，操作请求信息可以包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数 据通知的PDU会话信息。
可选地，第一网络单元的PDU会话恢复结果信息可以包括：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息中的至少一项；
终端请求恢复的PDU会话信息可以是第一网络单元转发的或终端发送的终端请求恢复的PDU会话信息；比如是第一网络单元通过RRC消息收到终端发送的请求恢复的PDU会话信息后，再通过S1/NG等接口消息发送给第二网络单元。或者比如是终端通过NAS消息直接请求恢复的PDU会话信息。
终端请求释放的PDU会话信息可以是第一网络单元转发的或终端发送的终端请求释放的PDU会话信息；
终端请求挂起的PDU会话信息可以是第一网络单元转发的或终端发送的终端请求恢复的PDU会话信息。
其中，PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
步骤52：根据操作请求信息，进行PDU会话处理。
在一种实施方式中，步骤52可以包括至少以下一项：
对需要进行恢复操作的PDU会话，可以执行以下操作中的至少一项：
恢复相应PDU会话的上下文、
将相应PDU会话的下行传输地址发送至用户面功能实体，向用户面功能实体激活相应的PDU会话；
其中，需要进行恢复操作的PDU会话可以包括：第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话、终端请求恢复的PDU会话信息指示的PDU会话、第三网络单元请求恢复的PDU会话信息指示的PDU会话、有下行数据传输需求的PDU会话信息指示的PDU会话、收到下行数据通知的PDU会话信息指示的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且第三网络单元请求恢复的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且有下行数据传输需求的PDU会话信 息指示的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且收到下行数据通知的PDU会话信息指示的PDU会话，以及终端请求恢复的且第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话中的至少一项。
对终端请求释放的PDU会话信息指示的PDU会话和第一网络单元请求释放PDU会话信息指示的PDU会话中的至少一项，可以执行以下操作：释放终端和/或第二网络单元请求释放的PDU会话。
对终端请求挂起的PDU会话信息指示的PDU会话和第一网络单元请求挂起PDU会话信息指示的PDU会话中的至少一项，可以执行以下操作：挂起终端和/或第二网络单元请求释放的PDU会话。
对第一网络单元的PDU会话恢复结果信息指示的恢复失败的PDU会话，可以执行以下操作中的至少一项：
挂起恢复失败的PDU会话的上下文、
删除恢复失败的PDU会话的上下文、
请求用户面功能删除恢复失败的PDU会话。
可选地，在步骤52之后还可以包括：
生成第二网络单元的PDU会话恢复结果信息，将第二网络单元的PDU会话恢复结果信息发送至第一网络单元和/或通过第一网络单元发送给终端。其中，第二网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息、第二网络单元请求挂起的PDU会话信息；
具体地，第二网络请求恢复的PDU会话信息可以包含：下行数据传送需求的PDU会话信息、收到下行数据通知的PDU会话和第三网络单元请求恢复的PDU会话中的至少一项；
第二网络请求挂起的PDU会话信息可以包含：第二网络恢复失败的PDU会话、第一网络单元恢复成功但第二网络恢复失败的PDU会话、第一网络单元和终端恢复成功但第二网络恢复失败的PDU会话中的至少一项；
第二网络请求释放的PDU会话信息可以包含：第二网络恢复失败的PDU 会话、第一网络单元恢复成功但第二网络恢复失败的PDU会话、第一网络单元和终端恢复成功但第二网络恢复失败的PDU会话中的至少一项。
在一种实施例方式中，步骤52可以包括：当操作请求信息为第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项时，可以通过寻呼请求或通知消息，向第一网络单元发送第三网络单元请求恢复的PDU会话信息第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项。
以上介绍了会话控制方法中，第二网络单元的具体操作流程，下面本公开将结合具体场景对其做进一步说明。
场景四、
对应上述场景一，第一网络单元通过接收终端发送的无线资源控制(Radio Resource Control，RRC)恢复请求(即操作请求信息)，获取终端请求恢复、释放和/或挂起的PDU会话信息，并对相应PDU会话进行恢复、释放和/或挂起处理。在对终端请求恢复的PDU会话进行恢复、释放和挂起的过程中，第一网络单元还可以根据处理结果第一网络单元的PDU会话恢复结果信息，并发送至第二网络单元(如AMF)。第一网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：终端请求恢复、释放和/或挂起的PDU会话信息、恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息。此外，第二网络单元还可以获取第三网络单元(如SMF、用户面功能等)请求恢复、释放和/或挂起的PDU会话信息，以及有下行数据传输需求的PDU会话信息和/或接收到下行数据通知的PDU会话信息。
第二网络单元(如SMF)在获取到上述需要处理的PDU会话信息后，可以执行以下操作：
对需要进行恢复操作的PDU会话，如第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话、终端请求恢复的PDU会话信息指示的PDU 会话、第三网络单元请求恢复的PDU会话信息指示的PDU会话、有下行数据传输需求的PDU会话信息指示的PDU会话、收到下行数据通知的PDU会话信息指示的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且第三网络单元请求恢复的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且有下行数据传输需求的PDU会话信息指示的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且收到下行数据通知的PDU会话信息指示的PDU会话和终端请求恢复的且第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话中的至少一项，可以执行以下操作中的至少一项：
恢复相应PDU会话的上下文、
将相应PDU会话的下行传输地址发送至用户面功能实体，向用户面功能实体激活相应的PDU会话；
对终端请求释放的PDU会话信息指示的PDU会话和第一网络单元请求释放PDU会话信息指示的PDU会话中的至少一项，可以执行以下操作：释放终端和/或第二网络单元请求释放的PDU会话；
对终端请求挂起的PDU会话信息指示的PDU会话和第一网络单元请求挂起PDU会话信息指示的PDU会话中的至少一项，可以执行以下操作：挂起终端和/或第二网络单元请求释放的PDU会话；
对第一网络单元的PDU会话恢复结果信息指示的恢复失败的PDU会话，可以执行以下操作中的至少一项：
挂起恢复失败的PDU会话的上下文、
删除恢复失败的PDU会话的上下文、
请求用户面功能实体删除恢复失败的PDU会话。
可选地，第二网络单元在对相应PDU会话执行完上述操作后还可以包括：生成第二网络单元的PDU会话恢复结果信息，并将第二网络单元的PDU会话恢复结果信息发送至第一网络单元和/或通过第一网络单元发送给终端。这样第一网络单元即可根据第二网络单元的PDU会话恢复结果信息对PDU会话进行进一步处理，其处理方式可参见上述场景一，故在此不再赘述。
场景五、
对应于场景二，第一网络单元可以在接收到终端发送的操作请求信息后，直接将该操作请求信息转发给第二网络单元，第二网络单元直接根据该操作请求对终端的PDU会话进行处理。其中，该操作请求信息中可以包括：终端请求恢复、释放和/或挂起的PDU会话信息。第二网络单元除了对上述PDU会话进行处理外，还可同场景四一样，获取第三网络单元(如SMF、用户面功能等)请求恢复、释放和/或挂起的PDU会话信息，以及有下行数据传输需求的PDU会话信息和/或接收到下行数据通知的PDU会话信息。第二网络单元对相应PDU会话的处理方式可参见场景四，故在此不再赘述。
场景六、
对应于场景三，第二网络单元获取第三网络单元(如SMF、用户面功能等)请求恢复、释放和/或挂起的PDU会话信息，以及有下行数据传输需求的PDU会话信息和/或接收到下行数据通知的PDU会话信息；并可以通过寻呼请求或通知消息向第一网络单元发送第三网络单元请求恢复、释放和/或挂起的PDU会话信息，以及有下行数据传输需求的PDU会话信息和/或收到下行数据通知的PDU会话信息。
本公开的一些实施例的会话控制方法中，第二网络单元通过获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，进行PDU会话处理。其中，操作请求信息可以包括以下信息中的至少一项：操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和/或收到下行数据通知的PDU会话信息。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢复，从而节省无线接入网的资源，减少信令开销。
以上实施例分别详细介绍了不同场景下的会话控制方法，下面本公开将结合附图对其对应的网络设备做进一步介绍。
如图6所示，本公开的一些实施例的网络设备60，能实现上述实施例中 获取分组数据单元PDU会话信息的操作请求信息，根据操作请求信息，进行PDU会话处理方法的细节，并达到相同的效果，该网络设备600具体包括以下功能模块：
第三获取模块610，可以用于获取分组数据单元PDU会话信息的操作请求信息；操作请求信息可以包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息；
第三处理模块620，可以用于根据操作请求信息，进行PDU会话处理。
其中，第一网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息；
终端请求恢复的PDU会话信息可以是第一网络单元转发的或终端发送的终端请求恢复的PDU会话信息；
终端请求释放的PDU会话信息可以是第一网络单元转发的或终端发送的终端请求释放的PDU会话信息；
终端请求挂起的PDU会话信息可以是第一网络单元转发的或终端发送的终端请求恢复的PDU会话信息。
其中，第三处理模块620可以包括至少以下一项：
第八处理子模块，用于对需要进行恢复操作的PDU会话，可以执行以下操作中的至少一项：
恢复相应PDU会话的上下文、
将相应PDU会话的下行传输地址发送至用户面功能实体，向用户面功能实体激活相应的PDU会话；
其中，需要进行恢复操作的PDU会话可以包括：第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话、终端请求恢复的PDU会话信息指示的PDU会话、第三网络单元请求恢复的PDU会话信息指示的PDU会 话、有下行数据传输需求的PDU会话信息指示的PDU会话、收到下行数据通知的PDU会话信息指示的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且第三网络单元请求恢复的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且有下行数据传输需求的PDU会话信息指示的PDU会话、第一网络单元的PDU会话恢复结果信息指示恢复成功且收到下行数据通知的PDU会话信息指示的PDU会话、和终端请求恢复的且第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话中的至少一项。
第九处理子模块，可以用于对终端请求释放的PDU会话信息指示的PDU会话和第一网络单元请求释放PDU会话信息指示的PDU会话中的至少一项，执行以下操作：释放终端和/或第二网络单元请求释放的PDU会话；
第十处理子模块，可以用于对终端请求挂起的PDU会话信息指示的PDU会话和第一网络单元请求挂起PDU会话信息指示的PDU会话中的至少一项，执行以下操作：挂起终端和/或第二网络单元请求释放的PDU会话；
第十一处理子模块，可以用于对第一网络单元的PDU会话恢复结果信息指示的恢复失败的PDU会话，可以执行以下操作中的至少一项：
挂起恢复失败的PDU会话的上下文、
删除恢复失败的PDU会话的上下文、
请求用户面功能实体删除恢复失败的PDU会话。
其中，网络设备600还可以包括：
第一生成模块，可以用于生成第二网络单元的PDU会话恢复结果信息；其中，第二网络单元的PDU会话恢复结果信息可以包括以下信息中的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息、第二网络单元请求挂起的PDU会话信息；
第二发送模块，可以用于将第二网络单元的PDU会话恢复结果信息发送至第一网络单元和/或通过第一网络单元发送给终端。
其中，第二网络请求恢复的PDU会话信息可以包含至少以下之一：下行数据传送需求的PDU会话信息、收到下行数据通知的PDU会话、第三网络 单元请求恢复的PDU会话；
第二网络请求挂起的PDU会话信息可以包含至少以下之一：第二网络恢复失败的PDU会话、第一网络单元恢复成功但第二网络恢复失败的PDU会话、第一网络单元且终端恢复成功但第二网络恢复失败的PDU会话；
第二网络请求释放的PDU会话信息可以包含至少以下之一：第二网络恢复失败的PDU会话、第一网络单元恢复成功但第二网络恢复失败的PDU会话、第一网络单元且终端恢复成功但第二网络恢复失败的PDU会话。
其中，第三处理模块620还可以包括：
第十二处理子模块，可以用于当操作请求信息为第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项时，通过寻呼请求或通知消息，向第一网络单元发送第三网络单元请求恢复的PDU会话信息第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项。
其中，PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
其中，第一网络单元可以包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元CU、分布式单元DU、基站、eNB、gNB、N3IWF、AC、接入点AP设备或无线局域网WLAN节点；
第二网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、服务网关SGW、PDN网关PGW、用户平面功能UPF；
第三网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、服务网关SGW、PDN网关PGW、用户平面功能UPF。
本公开的一些实施例的网络设备，通过获取分组数据单元PDU会话信息 的操作请求信息；根据操作请求信息，进行PDU会话处理。其中，操作请求信息可以包括以下信息中的至少一项：操作请求信息可以包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢复，从而节省无线接入网的资源，减少信令开销。
为了更好的实现上述目的，本公开的实施例还提供了一种网络设备，该网络设备包括处理器、存储器以及存储于存储器上并可在处理器上运行的计算机程序，处理器执行计算机程序时实现如上的会话控制方法中的步骤。
本公开的一些实施例还提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器执行时实现如上的会话控制方法的步骤。
本公开的计算机可读存储介质可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。
具体地，本公开的一些实施例还提供了一种网络设备。如图7所示，该网络设备700可以包括：天线71、射频装置72、基带装置73。天线71与射频装置72连接。在上行方向上，射频装置72通过天线71接收信息，将接收的信息发送给基带装置73进行处理。在下行方向上，基带装置73对要发送的信息进行处理，并发送给射频装置72，射频装置72对收到的信息进行处理后经过天线71发送出去。
上述频带处理装置可以位于基带装置73中，以上实施例中网络设备执行的方法可以在基带装置73中实现，该基带装置73包括处理器74和存储器75。
基带装置73例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图7所示，其中一个芯片例如为处理器74，与存储器75连接，以调用存 储器75中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置73还可以包括网络接口76，用于与射频装置72交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
这里的处理器可以是一个处理器，也可以是多个处理元件的统称，例如，该处理器可以是CPU，也可以是ASIC，或者是被配置成实施以上网络设备所执行方法的一个或多个集成电路，例如：一个或多个微处理器DSP，或，一个或者多个现场可编程门阵列FPGA等。存储元件可以是一个存储器，也可以是多个存储元件的统称。
存储器75可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(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，简称DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，简称ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，简称SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，简称DRRAM)。本公开描述的存储器75旨在包括但不限于这些和任意其它适合类型的存储器。
具体地，本公开的一些实施例的网络设备还包括：存储在存储器75上并可在处理器74上运行的计算机程序，处理器74调用存储器75中的计算机程序执行图2、图4或图6所示各模块执行的方法。
本公开的一些实施例中的网络设备，通过获取分组数据单元PDU会话信息的操作请求信息；根据操作请求信息，进行PDU会话处理。这样，通过终端、第一网络单元和第二网络单元之间的相互配合，被挂起的终端在连接恢复时，可以按操作请求信息中需要恢复的PDU会话信息进行PDU会话的恢 复，从而节省无线接入网的资源，减少信令开销。
以上实施例从网络设备侧介绍了本公开的会话控制方法，下面本公开将结合附图对终端侧的会话控制方法做进一步介绍。
如图8所示，本公开的一些实施例的会话控制方法，应用于终端侧，具体包括以下步骤81-83。
步骤81：向第一网络单元发送分组数据单元PDU会话信息的操作请求信息。
其中，操作请求信息可以包括至少以下之一：终端自身请求的PDU会话信息、第二网络请求恢复的PDU会话信息、第一网络请求恢复的PDU会话信息。
步骤82：接收第一网络单元根据操作请求信息发送的PDU会话操作响应信息。
可选地，PDU会话操作响应信息信息包括：确认恢复和/或确认不能恢复的PDU会话信息。
步骤83：根据PDU会话操作响应信息信息信息，对PDU会话进行处理。
具体地，根据确认恢复和/或确认不能恢复的PDU会话的信息，对PDU会话进行处理的步骤，可以包括至少以下之一：根据确认恢复的PDU会话的信息，恢复确认恢复的PDU会话；根据确认不能恢复的PDU会话的信息，释放或挂起不能恢复的PDU会话。
在一种实施方式中，在步骤81之前所述方法还可以包括：生成请求恢复的PDU会话信息。在生成请求恢复的PDU会话信息后，将请求恢复的PDU会话信息发送至第一网络单元，具体可通过RRC恢复请求进行发送。
在一种实施方式中，在步骤81之前所述方法还可以包括：接收第一网络单元发送的请求恢复的PDU会话信息。具体地，可通过寻呼，接收第一网络单元发送的请求恢复的PDU会话信息。
在一种实施方式中，在步骤81之前所述方法还可以包括：通过第一网络单元接收第二网络单元发送的请求恢复的PDU会话信息。具体地，可通过寻呼，接收第一网络单元发送的第二网络单元请求恢复的PDU会话信息。
可选地，在步骤81之前所述方法还可包括：通过通知消息，接收第二单 元请求恢复的PDU会话信息。
可选地，在步骤81之后所述方法还可以包括：在根据确认恢复或确认不能恢复的PDU会话的信息；对PDU会话进行处理的步骤之后，所述方法还可以包括：生成PDU会话处理后的终端的PDU会话恢复结果信息并反馈至第一网络单元。其中，终端的PDU恢复结果信息可以包括以下信息中的至少一项：终端恢复成功的PDU会话信息、终端恢复失败的PDU会话信息、终端释放成功的PDU会话信息和终端挂起的PDU会话信息。
值得指出的是，上述PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。在PDU会话标识比特地图中的比特位置代表PDU会话标识，某比特位置指示是否恢复指示该比特代表的PDU会话是否恢复。
上述第一网络单元可以包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元CU、分布式单元DU、基站、eNB、gNB、N3IWF、接入控制节点AC、接入点AP设备或无线局域网WLAN节点；
第二网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、服务网关SGW、PDN网关PGW、用户平面功能UPF。
本公开的一些实施例通过终端、第一网络单元和第二网络单元的配合，被挂起的终端在连接恢复时，可以按需恢复PDU会话，节省无线接入网的资源，减少信令开销。
以上实施例介绍了不同场景下的会话控制方法，下面将结合附图对与其对应的终端做进一步介绍。
如图9所示，本公开的一些实施例的终端900，能实现上述实施例中向第一网络单元发送请求恢复的分组数据单元PDU会话信息方法的细节，并达到相同的效果，该终端900可以包括以下功能模块：
第三发送模块910，可以用于向第一网络单元发送分组数据单元PDU会话信息的操作请求信息；
第二接收模块920，可以用于接收第一网络单元根据操作请求信息发送的第一网络单元的PDU会话恢复结果信息；
第四处理模块930，可以用于根据第一网络单元的PDU会话恢复结果信息，对PDU会话进行处理。
其中，操作请求信息包括至少以下之一：
终端自身请求的PDU会话信息、第二网络请求恢复的PDU会话信息、第一网络请求恢复的PDU会话信息。
其中，终端900还可以包括至少以下之一：
第二生成模块，可以用于生成请求恢复的PDU会话信息；
第三接收模块，可以用于接收第一网络单元发送的请求恢复的PDU会话信息；
第四发送模块，可以用于通过第一网络单元接收第二网络单元发送的请求恢复的PDU会话信息。
其中，第一网络单元的PDU会话恢复结果信息可以包括：确认恢复和/或确认不能恢复的PDU会话信息；
第四处理模块930可以包括至少以下之一：
第十三处理子模块，可以用于根据确认恢复和/或确认不能恢复的PDU会话的信息，对PDU会话进行处理。
可选地，第十三处理子模块可以用于：根据确认恢复的PDU会话的信息，恢复确认恢复的PDU会话；
根据确认不能恢复的PDU会话的信息，释放或挂起不能恢复的PDU会话。
其中，第四处理模块930还可以包括：
反馈子模块，可以用于生成PDU会话处理后的终端的PDU会话恢复结果信息并反馈至第一网络单元；其中，终端的PDU恢复结果信息可以包括以下信息中的至少一项：终端恢复成功的PDU会话信息、终端恢复失败的PDU会话信息、终端释放成功的PDU会话信息和终端挂起的PDU会话信息。
其中，PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会 话标识比特地图信息和PDU会话中QoS流信息。
其中，第一网络单元可以包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元CU、分布式单元DU、基站、eNB、gNB、N3IWF、接入控制节点AC、接入点AP设备或无线局域网WLAN节点；
第二网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、服务网关SGW、PDN网关PGW、用户平面功能UPF。
值得指出的是，本公开的一些实施例通过终端、第一网络单元和第二网络单元的配合，被挂起的终端在连接恢复时，可以按需恢复PDU会话，节省无线接入网的资源，减少信令开销。
需要说明的是，应理解以上网络设备和终端的各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些模块可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分模块通过处理元件调用软件的形式实现，部分模块通过硬件的形式实现。例如，确定模块可以为单独设立的处理元件，也可以集成在上述装置的某一个芯片中实现，此外，也可以以程序代码的形式存储于上述装置的存储器中，由上述装置的某一个处理元件调用并执行以上确定模块的功能。其它模块的实现与之类似。此外这些模块全部或部分可以集成在一起，也可以独立实现。这里的处理元件可以是一种集成电路，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个模块可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。
例如，以上这些模块可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个专用集成电路(Application Specific Integrated Circuit，简称ASIC)，或，一个或多个微处理器(例如digital signal processor，简称DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，简称FPGA)等。再如，当以上某个模块通过处理元件调度程序代码的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing  Unit，简称CPU)或其它可以调用程序代码的处理器。再如，这些模块可以集成在一起，以片上系统(system-on-a-chip，简称SOC)的形式实现。
为了更好的实现上述目的，进一步地，图10为实现本公开各个实施例的一种终端的硬件结构示意图，该终端100包括但不限于：射频单元101、网络模块102、音频输出单元103、输入单元104、传感器105、显示单元106、用户输入单元107、接口单元108、存储器109、处理器1010、以及电源1011等部件。本领域技术人员可以理解，图10中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开的一些实施例中，终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
其中，射频单元101，可以用于在处理器1010的控制下，向第一网络单元发送请求恢复的分组数据单元PDU会话信息。
其中，请求恢复的PDU会话信息可以包括至少以下之一:
终端自身请求的PDU会话信息、第二网络请求恢复的PDU会话信息、第一网络请求恢复的PDU会话信息。
具体地，处理器1010，可以用于在向第一网络单元发送请求恢复的分组数据单元PDU会话信息之前，执行以下至少之一：
生成请求恢复的PDU会话信息；
接收第一网络单元发送的请求恢复的PDU会话信息；
通过第一网络单元接收第二网络单元发送的请求恢复的PDU会话信息；
通过寻呼，接收第一网络单元发送的请求恢复的PDU会话信息；
通过寻呼，接收第一网络单元发送的第二网络单元请求恢复的PDU会话信息；
通过通知消息，接收第二单元请求恢复的PDU会话信息。
具体地，处理器1010还可以用于：接收第一网络单元反馈的确认恢复的PDU会话信息和/或确认不能恢复的PDU会话的信息；
根据确认恢复或确认不能恢复的PDU会话的信息，对PDU会话进行处理。
具体地，处理器1010还可以用于：可以根据确认恢复的PDU会话的信 息，恢复确认恢复的PDU会话；
根据确认不能恢复的PDU会话的信息，释放或挂起不能恢复的PDU会话。
具体地，处理器1010还用于：生成PDU会话处理后的终端的PDU会话恢复结果信息并反馈至第一网络单元；其中，终端的PDU恢复结果信息可以包括以下信息中的至少一项：终端恢复成功的PDU会话信息、终端恢复失败的PDU会话信息、终端释放成功的PDU会话信息和终端挂起的PDU会话信息。
具体地，PDU会话信息可以包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
具体地，上述第一网络单元可以包括至少以下之一：无线接入网设备、无线接入网节点、无线接入网功能单元、集中单元CU、分布式单元DU、基站、eNB、gNB、N3IWF、接入控制节点AC、接入点AP设备或无线局域网WLAN节点；
第二网络单元可以包括至少以下之一：核心网设备、核心网节点、核心网功能单元、移动管理实体MME、接入管理功能AMF、会话管理功能SMF、服务网关SGW、PDN网关PGW、用户平面功能UPF。
具体来说，终端产生PDU会话恢复需求；
终端发送请求恢复的PDU会话信息；
终端向第一网络单元发送请求恢复的PDU会话信息。
进一步地，终端接收确认恢复的PDU会话信息；
终端根据确认恢复的PDU会话信息进行PDU恢复操作。
在接收确认恢复的PDU会话信息之前，终端还发送请求恢复的PDU会话信息。
本公开的一些实施例通过终端、第一网络单元和第二网络单元的配合，被挂起的终端在连接恢复时，可以按需恢复PDU会话，节省无线接入网的资源，减少信令开销。
应理解的是，本公开的一些实施例中，射频单元101可用于收发信息或 通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器1010处理；另外，将上行的数据发送给基站。通常，射频单元101包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元101还可以通过无线通信系统与网络和其他设备通信。
终端通过网络模块102为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元103可以将射频单元101或网络模块102接收的或者在存储器109中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元103还可以提供与终端100执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元103包括扬声器、蜂鸣器以及受话器等。
输入单元104用于接收音频或视频信号。输入单元104可以包括图形处理器(Graphics Processing Unit，GPU)1041和麦克风1042，图形处理器1041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元106上。经图形处理器1041处理后的图像帧可以存储在存储器109(或其它存储介质)中或者经由射频单元101或网络模块102进行发送。麦克风1042可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元101发送到移动通信基站的格式输出。
终端100还包括至少一种传感器105，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板1061的亮度，接近传感器可在终端100移动到耳边时，关闭显示面板1061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器105还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、 陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元106用于显示由用户输入的信息或提供给用户的信息。显示单元106可包括显示面板1061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板1061。
用户输入单元107可用于接收输入的数字或字符信息，以及产生与终端的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元107包括触控面板1071以及其他输入设备1072。触控面板1071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板1071上或在触控面板1071附近的操作)。触控面板1071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器1010，接收处理器1010发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板1071。除了触控面板1071，用户输入单元107还可以包括其他输入设备1072。具体地，其他输入设备1072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板1071可覆盖在显示面板1061上，当触控面板1071检测到在其上或附近的触摸操作后，传送给处理器1010以确定触摸事件的类型，随后处理器1010根据触摸事件的类型在显示面板1061上提供相应的视觉输出。虽然在图10中，触控面板1071与显示面板1061是作为两个独立的部件来实现终端的输入和输出功能，但是在某些实施例中，可以将触控面板1071与显示面板1061集成而实现终端的输入和输出功能，具体此处不做限定。
接口单元108为外部装置与终端100连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元108可以用于接收来 自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到终端100内的一个或多个元件或者可以用于在终端100和外部装置之间传输数据。
存储器109可用于存储软件程序以及各种数据。存储器109可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器109可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器1010是终端的控制中心，利用各种接口和线路连接整个终端的各个部分，通过运行或执行存储在存储器109内的软件程序和/或模块，以及调用存储在存储器109内的数据，执行终端的各种功能和处理数据，从而对终端进行整体监控。处理器1010可包括一个或多个处理单元；可选的，处理器1010可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器1010中。
终端100还可以包括给各个部件供电的电源1011(比如电池)，可选的，电源1011可以通过电源管理系统与处理器1010逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，终端100包括一些未示出的功能模块，在此不再赘述。
可选的，本公开的一些实施例还提供一种终端，包括处理器1010，存储器109，存储在存储器109上并可在处理器1010上运行的计算机程序，该计算机程序被处理器1010执行时实现上述会话控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，终端可以是无线终端也可以是有线终端，无线终端可以是指向用户提供语音和/或其他业务数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network，简称RAN)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携 式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，简称PCS)电话、无绳电话、会话发起协议(Session Initiation Protocol，简称SIP)话机、无线本地环路(Wireless Local Loop，简称WLL)站、个人数字助理(Personal Digital Assistant，简称PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device or User Equipment)，在此不作限定。
本公开的一些实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述会话控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，本公开的计算机可读存储介质可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
以上分别从第一网络单元、第二网络单元和终端介绍了本公开的一些实施例的会话控制方法的不同处理方式，下面本公开将以PDU会话恢复操作为例对不同场景下的会话控制方法做进一步说明。
如图11所示，本公开的一些实施例的网络架构包括：终端、第一网络单元(以无线接入网为例)、第二网络单元(以核心网为例)，其中，核心网包括接入管理功能AMF、会话管理功能SMF和用户面功能。无线接入网接收UE发送的请求恢复的PDU会话信息，并根据UE请求恢复的PDU会话的进行恢复，其中，无线接入网优先UE请求的PDU会话情况下恢复UE的所有PDU会话，此后，无线接入网将UE请求恢复的PDU会话信息发送给核心网。
第一示例
UE向无线接入网发送请求恢复的PDU会话信息，无线接入网可以根据UE请求恢复的PDU会话进行恢复，并将PDU会话恢复的结果通知核心网进行PDU会话恢复。核心网接收无线接入网发送的PDU会话恢复的结果进行 PDU会话恢复，并将核心网PDU会话恢复的结果通知无线接入网。UE根据无线接入网的确认恢复的PDU会话进行PDU会话恢复。
具体地，该示例为恢复操作，PDU会话恢复顺序是无线接入网与UE先恢复，核心网侧再根据UE和无线接入网的PDU会话恢复结果进行PDU会话的恢复。其优点是完成UE和无线接入网侧的PDU会话恢复后，UE即可发送上行数据。在该示例中，无线接入网是根据UE请求恢复的PDU会话信息进行PDU会话恢复的。如图12所示，该示例具体包括以下步骤：
步骤121：UE向无线接入网发送RRC恢复请求。这里，RRC恢复请求对应上述操作请求信息。可选的，在操作请求信息中可以指示至少以下之一：请求恢复的PDU会话的信息。
对不属于请求恢复的PDU会话，无线接入网可以继续挂起或进行释放。
无线接入网可以根据UE的请求进行PDU会话恢复操作，包括至少以下之一：
-恢复指定PDU会话的上下文，
-恢复指定PDU会话映射的无线承载(如数据资源承载(Data Resource Bearer，DRB)等)，
-为指定的PDU会话分配或映射无线承载(如DRB)，
-恢复无线接入网与核心网之间关于UE的连接。
在一些实施方式中，由于无线资源紧缺，不是每个UE请求的PDU会话都能够被分配无线资源。所以，无线接入网可以将确认恢复的PDU会话的信息发送给UE。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤122：无线接入网向UE发送RRC恢复，RRC恢复中携带有PDU会话恢复结果信息，可选的，在RRC恢复指示至少以下之一：确认恢复的PDU会话信息、确认不能恢复的PDU会话信息。
UE根据指示的“确认恢复的PDU会话信息和/或确认不能恢复的PDU会话信息”进行PDU会话恢复。
步骤123：UE向无线接入网发送RRC恢复完成。可选的，在RRC恢复 完成中可以指示至少以下之一：UE恢复成功的PDU会话的信息、UE侧恢复失败的PDU会话的信息。
在一些实施方式中，由于不可预知的原因，UE侧可能不是都能恢复PDU会话。需要UE返回UE的PDU会话恢复结果信息确认UE上的PDU会话的恢复结果。
步骤124：无线接入网向接入移动管理功能发送恢复请求。
可选的，在恢复请求中携带有无线接入网的PDU会话恢复结果信息，具体可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息指示无线接入网根据UE请求确认在UE和无线接入网上恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤125：接入移动管理功能向UE的PDU会话的会话管理功能发送恢复请求。
可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息指示无线接入网根据UE请求确认在UE和无线接入网上恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
其中，
-对恢复成功的UE的PDU会话，会话管理功能可以执行至少以下之一：恢复UE的PDU会话上下文，将UE的PDU会话的下行传输地址(即无线接入网为UE的PDU会话分配的传输地址)发送用户面功能，向用户面功能激活UE的PDU会话，将UE的PDU会话状态设置为激活。
-对恢复失败的UE的PDU会话和/或请求挂起的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起UE的PDU会话，删除UE的PDU会话，请求用户面功能删除UE的PDU会话。在一些实施方式中，继续挂起还是删除恢复失败的UE的PDU会话取决于恢复失败的原因。比如无线接入网侧资源不足导致的恢复失败可以继续挂起。比如是请求恢复的PDU会 话是未知的PDU会话说明信息不一致，应该删除。
-对请求挂起的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起UE的PDU会话。
-对请求释放的PDU会话信息，会话管理功能可以执行至少以下之一：删除UE的PDU会话，请求用户面功能删除UE的PDU会话。
步骤126：会话管理功能向接入移动管理功能发送恢复响应，该恢复响应对应上述第二网络单元的PDU会话恢复结果信息。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息指示会话管理功能在核心网侧恢复成功的PDU会话的信息。
步骤127：接入移动管理功能向无线接入网发送恢复响应，对应上述第二网络单元的PDU会话恢复结果信息。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息指示会话管理功能在核心网侧恢复成功的PDU会话的信息。
-对恢复失败的PDU会话的信息，无线接入网可以执行以下之一：挂起PDU会话上下文、挂起PDU会话的映射的无线承载的上下文、释放承载资源、保存PDU会话的上行传输地址(即用户面功能为UE的PDU会话分配的传输地址)、将UE的PDU会话状态设置为挂起、请求UE挂起PDU会话、删除PDU会话上下文、请求UE删除PDU会话。
第二示例
该示例为恢复操作。恢复顺序是无线接入网侧与UE先恢复PDU会话；核心网侧再根据UE和无线接入侧的PDU会话恢复结果恢复PDU会话。优点是完成UE与无线接入网之间的PDU会话恢复后UE即可发送上行数据。
在本示例中，网络根据UE请求的PDU会话信息和第二网络单元请求的PDU会话信息，如有数据传送需求的PDU会话信息进行恢复。如图13所示，该示例具体包括以下步骤：
步骤131：UE向无线接入网发送RRC恢复请求。可选的，在请求中可以指示至少以下之一：请求恢复的PDU会话的信息。
对不属于请求恢复的PDU会话，无线接入网可以继续挂起或进行释放。
无线接入网可以根据UE的请求进行PDU会话恢复操作，包括至少以下之一：
-恢复指定PDU会话的上下文，
-恢复指定PDU会话映射的无线承载(如DRB)，
-为指定的PDU会话分配或映射无线承载(如DRB)，
-恢复无线接入网与核心网之间关于UE的连接。
在一些实施方式中，由于无线资源紧缺，不是每个UE请求的PDU会话都能够被分配无线资源。所以，无线接入网需要可以将确认恢复的PDU会话的信息发送给UE。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤132：无线接入网向UE发送RRC恢复，可选的，在RRC恢复指示至少以下之一：确认恢复的PDU会话的信息、确认不能恢复的PDU会话的信息。
UE根据指示的“确认恢复的PDU会话的信息和/或确认不能恢复的PDU会话的信息”进行PDU会话恢复。
步骤133：UE向无线接入网发送RRC恢复完成。可选的，在RRC恢复完成中可以指示至少以下之一：UE恢复成功的PDU会话的信息、UE侧恢复失败的PDU会话的信息。
在一些实施方式中，由于不可预知的原因，UE侧可能不是都能恢复PDU会话。需要UE返回UE的PDU会话恢复结果。
步骤134：无线接入网向接入移动管理功能发送恢复请求。
可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息指示无线接入网根据UE请求确认在UE和无线接入网上恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤135：接入移动管理功能向UE的PDU会话的会话管理功能发送恢 复请求。
可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息指示无线接入网根据UE请求确认在UE和无线接入网上恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
-对恢复成功的UE的PDU会话，会话管理功能可以执行至少以下之一：恢复UE的PDU会话上下文，将UE的PDU会话的下行传输地址(即无线接入网为UE的PDU会话分配的传输地址)发送用户面功能，向用户面功能激活UE的PDU会话，将UE的PDU会话状态设置为激活。
-对恢复失败的UE的PDU会话和/或请求挂起的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起UE的PDU会话，删除UE的PDU会话，请求用户面功能删除UE的PDU会话。在一些实施方式中，继续挂起还是删除恢复失败的UE的PDU会话取决于恢复失败的原因。比如无线接入网侧资源不足导致的恢复失败可以继续挂起。比如是请求恢复的PDU会话是未知的PDU会话说明信息不一致，应该删除。
-对请求挂起的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起UE的PDU会话。
-对请求释放的PDU会话信息，会话管理功能可以执行至少以下之一：删除UE的PDU会话，请求用户面功能删除UE的PDU会话。
-对有下行数据传送需求(如收到下行数据通知)的PDU会话，会话管理功能可以执行至少以下之一：恢复UE的PDU会话，发送关于该PDU会话的要求恢复的PDU会话的信息。
步骤136：会话管理功能向接入移动管理功能发送恢复响应。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息、核心网请求恢复的PDU会话的信息。恢复成功的PDU会话信息指示会话管理功能在核心网侧恢复成功的PDU会话的信息。要求恢复的PDU会话的信息指示会话管理功能额外要求恢复的PDU会话的信息。
步骤137：接入移动管理功能向无线接入网发送恢复响应。可选的，在 请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息、核心网请求恢复的PDU会话的信息。恢复成功的PDU会话信息指示会话管理功能在核心网侧恢复成功的PDU会话的信息。
-对恢复失败的PDU会话的信息，无线接入网可以执行以下之一：挂起PDU会话上下文、挂起PDU会话的映射的无线承载的上下文、释放承载资源、保存PDU会话的上行传输地址(即用户面功能为UE的PDU会话分配的传输地址)、将UE的PDU会话状态设置为挂起、请求UE挂起PDU会话、删除PDU会话上下文、请求UE删除PDU会话。
-要求恢复的PDU会话的信息，无线接入网可以执行以下之一：恢复UE的PDU会话、请求UE恢复PDU会话。可以通过RRC重配置消息包含指定恢复的PDU会话请求UE.
根据要求恢复的PDU会话的信息，无线接入网可以执行以下之一：
-恢复指定PDU会话的上下文，
-恢复指定PDU会话映射的无线承载(如DRB)，
-为指定的PDU会话分配或映射无线承载(如DRB)，
-恢复无线接入网与核心网之间关于UE的连接。
-向UE发送要求释放/挂起的PDU会话的信息。
可选的，步骤138：无线接入网向UE发送RRC重配置请求消息。可选的，消息中可以包括要求恢复的PDU会话的信息。
UE根据收到的要求恢复的PDU会话的信息进行指定PDU会话的恢复。
可选的，步骤139：UE向无线接入网返回RRC重配置消息响应消息。可选的，在消息中中可以指示至少以下之一：UE恢复成功的PDU会话的信息、UE侧恢复失败的PDU会话的信息。
第三示例
该示例为恢复操作，PDU会话恢复顺序是无线接入网侧与UE先恢复PDU会话，核心网侧再根据UE和无线接入网的PDU会话恢复结果、以及UE请求恢复的PDU会话信息进行PDU会话的恢复。其优点是完成UE和无线接入网侧的PDU会话恢复后，UE即可发送上行数据。在该示例中，无线接入网尝试恢复UE所有的挂起的PDU会话，在资源不足时优先恢复UE请 求的PDU会话信息。等恢复请求到了会话管理功能后，会话管理功能网络根据UE请求的PDU会话信息和有数据传送需求的PDU会话信息进行恢复。无线接入网根据会话管理功能最终需要恢复的PDU会话的信息，挂起/释放不需要的PDU会话的资源。如图14所示，该示例具体包括以下步骤：
步骤141：UE向无线接入网发送RRC恢复请求。可选的，UE可以在步骤141或者步骤143中指示至少以下之一：UE请求恢复的PDU会话的信息。
可选的，无线接入网进行PDU会话恢复操作，可以包括至少以下之一：
-恢复挂起的UE的PDU会话的上下文，
-恢复挂起的UEPDU会话映射的无线承载(如DRB)，
-为UE的PDU会话分配或映射无线承载(如DRB)，
-恢复无线接入网与核心网之间关于UE的连接。
在一些实施方式中，由于无线资源紧缺，不是每个UE请求的PDU会话都能够被分配无线资源。无线接入网可以优先恢复UE请求激活的PDU会话。另外，无线接入网可以将确认恢复的PDU会话的信息发送给UE。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤142：无线接入网向UE发送RRC恢复，可选的，在RRC恢复指示至少以下之一：确认恢复的PDU会话的信息。在一些实施方式中，确认恢复的PDU会话信息可以是无线接入侧恢复成功的PDU会话。
UE根据指示的“确认恢复的PDU会话的信息”进行PDU会话恢复。
步骤143：UE向无线接入网发送RRC恢复完成。可选的，在RRC恢复完成中可以指示UE的PDU会话恢复结果信息，包含至少以下之一：UE恢复成功的PDU会话的信息、UE侧恢复失败的PDU会话的信息。
在一些实施方式中，由于不可预知的原因，有些PDU会话可能在UE侧恢复失败。对UE侧恢复失败的PDU会话，无线接入网可以执行以下之一：释放/挂起PDU会话，请求核心网释放/挂起PDU会话。
步骤144：无线接入网向接入移动管理功能发送恢复请求。
可选的，在请求中携带有无线接入网的PDU会话恢复结果信息以及终端请求恢复的PDU会话信息，具体可以指示至少以下之一：恢复成功的PDU 会话的信息、恢复失败的PDU会话的信息、UE请求恢复的PDU会话的信息。恢复成功的PDU会话信息指示无线接入网根据UE请求确认在UE和无线接入网上恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤145：接入移动管理功能向UE的PDU会话的会话管理功能发送恢复请求。
可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息、UE请求恢复的PDU会话的信息。恢复成功的PDU会话信息可以是无线接入网和UE侧都恢复成功的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
-对(1)无线接入网侧恢复成功的PDU会话并且是UE请求激活的PDU会话和(2)无线接入网侧恢复成功的PDU会话并且有下行数据传送需求的PDU会话中的至少一项，会话管理功能可以执行至少以下之一：恢复UE的PDU会话上下文，将UE的PDU会话的下行传输地址(即无线接入网为UE的PDU会话分配的传输地址)发送用户面功能，向用户面功能激活UE的PDU会话，将UE的PDU会话状态设置为激活。在一些实施方式中，有下行数据传送需求的PDU会话不一定在UE请求激活的PDU会话中。
-对恢复失败的UE的PDU会话和/或请求挂起的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起UE的PDU会话，删除UE的PDU会话，请求用户面功能删除UE的PDU会话。在一些实施方式中，继续挂起还是删除恢复失败的UE的PDU会话取决于恢复失败的原因。比如无线接入网侧资源不足导致的恢复失败可以继续挂起。比如是请求恢复的PDU会话是未知的PDU会话说明信息不一致，应该删除。
-对无线接入网侧恢复成功但既不是UE请求激活的PDU会话又没有下行数据传送需求的PDU会话，会话管理功能可以执行至少以下之一：挂起/释放PDU会话、请求用户面管理功能挂起/释放PDU会话、请求无线接入网挂起/释放PDU会话、请求UE挂起/释放PDU会话。
-对请求挂起的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起PDU会话。
-对请求释放的PDU会话信息，会话管理功能可以执行至少以下之一：释放PDU会话，请求用户面功能释放PDU会话。
步骤146：会话管理功能向接入移动管理功能发送恢复响应。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息、要求释放/挂起的PDU会话的信息。恢复成功的PDU会话信息可以指示核心网侧恢复成功的PDU会话的信息。要求释放/挂起的PDU会话的信息指示会话管理功能要求释放/恢复的PDU会话的信息。
步骤147：接入移动管理功能向无线接入网发送恢复响应。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息、要求释放/挂起的PDU会话的信息。恢复成功的PDU会话信息可以指示核心网侧恢复成功的PDU会话的信息。
-对恢复失败的PDU会话的信息，无线接入网可以执行以下之一：挂起PDU会话上下文、挂起PDU会话的映射的无线承载的上下文、释放承载资源、保存PDU会话的上行传输地址(即用户面功能为UE的PDU会话分配的传输地址)、将UE的PDU会话状态设置为挂起、请求UE挂起PDU会话、删除PDU会话上下文、请求UE删除PDU会话。
根据要求释放/挂起的PDU会话的信息，无线接入网可以执行以下之一：
-挂起/释放指定的PDU会话的上下文，
-挂起的UE的PDU会话映射的无线承载上下文，
-释放指定的PDU会话分配或映射无线承载，
-向UE发送要求释放/挂起的PDU会话的信息
可选的，步骤148：无线接入网向UE发送RRC重配置消息。可选的，消息中包括要求释放/挂起的PDU会话的信息。
UE根据收到的要求释放/挂起的PDU会话的信息进行指定PDU会话的挂起/释放。
第四示例
UE向无线接入网发送请求恢复的PDU会话信息，无线接入网将UE请 求恢复的PDU会话信息发送给核心网，核心网根据UE请求的PDU会话信息以及核心网自身请求恢复的PDU会话信息(即有下行传输需求的PDU会话)进行PDU会话恢复，并将核心网PDU会话恢复的结果通知无线接入网，无线接入网继而根据核心网对UE请求的PDU会话的恢复结果进行PDU会话恢复。如图15所示，该示例具体包括以下步骤：
步骤151：UE向无线接入网发送RRC恢复请求。可选的，在请求中可以指示至少以下之一：UE请求恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤152：无线接入网向接入移动管理功能发送恢复请求。
可选的，在请求中可以指示至少以下之一：UE请求恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
步骤153：接入移动管理功能向UE的PDU会话的会话管理功能发送恢复请求。
可选的，在请求中可以指示至少以下之一：UE请求恢复的PDU会话的信息。
此外，请求中可以指示至少以下之一：请求挂起的PDU会话信息、请求释放的PDU会话信息。
对不属于请求恢复的PDU会话，会话管理功能可以继续挂起或进行释放。
-对(1)UE请求恢复的PDU会话和(2)有下行数据传送需求的PDU会话中的至少一项，会话管理功能可以执行至少以下之一：恢复UE的PDU会话上下文，将UE的PDU会话的下行传输地址(即无线接入网为UE的PDU会话分配的传输地址)发送用户面功能，向用户面功能激活UE的PDU会话，将UE的PDU会话状态设置为激活。在一些实施方式中，由下行数据传送需求的PDU会话不一定在UE请求激活的PDU会话中。
-对请求挂起的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起UE的PDU会话。
-对请求释放的PDU会话信息，会话管理功能可以执行至少以下之一：删除UE的PDU会话，请求用户面功能删除UE的PDU会话。
步骤154：会话管理功能向接入移动管理功能发送恢复响应。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息、要求释放/挂起的PDU会话的信息。恢复成功的PDU会话信息指示会话管理功能在核心网侧恢复成功的PDU会话的信息。要求释放/挂起的PDU会话的信息指示会话管理功能要求释放/恢复的PDU会话的信息。
步骤155：接入移动管理功能向无线接入网发送恢复响应。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息、要求释放/挂起的PDU会话的信息。恢复成功的PDU会话信息指示会话管理功能在核心网侧恢复成功的PDU会话的信息。
对指示恢复成功的PDU会话，无线接入网进行PDU会话恢复操作，可以包括至少以下之一：
-恢复挂起的UE的PDU会话的上下文，
-恢复挂起的UEPDU会话映射的无线承载(如DRB)，
-为UE的PDU会话分配或映射无线承载(如DRB)，
-恢复无线接入网与核心网之间关于UE的连接。
-对恢复失败的PDU会话的信息，无线接入网可以执行以下之一：挂起PDU会话上下文、挂起PDU会话的映射的无线承载的上下文、释放承载资源、保存PDU会话的上行传输地址(即用户面功能为UE的PDU会话分配的传输地址)、将UE的PDU会话状态设置为挂起、请求UE挂起PDU会话、删除PDU会话上下文、请求UE删除PDU会话。
根据要求释放/挂起的PDU会话的信息，无线接入网可以执行以下之一：挂起/释放指定的PDU会话的上下文，挂起的UE的PDU会话映射的无线承载上下文，释放指定的PDU会话分配或映射无线承载，向UE发送要求释放/挂起的PDU会话的信息
在一些实施方式中，由于无线资源紧缺，不是每个UE请求的PDU会话都能够被分配无线资源。对核心网恢复成功但无线接入网恢复失败的PDU会话，无线接入网执行至少以下之一：请求核心网(比如接入移动管理功能、 会话管理功能和用户面功能等)释放/挂起核心网恢复成功但无线接入网恢复失败的PDU会话
步骤156：无线接入网向UE发送RRC恢复，可选的，在RRC恢复指示至少以下之一：确认恢复的PDU会话的信息。在一些实施方式中，确认恢复的PDU会话的信息包含的PDU会话是核心网恢复和无线接入网都恢复成功的PDU会话
UE根据指示的“确认恢复的PDU会话的信息”进行PDU会话恢复。
步骤157：UE向无线接入网发送RRC恢复完成。可选的，在RRC恢复完成中可以指示至少以下之一：UE恢复成功的PDU会话的信息、UE侧恢复失败的PDU会话的信息。
在一些实施方式中，由于不可预知的原因，有些PDU会话可能在UE侧恢复失败。对UE侧恢复失败的PDU会话，无线接入网可以执行以下之一：释放/挂起PDU会话，请求核心网释放/挂起PDU会话。
第五示例
该示例为恢复操作，PDU恢复的顺序仍然是无线接入网侧与UE先恢复PDU会话，核心网侧再根据UE和无线接入网的PDU会话恢复结果进行PDU会话的恢复，其优点是完成UE和无线接入网侧的PDU会话恢复后，UE即可发送上行数据。在该示例中，无线接入网尝试恢复UE挂起的所有PDU会话。如图16所示，该示例具体包括以下步骤：
步骤161：UE向无线接入网发送RRC恢复请求。
无线接入网进行PDU会话恢复操作，可以包括至少以下之一：
-恢复挂起的UE的PDU会话的上下文，
-恢复挂起的UEPDU会话映射的无线承载(如DRB)，
-为UE的PDU会话分配或映射无线承载(如DRB)，
-恢复无线接入网与核心网之间关于UE的连接。
在一些实施方式中，由于无线资源紧缺，不是每个UE请求的PDU会话都能够被分配无线资源。无线接入网可以优先恢复UE请求激活的PDU会话。另外，无线接入网可以将确认恢复的PDU会话的信息发送给UE。
步骤162：无线接入网向UE发送RRC恢复，可选的，在RRC恢复指示 至少以下之一：确认恢复的PDU会话的信息。在一些实施方式中，确认恢复的PDU会话信息可以是无线接入侧恢复成功的PDU会话。
UE根据指示的“确认恢复的PDU会话的信息”进行PDU会话恢复。
步骤163：UE向无线接入网发送RRC恢复完成。可选的，在RRC恢复完成中可以指示至少以下之一：UE恢复成功的PDU会话的信息、UE侧恢复失败的PDU会话的信息。
在一些实施方式中，由于不可预知的原因，有些PDU会话可能在UE侧恢复失败。对UE侧恢复失败的PDU会话，无线接入网可以执行以下之一：释放/挂起PDU会话，请求核心网释放/挂起PDU会话。
步骤164：无线接入网向接入移动管理功能发送恢复请求。
可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息指示无线接入网根据UE请求确认在UE和无线接入网上恢复的PDU会话的信息。
步骤165：接入移动管理功能向UE的PDU会话的会话管理功能发送恢复请求。
可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。
-对无线接入网侧恢复成功的PDU会话，会话管理功能可以执行至少以下之一：恢复UE的PDU会话上下文，将UE的PDU会话的下行传输地址(即无线接入网为UE的PDU会话分配的传输地址)发送用户面功能，向用户面功能激活UE的PDU会话，将UE的PDU会话状态设置为激活。在一些实施方式中，有下行数据传送需求的PDU会话不一定在UE请求激活的PDU会话中。
-对无线接入网侧恢复失败的UE的PDU会话，会话管理功能可以执行至少以下之一：继续挂起UE的PDU会话，删除UE的PDU会话，请求用户面功能删除UE的PDU会话。在一些实施方式中，继续挂起还是删除恢复失败的UE的PDU会话取决于恢复失败的原因。比如无线接入网侧资源不足导致的恢复失败可以继续挂起。比如是请求恢复的PDU会话是未知的PDU会话说明信息不一致，应该删除。
步骤166：会话管理功能向接入移动管理功能发送恢复响应。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息可以指示核心网侧恢复成功的PDU会话的信息。
步骤167：接入移动管理功能向无线接入网发送恢复响应。可选的，在请求中可以指示至少以下之一：恢复成功的PDU会话的信息、恢复失败的PDU会话的信息。恢复成功的PDU会话信息可以指示核心网侧恢复成功的PDU会话的信息。
-对恢复失败的PDU会话的信息，无线接入网可以执行以下之一：挂起PDU会话上下文、挂起PDU会话的映射的无线承载的上下文、释放承载资源、保存PDU会话的上行传输地址(即用户面功能为UE的PDU会话分配的传输地址)、将UE的PDU会话状态设置为挂起、请求UE挂起PDU会话、删除PDU会话上下文、请求UE删除PDU会话。
可选的，步骤168：无线接入网向UE发送RRC重配置消息。可选的，消息中包括要求释放/挂起的PDU会话的信息。
UE根据收到的要求释放/挂起的PDU会话的信息进行指定PDU会话的挂起/释放。
第六示例
在5G移动通信系统中，移动性管理和会话管理进一步拆分和重组，MME中的移动性管理功能归于AMF。MME中的会话管理功能与SGW和PGW中的会话管理功能整合成SMF，而SGW和PGW中的用户面功能整合成AMF。对用户面CIOT。由于AMF与UPF之间没有接口，如果仅仅在AMF上保持UE上下文，而释放SMF上的UE上下文，则无法支持UPF上关于UE会话的恢复。
该示例为PDU会话挂起流程。如图17所示，该示例包括以下步骤：
步骤171：无线接入网决定挂起UE，则向接入移动管理功能发送挂起请求。
步骤172：接入移动管理功能向UE的PDU会话的会话管理功能发送挂起请求。不同的UE的PDU会话的会话管理功能可能不同。
会话管理功能可以执行至少以下之一：保存UE的PDU会话上下文，保存UE的PDU会话的下行传输地址(即无线接入网为UE的PDU会话分配的传输地址)，向UPF发送PDU会话去激活，将UE的PDU会话状态设置为挂起。
步骤173：会话管理功能向接入移动管理功能发送挂起响应。
接入移动管理功能可以执行以下之一：保存UE的移动上下文，保存UE会话相关信息(PDU会话标识、PDU会话状态、会话管理功能的地址、切片信息)
步骤174：接入移动管理功能向无线接入网发送挂起响应。可选的，响应中可以包含至少以下之一：挂起成功UE的PDU会话的信息，挂起失败的UE的PDU会话的信息。
接入移动管理功能可以等到所有UE的PDU会话的会话管理功能返回挂起响应后向无线接入网发起挂起响应。
无线接入网可以执行以下之一：挂起UE的PDU会话上下文、挂起UE的PDU会话的映射的无线承载的上下文、释放承载资源、保存UE的PDU会话的上行传输地址(即用户面功能为UE的PDU会话分配的传输地址)、将UE的PDU会话状态设置为挂起、挂起无线接入网与核心网控制面(AMF，MME等)之间关于UE的连接。
在一些实施方式中，无线接入网仅仅对指定挂起成功的PDU会话执行挂起操作。
在另一些实施方式中，对挂起失败的PDU会话，无线接入网进行释放。
步骤175：无线接入网向UE发送RRC挂起或RRC释放消息。可选的，消息中可以包含至少以下之一：挂起UE的PDU会话的信息，删除的UE的PDU会话的信息。
UE底层(或者是AS层)可以执行挂起操作，包括至少以下之一：挂起UE的PDU会话上下文、挂起UE的PDU会话的映射的无线承载的上下文、释放承载资源、将UE的PDU会话状态设置为挂起、通知UE高层(或者是NAS层)挂起UE的PDU会话上下文、挂起无线接入网与核心网控制面(AMF，MME等)之间关于UE的连接。
在一些实施方式中，无线接入网仅对指定挂起的PDU会话执行挂起操作。
在另一些实施方式中，无线接入网对指定删除的PDU会话进行释放。
第七示例
对空闲态的终端时，核心网侧可能收到关于终端个别PDU会话的下行数据通知。对这些会话，需要进行恢复才能将数据传送给终端。但是寻呼消息中并没有这样的信息。则在终端服务请求时，并不知道还有下行的数据传送需求的PDU会话，则终端请求的激活的PDU会话就少了这部分PDU会话。同样，对采用了用户面CIOT的终端，如果处于空闲态，寻呼消息中没有下行的数据传送需求的PDU会话的信息，UE如果按需请求恢复PDU会话，也会缺少这部分PDU会话。
该示例为寻呼操作/通知操作，该示例适用于基于核心网请求恢复的PDU会话进行PDU会话处理的场景。如图18所示，该示例包括以下步骤：
步骤181：当核心网的用户面功能有下行数据需要传输时，确定请求恢复的PDU会话信息，核心网的用户面功能向SMF发送下行数据通知。
步骤182：SMF将该下行数据通知发送至AMF。
步骤183a：AMF向无线接入网发送寻呼消息或通知消息，其中，该寻呼消息中携带有核心网请求恢复的PDU会话信息。
步骤184：无线接入网将该寻呼消息转发至终端。
步骤183b：AMF向UE通知消息。其中，该通知消息中可以携带有核心网请求恢复的PDU会话信息。一种实施方式中，虽然UE在3GPP接入网内处于空闲态，但UE在非3GPP接入网处于连接态。所以通过3GPP接入网将包含后核心网请求恢复的PDU会话信息的通知消息发送给UE。
步骤185a：终端在接收到寻呼消息后，启动PDU会话恢复流程，向核心网发送服务请求消息。其中，该消息中可以携带有核心网请求恢复的PDU会话信息。
或步骤185b：终端在接收到寻呼消息后，启动PDU会话恢复流程，向无线接入网发送RRC恢复请求消息。其中，该消息中可以携带有核心网请求恢复的PDU会话信息。
其中，值得指出的是，本公开的一些实施例中所涉及到的获取可以是接 收到、配置得到或自行知道的。在一些实施方式中，数据传输需求的PDU会话可以是有下行数据传送需求的PDU会话、或接收到下行数据通知的PDU会话等。有数据传输需求的PDU会话不一定包含在请求恢复的PDU会话信息中。因为UE在发送请求恢复的PDU会话的信息时并不知道网络设备存在下行数据传输的PDU会话。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本公开方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术 方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
此外，需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行，某些步骤可以并行或彼此独立地执行。对本领域的普通技术人员而言，能够理解本公开的方法和装置的全部或者任何步骤或者部件，可以在任何计算装置(包括处理器、存储介质等)或者计算装置的网络中，以硬件、固件、软件或者它们的组合加以实现，这是本领域普通技术人员在阅读了本公开的说明的情况下运用他们的基本编程技能就能实现的。
因此，本公开的目的还可以通过在任何计算装置上运行一个程序或者一组程序来实现。计算装置可以是公知的通用装置。因此，本公开的目的也可以仅仅通过提供包含实现方法或者装置的程序代码的程序产品来实现。也就是说，这样的程序产品也构成本公开，并且存储有这样的程序产品的存储介质也构成本公开。显然，存储介质可以是任何公知的存储介质或者将来所开发出来的任何存储介质。还需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行。某些步骤可以并行或彼此独立地执行。
以上的是本公开的可选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (53)

  1. 一种会话控制方法，应用于第一网络单元侧，包括：
    获取分组数据单元PDU会话信息的操作请求信息；所述操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息和终端请求挂起的PDU会话信息；
    根据所述操作请求信息，进行PDU会话处理。
  2. 根据权利要求1所述的会话控制方法，其中，所述根据所述操作请求信息，进行PDU会话处理的步骤，包括以下至少一项：
    当所述操作请求信息为终端请求恢复的PDU会话信息时，执行以下至少一项：对所述终端请求恢复的PDU会话进行恢复操作；对所述终端挂起的所有PDU会话进行恢复操作；以及对所述终端挂起的所有PDU会话进行恢复操作且在资源不足时，优先对所述终端请求恢复的PDU会话进行恢复操作；
    当所述操作请求信息为终端请求释放的PDU会话信息时，对所述终端请求释放的PDU会话进行释放操作；
    当所述操作请求信息为终端请求挂起的PDU会话信息时，对所述终端请求挂起的PDU会话进行挂起操作。
  3. 根据权利要求2所述的会话控制方法，其中，对PDU会话进行恢复操作的步骤，包括：
    对PDU会话执行以下操作中的至少一项：
    恢复PDU会话的上下文；
    恢复PDU会话对应的无线承载；
    为PDU会话的QoS流分配和/或映射无线承载资源；
    恢复所述第一网络单元与第二网络单元之间关于所述终端的连接。
  4. 根据权利要求2所述的会话控制方法，其中，所述根据所述操作请求信息，进行PDU会话处理的步骤，还包括以下至少一项：
    向所述终端发送确认恢复和/或确认不能恢复的PDU会话信息；
    以及，
    向所述第二网络单元发送所述第一网络单元的PDU会话恢复结果信息； 其中，所述第一网络单元的PDU会话恢复结果信息包括以下信息中的至少一项：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息。
  5. 根据权利要求4所述的会话控制方法，包括以下至少一项：
    所述恢复成功的PDU会话信息用于指示所述终端和所述第一网络单元均恢复成功的PDU会话；
    所述恢复失败的PDU会话信息用于指示所述终端或所述第一网络单元恢复失败的PDU会话；
    所述请求释放的PDU会话信息用于指示所述终端恢复失败的PDU会话、所述第一网络单元恢复失败的PDU会话以及所述终端请求释放的PDU会话中的至少一项；
    所述请求挂起的PDU会话信息用于指示所述终端恢复失败的PDU会话、所述第一网络单元恢复失败的PDU会话以及所述终端请求挂起的PDU会话中的至少一项；
    所述确认恢复的PDU会话信息用于指示存在PDU会话上下文的PDU会话、能够分配或映射无线承载资源的PDU会话、第一网络单元和第二网络单元都确认能够恢复的PDU会话中的至少一项；
    所述确认不能恢复的PDU会话包括：不存在PDU会话上下文的PDU会话、不能够分配或映射无线承载资源的PDU会话、第一网络单元确认不能恢复的PDU会话、第二网络单元确认不能恢复的PDU会话中的至少一项。
  6. 根据权利要求4所述的会话控制方法，其中，所述向所述终端发送确认恢复和/或确认不能恢复的PDU会话信息的步骤之后，所述方法还包括：
    接收所述终端反馈的所述终端的PDU恢复结果信息；其中，所述终端的PDU恢复结果信息包括：所述终端恢复成功的PDU会话信息和所述终端恢复失败的PDU会话信息中的至少一项。
  7. 根据权利要求4所述的会话控制方法，其中，所述向所述第二网络单元发送所述第一网络单元的PDU会话恢复结果信息的步骤，包括：
    向第二网络单元发送携带有所述第一网络单元的PDU会话恢复结果信息的会话操作请求；
    接收所述第二网络单元根据所述会话操作请求返回的第二网络单元的PDU会话恢复结果信息。
  8. 根据权利要求7所述的会话控制方法，其中，所述接收所述第二网络单元根据所述会话操作请求返回的第二网络单元的PDU会话恢复结果信息的步骤之后，还包括：
    根据所述第二网络单元的PDU会话恢复结果信息，对所述终端的PDU会话进行处理。
  9. 根据权利要求1所述的会话控制方法，其中，所述根据所述操作请求信息，进行PDU会话处理的步骤，包括：
    当所述操作请求信息包括终端请求恢复的PDU会话信息时，向所述第二网络单元发送所述终端请求恢复的PDU会话信息。
  10. 根据权利要求9所述的会话控制方法，其中，所述向所述第二网络单元发送所述终端请求恢复的PDU会话信息的步骤之后，所述方法还包括：
    接收所述第二网络单元根据所述终端请求恢复的PDU会话信息反馈的第二网络单元的PDU会话恢复结果信息；
    根据所述第二网络单元的PDU会话恢复结果信息，对所述终端的PDU会话进行处理。
  11. 根据权利要求8或10所述的会话控制方法，其中，所述第二网络单元的PDU会话恢复结果信息包括以下信息中的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息和第二网络单元请求挂起的PDU会话信息。
  12. 根据权利要求11所述的会话控制方法，其中，根据所述第二网络单元的PDU会话恢复结果信息，对所述终端的PDU会话进行处理的步骤，包括：
    若所述第二网络单元的PDU会话恢复结果信息为第二网络单元恢复成功的PDU会话信息，在检测到第二网络单元恢复成功的PDU会话无法在第一网络单元或终端侧恢复时，向所述第二网络单元发送请求释放或挂起该PDU会话的请求信息；
    若所述第二网络单元的PDU会话恢复结果信息为第二网络单元恢复失败的PDU会话信息，对所述第二网络单元恢复失败的PDU会话执行以下操作中的至少一项：
    挂起所述第二网络单元恢复失败的PDU会话上下文、
    挂起所述第二网络单元恢复失败的PDU会话对应的无线承载的上下文、
    释放所述第二网络单元恢复失败的PDU会话对应的承载资源、
    保存所述第二网络单元恢复失败的PDU会话的上行传输地址、
    将所述第二网络单元恢复失败的PDU会话状态设置为挂起、
    请求终端挂起所述第二网络单元恢复失败的PDU会话、
    请求终端删除所述第二网络单元恢复失败的PDU会话上下文、
    请求终端删除所述第二网络单元恢复失败的PDU会话；
    若所述第二网络单元的PDU会话恢复结果信息为第二网络单元请求恢复的PDU会话信息，对所述第二网络单元请求恢复的PDU会话执行以下操作中的至少一项：
    恢复第二网络单元请求恢复的PDU会话的上下文、
    恢复第二网络单元请求恢复的PDU会话对应的无线承载、
    为第二网络单元请求恢复的PDU会话分配或映射无线承载资源、
    恢复与第二网络单元之间关于所述终端的连接；
    若所述第二网络单元的PDU会话恢复结果信息为第二网络单元请求释放的PDU会话信息，对第二网络单元请求释放的PDU会话执行以下操作中的至少一项：
    释放第二网络单元请求释放的PDU会话的上下文、
    释放第二网络单元请求释放的PDU会话对应的无线承载上下文、
    释放第二网络单元请求释放的PDU会话对应的无线承载资源、
    向终端发送第二网络单元请求释放的PDU会话信息；
    若所述第二网络单元的PDU会话恢复结果信息为第二网络单元请求挂起的PDU会话信息，对第二网络单元请求挂起的PDU会话执行以下操作中的至少一项：
    挂起第二网络单元请求挂起的PDU会话的上下文、
    挂起第二网络单元请求挂起的PDU会话对应的无线承载上下文、
    释放第二网络单元请求挂起的PDU会话对应的无线承载资源、
    向终端发送第二网络单元请求挂起的PDU会话信息。
  13. 根据权利要求1至12中任一项所述的会话控制方法，其中，所述PDU会话信息包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
  14. 根据权利要求1至13中任一项所述的会话控制方法，其中，所述第一网络单元是无线接入网设备；
    所述获取分组数据单元PDU会话信息的操作请求信息，包括：
    接收所述终端向所述无线接入网设备发送的无线资源控制RRC恢复请求，其中所述RRC恢复请求中包含所述操作请求信息。
  15. 一种网络设备，应用于第一网络单元侧，包括：
    第一获取模块，用于获取分组数据单元PDU会话信息的操作请求信息；所述操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息和终端请求挂起的PDU会话信息；
    第一处理模块，用于根据所述操作请求信息，进行PDU会话处理。
  16. 根据权利要求15所述的网络设备，其中，所述第一处理模块包括以下至少一项：
    第一处理子模块，用于当所述操作请求信息为终端请求恢复的PDU会话信息时，执行以下至少一项：对所述终端请求恢复的PDU会话进行恢复操作；对所述终端挂起的所有PDU会话进行恢复操作；以及对所述终端挂起的所有PDU会话进行恢复操作且在资源不足时，优先对所述终端请求恢复的PDU会话进行恢复操作；
    第二处理子模块，用于当所述操作请求信息为终端请求释放的PDU会话信息时，对所述终端请求释放的PDU会话进行释放操作；
    第三处理子模块，用于当所述操作请求信息为终端请求挂起的PDU会话信息时，对所述终端请求挂起的PDU会话进行挂起操作。
  17. 根据权利要求16所述的网络设备，其中，所述第一处理模块还包括 以下至少一项：
    第一发送子模块，用于向所述终端发送确认恢复和/或确认不能恢复的PDU会话信息；
    以及，
    第二发送子模块，用于向所述第二网络单元发送所述第一网络单元的PDU会话恢复结果信息；其中，所述第一网络单元的PDU会话恢复结果信息包括以下信息中的至少一项：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息。
  18. 根据权利要求17所述的网络设备，其中，所述第一处理模块还包括：
    第一接收子模块，用于接收所述终端反馈的所述终端的PDU恢复结果信息；其中，所述终端的PDU恢复结果信息包括：所述终端恢复成功的PDU会话信息和所述终端恢复失败的PDU会话信息中的至少一项。
  19. 根据权利要求15所述的网络设备，其中，所述第一处理模块还包括：
    第四处理子模块，用于当所述操作请求信息包括终端请求恢复的PDU会话信息时，向所述第二网络单元发送所述终端请求恢复的PDU会话信息。
  20. 根据权利要求15所述的网络设备，其中，所述网络设备是无线接入网设备，所述第一获取模块进一步配置为：
    接收所述终端向所述无线接入网设备发送的无线资源控制RRC恢复请求，其中所述RRC恢复请求中包含所述操作请求信息。
  21. 一种会话控制方法，应用于第一网络单元侧，包括：
    获取分组数据单元PDU会话信息的操作请求信息；所述操作请求信息包括以下信息中的至少一项：第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息；
    根据所述操作请求信息，进行PDU会话处理。
  22. 根据权利要求21所述的会话控制方法，其中，所述根据所述操作请求信息，进行PDU会话处理的步骤，包括以下至少一项：
    当所述操作请求信息为第二网络单元请求恢复的PDU会话信息时，对所述第二网络单元请求恢复的PDU会话进行恢复操作；
    当所述操作请求信息为第二网络单元请求释放的PDU会话信息时，对所 述第二网络单元请求释放的PDU会话进行释放操作；
    当所述操作请求信息为第二网络单元请求挂起的PDU会话信息时，对所述第二网络单元请求挂起的PDU会话进行挂起操作。
  23. 根据权利要求21或22所述的会话控制方法，其中，所述根据所述操作请求信息，进行PDU会话处理的步骤，还包括：
    向所述终端发送所述操作请求信息。
  24. 根据权利要求23所述的会话控制方法，其中，所述获取分组数据单元PDU会话信息的操作请求信息的步骤包括：
    接收第二网络单元发送的寻呼消息或通知消息；
    所述向所述终端发送所述操作请求信息的步骤，包括：
    向终端发送接收的寻呼消息或通知消息；
    其中，所述寻呼消息或通知消息中携带有指示所述第二网络单元请求恢复的PDU会话的信息、所述第二网络单元请求释放PDU会话信息、所述第二网络单元请求挂起的PDU会话信息中至少一项。
  25. 一种网络设备，应用于第一网络单元侧，包括：
    第二获取模块，用于获取分组数据单元PDU会话信息的操作请求信息；所述操作请求信息包括以下信息中的至少一项：第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放PDU会话信息、第二网络单元请求挂起的PDU会话信息；
    第二处理模块，用于根据所述操作请求信息，进行PDU会话处理。
  26. 根据权利要求25所述的网络设备，其中，所述第二处理模块包括以下至少一项：
    第五处理子模块，用于当所述操作请求信息为第二网络单元请求恢复的PDU会话信息时，对所述第二网络单元请求恢复的PDU会话进行恢复操作；
    第六处理子模块，用于当所述操作请求信息为第二网络单元请求释放的PDU会话信息时，对所述第二网络单元请求释放的PDU会话进行释放操作；
    第七处理子模块，用于当所述操作请求信息为第二网络单元请求挂起的PDU会话信息时，对所述第二网络单元请求挂起的PDU会话进行挂起操作。
  27. 根据权利要求25或26所述的网络设备，其中，所述第二处理模块 还包括：
    第三发送子模块，用于向所述终端发送所述操作请求信息。
  28. 一种会话控制方法，应用于第二网络单元侧，包括：
    获取分组数据单元PDU会话信息的操作请求信息；所述操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息；
    根据所述操作请求信息，进行PDU会话处理。
  29. 根据权利要求28所述的会话控制方法，包括以下至少一项：
    所述第一网络单元的PDU会话恢复结果信息包括：恢复成功的PDU会话信息、恢复失败的PDU会话信息、请求释放的PDU会话信息和请求挂起的PDU会话信息中的至少一项；
    所述终端请求恢复的PDU会话信息是所述第一网络单元转发的或所述终端发送的所述终端请求恢复的PDU会话信息；
    所述终端请求释放的PDU会话信息是所述第一网络单元转发的或所述终端发送的所述终端请求释放的PDU会话信息；
    所述终端请求挂起的PDU会话信息是所述第一网络单元转发的或所述终端发送的所述终端请求恢复的PDU会话信息。
  30. 根据权利要求28或29所述的会话控制方法，其中，所述根据所述操作请求信息，进行PDU会话处理的步骤，包括至少以下一项：
    对需要进行恢复操作的PDU会话，执行以下操作中的至少一项：
    恢复相应PDU会话的上下文、
    将相应PDU会话的下行传输地址发送至用户面功能实体，向用户面功能实体激活相应的PDU会话；
    对所述终端请求释放的PDU会话信息指示的PDU会话和第一网络单元请求释放PDU会话信息指示的PDU会话中的至少一项，执行以下操作：释放所述终端和/或第二网络单元请求释放的PDU会话；
    对所述终端请求挂起的PDU会话信息指示的PDU会话和第一网络单元请求挂起PDU会话信息指示的PDU会话中的至少一项，执行以下操作：挂起所述终端和/或第二网络单元请求释放的PDU会话；
    对所述第一网络单元的PDU会话恢复结果信息指示的恢复失败的PDU会话，执行以下操作中的至少一项：
    挂起恢复失败的PDU会话的上下文、
    删除恢复失败的PDU会话的上下文、
    请求用户面功能实体删除恢复失败的PDU会话；
    其中，所述需要进行恢复操作的PDU会话包括：所述第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话、所述终端请求恢复的PDU会话信息指示的PDU会话、第三网络单元请求恢复的PDU会话信息指示的PDU会话、有下行数据传输需求的PDU会话信息指示的PDU会话、收到下行数据通知的PDU会话信息指示的PDU会话、所述第一网络单元的PDU会话恢复结果信息指示恢复成功且第三网络单元请求恢复的PDU会话、所述第一网络单元的PDU会话恢复结果信息指示恢复成功且有下行数据传输需求的PDU会话信息指示的PDU会话、所述第一网络单元的PDU会话恢复结果信息指示恢复成功且收到下行数据通知的PDU会话信息指示的PDU会话，以及所述终端请求恢复的且所述第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话中的至少一项。
  31. 根据权利要求28所述的会话控制方法，其中，所述根据所述操作请求信息，进行PDU会话处理的步骤之后，所述方法还包括：
    生成第二网络单元的PDU会话恢复结果信息；其中，所述第二网络单元的PDU会话恢复结果信息包括以下信息中的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息、第二网络单元请求挂起的PDU会话信息；
    将所述第二网络单元的PDU会话恢复结果信息发送至所述第一网络单元和/或通过第一网络单元发送给所述终端。
  32. 根据权利要求31所述的会话控制方法，其中，
    第二网络请求恢复的PDU会话信息包含：下行数据传送需求的PDU会话信息、收到下行数据通知的PDU会话和第三网络单元请求恢复的PDU会话中的至少一项；和/或
    第二网络请求挂起的PDU会话信息包含：第二网络恢复失败的PDU会话、第一网络单元恢复成功但第二网络恢复失败的PDU会话、以及第一网络单元和终端恢复成功但第二网络恢复失败的PDU会话中的至少一项；和/或
    第二网络请求释放的PDU会话信息包含：第二网络恢复失败的PDU会话、第一网络单元恢复成功但第二网络恢复失败的PDU会话、以及第一网络单元和终端恢复成功但第二网络恢复失败的PDU会话中的至少一项。
  33. 根据权利要求28所述的会话控制方法，其中，根据所述操作请求信息，进行PDU会话处理，包括：
    当所述操作请求信息为第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项时，通过寻呼请求或通知消息，向所述第一网络单元发送所述第三网络单元请求恢复的PDU会话信息第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项。
  34. 根据权利要求28至33中任一项所述的会话控制方法，其中，所述PDU会话信息包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
  35. 一种网络设备，应用于第二网络单元侧，包括：
    第三获取模块，用于获取分组数据单元PDU会话信息的操作请求信息；所述操作请求信息包括以下信息中的至少一项：终端请求恢复的PDU会话信息、终端请求释放的PDU会话信息、终端请求挂起的PDU会话信息、第一网络单元的PDU会话恢复结果信息、第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU 会话信息；
    第三处理模块，用于根据所述操作请求信息，进行PDU会话处理。
  36. 根据权利要求35所述的网络设备，其中，所述第三处理模块包括至少以下一项：
    第八处理子模块，用于对需要进行恢复操作的PDU会话，执行以下操作中的至少一项：
    恢复相应PDU会话的上下文、
    将相应PDU会话的下行传输地址发送至用户面功能实体，向用户面功能实体激活相应的PDU会话；
    第九处理子模块，用于对所述终端请求释放的PDU会话信息指示的PDU会话和第一网络单元请求释放PDU会话信息指示的PDU会话中的至少一项，执行以下操作：释放所述终端和/或第二网络单元请求释放的PDU会话；
    第十处理子模块，用于对所述终端请求挂起的PDU会话信息指示的PDU会话和第一网络单元请求挂起PDU会话信息指示的PDU会话中的至少一项，执行以下操作：挂起所述终端和/或第二网络单元请求释放的PDU会话；
    第十一处理子模块，用于对所述第一网络单元的PDU会话恢复结果信息指示的恢复失败的PDU会话，执行以下操作中的至少一项：
    挂起恢复失败的PDU会话的上下文、
    删除恢复失败的PDU会话的上下文、
    请求用户面功能实体删除恢复失败的PDU会话；
    其中，所述需要进行恢复操作的PDU会话包括：所述第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话、所述终端请求恢复的PDU会话信息指示的PDU会话、第三网络单元请求恢复的PDU会话信息指示的PDU会话、有下行数据传输需求的PDU会话信息指示的PDU会话、收到下行数据通知的PDU会话信息指示的PDU会话、所述第一网络单元的PDU会话恢复结果信息指示恢复成功且第三网络单元请求恢复的PDU会话、所述第一网络单元的PDU会话恢复结果信息指示恢复成功且有下行数据传输需求的PDU会话信息指示的PDU会话、所述第一网络单元的PDU会话恢复结果信息指示恢复成功且收到下行数据通知的PDU会话信息指示的PDU会话、 和所述终端请求恢复的且所述第一网络单元的PDU会话恢复结果信息指示恢复成功的PDU会话中的至少一项。
  37. 根据权利要求35所述的网络设备，还包括：
    第一生成模块，用于生成第二网络单元的PDU会话恢复结果信息；其中，所述第二网络单元的PDU会话恢复结果信息包括以下信息中的至少一项：第二网络单元恢复成功的PDU会话信息、第二网络单元恢复失败的PDU会话信息、第二网络单元请求恢复的PDU会话信息、第二网络单元请求释放的PDU会话信息、第二网络单元请求挂起的PDU会话信息；
    第二发送模块，用于将所述第二网络单元的PDU会话恢复结果信息发送至所述第一网络单元和/或通过第一网络单元发送给所述终端。
  38. 根据权利要求35所述的网络设备，其中，所述第三处理模块还包括：
    第十二处理子模块，用于当所述操作请求信息为第三网络单元请求恢复的PDU会话信息、第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项时，通过寻呼请求或通知消息，向所述第一网络单元发送所述第三网络单元请求恢复的PDU会话信息第三网络单元请求释放PDU会话信息、第三网络单元请求挂起的PDU会话信息、有下行数据传输需求的PDU会话信息和收到下行数据通知的PDU会话信息中的至少一项。
  39. 一种会话控制方法，应用于终端侧，包括：
    向第一网络单元发送分组数据单元PDU会话信息的操作请求信息；
    接收所述第一网络单元根据所述操作请求信息发送的PDU会话操作响应信息；
    根据所述PDU会话操作响应信息，进行PDU会话处理。
  40. 根据权利要求39所述的会话控制方法，其中，所述操作请求信息包括至少以下之一：
    终端自身请求的PDU会话信息、第一网络请求恢复的PDU会话信息、第二网络请求恢复的PDU会话信息。
  41. 根据权利要求39所述的会话控制方法，其中，在向第一网络单元发 送分组数据单元PDU会话信息的操作请求信息的步骤之前，还包括至少以下之一：
    生成请求恢复的PDU会话信息；
    接收第一网络单元发送的请求恢复的PDU会话信息；
    通过第一网络单元接收第二网络单元发送的请求恢复的PDU会话信息。
  42. 根据权利要求39所述的会话控制方法，其中，所述PDU会话操作响应信息包括：确认恢复和/或确认不能恢复的PDU会话信息；
    根据所述PDU会话操作响应信息，进行PDU会话处理的步骤，包括：
    根据所述确认恢复和/或确认不能恢复的PDU会话的信息，对PDU会话进行处理。
  43. 根据权利要求42所述的会话控制方法，其中，根据所述确认恢复和/或确认不能恢复的PDU会话的信息，对PDU会话进行处理的步骤，包括至少以下之一：
    根据所述确认恢复的PDU会话的信息，恢复确认恢复的PDU会话；
    根据确认不能恢复的PDU会话的信息，释放或挂起不能恢复的PDU会话。
  44. 根据权利要求42所述的会话控制方法，其中，根据所述确认恢复和/或确认不能恢复的PDU会话的信息，对PDU会话进行处理的步骤之后，所述方法包括：
    生成PDU会话处理后的终端的PDU会话恢复结果信息并反馈至所述第一网络单元；其中，所述终端的PDU恢复结果信息包括以下信息中的至少一项：所述终端恢复成功的PDU会话信息、所述终端恢复失败的PDU会话信息、所述终端释放成功的PDU会话信息和所述终端挂起的PDU会话信息。
  45. 根据权利要求39至44任一项所述的会话控制方法，其中，所述PDU会话信息包括以下信息中的至少一项：PDU会话标识信息、恢复指示信息、恢复指示信息、挂起指示信息、释放指示信息、PDU会话标识比特地图信息和PDU会话中QoS流信息。
  46. 根据权利要求39所述的会话控制方法，其中，所述第一网络单元是无线接入网设备；
    所述向所述第一网络单元发送分组数据单元PDU会话信息的操作请求信息，包括：
    向所述无线接入网设备发送的无线资源控制RRC恢复请求，其中所述RRC恢复请求中包含所述操作请求信息。
  47. 一种终端，包括：
    第三发送模块，用于向第一网络单元发送分组数据单元PDU会话信息的操作请求信息；
    第二接收模块，用于接收所述第一网络单元根据所述操作请求信息发送的第一网络单元的PDU会话恢复结果信息；
    第四处理模块，用于根据所述第一网络单元的PDU会话恢复结果信息，对PDU会话进行处理。
  48. 根据权利要求47所述的终端，其中，所述终端还包括至少以下之一：
    第二生成模块，用于生成请求恢复的PDU会话信息；
    第三接收模块，用于接收第一网络单元发送的请求恢复的PDU会话信息；
    第四发送模块，用于通过第一网络单元接收第二网络单元发送的请求恢复的PDU会话信息。
  49. 根据权利要求47所述的终端，其中，第一网络单元的PDU会话恢复结果信息包括：确认恢复和/或确认不能恢复的PDU会话信息；
    所述第四处理模块包括：
    第十三处理子模块，用于根据所述确认恢复和/或确认不能恢复的PDU会话的信息，对PDU会话进行处理。
  50. 根据权利要求47所述的终端，其中，所述第四处理模块还包括：
    反馈子模块，用于生成PDU会话处理后的终端的PDU会话恢复结果信息并反馈至所述第一网络单元；其中，所述终端的PDU恢复结果信息包括以下信息中的至少一项：所述终端恢复成功的PDU会话信息、所述终端恢复失败的PDU会话信息、所述终端释放成功的PDU会话信息和所述终端挂起的PDU会话信息。
  51. 一种网络设备，包括：
    处理器、存储器以及存储于所述存储器上并可在所述处理器上运行的计 算机程序，所述处理器执行所述计算机程序时实现如权利要求1至14、21至24、28至34中任一项所述的会话控制方法的步骤。
  52. 一种终端，包括：
    处理器、存储器以及存储于所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求39至46中任一项所述的会话控制方法的步骤。
  53. 一种计算机可读存储介质，包括：
    所述计算机可读存储介质上存储的计算机程序，所述计算机程序被处理器执行时所述处理器实现如权利要求1至14、21至24、28至34、39至46中任一项所述的会话控制方法的步骤。
PCT/CN2019/070215 2018-01-04 2019-01-03 会话控制方法、网络设备及终端 Ceased WO2019134657A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810009027.5A CN110012553B (zh) 2018-01-04 2018-01-04 会话控制方法、网络设备及终端
CN201810009027.5 2018-01-04

Publications (1)

Publication Number Publication Date
WO2019134657A1 true WO2019134657A1 (zh) 2019-07-11

Family

ID=67144416

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/070215 Ceased WO2019134657A1 (zh) 2018-01-04 2019-01-03 会话控制方法、网络设备及终端

Country Status (2)

Country Link
CN (1) CN110012553B (zh)
WO (1) WO2019134657A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12471171B2 (en) 2019-07-15 2025-11-11 Qualcomm Incorporated RRC layer based suspend and resume for multi-SIM UE
CN110474969B (zh) 2019-07-29 2021-07-16 华为技术有限公司 会话管理方法及装置
CN116489721B (zh) * 2022-01-14 2026-02-13 北京小米移动软件有限公司 通话方法及装置、存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017116115A1 (ko) * 2015-12-29 2017-07-06 엘지전자 주식회사 사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치
CN106961748A (zh) * 2016-01-08 2017-07-18 北京三星通信技术研究有限公司 控制ue上下文和ue连接的方法和设备
CN107046735A (zh) * 2016-02-05 2017-08-15 中兴通讯股份有限公司 终端与网络间连接处理方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105636207A (zh) * 2014-10-28 2016-06-01 电信科学技术研究院 一种传输上行数据的方法和设备
CN106686749A (zh) * 2015-11-06 2017-05-17 电信科学技术研究院 一种rrc连接建立及其控制方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017116115A1 (ko) * 2015-12-29 2017-07-06 엘지전자 주식회사 사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치
CN106961748A (zh) * 2016-01-08 2017-07-18 北京三星通信技术研究有限公司 控制ue上下文和ue连接的方法和设备
CN107046735A (zh) * 2016-02-05 2017-08-15 中兴通讯股份有限公司 终端与网络间连接处理方法和装置

Also Published As

Publication number Publication date
CN110012553B (zh) 2021-04-20
CN110012553A (zh) 2019-07-12

Similar Documents

Publication Publication Date Title
US11617219B2 (en) Bearer configuration method for RRC connection reestablishment, terminal, and network device
WO2020088584A1 (zh) 副链路释放方法、终端及网络侧设备
CN113543313B (zh) 寻呼响应方法、终端及网络设备
WO2020063442A1 (zh) 双连接切换方法、终端及网络设备
WO2019137276A1 (zh) 通信业务过程冲突的处理方法及终端
CN111130722A (zh) 一种承载的控制方法、终端及网络侧设备
CN112770409B (zh) 无线链路失败处理方法及装置
CN110719628A (zh) 传输方法、终端设备及网络设备
WO2020063263A1 (zh) 旁链路的链路释放方法及终端
JP2022517240A (ja) 接続確立方法、端末機器及びネットワーク機器
CN109548097B (zh) 一种承载建立方法及装置
CN111278061A (zh) 数据处理方法、信息配置方法、终端及网络设备
CN111277998A (zh) 一种无线通信方法及终端设备
CN111132203A (zh) 一种处理方法及终端
WO2019134657A1 (zh) 会话控制方法、网络设备及终端
CN111263412A (zh) 一种信息传输方法、设备及系统
CN109587704B (zh) 信息传输方法、终端、网络设备及计算机可读存储介质
CN113596737B (zh) 数据重传方法、装置、目标节点、源节点及终端
CN111836379B (zh) 辅助信息上报方法、配置方法、终端和网络侧设备
WO2019137425A1 (zh) 重配置方法、终端及基站
CN110972212B (zh) 一种PC5接口的QoS参数配置方法、设备及系统
CN111182590B (zh) 一种小区切换方法、终端和通信节点
WO2022152017A1 (zh) 信息传输方法、终端及网络设备
CN110621034A (zh) 一种传输控制方法、装置及系统
CN110620640B (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: 19735921

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19735921

Country of ref document: EP

Kind code of ref document: A1