CN117336896A - Session management method and device, equipment and storage medium - Google Patents

Abstract

The application discloses a session management method and device, equipment and a storage medium; wherein the method comprises the following steps: starting a timer for the established first connection; the timer is set to a first duration, and the first connection is used for transmitting PDU data packets; transmitting first signaling to a network device, the first signaling being for requesting release of the first connection, based on determining that an amount of data transmitted over the first connection for the first duration is less than or equal to a first threshold; therefore, the PDU session which is not needed to be used can be released in time, so that the slice blockage is reduced, and the new communication energy is improved.

Description

Session management method and device, equipment and storage medium

Technical field

This application relates to communication technology, including but not limited to session management methods and devices, equipment, and storage media.

Background technique

In a mobile communication network, a Protocol Data Unit (PDU) session can be understood as a connection between a terminal and an external network access point gateway. Taking 5G technology as an example, a PDU session is represented by an Internet Protocol (IP) address and a Data Network Name (DNN) assigned to the terminal. The terminal can transmit data through PDU sessions in the 5G mobile communication network.

In the current solution used in the existing network, one or more PDU sessions are usually configured for the terminal. With the introduction of slicing function in the 5G network, there is a corresponding relationship between PDU sessions and slices. Different application services sign up for different slices, and the terminal will be Different slices establish corresponding PDU sessions. However, slice congestion may be caused during data transmission through PDU sessions.

Contents of the invention

In view of this, the session management method, device, equipment, and storage medium provided by this application can release unused PDU sessions in a timely manner, thereby reducing slice congestion and improving new communication performance.

According to an aspect of an embodiment of the present application, a session management method is provided, applied to a terminal device, including: starting a timer for the first connection established; wherein the timer is set to a first duration, and the first connection for transmitting PDU data packets; and, based on determining that the amount of data transmitted on the first connection of the first duration is less than or equal to a first threshold, sending first signaling to the network device, the first signaling using Request to release the first connection.

According to an aspect of an embodiment of the present application, a session management method is provided, applied to a network device, including: receiving a first signaling sent by a terminal device, the first signaling being used to request the release of a session established with the terminal device. The first connection, the first connection is used to transmit PDU data packets; the first connection is released; wherein the first signaling is during the first duration of the timer. The amount of data transmitted on the first connection is less than or equal to the first threshold, and the timer is set for the first connection.

According to an aspect of an embodiment of the present application, a session management device is provided, including: a starting module for starting a timer for the established first connection; wherein the timer is set to a first duration, and the first connection used to transmit PDU data packets; a sending module configured to send first signaling to the network device based on determining that the amount of data transmitted on the first connection of the first duration is less than or equal to a first threshold, the first The signaling is used to request release of the first connection.

According to an aspect of an embodiment of the present application, a session management device is provided, including: a receiving module configured to receive a first signaling sent by a terminal device, where the first signaling is used to request the release of a session established with the terminal device. The first connection, the first connection is used to transmit PDU data packets; the release module is used to release the first connection; wherein the first signaling is on the first connection during the first duration of the timer It is sent when the amount of transmitted data is less than or equal to the first threshold, and the timer is set for the first connection.

The terminal device provided by the embodiment of the present application includes a memory and a processor. The memory stores a computer program that can be run on the processor. When the processor executes the program, the method described in the embodiment of the present application is implemented.

The network device provided by the embodiment of the present application includes a memory and a processor. The memory stores a computer program that can be run on the processor. When the processor executes the program, the method described in the embodiment of the present application is implemented.

The computer-readable storage medium provided by the embodiment of the present application has a computer program stored thereon, and when the computer program is executed by the processor, the method provided by the embodiment of the present application is implemented.

It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and do not limit the present application.

Description of drawings

The accompanying drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application, and together with the description, are used to explain the technical solutions of the present application. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

The flowcharts shown in the drawings are only illustrative, and do not necessarily include all contents and operations/steps, nor must they be performed in the order described. For example, some operations/steps can be decomposed, and some operations/steps can be merged or partially merged, so the actual order of execution may change according to the actual situation.

Figure 1 is a schematic flow chart of the implementation of the session management method provided by the embodiment of the present application;

Figure 2 is a schematic flowchart of the implementation of another session management method provided by an embodiment of the present application;

Figure 3 is a schematic flow chart of the implementation of yet another session management method provided by an embodiment of the present application;

Figure 4 is a schematic flow chart of the implementation of another session management method provided by an embodiment of the present application;

Figure 5 is a schematic structural diagram of a session management device according to an embodiment of the present application;

Figure 6 is a schematic structural diagram of another session management device according to an embodiment of the present application;

Figure 7 is a schematic structural diagram of a terminal device provided by an embodiment of the present application;

Figure 8 is a schematic structural diagram of a network device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the specific technical solutions of the present application will be further described in detail below in conjunction with the drawings in the embodiments of the present application. The following examples are used to illustrate the present application but are not intended to limit the scope of the present application.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or a different subset of all possible embodiments, and Can be combined with each other without conflict.

The embodiment of the present application provides a session management method, which is applied to a terminal device. During the implementation process, the terminal device can be various types of devices with information processing capabilities. For example, the terminal device can include mobile phones and tablet computers. , desktop computers, personal digital assistants, navigators, digital phones, video phones or sensing devices, etc. The functions implemented by this method can be implemented by the processor in the terminal device calling the program code. Of course, the program code can be stored in a computer storage medium. It can be seen that the terminal device at least includes a processor and a storage medium.

Figure 1 is a schematic flow chart of the implementation of the session management method provided by the embodiment of the present application. As shown in Figure 1, the method may include the following steps 101 to 102:

Step 101: The terminal device starts a timer for the established first connection, wherein the timer is set to a first duration, and the first connection is used to transmit PDU data packets.

In some embodiments, the first connection may be a first PDU session connection, which may be used to transmit PDU session packets.

In some embodiments, the network device may be a physical network device used to communicate with the mobile terminal device, which may be an existing cellular base station or a cellular base station with a satellite reference station. For example, the network equipment can be a Base Transceiver Station (BTS) in Global System of Mobile Communication (GSM) or Broadband Code Division Multiple Access (CodeDivision Multiple Acccess), or it can be a Long Term Evolution (Long Term Evolution) Evolutionary base station (Evolutional Node B, eNodeB), relay station or access point in LTE) and network side equipment in 5G network.

In the embodiment of the present application, the network device can be described as a network side device, a network side, a network, etc., which is not limited in the embodiment of the present application.

In this embodiment of the present application, the terminal device may be described as a UE, a terminal, a terminal side device, a terminal side, etc., which is not limited in this embodiment of the present application.

