Keeping alive method between peer node and client under peer node-client architecture
A peer-to-peer node and client technology, applied in the network field, can solve problems such as heavy burden on peer nodes, discrete topology keep-alive and session connection keep-alive, and bloated total number of keep-alive signaling, so as to reduce burden and reduce keep-alive The effect of the number of signaling
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0050] Such as Image 6 As shown, the client carries all existing session connection identifiers (Session ID, abbreviated as Ses ID, such as Ses1 and Ses2) in its own session table in the keep-alive signaling sent periodically (period Tc);
[0051] The peer node periodically receives the keep-alive signaling, and at the same time, matches and checks all the session connection identifiers immediately carried in the keep-alive signaling and all the session connection identifiers saved in the local session table of the peer node, so as to judge the local Check whether the session connection hangs up abnormally. If the peer node does not receive the keep-alive signaling from the client within a given time (Tp, Tp>Tc, the peer node’s maximum tolerance time for keeping the client alive), then it is determined that the client The client is abnormal (all session connections of this client are abnormal).
[0052] For example, if Image 6 Shown:
[0053] 1) At time t0,
[0054] The...
Embodiment 2
[0063] Such as Figure 7 As shown, in addition to carrying its own client identification (Client ID) in the Keepalive signaling sent by the client (Client) periodically (period Tc), it also carries all existing session connections in its own session table Identification (Session ID, abbreviated as Ses ID, such as Ses1, Ses2);
[0064] In addition to judging whether the client is alive by periodically receiving keep-alive signaling, the peer node (Peer) also uses all session connection identifiers carried in the keep-alive signaling and all session connections stored in the local session table of the peer node. The connection identifiers are checked one by one to determine whether there is a local session connection that hangs abnormally. If the peer node does not receive the keep-alive signaling from the client within a given time (Tp, Tp>Tc, the peer node’s maximum tolerance time for keeping the client alive), then it is determined that the client The terminal is abnormal (...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 