WO2022227010A1

WO2022227010A1 - Method for managing protocol data unit session, and device

Info

Publication number: WO2022227010A1
Application number: PCT/CN2021/091512
Authority: WO
Inventors: 赵鹏涛; 李岩
Original assignee: 华为技术有限公司
Priority date: 2021-04-30
Filing date: 2021-04-30
Publication date: 2022-11-03

Abstract

The present application provides a method for managing a protocol data unit session, and a communication device. The method comprises: a session management function network element sends first information to a first data transmission device, the first information indicating that a protocol data unit session will be released; the session management function network element determines that the transmission control protocol connection between the first data transmission device and a second data transmission device has been released according to the first information, the transmission control protocol connection bearing a breakpoint resume service, and the protocol data unit session comprising the transmission control protocol connection; and the session management function network element releases the protocol data unit session. The first data transmission device receives the first information and releases the transmission control protocol connection according to the first information. The communication method and device provided by the present application can reduce the waste of air interface resources and prevent an increase in the transmission delay at a breakpoint part.

Description

Method and apparatus for managing protocol data unit sessions

technical field

The present application relates to the field of communications, and, more particularly, to methods and apparatus for managing protocol data unit sessions.

Background technique

The protocol data unit (PDU) session in service and session continuity mode 2 (SSC mode 2) in 3GPP TS 23.502 cannot guarantee service continuity for terminal equipment. When the network determines that the user plane function (UPF) of the anchor point needs to be changed (for example, the routing path of the anchor point UPF is too long relative to the current location of the terminal device), the network will trigger the release of the current PDU session and indicate The terminal device establishes a new PDU session, and selects a new anchor point UPF in the process of establishing the new PDU session, so that the routing path of the new session is more optimized. This way of establishing a PDU session is also called "break-before-build". However, this "break first and then build" will cause the transmission control protocol (Transmission Control Protocol, TCP) connection on the original PDU session to be hard interrupted, and the state of the application server and the terminal device cannot be synchronized, which may lead to the successful transmission of data and TCP connections. The repeated transmission of undelivered data on the Internet wastes air interface resources and increases the transmission delay of the breakpoint part.

SUMMARY OF THE INVENTION

The present application provides a method and device for managing a protocol data unit session, which can synchronize the transmission and reception status of a transmission control protocol connection between a terminal device and an application server, reduce the waste of air interface resources, and avoid the increase in transmission delay of the resumed transmission service. big.

A first aspect provides a method for managing a protocol data unit session, comprising: a session management function network element sending first information to a first data transmission device, the first information indicating that the protocol data unit session will be released; The element determines that the transmission control protocol connection between the first data transmission device and the second data transmission device has been released according to the first information, the transmission control protocol connection bears the resume transmission service, and the protocol data unit session includes the transmission control protocol connection; session management The functional network element releases the protocol data unit session.

The first data transmission device may be a terminal device, and the second data transmission device may be an application server, or, the first data transmission device may be an application server, and the second data transmission device may be a terminal device.

According to the communication method provided by the present application, the first data transmission device and the second data transmission can be synchronized by notifying the first data transmission device to disconnect the transmission control protocol connection carrying the resumed transmission service before the protocol data unit session is disconnected. The transmission control protocol connection transceiver status of the device. Since the transmission and reception status of the transmission control protocol connection of the first data transmission device and the second data transmission device are synchronized, retransmission of successfully transmitted data is avoided, and because the transmission control protocol connection release process is actively executed, it is avoided that the transmission control protocol connection is not delivered on the connection. data retransmission. The waste of air interface resources can be reduced, and the transmission delay of the breakpoint part can be avoided from increasing.

With reference to the first aspect, in some implementations of the first aspect, the first information may be sent to the first data transmission device through the user plane, the session management function network element sends the first information through the user plane function network element, and the first information It is included in the packet header of the data packet of the user plane functional network element.

In this implementation manner, one manner may be that the session management function network element sends the first information to the user plane function network element, and the user plane management function network element directly includes the first information in the header of the data packet. Another way may be that the session management function network element sends the first signaling to the user plane function network element, the user plane function network element generates the first information through the first signaling, and includes the first information in the packet header of the data packet middle.

With reference to the first aspect, in some implementations of the first aspect, when the session management function network element sends the first information to the first data transmission device through the control plane or the user, the session management function network element determines the first data transmission device The transmission control protocol connection with the second data transmission device has been released according to the first information, including:

The session function management network element starts a timer after sending the first information, and when the first time elapses after the first information is sent, it is determined that the transmission control protocol connection has been released according to the first information.

With reference to the first aspect, in some implementations of the first aspect, when the session management function network element sends the first information by controlling the terminal device or the application server, the session management function network element determines the relationship between the terminal device and the application server. The TP connection has been released according to the first information, including:

The session function management network element receives the first feedback information from the terminal device or the application server, where the first feedback information indicates that the transmission control protocol connection has been released according to the first information.

In a second aspect, a method for managing a protocol data unit session is provided, comprising: a first data transmission device receiving first information sent from a network element with a session management function, the first information indicating that the first protocol data unit session will be released; The first data transmission device determines that the transmission control protocol connection between the first data transmission device and the second data transmission device bears the resume-break service, and the protocol data unit session includes the transmission control protocol connection; the first data transmission device according to the first information , to release the Transmission Control Protocol connection.

According to the communication method provided by the present application, the first data transmission device and the second data transmission can be synchronized by notifying the first data transmission device to disconnect the transmission control protocol connection carrying the resumed transmission service before the protocol data unit session is disconnected. Transmit and receive status of the TP connection between the devices. Since the transmission and reception status of the transmission control protocol connection between the first data transmission device and the second data transmission device is synchronized, retransmission of successfully transmitted data is avoided, and because the transmission control protocol connection release process is actively executed, it is avoided that the transmission control protocol connection is not sent on the connection. Retransmission of data. The waste of air interface resources can be reduced, and the transmission delay of the breakpoint part can be avoided from increasing.

With reference to the second aspect, in some implementations of the second aspect, when the first information is sent through the control plane, the first data transmission device sends the first feedback information to the session management network element after releasing the transmission control protocol connection, and the first data transmission device sends the first feedback information to the session management network element. A feedback message indicates that the Transmission Control Protocol connection has been released. The transmission control protocol connection is a transmission control protocol connection between the first data transmission device and the second data transmission device that bears the resumed transmission service.