In some embodiments, the timer is set to a first duration, which can be understood as starting from the time when the timer is started and continuing to the first duration, when the timer times out.

In some embodiments, the first duration may be determined according to at least one of (1) to (4):

(1) Slicing resource usage.

The so-called slicing, that is, network slicing, is determined based on an on-demand networking method, which allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice starts from the wireless access network. logical isolation from the bearer network to the core network to adapt to various types of applications. That is, network equipment can process traffic differently and isolate resources in the form of slices, so that different application services can sign up for different slices according to their service requirements.

In some embodiments, the slice resource occupancy may be a slice resource occupancy ratio. It can be characterized by the number of established PDU session connections on the slice/the maximum number of PDU session connections that the slice can carry.

In some embodiments, the process of determining the first duration based on slice resource occupancy is as follows:

Based on determining that the slice resource occupation ratio of the first slice is greater than the first threshold, determine a third duration;

Based on determining that the slice resource occupancy ratio of the second slice is less than the second threshold value, a fourth duration is determined; wherein the first slice and the second slice are set by the network device and are different from the third slice where the first connection is located. For network slicing, the first threshold value is greater than the second threshold value, and the third duration is less than the fourth duration.

Determine the proportion of slice resources occupied by the third slice carried by the first connection, and determine the first duration according to the following formula:

y＝kx+b (1)

Among them, y is the first duration; Slice resource occupancy ratio); b is the intercept, b=third duration-k*slice resource occupancy ratio of the first slice, or, b=fourth duration-k*slice resource occupancy ratio of the second slice.

It should be noted that the above method of determining the timer duration based on slice resource occupancy is not only suitable for determining the first duration for the first connection, but also for determining the timer duration for PDU session connections in other slices. In this way, the timer duration matching the slice status of each PDU session connection can be determined based only on the third duration and the fourth duration, which improves the setting efficiency of the timer.

(2)Terminal type.

In some embodiments, the terminal type includes at least one of the following:

To Business (ToB) terminal;

To Consumer (ToC) terminal.

In some embodiments, the ToB terminal may be a terminal device with specific rules for data transmission. For example: control machines in factories, intercoms, etc. For this kind of terminal device, after one data transmission is completed on the first connection, the possibility of sudden data transmission is extremely small, so there is no need to extend the time to maintain the first connection. In this way, when the terminal type of the terminal device is a ToB terminal, the first duration can be set to a smaller value, thereby reducing the timer duration and making the release of the first connection more timely.

In some embodiments, the ToC terminal may be a terminal whose data transmission does not have specific rules, that is, the data transmission of such terminal devices is relatively random, such as mobile phones, personal computers, etc. For this type of terminal equipment, after completing a data transmission on the first connection, there is a high possibility of burst data transmission, so the first connection time needs to be appropriately extended, that is, the first duration needs to be set to a larger value. The value of , in this way, can prepare for burst data transmission while ensuring the timely release of the first connection.

(3) The service quality requirements of the first connection.

In some embodiments, the service quality requirement of the first connection may be the quality of service (Quality of Service, QoS) of the first connection and/or the slice type carried by the first connection.

In some embodiments, the QoS includes bandwidth for data transmission on the first connection, transmission delay, data packet loss rate, etc. The greater the data transmission bandwidth, the smaller the transmission delay, and the smaller the data packet loss rate, the higher the service quality requirements of the first connection. At this time, frequent releases and establishment of the first connection should be avoided. Therefore, you can The first duration is set to a larger value so that data can be transmitted in a timely manner when the application business is processed again.

In some embodiments, the service quality requirement of the first connection may be a slice type carried by the first connection, and the slice type includes a high-reliable and low-latency communications (URLLC) slice, a massive Internet of Things (Massive Machine Type Communication, mMTC) slicing and so on.

In some embodiments, if the slice type carried on the first connection is URLLC, the first duration takes a value within the first value range. If the slice type carried on the first connection is MTC, the first duration takes a value within the second numerical range, and the first numerical range is not less than the second numerical range.

It can be understood that if the slice type carried on the first connection is URLLC, that is, the service corresponding to the slice carried on the first connection has higher latency requirements. If the first connection is frequently established and released on the first connection, then Each time, the first connection needs to be established before business can be processed, which greatly reduces the speed of business processing. At this time, it is necessary to avoid establishing and releasing the first connection multiple times. Therefore, the first duration can take a value within a larger value range, ensuring the service processing speed on the first connection.

If the slice type carried on the first connection is MTC, that is, the number of terminals carrying the slice on the first connection is larger, but the service corresponding to the slice has lower latency requirements. Therefore, the first duration can be smaller. The value is within the numerical range, that is, the timer duration is reduced, making the release of the first connection more timely.

It should be noted that the first duration determined based on the service quality requirements of the first connection takes into account the latency requirements of the services contracted on the slice, and the granularity is finer. Compared with the first duration determined based on the terminal type, The first duration is more suitable for the current business. Furthermore, the first duration determined based on the occupancy of slice resources takes into account the slicing status of the network. The first duration determined is more conducive to avoiding slice congestion than the first duration determined based on the service quality requirements of the first connection. .

(4) Second duration.

In some embodiments, the second duration may be a value of a timer that the terminal requests to set from the network device, so that the network device can determine the first duration based on the second duration.

In some embodiments, the second duration may be determined by the terminal according to at least one of the following:

terminal type;

The service quality requirements of the first connection.

It should be noted that the method by which the terminal device determines the first duration and the basis by which the network device determines the first duration may be the same or different. That is, the first duration and the second duration may be the same or different. In this embodiment, the terminal device can set the first duration according to the terminal type and/or the service quality requirement of the first connection; the network device can set the first duration according to the slice resource occupancy, the terminal type, the service quality requirement of the first connection, At least one of the second duration to set the first duration. This embodiment does not limit the manner in which the terminal device and the network device set the first duration.

Step 102: Based on determining that the amount of data transmitted on the first connection of the first duration is less than or equal to a first threshold, the terminal device sends a first signaling to the network device, where the first signaling is used to request the release of all data. Describe the first connection.

In some embodiments, the network device receives the first signaling sent by the terminal device and releases the first connection. The first signaling is used to request the release of the first connection established with the terminal device, and the first connection is used to transmit PDU data packets.

In some embodiments, the first signaling may be a PDU session release request (PDU SESSION RELEASEREQUEST).

