CN117336896A

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

Info

Publication number: CN117336896A
Application number: CN202210726452.2A
Authority: CN
Inventors: 孔露婷; 金晨光; 宋丹
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2022-06-23
Filing date: 2022-06-23
Publication date: 2024-01-02

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

The present application relates to communication technology, and relates to, but is not limited to, session management methods and apparatuses, devices, and storage media.

Background

A protocol data unit (Protocol Data Unit, PDU) session may be understood in a mobile communication network as a connection between a terminal and an external network access point gateway. Taking the 5G technique as an example, the PDU session is characterized by an internet protocol (Internet Protocol, IP) address assigned to the terminal and a data network name (Data Network Name, DNN). The terminal may perform data transmission through a PDU session in a 5G mobile communication network.

In the scheme used in the current network, one or more PDU sessions are usually configured for the terminal, and as a slice function is introduced into the 5G network, a corresponding relationship exists between the PDU session and the slice, different application services sign up for different slices, and the terminal establishes corresponding PDU sessions for different slices. However, slice congestion may be caused during data transmission over a PDU session.

Disclosure of Invention

In view of this, the session management method, device, equipment and storage medium provided by the present application can timely release the PDU session that is not needed to be used, thereby reducing slice blocking and improving new communication energy.

According to an aspect of the embodiments of the present application, there is provided a session management method, applied to a terminal device, including: 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 a first signaling to a network device, the first signaling being used to request release of the first connection.

According to an aspect of the embodiments of the present application, there is provided a session management method, applied to a network device, including: 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.

According to an aspect of the embodiments of the present application, there is provided a session management apparatus, including: 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 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.

According to an aspect of the embodiments of the present application, there is provided a session management apparatus, including: a 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 data 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.

The terminal device provided by the embodiment of the application comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor realizes the method described by the embodiment of the application when executing the program.

The network device provided by the embodiment of the application comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor realizes the method described by the embodiment of the application when executing the program.

The computer readable storage medium provided in the embodiments of the present application stores a computer program thereon, which when executed by a processor implements the method provided in the embodiments of the present application.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the technical aspects of the application. It is apparent that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.

The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

Fig. 1 is a schematic implementation flow chart of a session management method provided in an embodiment of the present application;

fig. 2 is a schematic implementation flow chart of another session management method according to an embodiment of the present application;

fig. 3 is a schematic implementation flow chart of another session management method according to an embodiment of the present application;

fig. 4 is a schematic implementation flow chart of another session management method according to an embodiment of the present application;

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

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

fig. 7 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

For the purposes, technical solutions and advantages of the embodiments of the present application to be more apparent, the specific technical solutions of the present application will be described in further detail below with reference to the accompanying drawings in the embodiments of the present application. The following examples are illustrative of the present application, but are not intended to limit the scope of the present application.

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

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

The embodiment of the application provides a session management method, which is applied to terminal equipment, wherein the terminal equipment can be various types of equipment with information processing capability in the implementation process, and for example, the terminal equipment can comprise a mobile phone, a tablet computer, a desktop computer, a personal digital assistant, a navigator, a digital telephone, a video telephone or a sensing equipment and the like. The functions performed by the method may be performed by a processor in a terminal device, which may of course be stored in a computer storage medium, as will be seen, comprising at least the processor and the storage medium.

Fig. 1 is a schematic implementation flow chart of a session management method according to an embodiment of the present application, as shown in fig. 1, the method may include the following steps 101 to 102:

step 101, a 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 for transmitting a PDU data packet.

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

In some embodiments, the network device may be a physical network device for communicating with a 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 devices may be base stations (Base Transceiver Station, BTS) in Global System for Mobile communications (Global System of Mobile Communication, GSM) or wideband code division multiple Access (Code Division Multiple Acccess), and may also be evolved base stations (Evolutional Node B, eNodeB) in Long term evolution (Long Term Evolution, LTE), relay stations or access points, and network side devices in 5G networks.

In the embodiment of the present application, the network device may 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 the embodiment of the present application, the terminal device may be described as UE, a terminal side device, a terminal side, or the like, which is not limited in the embodiment of the present application.

In some embodiments, the timer is set to a first duration, and it may be understood that the timer times out from the time when the timer is started to the time when the timer is continued to the first duration.

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

(1) Slice resource occupancy.

The slicing, i.e. network slicing, is determined based on an on-demand networking manner, and can enable an operator to separate a plurality of virtual end-to-end networks on a unified infrastructure, and each network slicing is logically isolated from a radio access network to a bearer network and then to a core network so as to adapt to various types of applications. That is, the network device may perform the traffic differentiation processing in the form of slices, and may isolate resources, so that different application services sign up for different slices according to their service requirements.

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

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