In combination with the second aspect, in some implementations of the second aspect, when the first information is sent through the user plane, the first data transmission device decapsulates the data packet to receive the first information, and further, releases the transmission control according to the first information protocol connection.

The release of the TP connection can be initiated by the terminal device alone or by the application server alone.

In a third aspect, a communication apparatus is provided, which includes a unit for performing each step of the communication method in any one of the first and second aspects and implementations thereof.

In one design, the communication device is a communication chip, which may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

In another design, the communication device is a communication device (eg, terminal device or network device, etc.), and the communication chip may include a transmitter for sending information or data, and a receiver for receiving information or data.

In a fourth aspect, a communication device is provided, including a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device executes the above-mentioned first aspect and A communication method in any of the second aspects and implementations thereof.

Optionally, there are one or more processors and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

Optionally, the communication device further includes a transmitter (transmitter) and a receiver (receiver).

In a fifth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code, or instructions), which, when the computer program is executed, causes a computer to execute the first aspect and the first aspect above. Any one of the two aspects and a communication method in each of its implementations.

In a sixth aspect, a computer-readable medium is provided, the computer-readable medium stores a computer program (also referred to as code, or instruction), when it runs on a computer, causing the computer to execute the above-mentioned first aspect and the first aspect. Any one of the two aspects and a communication method in each of its implementations.

In a seventh aspect, a chip system is provided, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device installed with the chip system executes the above-mentioned A communication method in any of the first and second aspects and implementations thereof.

Wherein, the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

Description of drawings

FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present application.

FIG. 2 is a schematic diagram of an application scenario of an embodiment of the present application.

FIG. 3 is a schematic diagram of another application scenario of the embodiment of the present application.

FIG. 4 is a schematic diagram of a process of changing the anchor point UPF under SSC mode 2 according to an embodiment of the present application.

FIG. 5 is a schematic diagram of a flow of establishing a TCP connection according to an embodiment of the present application.

FIG. 6 is a schematic diagram of a process of releasing a TCP connection according to an embodiment of the present application.

FIG. 7 is a schematic interaction diagram of an example of a method for managing a PDU session according to an embodiment of the present application.

FIG. 8 is a schematic interaction diagram of another example of a method for managing a PDU session according to an embodiment of the present application.

FIG. 9 is a schematic interaction diagram of another example of a method for managing a PDU session according to an embodiment of the present application.

FIG. 10 is a schematic interaction diagram of another example of a method for managing a PDU session according to an embodiment of the present application.

FIG. 11 is a schematic diagram of a communication apparatus according to an embodiment of the present application.

FIG. 12 is a schematic diagram of another communication device according to an embodiment of the present application.

Detailed ways

The technical solutions in the present application will be described below with reference to the accompanying drawings. As used in this application, the terms "component," "module," "system," etc. are used to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be components. One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a wideband Code Division Multiple Access (CDMA) system (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) system, LTE Frequency Division Duplex (Frequency Division Duplex, FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) System or New Radio (New Radio, NR), etc.

The terminal device in this embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or user device. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or future evolved Public Land Mobile Networks (PLMN) A terminal device, etc., is not limited in this embodiment of the present application.

Fig. 1 is a network architecture applied to an embodiment of the present application, which is a schematic diagram of a 5G network architecture based on a point-to-point interface, which can be divided into three parts, namely user equipment (user equipment, UE), data network (data network, DN) and operation Each network element that may be involved in the network architecture will be described separately. Terminal equipment: refers to network terminal equipment, such as mobile phones, Internet of Things terminal equipment, etc.

RAN (Radio Access Network, Radio Access Network): A device that provides wireless access for terminal devices, including but not limited to gNodeB, eNodeB, WiFi AP, WiMAX BS, etc.

AMF (Access and Mobility management Function): It is mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user switching, etc.

SMF (Session Management Function): It is mainly responsible for session management (such as session establishment, modification, and release) in the mobile network, IP address allocation and management, and UPF selection and control.

PCF (Policy Control Function, policy control function): responsible for the generation of terminal equipment access policies and quality of service (quality of service, QoS) flow control policies.

UDM (Unified Data Management): Responsible for managing subscription data, and notifying the corresponding network element when the subscription data is modified.

AUSF (Authentication Server Function): Responsible for authorizing users to access 5G networks.

NEF (Network Exposure Function): Provide 5G network capabilities and events to the outside world, and receive related external messages.

UDR (Unified Data Repository): Provides storage capabilities for contract data, policy data, and data related to capability opening.

NRF (Network Repository Function): Provides registration and discovery capabilities for network elements in 5G networks.

AF (Application Function): Responsible for providing services to the 3GPP network, such as affecting service routing, interacting with PCF for policy control, etc.

UPF (User Plane Function, user plane function): Provides user plane functions such as forwarding, processing, connection with DN, session anchor, and QoS policy execution of user packets.

DN (Data Network, data network): refers to a specific data service network that terminal equipment accesses. The DN is identified by the Data Network Name (DNN) in the 5G network. Typical DNs include Internet, IMS (IP Multi-media Service, IP Multimedia Service) networks, etc.

The operator network may include one or more of the following network elements: Authentication Server Function (AUSF) network element, Network Exposure Function (Network Exposure Function, NEF) network element, Policy Control Function (Policy Control Function, PCF) network element, Unified Data Management (UDM) network element, Unified Data Repository (UDR), Network Repository Function (NRF) network element, Application Function (AF) network element element, access and mobility management function (Access and Mobility Management Function, AMF) network element, session management function (Session Management Function, SMF) network element, radio access network (Radio Access Network, RAN) and user plane functions ( User Plane Function, UPF) network element, etc. In the above-mentioned operator network, the part other than the RAN may be referred to as the core network part.

It should be noted that the above-mentioned "network element" may also be referred to as an entity, a device, an apparatus, or a module, etc., which is not particularly limited in this application. In addition, in this application, in order to facilitate understanding and description, the description of "network element" is omitted in some descriptions. For example, the NEF network element is abbreviated as NEF. In this case, the "NEF" should be understood as the NEF network element or NEF entity, hereinafter, the description of the same or similar situations is omitted.

It should be noted that the name of each network element included in FIG. 1 is only a name, and the name does not limit the function of the network element itself. In the 5G network and other future networks, the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, or other names, etc., which will be uniformly described here, and will not be repeated below.