It can be understood that after the user uses the application service of the contracted slice, the first connection is established between the terminal device and the network device according to the normal process. However, after the user exits the service, the first connection still exists. Furthermore, in the scenario where the application services of multiple contracted slices are continuously used and then exited, the terminal maintains multiple PDU session connections, but at this time there is no data transmission or the data transmission volume is small on the multiple PDU session connections. When the number of terminals registered on a certain slice reaches the maximum value, or the number of PDU session connections established on a certain slice reaches the maximum value, it will cause slice congestion and affect the normal use of the slice by other terminals subscribing to the slice.

In this embodiment, a timer can be started for the established first connection, and the terminal determines that the amount of data transmitted on the first connection during the first duration is less than or equal to the first threshold, that is, the terminal can determine that the first connection has a large amount of data. If the connection is no longer used for data transmission and there is no need to exist, apply to the network device to release the first connection. In this way, when the data transmission volume of the first connection is small or even no data transmission, unused PDU sessions can be released in time, thereby reducing slice congestion.

In some embodiments, the amount of data transmitted on the first connection may be the amount of data transmitted on a data resource bearer (Data Resource Bearer, DRB) on the first connection; the data includes uplink data and downlink data.

In some embodiments, the amount of data transmitted on the first connection during the first duration is less than or equal to the first threshold, which can be understood as starting from the time when the timer starts and continuing until the first duration. The amount of transmitted data is less than or equal to the first threshold.

In some embodiments, from the time the timer starts to the first duration, the amount of data transmitted on the first connection is less than or equal to the first threshold, including:

From the time when the timer starts to the first duration, the amount of data transmitted on the first connection at each moment is less than or equal to the first threshold;

From the time when the timer starts to the first duration, the sum of the amount of data transmitted on the first connection within the first duration is less than or equal to the first threshold.

In some embodiments, the amount of data transmitted on the first connection includes:

The sum of the amount of data transmitted on all DBRs on the first connection;

The amount of data transferred on each DBR on the first connection.

In some embodiments, the first threshold may be preset by the terminal according to its own needs. For example, the first threshold may be 0.

In some embodiments, the terminal may monitor the data transmission volume of the first connection by monitoring the data transmission volume of all DBRs on the first connection.

It should be noted that if the amount of data transmitted on the first connection of the first duration is less than or equal to the first threshold, it can be considered that there is no data transmission on the first connection of the first duration, or it can be It is considered that no data packet is received on the first connection during the first duration; otherwise, it can be considered that there is data transmission on the first connection within the first duration, or it can be considered that the first connection within the first duration is At least one packet was sent and/or received on the connection.

In some embodiments, the terminal may start the timer when the first connection is successfully established. That is, the time to start the timer is the moment when the first connection is successfully established, instead of first judging whether the data transmission amount meets the conditions after the establishment is successful. If there is data transmission, wait until the data transmission is completed before starting the timer. In this way, start The timer is advanced so that the terminal can release unused sessions in a more timely manner.

In some embodiments, when at least one data packet is received within the first period of time, the timer is stopped, and then the cleared timer is restarted.

In some embodiments, when at least one data packet is sent within the first period of time, the timer is stopped, and then the cleared timer is restarted.

It should be noted that the time for sending at least one data packet is very short, about a few us, that is, within a few us, at least one data packet is sent successfully, and the time for sending at least one data packet successfully is much shorter than the first time.

In some embodiments, the time sequence of stopping the timer and clearing the timer is not limited.

It can be understood that the timer is started when the first connection session is successfully established. When the timer lasts to the first duration and there is no data transmission, the release of the first connection is requested. If at least one is sent and/or received within the first duration, When a data packet is received, the timer is stopped, and then the cleared timer is restarted; in this way, the unused first connection can be released in time to avoid slice congestion.

This embodiment of the present application provides a session management method. Figure 2 is a schematic flow chart of the implementation of the session management method provided by this embodiment of the present application. As shown in Figure 2, the method may include the following steps 201 to 204:

Step 201: The terminal device sends second signaling to the network device, where the second signaling is at least used to request to set the timer but not to set the timer duration.

In some embodiments, the second signaling may be a PDU session establishment request (PDU SESSIONESTABLISHMENT REQUEST), used to request the establishment of a first connection with the network device; it may also be other signaling different from the PDUSESSION ESTABLISHMENT REQUEST.

In some embodiments, if the second signaling is PDU SESSION ESTABLISHMENT REQUEST, the terminal device can set the timer and/or apply for the first connection application by carrying a specific information element (information element, IE) in the second signaling. Set the timer to the first duration.

Step 202: The network device receives the second signaling sent by the terminal device;

Step 203: The network device sends third signaling to the terminal device, where the third signaling is used to instruct to set the timer, or to instruct to set the timer and set the timer to the first value. A duration, wherein the first duration is determined based on at least one of slice resource occupancy, terminal type, and service quality requirements of the first connection.

In some embodiments, the third signaling may be PDU SESSION ESTABLISHMENT ACCEPT signaling, or may be other signaling different from PDU SESSION ESTABLISHMENT ACCEPT.

If the third signaling is PDU SESSION ESTABLISHMENT ACCEPT, the network device can set the timer for the terminal through the specific IE in the third signaling and/or set the timer to the first duration.

Step 204: The terminal device receives the third signaling sent by the network device.

In some embodiments, in the case where the third signaling is used to indicate setting the timer and does not indicate the duration of setting the timer, the terminal device determines the timer according to the terminal type and/or the service of the first connection. Quality requirements set the timer to the first duration.

It can be understood that the terminal device applies to the network device to set the timer and does not request to set the timer duration. When the network device allows the terminal device to set the timer, the network device can set the timer according to the slice resource occupancy, terminal type, and the service of the first connection. Quality requires at least one to set the timer for the first duration. In the case where the network device does not indicate to set the timer duration, the terminal device can set the first duration according to its own terminal type and the service quality requirements of the first connection, so that when there is no data transmission on the first connection for the first duration, it can be timely. The application releases the first connection.

In some embodiments, without requesting the network device to set the timer, the network device sends fifth signaling to the terminal device, and the terminal device receives the fifth signaling sent by the network device; Wherein, the fifth signaling is used to instruct to set the timer, or to instruct to set the timer and set the timer to the first duration; in this embodiment, the third signaling The duration is determined by the network device based on at least one of slice resource occupancy, terminal type, and service quality requirements of the first connection.

In some embodiments, the terminal device may send the eighth signaling to the network device, and the network device may determine that the terminal device does not request the network device to set the timing based on determining that the eighth signaling does not carry a specific IE related to the timer. The eighth signaling may be PDU SESSION ESTABLISHMENT REQUEST.