determining a third duration based on determining that the slice resource occupancy proportion of the first slice is greater than a first threshold value;

determining a fourth time length based on determining that the slice resource occupancy ratio of the second slice is less than the second threshold; the first slice and the second slice are network slices which are set by the network equipment and are different from a third slice where the first connection is located, the first threshold value is greater than the second threshold value, and the third duration is less than the fourth duration.

Determining a slice resource occupation ratio of a third slice borne by the first connection, and determining a first time length according to the following formula:

y＝kx+b (1)

wherein y is a first duration; x is the slice resource occupation condition of the third slice; k is a slope, k= (third time length-fourth time length)/(slice resource occupation ratio of the first slice-slice resource occupation ratio of the second slice); b is the intercept, b=third duration-k is the slice resource occupation ratio of the first slice, or b=fourth duration-k is the slice resource occupation ratio of the second slice.

It should be noted that, the method for determining the timer duration according to the slice resource occupation condition is not only suitable for determining the first duration for the first connection, but also suitable for determining the timer duration for the PDU session connection in other slices. Therefore, the timer duration matched with the slicing condition of each PDU session connection can be determined only according to the third duration and the fourth duration, and the setting efficiency of the timer is improved.

(2) Terminal type.

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

an enterprise (ToB) oriented terminal;

consumer (ToC) oriented terminals.

In some embodiments, the ToB terminal may be a terminal device with a specific rule of data transmission. For example: control machines inside the factory, interphones, etc. With such a terminal device, the possibility of burst data transmission after one data transmission is performed on the first connection is extremely small, and thus it is unnecessary to lengthen the time for maintaining the first connection. Thus, when the terminal type of the terminal device is a ToB terminal, the first time length can be set to a smaller value, so that the timer time length is shortened, and the first connection is released more timely.

In some embodiments, the ToC terminal may be a terminal whose data transmission does not have a specific rule, i.e. the data transmission of such terminal devices is more random, for example: cell phones, personal computers, and the like. For such a terminal device, after the first connection is performed for one data transmission, there is a high possibility of performing burst data transmission, and thus it is necessary to appropriately lengthen the first connection time, that is, to set the first time length to a high value, so that preparation for burst data transmission can be made while ensuring timely release of the first connection.

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

In some embodiments, the quality of service requirement of the first connection may be a quality of service (Quality of Service, qoS) of the first connection and/or a slice type of the first connection bearer.

In some embodiments, the QoS includes a bandwidth over which data is transmitted over the first connection, a delay in transmission, a packet loss rate of the data, and so on. The larger the bandwidth of the data transmission, the smaller the delay of the transmission, the smaller the packet loss rate of the data, and the higher the service quality requirement of the first connection, at this time, frequent release and establishment of the first connection should be avoided, so that the first time length can be set to a larger value, so that the data transmission can be timely performed when the application service is processed again.

In some embodiments, the quality of service requirement of the first connection may be a slice type of the first connection bearer, including a high reliability low latency communication (Ultra-reliable and Low Latency Communications, URLLC) slice, a mass internet of things (Massive Machine Type Communication, mctc) slice, 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 range of values. If the type of the slice carried on the first connection is MTC, the first time length takes a value in a second numerical value range, and the first numerical value range is not smaller than the second numerical value range.

It can be understood that if the type of the slice carried on the first connection is URLLC, that is, the service corresponding to the slice carried on the first connection has a high requirement on time delay, and if the first connection is frequently established and released on the first connection, the service needs to be processed after the first connection is established each time, so that the speed of processing the service is greatly reduced. At this time, the first connection should be avoided from being established and released as many times as possible, so that the first duration can be valued in a larger numerical range, and the service processing speed on the first connection is ensured.

If the type of the slice carried on the first connection is MTC, that is, the number of terminals of the slice carried on the first connection is larger, but the service corresponding to the slice has a lower requirement for time delay, so that the first time length can be valued in a smaller numerical range, that is, the duration of the timer is reduced, so that the first connection is released more timely.

It should be noted that, the first time length determined according to the service quality requirement of the first connection considers the requirement of the service subscribed on the slice on the time delay, the granularity is finer, and the determined first time length is more suitable for the current service than the first time length determined according to the terminal type. Further, the first time length determined according to the slice resource occupation condition considers the slice condition of the network, and compared with the first time length determined according to the service quality requirement of the first connection, the determined first time length is more beneficial to avoiding slice congestion.

(4) A second time period.

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

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

A terminal type;

the quality of service requirement of the first connection.