It should be noted that each network element in FIG. 1 does not necessarily exist at the same time, and which network elements are required can be determined according to requirements. The connection relationship between each network element in FIG. 1 is not uniquely determined, and can be adjusted according to requirements.

It can be understood that the above network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).

FIG. 2 shows a schematic diagram of an application scenario of an embodiment of the present application. As shown in Figure 2, it is a typical service and session continuity mode 2 (service and session continuity mode 2, SSC mode 2) business scenario.

FIG. 3 shows a schematic diagram of still another application scenario of the embodiment of the present application. The SSC mode 2 service scenario shown in Figure 3 involves AS migration in the same DN.

The functions of network elements or modules that may be involved in the scenarios of Figures 2 and 3 are as follows:

RAN: Used to implement wireless-related functions.

AMF: Responsible for user mobility management, including mobility status management, assigning user temporary identities, authenticating and authorizing users.

SMF: It is mainly responsible for session management (such as session establishment, modification, and release) in the mobile network, IP address allocation and management, and UPF selection and control.

PCF: Responsible for the generation of terminal device access policies and quality of service (QoS) flow control policies.

UDM: Responsible for managing subscription data, and informing the corresponding network element when the subscription data is modified.

AF: Responsible for providing services to the 3GPP network, such as affecting service routing, interacting with PCF for policy control, etc.

UPF: Provides user plane functions such as user packet forwarding, processing, connection to DN, session anchor, and QoS policy enforcement.

DN: refers to a specific data service network that terminal equipment accesses. The DN is identified by the data network name (DNN) in the 5G network. Typical DNs include Internet, IMS (IP Multi-media Service, IP Multimedia Service) networks, etc.

In order to describe the technical solution, the following will introduce the PDU session anchor point change process and the Transmission Control Protocol (Transmission Control Protocol, TCP) connection establishment and release process with reference to the accompanying drawings.

The following will specifically describe the process of changing the anchor point UPF under SSC mode 2 in the embodiment of the present application with reference to FIG. 4 . PDU sessions in this mode cannot guarantee service continuity for terminal equipment. The process includes the following steps:

1. The SMF decides to perform UPF reselection, that is, when the network determines that the UPF of the anchor point needs to be changed (for example, the routing path of the anchor point UPF is too long relative to the current position of the terminal device).

2. The network triggers the release of the current PDU session, and the path of the current PUD session is UPF1.

3. PDU session reconstruction, the terminal device establishes a new PDU session, and selects a new anchor point UPF2 in the process of establishing the new PDU session, so that the routing path of the new session is more optimized.

This way of establishing a PDU session is also called "break-before-build".

SSC mode 2 can carry services such as resumable uploading from breakpoints. Resuming uploading from breakpoints is to artificially divide the task (a file or compressed package) into several parts during uploading/downloading, and each part uses a thread for uploading/downloading , if you encounter a network failure, you can continue uploading/downloading the unfinished part from the part that has already been uploaded/downloaded, instead of having to start uploading/downloading from the beginning. Save time and increase speed. Common upload/download software that supports resumed uploads: QQ whirlwind, Xunlei, Kuaiche, eMule, Ku6, Tudou, Youku, Baidu Video, Sina Video, Tencent Video, Baidu Cloud, etc.

On any PDU session under SSC mode 2, there are one or more TCP connections, which will be described below.

TCP provides a connection-oriented reliable byte stream service. Connection-oriented means that two applications using TCP must establish a TCP connection before exchanging data with each other. TCP uses "ports" to identify application processes at the source and destination. The port number can use any number between 0 and 65535. When a service request is received, the operating system dynamically assigns a port number to the client's application. On the server side, each service provides services to users on a "Well-Know Port".

There are fields used in the establishment and release of TCP connections in the TCP flag. The functions of each field are as follows:

(1) URG: When it is 1, the emergency pointer is valid.

(2) ACK: When it is 1, the confirmation serial number is valid.

(3) PSH: When it is 1, the receiver should hand over this segment to the application layer as soon as possible.

(4) RST: When it is 1, the connection is rebuilt.

(5) SYN: When it is 1, the program is synchronized and a connection is initiated.

(6) FIN: When it is 1, the sender completes the task and releases a connection.

The following will specifically describe a process for establishing a TCP connection and a process for releasing a TCP connection in this embodiment of the present application with reference to FIG. 5 and FIG. 6 .

Figure 5 shows the flow of establishing a TCP connection. As shown in the figure, establishing a TCP connection has the following process:

1. The requester (client) sends a connection request message to the server: SYN=1, seq=x. At the initial moment, both the client and the server are in a closed state. When the client needs to send a data packet to the server, the client actively opens the connection. At this time, the server is notified to let the server also open the connection, so the server opens the connection passively. After the connection is opened, the server enters the listening state, waiting for the connection request from the client. The client also begins to prepare connection request packets and starts sending them. The first data packet sent by the client is a connection request segment. The content of this message is as shown in the figure. It is a synchronization bit SYN=1, and the other is an initial sequence number seq=x. TCP stipulates that a segment with SYN=1 cannot carry data, but consumes a sequence number. After the client sends this message, it enters the synchronous sent state.

2. After receiving the connection request message, the server sends an acknowledgement message to the client: SYN=1, ACK=1, seq=y, ack=x+1. After the server receives the connection request message, it knows that a client requests a connection. If there are currently resources available and the connection can be approved, a confirmation message will be sent to the client. The contents of this confirmation message are: SYN=1 (no change), seq=y (serial number of the server), newly added ACK=1, ack=x+1 (serial number of the client+1). Here SYN=1, so the message cannot carry data, which also consumes a sequence number of the server. Then the server enters the synchronous reception state.

3. After the client receives the acknowledgment message, it sends a client acknowledgment message to the server: ACK=1, seq=x+1, ack=y+1. After the client sends the confirmation message, the client enters the established connection state, and the server also enters the connected state after receiving the confirmation message from the client.

These three message segments complete the establishment of the connection, and the establishment of the connection can only be initiated by the client. In our embodiment, the client can be a terminal device, the server can be an application server, and one terminal device can establish multiple TCP connections with multiple application servers, respectively carrying different tasks.

Figure 6 shows the release flow of the TCP connection. As shown in Figure 6, releasing a TCP connection has the following process:

1. The client sends a connection release request message to the server: FIN=1, seq=u. When the TCP connection needs to be released, both the client and the server are in the established connection state. At this time, after the client data is sent, it wants to end the connection and actively sends out a connection release request packet. The content of the packet is: FIN= 1, seq=u (this u is the sequence number of a data packet before this data packet + 1), and then the client enters the termination waiting state of 1, no longer sends data packets, and waits for the server to confirm.

2. After the server receives the connection release request packet, it sends an acknowledgment packet to the client: ACK=1, seq=v, ack=u+1 (this v is the sequence number+1 of the last data packet sent by the server ). After the server sends the confirmation message, it enters the shutdown waiting state. At this time, the connection between the client and the server has ended, but TCP is full-duplex communication, because it is the end initiated by the client at this time, and there may still exist on the server side. The data is not completely sent to the client, so the server to the client is still not over, the client no longer sends data, but the server has data to send, and the client can still receive it. The client receives the confirmation message from the server and enters the termination waiting state 2.

3. The server sends a connection release message to the client: FIN=1, ACK=1, seq=w, ack=u+1. Finally, after there is no data to be sent, the server sends a connection release packet, the content of this packet: FIN=1, ACK=1, seq=w (because the server replies to the client's connection request (the sequence number of the packet is v) After that, there may still be other data packets to be sent, so the w here is not necessarily v+1), ack=u+1 (the acknowledgment number is the same as the acknowledgment number of the last reply to the client's request to release the connection). Then the server enters the final confirmation state and waits for the confirmation of the client.

4. After receiving the connection release message from the server, the client sends an acknowledgement message: ACK=1, seq=u+1, ack=w+1. Then the client enters the time waiting state. At this time, the TCP connection has not been released. The client still needs to wait for the time set by the timer for the two longest segment lifetimes before the client enters the shutdown state. It should be noted that the longest segment lifetime may be 2 minutes.

As can be seen from Figure 5 and Figure 6, the establishment and release of the TCP connection are not completed in one step.

The release of the TCP connection can be initiated by the server or by the client.

A method 700 for managing a PDU session provided by an embodiment of the present application will be described below with reference to FIG. 7 . The method 700 includes:

S710, SMF1 decides to perform UPF reselection.

S720, the SMF1 sends the first information to the first data transmission apparatus.

In a possible implementation manner, the first information indicates that the PDU session will be released, and indirectly instructs the first data transmission apparatus to release the TCP connection according to the first information.

In a possible implementation manner, the first information may directly instruct the first data transmission apparatus to release the TCP connection.

It should be noted that the TCP connection is between the first data transmission device and the second data transmission device, and bears the resume transmission service, and the PDU session includes a TCP connection. In other words, the TCP connection included in the PDU session is a bearer The transmission of the continuous transmission type service between the first data transmission device and the second data transmission device.

Preferably, the first data transmission device may be a terminal device, the second data transmission device may be an application server, or the first data transmission device may be an application server, and the first data transmission device may be a terminal device.

It should be noted that the first data transmission device and the second data transmission device may also be other data transmission devices, which are not limited in this application.

S730, the first data transmission apparatus receives the first information, and further releases the TCP connection according to the first information.

In a possible implementation manner, the first data transmission apparatus receives the first information through the control plane, and further releases the TCP connection according to the first information.

In a possible implementation manner, the first data transmission apparatus receives the first information through the user plane decapsulation data packet, and further releases the TCP connection according to the first information.

S740, SMF1 determines that the TCP connection has been released, and further, SMF1 releases the PDU session.

It should be noted that there are at least two possible ways for SMF1 to determine that a TCP connection has been released:

In a possible implementation manner, SMF1 indirectly determines that the TCP connection is released, and starts a timer after sending the first information. When the first time elapses, the default TCP connection of SMF1 is released, and the first time is the default TCP connection of SMF1 time required to be released.

In a possible implementation manner, the SMF1 directly determines that the TCP connection is released, the SMF1 receives the first feedback information sent from the first data transmission device or the second data transmission device, and the SMF1 determines that the TCP connection is released.

It should be noted that when the SMF1 sends the first information through the control plane, it may determine that the TCP connection has been released by starting a timer, or may determine that the TCP connection has been released by receiving the first feedback information. When the SMF1 sends the first information through the user plane data packet, it may determine that the TCP connection has been released by starting a timer.

It should be noted that when the SMF1 determines that the TCP connection is released, it executes the release of the PDU session.

A method 800 for managing a PDU session provided by an embodiment of the present application will be described below with reference to FIG. 8 . The method 800 includes:

S810, SMF1 decides to perform UPF reselection.

S820, the SMF1 sends the first information to the terminal device.

Optionally, the first information indicates that the PDU session is about to be released, and indirectly instructs the terminal device to release the TCP connection, where the TCP connection is a TCP connection between the terminal device and the application server that bears the resumed transmission service, and the TCP connection belongs to the PDU session. .

Optionally, the first information directly instructs the terminal device to release the TCP connection.

As an example and not a limitation, the content of the first information may be PDU Session Modification Command.

It should be noted that the SMF1 may send the first information to the terminal device through the AMF. As an example and not a limitation, the SMF1 may send the first information through the Namf_Communication_N1N2MessageTransfer service of the AMF.

It should be noted that this PDU session is a PDU session for which SMF1 decides to perform UPF reselection.

S830, the terminal device receives the first information, and further releases the TCP connection according to the first information.

It should be noted that one PDU session corresponds to one terminal device, and one terminal device has at least one TCP connection, which are respectively connected to different application servers and carry different services, some of which are of the type of continuous transmission.

In a possible implementation manner, when the terminal device receives the first information, it immediately sends second feedback information to SMF1 through the AMF, and then releases the TCP connection according to the first information. The second feedback information indicates that the terminal device has received the first information. a message.

As an example and not a limitation, the second feedback information may be Ack, and the second feedback information is used to notify the SMF1 terminal device that the first information has been received.

In a possible implementation manner, after receiving the first information, the terminal device initiates a process of releasing the TCP connection according to the first information, and after the TCP connection is released, it sends first feedback information to SMF1, the first feedback information Indicates that the TCP connection has been released, by way of example and not limitation, the first feedback information may be Ack.

S840, SMF1 determines that the TCP connection has been released, and further, SMF1 releases the PDU session.

In a possible implementation manner, the SMF1 starts a timer after sending the first information in step S820. As an example and not a limitation, the timer may be a UPF relocation timer. When the timer elapses for the first time, SMF1 determines that the TCP connection has been released, which is an indirect determination. SMF1 defaults that after the first time has elapsed, the TCP connection has been released, and then initiates the release of the PDU session.

