Heartbeat packet sending method, related device and communication system

Abstract

The present application relates to the field of communications, and specifically relates to a heartbeat packet sending method, a related device and a communication system. The method comprises: a first proxy network element receives a heartbeat proxy rule from an SMF network element; the first proxy network element determines, on the basis of the heartbeat proxy rule, whether to implement heartbeat proxying between a target UE and an application server by the first proxy network element; when it is determined on the basis of the heartbeat proxy rule that the first proxy network element is to implement heartbeat proxying between the target UE and the application server, the first proxy network element generates a heartbeat packet and sends the heartbeat packet to the application server. By introducing the proxy network element to act as a proxy for the UE to send the heartbeat packet to the application server, the present application helps to reduce the standby power consumption and the background load of the UE, and saves network resources between the UE and the network.

Description

Heartbeat packet sending method, related equipment and communication system

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 15, 2023, with application number 202311733320.3 and invention name “Heartbeat packet sending method, related equipment and communication system”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a heartbeat packet sending method, related equipment, and a communication system. Background Art

[0003] A persistent connection is a process in which two communicating parties establish a Transmission Control Protocol (TCP) connection and then maintain it after the communication is complete, rather than disconnecting. This eliminates the time required for Domain Name System (DNS) resolution, connection establishment, and TCP slow start, significantly speeding up requests and facilitating the reception of real-time server messages. However, maintaining the availability of persistent connections is crucial in this scenario.

[0004] Heartbeat keepalive is a common method for maintaining long connections. It means that the user device sends a heartbeat packet to the server at regular intervals. After receiving the heartbeat packet, the server replies with the same heartbeat packet to the user device. If the server or user device does not receive any message including the heartbeat packet within a preset period of time, the TCP connection is considered disconnected, that is, the heartbeat timeout.

[0005] There are two main TCP long connection heartbeat keepalive solutions:

[0006] 1. The user device's application establishes a persistent TCP connection with its own server and periodically sends heartbeat packets to maintain the connection. This solution achieves a high degree of autonomy through application-level control, but multiple applications require multiple heartbeats, significantly impacting power consumption.

[0007] 2. The user device manufacturer or operating system provides a unified persistent connection link. Multiple applications reuse a persistent connection link, and token identifiers are used to distinguish different application messages. Compared with solution 1, this can save power and memory resources, but requires application manufacturers to adapt.

[0008] Both of the above keep-alive solutions require the user device and the server to transmit heartbeat packets, which consumes network resources between the user device and the network and seriously affects the standby power consumption and background load of the user device. Summary of the Invention

[0009] The embodiments of the present application provide a heartbeat packet sending method, related equipment, and a communication system. Adoption of the embodiments of the present application is beneficial to reducing the standby power consumption and background load of user equipment (UE).

[0010] In a first aspect, embodiments of the present application provide a method for sending a heartbeat packet. The method can be applied to a first proxy network element. The first proxy network element can be a user plane function (UPF) network element or a first network element. The first network element is a network element different from a UPF network element and an application function (AF) network element.

[0011] The first proxy network element receives a heartbeat proxy rule from a session management function (SMF) network element; the first proxy network element determines, based on the heartbeat proxy rule, whether the first proxy network element performs heartbeat proxy between a target UE and an application server; when it is determined, based on the heartbeat proxy rule, that the first proxy network element performs heartbeat proxy between the target UE and the application server, the first proxy network element generates a heartbeat packet and sends the heartbeat packet to the application server.

[0012] By introducing a proxy network element to send heartbeat packets to the application server on behalf of the UE, it is beneficial to reduce the standby power consumption and background load of the UE, and at the same time can save network resources between the UE and the network.

[0013] With reference to the first aspect, in a possible implementation, the heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server.

[0014] Optionally, the heartbeat proxy rule includes instruction information for instructing the first proxy network element to perform heartbeat proxy between the target UE and the application server.

[0015] By implicitly or explicitly indicating that the first proxy network element performs heartbeat proxy between the target UE and the application server, the first proxy network element can know that the first proxy network element performs heartbeat proxy between the target UE and the application server without performing other operations, thereby reducing the workload of the first proxy network element.

[0016] In conjunction with the first aspect, in one possible implementation, a heartbeat proxy rule includes an identifier of a target UE. The first proxy network element matches the identifier of the target UE with a pre-stored UE identifier. If the match is successful, the heartbeat proxy rule includes instruction information for instructing the first proxy network element to perform heartbeat proxy between the target UE and the application server. The UE identifier pre-stored in the first proxy network element is used to indicate a UE requiring heartbeat proxy. The identifier of the UE requiring heartbeat proxy is pre-configured in the first proxy network element.

[0017] In this way, the SMF network element does not need to perform matching operations, which reduces the workload of the SMF network element.

[0018] In conjunction with the first aspect, in one possible implementation, a heartbeat proxy rule includes an identifier of a UE requiring heartbeat proxy, a first proxy network element stores an identifier of a target UE, and the first proxy network element matches the identifier of the target UE with the identifier of the UE requiring heartbeat proxy. If the match is successful, the heartbeat proxy rule includes instruction information for instructing the first proxy network element to perform heartbeat proxy between the target UE and the application server. The identifier of the target UE is preconfigured in the first proxy network element.

[0019] In this way, the SMF network element does not need to perform matching operations, which reduces the workload of the SMF network element.

[0020] With reference to the first aspect, in a possible implementation, the heartbeat proxy rule includes a heartbeat proxy frequency, where the heartbeat proxy frequency is a frequency at which the first proxy network element sends heartbeat packets to the application server.

[0021] In conjunction with the first aspect, in one possible implementation, the method of this embodiment further includes:

[0022] The first proxy network element sends a first heartbeat proxy request to the target UE, where the first heartbeat proxy request is used to request the first proxy network element to perform heartbeat proxy between the target UE and the application server, and receives a response message sent by the target UE in response to the first heartbeat proxy request.

[0023] It should be understood that when the first proxy network element receives the response message from the UE, it knows that the target UE agrees that the first proxy network element will perform heartbeat proxy between the target UE and the application server.

[0024] In conjunction with the first aspect, in one possible implementation, the first proxy network element is the first network element, and the heartbeat proxy rule from the SMF network element is forwarded to the first network element by the UPF network element. Further, the heartbeat proxy rule is forwarded to the first network element by the UPF network element when determining that the first network element is to perform heartbeat proxy between the target UE and the application server.

[0025] In this way, in the mobile edge computing (MEC) scenario, it is also beneficial to reduce the standby power consumption and background load of the UE, while saving network resources between the UE and the network.

[0026] In combination with the first aspect, in one possible implementation, after the first proxy network element sends a heartbeat packet to the application server, it receives a response message to the heartbeat packet fed back by the application server; if, starting from the moment the first proxy network element sends the heartbeat packet to the application server, no response message to the heartbeat packet is received from the application server within a preset time period, a first message is sent to the target UE, and the first message is used to indicate that the application server is unreachable.

[0027] By sending information indicating that the application server is unreachable to the target UE, the target UE can be informed that the application server is unreachable, and the target UE can disconnect from the application server, thereby saving connection resources.

[0028] In conjunction with the first aspect, in one possible implementation, the first proxy network element receives second information sent by the SMF network element and sends the second information to the application server. The second information is used to indicate that the target UE is unreachable. The second information is generated when the access and mobility management function (AMF) network element perceives that the target UE is unreachable, and is sent to the SMF network element.

[0029] By sending information indicating that the target UE is unreachable to the application server, the application server can be informed that the target UE is unreachable, and the application server can disconnect from the target UE, thereby saving connection resources.

[0030] In combination with the first aspect, in a possible implementation, the first proxy network element sends a context for restoring the heartbeat proxy service to the second proxy network element, instructing the second proxy network element to restore the heartbeat proxy between the target UE and the application server when the first proxy network element fails.

[0031] In this way, when the heartbeat proxy service between the first proxy network element and the application server fails, or the first proxy network element fails, the second proxy network element replaces the first proxy network element, ensuring the normal operation of the heartbeat proxy.

[0032] In a second aspect, an embodiment of the present application provides a method for sending a heartbeat packet, which is applied to an SMF network element. The method includes:

[0033] The SMF network element receives the heartbeat proxy policy sent by the policy control function (PCF) network element; the SMF network element determines the heartbeat proxy rule based on the heartbeat proxy policy, and the heartbeat proxy rule is used to determine whether the first proxy network element performs the heartbeat proxy between the target UE and the application server, and the SMF network element sends the heartbeat proxy rule to the first proxy network element.

[0034] Introducing a proxy network element in this manner to send heartbeat packets to the application server on behalf of the UE is beneficial to reducing the standby power consumption and background load of the UE, while saving network resources between the UE and the network.

[0035] In combination with the second aspect, in one possible implementation, the heartbeat proxy strategy includes the UE identifier that requires a heartbeat proxy, and the SMF network element matches the identifier of the target UE with the UE identifier that requires a heartbeat proxy; if the match is successful, the heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server.

[0036] The target UE identifier is pre-configured in the first proxy network element. In this way, the first proxy network element does not need to perform a matching operation, which reduces the workload of the first proxy network element.

[0037] In combination with the second aspect, in one possible implementation, the heartbeat proxy strategy includes an identifier of the target UE, and the SMF network element matches the identifier of the target UE with a pre-stored UE identifier; wherein the pre-stored UE identifier is used to indicate the UE that requires a heartbeat proxy; if the match is successful, the heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server.

[0038] In this way, the first agent network element does not need to perform the matching operation, which reduces the workload of the first agent network element.

[0039] In conjunction with the second aspect, in one possible implementation, the heartbeat proxy rule includes an identifier of a UE requiring heartbeat proxy. The heartbeat proxy rule is used to instruct the first proxy network element to determine, based on the identifier of the UE requiring heartbeat proxy, whether to perform heartbeat proxy between the target UE and the application server by the first proxy network element. In this manner, the SMF network element is not required to perform matching operations, thereby reducing the workload of the SMF network element.

[0040] In conjunction with the second aspect, in one possible implementation, the heartbeat proxy rule includes a target UE identifier, and the heartbeat proxy rule is used to instruct the first proxy network element to determine, based on the target UE identifier, whether to perform heartbeat proxying between the target UE and the application server. In this way, the SMF network element does not need to perform matching operations, thereby reducing the workload of the SMF network element.

[0041] In conjunction with the second aspect, in one possible implementation, the method of this embodiment further includes:

[0042] When the SMF network element determines that the first proxy network element performs heartbeat proxy between the target user equipment UE and the application server, the SMF network element sends a second heartbeat proxy request to the target UE and the AF network element respectively, wherein the second heartbeat proxy request is used to inform the target UE and the AF network element that the first proxy network element performs heartbeat proxy between the target UE and the application server.

[0043] In conjunction with the second aspect, in one possible implementation, the method of this embodiment further includes:

[0044] The SMF network element receives a third heartbeat proxy request sent by the target UE, where the third heartbeat proxy request is used to request the network side to perform a heartbeat proxy between the target UE and the application server; and sends a first request to the PCF network element, where the first request is used to request the heartbeat proxy policy.

[0045] In conjunction with the second aspect, in one possible implementation, the method of this embodiment includes:

[0046] The SMF network element receives the fourth heartbeat proxy request sent by the PCF network element, where the fourth heartbeat proxy request is sent when the application server agrees that the network side performs heartbeat proxy between the target UE and the application server; the fourth heartbeat proxy request is used to request that the network side perform heartbeat proxy between the target UE and the application server; the SMF network element sends the fourth heartbeat proxy request to the target UE; receives and sends a response message of the target UE to the fourth heartbeat proxy request to the PCF network element, where the response message is used to inform the PCF network element that the target UE agrees that the network side performs heartbeat proxy between the target UE and the application server.

[0047] In conjunction with the second aspect, in one possible implementation, the method of this embodiment further includes:

[0048] When the SMF network element receives the first information sent by the first proxy network element, it sends the first information to the target UE, wherein the first information is used to indicate that the application server is unreachable; the first information is generated when the first proxy network element sends a heartbeat packet to the application server and does not receive a response message from the application server for the heartbeat packet within a preset time period.

[0049] By sending information indicating that the application server is unreachable to the target UE, the target UE can be informed that the application server is unreachable, and the target UE can disconnect from the application server, thereby saving connection resources.