In some embodiments, in the case where the fifth signaling is used to indicate setting the timer and does not indicate the duration of setting the timer, the terminal device determines the quality of service according to the terminal type and/or the service requirement of the first connection. The timer is set to the first duration.

It can be understood that when the terminal does not request to set the timer from the network device, the network device can determine the first duration based on at least one of slice resource occupancy, terminal type, and service quality requirements of the first connection, and then instruct the terminal device Set the timer and set the timer to the first duration, but when the network device indicates that the terminal device can set the timer but does not indicate to set the timer duration, the terminal will set the timer according to its own terminal type and/or the service requirement quality of the first connection. The timer is set to a first duration to release the first connection in time when there is no data transmission on the first connection for the first duration.

In some embodiments, without requesting the network device to set the timer and the network device not instructing to set the timer, the terminal device determines the timer according to the terminal type and/or the service of the first connection. Quality requirements set the timer to the first duration.

In some embodiments, the network device sends the ninth signaling to the terminal device, and the terminal device may determine that the network device has not instructed to set the timer based on determining that the ninth signaling does not carry an IE related to the timer; Nine signaling can be PDU SESSION ESTABLISHMENT ACCEPT.

Understandably, the terminal can set a timer internally according to its own needs. In this way, the terminal does not need to send signaling to request the network device to set the timer, and the network device does not need to set the timer by sending signaling to instruct the terminal whether to set the timer. It saves signaling overhead and is easy to set up.

An embodiment of the present application provides a session management method. Figure 3 is a schematic flowchart of the implementation of the session management method provided by an embodiment of the present application. As shown in Figure 3, the method may include the following steps 301 to 304:

Step 301: The terminal device sends second signaling to the network device, where the second signaling is at least used to request setting of the timer and to set the timer to a second duration;

Step 302: The network device receives the second signaling sent by the terminal device;

Step 303: The network device sends fourth signaling to the terminal device. The fourth signaling is used to instruct to set the timer, or to instruct to set the timer and set the timer to the first value. A long time. The first duration is determined based on at least one of slice resource occupancy, terminal type, service quality requirements of the first connection, and the second duration.

In some embodiments, the fourth signaling may be PDU SESSION ESTABLISHMENT ACCEPT, or may be other signaling different from PDU SESSION ESTABLISHMENT ACCEPT.

If the fourth signaling is PDU SESSION ESTABLISHMENT ACCEPT, the network device can set the timer for the terminal through the specific IE in the fourth signaling and/or set the timer to the first duration.

Step 304: The terminal device receives the fourth signaling sent by the network device.

In some embodiments, in the case where the fourth signaling is used to indicate setting the timer and does not indicate setting the duration of the timer, the terminal device determines the timer according to the terminal type and/or the service of the first connection. Quality requirements set the timer to the first duration.

It can be understood that the terminal device requests the network device to set the timer and set the timer to the second duration. The network device instructs the terminal device to set the timer, and the timer is set according to the slice resource occupancy, terminal type, and service quality of the first connection. At least one of the requirement and the second duration sets the timer to the first duration. When the network device indicates that the terminal device can set the timer, but does not indicate to set the timer duration, the terminal device can set the timer to the first duration according to the terminal type and/or the service quality requirements of the first connection, In order to release the first connection in time when there is no data transmission on the first connection for the first duration.

This embodiment of the present application provides a session management method. Figure 4 is a schematic flowchart of the implementation of the session management method provided by this embodiment of the present application. As shown in Figure 4, the method may include the following steps 401 to 404:

Step 401: The terminal device sends sixth signaling to the network device, where the sixth signaling is used to request establishment of a second connection and request to set the timer.

In some embodiments, the type of the second connection and the type of the first connection may be the same, for example, both are PDU session connections; but the establishment moments of the two may be different.

In some embodiments, the sixth signaling may be PDU SESSION ESTABLISHMENT REQUEST.

In some embodiments, the sixth signaling is also used to set the timer to a second duration.

Step 402: The network device receives the sixth signaling;

Step 403: The network device sends seventh signaling to the terminal device. Wherein, the seventh signaling is used to indicate establishing the second connection with the terminal device.

In some embodiments, the seventh signaling may be PDU SESSION ESTABLISHMENT ACCEPT.

In some embodiments, if the seventh signaling does not carry an IE related to the timer, the timer is not set for the second connection;

In some embodiments, it may be determined that the network device has not instructed to set the timer based on determining that the seventh signaling does not carry an IE related to the timer.

Understandably, the terminal device requests the network device to set the timer through the sixth signaling. The network device can determine whether the terminal needs to set the timer based on its own network conditions or slice congestion conditions. If the slice has no congestion or the slice congestion is weak, In order to ensure service quality, the terminal may not be allowed to set a timer to release the second connection request.

In a mobile communication network, a Protocol Data Unit (PDU) session can be understood as a connection between a terminal and an external network access point gateway. Taking 5G technology as an example, a PDU session is represented by the IP address assigned to the terminal and the Data Network Name (DNN). The terminal transmits data through PDU sessions in the 5G mobile communication network. The DNN is a user plane function (UPF) flag, which identifies different destination networks outside the 5G network.

PDU session connection establishment is initiated by the terminal when it needs to transmit data, and is completed in collaboration with the network. The release of PDU session connections can be initiated by both the network and the terminal.

In some embodiments, the reasons why the network device triggers the release of the PDU session connection include the following, which does not include release reasons related to application services:

Operator determined barring; insufficient resources; user authentication or authorization failed; regular deactivation; network failure; reactivation request (reactivation requested); out of LADN service area; local data network (LADN, Local Area Data Network) insufficient resources for specific slice and DNN (insufficient resources for specific slice and DNN); insufficient resources for specific slices (insufficient resources for specific slice).

In some embodiments, the reasons for the PDU session connection release request initiated by the UE include: insufficient resources (insufficient resources); regular deactivation (regular deactivation); semantic errors in packet filter(s) ); Syntactical error in packet filter(s); Semantic error in the QoS operation; QoS (Quality of Service, Quality of Service) Syntactic error in the QoS operation (Syntactical error in the QoS operation); Invalid mandatory information.

In the solution currently used in the existing network, the terminal is usually configured with a PDU session connection for data services (default PDU session connection) and a PDU session connection for audio and video services (such as Internet Protocol Multimedia Subsystem (IMS)). ), each terminal maintains usually two PDU session connections. Moreover, because all data services use the same PDU session connection, and data packets such as business heartbeat packets exist for a long time, they rarely involve the removal (release) of the PDU session.

