CN102612164B - A kind of restart for network element after discharge the methods, devices and systems of resource - Google Patents

Abstract

The invention belongs to the field of computer communication, and mainly relates to a method, device and system for releasing resources after network elements are restarted. A method for releasing resources after a network element is restarted includes that the second network node receives a capability exchange request from the first network node, where the capability exchange request carries a first original state identifier; and further compares the corresponding The second original state identifier of the first network node and the first original state identifier; if the comparison result is different, a session end request is sent to the third network node, and the session end request carries the first network node identifier and Reboot logo. The waste of network channels caused by the abnormal restart of the first network node is improved.

Description

A method, device and system for releasing resources after network element restart

technical field

The invention belongs to the field of computer communication, and mainly relates to a method, device and system for releasing resources after network elements are restarted.

Background technique

Diameter protocol includes basic protocol, network access service (NetAccessServer, NAS) protocol, extensible authentication (ExtensionsAuthenticationProtocol, EAP) protocol, mobile IP (MotoInternetProtocol, MIP) protocol, password message syntax (CodeMessagesyntax, CMS) protocol, etc. The Diameter protocol supports mobile IP, NAS requests, and mobile agent authentication, authorization, and accounting work. The implementation of the Diameter protocol is similar to the RADIUS protocol, and it also uses attribute value pairs (attribute value pairs, AVP), that is, in the form of Attribute-Length-Value triples. It is implemented, and specifies error handling, has failover mechanism, adopts TCP protocol, supports distributed accounting, and overcomes many shortcomings of RADIUS protocol. It is the most suitable authentication, authorization and accounting (AuthenticationAuthorizationAccounting, AAA) agreement.

In order to handle user access, the Diameter client performs a series of information exchanges with the Diameter server through the Diameter basic protocol and the Diameter application protocol, and such a series of information exchanges from initiation to termination is called a User session (UserSession).

The establishment of a user session is generally initiated by the Diameter client, which can be extended to the Diameter server through several Diameter agents, redirectors or protocol converters. The end of the user session is determined by the Diameter client, but the server can also issue an abort user session request (AbortSessionRequest, ASR) first, and if the client agrees to the abort request, it will respond to the abort user session response (AbortSessionAnswer, ASA), and then Then send a user session end request to notify the server to end the user session; otherwise, the user session is still maintained. In the absence of a request from the server, the client can also send a user session end request to the server by itself, for example, when the client itself is abnormal or the user access is abnormal.

When the Diameter proxy is set up between the Diameter client and the Diameter server for security and reliability reasons, since the client and the server are no longer directly visible, the abnormal restart of the client is only noticed by the Diameter proxy for the server. Only then can the Diameter server be notified, and the Diameter server can only be notified one by one through the session corresponding to the Diameter agent to end the session and release resources.

Contents of the invention

The invention solves the waste of the network channel caused by the Diameter server which can only notify the Diameter server to end the session and release resources one by one through the sessions corresponding to the Diameter proxy after the abnormal restart of the Diameter client under the environment of the Diameter proxy.

One aspect of the present invention provides a method for releasing resources after a network element is restarted, including that the second network node receives a capability exchange request from the first network node, and the capability exchange request carries a first original state identifier; further comparison The second original state identifier corresponding to the first network node stored by the second network node and the first original state identifier; if the comparison result is different, a session end request is sent to the third network node, and the session end request Carrying the first network node identifier and the restart identifier, so that the third network node can confirm the restart of the first network node according to the restart identifier, and further search for the connection with the first network node from the session mapping table stored by the third network node A related session ID is identified, and a session resource corresponding to the related session ID is released.

Another aspect of the present invention provides a method for releasing resources after a network element is restarted, including accepting a session end request from a second network node, the session end request carrying the first network node identifier and a restart identifier, further according to The restart identifier confirms that the first network node is restarted, and searches for a session identifier related to the first network node identifier from a stored session mapping table, and releases session resources corresponding to the related session identifier.

Another aspect of the present invention provides a method for releasing resources after a network element restarts, including the second network node receiving a capability exchange request from the first network node, the capability exchange request carrying a first original state identifier; further Comparing the second original state identifier corresponding to the first network node stored by the second network node with the first original state identifier; if the comparison result is different, look up from the session mapping table stored by the second network node Corresponding to the relevant session identification of the third network node identification and the first network node identification, and sending a session end request carrying the relevant session identification and restart identification to the third network node, so that the third network node can confirm the first network node according to the restart identification. A network node is restarted, and the session resource corresponding to the related session identifier is released.