[0050] In conjunction with the second aspect, in one possible implementation, the method of this embodiment further includes:

[0051] The SMF network element receives the second information sent by the AMF network element, where the second information is generated when the AMF network element perceives that the target UE is unreachable; the SMF network element sends the second information to the application server.

[0052] By sending information indicating that the target UE is unreachable to the application server, the application server can be informed that the target UE is unreachable, and the application server can disconnect from the target UE, thereby saving connection resources.

[0053] In conjunction with the second aspect, in one possible implementation, the method of this embodiment further includes:

[0054] The SMF network element sends a subscription message to the AMF network element, which is used to subscribe to the reachability information of the target UE.

[0055] By subscribing to the reachability information of the target UE, the SMF network element can know that the target UE is unreachable when the target UE is unreachable.

[0056] In conjunction with the second aspect, in one possible implementation, the method of this embodiment further includes:

[0057] When the SMF network element detects a heartbeat proxy service failure of the first proxy network element or a device failure of the first proxy network element, it sends a context for restoring the heartbeat proxy service to the second proxy network element to instruct the second proxy network element to restore the heartbeat proxy between the target UE and the application server.

[0058] In this way, when the heartbeat proxy service between the first proxy network element and the application server fails, or when the first proxy network element fails, the second proxy network element replaces the first proxy network element, thereby ensuring the normal operation of the heartbeat proxy.

[0059] In a third aspect, an embodiment of the present application provides a first proxy network element, comprising a unit or module for implementing the method provided in the first aspect or any possible implementation manner of the first aspect.

[0060] In a fourth aspect, an embodiment of the present application provides an SMF network element, comprising a unit or module for implementing the method provided in the second aspect or any possible implementation method of the second aspect.

[0061] In a fifth aspect, an embodiment of the present application provides a first proxy network element, comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the first aspect or any possible implementation of the first aspect.

[0062] In a sixth aspect, an embodiment of the present application provides an SMF network element, comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the second aspect or any possible implementation of the second aspect.

[0063] In the seventh aspect, an embodiment of the present application provides a computer storage medium, including computer instructions. When the computer instructions are run on an electronic device, the electronic device executes the method provided in any possible implementation of the first aspect, or the method provided in any possible implementation of the second aspect.

[0064] In an eighth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute the method provided in any possible implementation of the first aspect, or the method provided in any possible implementation of the second aspect.

[0065] In a ninth aspect, an embodiment of the present application further provides a heartbeat packet sending method, which is applied to a communication system, the communication system including a user device, a first proxy network element, an SMF network element, a PCF network element, and an application server, the method comprising:

[0066] The SMF network element receives the heartbeat proxy policy sent by the PCF network element; the SMF network element generates a heartbeat proxy rule based on the heartbeat proxy rule, and the heartbeat proxy rule is used to determine whether the first proxy network element performs heartbeat proxy between the target UE and the application server; the SMF network element sends the heartbeat proxy rule to the first proxy network element; when the first proxy network element determines that the first proxy network element performs heartbeat proxy between the target UE and the application server based on the heartbeat proxy rule, the first proxy network element generates a heartbeat packet and sends the heartbeat packet to the application server.

[0067] In a tenth aspect, an embodiment of the present application further provides a communication system, the communication system including a user equipment, a first proxy network element, an SMF network element, a PCF network element and an application server;

[0068] The SMF network element is used to receive the heartbeat proxy policy sent by the PCF network element;

[0069] The SMF network element is configured to generate a heartbeat proxy rule based on the heartbeat proxy rule, where the heartbeat proxy rule is used to determine whether the first proxy network element performs a heartbeat proxy between the target UE and the application server;

[0070] The SMF network element is configured to send a heartbeat proxy rule to the first proxy network element;

[0071] The first proxy network element is configured to generate a heartbeat packet and send the heartbeat packet to the application server when it is determined based on the heartbeat proxy rule that the first proxy network element performs heartbeat proxy between the target UE and the application server.

[0072] It can be understood that the beneficial effects of the embodiments described in the third to tenth aspects can refer to the beneficial effects of the methods described in the first to second aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] FIG1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0074] FIG2 is a flow chart of a method for sending a heartbeat packet according to an embodiment of the present application;

[0075] FIG3 is a flow chart of another method for sending a heartbeat packet according to an embodiment of the present application;

[0076] FIG4 is a schematic diagram of an interactive process of a heartbeat packet sending method provided in an embodiment of the present application;

[0077] FIG5 is a schematic diagram of an interactive process of another method for sending a heartbeat packet provided in an embodiment of the present application;

[0078] FIG6 is a schematic diagram of an interactive process of another method for sending a heartbeat packet provided in an embodiment of the present application;

[0079] FIG7 is a schematic diagram of an interactive process of another method for sending a heartbeat packet provided in an embodiment of the present application;

[0080] FIG8 is a schematic diagram of an interactive process of another method for sending a heartbeat packet provided in an embodiment of the present application;

[0081] FIG9 is a schematic structural diagram of a first proxy network element provided in an embodiment of the present application;

[0082] FIG10 is a schematic structural diagram of an SMF network element provided in an embodiment of the present application;

[0083] FIG11 is a schematic structural diagram of another first proxy network element provided in an embodiment of the present application;

[0084] FIG12 is a schematic diagram of the structure of another SMF network element provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] The terms "first", "second", "third" and "fourth" in the specification, claims and drawings of this application are used to distinguish different objects rather than to describe a specific order.

[0086] "Multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating the existence of three relationships. For example, "A and / or B" means: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0087] The embodiments of the present application are described below with reference to the accompanying drawings.