However, with the introduction of slicing functions in 5G networks, there is a corresponding relationship between PDU session connections and slices. If different application services sign up for different slices, the terminal will establish different PDU session connections for them. A common implementation method is that the services of the default slice (including unactivated slices) correspond to the default PDU session connection, and other application services signed up for specific slice services correspond to specific PDU session connections. In this case, a terminal needs to maintain multiple PDUs. Session connection.

During the test, the following problems were found: after the user uses the application service of the contract slice (such as opening the APP of the service on the mobile phone), the PDU session connection is established between the terminal and the network according to the normal process. After the user exits the service (such as exiting the service APP on the mobile phone), the PDU session connection still exists and is not released. In the scenario where the service of multiple contracted slices is continuously used and then exited, the terminal maintains multiple PDU session connections, but at this time there is no data transmission on the PDU session connection. The consequence of this problem is that when the number of terminals registered on a certain slice reaches the maximum, or the number of PDU session connections established on a certain slice reaches the maximum, subsequent terminals will no longer be allowed to access or use the slice. That is, if the terminal does not release the PDU session connection in time, it will cause slice congestion and affect the normal use of the slice by other terminals subscribing to the slice.

Based on this, the following will describe an exemplary application of the embodiment of the present application in an actual application scenario.

In the embodiment of this application, a method of automatically releasing a PDU session connection is provided, which can be applied to terminal equipment and network equipment. In this application, the terminal can determine based on the amount of data transmitted on the first PDU session connection within a certain period of time. Whether it is necessary to release the first PDU session connection. The specific process is as follows:

In some embodiments, the terminal starts and maintains a timer for each PDU session connection including the first PDU session. There is a one-to-one correspondence between PDU session connections and timers.

In some embodiments, the timer can be set through methods (1) to (3) and/or the timer can be set to the first duration:

Method (1) is: the network configures different timers and corresponding timer durations for each PDU session connection between the network and the terminal through signaling. For example, during the establishment process of the first PDU session connection, the network configures the first PDU session connection through relevant signaling. A PDU session connection configures a timer and/or configures the timer to a first duration.

Method (2) is: the terminal and the network determine through negotiation whether to configure or not configure a timer for the first PDU session connection. Specifically, the terminal applies to the network through signaling to set a timer for the first PDU session connection and/or applies to set the timer to the second duration, and the network informs the network through signaling that the terminal is allowed to configure or not configure the timer. If configuration is allowed, the terminal can set the timer to the first duration, or the network device configures the timer to the first duration. For example, during the first PDU session connection establishment process, the UE carries a specific IE in the relevant signaling to apply for a configuration timer for the first PDU session, and the network configures the timer and the first PDU session through the specific IE in the relevant signaling during the first PDU session establishment process. One time duration. If IE is not carried, no timer is configured.

Method (3) is: the terminal maintains the timer internally and sets the first duration, and the network does not know the timer.

In some embodiments, the network sets different maximum values for corresponding timers based on the occupancy of slice resources used by each PDU session.

In some embodiments, "slice resource occupancy" can be expressed by the ratio of "the number of established PDU sessions on the slice/the maximum number of PDU sessions that the slice can carry".

In some embodiments, when the slice resource occupancy ratio is greater than the first threshold value, the timer is set to a third duration; when the slice resource occupancy ratio is less than the second threshold value, the timer is set to the third duration; according to the third The duration and the fourth duration determine the first duration. The first threshold value is greater than the second threshold value, and the third duration is less than the fourth duration.

In some embodiments, the terminal may determine the second duration based on the terminal type and request the network to set the timer to the second duration; or the network may set the timer to the first duration based on the terminal type. For example: for enterprise-oriented (TOBusiness, ToB) terminals, data transmission has a certain regularity. After a data transmission is completed, the possibility of burst data transmission is small, and the timer can be set to a smaller value; for consumer-oriented terminals (TO Consumer, ToC) terminals have greater randomness in data transmission, so it is appropriate to extend the time to maintain the first PDU session connection, and the timer can be set to a larger value.

In some embodiments, the terminal can determine the second duration based on the service quality requirements of the first PDU session connection, and request the network to set the timer to the second duration; or, the network can set the timer according to the service quality requirements of the first PDU session connection. The device is set to the first duration. Here, the "service quality requirements of the first PDU session connection" refers to the QoS of the first PDU session connection or the slice type carried by the first PDU session connection. For example, if the slice type carried by the first PDU session connection is URLLC, which has greater requirements on delay, the timer can take a value within the first value range; the slice type carried by the PDU session is mMTC, and the terminal using this slice If the number is larger, the timer can take a value within the second value range. The values in the first numerical range are not less than the values in the second numerical range.

In some embodiments, the timer is started when the first PDU session connection is successfully established, and the timer is deleted after the first PDU session connection is released.

In some embodiments, for each established PDU session, the terminal monitors the data transmission status of the PDU session and maintains a timer according to the data transmission status.

In some embodiments, the terminal monitors the uplink and downlink data transmission status on the first PDU session connection, and the data transmission status can at least distinguish between "data transmission with" and "no data transmission".

In some embodiments, the terminal can monitor the data transmission status of the first PDU session connection by monitoring the data transmission status of all DRBs on the first PDU session connection. If there is data transmission on any DRB, the first PDU is considered If there is "data transmission" on the session connection; if there is no data transmission on all DRBs, it is considered that there is "no data transmission" on the session connection of the first PDU, and "data" includes uplink or downlink data.

In some embodiments, the timer is cleared and restarted after the terminal detects data transmission on the first PDU session connection.

In some embodiments, after the timer times out, the terminal determines that the first PDU session connection can be released, and the terminal sends the first PDU session connection release request signaling (ie, an example of the first signaling). The first PDU The session connection release request signaling is used to request the network to release the first PDU session connection.

This embodiment of the present application provides a session management method, which may include the following steps 401a to 406a (not shown in the figure):

Step 401a: The terminal requests to establish a first PDU session connection through PDU SESSION ESTABLISHMENT REQUEST signaling (that is, an example of the second signaling, sixth signaling, or eighth signaling). In the first PDU SESSIONESTABLISHMENT REQUEST signaling Set the timer in the application.

In some embodiments, the terminal requests to establish the first PDU session connection through PDU SESSION ESTABLISHMENT REQUEST signaling, and applies to set the timer and apply for the second duration of the timer in the PDU SESSION ESTABLISHMENT REQUEST signaling.

In some embodiments, the terminal requests the establishment of a PDU session through PDU SESSION ESTABLISHMENT REQUEST signaling, and does not apply to set the timer in the PDU SESSION ESTABLISHMENT REQUEST signaling. In this embodiment, the fifth signaling sent by the network device is received; wherein the fifth signaling is used to instruct to set the timer, or to instruct to set the timer and set the timer. The timer is set to the first duration; when the fifth signaling is used to indicate setting the timer and does not indicate the duration of setting the timer, the timer is set to the first duration. ;