It should be noted that, the manner in 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. I.e. the first time period and the second time period may be the same or different. In this embodiment, the terminal device may set the first duration according to a terminal type and/or a service quality requirement of the first connection; the network device may set the first duration according to at least one of a slice resource occupancy, a terminal type, a quality of service requirement of the first connection, and a second duration. The manner in which the terminal device and the network device set the first duration is not limited in this embodiment.

Step 102, the terminal device sends a first signaling to the 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.

In some embodiments, the network device receives a first signaling sent by the terminal device, releasing the first connection. 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 PDU data packets.

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

It will be appreciated that after the user uses the application service of the subscription slice, the first connection is established between the terminal device and the network device according to the normal flow, but after the user exits the service, the first connection still exists. Further, in a scenario where application services of a plurality of subscription slices are continuously used and then exited, the terminal maintains a plurality of PDU session connections, but at this time, the plurality of PDU session connections have no data transmission or a small amount of data transmission. When a terminal registered on a certain slice reaches a maximum value, or a PDU session connection established on a certain slice reaches a maximum value, slice congestion is caused, and other terminals subscribed to the slice are influenced to normally use the slice.

In this embodiment, a timer may be started for the established first connection, and the terminal applies for releasing the first connection to the network device based on determining that the amount of data transmitted on the first connection for the first duration is less than or equal to the first threshold, i.e., the terminal is able to determine that the first connection has been used for data transmission with a high probability, and there is no need. Therefore, the PDU session which is not needed to be used can be released in time when the data transmission quantity of the first connection is smaller or even no data transmission exists, and the slice congestion is reduced.

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

In some embodiments, the amount of data transmitted on the first connection for the first duration is less than or equal to the first threshold, which may be understood as the amount of data transmitted on the first connection for the first duration from the starting time of the timer.

In some embodiments, continuing from the time of starting the timer to the first time period, the amount of data transmitted on the first connection is less than or equal to a first threshold, comprising:

starting the timer, and continuing to the first time, wherein the data quantity transmitted on the first connection at each time is smaller than or equal to a first threshold value;

and from the starting moment of the timer, continuing to the first time period, wherein the sum of the data quantity transmitted on the first connection in the first time period is less than or equal to a first threshold value.

In some embodiments, the amount of data transmitted over the first connection comprises:

the sum of the data amounts transmitted over 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 requirement, and illustratively, the first threshold may be 0.

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

It should be noted that, if the amount of data transmitted on the first connection in the first duration is less than or equal to a first threshold, it may be considered that there is no data transmission on the first connection in the first duration, or it may be considered that no data packet is received on the first connection in the first duration; otherwise, it may be considered that there is a data transmission on the first connection for the first time period, or it may be considered that at least one data packet is sent and/or received on the first connection for the first time period.

In some embodiments, the terminal may start the timer when the first connection establishment is successful. The time for starting the timer is the time when the first connection is successfully established, instead of judging whether the data transmission quantity meets the condition after the first connection is successfully established, if the data transmission is completed, the timer is started after the data transmission is completed, so that the time for starting the timer is advanced, and the terminal can release the session which is not needed to be used more timely.

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

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

It should be noted that the time for transmitting the at least one data packet is short, which is about several us, that is, the time for transmitting the at least one data packet is successful within several us, and the duration for transmitting the at least one data packet is far less than the first duration.

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

It can be appreciated that when the first connection session is established successfully, the timer is started, when the timer is continued for a first duration, no data transmission is required to release the first connection, if at least one data packet is sent and/or received in the first duration, the timer is stopped, and then the cleared timer is restarted; therefore, the first connection which is not needed to be used can be timely released, and slice congestion is avoided.

An embodiment of the present application provides a session management method, and fig. 2 is a schematic implementation flow diagram of the session management method provided in the embodiment of the present application, as shown in fig. 2, where the method may include the following steps 201 to 204:

Step 201, the terminal device sends a second signaling to the network device, where the second signaling is at least used for requesting to set the timer but not used for setting the timer duration.

In some embodiments, the second signaling may be a PDU session establishment request (PDU SESSION ESTABLISHMENT REQUEST) requesting to establish a first connection with a network device; other signaling than PDU SESSION ESTABLISHMENT REQUEST is also possible.

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

Step 202, the network equipment receives a second signaling sent by the terminal equipment;

in step 203, the network device sends third signaling to the terminal device, where the third signaling is used to instruct setting the timer, or instruct setting the timer and setting the timer to the first duration, where the first duration is determined according to at least one of a slice resource occupation situation, a terminal type, and a service quality requirement of the first connection.

In some embodiments, the third signaling may be grant PDU session establishment (PDU SESSION ESTABLISHMENT ACCEPT) signaling, or may be other signaling than PDU SESSION ESTABLISHMENT ACCEPT.

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

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