Another aspect of the present invention provides a proxy device for releasing resources after a network element restarts, including a first receiver, configured to receive a capability exchange request from a first network node, and the capability exchange request carries the first The original state identifier; the first configurator is used to compare the second original state identifier corresponding to the first network node and the first original state identifier stored by itself, and if the comparison results are different, the generated The session end request of the node ID and the restart ID; the first sender is configured to send the session end request to the third network node, so that the third network node can confirm the restart of the first network node according to the restart ID, and further obtain from the The session mapping table is searched for a session ID related to the first network node ID, and the session resource corresponding to the related session ID is released.

Another aspect of the present invention provides a server for releasing resources after a network element is restarted, including a first receiver for receiving a session end request from a second network node, the session end request carrying the first network node ID and restart ID; a first processor, configured to confirm the restart of the first network node according to the restart ID, and search for a session ID related to the ID of the first network node from a stored session mapping table, and release the related session Identifies the corresponding session resource.

Another aspect of the present invention provides a proxy device for releasing resources after a network element restarts, including a second receiver, the application receives a capability exchange request from the first network node, and the capability exchange request carries the first primitive State identification; the second configurator is used to compare the second original state identification corresponding to the first network node stored by itself with the first original state identification, and if the comparison result is different, then the stored session mapping table Search for the relevant session identifier corresponding to the third network node identifier and the first network node identifier, and generate a session end request carrying the relevant session identifier and restart identifier; the second sender is configured to send the session identifier to the third network node Ending the request enables the third network node to confirm the restart of the first network node according to the restart identifier, and release the session resource corresponding to the relevant session identifier.

Description of drawings

FIG. 1 is a flowchart of a method for releasing resources after a network element is restarted according to the present invention;

FIG. 2 is a flow chart of a method for releasing resources after a network element is restarted according to the present invention;

FIG. 3 is a signaling flowchart of a method for releasing resources after a network element is restarted according to the present invention;

A general architecture diagram of a DiameterSIP application of the present invention in Fig. 4;

FIG. 5 is a signaling flow diagram of a method for releasing resources after a network element is restarted according to the present invention;

FIG. 6 is a structural diagram of an agent for releasing resources after a network element is restarted according to the present invention;

FIG. 7 is a structural diagram of a server for releasing resources after a network element is restarted according to the present invention;

FIG. 8 is a structural diagram of an agent for releasing resources after a network element is restarted according to the present invention;

The following description and accompanying drawings set forth in detail several exemplary embodiments of the invention. These embodiments are only examples, and the present invention can also be implemented in other different ways.

specific implementation plan

An embodiment of a method for releasing resources after a network element is restarted provided by the present invention includes:

S1001. The second network node receives a capability exchange request from the first network node.

The capability exchange request carries a first original state identifier; wherein the first network node and the third network may be network nodes that support the Diameter protocol and exist in each communication architecture, such as GGSN and CBP in the VoIP network architecture; such as the IMS architecture In P-CSCF and CCF or S-CSCF and MRFC etc. Wherein the second network node specifically refers to the proxy node between the first network node and the second network node, and the purpose of the arrangement of the proxy node is generally to shield the (DiameterCreditControl, DCC) DCC client from the number of DCC servers, or for security, In consideration of reliability, avoid direct connection between the DCC client and the DCC server.

In addition to receiving the capability exchange request from the first network node, the second network node may also receive the session request from the first network node, and forward the session carrying the first network node identifier and the session identifier to the third network node The request enables the third network node to add the session identifier to a session mapping table corresponding to the first network node identifier, and the session mapping table is stored in the third network node.

The session request includes credit control request CCR, session interruption request (AbortSessionRequest, ASR), connection termination request (DisconnectPeerRequest, DPR), session termination request (SessionTerminationRequest, STR) etc. in addition to the capability exchange request.

S1002. Compare the second original state identifier corresponding to the first network node and the first original state identifier stored by the second network node.

The second original state identifier is the AVP parameter Origin-State-Id in the Diameter protocol, and its value is only changed when the first network node restarts and is abnormally restarted, such as the first network node due to power failure, system crash, etc., Furthermore, the session between network nodes cannot be terminated normally through the STR message. After restarting, when the first network node initiates a capability exchange request CER again, it will carry a new Origin-State-Id. The change process of Origin-State-Id is single-increasing. The Origin-State-Id value carried in the capability exchange request CER or session request before the abnormal restart is large.

S1003. Send a session end request to the third network node if the comparison result is different.

The session end request carries the identifier of the first network node and the restart identifier, so that the third network node can confirm the restart of the first network node according to the restart identifier, and further search for a connection with the first network node from the stored session mapping table. The node identifies a related session ID, and releases the session resource corresponding to the related session ID.