Step 402a: The network confirms the number of PDU session connections currently established on the slice and the maximum number of PDU session connections that the slice can carry, determines the degree of congestion based on the ratio between the two, and sets the timer to the first duration. The network establishes the first PDU session connection by issuing PDU SESSION ESTABLISHMENT ACCEPT signaling (that is, an example of the third signaling, fourth signaling, fifth signaling, seventh signaling or ninth signaling), At the same time, a timer is configured in the PDU SESSIONESTABLISHMENT ACCEPT signaling, and the timer value is set to the first duration.

Step 403a: After completing the establishment of the first PDU session connection, the terminal starts the timer and the timer runs.

Step 404a: The terminal and the network perform data transmission on the first PDU session connection. The terminal clears the timer and restarts it after sending or receiving at least one data packet.

Step 405a: The terminal and the network stop data transmission on the first PDU session connection, and the timer runs normally.

Step 406a: When the timer runs to the first duration and then times out, the terminal sends PDU SESSION RELEASEREQUEST (ie, an example of the first signaling) to request to release the first connection.

This embodiment of the present application provides a session management method, which may include the following steps 401b to 403b (not shown in the figure):

Step 401b: The terminal requests to establish a second PDU session connection (ie, an example of the second connection) through PDU SESSION ESTABLISHMENT REQUEST signaling, and applies to set a timer in the PDU SESSION ESTABLISHMENT REQUEST signaling.

Step 402b: The network establishes the second PDU session connection by issuing PDU SESSION ESTABLISHMENT ACCEPT signaling. At the same time, the PDU SESSION ESTABLISHMENT ACCEPT signaling does not carry timer-related IEs.

Step 403b: After the second PDU session connection is established, the terminal does not set a timer for the second PDU session connection.

This embodiment of the present application provides a session management method, which may include the following steps 401c to 406c (not shown in the figure):

Step 401c: The terminal requests to establish the first PDU session connection through PDU SESSION ESTABLISHMENT REQUEST signaling.

Step 402c: The network establishes a PDU session by issuing PDU SESSION ESTABLISHMENT ACCEPT signaling.

Step 403c: After the first PDU session is established, the terminal starts the timer and sets the timer to the first duration.

Step 404c: The terminal and the network perform data transmission on the first PDU session connection. When the terminal sends or receives at least one data packet, it clears the timer and restarts it.

Step 405c: The terminal and the network stop data transmission on the first PDU session connection, and the timer runs normally.

Step 406c: When the timer runs to the first duration and times out, the terminal sends a PDU SESSION RELEASEREQUEST request to release the first PDU session connection.

Embodiments of the present application provide a method and device for automatically releasing a PDU session connection, which is applied to terminals and networks and determines whether it is necessary to release the first PDU session connection based on the amount of data transmitted on the first PDU session connection within a certain period of time.

In some embodiments, the terminal sets and maintains a timer for each established PDU session connection.

In some embodiments, the terminal and the network negotiate whether to set the timer and the value of the timer through signaling. The value of the timer may be set based on the slice resource occupancy ratio corresponding to the first PDU session connection, or the terminal type, or set based on the service quality requirements of the first PDU session connection.

In some embodiments, the terminal sets the timer internally and sets the timer to the first duration.

In some embodiments, the network informs the terminal through signaling whether the first PDU session connection sets a timer and/or sets the timer to the first duration.

In some embodiments, for each established PDU session connection, the terminal monitors the data transmission status of the PDU session.

In some embodiments, the terminal initiates the first PDU session connection release request after the timer times out.

The method provided by the embodiments of this application can promptly release PDU session connections that are no longer needed. Especially in slicing application scenarios, it is easy for one terminal to maintain multiple PDU session connections, and can make the use of PDU session connection resources more flexible. And save IP address resources.

The method provided by the embodiments of this application can solve the problem of the terminal not releasing the PDU session connection in time, causing the PDU session connection established on a certain slice to reach the upper limit, thus causing other terminals subscribing to the slice to be unable to access.

The solution of the embodiment of this application is simple to implement and can be implemented at the communication level. It does not involve the interface design of the application layer and the communication layer and is easier to implement on the terminal side.

It should be noted that although the various steps of the methods in this application are described in a specific order in the drawings, this does not require or imply that these steps must be performed in that specific order, or that all of the steps shown must be performed to achieve the desired results. the result of. Additionally or alternatively, some steps can be omitted, multiple steps can be combined into one step for execution, and/or one step can be decomposed into multiple steps for execution, etc.; or, steps in different embodiments can be combined into a new technology. plan.

Based on the foregoing embodiments, embodiments of the present application provide a session management device. The device includes various modules and units included in each module. It can be implemented by a processor; of course, it can also be implemented by specific logic circuits. Implementation; During the implementation process, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA), etc.

Figure 5 is a schematic structural diagram of a session management device provided by an embodiment of the present application. As shown in Figure 5, the device 50 includes a startup module 51 and a sending module 52, wherein:

Start module 51, configured to start a timer for the first connection established; wherein the timer is set to a first duration, and the first connection is used to transmit PDU data packets;

The first sending module 52 is configured to send first signaling to the network device based on determining that the amount of data transmitted on the first connection of the first duration is less than or equal to a first threshold, where the first signaling is used Request release of the first connection.

In some embodiments, the starting module 51 is also configured to start the timer when the first connection is successfully established.

In some embodiments, the session management device 50 further includes a stop module, the stop module is used to stop the timer; the start module 51 is also used to restart the cleared timer.

In some embodiments, the first duration is determined based on at least one of the following: slice resource occupancy; terminal type; and service quality requirements of the first connection.

In some embodiments, the first sending module 52 is also configured to send second signaling to the network device, where the second signaling is at least used to request setting of the timer; the session management device is also including a second receiving module, the second receiving module being used to receive third signaling sent by the network device; wherein the third signaling is used to indicate setting of the timer, or to indicate setting the timer and setting the timer to the first duration; the session management device further includes a setting module configured to indicate setting of the timer in the third signaling And if there is no instruction to set the duration of the timer, the timer is set to the first duration.

In some embodiments, the second signaling is also used to request to set the timer to a second duration; the second receiving module is also used to receive the fourth signaling sent by the network device; wherein , the fourth signaling is used to instruct to set the timer, or to instruct to set the timer and set the timer to the first duration; the setting module is also used to set the timer. When the fourth signaling is used to indicate setting of the timer and does not indicate the duration of setting the timer, the timer is set to the first duration; wherein the first duration is at least based on The second duration is determined.