In some embodiments, in case the third signaling is used to indicate setting the timer and does not indicate setting a duration of the timer, the terminal device sets the timer to the first duration according to a terminal type and/or a quality of service requirement of the first connection.

It may be appreciated that, when the terminal device applies for setting the timer to the network device and does not request to set the timer duration, and the network device allows the terminal device to set the timer, the network device may set the timer to be the first duration according to at least one of a slice resource occupation situation, a terminal type, and a service quality requirement of the first connection. Under the condition that the network equipment does not indicate to set the time length of the timer, the terminal equipment can set the first time length according to the terminal type of the terminal equipment and the service quality requirement of the first connection, so that the first connection can be timely applied to be released when no data is transmitted on the first connection with the first time length.

In some embodiments, in a case that the setting of the timer is not requested to the network device, the network device sends a 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 for indicating to set the timer or for indicating to set the timer and setting the timer to the first duration; in this embodiment, the first duration is determined by the network device according to at least one of a slice resource occupancy, a terminal type, and a quality of service requirement of the first connection.

In some embodiments, the terminal device may send an 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 timer based on determining that a specific IE related to the timer is not carried in the eighth signaling; the eighth signaling may be PDU SESSION ESTABLISHMENT REQUEST.

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

It will be appreciated that when the terminal does not request to the network device to set the timer, the network device may determine the first time period according to at least one of the slice resource occupancy, the terminal type, and the quality of service requirement of the first connection, and then instruct the terminal device to set the timer and set the timer to the first time period, but when the network device instructs the terminal device that the timer can be set but does not instruct the setting of the timer period, the terminal sets the timer to the first time period according to its terminal type and/or the quality of service requirement of the first connection, so as to release the first connection in time when there is no data transmission on the first connection at the first time period.

In some embodiments, in case the setting of the timer is not requested to the network device and the network device does not indicate the setting of the timer, the terminal device sets the timer to the first duration according to a terminal type and/or a quality of service requirement of the first connection.

In some embodiments, the network device sends the ninth signaling to the terminal device, and the terminal device may determine that the network device does not indicate to set the timer based on determining that the IE related to the timer is not carried in the ninth signaling; the ninth signaling may be PDU SESSION ESTABLISHMENT ACCEPT.

It can be understood that the terminal can internally set a timer according to its own needs, so that the terminal does not need to request the network device to set the timer by sending signaling, the network device does not need to set the timer by indicating whether the terminal sets the timer or not by sending signaling, signaling cost is saved, and the setting mode is simple.

An embodiment of the present application provides a session management method, and fig. 3 is a schematic implementation flow diagram of the session management method provided in the embodiment of the present application, as shown in fig. 3, where the method may include the following steps 301 to 304:

step 301, a terminal device sends a second signaling to the network device, where the second signaling is at least used to request to set the timer, and set the timer to a second duration;

step 302, the network equipment receives a second signaling sent by the terminal equipment;

in step 303, the network device sends fourth signaling to the terminal device, where the fourth signaling is used to instruct setting the timer, or instruct setting the timer and setting the timer to the first duration. The first duration is determined according to at least one of slice resource occupation condition, terminal type, service quality requirement of the first connection and second duration.

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

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

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

In some embodiments, in case the fourth signaling is used to indicate setting the timer and not to indicate setting a duration of the timer, the terminal device sets the timer to the first duration according to a terminal type and/or a quality of service requirement of the first connection.

It will be appreciated that the terminal device requests the network device to set the timer and to set the timer to the second duration, the network device indicates that the terminal device can set the timer, and sets the timer to the first duration according to at least one of a slice resource occupancy, a terminal type, a quality of service requirement of the first connection, and the second duration. When the network device indicates that the terminal device can set the timer, but does not indicate to set the duration of the timer, the terminal device can set the timer to be the first duration according to the type of the terminal and/or the service quality requirement of the first connection, so as to release the first connection in time when no data is transmitted on the first connection of the first duration.

An embodiment of the present application provides a session management method, and fig. 4 is a schematic implementation flow diagram of the session management method provided in the embodiment of the present application, as shown in fig. 4, where the method may include the following steps 401 to 404:

step 401, the terminal device sends a sixth signaling to the network device, where the sixth signaling is used to request to establish the 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, such as both PDU session connections; but the establishment times 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 further configured to set the timer to a second duration.

Step 402, the network device receives sixth signaling;

in step 403, the network device sends a seventh signaling to the terminal device. Wherein the seventh signaling is used to instruct to establish the second connection with the terminal device.

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

In some embodiments, in the case where 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 does not indicate to set the timer based on determining that no IE associated with the timer is carried in the seventh signaling.