The session ID related to the first network node ID may be one or more session IDs, specifically determined by the number of sessions established between the first network node and the third network node through the proxy node before the abnormal restart.

If the session resource corresponding to the session identifier is successfully released, the corresponding session identifier is deleted from the session mapping table. When the third network node receives a session end request that does not carry a restart identifier, and the session end request carries the session identifier to be ended, after the session resource corresponding to the session identifier is successfully released, the session mapping table Delete the corresponding session ID.

In the prior art, the session end request STR is also used to end the session between network nodes, but since a proxy node is used between the first network node and the third network node, the STR carries the identifier of the second network node at this time, And there is a session identifier corresponding to the end, and a session process usually includes multiple session identifiers, so the existing technology needs to send multiple STRs to end the session that the abnormal first network node failed to end in time due to abnormal restart .

The present invention saves the mapping relationship between the session identifier between the second network node and the third network node and the first network node identifier through the session mapping table. The session ID generated by the node. Further, the first network node identifier and the restart identifier are carried in the STR, so that the third network node can end the related session corresponding to the first network node in the session mapping table through one STR message.

An embodiment of a method for releasing resources after a network element is restarted provided by the present invention includes:

S2001. Receive a capability exchange request from a first network node.

The capability exchange request carries a first original state identifier.

In addition to receiving the capability exchange request from the first network node, the second network node may also receive a session request from the first network node, and forward the session request carrying the session identifier to the third network node; further, the second network node Adding the session identifier to a session mapping table corresponding to the third network node identifier and the first network node identifier, and the session mapping table is stored in the second network node.

S2002. Compare the second original state identifier corresponding to the first network node stored by itself with the first original state identifier.

The second original state identifier is the AVP parameter Origin-State-Id in the Diameter protocol, and its value is only changed when the first network node restarts and is abnormally restarted, such as the first network node due to power failure, system crash, etc., Furthermore, the session between network nodes cannot be terminated normally through the STR message. After restarting, when the first network node initiates a capability exchange request CER again, it will carry a new Origin-State-Id. The change process of Origin-State-Id is single-increasing. The Origin-State-Id value carried in the capability exchange request CER or session request before the abnormal restart is large.

S2003, if the comparison results are different, search the session mapping table stored by the second network node for the relevant session identification corresponding to the third network node identification and the first network node identification, and send the related session identification to the third network node and a session end request identified by a restart.

The third network node is enabled to confirm the restart of the first network node according to the restart identifier, and release the session resource corresponding to the relevant session identifier.

An AVP parameter is preferably generated, and the relevant session identifier is used as the data content of the AVP parameter, and the AVP parameter and the restart identifier are carried in the session end request, and after the third network node confirms that the first network node is restarted , further extracting data content from the AVP parameter, that is, the related session ID, and releasing session resources according to the related session ID.

In the following description, for purposes of illustration rather than limitation, specific details such as specific system architectures, interfaces, and techniques are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the invention may be practiced in other embodiments without these specific details. In other instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

The present invention provides an embodiment of a method for releasing resources after a network element is restarted. Its signaling transmission is shown in FIG. GatewayGPRSSupportNode, GGSN), the second network node is the Diameter proxy, specifically Diameter credit control proxy (DiameterCreditControlproxy, DCCproxy), the third network node is the Diameter server, specifically the Convergence Billing Point (CBP), the session request The message is specifically expressed as a credit control request (CreditControlRequest, CCR)/credit control answer (CreditControlAnswer, CCA) in the Diameter message, and further involves a capability exchange request (CapabilitiesExchangeRequest, CER)/capabilitiesExchangeAnswer (CapabilitiesExchangeAnswer, CEA); GGSN, DCCproxy , CBP are all Diameter entities, the specific implementation process is as follows:

S301. The gateway GPRS support node GGSN sends a Diameter message to the information management agent DDCproxy. The Diameter message is specifically a capability exchange request CER message. The CER is mainly used for requesting message exchange between Diameter entities to exchange local capabilities, and carries the original AVP parameter State identifier Origin-State-Id, the original state identifier is carried in each Diameter message during a stable operation, and remains unchanged; in this embodiment, when the GGSN is restarted as a Diameter client due to an abnormal situation, the subsequent GGSN sends The Origin-State-Id value carried in the Diameter message will increase compared to before the restart. The specific Origin-State-Id value can be the time at the restart time or a single-increment variable for non-volatile storage records. Here, you may wish to use the non-volatile The single-increment variable of the volatile storage record, and set its current value to 5.