In a possible implementation manner, the SMF1 starts a timer after receiving the second feedback information in step S830. As an example and not a limitation, the timer may be a UPF relocation timer. When the timer elapses for the first time, the SMF1 determines that the TCP connection has been released, which is an indirect determination. SMF1 defaults that after the first time elapses, the TCP connection has been released, and then initiates the release of the PDU session.

In a possible implementation manner, the SMF1 receives the first feedback information from the terminal device, directly determines that the TCP connection has been released, and then initiates the release of the PDU session.

The release of the PDU session specifically includes: as an example but not a limitation, the SMF1 can send the N1 SM Information to the terminal device by calling the Namf_Communication_N1N2MessageTransfer service of the AMF, and the N1 SM Information contains a PDU session release instruction, which includes the PDU session ID and the re-established PDU session. to the same DN. The network and the terminal device complete the process of releasing the original PDU session. The terminal device receives the PDU session release instruction, generates a new PDU session ID, and initiates a PDU session establishment process. AMF selects SMF2, and SMF2 selects UPF2. The network and the terminal device complete the re-establishment of the PDU session of SSC mode 2.

It should be noted that the SMF1 and SMF2 are only exemplary, representing the session management function network element of the original PDU session and the session management function network element of the re-established PDU session, which may also be represented by SMF3 or the like.

It should be noted that the UPF2 is only exemplary, and represents a newly created PDU session path, and may also be represented by UPF3 or the like.

In this embodiment, the SMF notifies the terminal device through the control plane that the network should release the original PDU session, perform UPF reselection, and create a new PDU session to connect to the same DN. After receiving the notification, the terminal device actively executes the release process of the TCP connection carrying the resumed transmission service on the PDU session, and synchronizes the TCP sending and receiving status between the terminal device and the application server. Due to the synchronization of the sending and receiving status of the TCP connection between the terminal device and the application server, the retransmission of successfully transmitted data is avoided, and the retransmission of undelivered data on the TCP connection is avoided due to the active execution of the TCP connection release process. The method of this embodiment can reduce the waste of air interface resources and avoid increasing the transmission delay of the breakpoint part.

A method 900 for managing a PDU session provided by an embodiment of the present application will be described below with reference to FIG. 9 . The method 900 includes:

S910, SMF1 decides to perform UPF reselection.

S920, the SMF1 sends the first information to the application server.

Optionally, the first information indicates that the PDU session is about to be released, and indirectly instructs the application server to release the TCP connection. PDU session.

Optionally, the first information directly instructs the application server to release the TCP connection.

It should be noted that the SMF1 sends the first information to the application server, and the first information may actually be received by the application function network element in the application server. The application function network element is mainly responsible for the control plane function and interacts with the 5G core network. The application server is mainly responsible for It is responsible for user plane functions and transmits service data with terminal devices.

It should be noted that, one PDU session corresponds to one terminal device, and one terminal device can be connected to at least one application server through at least one TCP connection, and some of the at least one TCP connection bears the resume transmission service, and some bears other services. In the embodiment of the present application, the TCP connection is located between the terminal device and the application server, and bears the resumed transmission service from a breakpoint.

In a possible implementation manner, the SMF1 sends the first information to all associated application servers through the control plane, and the application server determines whether the connection between it and the terminal device is a TCP connection carrying a resume-break service, and if it is a TCP connection The connection initiates the release, and if it is another TCP connection, the first information may be ignored and the release is not initiated.

In a possible implementation manner, the SMF1 sends the first information through the control plane to the application server carrying the resumed transmission service, in other words, the connection between the SMF1 and the terminal device is directly sent as a TCP connection It should be noted that if the application server provides enough information about itself when subscribing to the SMF1 for the first information, the SMF1 can only send the first information to the application server carrying the resumed transmission service.

By way of example and not limitation, SMF1 may send the first information through the Nsmf_EventExposure_Notify service.

Optionally, the SMF1 may directly send the first information to all associated application servers or application servers carrying the resume-break service.

Optionally, the SMF1 may send the first information to the NEF, and forward the first information to all associated application servers or application servers that carry the resume-break service through the NEF.

It should be noted that the first information is subscribed to the SMF1 by the application server in advance.

As an example and not a limitation, the first information is subscribed when all associated application servers subscribe to SMF1 for early notification information.

Optionally, when subscribing to SMF1 for the first information, the application server carrying the resume-break service also indicates that SMF1 needs to wait for its own first feedback information, and the first feedback information is used in applications that carry resume-break services. Sent when the server finishes releasing the TCP connection.

Optionally, when subscribing to the SMF1 for the first information, the application server that does not carry a service of the type of resumable transmission at a break point indicates that the SMF1 does not need to wait for its own first feedback information at the same time.

It should be noted that if all the application servers associated with the PDU session indicate that they do not need to wait for their own first feedback information when subscribing, it indicates that the service on the PDU session does not need to be resumed. At this time, SMF1 can directly initiate the release of the PDU session without waiting for the first feedback information.

It should be noted that if all the application servers associated with the PDU session have at least one application server indicating that they need to wait for their own first feedback information when subscribing, it indicates that there is a service that needs to be resumed on the PDU session.

S930, the application server receives the first information, and further releases the TCP connection according to the first information.

In a possible implementation manner, the SMF1 sends the first information to all associated application servers, and the application server receives the first information and first determines whether it carries the resume-break service. If it carries the resume-break service, further , and release the TCP connection according to the first information.

In a possible implementation manner, the SMF1 sends the first information to the application server carrying the resume-break service, and the application server carrying the resume-break service receives the first information, and further releases the TCP according to the first information. connect.

S940, the SMF1 determines that the TCP connection has been released, and further, the SMF1 triggers the release process of the original PDU session.

In a possible implementation manner, the SMF1 starts a timer after sending the first information to the application server, and after the first time elapses, the SMF1 determines that the TCP connection has been released, and further triggers the release process of the original PDU session. A time is the time required for the SMF1 default TCP connection to be released.

In a possible implementation manner, the SMF1 receives the first feedback information to determine that the TCP connection has been released, and the first feedback information is sent to the SMF1 after the application server releases the TCP connection. Optionally, after receiving the first feedback information from all the application servers to which the first information is subscribed and indicating that the first feedback information needs to be waited, the SMF1 further triggers the release of the original PDU session.