[0088] Refer to Figure 1, which is a schematic diagram of a communication system architecture provided in an embodiment of the present application. The communication system is a schematic diagram of the network architecture of the fifth generation mobile communication technology (5th Generation Mobile Networks, 5G). It includes a (radio) access network ((radio) access network, (R)AN, which is expressed as two parts: RAN equipment and core network (CN). The RAN equipment is used to provide network access functions for authorized user equipment (User Equipment, UE) in a specific area, and can use transmission tunnels of different qualities according to the level of UE, business requirements, etc. For example, the RAN equipment can manage wireless resources, provide access services for UE, and then complete the forwarding of control information and / or data information between UE and CN. The CN mainly includes the following functional network elements:

[0089] AMF network element, whose main functions include managing user registration, reachability detection, SMF node selection, and mobility state transition management.

[0090] The main function of the SMF network element is to control the establishment, modification and deletion of sessions, the selection of user plane nodes, etc.

[0091] The main functions of the UPF network element are data packet routing and forwarding, serving as a mobility anchor point, serving as an uplink classifier to support routing service flows to the data network, and serving as a branch point to support multi-homed packet data unit (PDU) sessions.

[0092] The PCF network element is a policy decision point that provides rules based on service data flow and application detection, gating, Quality of Service (QoS), and flow-based charging control.

[0093] The unified data management (UDM) functional network element mainly stores user contract data.

[0094] The authentication server function (AUSF) network element mainly provides authentication services.

[0095] AF network element: Its main function is to interact with the 3rd Generation Partnership Project (3GPP) core network to provide services, influence business flow routing, access network capability exposure, policy control, etc.

[0096] Network exposure function (NEF) network element: securely exposes services and capabilities provided by 3GPP network functions, such as third parties, edge computing, and AF.

[0097] Data network (DN): such as operator services, Internet access, or third-party services.

[0098] Referring to FIG. 2 , FIG. 2 is a flow chart illustrating a method for sending a heartbeat packet according to an embodiment of the present application. The method is applied to a first proxy network element, which is a UPF network element or a first network element in the 5G system shown in FIG. 1 . The first network element is a network element different from the UPF network element and the AF network element. As shown in FIG. 2 , the method includes:

[0099] S201. The first proxy network element receives a heartbeat proxy rule from an SMF network element.

[0100] The heartbeat proxy rule is used to determine whether the first proxy network element performs heartbeat proxy between the target UE and the application server.

[0101] In one possible implementation, when the first proxy network element is the first network element, the heartbeat proxy rules from the SMF network element are forwarded to the first network element via the UPF network element. Further, the heartbeat proxy rules are sent by the UPF network element to the first network element when determining that the first network element is to perform heartbeat proxy between the target UE and the application server.

[0102] S202 : When the first proxy network element determines based on the heartbeat proxy rule that the first proxy network element performs heartbeat proxying between the target UE and the application server, the first proxy network element generates a heartbeat packet and sends the heartbeat packet to the application server.

[0103] Specifically, the first proxy network element determines whether to perform heartbeat proxy between the target UE and the application server based on the heartbeat proxy rule, specifically in the following manner:

[0104] Method 1: The heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server. Optionally, the heartbeat proxy rule includes instruction information for instructing the first proxy network element to perform heartbeat proxy between the target UE and the application server. In other words, upon receiving the heartbeat proxy rule, the first proxy network element knows that the first proxy network element performs heartbeat proxy between the target UE and the application server. By implicitly or explicitly instructing the first proxy network element to perform heartbeat proxy between the target UE and the application server, the first proxy network element can know that the first proxy network element performs heartbeat proxy between the target UE and the application server without performing other operations, thereby reducing the workload of the first proxy network element.

[0105] Method 2: The heartbeat proxy rule includes the identifier of the target UE, and the first proxy network element pre-stores the identifier of the UE that requires a heartbeat proxy; the first proxy network element matches the identifier of the target UE with the identifier of the UE that requires a heartbeat proxy, that is, determines whether the UE identifier of the heartbeat proxy includes the identifier of the target UE. If the UE identifier that requires a heartbeat proxy includes the identifier of the target UE, the match is successful, and then the first proxy network element determines that the first proxy network element performs heartbeat proxy between the target UE and the application server; if the match is unsuccessful, it is determined that the first proxy network element does not need to perform heartbeat proxy between the target UE and the application server.

[0106] Method three: The heartbeat proxy rule includes the UE identifier that requires a heartbeat proxy. The first proxy network element pre-stores the identifier of the target UE, which can be obtained by the first proxy network element during the process of establishing a PDU session between the target UE and the application server. Of course, it can also be obtained through other methods, which are not limited. The first proxy network element matches the identifier of the target UE with the identifier of the UE that requires a heartbeat proxy, that is, determines whether the UE identifier of the heartbeat proxy includes the identifier of the target UE. If the UE identifier that requires a heartbeat proxy includes the identifier of the target UE, the match is successful, and then the first proxy network element determines that the first proxy network element will perform heartbeat proxy between the target UE and the application server; if the match is unsuccessful, it is determined that the first proxy network element is not required to perform heartbeat proxy between the target UE and the application server.

[0107] In an optional implementation, the heartbeat proxy rule further includes a heartbeat proxy frequency, where the heartbeat proxy frequency is the frequency at which the first proxy network element sends the heartbeat packet to the application server.

[0108] It should be noted that the UE identifier mentioned in this application is used to uniquely identify the UE. Optionally, the UE identifier is an international mobile equipment identity (IMEI), an international mobile subscriber identity (IMSI), a mobile station integrated services digital network (MSISDN), or a field in any of the IMEI, IMSI, and MSISDN, such as the manufacturer identifier and model identifier in the IMEI.

[0109] In one possible implementation, the method of this embodiment further includes:

[0110] After sending a heartbeat packet to the application server, the first proxy network element receives a response message to the heartbeat packet from the application server. If the first proxy network element does not receive a response message to the heartbeat packet from the application server within a preset time period starting from when the first proxy network element sent the heartbeat packet to the application server, the application server is determined to be unreachable. In this case, the first proxy network element sends first information to the target UE, where the first information is used to indicate that the application server is unreachable. Optionally, the first proxy network element sends the first information to the target UE via an SMF network element.

[0111] By sending information indicating that the application server is unreachable to the target UE, the target UE can be informed that the application server is unreachable. At this time, the target UE can disconnect from the application server to save connection resources, or re-establish a connection with the application server.

[0112] In one possible implementation, the AMF network element can sense whether the target UE is reachable. There are two situations in which the target UE is reachable: one is when a signaling connection exists between the target UE and the network (i.e., in the connected state), in which case the AMF network element determines that the UE is reachable; the other is when a signaling connection temporarily ceases between the target UE and the network, but the network is able to page the target UE and reestablish the signaling connection. In this case, the target UE is also reachable. The AMF network element can sense both of these situations and determine whether the target UE is reachable. When the AMF network element senses that the target UE is unreachable, it sends a second message to the SMF network element, indicating that the target UE is unreachable. The SMF network element sends the second message to the first proxy network element, which in turn sends the second message to the application server to inform the application server that the target UE is unreachable. By sending information indicating that the target UE is unreachable to the application server, the application server is informed that the target UE is unreachable. In this case, the target UE can disconnect from the target UE to save connection resources, or reestablish a connection with the target UE.

[0113] In one possible implementation, the first proxy network element sends a context for restoring the heartbeat proxy service to the second proxy network element during the heartbeat proxy process between the target UE and the application server, thereby instructing the second proxy network element to restore the heartbeat proxy between the target UE and the application server when the first proxy network element fails.

[0114] It should be noted that the failure of the first proxy network element here may be a failure of the first proxy network element device itself, or a failure of the heartbeat proxy service between the first proxy network element and the application server, which makes it impossible to continue the heartbeat proxy between the target UE and the application server.

[0115] In one example, the first proxy network element and the second proxy network element are both UPF network elements; in one example, the first proxy network element and the second proxy network element are both MEC network elements.

[0116] In this way, when the heartbeat proxy service between the first proxy network element and the application server fails, or the first proxy network element fails, the second proxy network element replaces the first proxy network element, ensuring the normal operation of the heartbeat proxy.

[0117] As can be seen, in the solution of this embodiment, by introducing a proxy network element to send heartbeat packets on behalf of the UE to the application server, it is beneficial to reduce the UE's standby power consumption and background load, while also saving network resources between the UE and the network. In the MEC scenario, by introducing a first network element to send heartbeat packets on behalf of the UE to the application server, it is also beneficial to reduce the UE's standby power consumption and background load, while also saving network resources between the UE and the network. When the application server is unreachable, sending information indicating that the application server is unreachable to the target UE allows the target UE to be aware of the unreachable application server, allowing the target UE to disconnect from the application server, thus saving connection resources. When the target UE is unreachable, sending information indicating that the target UE is unreachable to the application server allows the application server to be aware of the unreachable application server, allowing the target UE to disconnect from the target UE to save connection resources or re-establish a connection with the target UE. If the heartbeat proxy service between the first proxy network element and the application server fails, or if the first proxy network element fails, the second proxy network element will replace the first proxy network element, ensuring the normal operation of the heartbeat proxy.

[0118] See Figure 3, which is a flow chart of another heartbeat packet sending method provided in an embodiment of the present application. The method is applied to a first proxy network element, which is an SMF network element in the 5G system shown in Figure 1. As shown in Figure 3, the method includes:

[0119] S301. The SMF network element receives the heartbeat proxy policy sent by the PCF.

[0120] In one possible implementation, for some services configured on the application function (AF) network element, some UEs need a heartbeat proxy, such as Huawei's UE. The AF network element sends the identifiers and service information of these UEs to the PCF network element. The service information includes the address and port number of the application server, and the address and port number of the application server are used to distinguish different services, or to identify the type of service. When the target UE requests a service from the application server, the target UE creates a PDU session with the application server. After the PDU session is created, when the PCF network element knows the type of service requested by the target UE, it determines whether there is a UE that needs a heartbeat proxy for the service; if so, the PCF network element sends the identifier of the UE that needs a heartbeat proxy to the SMF network element. In one example, the PCF network element sends a heartbeat proxy policy to the SMF network element, wherein the heartbeat proxy policy includes the identifier of the UE that needs a proxy, the address and port number of the application server. Optionally, the heartbeat proxy policy also includes a heartbeat proxy identifier, a heartbeat proxy frequency, etc.

[0121] In another possible implementation, when the target UE requests a service from the application server, the target UE creates a PDU session with the application server. Since the PDU session creation process requires the participation of the AF network element, when the AF network element perceives this process, it initiates a heartbeat proxy: the AF network element sends the target UE identifier to the PCF network element, and the PCF network element then sends the target UE identifier to the SMF network element. In one example, the PCF network element sends a heartbeat proxy policy to the SMF network element, where the heartbeat proxy policy includes the target UE identifier. Optionally, the heartbeat proxy policy also includes a heartbeat proxy identifier, a heartbeat proxy frequency, etc.

[0122] It should be understood that the AF network element can obtain the target UE during the process of establishing a PDU session between the target UE and the application server.

[0123] In another possible implementation, when the target UE requests a service from the application server, the target UE creates a PDU session with the application server. Information about the application server that requires a heartbeat proxy between the target UE and the target UE will be configured in the target UE. If the target UE determines that a heartbeat proxy is required between the target UE and the application server when requesting a service from the application server, the target UE sends a third heartbeat proxy request to the SMF network element. The third heartbeat proxy request is used to request the network side to perform a heartbeat proxy between the target UE and the application server. In one example, the third heartbeat proxy request is carried in a PDU session establishment request or a PDU session modification request sent by the target UE. The SMF network element sends a first request to the PCF network element. The first request is a PDU session establishment request or a PDU session modification request.

[0124] In another possible implementation, the PCF network element is configured with the UE identifier that requires a heartbeat proxy and the service information that requires a heartbeat proxy. When the target UE requests a service from the application server, the target UE establishes a PDU session with the application server. After the PDU session is established, the PCF network element can obtain the identifier of the target UE or the service type requested by the target UE; the PCF network element determines whether the target UE needs a heartbeat proxy based on the identifier or service type of the target UE. If it is determined that a heartbeat proxy is needed, the PCF network element initiates a heartbeat proxy. The PCF network element sends a fourth heartbeat proxy request to the SMF network element, and the SMF network element sends a fourth heartbeat proxy request to the target UE. The fourth heartbeat proxy request is used to request that the network side perform a heartbeat proxy between the target UE and the application server; the SMF network element receives a response message from the target UE that agrees that the network side perform a heartbeat proxy between the target UE and the application server, and the SMF network element forwards the response message to the PCF network element. When the PCF network element receives the response message, it sends a heartbeat proxy policy to the SMF network element.

[0125] In one possible implementation, when the target UE requests a service from the application server, the target UE creates a PDU session with the application server. Information about the application server that requires a heartbeat proxy between the target UE and the application server is configured in the target UE. When the target UE determines that a heartbeat proxy is required between the target UE and the application server, the target UE sends a fifth heartbeat proxy request to the SMF network element. The fifth heartbeat proxy network element is used to request that the network side perform a heartbeat proxy between the target UE and the application server. The SMF network element sends a response message to the target UE in response to the fifth heartbeat proxy request. The response message includes information about the first proxy network element. After the target UE obtains the information about the first proxy network element, it requests the first proxy network element to perform a heartbeat proxy between the target UE and the application server based on the information about the first proxy network element.

[0126] The information of the first proxy network element includes at least one of an identifier of the first proxy network element and an address of the first proxy network element.

[0127] It should be noted that the target UE sends the fifth heartbeat proxy request to the SMF network element on the premise that the target UE and the application server have established a PDU session. After the target UE and the application server establish a PDU session, the target UE can obtain the information of the SMF network element.

[0128] S302. The SMF network element determines a heartbeat proxy rule based on the heartbeat proxy policy. The heartbeat proxy rule is used to determine whether the first proxy network element performs heartbeat proxy between the target UE and the application server.

[0129] In one possible implementation, the heartbeat proxy strategy includes an identifier of a UE requiring a heartbeat. The SMF network element pre-stores the identifier of the target UE, which may be obtained by the SMF network element during the process of establishing a PDU session between the target UE and the application server, or by other means, without limitation. The SMF network element matches the identifier of the target UE with the identifier of the UE requiring a heartbeat proxy, that is, determines whether the UE identifier of the heartbeat proxy includes the identifier of the target UE. If the UE identifier requiring a heartbeat proxy includes the identifier of the target UE, the match is successful, and the SMF network element determines that the first proxy network element performs heartbeat proxy between the target UE and the application server. The heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server. If the match is unsuccessful, it is determined that the first proxy network element is not required to perform heartbeat proxy between the target UE and the application server.

[0130] In another possible implementation, the heartbeat proxy strategy includes the identifier of the target UE, and the identifier of the UE requiring a heartbeat proxy is pre-stored in the SMF network element; the SMF network element matches the identifier of the target UE with the identifier of the UE requiring a heartbeat proxy, that is, determines whether the UE identifier of the heartbeat proxy includes the identifier of the target UE. If the UE identifier requiring a heartbeat proxy includes the identifier of the target UE, the match is successful, and then the SMF network element determines that the first proxy network element performs heartbeat proxy between the target UE and the application server, and the heartbeat proxy rule is used to indicate that the first proxy network element performs heartbeat proxy between the target UE and the application server; if the match is unsuccessful, it is determined that the first proxy network element is not required to perform heartbeat proxy between the target UE and the application server.

[0131] In one possible implementation, when it is determined that the first proxy network element performs heartbeat proxy between the target UE and the application server, the SMF network element sends a second heartbeat proxy request to the target UE and the application function AF network element respectively, wherein the second heartbeat proxy request is used to inform the target UE and the AF network element that the first proxy network element performs heartbeat proxy between the target UE and the application server.

[0132] In another possible implementation, the heartbeat proxy rule includes an identifier of a UE requiring heartbeat proxy, and the heartbeat proxy rule is used to instruct the first proxy network element to determine, based on the identifier of the UE requiring heartbeat proxy, whether the first proxy network element should perform heartbeat proxy between the target UE and the application server. In another possible implementation, the heartbeat proxy rule includes an identifier of a target UE, and the heartbeat proxy rule is used to instruct the first proxy network element to determine, based on the identifier of the target UE, whether the first proxy network element should perform heartbeat proxy between the target UE and the application server. In other words, the SMF network element does not perform a matching action, and the first proxy network element performs the matching action. In this way, the SMF network element does not need to perform a matching operation, thereby reducing the workload of the SMF network element.

[0133] S303. The SMF network element sends the heartbeat proxy rules to the first proxy network element.

[0134] It should be noted here that the specific operations of the first proxy network element after receiving the heartbeat proxy rule can be found in the specific description of the embodiment shown in FIG2 , and will not be described again here.

[0135] In one possible implementation, upon receiving the first information sent by the first proxy network element, the SMF network element sends the first information to the target UE, wherein the first information is used to indicate that the application server is unreachable; the first information is generated when the first proxy network element does not receive a response message from the application server for the heartbeat packet sent within a preset time period when sending a heartbeat packet to the application server. By sending the information indicating that the application server is unreachable to the target UE, the target UE can be made aware that the application server is unreachable. At this time, the target UE can disconnect from the application server to save connection resources, or re-establish a connection with the application server.

[0136] In one possible implementation, the SMF network element subscribes to a message from the AMF network element to subscribe to the reachability information of the target UE.

[0137] In one possible implementation, the SMF network element receives the second information sent by the AMF network element, where the second information is generated when the AMF network element perceives that the target UE is unreachable; the SMF network element sends the second information to the application server.

[0138] Specifically, the AMF network element can sense whether the target UE is reachable. There are two situations in which the target UE is reachable. One is that there is a signaling connection between the target UE and the network, that is, the connected state, and the AMF network element determines that the UE is reachable; the other is: there is temporarily no signaling connection between the target UE and the network, but the network can page the target UE and re-establish the signaling connection. At this time, the target UE is also reachable. The AMF network element can sense these two kinds of information and then determine whether the target UE is reachable. When the AMF network element senses that the target UE is unreachable, it sends a second message to the SMF network element, and the second information is used to indicate that the target UE is unreachable. The SMF network element sends the second message to the application server to inform the application server that the target UE is unreachable. By sending information to the application server indicating that the target UE is unreachable, the application server can know that the target UE is unreachable. At this time, the target UE can disconnect the connection with the target UE to save connection resources, or re-establish the connection with the target UE.

[0139] In one possible implementation, when the SMF network element detects a heartbeat proxy service failure of the first proxy network element or a device failure of the first proxy network element, it sends a context for restoring the heartbeat proxy service to the second proxy network element to instruct the second proxy network element to restore the heartbeat proxy between the target UE and the application server.

[0140] In one example, the first agent network element and the second agent network element are both UPF network elements; in one example, the first agent network element and the second agent network element are both first network elements.

[0141] In this way, when the heartbeat proxy service of the first proxy network element fails, or the equipment of the first proxy network element fails, the SMF network element instructs the second proxy network element to replace the work of the first proxy network element, ensuring the normal operation of the heartbeat proxy.

[0142] It can be seen that in the solution of the embodiment, by introducing a proxy network element to act on behalf of the UE to send heartbeat packets to the application server, it is beneficial to reduce the standby power consumption and background load of the UE, and at the same time can save network resources between the UE and the network. When the application server is unreachable, information indicating that the application server is unreachable is sent to the target UE, so that the target UE can know that the application server is unreachable, and the target UE can disconnect from the application server, saving connection resources. When the target UE is unreachable, information indicating that the target UE is unreachable is sent to the application server, so that the application server can know that the target UE is unreachable, and the target UE can disconnect from the target UE to save connection resources, or re-establish a connection with the target UE. When the heartbeat proxy service of the first proxy network element fails, or the equipment of the first proxy network element fails, the second proxy network element is instructed to replace the work of the first proxy network element, thereby ensuring the normal operation of the heartbeat proxy.

[0143] Referring to FIG4 , FIG4 is a schematic diagram of an interactive process of a heartbeat packet sending method provided in an embodiment of the present application. The method is applied to the system shown in FIG1 . As shown in FIG4 , the method includes:

[0144] S401. The AF network element sends a sixth heartbeat proxy request to the PCF network element.

[0145] In one possible implementation, some UEs, such as Huawei UEs, require a heartbeat proxy for certain services on the AF network element. The AF network element sends the identifiers and service information of these UEs to the PCF network element via the sixth heartbeat proxy request. The service information includes the address and port number of the application server, which are used to distinguish different services or identify the service type.

[0146] In another possible implementation, when the target UE requests a service from the application server, it establishes a PDU session with the application server. Since the PDU session creation process requires the participation of the AF network element, upon detecting this process, the AF network element initiates a heartbeat proxy: the AF network element sends a sixth heartbeat proxy request to the PCF network element, carrying the target UE identifier.

[0147] Optionally, the sixth heartbeat proxy request further includes a heartbeat proxy frequency and a heartbeat proxy identifier.

[0148] Optionally, when the AF network element is used to receive control instructions for the application server, the AF network element may be a part of the application server, or may be two different entities from the application server. The AF network element may be the AF layer of the target UE.

[0149] In an example, the AF network element sends the first heartbeat proxy request to the PCF network element, specifically: the AF network element directly sends the sixth heartbeat proxy request to the PCF network element, or the AF network element sends the sixth heartbeat proxy request to the PCF network element through the NEF network element.

[0150] S402. The PCF network element sends the heartbeat proxy policy to the SMF network element.

[0151] The heartbeat proxy strategy is used to indicate that the UPF network element or other network element performs the heartbeat proxy. Further, the heartbeat proxy strategy includes a heartbeat proxy identifier, which is used to indicate that the UPF network element or other network element performs the heartbeat proxy.

[0152] In an example, the heartbeat proxy policy includes the UE identifier requiring the heartbeat proxy, the address and port number of the application server. Optionally, the heartbeat proxy policy also includes the heartbeat proxy identifier and the heartbeat proxy frequency.

[0153] In one example, the heartbeat proxy policy includes a target UE identifier. Optionally, the heartbeat proxy policy also includes a heartbeat proxy identifier and a heartbeat proxy frequency.

[0154] In one example, the SMF network element is a common SMF network element or a dedicated SMF network element. It should be noted that the dedicated SMF network element here means that the SMF network element is specifically used to perform operations related to the heartbeat agent, and the common SMF network element means that the SMF network element can not only perform operations related to the heartbeat agent, but also perform other operations, such as establishing, modifying and deleting a control session, selecting a user plane node, etc.

[0155] This step may occur in the session establishment or session modification process. In one example, the heartbeat proxy policy is carried in the session establishment request or session modification request sent by the PCF network element to the SMF network element.

[0156] S403a. The SMF network element sends the first heartbeat proxy rule to the UPF network element.

[0157] When the heartbeat proxy policy includes the identifier of the target UE, the SMF network element matches the target UE identifier with the pre-stored identifier of the UE that requires a heartbeat proxy. If the match is successful, the SMF network element sends a first heartbeat proxy rule to the UPF network element. The UE identifier pre-stored in the SMF network element can be obtained by the SMF network element during the PDU session establishment / modification process, registration process, or other information from the PCF to the SMF. When the heartbeat proxy policy includes the identifier of the UE that requires a heartbeat proxy, the SMF network element matches the target UE identifier with the identifier of the UE that requires a heartbeat proxy. If the match is successful, the SMF network element sends the first heartbeat proxy rule to the UPF network element. The target UE identifier in the SMF network element can be obtained by the SMF network element during the PDU session establishment / modification process, registration process, or other information from the PCF to the SMF. The first heartbeat proxy rule is used to instruct the UPF network element to perform a heartbeat proxy between the target UE and the application server. Optionally, the first heartbeat proxy rule includes a heartbeat proxy identifier, which is used to instruct the UPF network element to perform a heartbeat proxy between the target UE and the application server.

[0158] The first heartbeat proxy rule includes but is not limited to any one or more of the address and port number of the application server, the heartbeat proxy identifier, and the heartbeat proxy frequency. If the match is unsuccessful, the SMF network element does not send the first heartbeat proxy rule to the UPF network element.

[0159] S403b. The SMF network element sends the second heartbeat proxy rule to the UPF network element.

[0160] When the SMF network element receives the heartbeat proxy policy sent by the PCF network element, the SMF does not match the UE identifier and directly sends the second heartbeat proxy rule to the UPF network element. The second heartbeat proxy rule includes, but is not limited to, any one or more of the following: the UE identifier, the address and port number of the application server, the heartbeat proxy identifier, and the heartbeat proxy frequency. The UE identifier here is the identifier of the target UE or the identifier of the UE that requires the heartbeat proxy.

[0161] Optionally, the UPF network element here is an ordinary UPF network element or a dedicated UPF network element. When the UPF network element is a dedicated UPF network element, if the SMF network element determines that the dedicated UPF network element performs heartbeat proxy between the target UE and the application server, the SMF network element sends a dedicated session diversion rule to the UPF network element of the large network. Among them, the dedicated session diversion rule includes but is not limited to the address and port number of the application server. The UPF network element of the large network here is a UPF network element that provides data packet routing and forwarding, serves as a mobility anchor point, serves as an uplink classifier to support routing service flows to the data network, and serves as a branch point to support multi-home PDU sessions. In other words, in one network, there are dedicated UPF network elements and large network UPFs.

[0162] S404. The UPF network element determines that the UPF network element performs heartbeat proxy between the target UE and the application server.

[0163] In one example, if the UPF network element receives the first heartbeat proxy rule, the UPF network element determines that the UPF network element performs heartbeat proxy between the target UE and the application server.

[0164] In another example, the UPF network element receives a second heartbeat proxy rule. If the second heartbeat proxy rule includes the identifier of the target UE, the UPF network element matches the identifier of the UE that needs a heartbeat proxy based on the target UE identifier. If the match is successful, the UPF network element determines that the UPF network element performs a heartbeat proxy between the target UE and the application server. The identifier of the UE that needs a heartbeat proxy pre-stored in the UPF network element may be obtained by the UPF network element during PDU session establishment / modification, registration process, or information sent by other SMFs to the UPF. If the match fails, the UPF network element determines that the UPF network element does not perform a heartbeat proxy between the target UE and the application server. If the second heartbeat proxy rule includes the identifier of the UE that needs a heartbeat proxy, the UPF network element matches the identifier of the UE that needs a heartbeat proxy based on the target UE identifier; if the match is successful, the UPF network element determines that the UPF network element performs a heartbeat proxy between the target UE and the application server. The target UE identifier in the UPF network element may be obtained by the UPF network element during PDU session establishment / modification, registration process, or information sent by other SMFs to the UPF. If the match fails, the UPF network element determines that the UPF network element does not perform heartbeat proxying between the target UE and the application server.

[0165] Optionally, when the UPF network element determines that the UPF network element performs heartbeat proxy between the target UE and the application server, it executes S405 and / or S407.

[0166] It should be noted that after the UPF network element receives the first heartbeat proxy rule or the second heartbeat proxy rule from the SMF network element, if it receives data from the application server, the UPF network element executes S404. This data corresponds to the service requested by the target UE. Of course, S404 can also be executed when the first heartbeat proxy rule or the second heartbeat proxy rule is received from the SMF network element, which is not limited here.

[0167] S405. The UPF network element sends a first heartbeat proxy request to the target UE.

[0168] Among them, the first heartbeat proxy request is used to request the UPF network element to perform heartbeat proxy between the target UE and the application server.

[0169] S406. The target UE sends a response message to the UPF network element to respond to the first heartbeat proxy request.

[0170] Among them, the response message used to respond to the first heartbeat proxy request is used to inform the UPF network element that the target UE agrees that the UPF network element will perform heartbeat proxy between the target UE and the application server.

[0171] S407. The UPF network element sends a first response message to the AF network element.

[0172] Among them, the first response message is used to inform the AF network element, and the UPF network element performs heartbeat proxy between the target UE and the application server.

[0173] S407 is optional and the execution order of S407 has no precedence relationship with the execution order of S405-S406.

[0174] S408. The UPF network element sends a second response message to the SMF network element.

[0175] Among them, the second response message is used to inform the SMF network element that the UPF network element performs heartbeat proxy between the target UE and the application server.

[0176] S409. The SMF network element sends a second heartbeat proxy request to the target UE.

[0177] Among them, the second heartbeat proxy request is used to inform the target UE that the UPF network element performs heartbeat proxy between the target UE and the application server.

[0178] S410. The target UE sends a third response message to the SMF network element.

[0179] The third response message is used to respond to the second heartbeat proxy request.

[0180] S411. The SMF network element sends a fourth response message to the AF network element.

[0181] Among them, the fourth response message is used to inform the AF network element that the UPF network element performs heartbeat proxy between the target UE and the application server.

[0182] S411 is optional and has no precedence relationship with the execution order of S409-S410.

[0183] It should be pointed out that S405-S407 and S408-S411 are executed one by one in the process.

[0184] The purpose of executing S405 and S409 is to inform the UE that the UPF network element performs heartbeat proxy between the target UE and the application server. Of course, other methods can also be used. For example, the AF network element informs the UE's application layer through the application layer protocol that the UPF network element performs heartbeat proxy between the target UE and the application server. It should be noted that this method requires executing S407 or S411 before this. When the AF network element is the application layer of the target UE, when the AF network element knows that the UPF network element performs heartbeat proxy between the target UE and the application server, the target UE knows that the UPF network element performs heartbeat proxy between the target UE and the application server, and there is no need for the UE's lower layer to perceive it.

[0185] S412. The SMF network element sends a subscription message to the AMF network element.

[0186] The subscription message is used to subscribe to the target UE reachability information.

[0187] S413. The UPF network element sends a heartbeat packet to the application server.

[0188] Optionally, the UPF network element sends heartbeat packets to the application server according to the heartbeat proxy frequency.

[0189] S414. The application server sends a response message to the UPF network element to respond to the heartbeat packet.

[0190] S415. The UPF network element sends the first information to the target UE.

[0191] Specifically, if the UPF network element does not receive a response message for the heartbeat packet fed back by the application server within a preset time period from the moment the heartbeat packet is sent to the application server, the first information is sent to the target UE, where the first information is used to indicate that the application server is unreachable. Optionally, the first information is sent directly to the target UE by the UPF network element through the user plane, or is sent to the UE through the control plane via the SMF network element.

[0192] S416. The AMF network element sends the second information to the SMF network element.

[0193] Specifically, the AMF network element can sense whether the target UE is reachable, that is, whether the target UE can receive messages normally. If it is determined that the UE is unreachable, the AMF network element sends a second message to the SMF network element, and the second message is used to indicate that the target UE is unreachable.

[0194] S417. The SMF network element sends the second information to the AF network element.

[0195] Specifically, the SMF network element sends the second information to the AF network element through the PCF network element and / or the NEF network element.

[0196] S418. The SMF network element sends the second information to the UPF network element.

[0197] S419. The UPF network element sends the second information to the application server.

[0198] Specifically, the UPF network element sends the second information to the application server directly or through the NEF network element.

[0199] It should be noted that S417 and S418-S419 are executed selectively in the process, that is, the second information can be sent to the AF network element or the application server via the user plane or the control plane.

[0200] In one possible implementation, during the heartbeat proxy process performed by the UPF network element, the SMF network element detects in real time whether the heartbeat proxy service fails, such as whether the heartbeat proxy function of the UPF network element fails, or whether the dedicated UPF network element has a device failure. If it is determined that the heartbeat proxy service fails, the SMF network element sends a context for restoring the heartbeat proxy service to the backup UPF network element, which is used to instruct the backup UPF network element to restore the heartbeat proxy service between the target UE and the application server. The context for restoring the heartbeat proxy service includes but is not limited to the session context and the heartbeat link flow table. The backup UPF network element restores the heartbeat proxy between the target UE and the application server.

[0201] In another possible implementation, during the heartbeat proxy process of the UPF network element, the UPF network element sends a context for restoring the heartbeat proxy service to the backup UPF network element; when the backup UPF network element detects a heartbeat proxy service failure, such as a functional failure of the heartbeat proxy of the UPF network element, a device failure in the dedicated UPF network element, and no backup information is received within a preset time period, the backup UPF network element restores the heartbeat proxy between the target UE and the application server.

[0202] The backup UPF network element restores the heartbeat proxy between the UE and the application server. The specific process includes:

[0203] The backup UPF network element determines whether the connection between the UE and the application server is disconnected, specifically in the following manner: the backup UPF network element sends a heartbeat connection establishment request to the target UE, requesting the backup UPF network element to perform heartbeat proxy between the target UE and the application server; if a response message to the heartbeat connection establishment request is received from the target UE, the backup UPF network element determines that the connection between the backup UPF network element and the target UE is normal. The backup UPF network element sends a heartbeat proxy message to the application server, for performing heartbeat proxy between the target UE and the application server; if a response message to the heartbeat proxy message is received from the application server, it indicates that the connection between the backup UPF network element and the application server is normal, and the backup UPF network element is now able to perform heartbeat proxy between the target UE and the application server; if no response message to the heartbeat proxy message is received from the application server within a preset time period, the backup UPF network element determines that the connection between the target UE and the application server is disconnected.

[0204] In another example, when a heartbeat proxy service failure is detected, the backup UPF network element assumes that the connection between the target UE and the application server is disconnected.

[0205] When it is determined that the connection between the target UE and the application server is disconnected, the backup UPF network element sends a reset message to the target UE. After receiving the reset message, the target UE establishes a connection with the application server, and the application server re-initiates execution of S401-S412, where the operations performed by the UPF network element are all performed by the backup UPF network element. After re-executing S401-S412, the backup UPF network element performs a heartbeat proxy between the UE and the application server. For the subsequent heartbeat proxy process, please refer to the relevant description of S413-S419 and will not be described here.

[0206] It can be seen that in the solution of this embodiment, the network side initiates the UPF agent UE to send heartbeat packets to the application server and receive the response message for the heartbeat packet fed back by the application server, without the participation of the UE. This heartbeat proxy method is conducive to reducing the standby power consumption and background load of the UE, while saving network resources between the UE and the network. When the heartbeat proxy fails, the backup UPF network element is introduced to act as the agent for the transmission and reception of heartbeat packets between the UE and the application server, thus avoiding a long-term heartbeat proxy failure.

[0207] Referring to FIG5 , FIG5 is an interactive flow diagram of another method for sending a heartbeat packet provided in an embodiment of the present application. The method is applied to the system shown in FIG1 . As shown in FIG5 , the method includes:

[0208] S501. The target UE sends a third heartbeat proxy request to the SMF network element.

[0209] The third heartbeat proxy request is used to request that the network side perform a heartbeat proxy between the target UE and the application server. Specifically, when the target UE requests a service from the application server, the target UE establishes a PDU session with the application server. The target UE is configured with information about the application server that requires a heartbeat proxy with the target UE. If the target UE determines that a heartbeat proxy is required with the application server when requesting a service from the application server, the target UE sends a third heartbeat proxy request to the SMF network element.

[0210] Optionally, the target UE sends a third heartbeat proxy request to the SMF network element through the AMF network element.

[0211] S502. The SMF network element sends a first request to the PCF network element.

[0212] The first request is used to request the heartbeat proxy policy. Optionally, the first request is a session modification request or a session creation request, and of course, it can also be other requests, which are not limited here.

[0213] S503. The PCF network element sends a seventh heartbeat proxy request to the AF network element.

[0214] The seventh heartbeat proxy request is used to request the network side to perform a heartbeat proxy between the target UE and the application server.

[0215] S504a. The AF network element sends a response message for responding to the seventh heartbeat proxy request to the PCF network element.

[0216] The response message for responding to the seventh heartbeat proxy request informs the PCF network element and the AF network element that they agree to perform the heartbeat proxy between the target UE and the application server by the network side.

[0217] S504b. The PCF network element sends a response message for responding to the third heartbeat proxy request to the target UE through the control direction via the SMF network element.

[0218] The response message for responding to the third heartbeat proxy request is used to inform the target UE that the network side agrees to perform heartbeat proxy between the target UE and the application server.

[0219] It should be noted that if the heartbeat proxy is insensitive to the AF network element, S503-S504b can be omitted in the process.

[0220] S505. The PCF network element sends the heartbeat proxy policy to the SMF network element.

[0221] The heartbeat proxy strategy is used to indicate that the UPF network element or other network element performs the heartbeat proxy. Further, the heartbeat proxy strategy includes a heartbeat proxy identifier, which is used to indicate that the UPF network element or other network element performs the heartbeat proxy.

[0222] In one example, the heartbeat proxy policy includes but is not limited to a heartbeat proxy identifier and a heartbeat proxy frequency. It should be noted that the heartbeat proxy frequency here is the frequency of sending heartbeat packets.

[0223] S506. The SMF network element sends the heartbeat proxy rules to the UPF network element.

[0224] The heartbeat proxy rule is used to instruct the UPF network element to perform heartbeat proxy between the target UE and the application server. The heartbeat proxy rule includes but is not limited to the heartbeat proxy frequency.

[0225] S507. The SMF network element sends a subscription message to the AMF network element.

[0226] The subscription message is used to subscribe to the target UE reachability information.

[0227] S508. The UPF network element sends a heartbeat packet to the application server.

[0228] Optionally, the UPF network element sends heartbeat packets to the application server according to the heartbeat proxy frequency.

[0229] S509. The application server sends a response message to the UPF network element to respond to the heartbeat packet.

[0230] S510. The UPF network element sends first information to the target UE.

[0231] Specifically, if the UPF network element does not receive a response message to the heartbeat packet from the application server within a preset time period from the moment the heartbeat packet is sent to the application server, the UPF network element sends a first message to the target UE, where the first message is used to indicate that the application server is unreachable. Optionally, the first message is sent directly to the target UE by the UPF network element, or is sent to the target UE via the SMF network element.

[0232] S511. The AMF network element sends the second information to the SMF network element.

[0233] Specifically, the AMF network element can sense whether the target UE is reachable, that is, whether the target UE can receive messages normally. If it is determined that the target UE is unreachable, the AMF network element sends a second message to the SMF network element, and the second message is used to indicate that the target UE is unreachable.

[0234] S512. The SMF network element sends the second information to the AF network element.

[0235] Specifically, the SMF network element sends the second information to the AF network element through the PCF network element and the NEF network element.

[0236] S513. The SMF network element sends the second information to the UPF network element.

[0237] S514. The UPF network element sends the second information to the application server.

[0238] Specifically, the UPF network element sends the second information to the application server through the NEF network element.

[0239] It should be noted that S512 and S513-S514 are executed selectively in the process, that is, the second information can be sent to the AF network element or the application server via the user plane or the control plane.

[0240] The heartbeat proxy fault detection process and the heartbeat proxy fault recovery process can be found in the relevant description of the embodiment shown in FIG4 , which will not be described again here. It should be noted that the re-execution of S501 - S507 is initiated by the target UE.

[0241] It can be seen that in the solution of this embodiment, the UE initiates the UPF to proxy the UE to send a heartbeat packet to the application server and receive the response message for the heartbeat packet fed back by the application server, without the UE's participation. This heartbeat proxy method is conducive to reducing the UE's standby power consumption and background load, while saving network resources between the UE and the network. When the heartbeat proxy fails, the introduction of a backup UPF network element to proxy the sending and receiving of heartbeat packets between the UE and the application server avoids long-term heartbeat proxy failures.

[0242] Referring to FIG6 , FIG6 is an interactive flow diagram of another method for sending a heartbeat packet provided in an embodiment of the present application. The method is applied to the system shown in FIG1 . As shown in FIG6 , the method includes:

[0243] S601. The PCF network element sends an eighth heartbeat proxy request to the AF network element.

[0244] Specifically, the PCF network element is configured with the UE identifier that requires a heartbeat proxy and the service information that requires a heartbeat proxy. When the target UE requests a service from the application server, the target UE establishes a PDU session with the application server. After the PDU session is established, the PCF network element can obtain the target UE identifier or the service type requested by the target UE. The PCF network element determines whether the target UE requires a heartbeat proxy based on the target UE identifier or service type. If it is determined that a heartbeat proxy is required, the PCF network element initiates a heartbeat proxy and sends an eighth heartbeat proxy request to the AF network element. The eighth heartbeat proxy request is used to request that the network side perform a heartbeat proxy between the target UE and the application server.

[0245] S602. The AF network element sends a response message for responding to the eighth heartbeat proxy request to the PCF network element.

[0246] The response message for responding to the eighth heartbeat proxy request informs the PCF network element and the AF network element that they agree to perform the heartbeat proxy between the target UE and the application server by the network side.

[0247] It should be noted that if the heartbeat proxy is insensitive to the AF network element, S601-S602 can be omitted in the process.

[0248] S603. The PCF network element sends a fourth heartbeat proxy request to the target UE.

[0249] Among them, the PCF network element sends a fourth heartbeat proxy request to the target UE via the SMF network element, and the fourth heartbeat proxy request is used by the network side to perform a heartbeat proxy between the target UE and the application server.

[0250] S604. The target UE sends a response message to the PCF network element for responding to the fourth heartbeat proxy request.

[0251] Among them, the target UE sends a response message for responding to the fourth heartbeat proxy request to the PCF network element via the SMF network element to inform the PCF network element that the target UE agrees to the network side to perform heartbeat proxy between the target UE and the application server.

[0252] S605. The PCF network element sends the heartbeat proxy policy to the SMF network element.

[0253] The heartbeat proxy policy is used to instruct the UPF network element or other network element to perform heartbeat proxy between the target UE and the application server. Further, the heartbeat proxy policy includes a heartbeat proxy identifier, which is used to instruct the UPF network element or other network element to perform heartbeat proxy between the target UE and the application server.

[0254] In one example, the heartbeat proxy policy includes but is not limited to a heartbeat proxy identifier and a heartbeat proxy frequency. It should be noted that the heartbeat proxy frequency here is the frequency of sending heartbeat packets.

[0255] S606. The SMF network element sends the sixth heartbeat proxy request to the UPF network element.

[0256] The sixth heartbeat proxy request includes a heartbeat proxy rule, which is used to instruct the UPF network element to perform a heartbeat proxy between the target UE and the application server. The sixth heartbeat proxy request also includes but is not limited to a heartbeat proxy frequency.

[0257] S607. The SMF network element sends a subscription message to the AMF network element.

[0258] The subscription message is used to subscribe to the target UE reachability information.

[0259] S608. The UPF network element sends a heartbeat packet to the application server.

[0260] Optionally, the UPF network element sends heartbeat packets to the application server according to the heartbeat proxy frequency.

[0261] S609. The application server sends a response message for responding to the heartbeat packet to the UPF network element.

[0262] S610. The UPF network element sends first information to the target UE.

[0263] Specifically, if the UPF network element does not receive a response message to the heartbeat packet from the application server within a preset time period from the moment the heartbeat packet is sent to the application server, the UPF network element sends a first message to the target UE, where the first message is used to indicate that the application server is unreachable. Optionally, the first message is sent directly to the target UE by the UPF network element, or is sent to the target UE via the SMF network element.

[0264] S611. The AMF network element sends the second information to the SMF network element.

[0265] Specifically, the AMF network element can sense whether the target UE is reachable, that is, whether the target UE can receive messages normally. If it is determined that the target UE is unreachable, the AMF network element sends a second message to the SMF network element, and the second message is used to indicate that the target UE is unreachable.

[0266] S612. The SMF network element sends the second information to the AF network element.

[0267] Specifically, the SMF network element sends the second information to the AF network element through the PCF network element and the NEF network element.

[0268] S613. The SMF network element sends the second information to the UPF network element.

[0269] S614. The UPF network element sends the second information to the application server.

[0270] Specifically, the UPF network element sends the second information to the application server through the NEF network element.

[0271] It should be noted that S612 and S613-S614 are executed selectively in the process, that is, the second information can be sent to the AF network element or the application server via the user plane or the control plane.

[0272] The heartbeat proxy fault detection process and the heartbeat proxy fault recovery process can be found in the relevant description of the embodiment shown in FIG4 , which will not be described again here. It should be noted that the re-execution of S601 - S607 is initiated by the UE.

[0273] As can be seen, in the solution of this embodiment, the PCF network element sends heartbeat packets to the application server through the UPF agent, and receives the response message to the heartbeat packet fed back by the application server, without the participation of the UE. This heartbeat proxy method is conducive to reducing the standby power consumption and background load of the UE, while saving network resources between the UE and the network. In the event of a heartbeat proxy failure, a backup UPF network element is introduced to act as an agent for the transmission and reception of heartbeat packets between the UE and the application server, thus avoiding a long-term heartbeat proxy failure.

[0274] Referring to FIG. 7 , FIG. 7 is a schematic diagram of an interactive process of a heartbeat packet sending method provided in an embodiment of the present application. The method is applied to the system shown in FIG. 1 . As shown in FIG. 7 , the method includes:

[0275] S701. The target UE sends a fifth heartbeat proxy request to the SMF network element.

[0276] Specifically, when the target UE requests a service from the application server, the target UE establishes a PDU session with the application server. Information about the application server that requires a heartbeat proxy between the target UE and the application server is configured in the target UE. When the target UE determines that a heartbeat proxy is required between the target UE and the application server, the target UE sends a fifth heartbeat proxy request to the SMF network element. The fifth heartbeat proxy network element is used to request that the network side perform a heartbeat proxy between the target UE and the application server.

[0277] The information of the first proxy network element includes at least one of an identifier of the first proxy network element and an address of the first proxy network element.

[0278] It should be noted that the target UE sends the fifth heartbeat proxy request to the SMF network element on the premise that the target UE and the application server have established a PDU session. After the target UE and the application server establish a PDU session, the target UE can obtain the information of the SMF network element.

[0279] Optionally, the UE sends a fifth heartbeat proxy request to the SMF network element via the control plane.

[0280] S702. The SMF network element sends a response message to the target UE to respond to the fifth heartbeat proxy request.

[0281] Among them, the response message used to respond to the second request carries information of the network element used for heartbeat proxy, such as at least one of the identifier of the UPF network element and the address of the UPF network element.

[0282] S703. The target UE sends a ninth heartbeat proxy request to the UPF network element.

[0283] Specifically, the target UE sends a ninth heartbeat proxy request to the UPF network element based on the identifier of the UPF network element or the address of the UPF network element, where the ninth heartbeat proxy request is used to request the UPF network element to perform a heartbeat proxy between the target UE and the application server. The ninth heartbeat proxy request includes but is not limited to a heartbeat proxy frequency.

[0284] S704. The UPF network element sends the tenth heartbeat proxy request to the AF network element.

[0285] The tenth heartbeat proxy request is used to request the UPF network element to perform heartbeat proxy between the target UE and the application server. The UPF network element sends the tenth heartbeat proxy request to the AF network element through the NEF network element.

[0286] S705. The AF network element sends a response message for responding to the tenth heartbeat proxy request to the UPF network element.

[0287] The response message for responding to the tenth heartbeat proxy request is used to inform the UPF network element that the AF network element agrees that the UPF network element will perform heartbeat proxy between the target UE and the application server. The AF network element sends a response message for responding to the tenth heartbeat proxy request to the UPF network element through the NEF network element.

[0288] It should be noted that if the heartbeat proxy is insensitive to the AF network element, S704-S705 can be omitted in the process.

[0289] S706. The UPF network element sends a response message to the target UE to respond to the ninth heartbeat proxy request.

[0290] Among them, the response message for responding to the ninth heartbeat proxy request is used to inform the target UE that the UPF network element agrees that the UPF network element will perform heartbeat proxy between the target UE and the application server.

[0291] S707. The UPF network element sends a heartbeat packet to the application server.

[0292] Specifically, the UPF network element sends a heartbeat packet to the application server according to the heartbeat proxy frequency.

[0293] S708. The application server sends a response message to the UPF network element to respond to the heartbeat packet.

[0294] S709. The UPF network element sends the first information to the target UE.

[0295] Specifically, if the UPF network element does not receive a response message for the heartbeat packet fed back by the application server within a preset time period from the moment the heartbeat packet is sent to the application server, the UPF network element sends a first message to the target UE, where the first message is used to indicate that the application server is unreachable. Optionally, the first message is sent to the target UE directly by the UPF network element through the user plane, or is sent to the target UE through the control plane via the SMF network element.

[0296] The heartbeat proxy fault detection process and the heartbeat proxy fault recovery process can be found in the relevant description of the embodiment shown in FIG4 , which will not be described again here. It should be noted that the re-execution of S701 - S706 is initiated by the UE.

[0297] It can be seen that the UE initiates the UPF proxy to send a heartbeat packet to the application server and receives the response message for the heartbeat packet fed back by the application server, without the UE's participation. This heartbeat proxy method is conducive to reducing the UE's standby power consumption and background load, while saving network resources between the UE and the network. In the event of a heartbeat proxy failure, the introduction of a backup UPF network element to act as an agent for the transmission and reception of heartbeat packets between the UE and the application server avoids long-term heartbeat proxy failures. Compared with the embodiment shown in Figure 5, there is no need to configure the heartbeat proxy policy, which is relatively simple to implement.

[0298] See Figure 8, which is a schematic diagram of an interactive process of a heartbeat packet sending method provided in an embodiment of the present application. The method is applied to the system shown in Figure 1. The method is applicable to MEC scenarios. As shown in Figure 8, the method includes:

[0299] S801. The UPF network element sends heartbeat proxy rules to the first network element.

[0300] Specifically, when the UPF network element determines that the first network element is to perform heartbeat proxying between the target UE and the application server, the UPF network element sends a heartbeat proxy rule to the first network element. The heartbeat proxy rule is used to instruct the first network element to perform heartbeat proxying between the UE and the application server. It should be noted that the implementation process of the UPF network element determining that the first network element is to perform heartbeat proxying between the target UE and the application server can be seen in the relevant description of Figures 4 to 7 and will not be described again here.

[0301] Optionally, the UPF network element encapsulates the heartbeat proxy request into a tunnel message or an IP message, and then sends the tunnel message or the IP message to the first network element.

[0302] S802. The first network element sends a heartbeat packet to the application server.

[0303] Optionally, the first network element sends a heartbeat packet to the application server according to the heartbeat proxy frequency.

[0304] S803. The application server sends a response message for responding to the heartbeat packet to the first network element.

[0305] S804. The first network element sends first information to the target UE.

[0306] Specifically, if the UPF network element does not receive a response message to the heartbeat packet from the application server within a preset time period from the moment the heartbeat packet is sent to the application server, the UPF network element sends a first message to the target UE, where the first message is used to indicate that the application server is unreachable. Optionally, the first message is sent directly to the target UE by the UPF network element, or is sent to the target UE via the SMF network element.

[0307] S805. The AMF network element sends the second information to the SMF network element.

[0308] Specifically, the AMF network element can sense whether the target UE is reachable, that is, whether the target UE can receive messages normally. If it is determined that the target UE is unreachable, the AMF network element sends a second message to the SMF network element, and the second message is used to indicate that the target UE is unreachable.

[0309] S806. The first network element sends second information to the AF network element.

[0310] Specifically, the first network element sends the second information to the AF network element through the PCF network element and the NEF network element.

[0311] S807. The SMF network element sends the second information to the first network element.

[0312] S808. The first network element sends second information to the application server.

[0313] Specifically, the first network element sends the second information to the application server through the NEF network element.

[0314] It should be noted that S806 and S807-S808 are executed selectively in the process, that is, the message indicating that the UE is unreachable can be sent to the application server via the user plane or the control plane.

[0315] In one possible implementation, during the heartbeat proxy process performed by the first network element, the SMF network element detects in real time whether a heartbeat proxy service failure has occurred, such as whether the heartbeat proxy function of the first network element has failed or whether a device failure has occurred in the dedicated first network element. If it is determined that the heartbeat proxy service has failed, the SMF network element sends a context for restoring the heartbeat proxy service to the backup first network element, instructing the backup first network element to restore the heartbeat proxy between the UE and the application server. The context for restoring the heartbeat proxy service includes, but is not limited to, a session context and a heartbeat link flow table. The backup first network element restores the heartbeat proxy between the target UE and the application server.

[0316] In another possible implementation, during the heartbeat proxy process of the first network element, the first network element sends a context for restoring the heartbeat proxy service to the backup first network element; when the backup first network element detects a heartbeat proxy service failure, such as a functional failure of the heartbeat proxy of the first network element or a device failure of the dedicated first network element, the backup first network element restores the heartbeat proxy between the UE and the application server.

[0317] Backing up the first network element to restore the heartbeat proxy between the UE and the application server includes the following steps:

[0318] The backup first network element determines whether the connection between the target UE and the AF network element is disconnected, specifically in the following manner: the backup first network element sends a heartbeat connection establishment request to the target UE, requesting the backup first network element to perform heartbeat proxy between the target UE and the application server; if a response message to the heartbeat connection establishment request is received from the UE, the backup first network element determines that the connection between the backup first network element and the target UE is normal. The backup first network element sends a heartbeat proxy message to the application server, for performing heartbeat proxy between the target UE and the application server; if a response message to the heartbeat proxy message is received from the application server, it indicates that the connection between the backup first network element and the application server is normal, and the backup first network element is now able to perform heartbeat proxy between the target UE and the application server; if no response message to the heartbeat proxy message is received from the application server within a preset time period, the backup first network element determines that the connection between the UE and the application server is disconnected.

[0319] In another example, when a heartbeat proxy service failure is detected, the backup first network element assumes that the connection between the target UE and the application server is disconnected.

[0320] Upon determining that the connection between the UE and the application server is disconnected, the backup first network element sends a reset message to the target UE. Upon receiving the reset message, the target UE establishes a connection with the application server and re-executes the process shown in FIG8 to implement heartbeat proxying between the target UE and the application server by the first network element. All operations previously performed by the first network element are now performed by the backup first network element. After re-execution of S801, the backup first network element performs heartbeat proxying between the target UE and the application server. The subsequent heartbeat proxying process can be found in the description of S802-S808 and will not be further described here. It should be noted that the UPF network element sends the heartbeat proxy rules to the backup first network element when the UPF network element determines that the backup first network element will perform heartbeat proxying between the target UE and the application server. The heartbeat proxy rules instruct the backup first network element to perform heartbeat proxying between the UE and the application server. It should be noted that the implementation process of the UPF network element determining that the backup first network element will perform heartbeat proxying between the target UE and the application server can be found in the description of FIG4-FIG7 and will not be further described here.

[0321] It can be seen that in the solution of this embodiment, in the MCE scenario, the first network element acts as an agent for the UE to send heartbeat packets to the application server and receive response messages to the heartbeat packets from the application server, without the participation of the UE. This heartbeat proxy method is conducive to reducing the standby power consumption and background load of the UE, while also saving network resources between the UE and the network. In the event of a heartbeat proxy failure, a backup first network element is introduced to act as an agent for the transmission and reception of heartbeat packets between the UE and the application server, thereby avoiding a long-term heartbeat proxy failure.

[0322] 9, which is a schematic diagram of the structure of a first proxy network element provided in an embodiment of the present application. The first proxy network element 900 is the UPF network element or the first network element in FIG1. ​​As shown in FIG9, the first proxy network element 900 includes:

[0323] Receiving unit 901, used to receive heartbeat proxy rules from SMF network elements;

[0324] A generating unit 902 is configured to determine, based on the heartbeat proxy rule, whether the first proxy network element performs a heartbeat proxy between the target UE and the application server; and generate a heartbeat packet when it is determined, based on the heartbeat proxy rule, that the first proxy network element performs a heartbeat proxy between the target UE and the application server.

[0325] The sending unit 903 is configured to send a heartbeat packet to the application server.

[0326] In a possible implementation, the heartbeat proxy rule is used to instruct the first proxy network element 900 to perform heartbeat proxy between the target UE and the application server.

[0327] In a possible implementation, the heartbeat proxy rule includes an identifier of the target UE, and the first proxy network element 900 further includes:

[0328] The matching unit 904 is used to match the identifier of the target UE with the pre-stored UE identifier. If the match is successful, the heartbeat proxy rule includes instruction information for instructing the first proxy network element 900 to perform heartbeat proxy between the target UE and the application server; the UE identifier pre-stored in the first proxy network element 900 is used to indicate the UE that needs heartbeat proxy.

[0329] In a possible implementation, the heartbeat proxy rule includes an identifier of a UE requiring a heartbeat proxy, and the first proxy network element 900 further includes:

[0330] The matching unit 904 is configured to match the target UE identifier with the UE identifier requiring heartbeat proxy. If the match succeeds, the heartbeat proxy rule includes instruction information for instructing the first proxy network element 900 to perform heartbeat proxy between the target UE and the application server.

[0331] In a possible implementation, the heartbeat proxy rule includes a heartbeat proxy frequency, and the heartbeat proxy frequency is a frequency at which the first proxy network element sends heartbeat packets to the application server.

[0332] In a possible implementation, the sending unit 903 is further configured to send a first heartbeat proxy request to the target UE, where the first heartbeat proxy request is used to request the first proxy network element 900 to perform a heartbeat proxy between the target UE and the application server;

[0333] The receiving unit 901 is further configured to receive a response message sent by the target UE to respond to the first heartbeat proxy request.

[0334] In one possible implementation, the first proxy network element is the first network element, and the heartbeat proxy rule from the SMF network element is forwarded to the first network element by the UPF network element. Further, the heartbeat proxy rule is forwarded to the first network element by the UPF network element when the UPF network element determines that the first network element is to perform heartbeat proxy between the target UE and the application server.

[0335] In one possible implementation, the receiving unit 901 is further configured to receive a response message for the heartbeat packet fed back by the application server after the sending unit 903 sends the heartbeat packet to the application server;

[0336] The sending unit 903 is also used to send a first message to the target UE if no response message for the heartbeat packet is received from the application server within a preset time period starting from the moment the sending unit 903 sends the heartbeat packet to the application server. The first message is used to indicate that the application server is unreachable.

[0337] In a possible implementation, the receiving unit 901 is further configured to receive second information sent by the SMF network element;

[0338] The sending unit 903 is further configured to send a second message to the application server. The second message is used to indicate that the target UE is unreachable; the second message is generated when the AMF network element senses that the target UE is unreachable and is sent to the SMF network element.

[0339] In a possible implementation, the sending unit 903 is further configured to send a context for restoring the heartbeat proxy service to the second proxy network element, so as to instruct the second proxy network element to restore the heartbeat proxy between the target UE and the application server when the first proxy network element fails.

[0340] It is worth noting that, for the specific functional implementation of the first proxy network element 900, please refer to the specific description of the embodiment shown in Figure 2. For example, the receiving unit 901 is used to execute the relevant content of S201, and the generating unit 902, the sending unit 903 and the matching unit 904 are used to execute the relevant content of S202. Each unit or module in the first proxy network element 900 can be individually or completely merged into one or more other units or modules to form a structure, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a structure, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0341] 10 is a schematic diagram of the structure of an SMF network element provided in an embodiment of the present application. The SMF network element 1000 is the SMF network element in FIG1 . The SMF network element 1000 includes:

[0342] Receiving unit 1001, configured to receive a heartbeat proxy policy sent by a PCF network element;

[0343] A determining unit 1002 is configured to determine a heartbeat proxy rule based on the heartbeat proxy policy, the heartbeat proxy rule being used to determine whether the first proxy network element performs heartbeat proxying between the target UE and the application server;

[0344] The sending unit 1003 is configured to send the heartbeat proxy rule to the first proxy network element.

[0345] In one possible implementation, the heartbeat proxy strategy includes the UE identifier that requires a heartbeat proxy, and the determination unit 1002 is specifically used to match the identifier of the target UE with the UE identifier that requires a heartbeat proxy; if the match is successful, the heartbeat proxy rule is determined to indicate that the first proxy network element performs heartbeat proxy between the target UE and the application server.

[0346] In one possible implementation, the heartbeat proxy strategy includes an identifier of the target UE, and the determination unit 1002 is specifically used to match the identifier of the target UE with a pre-stored UE identifier; wherein the pre-stored UE identifier is used to indicate the UE that requires a heartbeat proxy; if the match is successful, the heartbeat proxy rule is determined to indicate that the first proxy network element performs heartbeat proxy between the target UE and the application server.

[0347] In one possible implementation, the heartbeat proxy rule includes an identifier of a UE requiring heartbeat proxy, and the heartbeat proxy rule is used to instruct the first proxy network element to determine whether to perform heartbeat proxy between the target UE and the application server based on the identifier of the UE requiring heartbeat proxy.