S302. After DCCproxy receives the CER message sent by the GGSN, it further searches its own storage area for the corresponding Origin-State-Id value identical to the original host name Origin-Host identifier carried in the CER message, specifically:

When the storage area does not find the Origin-Host identifier, store the data content GGSN of the AVP parameter Origin-Host in the CER message corresponding to the data content 5 of the AVP parameter Origin-State-Id;

When the storage area finds that the corresponding Origin-State-Ids are the same, a Capability Interaction Answer CEA message is returned to the GGSN.

S303. The GGSN sends a Diameter message to the DCCproxy. The Diameter message is specifically a credit control request CCR message, and the message includes user authentication, charging, authorization and other information.

S304. When DCCproxy forwards the CCR message to the converged charging access point CBP, it expands and adds a custom AVP parameter HW_OriginHostName in the CCR message. The format of the extended CCR complete message is as follows, and in actual situations, it may be some of the AVPs Combination of parameters:

DCCproxy assigns the Origin-Host data content carried by the CCR received in S303, that is, the GGSN identifier to HW_OriginHostName, and forwards the credit control request CCR message carrying the HW_OriginHostName identifier. The CCR message forwarded by DCCproxy to the CBP mainly includes:

Session-Id=Session1

Origin-Host=DCC1

Origin-State-Id=3

HW_OriginHostName=GGSN

Here, Origin-State-Id=3 is an original state identifier of DCCproxy, and the change of its value can reflect data loss and abnormal restart of DCCproxy.

S305, CBP receives the credit control request CCR message, obtains the AVP parameters in the CCR message including: the session identifier Session-Id and the original host name identifier HW_OriginHostName, and adds the session identifier Session1 to the Diameter client GGSN corresponding to HW_OriginHostName and Session-Id Conference mapping table, the conference mapping table is stored in the CBP, and its format is optional as follows:

S306-S307. The CBP sends a credit control response CCA message to the DCCproxy, which includes the request content carried in the CCR message, and the AVP parameter Destination-Host and the current session parameter Session-Id pointing to the DCCproxy.

S308, carry out the same business interaction between S301-S307, further the session request sent by it can be different, and the specific processing process can also be changed corresponding to the session request; the subsequent CBP receives a Diameter message, such as the above-mentioned CCR message, CER message, etc., The CBP will carry the content according to the AVP parameter HW_OriginHostName. For example, the above-mentioned GGSN searches for the corresponding session mapping table and updates the session mapping table; the specific update operation includes adding a session ID, deleting a session ID, etc.

S309-S310, when the GGSN restarts due to an abnormality, and fails to send a session termination request STR before disconnecting from DCCproxy, re-establish a connection with DCCproxy after restarting, and send a CER message for capability negotiation, the message contains necessary parameters :

Origin-Host=GGSN

Origin-State-Id=6

The Origin-State-Id value is incremented from 5 to 6 after the GGSN restarts, and the CER message carries the AVP parameters Origin-Host and Origin-State-Id together, indicating that it is the Diameter entity GGSN that completes the restart operation.

S311, DCCproxy receives the CER message of the GGSN, compares the Origin-State-Id value of the corresponding GGSN stored by itself with the Origin-State-Id value carried in the received CER, confirms that the GGSN restarts due to an abnormality, and then sends a STR to the CBP message, the key AVP parameters carried in it are as follows:

Termination-Cause=CLIENT_REBOOT

HW_OriginHostName=GGSN

The main parameters in the message also include:

Session-Id=0

Termination-Cause=CLIENT_REBOOT

HW_OriginHostName=GGSN

Wherein, Session-Id=0 means any session, Termination-Cause=CLIENT_REBOOT means that the sending reason is client restart, and the restart identifier CLIENT_REBOOT is a custom identifier, and there is an analysis and operation implementation corresponding to the CLIENT_REBOOT identifier on the CBP side.

S312, after the CBP receives the STR message, it judges that if the content of the AVP parameter Termination-Cause identifier is the restart identifier CLIENT_REBOOT, then query the corresponding session mapping table according to the data content in the original host name identifier HW_OriginHostName GGSN, and obtain all the session identifiers Session corresponding to the GGSN -Id;

The specific session mapping table can be in the format shown in the following table. If there is the following data in the Diameter client GGSN and session ID correspondence table, CBP will release the session resources corresponding to the Session1, Session6, and Session9 session IDs; further delete the session mapping table Corresponding to the information related to the session identifier; the actual session mapping table can also use HW_OriginHostName as a distinguishing group to save the Session-Id, and the specific implementation is not limited to this;