It can be understood that the terminal device requests to set the timer to the network device through the sixth signaling, the network device may determine whether the terminal needs to set the timer according to its network condition or slice congestion condition, and if the slice has no congestion phenomenon or the slice congestion degree is weaker, the terminal may not agree to set the timer to release the request for the second connection in order to ensure the service quality.

A protocol data unit (Protocol Data Unit, PDU) session may be understood in a mobile communication network as a connection between a terminal and an external network access point gateway. Taking the 5G technique as an example, the PDU session is characterized by an IP address assigned to the terminal and a data network name (Data Network Name, DNN). The terminal performs data transmission through a PDU session in a 5G mobile communication network. The DNN is a user plane function (User Plane Function, UPF) flag identifying different destination networks outside the 5G network.

The PDU session connection establishment is completed by the terminal initiating a request when it needs to transmit data, in cooperation with the network. Both the release network and the terminal of the PDU session connection may be initiated.

In some embodiments, the reasons for the network device to trigger the PDU session connection release include the following, which does not include release reasons related to the application traffic:

an operator-determined blocking service (operator determined barring); starved resources (insufficient resources); user authentication or authorization fails (user authentication or authorization failed); phase deactivation (regular deactivation); network failure (network failure); a reactivation request (reactivation requested); outside the LADN service area (out of LADN service area); local data network (LADN, local Area Data Network) specific slices and DNNs are resource starved (insufficient resources for specific slice and DNN); the resources of a particular slice are inadequate (insufficient resources for specific slice).

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

In the solutions currently used in the networks, terminals are typically configured with one PDU session connection (default PDU session connection) for data-like services and with audio-video services (PDU session connection for e.g. internet protocol multimedia system (Internet Protocol Multimedia Subsystem, IMS)), typically two per terminal. Moreover, since all data traffic goes to the same PDU session connection, packets such as service heartbeat packets exist for a long time, and the tearing down (releasing) of the PDU session is rarely involved.

However, as the slice function is introduced into the 5G network, there is a correspondence between PDU session connection and slices, and different application services sign up for different slices, the terminal will establish different PDU session connections for them. One common implementation is that a default slice (including an unopened slice) of traffic corresponds to a default PDU session connection, and one terminal needs to maintain multiple PDU session connections if other specific PDU session connections correspond to application traffic subscribed to a specific slice service.

The following problems were found in the test: after the user uses the application service of the signed slice (such as APP for opening the service at the mobile phone end), the PDU session connection is established between the terminal and the network according to the normal flow. After the user exits the service (e.g., APP exiting the service at the handset end), the PDU session connection still exists and is not released. In the scenario where multiple subscribed slices of traffic are used consecutively and then exited, the terminal maintains multiple PDU session connections, but now there is no data transmission on the PDU session connection. The consequence of this problem is that when a terminal registered on a certain slice reaches a maximum, or a PDU session connection established on a certain slice reaches a maximum, the subsequent terminal will no longer be allowed to access or use the slice. That is, the terminal releases the PDU session connection not timely, which will cause slice congestion, and affect other terminals subscribing to the slice to use the slice normally.

Based on this, an exemplary application of the embodiments of the present application in one practical application scenario will be described below.

In the embodiment of the present application, a method for automatically releasing a PDU session connection is provided, which may be applied to a terminal device and a network device, where in the present application, a terminal may determine whether to release a first PDU session connection according to the amount of data transmitted on the first PDU session connection in a certain time. The specific flow is as follows:

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

In some embodiments, the timer may be set by way (1) to (3) and/or set to a first time length:

the mode (1) is as follows: the network configures different timers and corresponding timer durations for the PDU session connection between each network and the terminal by signaling, e.g., configuring the timers for the first PDU session connection and/or configuring the timers for the first duration by related signaling during the first PDU session connection establishment.

The mode (2) is as follows: the terminal and the network determine whether to configure or not configure a timer for the first PDU session connection through negotiation. Specifically, the terminal applies for setting a timer for the first PDU session connection and/or applies for setting the timer to a second duration through signaling, and the network informs the permission terminal to configure or not configure the timer through signaling. The terminal may set the timer to the first duration if configuration is allowed, or the network device may configure the timer to the first duration. For example, the UE applies for configuring a timer for the first PDU session by carrying a specific IE through a related signaling in the process of establishing the first PDU session connection, and the network configures the timer and the first duration through the specific IE in the related signaling in the process of establishing the first PDU session, and does not configure the timer if the UE does not carry the IE.

The mode (3) is as follows: the terminal maintains a timer internally and sets a first duration, which is not known to the network.

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