In a possible implementation manner, all application servers associated with SMF1 indicate that SMF1 does not need to wait for the first feedback information when subscribing to the first information, and then SMF1 immediately triggers the release of the original PDU session after sending the first information.

SMF1 triggers the release process steps of the original PDU session, please refer to method 800.

In this embodiment, the SMF1 notifies the application server through the control plane that the network should release the original PDU session, perform UPF reselection, and create a new PDU session to connect to the same DN. After the application server receives the first information, it actively executes the process of releasing the TCP connection with the terminal device carrying the resumed transmission service, and synchronizes the TCP sending and receiving status between the terminal device and the application server. Due to the synchronization of the TCP transceiver status between the terminal device and the application server, the retransmission of successfully transmitted data is avoided. In addition, due to the active execution of the TCP connection release process, the retransmission of undelivered data on the TCP connection is avoided. The method of this embodiment can reduce the waste of air interface resources and avoid increasing the transmission delay of the breakpoint part.

A method 1000 for managing a PDU session provided by an embodiment of the present application will be described below with reference to FIG. 10 . The method 1000 includes:

S1010, SMF1 decides to perform UPF reselection.

S1020, the SMF1 sends the first information to the terminal device or the application server.

Optionally, the first information indicates that the PDU session is about to be released, and indirectly instructs the terminal device or the application server to release the TCP connection. A connection belongs to a PDU session.

Optionally, the first information directly instructs the terminal device or the application server to release the TCP connection.

In a possible implementation manner, the SMF1 may directly send the first information to the UPF, and the UPF directly includes the first information into the packet header of the UPF data packet.

In a possible implementation manner, the SMF1 may send the first signaling to the UPF, and the UPF generates the first information according to the first signaling, and includes the first information in the packet header of the UPF data packet.

As an example and not a limitation, the first information or the first signaling sent by the SMF1 to the UPF1 may specifically be an N4 Session Modification Request. Optionally, after receiving the first information or the first signaling, the UPF1 may also reply information to the SMF1, and then perform the action of adding the first information or adding the first information generated by the first signaling to the packet header of the data packet. As an example and not a limitation, the reply information may specifically be an N4 Session Modification Response.

S1030, the terminal device or the application server receives the first information, and further releases the TCP connection according to the first information.

Specifically, the application server decapsulates the uplink data packet and receives the first information, or the terminal device decapsulates the downlink data packet and receives the first information.

S1040, the SMF1 determines that the TCP connection has been released, and further, the SMF1 triggers the release process of the original PDU session.

Specifically, when the SMF1 sends the first information or the first signaling to the UPF, it starts a timer. When the timer elapses for the first time, and the SMF1 determines that the TCP connection has been released, it initiates the release process of the PDU session. The first time The time required for the SMF1 default TCP connection release.

The process of releasing and re-establishing the PDU session is the same as in method 800 .

It should be noted that the SMF1 or SMF2 is only an example, and represents switching from one original SMF to another target SMF, and may also be represented by SMF3 or SMF4 or the like.

It should be noted that the UPF1 and UPF2 are only exemplary, representing the original PDU session path and the newly created PDU session path, and may also be UPF3, UPF4, and so on.

In this embodiment, SMF1 notifies the terminal device or the application server by sending the first information through the user plane. The first information exists in the IP header or TCP header of the data packet and can specifically instruct the terminal device and the application carrying the resume transmission service. The server disconnects the TCP connection in the middle, and after receiving the notification, the terminal device or the application server actively executes the release process of the TCP connection carrying the resumed transmission service, and synchronizes the TCP sending and receiving status between the terminal device and the application server. Due to the synchronization of the TCP transceiver status between the terminal device and the application server, the retransmission of successfully transmitted data is avoided. In addition, due to the active execution of the TCP connection release process, the retransmission of undelivered data on the TCP connection is avoided. This embodiment can reduce the waste of air interface resources and avoid increasing the transmission delay of the breakpoint part.

FIG. 11 shows a schematic block diagram of a communication apparatus 1100 according to an embodiment of the present application, and the communication apparatus 1100 may be used to execute the methods or steps corresponding to the foregoing method SMF1. Optionally, each unit in the communication apparatus 1100 may be implemented by software.

In a possible embodiment, the communication apparatus can be configured to execute the method or step corresponding to SMF1 in the method 800. The apparatus is shown in FIG. 11 , and the communication apparatus 1100 includes:

The transceiver unit 1110 is configured to send the first information.

The processing unit 1120 is configured to release the PDU session after determining that the TCP connection has been released.

It should be noted that the transceiver unit 1110 may send the first information to the terminal device through the AMF. As an example and not a limitation, the transceiver unit 1110 may send the first information through the Namf_Communication_N1N2MessageTransfer service of the AMF.

It should be noted that the processing unit 1120 is further configured to decide to perform UPF reselection of a PDU session, and the PDU session is the PDU session for which the processing unit 1120 decides to perform UPF reselection.

In a possible implementation manner, after the transceiver unit 1110 sends the first information, the processing unit 1120 is further configured to start a timer. As an example and not a limitation, the timer may be a UPF relocation timer. When the timer elapses for the first time, the processing unit 1120 determines that the TCP connection has been released, which is an indirect determination. The processing unit 1120 defaults to the first time after the TCP connection has been released, and then initiates the release of the PDU session.

In a possible implementation manner, the transceiver unit 1110 is further configured to receive second feedback information, the second feedback information is sent by the terminal device after receiving the first information, and the processing unit 1120 receives the second feedback information after receiving the second feedback information. A timer is started. As an example and not a limitation, the timer may be a UPF relocation timer. When the timer elapses for the first time, the processing unit 1120 determines that the TCP connection has been released, which is an indirect determination. The processing unit 1120 defaults that after the first time elapses, the TCP connection has been released, and then initiates the release of the PDU session.

In a possible implementation manner, the transceiver unit 1110 receives the first feedback information from the terminal device, the first feedback information indicates that the TCP connection has been released, the processing unit 1120 directly determines that the TCP connection has been released, and then initiates a PDU session release.

The release of the PDU session specifically includes: as an example but not a limitation, the transceiver unit 1110 can send the N1 SM Information to the terminal device by calling the Namf_Communication_N1N2MessageTransfer service of the AMF, and the N1 SM Information includes a PDU session release instruction, and the instruction includes the PDU session ID and Reason for re-establishing the PDU session to the same DN. The network and the terminal device complete the process of releasing the original PDU session. The terminal device receives the PDU session release instruction, generates a new PDU session ID, and initiates a PDU session establishment process. AMF selects SMF2, and SMF2 selects UPF2. The network and the terminal device complete the re-establishment of the PDU session of SSC mode 2.