S313. After releasing the resources, the CBP replies to the DCCproxy with a session termination response STA message, which carries a successfully terminated session identifier or error information during the process of terminating the session;

S314. The DCCproxy returns a Capability Interactive Answer CEA message to the GGSN according to the success information carried in the received STA.

The order of steps S311 and S314 in the above embodiment is the preferred solution of the present invention, which is beneficial to reduce the resource processing pressure on the server side. Optionally, steps S311 and S314 can also be performed synchronously, and the GGSN can be improved on the basis of increasing the server-side processing process. The processing speed of requesting CER message with DCCproxy capability exchange after restart.

In this embodiment, the AVP parameter HW_OriginHostName and the restart identifier CLIENT_REBOOT indicating the initiator are added in the Diameter message forwarded by DCCproxy; the maintenance of the session mapping table is added to the corresponding HW_OriginHostName of the server, and the corresponding CLIENT_REBOOT is further implemented according to the session mapping table. A session termination request CER message completes the release function of the corresponding session resources in the CBP after the abnormal restart of the GGSN, which improves the network transmission efficiency.

The general system of DiameterSIP application is shown in Figure 4. Specifically, Diameter client A may be the interrogating call session control function (Interrogating Call Session Control Function, I-CSCF) in IMS, and Diameter client B may be specifically the serving call session control function in IMS. Function (ServeCallSessionControlFunction, S-CSCF), the Diameter server may specifically be a home subscriber server (HomeSubscriberServer, HSS) in the IMS, where the proxy unit A and the proxy unit B are optional in this system.

An embodiment provided by the present invention, as shown in Figure 5, is the A side in the general system of the DiameterSIP application, and is a Diameter signaling interaction diagram for charging, where the Diameter client A is the first network node. It is a proxy call session control function (ProxyCallSessionControlFunction, P-CSCF) unit, and the Diameter server, that is, the third network node is specifically a charge accumulation function (ChargingAccumulatedFunction, CCF) unit, and in the case of having a proxy unit proxy, that is, the second network node, the Charge Request (Accounting-Request, ACR) message and Accounting-Answer (Accounting-Answer, ACA) message and STR/STA are used as the Diameter message of transmission; In this embodiment, taking Accounting Request as an example, the authentication before accounting is not and the authorization process are fully described, but it does not affect the statement of the invention in this embodiment. Those skilled in the art can improve the entire charging signaling process by virtue of the SIPDiameter protocol. The specific implementation process is as follows:

S501. The P-CSCF sends a Diameter message to the proxy unit proxy. The Diameter message is an charging request ACR message. When the P-CSCF is in a normal state, the original state identifier Origin-State-Id value in the ACR message remains unchanged. Here you may wish to use the time parameter method, and set the initial value to 20111128T152000Z; a complete ACR message is as follows:

S502, the proxy unit proxy recognizes that the Diameter message is an ACR message, then generates an ACR message forwarded to the CCF, uses its own identity proxy as the value of the AVP parameter Origin-Host in the forwarded ACR message, and generates a communication between the proxy unit and the CCF The session identifier Session2 is used as the value of the AVP parameter Session-Id in the forwarded ACR message. Session2 corresponds to the Diameter client P-CSCF and the Diameter server CCF and saves it in the session mapping table in the proxy proxy to establish Session2 and the Diameter client P-CSCF. The mapping relationship between CSCF and Diameter server CCF, the specific conference mapping table format is as follows:

S503. The proxy unit proxy forwards the generated ACR message to the CCF;

S504, the charging accumulation function entity CCF receives the charging request ACR message from the proxy, and processes the request content in the charging request message, and then returns the charging response ACA message to the proxy

S505. The proxy unit proxy forwards the accounting response ACA message to the P-CSCF;

S506, the process may include the processing flow of the above steps S501-S505, and store the Diameter client ID and Diameter server ID corresponding to the session ID in the session mapping table, wherein the session ID is generated by the proxy unit and carried in the forwarded to CCF In the Diameter message;

S507-508, P-CSCF did not end the charging normally due to some unexpected reasons, such as: no STR message was sent to end the session; after restarting the P-CSCF, the conference capability request CER sent will be The value of the AVP parameter Origin-State-Id will become the current time, which may be set to 20111128T152530Z;

S509, the proxy proxy exchanges the Origin-Host in the request CER according to the receiving capability, compares the received and stored Origin-State-Id data content for the same Origin-Host identifier, and receives the Origin-State-Id data When the content value is larger, it is analyzed that the P-CSCF restarts due to an abnormal reason, and then sends a session termination request STR to the CCF, which carries the AVP parameter:

Termination-Cause=CLIENT_REBOOT

HW_OriginHostName=P-CSCF

Terminat_Session = Terminat_Session1

Termination-Cause=CLIENT_REBOOT indicates that the reason for sending is client restart, and the restart identifier CLIENT_REBOOT is a custom identifier, which has the parsing and operation implementation of the corresponding identifier in CCF; when the session is terminated, the data content corresponding to the Terminat_Session contains the original host name identifier and the corresponding In the session mapping table, the original host name identifier HW_OriginHostName of the AVP parameter in the session termination request STR is optional. A complete STR message is as follows:

Wherein Terminat_Session is the AVP parameter that the present invention adds, and its format meets the AVP structure of standard as follows:

The data content is the session mapping table generated for both the Origin-State-Id 20111128T152000Z, and the Origin-Host is P-CSCF; the data content is optional and only needs to include the session ID in the session mapping table. At this time, HW_OriginHostName Logo is preferred;

S510. After the CCF recognizes the ACR as an accounting request message according to the command code of the Diameter message being 271, it learns from the data content CLIENT_REBOOT of the Termination-Cause that the P-CSCF needs to give up the session resources before the restart due to an abnormal restart, so it starts the new processing Function, according to the session identification Session-Id corresponding to the Terminat_Session data content in the ACR message or the session mapping table of the P-CSCF, release the resources corresponding to the session identification;

S511. The CCF sends a session end response STA message to the proxy unit proxy, which carries a successfully terminated session identifier Session-Id or error information during the process of terminating the session;

S512. The proxy unit proxy deletes the relevant information corresponding to the session identifier in the session mapping table, and sends a conference capability response CEA to the P-CSCF.

In this embodiment, by maintaining the session mapping table between the Diameter client ID, the session ID forwarded by the Diameter agent to the Diameter service, and the Diameter server; the session ID is generated by the Diameter agent, and the Diameter server and the Diameter client For Diameter, all direct interaction nodes are visible, which can provide more efficient processing for maintaining the session mapping table, and increase the processing complexity of the Diameter agent on the basis of reducing the processing complexity of the Diameter server.

The present invention provides a proxy device 600 for releasing resources after a network element is restarted, including:

The first receiver 601 receives a capability exchange request from a first network node, where the capability exchange request carries a first original state identifier;

The first configurator 602 is configured to compare the second original state identifier corresponding to the first network node stored by itself with the first original state identifier, and if the comparison results are different, generate A session end request identified by restart;

The first sender 603 is configured to send the session end request to the third network node, so that the third network node can confirm the restart of the first network node according to the restart identifier, and further search for a connection with the first network node from the session mapping table. The node identifies a related session ID, and releases the session resource corresponding to the related session ID.

The agent device 600 further includes:

The first receiver 601 is further configured to receive a session request from a first network node;

The first configurator 602 is further configured to generate a session request carrying a first network node identifier and a session identifier;

The first sender 603 is further configured to forward the session request carrying the first network node identifier and the session identifier to a third network node, so that the third network node can add the A session identifier to a session mapping table, and the session mapping table is stored in the third network node.

The present invention provides a server 700 for releasing resources after network elements are restarted, including:

The first receiver 701 is configured to receive a session end request from a second network node, where the session end request carries a first network node identifier and a restart identifier;

The first processor 702 is configured to confirm the restart of the first network node according to the restart identifier, and search for a session identifier related to the first network node identifier from the stored session mapping table, and release the session corresponding to the related session identifier resource.

The server 700 further includes:

The first receiver 701 is further configured to receive a session request from the second network node, where the session request carries the first network node identifier and the session identifier;

The first processor 702 is further configured to add the session identifier to a session mapping table corresponding to the first network node identifier, where the session mapping table is stored in the third network node.

The present invention provides a device 800 for releasing resources after a network element is restarted, including:

The second receiver 801, the application receives a capability exchange request from the first network node, where the capability exchange request carries a first original state identifier;

The second configurator 802 is configured to compare the second original state identifier corresponding to the first network node stored by itself with the first original state identifier, and if the result of the comparison is different, search the corresponding session mapping table from the stored session mapping table. The third network node identifier and the related session identifier of the first network node identifier, generating a session end request carrying the related session identifier and the restart identifier;

The second sender 803 is configured to send the session end request to the third network node, so that the third network node can confirm the restart of the first network node according to the restart identifier, and release the session resource corresponding to the relevant session identifier.

The device 800 further includes:

The second receiver 801 is further configured to receive a session request from the first network node;

The second configurator 802 is further configured to add the session identifier to a session mapping table corresponding to the third network node identifier and the first network node identifier, and the session mapping table is stored in the second network node.

Through the above description of the implementation manners, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or by means of software plus a necessary general-purpose hardware platform. Based on this understanding, the technical solution of the present invention can be embodied in the form of software products, which can be stored in a non-volatile storage medium (which can be CD-ROM, U disk, mobile hard disk, etc.), including several The instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute the methods described in various embodiments of the present invention.

Those skilled in the art can understand that the drawing is only a schematic diagram of a preferred embodiment, and the modules or processes in the drawing are not necessarily necessary for implementing the present invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be distributed in the device in the embodiment according to the description in the embodiment, or can be located in one or more devices different from the embodiment according to corresponding changes. The modules in the above embodiments can be combined into one module, and can also be further divided into multiple sub-modules.

To sum up, the above are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (16)

1. one kind restart for network element after discharge the method for resource, it is characterised in that including:

The capabilities exchange that second network node receives from first network node is asked, and the request of described capabilities exchange carries the first initial condition mark；Compare the second initial condition mark of the correspondence described first network node of the second network node storage and described first initial condition mark further；

Different then generation of described result of the comparison carries first network node identification and restarts the conversation end request of mark, the request of described conversation end is sent to the 3rd network node, make the 3rd network node can restart identity validation first network node restart according to described, and from the session mapping table of the 3rd network node storage, find the session identification relevant to described first network node identification further, discharge the Session Resources that described associated session mark is corresponding, wherein said restart be designated user-defined identification, the parsing and the operation that have corresponding identifier in described 3rd network node realize.

2. the method for claim 1, it is characterised in that described method further comprises:

Receive the conversation request from first network node, and the conversation request of first network node identification and session identification is carried to the 3rd target node so that the 3rd network node can add described session identification to session mapping table by corresponding described first network node identification.

3. method as claimed in claim 2, it is characterised in that described first network node is Gateway GPRS Support Node, and described conversation request is credit control request, and described 3rd network node is convergent billing access point, and described method specifically includes:

Receive the credit control request from Gateway GPRS Support Node, the credit control request carrying Gateway GPRS Support Node mark and session identification is forwarded to convergent billing access point, making convergent billing access point corresponding described Gateway GPRS Support Node mark can add described session identification to session mapping table, described session mapping table is stored in convergent billing access point.

4. the method as described in claim 1,2 or 3, it is characterized in that, described first network node is Gateway GPRS Support Node, and described second network node is Diameter diameter credit control agency, described 3rd network node is convergent billing access point, and described method specifically includes:

The capabilities exchange that Diameter diameter credit control agency receives from Gateway GPRS Support Node is asked, and compares the second initial condition mark of the described Gateway GPRS Support Node of correspondence of Diameter diameter credit control agency's storage and described first initial condition mark further；

Described result of the comparison difference then sends conversation end request to convergent billing access point, the request of described conversation end carries Gateway GPRS Support Node mark and restarts mark, make convergent billing access point can judge that Gateway GPRS Support Node is because of abnormal restarting according to restarting mark, and from described session mapping table, search the session identification relevant to Gateway GPRS Support Node mark further, discharge the Session Resources that described associated session mark is corresponding.

5. one kind restart for network element after discharge the method for resource, it is characterised in that including:

3rd network node accepts to ask from the conversation end of the second network node, the request of described conversation end carries first network node identification and restarts mark, restart identity validation first network node described in basis further to restart, and find and described first network node identification associated session mark from the session mapping table of storage, discharge the Session Resources that described associated session mark is corresponding, wherein said restart be designated user-defined identification, described 3rd network node have corresponding identifier parsing and operation realize.

6. method as claimed in claim 5, it is characterised in that described method further comprises:

Receive the conversation request from the second network node, described conversation request carries first network node identification and session identification, then corresponding described first network node identification adds described session identification to session mapping table, and described session mapping table is stored in the 3rd network node.

7. method as claimed in claim 6, it is characterised in that first network node is Gateway GPRS Support Node, and conversation request is credit control request, and the 3rd network node is convergent billing access point, and described method specifically includes:

Convergent billing access point receives the credit control request from diameter credit control agency, described credit control request carries Gateway GPRS Support Node mark and session identification, then corresponding described Gateway GPRS Support Node mark adds described session identification to session mapping table, and described session mapping table is stored in convergent billing access point.