In some embodiments, the "slice resource occupancy" may be expressed as a ratio of the number of established PDU sessions on the slice to 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, setting a timer for a third duration; when the slice resource occupation ratio is smaller than the second threshold value, setting a timer to be a third duration; and determining the first time length according to the third time length and the fourth time length. Wherein the first threshold is greater than the second threshold and the third duration is less than the fourth duration.

In some embodiments, the terminal may determine a second duration according to 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 according to the type of terminal. Such as: for terminals facing TO enterprises (ToB), the data transmission has certain regularity, after one data transmission is completed, the possibility of burst data transmission is smaller, and the timer can be set TO a smaller value; for a Consumer oriented (TO Consumer, toC) terminal, the data transmission is more flexible, and the timer can be set TO a larger value TO properly extend the time TO maintain the first PDU session connection.

In some embodiments, the terminal may determine a second duration according to a quality of service requirement of the first PDU session connection, and request the network to set the timer to the second duration; or, the network sets the timer to a first duration according to the quality of service requirement of the first PDU session connection. The "quality of service requirement of the first PDU session connection" herein refers to the QoS of the first PDU session connection or the slice type of the first PDU session connection bearer. For example, the slice type carried by the first PDU session connection is URLLC, and the timer can take a value in the first numerical range when there is a large demand for time delay; the slice type carried by the PDU session is mMTC, and if the number of terminals using the slice is large, the timer can take a value in a second numerical range. The values in the first range of values are not smaller than the values in the second range of values.

In some embodiments, the timer is started when the first PDU session connection is established successfully and 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 that PDU session and maintains a timer based on the data transmission status.

In some embodiments, the terminal monitors the uplink and downlink data transmission status of the first PDU session connection, the data transmission status being able to distinguish between at least "data transmission present" and "no data transmission".

In some embodiments, the terminal may 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, and if any one of the DRBs has data transmission, then consider "data transmission on the first PDU session connection"; no data transmission is performed on all DRBs, and the first PDU session connection is considered to be "no data transmission" and "data" contains uplink or downlink data.

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

In some embodiments, after the timer expires, the terminal determines that the first PDU session connection may be released, and the terminal sends a first PDU session connection release request signaling (i.e., an example of the first signaling) for requesting the network to release the first PDU session connection.

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

In step 401a, the terminal requests to establish a first PDU session connection through PDU SESSION ESTABLISHMENT REQUEST signaling (i.e. one example of the second signaling, the sixth signaling or the eighth signaling), and applies for setting a timer in the first PDU SESSION ESTABLISHMENT REQUEST signaling.

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

In some embodiments, the terminal requests the establishment of the PDU session by PDU SESSION ESTABLISHMENT REQUEST signaling, without applying for setting a timer in PDU SESSION ESTABLISHMENT REQUEST signaling. In this embodiment, receiving a fifth signaling sent by the network device; 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;

in step 402a, the network confirms the maximum value of the number of PDU session connections established on the slice and the number of PDU session connections carried by the slice, judges the congestion degree according to the ratio of the number of PDU session connections established on the slice and the number of PDU session connections carried by the slice, and sets a timer to be a first duration. The network establishes a first PDU session connection by issuing PDU SESSION ESTABLISHMENT ACCEPT signaling (i.e., one example of the third signaling, fourth signaling, fifth signaling, seventh signaling, or ninth signaling), while configuring a timer in PDU SESSION ESTABLISHMENT ACCEPT signaling, setting the timer value to a first duration.

In step 403a, the terminal starts a timer after completing the establishment of the first PDU session connection, and the timer runs.

In step 404a, the terminal and the network perform data transmission on the first PDU session connection, and the terminal clears the timer and restarts after sending or receiving at least one data packet.

In step 405a, the terminal and the network stop data transmission on the first PDU session connection and the timer operates normally.

In step 406a, the timer expires after running for a first duration, and the terminal sends PDU SESSION RELEASE REQUEST (i.e. an example of said first signaling) a request to release the first connection.

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

in step 401b, the terminal requests to establish a second PDU session connection (i.e. an example of said second connection) by means of PDU SESSION ESTABLISHMENT REQUEST signalling, and applies for setting a timer in PDU SESSION ESTABLISHMENT REQUEST signalling.

In step 402b, the network establishes a second PDU session connection by issuing PDU SESSION ESTABLISHMENT ACCEPT signaling, while PDU SESSION ESTABLISHMENT ACCEPT signaling does not carry a timer related IE.

In step 403b, the terminal does not set a timer for the second PDU session connection after the second PDU session connection is established.

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

in step 401c, the terminal requests to establish a first PDU session connection through PDU SESSION ESTABLISHMENT REQUEST signaling.

In step 402c, the network establishes the PDU session by issuing PDU SESSION ESTABLISHMENT ACCEPT signaling.