[0348] In a possible implementation, the heartbeat proxy rule includes a target UE identifier, and the heartbeat proxy rule is used to instruct the first proxy network element to determine whether to perform heartbeat proxy between the target UE and the application server based on the target UE identifier.

[0349] In one possible implementation, the SMF network element 1000 further includes:

[0350] The sending unit 1003 is used to send a second heartbeat proxy request to the target UE and the AF network element respectively when it is determined that the first proxy network element performs a heartbeat proxy between the target user equipment UE and the application server, wherein the second heartbeat proxy request is used to inform the target UE and the AF network element that the first proxy network element performs a heartbeat proxy between the target UE and the application server.

[0351] In one possible implementation, the SMF network element 1000 further includes:

[0352] The receiving unit 1001 is further configured to receive a third heartbeat proxy request sent by the target UE, wherein the third heartbeat proxy request is used to request the network side to perform a heartbeat proxy between the target UE and the application server; and to send a first request to the PCF network element, wherein the first request is used to request the heartbeat proxy policy.

[0353] In one possible implementation, the SMF network element 1000 further includes:

[0354] The receiving unit 1001 is further configured to receive a fourth heartbeat proxy request sent by the PCF network element, where the fourth heartbeat proxy request is sent when the application server agrees that the network side perform a heartbeat proxy between the target UE and the application server; the fourth heartbeat proxy request is used to request that the network side perform a heartbeat proxy between the target UE and the application server;