In a possible embodiment, the communication apparatus may be configured to execute the method or step corresponding to SMF1 in the method 900. The apparatus is shown in FIG. 11 , and the communication apparatus 1100 includes:

The transceiver unit 1110 is configured to send the first information.

It should be noted that the transceiver unit 1110 sends the first information to the application server, and the first information may actually be received by the application function network element in the application server. The application function network element is mainly responsible for the control plane function, interacts with the 5G core network, and applies The server is mainly responsible for the user plane function and transmits service data with the terminal device.

In a possible implementation manner, the transceiver unit 1110 sends the first information to all associated application servers through the control plane, and the application server determines whether the connection between it and the terminal device is a TCP connection that carries the resume transmission service. If it is a TCP connection, the release is initiated. If it is another TCP connection, the first information may be ignored and the release is not initiated.

In a possible implementation manner, the transceiver unit 1110 sends the first information through the control plane to the application server carrying the resume-break service, in other words, directly sends the first information to the connection with the terminal device as It should be noted that if the application server provides enough information about itself when subscribing to the SMF1 for the first information, the transceiver unit 1110 can only send the first information to the application server carrying the resumed transmission service. a message.

It should be noted that the processing unit is further configured to decide to perform UPF reselection of a PDU session, and the PDU session is the PDU session for which the processing unit 1120 decides to perform UPF reselection.

As an example and not a limitation, the transceiving unit 1110 may send the first information through the Nsmf_EventExposure_Notify service.

Optionally, the transceiver unit 1110 may directly send the first information to all associated application servers.

Optionally, the transceiver unit 1110 may send the first information to the NEF, and forward it to all associated application servers via the NEF.

It should be noted that the first information is subscribed by the application server to the processing unit 1120 in advance.

As an example and not a limitation, the first information is subscribed when all associated application servers subscribe to the processing unit 1120 for early notification information.

Optionally, when subscribing to the processing unit 1120 for the first information, the application server that bears the resumed transmission service at the same time instructs the processing unit 1120 that it needs to wait for its own first feedback information, and the first feedback information resumes transmission when the transmission is interrupted. It is sent after the application server of the similar service completes the release of the TCP connection.

Optionally, when subscribing to the processing unit 1120 for the first information, the application server that does not carry a service of the type of resumable transmission, at the same time instructs the processing unit 1120 that the processing unit 1120 does not need to wait for its own first feedback information.

In a possible implementation manner, the transceiver unit 1110 starts a timer after sending the first information to the application server, and after the first time elapses, the processing unit 1120 determines that the TCP connection has been released, and further triggers the release of the original PDU session Flow, the first time is the time required by the processing unit 1120 to release the TCP connection by default.

In a possible implementation manner, the transceiver unit 1110 receives first feedback information to determine that the TCP connection has been released, and the first feedback information is sent to the transceiver unit 1110 after the application server releases the TCP connection. Optionally, after the transceiver unit 1110 receives the first feedback information from all the application servers to which the first information is subscribed indicating that it needs to wait for the first feedback information, further, the processing unit 1120 triggers the release of the original PDU session.

In a possible implementation, all application servers associated with the processing unit 1120 instruct the processing unit 1120 not to wait for the first feedback information when subscribing to the first information, and the transceiver unit 1110 triggers the original PDU session immediately after sending the first information release.

For the process steps of the processing unit 1120 triggering the release of the original PDU session, reference may be made to the foregoing steps.

In a possible embodiment, the communication apparatus may be configured to execute the method or step corresponding to SMF1 in the method 1000. The apparatus is shown in FIG. 11 , and the communication apparatus 1100 includes:

The transceiver unit 1110 is configured to send the first information.

In a possible implementation manner, the transceiver unit 1110 may directly send the first information to the UPF, and the UPF directly includes the first information into the packet header of the UPF data packet.

In a possible implementation manner, the transceiver unit 1110 may send the first signaling to the UPF, and the UPF generates the first information according to the first signaling, and includes the first information in the packet header of the UPF data packet.

As an example and not a limitation, the first information or the first signaling sent by the transceiver unit 1110 to the UPF1 may specifically be an N4 Session Modification Request. Optionally, after receiving the first information or the first signaling, the UPF1 can also reply the information to the transceiver unit 1110, and then perform the action of adding the first information or adding the first information generated by the first signaling to the data packet header. . As an example and not a limitation, the reply information may specifically be an N4 Session Modification Response.

In a possible implementation manner, the transceiver unit 1110 starts a timer when sending the first information or the first signaling to the UPF. When the timer elapses for the first time, the processing unit 1120 determines that the TCP connection has been released, and then initiates a timer. For the release process of the PDU session, the first time is the time required by the processing unit 1120 to release the TCP connection by default.

The process of releasing the PDU session is the same as the above.

FIG. 11 shows a schematic block diagram of a communication apparatus 1100 according to an embodiment of the present application, where the communication apparatus 1100 may be used to execute the methods or steps corresponding to the terminal device or the application server of the foregoing method. Optionally, each unit in the communication apparatus 1100 may be implemented by software.

In a possible embodiment, the communication apparatus may be configured to execute the method or step corresponding to the terminal device in the method 800. The apparatus is shown in FIG. 11 , and the communication apparatus 1100 includes:

The transceiver unit 1110 is configured to receive the first information.

The processing unit 1120 is configured to release the TCP connection according to the first information.

In a possible implementation manner, upon receiving the first information, the transceiver unit 1110 immediately sends the second feedback information to the SMF1 through the AMF, and then the processing unit 1120 releases the TCP connection according to the first information, and the second feedback information indicates that the transmission and reception information is received. Unit 1110 receives the first message.

As an example and not a limitation, the second feedback information may be Ack, and the second feedback information is used to notify the SMF1 that the transceiver unit 1110 has received the first information.

In a possible implementation manner, after the transceiver unit 1110 receives the first information, the processing unit 1120 initiates a process of releasing the TCP connection according to the first information. After the TCP connection is released, the transceiver unit 1110 is further configured to send the first message to SMF1. A feedback information, the first feedback information indicates that the TCP connection has been released, as an example and not a limitation, the first feedback information may be sent to the SMF1 through the AMF.