In step 403c, the terminal starts a timer after the first PDU session is established, and sets the timer to be the first duration.

In step 404c, the terminal and the network perform data transmission on the first PDU session connection, and the terminal clears the timer and restarts when at least one data packet is sent or received.

In step 405c, the terminal and the network stop data transmission on the first PDU session connection, and the timer operates normally.

In step 406c, the timer expires when it is run for a first duration, and the terminal sends PDU SESSION RELEASE REQUEST a request to release the first PDU session connection.

The embodiment of the application provides a method and a device for automatically releasing PDU session connection, which are applied to a terminal and a network, and judge whether the first PDU session connection needs to be released according to the data quantity transmitted on the first PDU session connection within a certain 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 by signaling whether to set the timer and the value of the timer. The timer value may be set according to a slice resource occupation ratio corresponding to the first PDU session connection, or a terminal type, or a service quality requirement of the first PDU session connection.

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

In some embodiments, the network signals to the terminal whether the first PDU session connection sets a timer and/or sets the timer to a 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 expires.

The method provided by the embodiment of the invention can timely release the PDU session connection which is not needed to be used, especially in a slicing application scene, the condition that one terminal maintains a plurality of PDU session connections is easy to occur, the PDU session connection resource can be used more flexibly, and the IP address resource is saved.

The method provided by the embodiment of the invention can solve the problem that the PDU session connection established on a slice reaches the upper limit due to the fact that the PDU session connection is released by the terminal in time, so that other terminals subscribing the slice cannot access.

The scheme of the embodiment of the application is simple to realize, can be realized at the communication level, does not relate to interface design of an application layer and a communication layer, and is easy to realize at the terminal side.

It should be noted that although the steps of the methods in the present application are depicted in the accompanying drawings in a particular order, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to be performed, and/or one step decomposed into multiple steps to be performed, etc.; or, the steps in different embodiments are combined into a new technical scheme.

Based on the foregoing embodiments, the embodiments of the present application provide a session management apparatus, where the session management apparatus includes each module included, and each unit included in each module may be implemented by a processor; of course, the method can also be realized by a specific logic circuit; in an implementation, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.

Fig. 5 is a schematic structural diagram of a session management apparatus provided in an embodiment of the present application, as shown in fig. 5, the apparatus 50 includes a starting module 51 and a sending module 52, where:

a starting module 51 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;

a first sending module 52, configured to send, to a network device, first signaling for requesting to release the first connection, 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.

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

In some embodiments, the session management apparatus 50 further comprises a stopping module for stopping the timer; the starting module 51 is further configured to restart the cleared timer.

In some embodiments, the first time period is determined according to at least one of: slice resource occupation; a terminal type; the quality of service requirement of the first connection.

In some embodiments, the first sending module 52 is further 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 further comprises a second receiving module, which is used for 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; the session management device further comprises a setting module, wherein the setting module is used for setting the timer to the first duration when the third signaling is used for indicating to set the timer and the duration of the timer is not indicated to be set.

In some embodiments, the second signaling is further for requesting that the timer be set to a second duration; the second receiving module is further configured to receive a fourth signaling sent by the network device; 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; the setting module is further configured to set the timer to the first duration when the fourth signaling is used to indicate setting of the timer and no duration for setting of the timer is indicated; wherein the first time period is determined based at least on the second time period.

In some embodiments, the second receiving module is further configured to receive fifth signaling sent by the network device, where the setting of the timer is not requested to the network device; 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. And setting the timer to the first duration in the case that the fifth signaling is used to indicate setting of the timer and no indication is made of the duration of setting the timer; the setting module is further configured to set the timer to the first duration when the setting of the timer is not requested to the network device and the setting of the timer is not indicated by the network device.

In some embodiments, the first sending module 52 is further configured to send a sixth signaling to the network device, where the sixth signaling is used to request the establishment of the first connection and to request the setting of the timer; the second receiving module is further configured to receive a seventh signaling sent by the network device, where the seventh signaling is used to instruct the terminal device to establish the first connection; in case no IE related to the timer is carried in the seventh signaling, the timer is not set for the first connection.

In some embodiments, the terminal type includes at least one of: a ToB terminal; and (3) ToC terminal.

In some embodiments, the quality of service requirement of the first connection includes QoS of the first connection and/or a slice type of the first connection bearer.

Fig. 6 is a schematic structural diagram of a session management apparatus according to an embodiment of the present application, as shown in fig. 6, the apparatus 60 includes a first receiving module 61 and a releasing module 62, where:

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.

In some embodiments, the first receiving module 61 is further configured to receive a 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, configured to send a third signaling to the terminal device, where the third signaling is used to instruct setting the timer, or is used to instruct setting the timer and setting the timer to the first duration.