[0355] The sending unit 1003 is further configured to send a fourth heartbeat proxy request to the target UE;

[0356] The receiving unit 1001 is further configured to receive and send a response message of the target UE to the fourth heartbeat proxy request to the PCF network element. The response message is configured to inform the PCF network element that the target UE agrees to perform heartbeat proxy between the target UE and the application server by the network side.

[0357] In one possible implementation, the SMF network element 1000 further includes:

[0358] The sending unit 1003 is also used to send the first information to the target UE when the receiving unit 1001 receives the first information sent by the first proxy network element, wherein the first information is used to indicate that the application server is unreachable; the first information is generated when the first proxy network element sends a heartbeat packet to the application server and does not receive a response message from the application server for the heartbeat packet within a preset time period.

[0359] In one possible implementation, the SMF network element 1000 further includes:

[0360] The receiving unit 1001 is also used to receive the second information sent by the AMF network element, where the second information is generated when the AMF network element perceives that the target UE is unreachable; the SMF network element sends the second information to the application server.

[0361] In one possible implementation, the SMF network element 1000 further includes:

[0362] The sending unit 1003 is also used to send a subscription message to the AMF network element, where the subscription message is used to subscribe to the reachability information of the target UE.

[0363] In one possible implementation, the method of this embodiment further includes:

[0364] The sending unit 1003 is further configured to send a context for restoring the heartbeat proxy service to the second proxy network element when a heartbeat proxy service failure of the first proxy network element or a device failure of the first proxy network element is detected, so as to instruct the second proxy network element to restore the heartbeat proxy between the target UE and the application server.

[0365] It is worth noting that, for the specific functional implementation of the SMF network element 1000, please refer to the specific description of the embodiment shown in Figure 3 above. For example, the receiving unit 1001 is used to execute the relevant content of S301 and S303, and the determination unit 1002 is used to execute the relevant content of S302. The sending unit 1003 is used to execute the relevant content of S303. The various units or modules in the SMF network element 1000 can be individually or completely merged into one or several other units or modules to form a structure, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a structure, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0366] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 11 , which also provides a schematic structural diagram of a first proxy network element 1100. The first proxy network element 1100 shown in Figure 11 includes a memory 1101, a processor 1102, a communication interface 1103, and a bus 1104. The memory 1101, processor 1102, and communication interface 1103 are interconnected via bus 1104.

[0367] Optionally, the memory 1101 is a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM).

[0368] The memory 1101 can store programs. When the program stored in the memory 1101 is executed by the processor 1102, the processor 1102 and the communication interface 1103 are used to execute the various steps of the heartbeat packet sending method of the embodiment shown in FIG. 2 .

[0369] The processor 1102 uses a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the first proxy network element 900 of the embodiment of the present application, or to execute the heartbeat packet sending method of the embodiment shown in Figure 2 of the present application.

[0370] Processor 1102 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the heartbeat packet sending method shown in Figure 2 of the present application can be completed by hardware integrated logic circuits or software instructions in processor 1102. Optionally, processor 1102 is a general-purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Processor 1102 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor is a microprocessor or any conventional processor. The steps of the method disclosed in conjunction with the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, or other mature storage medium in the art. The storage medium is located in the memory 1101, and the processor 1102 reads the information in the memory 1101 and combines its hardware to complete the functions required to be executed by the units included in the first proxy network element 900 of the embodiment of the present application, or executes the heartbeat packet sending method of the embodiment shown in Figure 2.

[0371] The communication interface 1103 uses a transceiver device such as, but not limited to, a transceiver to implement communication between the first proxy network element 1100 and other devices (such as the SMF network element shown in FIG1 ) or a communication network.

[0372] The bus 1104 may include a path for transmitting information between various components of the first agent network element 1100 (eg, the memory 1101 , the processor 1102 , and the communication interface 1103 ).

[0373] It should be noted that although the first proxy network element 1100 shown in FIG11 only shows a memory, a processor, and a communication interface, during the specific implementation process, those skilled in the art will understand that the first proxy network element 1100 also includes other components necessary for normal operation. At the same time, based on specific needs, those skilled in the art will understand that the first proxy network element 1100 may also include hardware components that implement other additional functions. Furthermore, those skilled in the art will understand that the first proxy network element 1100 may also include only the components necessary to implement the embodiments of the present application, and does not necessarily need to include all of the components shown in FIG11.

[0374] Based on the description of the above method embodiment and the related device embodiment, please refer to Figure 12, which shows a schematic diagram of the structure of an SMF network element 1200 provided in the embodiment of the present application. The SMF network element 1200 shown in Figure 12 includes a memory 1201, a processor 1202, a communication interface 1203, and a bus 1204. The memory 1201, the processor 1202, and the communication interface 1203 are connected to each other via the bus 1204.

[0375] Optionally, the memory 1201 is a ROM, a static storage device, a dynamic storage device or a RAM.

[0376] The memory 1201 can store programs. When the program stored in the memory 1201 is executed by the processor 1202, the processor 1202 and the communication interface 1203 are used to execute the various steps of the heartbeat packet sending method of the embodiment shown in FIG. 3 .

[0377] The processor 1202 uses a general-purpose CPU, microprocessor, ASIC, GPU or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the SMF network element 1000 of the embodiment of the present application, or to execute the heartbeat packet sending method of the embodiment shown in Figure 3 of the present application.