In a possible embodiment, the communication apparatus can be used to execute the method or step of the application server in the method 900. The apparatus is shown in FIG. 11 , and the communication apparatus 1100 includes:

The transceiver unit 1110 is configured to receive the first information.

In a possible implementation manner, the SMF1 sends the first information to all associated transceiver units 1110, and the transceiver unit 1110 receives the first information. The processing unit 1120 first determines whether it carries the breakpoint resume service. For resuming the transmission service, further, the processing unit 1120 releases the TCP connection according to the first information.

In a possible implementation manner, the SMF1 sends the first information to the transceiver unit 1110 carrying the resume-break service, and the transceiver unit 1110 carrying the resume-break service receives the first information; further, the processing unit 1120 Release the TCP connection according to the first information.

The transceiver unit 1110 is further configured to send first feedback information to the SMF1, where the first feedback information indicates that the TCP connection has been released.

In a possible embodiment, the communication apparatus can be used to execute the method or step corresponding to the terminal device or the application server in the method 1000. The apparatus is shown in FIG. 11 , and the communication apparatus 1100 includes:

The transceiver unit 1110 is configured to receive the first information.

Specifically, the transceiver unit 1110 decapsulates the uplink data packet to receive the first information, or the transceiver unit 1110 decapsulates the downlink data packet to receive the first information.

When the communication device 1110 is implemented, the technical effects achieved may refer to methods 800-1000.

FIG. 12 is a schematic diagram of another communication apparatus 1200 according to an embodiment of the present application. Optionally, each unit in the communication apparatus 1100 may be implemented by software. The transceiver 1210 in the communication device 1200 performs actions similar to the transceiver unit 1110 in the communication device 1100, and the processor 1220 in the communication device 1200 performs actions similar to the processing unit 1120 in the communication device 1100. For detailed methods and steps, please refer to Description in Communication Device 1100 .

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

A method for managing a protocol data unit session, comprising:

The session management function network element sends first information to the first data transmission device, the first information indicating that the protocol data unit session will be released;

The session management function network element determines that the transmission control protocol connection between the first data transmission device and the second data transmission device has been released according to the first information, and the transmission control protocol connection bears a resume transmission service, the protocol data unit session includes the transmission control protocol connection;

The session management function network element releases the protocol data unit session.
The method according to claim 1, wherein the first data transmission device is a terminal device, and the second data transmission device is an application server, or,

The first data transmission device is an application server, and the second data transmission device is a terminal device.
The method according to claim 1, wherein the first information is sent by a user plane function network element, and the first information is included in a packet header of a data packet of the user plane function network element.
The method according to any one of claims 1 to 3, wherein the session management function network element determines that the transmission control protocol connection between the first data transmission device and the second data transmission device has been The first information release includes:

When the first time elapses after the first information is sent, the session management function network element determines that the transmission control protocol connection has been released according to the first information.
The method according to claim 1 or 2, wherein the session management function network element determines that the transmission control protocol connection between the first data transmission device and the second data transmission device has been A release of information, including:

receiving, by the session management function network element, first feedback information sent by the first data transmission apparatus, where the first feedback information indicates that the transmission control protocol connection has been released;

The session management function network element determines, according to the first feedback information, that the transmission control protocol connection has been released according to the first information.
A method for managing a protocol data unit session, comprising:

the first data transmission device receives first information sent from the session management function network element, the first information indicating that the protocol data unit session will be released;

The first data transmission device judges that the transmission control protocol connection between the first data transmission device and the second data transmission device bears a resume transmission service, and the protocol data unit session includes the transmission control protocol connection;

The first data transmission apparatus releases the transmission control protocol connection according to the first information.
The method according to claim 6, wherein the first data transmission device is a terminal device, and the second data transmission device is an application server, or,

The first data transmission device is an application server, and the second data transmission device is a terminal device.
The method according to claim 6 or 7, wherein the method further comprises:

After releasing the TP connection according to the first information, the first data transmission apparatus sends first feedback information to the session management network element, where the first feedback information indicates that the TP connection has been connected. freed.
A communication device for managing a protocol data unit session, comprising:

a transceiver, configured to send first information to the first data transmission device, the first information indicating that the protocol data unit session will be released;

a processor, configured to determine that the transmission control protocol connection between the first data transmission device and the second data transmission device has been released according to the first information, the transmission control protocol connection bears a resume transmission service, the transmission control protocol connection a protocol data unit session including the transmission control protocol connection;

The processor is also configured to release the protocol data unit session.
The communication device according to claim 9, wherein the first data transmission device is a terminal device, and the second data transmission device is an application server, or,

The first data transmission device is an application server, and the second data transmission device is a terminal device.
The communication device according to claim 9 or 10, wherein the transceiver sends the first information through a user plane function network element, and the first information is included in a data packet of the user plane function network element in the header.
The communication device according to any one of claims 9 to 11, wherein the processor determines that a transmission control protocol connection between the first data transmission device and the second data transmission device has been The first information release, including:

When a first time elapses after the first information is sent, the processor determines that the TP connection has been released according to the first information.
The communication device according to claim 9 or 10, wherein the processor determines that a transmission control protocol connection between the first data transmission device and the second data transmission device has been established according to the first information release, including:

receiving, by the transceiver, first feedback information sent by the first data transmission apparatus, the first feedback information indicating that the transmission control protocol connection has been released;

The processor determines that the Transmission Control Protocol connection has been released according to the first information.
A communication device for managing a protocol data unit session, comprising:

a transceiver, configured to receive first information sent from the session management function network element, the first information indicating that the protocol data unit session will be released;

a processor for judging that the transmission control protocol connection between the communication device and the data transmission device bears a resume transmission service, and the protocol data unit session includes the transmission control protocol connection;

The processor is further configured to release the transmission control protocol connection according to the first information.
The communication device according to claim 14, wherein the communication device is a terminal device, and the data transmission device is an application server, or,

The communication device is an application server, and the data transmission device is a terminal device.
The communication device according to claim 14 or 15, characterized in that:

After the processor releases the TP connection according to the first information, the transceiver sends first feedback information to the session management network element, the first feedback information indicating that the TP connection has been released .
A communication system for managing a protocol data unit session, characterized by comprising the communication device described in claims 9-16.
A computer-readable storage medium, characterized by comprising a computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1-8.
A chip, characterized in that it comprises a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of claims 1-8. one of the methods described.