CN110768853A - Heartbeat detection processing method and device - Google Patents
Heartbeat detection processing method and device Download PDFInfo
- Publication number
- CN110768853A CN110768853A CN201810824181.8A CN201810824181A CN110768853A CN 110768853 A CN110768853 A CN 110768853A CN 201810824181 A CN201810824181 A CN 201810824181A CN 110768853 A CN110768853 A CN 110768853A
- Authority
- CN
- China
- Prior art keywords
- heartbeat
- sender
- heartbeat detection
- response message
- detection request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
Abstract
The embodiment of the invention discloses a heartbeat detection processing method and a heartbeat detection processing device, wherein the method applied to a sender comprises the following steps: sending a heartbeat detection request to a receiver so that the receiver judges whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat detection request carries information indicating the identity of the sender.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a heartbeat detection processing method and apparatus.
Background
In the current separation scheme of Control Plane and User Plane (CU, Control Plane and User Plane), the Control Plane (CP, Control Plane) and the User Plane (UP, User Plane) perform message communication via a cups (Control Plane and User Plane separation) protocol, the two need to establish coupling first to carry a User session, 1 CP can establish coupling with a plurality of UPs, and 1 UP can also establish coupling with a plurality of CPs, that is, the relationship is many-to-many. After the CP and the UP establish the coupling, both need to actively initiate a heartbeat detection request to maintain the coupling state. For the receiver, after receiving the heartbeat detection request, if the coupling with the sender is found to be effective, a heartbeat response message needs to be replied to the sender; if the coupling status is not valid, no response should be returned. However, in the heartbeat message of the current CUPS protocol, only one TimeStamp (TimeStamp) field of the request and response messages represents the restart time of the sender. Thus, if the sending address or port of the sender changes, the receiver cannot know who sent the heartbeat detection request. Typical scenarios are such as: the address of the CP changes due to the configuration or reassignment of the IP; the messages sent by the CP to the UP pass through a Network Address Translation (NAT) device, and the addresses of all the messages are replaced by the addresses of the NAT device. In these cases, since the UP does not know the identity of the CP, it cannot determine whether to reply a heartbeat response to the peer according to the validity of the coupling, and finally, the consistency of the coupling state cannot be guaranteed. The above example describes a scenario in which the CP sends heartbeat detection to the UP, and the same is true when the UP sends heartbeat detection to the CP.
Disclosure of Invention
In order to solve the foregoing technical problem, embodiments of the present invention desirably provide a heartbeat detection processing method and apparatus, which can perform heartbeat detection with an opposite end in a scenario where a CP and an UP are separated and a local end address or a port is changed.
In a first aspect, an embodiment of the present invention provides a heartbeat detection processing method, which is applied to a sender, and the method includes:
sending a heartbeat detection request to a receiver so that the receiver judges whether a heartbeat response message is returned or not based on the heartbeat detection request;
wherein, the heartbeat detection request carries information indicating the identity of the sender.
In this embodiment of the present invention, optionally, the method further includes:
receiving a heartbeat response message returned by the receiver; wherein, the heartbeat response message carries information indicating the identity of the receiver.
In this embodiment of the present invention, optionally, the method further includes:
the identity of the sender of the message is indicated by adding a preset field.
In this embodiment of the present invention, optionally, when receiving the heartbeat response message returned by the receiver, the method further includes:
determining a receiver to establish or maintain a coupled state with the sender based on the heartbeat response message.
In a second aspect, an embodiment of the present invention provides a heartbeat detection processing method, which is applied to a receiving party, and the method includes:
receiving a heartbeat detection request sent by a sender, wherein the heartbeat detection request carries information indicating the identity of the sender;
judging whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat response message carries information indicating the identity of the receiver.
In this embodiment of the present invention, optionally, the determining whether to return a heartbeat response message based on the heartbeat detection request includes:
determining a sender identifier based on information which is carried by the heartbeat detection request and indicates the identity of the sender;
verifying the coupling state corresponding to the sender identification;
if the verification result is that the coupling state corresponding to the sender identification is normal, judging to return a heartbeat response message; otherwise, judging not to return the heartbeat response message.
In this embodiment of the present invention, optionally, the method further includes:
the identity of the sender of the message is indicated by adding a preset field.
In a third aspect, an embodiment of the present invention provides a heartbeat detection processing apparatus, which is applied to a sender, where the apparatus includes:
the first sending unit is used for sending a heartbeat detection request to the receiver so that the receiver judges whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat detection request carries information indicating the identity of the sender;
and the first processing unit is used for adding information indicating the identity of the sender in the heartbeat detection request.
In this embodiment of the present invention, optionally, the apparatus further includes:
a first receiving unit, configured to receive a heartbeat response message returned by the receiving party; wherein, the heartbeat response message carries information indicating the identity of the receiver.
In this embodiment of the present invention, optionally, the first processing unit is further configured to indicate an identity of a sender of the message by adding a preset field.
In this embodiment of the present invention, optionally, the first processing unit is further configured to:
and when the first receiving unit receives the heartbeat response message returned by the receiver, determining the receiver which establishes or maintains a coupling state with the sender based on the heartbeat response message.
In a fourth aspect, an embodiment of the present invention provides a heartbeat detection processing apparatus, which is applied to a receiving side, where the apparatus includes:
the second receiving unit is used for receiving a heartbeat detection request sent by a sender, wherein the heartbeat detection request carries information indicating the identity of the sender;
the second processing unit is used for judging whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat response message carries information indicating the identity of the receiver;
and the second sending unit is used for sending the heartbeat response message to the sender.
In this embodiment of the present invention, optionally, the second processing unit is further configured to:
determining a sender identifier based on information which is carried by the heartbeat detection request and indicates the identity of the sender;
verifying the coupling state corresponding to the sender identification;
if the verification result is that the coupling state corresponding to the sender identification is normal, judging to return a heartbeat response message; otherwise, judging not to return the heartbeat response message.
In this embodiment of the present invention, optionally, the second processing unit is further configured to:
the identity of the sender of the message is indicated by adding a preset.
In a fifth aspect, an embodiment of the present invention further provides a computer storage medium, where computer-executable instructions are stored in the computer storage medium, and the computer-executable instructions are used to execute the heartbeat detection processing method applied to the sender according to the embodiment of the present invention.
In a sixth aspect, an embodiment of the present invention further provides a computer storage medium, where computer-executable instructions are stored in the computer storage medium, and the computer-executable instructions are used to execute the heartbeat detection processing method applied to a receiving party according to the embodiment of the present invention.
In the technical scheme of the embodiment of the invention, a sender sends a heartbeat detection request to a receiver so that the receiver judges whether to return a heartbeat response message based on the heartbeat detection request; wherein, the heartbeat detection request carries information indicating the identity of the sender. Because the heartbeat detection request carries information indicating the identity of the sender, the receiver does not rely on judging the coupling state with the sender according to the address and the port of the sender any more, and can perform heartbeat detection with the opposite end under the condition that the address or the port of the local end is changed under the condition that the CP and the UP are separated, thereby being beneficial to successfully maintaining coupling with the opposite end through the heartbeat detection.
Drawings
Fig. 1 is a schematic flow chart of a heartbeat detection processing method according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart illustrating another method for detecting and processing heartbeat according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a heartbeat detection process provided in an embodiment of the present invention;
fig. 4 is a schematic diagram of a heartbeat detection interaction initiated by a CP in an embodiment of the present invention;
FIG. 5 is a schematic diagram of interaction of heartbeat detection initiated by UP in an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a heartbeat detection processing apparatus according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another heartbeat detection processing apparatus according to an embodiment of the present invention.
Detailed Description
So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.
Fig. 1 is a schematic flowchart of a heartbeat detection processing method according to an embodiment of the present invention, which is applied to a sender of a heartbeat detection request, and as shown in fig. 1, the method includes:
step 101: and sending a heartbeat detection request to the receiver so that the receiver judges whether to return a heartbeat response message based on the heartbeat detection request.
Wherein, the heartbeat detection request carries information indicating the identity of the sender.
In some alternative embodiments, the identity of the sender of the message is indicated by adding a preset field.
For example, the preset field may be a Node identification (Node ID) field.
It should be noted that the messages in the message sender identity include, but are not limited to, heartbeat detection request and heartbeat response messages.
Further, the method further comprises:
step 102: receiving a heartbeat response message returned by the receiver; wherein, the heartbeat response message carries information indicating the identity of the receiver.
In some optional embodiments, when receiving the heartbeat response message returned by the receiving side, the method further includes:
determining a receiver to establish or maintain a coupled state with the sender based on the heartbeat response message.
In some specific embodiments, when receiving a heartbeat response message returned by the receiving side, the method further includes:
and determining the receiver establishing or maintaining the coupling state with the sender based on the information which is carried by the heartbeat response message and indicates the identity of the receiver.
For example, the sender 1 sends a heartbeat detection request to N receivers, and if M heartbeat response messages are received, where M is less than or equal to N, determines which receivers return heartbeat response messages specifically by analyzing information carried in preset fields carried by the M heartbeat response messages, thereby determining which receivers currently maintain a coupling state.
It should be noted that the sender of the heartbeat detection request may be a CP or an UP.
In the technical scheme of the embodiment of the invention, a sender sends a heartbeat detection request to a receiver so that the receiver judges whether to return a heartbeat response message based on the heartbeat detection request; wherein, the heartbeat detection request carries information indicating the identity of the sender. Because the heartbeat detection request carries information indicating the identity of the sender, the receiver does not rely on judging the coupling state with the sender according to the address and the port of the sender any more, and can perform heartbeat detection with the opposite end under the condition that the address or the port of the local end is changed under the condition that the CP and the UP are separated, thereby being beneficial to successfully maintaining coupling with the opposite end through the heartbeat detection.
Fig. 2 is a schematic flowchart of another heartbeat detection processing method according to an embodiment of the present invention, which is applied to a receiver of a heartbeat detection request, and as shown in fig. 2, the method includes:
step 201: receiving a heartbeat detection request sent by a sender, wherein the heartbeat detection request carries information indicating the identity of the sender.
Step 202: judging whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat response message carries information indicating the identity of the receiver.
In some alternative embodiments, the identity of the sender of the message is indicated by adding a preset field.
For example, the preset field may be a Node identification (Node ID) field.
It should be noted that the messages in the message sender identity include, but are not limited to, heartbeat detection request and heartbeat response messages.
In some optional embodiments, the determining whether to return a heartbeat response message based on the heartbeat detection request includes:
determining a sender identifier based on information which is carried by the heartbeat detection request and indicates the identity of the sender;
verifying the coupling state corresponding to the sender identification;
if the verification result is that the coupling state is normal, judging to return a heartbeat response message; otherwise, judging not to return the heartbeat response message.
Further, the method further comprises:
step 203: and when the heartbeat response message needs to be returned, returning the heartbeat response message to the sender.
For example, the receiver 1 receives heartbeat detection requests sent by N senders, determines the identity of the sender by analyzing information carried by preset fields carried by the N heartbeat detection requests, further verifies the coupling state with the senders, thereby determining which senders currently maintain the coupling state with the senders, and sends a heartbeat response message to the senders maintaining the coupling state to inform that the senders and the receiver 1 currently maintain the coupling state.
It should be noted that the receiver of the heartbeat detection request may be a CP or an UP.
In the technical scheme of the embodiment of the invention, a receiver receives a heartbeat detection request sent by a sender, wherein the heartbeat detection request carries information indicating the identity of the sender; judging whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat response message carries information indicating the identity of the receiver. Because the heartbeat detection request carries information indicating the identity of the sender, the receiver does not rely on judging the coupling state with the sender according to the address and the port of the sender any more, and can perform heartbeat detection with the opposite end under the condition that the address or the port of the local end is changed under the condition that the CP and the UP are separated, thereby being beneficial to successfully maintaining coupling with the opposite end through the heartbeat detection.
Fig. 3 shows a schematic diagram of a heartbeat detection process, and as shown in fig. 3, a sender and a receiver should be corresponding to each other, that is: if the source address of the heartbeat detection request is IP1 and the source PORT is PORT1, then the destination address of the heartbeat response corresponding to the heartbeat detection request is IP1 and the destination PORT is PORT 1; if the source address of the heartbeat detection request is IP2 and the source PORT is PORT2, the destination address of the heartbeat response corresponding to the heartbeat detection request shall be IP2 and the destination PORT shall be PORT 2. The invention adds Node ID field for indicating sender identity in request and response message of heartbeat detection, Node ID can be IP address, or a character string, even can be understood as a section of binary code stream, as long as global uniqueness can be ensured. Thus, after receiving the heartbeat detection request, the receiver can not distinguish which Node sent the request through the source IP address and the port of the message, but knows who sent the request through the Node ID field carried in the message, and then verifies the coupling state corresponding to the Node ID, if the coupling is normal, the receiver replies the heartbeat response to the opposite side, the message also carries the Node ID of the receiver, and if the coupling does not exist, the receiver does not reply the heartbeat response. When the sender of the heartbeat detection request receives response, the coupling state is known to be normal; if the heartbeat response is not received, the coupling failure can be judged, and the coupling establishment can be reinitiated, so that the system can be quickly recovered.
Fig. 4 is a schematic diagram of interaction of heartbeat detection initiated by a CP in the embodiment of the present invention, and as shown in fig. 4, after a coupling between the CP and UP is established, an interaction flow includes:
step 401: a CP initiates a heartbeat detection request, wherein the heartbeat detection request carries a CP Node ID and is used for indicating the identity of a message sender;
the heartbeat detection request also carries source address information and source port information.
For example, if the source address of the message is CP IP1 and the source PORT is CP PORT1, the heartbeat detection request carries: CP Node ID, source address: CP IP1, source port: CP PORT 1.
Step 402: after receiving the request message, UP verifies the coupling state according to CP Node ID;
in the case that the UP determines that the coupling status is valid, step 403 is executed;
step 403: UP returns a heartbeat response message, and the heartbeat response message carries a UP Node ID and is used for indicating the identity of a message sender;
for example, the heartbeat response message carries: UP Node ID, destination address: CP IP1, destination port: CPPORT 1.
When the address or port of the CP local end changes (for example, the CP service address is configured and modified or the address and port are modified after the message passes through the NAT device), execute step 404;
step 404: a CP initiates a heartbeat detection request, wherein the heartbeat detection request carries a CP Node ID and is used for indicating the identity of a message sender;
that is, when the home address or port is changed, the heartbeat detection request message carries the CP Node ID without change.
For example, if the source address of the message is changed from CP IP1 to CP IP2, and the source PORT is changed from CP PORT1 to CP PORT2, then the heartbeat detection request carries: CP Node ID, source address: CP IP2, source port: CP PORT 2.
Step 405: after receiving the request message, UP verifies the coupling state according to CP Node ID;
in the case that UP determines that the coupling status is valid, go to step 406;
step 406: UP returns a heartbeat response message, and the heartbeat response message carries the UP Node ID and is used for indicating the identity of a message sender.
For example, the heartbeat response message carries: UP Node ID, destination address: CP IP2, destination port: CPPORT 2.
In the scheme, after the coupling between the CP and the UP is established, the CP initiates a heartbeat detection request, the CPnode ID carried in the message indicates the identity of a sender, and after the UP receives the request message, the coupling state is verified according to the CP Node ID, and the Node ID of the UP is carried in the heartbeat response; when the address or port of CP local end changes, the heartbeat detection request message will carry the unchanged CP Node ID, after UP receives the heartbeat request, the coupling is verified according to CP Node ID in the message, and the heartbeat response is replied.
Fig. 5 is a schematic diagram of interaction of heartbeat detection initiated by UP according to an embodiment of the present invention, and as shown in fig. 5, after a coupling between CP and UP is established, an interaction flow includes:
step 501: UP initiates a heartbeat detection request, wherein the heartbeat detection request carries a UP Node ID and is used for indicating the identity of a message sender;
the heartbeat detection request also carries source address information and source port information.
For example, if the source address of the message is UP IP1 and the source PORT is UP PORT1, the heartbeat detection request carries: UP Node ID, source address: UP IP1, source port: UP PORT 1.
Step 502: after receiving the request message, the CP verifies the coupling state according to the UP Node ID;
in case the CP determines that the coupling status is valid, step 503 is executed;
step 503: the CP returns a heartbeat response message, and the heartbeat response message carries a CP Node ID and is used for indicating the identity of a message sender;
for example, the heartbeat response message carries: CP Node ID, destination address: UP IP1, destination port: UPPORT 1.
When the address or port of the UP home terminal changes (for example, the UP service address is configured and modified or the address and port are modified after the message passes through the NAT device), execute step 504;
step 504: UP initiates a heartbeat detection request, wherein the heartbeat detection request carries a UP Node ID and is used for indicating the identity of a message sender;
that is, when the home address or port is changed, the heartbeat detection request message carries the unchanged UP Node ID.
For example, if the source address of the message is changed from UP IP1 to UP IP2, and the source PORT is changed from UP PORT1 to UP PORT2, then the heartbeat detection request carries: UP Node ID, source address: UP IP2, source port: UP PORT 2.
Step 505: after receiving the request message, the CP verifies the coupling state according to the UP Node ID;
in case the CP determines that the coupling status is valid, go to step 506;
step 506: and the CP returns a heartbeat response message, and the heartbeat response message carries the CP Node ID and is used for indicating the identity of the message sender.
For example, the heartbeat response message carries: CP Node ID, destination address: UP IP2, destination port: UPPORT 2.
In the scheme, after the coupling between the CP and the UP is established, the UP initiates a heartbeat detection request, the UPnode ID carried in the message indicates the identity of a sender, and after the CP receives the request message, the coupling state is verified according to the UP Node ID and the Node ID of the CP is carried in the heartbeat response; when the address or port of the UP local end changes, the heartbeat detection request message carries the unchanged UP Node ID, after the CP receives the heartbeat request, the coupling is verified according to the UP Node ID in the message, and the heartbeat response is replied.
Fig. 6 is a schematic structural diagram of a heartbeat detection processing apparatus according to an embodiment of the present invention, which is applied to a heartbeat detection request sender; as shown in fig. 6, the apparatus includes:
a first sending unit 61, configured to send a heartbeat detection request to a receiving party, so that the receiving party determines whether to return a heartbeat response message based on the heartbeat detection request; wherein, the heartbeat detection request carries information indicating the identity of the sender;
a first processing unit 62, configured to add, in the heartbeat detection request, information indicating an identity of the sender.
The heartbeat detection request also carries source address information and source port information.
For example, the preset field may be a Node identification (Node ID) field.
It should be noted that the messages in the message sender identity include, but are not limited to, heartbeat detection request and heartbeat response messages.
In this embodiment of the present invention, optionally, the apparatus further includes:
a first receiving unit 63, configured to receive a heartbeat response message returned by the receiving party; wherein, the heartbeat response message carries information indicating the identity of the receiver.
In this embodiment of the present invention, optionally, the first processing unit 62 is further configured to indicate an identity of a sender of the message by adding a preset field.
In this embodiment of the present invention, optionally, the first processing unit 62 is further configured to:
when the first receiving unit 63 receives the heartbeat response message returned by the receiving party, the receiving party that establishes or maintains a coupling state with the sending party is determined based on the heartbeat response message.
In practical applications, the first transmitting Unit 61, the first Processing Unit 62, and the first receiving Unit 63 may be implemented by a Central Processing Unit (CPU), a Microprocessor Unit (MPU), a Digital Signal Processor (DSP), a Field-Programmable Gate Array (FPGA), or the like, which are located in the heartbeat detection Processing device.
In a scenario where CP and UP are separated, the heartbeat detection processing apparatus of this embodiment can perform heartbeat detection with an opposite end under a condition that a local address or a port is changed, thereby facilitating successful heartbeat detection and maintaining coupling with the opposite end.
Fig. 7 is a schematic structural diagram of another heartbeat detection processing apparatus according to an embodiment of the present invention, which is applied to a receiver of a heartbeat detection request; as shown in fig. 7, the apparatus includes:
a second receiving unit 71, configured to receive a heartbeat detection request sent by a sender, where the heartbeat detection request carries information indicating an identity of the sender;
a second processing unit 72, configured to determine whether to return a heartbeat response message based on the heartbeat detection request; wherein, the heartbeat response message carries information indicating the identity of the receiver;
a second sending unit 73, configured to send the heartbeat response message to the sender.
The heartbeat detection request also carries source address information and source port information.
In this embodiment of the present invention, optionally, the second processing unit 72 is further configured to:
determining a sender identifier based on information which is carried by the heartbeat detection request and indicates the identity of the sender;
verifying the coupling state corresponding to the sender identification;
if the verification result is that the coupling state corresponding to the sender identification is normal, judging to return a heartbeat response message; otherwise, judging not to return the heartbeat response message.
In this embodiment of the present invention, optionally, the second processing unit 72 is further configured to:
the identity of the sender of the message is indicated by adding a preset.
For example, the preset field may be a Node identification (Node ID) field.
It should be noted that the messages in the message sender identity include, but are not limited to, heartbeat detection request and heartbeat response messages.
In practical applications, the second receiving Unit 71, the second Processing Unit 72, and the second transmitting Unit 73 may be implemented by a Central Processing Unit (CPU), a Microprocessor Unit (MPU), a Digital Signal Processor (DSP), a Field-Programmable Gate Array (FPGA), or the like, which are located in the heartbeat detection Processing device.
In a scenario where CP and UP are separated, the heartbeat detection processing apparatus of this embodiment can perform heartbeat detection with an opposite end under a condition that a local address or a port is changed, thereby facilitating successful heartbeat detection and maintaining coupling with the opposite end.
The present embodiment also provides a storage medium storing a computer program, which, after being executed by a processor, is capable of implementing any one or more of the foregoing heartbeat detection processing methods applied to a sender.
The computer storage medium may be of various types, and in this embodiment may preferably be a non-transitory storage medium.
It should be understood by those skilled in the art that the functions of the programs in the storage medium of the present embodiment can be understood by referring to the related description of the heartbeat detection processing method applied to the sender described in the embodiments.
The present embodiment also provides a storage medium storing a computer program, which, after being executed by a processor, is capable of implementing any one or more of the foregoing heartbeat detection processing methods applied to a receiving party.
The computer storage medium may be of various types, and in this embodiment may preferably be a non-transitory storage medium.
It should be understood by those skilled in the art that the functions of the programs in the storage medium of the present embodiment can be understood by referring to the related description of the heartbeat detection processing method applied to the receiving party described in the embodiments.
The technical schemes described in the embodiments of the present invention can be combined arbitrarily without conflict.
In the embodiments provided in the present invention, it should be understood that the disclosed method and intelligent device may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all the functional units in the embodiments of the present invention may be integrated into one second processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention.
Claims (10)
1. A heartbeat detection processing method applied to a sender is characterized by comprising the following steps:
sending a heartbeat detection request to a receiver so that the receiver judges whether a heartbeat response message is returned or not based on the heartbeat detection request;
wherein, the heartbeat detection request carries information indicating the identity of the sender.
2. The method of claim 1, further comprising:
receiving a heartbeat response message returned by the receiver; wherein, the heartbeat response message carries information indicating the identity of the receiver.
3. The method of claim 2, further comprising:
determining a receiver to establish or maintain a coupled state with the sender based on the heartbeat response message.
4. The method of claim 1, further comprising:
the identity of the sender of the message is indicated by adding a preset field.
5. A heartbeat detection processing method is applied to a receiving party, and is characterized by comprising the following steps:
receiving a heartbeat detection request sent by a sender, wherein the heartbeat detection request carries information indicating the identity of the sender;
judging whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat response message carries information indicating the identity of the receiver.
6. The method of claim 5, wherein the determining whether to return a heartbeat response message based on the heartbeat detection request comprises:
determining a sender identifier based on information which is carried by the heartbeat detection request and indicates the identity of the sender;
verifying the coupling state corresponding to the sender identification;
if the verification result is that the coupling state is normal, judging to return a heartbeat response message; otherwise, judging not to return the heartbeat response message.
7. The method of claim 5, further comprising:
the identity of the sender of the message is indicated by adding a preset field.
8. A heartbeat detection processing apparatus applied to a sender, the apparatus comprising:
the first sending unit is used for sending a heartbeat detection request to the receiver so that the receiver judges whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat detection request carries information indicating the identity of the sender;
and the first processing unit is used for adding information indicating the identity of the sender in the heartbeat detection request.
9. The apparatus of claim 8, further comprising:
a first receiving unit, configured to receive a heartbeat response message returned by the receiving party; wherein, the heartbeat response message carries information indicating the identity of the receiver.
10. A heartbeat detection processing device applied to a receiving party is characterized by comprising:
the second receiving unit is used for receiving a heartbeat detection request sent by a sender, wherein the heartbeat detection request carries information indicating the identity of the sender;
the second processing unit is used for judging whether a heartbeat response message is returned or not based on the heartbeat detection request; wherein, the heartbeat response message carries information indicating the identity of the receiver;
and the second sending unit is used for sending the heartbeat response message to the sender.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810824181.8A CN110768853A (en) | 2018-07-25 | 2018-07-25 | Heartbeat detection processing method and device |
PCT/CN2019/097754 WO2020020303A1 (en) | 2018-07-25 | 2019-07-25 | Processing method and device for heartbeat detection |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810824181.8A CN110768853A (en) | 2018-07-25 | 2018-07-25 | Heartbeat detection processing method and device |
Publications (1)
Publication Number | Publication Date |
---|---|
CN110768853A true CN110768853A (en) | 2020-02-07 |
Family
ID=69181352
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201810824181.8A Withdrawn CN110768853A (en) | 2018-07-25 | 2018-07-25 | Heartbeat detection processing method and device |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110768853A (en) |
WO (1) | WO2020020303A1 (en) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7617525B1 (en) * | 2005-06-21 | 2009-11-10 | Alto Ventures, Inc. | System and method for connectionless client-server communications |
CN107205208A (en) * | 2016-03-16 | 2017-09-26 | 华为技术有限公司 | Method, terminal and the server of authentication |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100486176C (en) * | 2006-04-27 | 2009-05-06 | 中兴通讯股份有限公司 | Method for managing user side equipment through network address translation gateway |
CN103298023A (en) * | 2012-02-23 | 2013-09-11 | 普天信息技术研究院有限公司 | Method and device for detecting terminal heartbeat |
CN104408945B (en) * | 2014-11-14 | 2016-06-08 | 南京蓝泰交通设施有限责任公司 | The roadway sign system of a kind of bus formula based on carrier communication and method of work thereof |
-
2018
- 2018-07-25 CN CN201810824181.8A patent/CN110768853A/en not_active Withdrawn
-
2019
- 2019-07-25 WO PCT/CN2019/097754 patent/WO2020020303A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7617525B1 (en) * | 2005-06-21 | 2009-11-10 | Alto Ventures, Inc. | System and method for connectionless client-server communications |
CN107205208A (en) * | 2016-03-16 | 2017-09-26 | 华为技术有限公司 | Method, terminal and the server of authentication |
Also Published As
Publication number | Publication date |
---|---|
WO2020020303A1 (en) | 2020-01-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109981316B (en) | Switching method of application server, session management network element and terminal equipment | |
EP3993347A1 (en) | Method and device for application migration | |
WO2021135448A1 (en) | Service invocation method, apparatus, device, and medium | |
CN110855792B (en) | Message pushing method, device, equipment and medium | |
US20050288045A1 (en) | Apparatus, and an associated method, for forming direct data connection between applications of a set of mobile stations | |
CN110611691A (en) | Message pushing method, system and storage medium | |
EP3200486B1 (en) | Connection establishment method, device, and system | |
CN108632307B (en) | Session connection establishing method and SMF entity | |
US20190166042A1 (en) | Method for data transmitting, centralized controller, forwarding plane device and communication apparatus | |
CN111917562B (en) | Broadcast message forwarding method, device, equipment and storage medium | |
CN104144098A (en) | Information pushing method and system and pushing server equipment | |
CN112152828B (en) | Game acceleration method and device, VPN terminal and storage medium | |
CN111263338A (en) | Network distribution method of Bluetooth Mesh network and related network distribution equipment and system | |
CN112152880A (en) | Link health detection method and device | |
WO2015172629A1 (en) | Message transmission method, apparatus and system | |
CN113196721A (en) | Discovery method and device of Internet of things equipment and terminal equipment | |
CN111404975A (en) | Message transmission method, device, equipment and computer storage medium | |
US8307104B2 (en) | Submit report handling in SMSIP | |
CN112543351A (en) | Network video data processing method and processing system | |
CN111416851A (en) | Method for session synchronization among multiple load balancers and load balancer | |
CN110768853A (en) | Heartbeat detection processing method and device | |
CN107454178B (en) | Data transmission method and device | |
CN107071038B (en) | Method and device for transmitting multimedia data | |
CN111565235A (en) | Method and device for obtaining address of multimedia message service server | |
CN114257634B (en) | Server discovery method, device and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
WW01 | Invention patent application withdrawn after publication | ||
WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200207 |