[0378] Processor 1202 can also be an integrated circuit chip with signal processing capabilities. During implementation, the various steps of the heartbeat packet sending method shown in Figure 3 of the present application can be completed by hardware integrated logic circuits in processor 1202 or by software instructions. Optionally, processor 1202 is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. Processor 1202 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor is a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory 1201, and the processor 1202 reads the information in the memory 1201, and combines its hardware to complete the functions required to be performed by the units included in the SMF network element 1000 of the embodiment of the present application, or executes the heartbeat packet sending method of the embodiment shown in Figure 3.

[0379] The communication interface 1203 uses a transceiver device such as but not limited to a transceiver to realize communication between the SMF network element 1200 and other devices (such as UPF network elements and PCF network elements) or communication networks.

[0380] The bus 1204 may include a path for transmitting information between the various components of the SMF network element 1200 (eg, the memory 1201, the processor 1202, the communication interface 1203).

[0381] It should be noted that although the SMF network element 1200 shown in FIG12 only shows a memory, a processor, and a communication interface, in the specific implementation process, those skilled in the art should understand that the SMF network element 1200 also includes other devices necessary for normal operation. At the same time, according to specific needs, those skilled in the art should understand that the SMF network element 1200 may also include hardware devices that implement other additional functions. In addition, those skilled in the art should understand that the SMF network element 1200 may also include only the devices necessary to implement the embodiments of the present application, and does not necessarily include all the devices shown in FIG12.

[0382] An embodiment of the present application further provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to implement the heartbeat packet sending method of the embodiment of the present application.

[0383] Optionally, as an implementation method, the chip further includes a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the heartbeat packet sending method.

[0384] An embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is executed on a computer or a processor, the computer or processor executes one or more steps in any of the above methods.

[0385] The present application also provides a computer program product comprising instructions, which, when executed on a computer or processor, causes the computer or processor to execute one or more steps in any of the above methods.

[0386] Those skilled in the art will appreciate that the functions described in conjunction with the various illustrative logic blocks, modules, and algorithm steps disclosed herein can be implemented by hardware, software, firmware, or any combination thereof. If implemented in software, the functions described by the various illustrative logic blocks, modules, and steps may be stored or transmitted as one or more instructions or codes on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to tangible media, such as data storage media, or communication media including any media that facilitates the transfer of computer programs from one place to another (e.g., based on a communication protocol). In this manner, computer-readable media may generally correspond to (1) non-transitory tangible computer-readable storage media, or (2) communication media, such as signals or carrier waves. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in this application. A computer program product may include computer-readable media.

[0387] By way of example, and not limitation, such computer-readable storage media include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, any connection is properly referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of media. However, it should be understood that the computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are actually directed to non-transitory tangible storage media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and Blu-ray disc. Disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also intended to be included within the scope of computer-readable media.

[0388] Instructions may be executed by one or more processors, such as one or more DSPs, general-purpose microprocessors, ASICs, FPGAs, or other equivalent integrated or discrete logic circuits. Thus, the term "processor," as used herein, may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Additionally, in some aspects, the functionality described by the various illustrative logical blocks, modules, and steps described herein is provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a combined codec. Furthermore, the techniques may be fully implemented in one or more circuits or logic elements.

[0389] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the division of the unit is only a logical function division, and there are other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Optionally, the mutual coupling, direct coupling, or communication connection shown or discussed is an indirect coupling or communication connection through some interfaces, devices or units, such as electrical, mechanical or other forms.

[0390] Optionally, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., located in one place, or distributed across multiple network units. Some or all of the units may be selected based on actual needs to achieve the purpose of the solution of this embodiment.

[0391] In the above embodiments, all or part of the embodiments can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.

[0392] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A heartbeat packet sending method, characterized in that: The method is applied to a first proxy network element, and the method includes: Receive heartbeat proxy rules from session management function network element; When it is determined based on the heartbeat proxy rule that the first proxy network element performs heartbeat proxy between the target user equipment UE and the application server, the heartbeat packet is generated and sent to the application server.

2. The method according to claim 1, characterized in that The heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server.

3. The method according to claim 1, characterized in that The heartbeat proxy rule includes a UE identifier that requires a heartbeat proxy, and the method further includes: Matching the target UE identifier with the UE identifier that requires a heartbeat proxy; If the match is successful, it is determined that the first proxy network element performs heartbeat proxy between the target UE and the application server.

4. The method according to claim 1, characterized in that: The heartbeat proxy rule includes the target UE identifier, and the method further includes: Matching the target UE identifier with a pre-stored UE identifier; wherein the pre-stored UE identifier is used to indicate a UE that requires a heartbeat proxy; If the match is successful, it is determined that the first proxy network element performs heartbeat proxy between the target UE and the application server.

5. The method according to any one of claims 1 to 4, characterized in that: The heartbeat proxy rule also includes a heartbeat proxy frequency, where the heartbeat proxy frequency is the frequency at which the first proxy network element sends the heartbeat packet to the application server.

6. The method according to any one of claims 3 to 5, characterized in that: The method further comprises: Sending a first heartbeat proxy request to the target UE, where the first heartbeat proxy request is used to request the first proxy network element to perform a heartbeat proxy between the target UE and the application server; Receive a response message sent by the target UE to respond to the first heartbeat proxy request.

7. The method according to any one of claims 1 to 6, characterized in that: The first proxy network element includes a first network element, and the heartbeat proxy rule from the session management function network element is forwarded to the first network element by the user plane function network element.

8. The method according to claim 7, characterized in that The heartbeat proxy rule is determined by the user plane functional network element and forwarded to the first network element when the first network element performs heartbeat proxy between the target UE and the application server.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: If no response message of the application server to the heartbeat packet is received within a preset time period starting from the moment when the first proxy network element sends the heartbeat packet to the application server, first information is sent to the target UE, where the first information is used to indicate that the application server is unreachable.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: Receiving second information sent by the session management function network element; wherein the second information is used to indicate that the target UE is unreachable, and the second information is generated when the access and mobility management function network element perceives that the target UE is unreachable, and is sent to the session management function network element; The second information is sent to the application server.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: A context for restoring the heartbeat proxy service is sent to the second proxy network element to instruct the second proxy network element to restore the heartbeat proxy between the target UE and the application server when the first proxy network element fails.

12. A method for sending a heartbeat packet, characterized in that: Applied to a session management function network element, the method comprises: Receive the heartbeat proxy policy sent by the policy control function network element; Generate a heartbeat proxy rule based on the heartbeat proxy strategy, where the heartbeat proxy rule is used to determine whether the first proxy network element performs a heartbeat proxy between a target user equipment UE and an application server; The heartbeat proxy rule is sent to the first proxy network element.

13. The method according to claim 12, characterized in that The heartbeat proxy strategy includes a UE identifier that requires a heartbeat proxy, and generating a heartbeat proxy rule according to the heartbeat proxy strategy includes: Matching the UE identifier that requires a heartbeat proxy with the identifier of the target UE; If the match succeeds, the heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server.

14. The method according to claim 12, characterized in that The heartbeat proxy strategy includes the target UE identifier, and generating the heartbeat proxy rule according to the heartbeat proxy strategy includes: Matching the target UE identifier with a pre-stored UE identifier; wherein the pre-stored UE identifier is used to indicate a UE that requires a heartbeat proxy; If the match succeeds, the heartbeat proxy rule is used to instruct the first proxy network element to perform heartbeat proxy between the target UE and the application server.

15. The method according to claim 12, characterized in that The heartbeat proxy rule includes an identifier of a UE requiring a heartbeat proxy, and the heartbeat proxy rule is used to instruct the first proxy network element to determine whether the first proxy network element performs a heartbeat proxy between the target UE and the application server based on the identifier of the UE requiring a heartbeat proxy.

16. The method according to claim 12, characterized in that The heartbeat proxy rule includes the target UE identifier, and the heartbeat proxy rule is used to instruct the first proxy network element to determine whether the first proxy network element performs heartbeat proxy between the target UE and the application server based on the target UE identifier.

17. The method according to any one of claims 12 to 16, characterized in that: The method comprises: When it is determined that the first proxy network element performs heartbeat proxy between the target UE and the application server, a second heartbeat proxy request is sent to the target UE and the application function network element respectively, The second heartbeat proxy request is used to inform the target UE and the application function network element that the first proxy network element performs heartbeat proxy between the target UE and the application server.

18. The method according to claim 12, characterized in that The method further comprises: Receiving a third heartbeat proxy request sent by the target UE, where the third heartbeat proxy request is used to request the network side to perform a heartbeat proxy between the target UE and the application server; A first request is sent to the policy control function network element, where the first request is used to request the heartbeat proxy policy.

19. The method according to claim 12, characterized in that The method further comprises: receiving a fourth heartbeat proxy request sent by the PCF network element, wherein the fourth heartbeat proxy request is sent when the application server agrees that the network side performs a heartbeat proxy between the target UE and the application server; the fourth heartbeat proxy request is used to request the network side to perform a heartbeat proxy between the target UE and the application server; Sending the fourth heartbeat proxy request to the target UE; Receive and send a response message of the target UE to the fourth heartbeat proxy request to the policy control function network element, wherein the response message is used to inform the policy control function network element that the target UE agrees that the network side performs heartbeat proxy between the target UE and the application server.

20. The method according to any one of claims 12 to 19, characterized in that: The method further comprises: When receiving the first information sent by the first proxy network element, sending the first information to the target UE, Among them, the first information is used to indicate that the application server is unreachable; the first information is generated when the first proxy network element sends a heartbeat packet to the application server and does not receive a response message from the application server for the heartbeat packet within a preset time period.

21. The method according to any one of claims 12 to 20, characterized in that: The method further comprises: receiving second information sent by an access and mobility management function network element, where the second information is generated when the access and mobility management network element senses that the target UE is unreachable; The second information is sent to the application server.

22. The method according to any one of claims 12 to 21, characterized in that: The method further comprises: Send a subscription message to the access and mobility management network element to subscribe to the reachability information of the target UE.

23. The method according to any one of claims 12 to 22, characterized in that: The method further comprises: When a heartbeat proxy service failure of the first proxy network element or a device failure of the first proxy network element is detected, a context for restoring the heartbeat proxy service is sent to a second proxy network element to instruct the second proxy network element to restore the heartbeat proxy between the target UE and the application server.

24. A first proxy network element, characterized in that: The first proxy network element includes a unit or module for implementing the method according to any one of claims 1-11.

25. A session management function network element, characterized in that: The session management function network element includes a unit or module for implementing the method as described in any one of claims 12-23.

26. A method for sending a heartbeat packet, characterized in that: The method is applied to a communication system, the communication system comprising a target user equipment UE, a first proxy network element, a session management function network element, a policy control function network element and an application server, and the method comprises: The session management function network element receives the heartbeat proxy policy sent by the policy control function network element; The session management function network element generates a heartbeat proxy rule based on the heartbeat proxy rule, wherein the heartbeat proxy rule is used to determine whether the first proxy network element performs a heartbeat proxy between the target UE and the application server; The session management function network element sends the heartbeat proxy rule to the first proxy network element; When the first proxy network element determines, based on the heartbeat proxy rule, that the first proxy network element performs heartbeat proxy between the target UE and the application server, the first proxy network element generates the heartbeat packet and sends the heartbeat packet to the application server.

27. A communication system, characterized in that: The communication system includes a user equipment, a first proxy network element, a policy control function network element, a session management function network element and an application server, The session management function network element is used to receive the heartbeat proxy policy sent by the policy control function network element; The session management function network element is used to generate a heartbeat proxy rule based on the heartbeat proxy rule, wherein the heartbeat proxy rule is used to determine whether the first proxy network element performs a heartbeat proxy between the target UE and the application server; A session management function network element, configured to send the heartbeat proxy rule to the first proxy network element; The first proxy network element is configured to generate the heartbeat packet and send the heartbeat packet to the application server when it is determined based on the heartbeat proxy rule that the first proxy network element performs heartbeat proxy between the target UE and the application server.

28. A first proxy network element, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 1 to 11.

29. A session management function network element, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 12 to 23.

30. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 23 is implemented.

Images