8. method as described in claim 5,6 or 7, it is characterised in that first network node is Gateway GPRS Support Node, the second network node is Diameter diameter credit control agency, and the 3rd network node is that method described in convergent billing access point specifically includes:

Convergent billing access point receives the conversation end request from diameter credit control agency, the request of described conversation end carries Gateway GPRS Support Node mark and restarts mark, restart mark further described in basis and judge that Gateway GPRS Support Node is restarted, and search and described Gateway GPRS Support Node mark associated session mark from the session mapping table of storage, discharge the Session Resources that described associated session mark is corresponding.

9. one kind restart for network element after discharge the method for resource, it is characterised in that including:

The capabilities exchange that second network node receives from first network node is asked, and the request of described capabilities exchange carries the first initial condition mark；Compare the second initial condition mark of the correspondence described first network node of the second network node storage and described first initial condition mark further；

Described result of the comparison is different then to be found the associated session of corresponding 3rd network node mark and first network node identification from the session mapping table of described second network node storage and identifies, and carry, to the 3rd network node transmission, the conversation end request that described associated session identifies and restarts mark, 3rd network node can be restarted according to restarting identity validation first network node, discharge the Session Resources that described associated session mark is corresponding, wherein said restart be designated user-defined identification, the parsing and the operation that have corresponding identifier in described 3rd network node realize.

10. method as claimed in claim 9, it is characterised in that described method also includes:

Receive the conversation request from first network node, carry the conversation request of session identification to the 3rd target node；The corresponding 3rd network node mark of further second network node and first network node identification add described session identification to session mapping table, and described session mapping table is stored in the second network node.

11. one kind restart for network element after discharge the agent apparatus of resource, it is characterised in that including:

First receptor, asks for the capabilities exchange received from first network node, carries the first initial condition mark in the request of described capabilities exchange；

First distributor, for comparing the second initial condition mark of the correspondence described first network node of self storage and described first initial condition mark, different then generation of described result of the comparison carries first network node identification and restarts the conversation end request of mark；

First transmitter, for sending the request of described conversation end to the 3rd network node, 3rd network node can be restarted according to restarting identity validation first network node, and from described session mapping table, find the session identification relevant to first network node identification further, discharge the Session Resources that described associated session mark is corresponding, wherein said restart be designated user-defined identification, have in described 3rd network node corresponding identifier parsing and operation realize.

12. device as claimed in claim 11, it is characterised in that also include:

Described first receptor, is additionally operable to receive the conversation request from first network node；

Described first distributor, is additionally operable to generate the conversation request carrying first network node identification and session identification；

Described first transmitter, it is additionally operable to the conversation request carrying first network node identification and session identification described in the 3rd target node, making the 3rd network node can add described session identification to session mapping table by corresponding described first network node identification, described session mapping table is stored in the 3rd network node.

13. one kind restart for network element after discharge the server of resource, it is characterised in that including:

First receptor, asks for the conversation end received from the second network node, and the request of described conversation end carries first network node identification and restarts mark；

First processor, described in basis, restart identity validation first network node restart, and find and described first network node identification associated session mark from the session mapping table of storage, discharge the Session Resources that described associated session mark is corresponding, wherein said restart be designated user-defined identification, have in described server corresponding identifier parsing and operation realize.

14. server as claimed in claim 13, it is characterised in that also include:

Described first receptor, is additionally operable to receive the conversation request from the second network node, and described conversation request carries first network node identification and session identification；

Described first processor, is additionally operable to corresponding described first network node identification and adds described session identification to session mapping table, and described session mapping table is stored in the 3rd network node.

15. one kind restart for network element after discharge the agent apparatus of resource, it is characterised in that including:

Second receptor, asks for the capabilities exchange received from first network node, carries the first initial condition mark in the request of described capabilities exchange；

Second distributor, for comparing the second initial condition mark of the correspondence described first network node of self storage and described first initial condition mark, the described result of the comparison different associated session then finding corresponding 3rd network node mark and first network node identification from the session mapping table of storage identify, generates and carries described associated session and identify and restart the conversation end of mark and ask；

Second transmitter, for sending the request of described conversation end to the 3rd network node, 3rd network node can be restarted according to restarting identity validation first network node, discharge the Session Resources that described associated session mark is corresponding, wherein said restart be designated user-defined identification, have in described 3rd network node corresponding identifier parsing and operation realize.

16. device as claimed in claim 15, it is characterised in that including:

Described second receptor, is additionally operable to receive the conversation request from first network node；

Described second distributor, is additionally operable to corresponding 3rd network node mark and first network node identification adds described session identification to session mapping table, and described session mapping table is stored in the second network node.