In some embodiments, the second signaling is further for requesting that the timer be set to a second duration; the second sending module is further configured to send a fourth signaling to the terminal device, where the fourth signaling is used to instruct setting of the timer, or instruct setting of the timer and setting of the timer to the first duration.

In some embodiments, the second sending module is further configured to send a fifth signaling to the terminal device if the request for setting the timer by the terminal device 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.

In some embodiments, the first receiving module 61 is further configured to receive a sixth signaling sent by the terminal device, where the sixth signaling is used to request to establish the second connection; the second sending module is further configured to send a seventh signaling to the terminal device, where the seventh signaling is used to instruct to establish the second connection with the terminal device; in case no IE related to the timer is carried in the seventh signaling, the terminal does not set the timer for the second connection.

The description of the apparatus embodiments above is similar to that of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

It should be noted that, in the embodiments of the present application, the division of modules by the session management device shown in fig. 5 and fig. 6 is schematic, and is merely a logic function division, and there may be another division manner in actual implementation. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units. Or in a combination of software and hardware.

It should be noted that, in the embodiment of the present application, if the method is implemented in the form of a software functional module, and sold or used as a separate product, the method may also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or part contributing to the related art, and the computer software product may be stored in a storage medium, including several instructions for causing a terminal device and a network device to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, an optical disk, or other various media capable of storing program codes. Thus, 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, fig. 7 is a schematic diagram of a hardware entity of an electronic device according to an embodiment of the present application, as shown in fig. 7, the electronic device 70 includes a memory 71 and a processor 72, where the memory 71 stores a computer program that can be run on the processor 72, and the processor 72 implements steps in a method provided in the foregoing embodiment when executing the program.

It should be noted that the memory 71 is configured to store instructions and applications executable by the processor 72, and may also be implemented by a FLASH memory (FLASH) or a random access memory (Random Access Memory, RAM), and may also cache data (e.g., image data, audio data, voice communication data, and video communication data) to be processed or already processed by each module in the processor 72 and the electronic device 70.

An embodiment of the present application provides a network device, fig. 8 is a schematic diagram of hardware entities of an electronic device according to an embodiment of the present application, as shown in fig. 8, where the electronic device 80 includes a memory 81 and a processor 82, where the memory 81 stores a computer program that can be run on the processor 82, and the processor 82 implements steps in the method provided in the foregoing embodiment when executing the program.

It should be noted that the memory 81 is configured to store instructions and applications executable by the processor 82, and may also cache data (e.g., image data, audio data, voice communication data, and video communication data) to be processed or already processed by each module in the processor 82 and the electronic device 80, which may be implemented by a FLASH memory (FLASH) or a random access memory (Random Access Memory, RAM).

The present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps in the session management method provided in the above embodiment.

The present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the steps of the session management method provided by the method embodiments described above.

It should be noted here that: the description of the storage medium and apparatus embodiments above is similar to that of the method embodiments described above, with similar benefits as the method embodiments. For technical details not disclosed in the storage medium, storage medium and device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" or "some embodiments" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "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 various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application. The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments. The foregoing description of various embodiments is intended to highlight differences between the various embodiments, which may be the same or similar to each other by reference, and is not repeated herein for the sake of brevity.

The term "and/or" is herein merely an association relation describing associated objects, meaning that there may be three relations, e.g. object a and/or object B, may represent: there are three cases where object a alone exists, object a and object B together, and object B alone exists.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments are merely illustrative, and the division of the modules is merely a logical function division, and other divisions may be implemented in practice, such as: multiple modules or components may be combined, or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or modules, whether electrically, mechanically, or otherwise.

The modules described above as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules; can be located in one place or distributed to a plurality of network units; some or all of the modules may 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 may be integrated in one processing unit, or each module may be separately used as one unit, or two or more modules may be integrated in one unit; the integrated modules may be implemented in hardware or in hardware plus software functional units.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, where the program, when executed, performs steps including the above method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read Only Memory (ROM), a magnetic disk or an optical disk, or the like, which can store program codes.

Alternatively, the integrated units described above may be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or part contributing to the related art, and the computer software product may be stored in a storage medium, including several instructions for causing a terminal device and a network device to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.

The methods disclosed in the several method embodiments provided in the present application may be arbitrarily combined without collision to obtain a new method embodiment.

The features disclosed in the several product embodiments provided in the present application may be combined arbitrarily without conflict to obtain new product embodiments.

The features disclosed in the several method or apparatus embodiments provided in the present application may be arbitrarily combined without conflict to obtain new method embodiments or apparatus embodiments.

The foregoing is merely an embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

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;

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 release module for releasing 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.