In some embodiments, the second receiving module is further configured to receive the fifth signaling sent by the network device without requesting the network device to set the timer; wherein the third Five signaling is used to instruct to set the timer, or to instruct to set the timer and set the timer to the first duration. Also configured to set the timer to the first duration when the fifth signaling is used to indicate setting the timer and does not indicate setting the duration of the timer; the setting module, It is also configured to set the timer to the first duration when the network device is not requested to set the timer and the network device does not indicate setting the timer.

In some embodiments, the first sending module 52 is also configured to send a sixth signaling to the network device, where the sixth signaling is used to request establishment of the first connection and request to set the timer; the second receiving module is also used to receive the seventh signaling sent by the network device, the seventh signaling is used to indicate establishing the first connection with the terminal device; in the third If the seven signaling does not carry the IE related to the timer, the timer is not set for the first connection.

In some embodiments, the terminal type includes at least one of the following: ToB terminal; ToC terminal.

In some embodiments, the service quality requirements of the first connection include QoS of the first connection and/or a slice type carried by the first connection.

Figure 6 is a schematic structural diagram of a session management device provided by an embodiment of the present application. As shown in Figure 6, the device 60 includes a first receiving module 61 and a releasing module 62, wherein:

The first receiving module is configured to receive the first signaling sent by the terminal device, the first signaling is used to request the release of the first connection established with the terminal device, and the first connection is used to transmit PDU data packets;

a release module, configured to release the first connection; wherein the first signaling is sent when the amount of data transmitted on the first connection is less than or equal to a first threshold during the first duration of the timer, The timer is set for the first connection.

In some embodiments, the first receiving module 61 is also configured to receive second signaling sent by the terminal device, where the second signaling is at least used to request to set the timer.

In some embodiments, the apparatus 60 further includes a second sending module, the second sending module being configured to send third signaling to the terminal device, where the third signaling is used to indicate setting the required the timer, or used to indicate setting the timer and setting the timer to the first duration.

In some embodiments, the second signaling is also used to request to set the timer to a second duration; the second sending module is also used to send fourth signaling to the terminal device, wherein, The fourth signaling is used to instruct to set the timer, or to instruct to set the timer and set the timer to the first duration.

In some embodiments, the second sending module is further configured to send fifth signaling to the terminal device without receiving a request from the terminal device to set the timer; wherein the fifth The signaling is used to indicate setting the timer, or to indicate setting the timer and setting the timer to the first duration.

In some embodiments, the first receiving module 61 is also used to receive the sixth signaling sent by the terminal device, where the sixth signaling is used to request the establishment of the second connection; the second sending Module, further configured to send seventh signaling to the terminal device, where the seventh signaling is used to indicate establishing the second connection with the terminal device; the seventh signaling does not carry the In the case of timer-related IE, the terminal does not set the timer for the second connection.

The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

It should be noted that the division of modules by the session management device shown in Figures 5 and 6 in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods. In addition, each functional unit in various embodiments of the present application may be integrated into one processing unit, may exist independently, or may have two or more units integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units. It can also be implemented by combining software and hardware.

It should be noted that in the embodiments of the present application, if the above method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products that are essentially or contribute to related technologies. The computer software product is stored in a storage medium and includes a number of instructions to enable The terminal device and the network device execute all or part of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read only memory (Read Only Memory, ROM), magnetic disk or optical disk and other various media that can store program codes. As such, embodiments of the present application are not limited to any specific combination of hardware and software.

An embodiment of the present application provides a terminal device. Figure 7 is a schematic diagram of a hardware entity of an electronic device according to an embodiment of the present application. As shown in Figure 7, the electronic device 70 includes a memory 71 and a processor 72. The memory 71 stores A computer program that can be run on the processor 72, and when the processor 72 executes the program, the steps in the method provided in the above embodiments are implemented.

It should be noted that the memory 71 is configured to store instructions and applications executable by the processor 72, and can also cache data to be processed or processed by each module in the processor 72 and the electronic device 70 (for example, image data, audio data , voice communication data and video communication data), which can be implemented through flash memory (FLASH) or random access memory (RandomAccess Memory, RAM).

An embodiment of the present application provides a network device. Figure 8 is a schematic diagram of a hardware entity of an electronic device according to an embodiment of the present application. As shown in Figure 8, the electronic device 80 includes a memory 81 and a processor 82. The memory 81 stores A computer program that can be run on the processor 82. When the processor 82 executes the program, the steps in the method provided in the above embodiments are implemented.

It should be noted that the memory 81 is configured to store instructions and applications executable by the processor 82, and can also cache data to be processed or processed by each module in the processor 82 and the electronic device 80 (for example, image data, audio data , voice communication data and video communication data), which can be implemented through flash memory (FLASH) or random access memory (RandomAccess Memory, RAM).

Embodiments of the present application provide a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the session management method provided in the above embodiments are implemented.

Embodiments of the present application provide a computer program product containing instructions that, when run on a computer, cause the computer to perform steps in the session management method provided by the above method embodiments.

It should be pointed out here that the above description of the storage medium and device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium, storage medium and device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

It will be understood that reference throughout this specification to "one embodiment" or "an embodiment" or "some embodiments" means that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. . Thus, the appearances of "in one embodiment" or "in an embodiment" or "in some embodiments" in various places throughout this specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation. The above serial numbers of the embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments. The above description of various embodiments tends to emphasize the differences between the various embodiments, and the similarities or similarities can be referred to each other. For the sake of brevity, they will not be described again here.

The term "and/or" in this article is just an association relationship that describes related objects, indicating that there can be three relationships, such as object A and/or object B, which can mean: object A exists alone, and object A and object exist at the same time. B, there are three cases of object B alone.

It should be noted that, in this document, the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of other identical elements in a process, method, article or device that includes that element.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The above-described embodiments are only illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods, such as: multiple modules or components may be combined, or may be Integrated into another system, or some features can be ignored, or not implemented. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or modules may be electrical, mechanical, or other forms. of.

The modules described above as separate components may or may not be physically separated; the components shown as modules may or may not be physical modules; they may be located in one place or distributed to multiple network units; Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present application can be all integrated into one processing unit, or each module can be separately used as a unit, or two or more modules can be integrated into one unit; the above-mentioned integration The module can be implemented in the form of hardware or in the form of hardware plus software functional units.

Those of ordinary skill in the art can understand that all or part of the steps to implement the above method embodiments can be completed through hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the execution includes: The steps of the above method embodiment; and the aforementioned storage media include: mobile storage devices, read-only memory (Read Only Memory, ROM), magnetic disks or optical disks and other various media that can store program codes.

Alternatively, if the integrated units mentioned above in this application are implemented in the form of software function modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products that are essentially or contribute to related technologies. The computer software product is stored in a storage medium and includes a number of instructions to enable The terminal device and the network device execute all or part of the methods described in various embodiments of this application. The aforementioned storage media include: mobile storage devices, ROMs, magnetic disks or optical disks and other media that can store program codes.

The methods disclosed in several method embodiments provided in this application can be combined arbitrarily to obtain new method embodiments without conflict.

The features disclosed in several product embodiments provided in this application can be combined arbitrarily without conflict to obtain new product embodiments.

The features disclosed in several method or device embodiments provided in this application can be combined arbitrarily without conflict to obtain new method embodiments or device embodiments.

The above are only embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application. are covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (21)

1. A session management method applied to a terminal device, the method comprising:

starting a timer for the established first connection; the timer is set to a first duration, and the first connection is used for transmitting PDU data packets;

and based on determining that the amount of data transmitted over the first connection for the first duration is less than or equal to a first threshold, sending first signaling to a network device, the first signaling being used to request release of the first connection.

2. The method of claim 1, wherein the starting a timer for the established first connection comprises:

and when the first connection is established successfully, starting the timer.

3. The method according to claim 2, wherein the method further comprises:

Stopping the timer when at least one data packet is received within the first time period;

restarting the cleared timer.

4. The method of claim 1, wherein the first time period is determined based on at least one of:

slice resource occupation;

a terminal type;

the quality of service requirement of the first connection.

5. The method according to claim 4, wherein the method further comprises:

transmitting a second signaling to the network device, wherein the second signaling is at least used for requesting to set the timer;

receiving a third signaling sent by the network equipment;

the third signaling is used for indicating to set the timer or used for indicating to set the timer and setting the timer to the first duration;

and setting the timer to the first duration in the case that the third signaling is used for indicating to set the timer and the duration of the timer is not indicated to be set.

6. The method of claim 5, wherein the second signaling is further for requesting that the timer be set to a second duration;

receiving a fourth signaling sent by the network equipment;

The fourth signaling is used for indicating to set the timer or used for indicating to set the timer and setting the timer to the first duration;

setting the timer to the first duration in the case that the fourth signaling is used for indicating setting the timer and does not indicate setting the duration of the timer;

wherein the first time period is determined based at least on the second time period.

7. The method according to claim 4, wherein the method further comprises:

receiving fifth signaling sent by the network equipment under the condition that the setting of the timer is not requested to the network equipment; wherein the fifth signaling is used for indicating to set the timer or for indicating to set the timer and setting the timer to the first duration;

setting the timer to the first duration in a case where the fifth signaling is used to indicate setting the timer and does not indicate setting the duration of the timer;

setting the timer to the first duration in the event that the setting of the timer is not requested to the network device and the network device does not indicate the setting of the timer.

8. The method according to claim 1, wherein the method further comprises:

transmitting a sixth signaling to the network device, the sixth signaling being used to request establishment of the second connection and to request setting of the timer;

receiving a seventh signaling sent by the network device, where the seventh signaling is used to instruct the terminal device to establish the second connection;

in case no IE related to the timer is carried in the seventh signaling, the timer is not set for the second connection.

9. The method according to any of claims 4 to 7, wherein the terminal type comprises at least one of:

a ToB terminal;

and (3) ToC terminal.

10. The method according to any of claims 4 to 7, wherein the quality of service requirement of the first connection comprises QoS of the first connection and/or slice type of the first connection bearer.

11. A session management method applied to a network device, the method comprising:

receiving a first signaling sent by a terminal device, wherein the first signaling is used for requesting to release a first connection established with the terminal device, and the first connection is used for transmitting a PDU data packet;

Releasing the first connection;

wherein the first signaling is sent if the amount of data transmitted on the first connection is less than or equal to a first threshold for a first duration of a timer, the timer being set for the first connection.

12. The method according to claim 11, characterized in that the method comprises: the first time period is determined according to at least one of the following:

slice resource occupation;

a terminal type;

the quality of service requirement of the first connection.

13. The method according to claim 12, wherein the method further comprises:

receiving a second signaling sent by the terminal equipment, wherein the second signaling is at least used for requesting to set the timer;

and sending a third signaling to the terminal equipment, wherein the third signaling is used for indicating to set the timer or used for indicating to set the timer and setting the timer to be the first duration.

14. The method of claim 13, wherein the second signaling is further for requesting that the timer be set to a second duration;

sending a fourth signaling to the terminal equipment, wherein the fourth signaling is used for indicating to set the timer or used for indicating to set the timer and setting the timer to the first duration;

Wherein the first time period is determined based at least on the second time period.

15. The method according to claim 12, wherein the method further comprises:

transmitting a fifth signaling to the terminal device under the condition that the request of the terminal device for setting the timer is not received; the fifth signaling is used for indicating to set the timer or used for indicating to set the timer and setting the timer to the first duration.

16. The method of claim 11, wherein the method further comprises:

receiving a sixth signaling sent by the terminal equipment, wherein the sixth signaling is used for requesting to establish the second connection;

transmitting a seventh signaling to the terminal device, where the seventh signaling is used to instruct the terminal device to establish the second connection;

in case no IE related to the timer is carried in the seventh signaling, the terminal device does not set the timer for the second connection.

17. A session management apparatus, comprising:

the starting module is used for starting a timer for the established first connection; the timer is set to a first duration, and the first connection is used for transmitting PDU data packets;

And a first sending module, configured to send a first signaling to a network device, where the first signaling is used to request to release the first connection, based on determining that the amount of data transmitted on the first connection for the first duration is less than or equal to a first threshold.

18. A session management apparatus, comprising:

a first receiving module, configured to receive a first signaling sent by a terminal device, where the first signaling is used to request to release a first connection established with the terminal device, and the first connection is used to transmit a PDU packet;

a release module for releasing the first connection;

wherein the first signaling is sent if the amount of data transmitted on the first connection is less than or equal to a first threshold for a first duration of a timer, the timer being set for the first connection.

19. A terminal device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that the processor implements the method of any of claims 1 to 10 when executing the program.

20. A network device comprising a memory and a processor, the memory storing a computer program executable on the processor, wherein the processor implements the method of any of claims 11 to 16 when the program is executed.

21. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method according to any one of claims 1 to 10, or the computer program, when being executed by a processor, implements the method according to any one of claims 11 to 16.