WO2013107402A1

WO2013107402A1 - Method, device and system for releasing resource after network element restarts

Info

Publication number: WO2013107402A1
Application number: PCT/CN2013/070752
Authority: WO
Inventors: 陆敬石; 杨斌
Original assignee: 华为技术有限公司
Priority date: 2012-01-21
Filing date: 2013-01-21
Publication date: 2013-07-25
Also published as: CN102612164B; CN102612164A

Abstract

The present invention belongs to the field of computer communication and mainly relates to a method, device and system for releasing resource after a network element restarts. The method comprises: a second network node receives an ability exchange request from a first network node and the ability exchange request carries a first original state identifier; a second original state identifier, which is corresponding to the first network node and stored in the second network node, is compared with the first original state identifier; if the identifiers are different, a session ending request is transmitted to a third network node and the session ending request carries the first network node identifier and a restart identifier. Therefore, the waste in network passages caused by abnormal restart of the first network node is reduced.

Description

Method, device and system for releasing resources after restarting a network element The present application claims to be submitted to the Chinese Patent Office on January 21, 2012, and the application number is 201210020513.X. The invention name is "A kind of resource is released after the network element is restarted. The priority of the Chinese Patent Application, the entire disclosure of which is incorporated herein by reference. Technical field

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

Background technique

The Diameter protocol includes a basic protocol, a Net Access Server (NAS) protocol, an Extensions Authentication Protocol (EAP) protocol, a Moto Internet Protocol (MIP) protocol, and a Code Message syntax. CMS) agreement, etc. The Diameter protocol supports the authentication, authorization, and accounting of mobile IP, NAS requests, and mobile agents. The implementation of the Diameter protocol is similar to the RADIUS protocol. It is also the attribute value pair (AVP), which is Attribute-Length-Value. It is implemented in the form of tuples, and specifies the error handling, possesses the failover mechanism, uses the TCP protocol, supports distributed charging, and overcomes many shortcomings of the RADIUS protocol. It is the most suitable for future authentication, authorization, and accounting of mobile communication systems. Authentication Authorization Accounting (AAA) protocol.

In order to handle the user's access, the Diameter client performs a series of information exchange with the Diameter server through the Diameter base protocol and the Diameter application protocol, and such a series of information interaction from initiation to suspension is called a Diameter protocol. User Session.

The establishment of a user session is generally initiated by the Diameter client, which can be extended to the Diameter server by means of 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 Session Request (ASR) first. If the client agrees to abort the request, it will respond to the abort user response (Abort Session Answer, ASA), then issue a user session end request, notifying the server to end the user session; otherwise the user session is still maintained. In the case that the server does not receive the request, the client can also issue a user session end request to the server, for example, if the client itself is abnormal, or the user access is abnormal. When the Diameter agent 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 client restarts abnormally. Only the Diameter agent detects the server. The Diameter server can be notified later, and the Diameter server can be notified one by one through the session corresponding to the Diameter agent to end the session and release the resources.

Summary of the invention

The invention solves the problem that the Diameter client terminates the session and releases the resources one by one through the session corresponding to the Diameter agent, and the network channel is wasted.

An aspect of the present invention provides a method for releasing resources after a network element is restarted, including: a second network node receiving a capability exchange request from a first network node, the capability exchange request carrying a first original state identifier; further comparing And storing, by the second network node, a second original state identifier corresponding to the first network node and the first original state identifier; if the result of the comparing is different, sending a session end request to the third network node, the session end request Carrying the first network node identifier and the restart identifier, so that the third network node can confirm the first network node restart according to the restart identifier, and further search for the first network node from the session mapping table stored by the third network node. Identify the related session identifier, and release the session resource corresponding to the related session identifier.

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

Another aspect of the present invention provides a method for releasing resources after a network element is restarted, comprising: a second network node receiving a capability exchange request from a first network node, the capability exchange request carrying a first original state identifier; Comparing the second original state identifier corresponding to the first network node and the first original state identifier stored by the second network node; if the result of the comparison is different, searching from the session mapping table stored by the second network node Corresponding to the third network node identifier and the related session identifier of the first network node identifier, and sending the related session identifier and the restart label to the third network node The session end request is obtained, 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 related session identifier.

Another aspect of the present invention provides a proxy device for releasing resources after a network element is restarted, including a first receiver, configured to receive a capability exchange request from a first network node, where the capability exchange request carries a first a first configurator, configured to compare a second original state identifier corresponding to the first network node and the first original state identifier that are stored by the first configurator, and the result of the comparison is different to generate a first network a node end identifier and a session end request for restarting the identifier; the first sender, 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 The session identifier is found in the session mapping table, and the session identifier corresponding to the related session identifier is released.

Another aspect of the present invention provides a server for releasing resources after a network element is restarted, including a first receiver, configured to receive a session end request from a second network node, where the session end request carries a first network node And identifying, by the first processor, the first network node restarting according to the restart identifier, and searching for a session identifier related to the first network node identifier from the stored session mapping table, releasing 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 is restarted, including a second receiver, where the application receives a capability exchange request from a first network node, where the capability exchange request carries a first original a second identifier, configured to compare the second original state identifier corresponding to the first network node and the first original state identifier that are stored by the first configurator, and the result of the comparison is different from the stored session mapping table. And searching for a session end identifier corresponding to the identifier of the third network node and the identifier of the first network node, and generating a session end request carrying the related session identifier and the restart identifier, where the second sender is configured to send the session to the third network node Ending the request, so that the third network node can confirm that the first network node restarts according to the restart identifier, and release the session resource corresponding to the related session identifier.

DRAWINGS

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

2 is a flowchart 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; FIG. 4 is a general architecture diagram of a Diameter SIP application according to the present invention; FIG. 5 is a signaling diagram of a method for releasing resources after a network element is restarted according to the present invention; FIG. 6 is a proxy structure diagram 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 schematic diagram of an agent structure for releasing resources after a network element is restarted according to the present invention;

The following description and the annexed drawings set forth in detail These examples are by way of example only and the invention can be implemented in other different ways.

detailed description

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

S 1001. 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 a GGSN and a CBP in a VoIP network architecture; for example, an IMS architecture P-CSCF and CCF or S-CSCF and MRFC. The second network node specifically refers to a proxy node between the first network node and the second network node, and the proxy node is generally arranged to shield the number of DCC servers from the DCC client of the Diameter Credit Control (DCC), or For security and reliability considerations, avoid direct connection between the DCC client and the DCC server.

The second network node may receive the session request from the first network node in addition to the capability exchange 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 is such that the third network node can add the session identifier to the session mapping table corresponding to the first network node identifier, where the session mapping table is stored in the third network node.

The session request includes a credit control request CCR, an Abort Session Request (ASR), a Disconnect Peer Request (DPR), and a Session Termination Request (STR) in addition to the capability exchange request. Wait.

S1002: Compare a 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 an AVP parameter Origin-State-Id in the Diameter protocol, and the value is changed only when the first network node is restarted and is abnormally restarted, for example, the first network node is powered off, the system is crashed, and the like. In turn, the session between the network nodes is not ended normally through the STR message. When the first network node after the restart initiates the capability exchange request CER again, it will carry a new one. The Origin-State-Id, Origin-State-Id change process is a single-increment. The new Origin-State-Id median value is larger than the Origin-State-Id value carried in the capability exchange request CER or session request before the abnormal restart. .

S1003. If the comparison result is different, the session end request is sent to the third network node.

The session end request carries 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 first network from the stored session mapping table. The node identifier is related to the session identifier, and the session resource corresponding to the related session identifier is released.

The session identifier associated with the identifier of the first network node may be one or more session identifiers, which is determined by the number of sessions established by the first network node and the third network node by the first network 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 the session end request that does not carry the restart identifier, the session end request carries the session identifier to be ended, and after successfully releasing the session resource corresponding to the session identifier, the slave 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 the network nodes, but since the proxy node is used between the first network node and the third network node, the STR carries the identifier of the second network node. There is a session identifier corresponding to the end, and a session process usually contains multiple session identifiers. Therefore, the existing technology needs to send multiple STRs to end the session where the abnormal first network node fails 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 identifier of the first network node by using the session mapping table, where the session identifier is the first network node and the third network The session ID generated by the node. The first network node identifier and the restart identifier are further carried in the STR, so that the third network node can end the related session in the session mapping table corresponding to the first network node by using one STR message.

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

The capability exchange request carries a first original state identifier. The second network node may receive the session request from the first network node in addition to the capability exchange 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 And adding the session identifier to the session mapping table corresponding to the third network node identifier and the first network node identifier, where the session mapping table is stored in the second network node.

S2002: Compare, by the self, the second original state identifier corresponding to the first network node and the first original state identifier.

The second original state identifier is an AVP parameter Origin-State-Id in the Diameter protocol, and the value is changed only when the first network node is restarted and is abnormally restarted, for example, the first network node is powered off, the system is crashed, and the like. In turn, the session between the network nodes is not ended normally through the STR message. When the first network node after the restart initiates the capability exchange request CER again, it will carry the new one.

The Origin-State-Id, Origin-State-Id change process is a single-increment. The new Origin-State-Id median value is larger than the Origin-State-Id value carried in the capability exchange request CER or session request before the abnormal restart. .

S2003, the result of the comparison is different, the corresponding session identifier corresponding to the third network node identifier and the first network node identifier is searched from the session mapping table stored by the second network node, and the related session identifier is sent to the third network node. And the session end request to restart the identity.

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

Preferably, an AVP parameter is generated, and the related 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 the third network node confirms that the first network node is restarted. And extracting the data content from the AVP parameter, that is, the related session identifier, and releasing the session resource according to the related session identifier.

In the following description, for purposes of illustration and description, reference, However, it will be apparent to those skilled in the art that the present 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 invention.

An embodiment of the present invention provides a method for releasing resources after a network element is restarted, and the signaling is as shown in FIG. 3. In this embodiment, the first network node, that is, the Diameter client, may be a gateway. The GPRS support node (GGSN), the second network node, that is, the Diameter proxy, may be a Diameter Credit Control Proxy (DCCproxy), and the third network node, that is, the Diameter server, may be a convergent charging connection. The Convergence Billing Point (CBP), the session request message is embodied as a Credit Control Request (CCR)/Credit Control Answer (CCA) in the Diameter message, and further relates to a capability exchange request (Capabilities). Exchange Request, CER) / Capabilities Exchange Answer (CEA); GGSN, DCCproxy, and 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, where the Diameter message is specifically a capability exchange request CER message, and the CER is mainly used for requesting message exchange local capability between Diameter entities, and carries the AVP parameter original The status indicator Origin-State-Id, the original status identifier is carried in each Diameter message during a stable operation, and remains unchanged. In this embodiment, the GGSN is sent as a Diameter client due to an abnormal situation, and then sent by the subsequent GGSN. The value of the Origin-State-Id carried in the Diameter message is larger than that before the restart. The value of the Origin-State-Id can be the time of the restart time or the single-variable variable of the non-volatile storage record. The single-increment variable of the non-volatile storage record, and set its current value to 5.

After receiving the CER message sent by the GGSN, the DCCproxy further searches for the corresponding Origin-State-Id value, which is the same as the original host name Origin-Host identifier carried in the CER message, in the storage area.

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

When the storage area finds that the corresponding Origin-State-Id is the same, it returns a capability interaction response CEA message to the GGSN.

S303: The GGSN sends a Diameter message to the DCCproxy, where the Diameter message is specifically a credit control request CCR message, where the message includes information such as authentication, charging, and authorization of the user. S304. When forwarding the CCR message to the convergent charging access point CBP, the DCCproxy adds a custom AVP parameter HW_EatestHostName in the CCR message, and the extended CCR complete message format is as follows. In actual situations, some of them may be Combination of item AVP parameters:

<Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY >

<Session-Id>

{Origin-Host}

{Origin-Realm}

{Destination-Realm}

{Auth- Application-Id}

{ Service-Context-Id}

{ CC-Request-Type }

{CC-Request-Number}

[Destination-Host]

[Origin- State-Id]

[Event-Timestamp]

* [Subscription-Id]

[Termination-Cause]

[Multiple-Services-Indicator]

* [Multiple-Services-Credit Control]

[ User-Equipment-Info ]

[Service-Information]

*[AVP]

[HW— OriginHostName]

The DCCproxy assigns the Origin-Host data content carried by the CCR received in the S303, that is, the GGSN identifier to the HW_EatgencyHostName, and forwards the carried

HW—The credit control request CCR message identified by OriginHostName, and the CCR message forwarded by DCCproxy to CBP mainly includes:

Session-Id=Sessionl

Origin-Host=DCCl Origin-State-Id=3

HW_OriginHostName=GGSN

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

S305. The CBP receives the credit control request CCR message, and the AVP parameters in the CCR message are: the session identifier Session-Id and the original host name identifier HW—EathostHostName, and are added according to the HW— OriginHostName and the Session-Id corresponding to the Diameter client GGSN. The session identifier Session1 is in the conference mapping table, and the conference mapping table is saved in the CBP, and the format is as follows:

S306-S307, CBP sends a credit control response CCA message to the DCCproxy, which includes

The content of the request carried in the CCR message, and the AVP parameter Destination-Host pointing to the DCCproxy and the current session parameter Session-Id.

S308, performing the same service interaction between S301 and S307, and further, the session request sent by the session may be different, and the specific processing may also be changed according to the session request; the subsequent CBP receives the Diameter message, such as the CCR message and the CER message, The CBP will carry the content according to the AVP parameter HW_EssenceHostName. For example, the GGSN searches for the corresponding session mapping table and updates the session mapping table. The specific update operations include adding the session identifier, deleting the session identifier, and the like.

S309-S310, the GGSN restarts due to an abnormality, and fails to send the session termination request STR before disconnecting from the DCCproxy, re-establishes a connection with the DCCproxy after completing the restart, and sends a CER message to perform capability negotiation, and the message includes necessary parameters. :

Origin-Host=GGSN

Origin-State-Id=6

The value of the Origin-State-Id is incremented from the previous 5 to 6 after the GGSN is restarted. The CER message carries the AVP parameters Origin-Host and Origin-State-Id—and indicates that the Diameter entity GGSN is completed. 5311. The DCCproxy receives the CER message of the GGSN, and compares the value of the Origin-State-Id of the corresponding GGSN stored in the CER to the value of the Origin-State-Id carried in the CER, and confirms that the GGSN sends the STR to the CBP because of abnormal restart. Message, which carries the key AVP parameters:

Termination-Cause=CLIENT— REBOOT

HW_OriginHostName=GGSN

The main parameters in the message also include:

Session-ld=0

Termination-Cause=CLIENT— REBOOT

HW_OriginHostName=GGSN

Where Session-ld=0 indicates any session, Termination-Cause=CLIENT-REBOOT indicates that the reason is the client restart, the restart identifier CLIENT-REBOOT is a custom identifier, and the CLIP-REBOOT identifier is parsed and operated at the CBP end. achieve.

5312. After receiving the STR message, the CBP determines that if the content of the AVP parameter Termination-Cause identifier is the restart identifier CLIENT_REBOOT, the original host name is identified.

The data content in the HW_OriginHostName GGSN queries the corresponding session mapping table, and obtains all session identifiers Session-Id corresponding to the GGSN;

The specific session mapping table may be in the format shown in the following table. If the following data is included in the correspondence table between the Diameter client GGSN and the session identifier, the CBP will release the session resources corresponding to the Session1, Session6, and Session9 session identifiers; Corresponding to the information related to the session identifier; the actual session mapping table may also save the Session-Id by using the HW_ErichostName as a distinct packet, and the specific implementation is not limited thereto;

Diameter client Session ID HW— OriginHostName Session-Id

GGSN Sessionl

GGSN Session6

GGSN2 Session4 GGSN Session9

After the resource is released, the CBP replies to the DCCproxy with a session termination response STA message, which carries the successfully terminated session identifier or the error message during the termination of the session;

5314. The DCCproxy replies to the GGSN with a capability interaction response CEA message according to the success information carried in the received STA.

The sequence of steps S311 and S314 in the foregoing embodiment is a preferred solution of the present invention, which is advantageous for reducing resource processing pressure on the server side. In an optional case, steps S311 and S314 can also be performed synchronously, and the GGSN can be improved on the basis of increasing the processing of the server. After the restart, the DCCproxy capability is exchanged to request the processing speed of the CER message.

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 the DCCproxy, and the session mapping table is added to the HW- OriginHostName corresponding to the server.

CLIENT_REBOOT further implements a CER message through a session termination request according to the session mapping table. The release function of the corresponding session resource in the CBP after the abnormal restart of the GGSN improves the network transmission efficiency.

The general system of the Diameter SIP application is shown in Figure 4. The Diameter client A can be

The Interrogating Call Session Control Function (I-CSCF) in the IMS, and the Diameter Client B may specifically be a Serve Call Session Control Function (S-CSCF) in the IMS. The server may specifically be a Home Subscriber Server (HSS) in the IMS, where the proxy unit A and the proxy unit B are optional in the system.

An embodiment provided by the present invention is shown in FIG. 5 as the A side in the general system of the Diameter SIP application, and is a Diameter signaling interaction diagram for charging, where the Diameter client A is the first network node. Specifically, it is a Proxy Call Session Control Function (P-CSCF) unit, and the Diameter server, that is, the third network node is specifically a Charging Accumulated Function (CCF) unit, and has a proxy unit proxy, that is, a second In the case of a network node, an Accounting-Request (ACR) message and an Accounting Answer (ACA) message and an STR/STA are used as the Diameter message for transmission. In this embodiment, an accounting request is taken as an example. The authentication and authorization process before billing is not completed The entire description, but does not affect the statement of the embodiment point of the present invention, those skilled in the art can complete the entire billing signaling process by means of the SIP Diameter protocol, and the specific implementation process is:

5501. The P-CSCF sends a Diameter message to the proxy unit proxy, where the Diameter message is an accounting request ACR message. When the P-CSCF state is normal, 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 starting value to 20111128T152000Z; a complete ACR message is as follows:

< Accounting-Request > ::= < Diameter Header: 271, REQ, PXY >

< Session-Id >

{ Origin-Host }

{ Origin-Realm }

{ Destination-Realm }

{ Accounting-Record-Type }

{ Accounting-Record-Number }

[ Acct- Application-Id ]

[ Vendor- Specific- Application-Id ]

[ User-Name ]

[ Accounting- Sub- Session-Id ]

[ Acct-Session-Id ]

[ Acct-Multi- Session-Id ]

[ Acct-Interim-Interval ]

[ Accounting-Realtime-Required ]

[ Origin- State-Id ]

[ Event-Timestamp ]

* [ Proxy-Info ]

* [ Route-Record ]

* [ AVP ]

The proxy unit proxy identifies the Diameter message as an ACR message, and generates an ACR message forwarded to the CCF, and uses the identifier of the identifier as the value of the AVP parameter Origin-Host in the forwarded ACR message to generate the proxy unit and the CCF. Session ID Session2 and as forwarding The value of the AVP parameter Session-Id in the ACR message, the session2 corresponding to the Diameter client P-CSCF and the Diameter server CCF are saved in the session mapping table in the proxy proxy to establish the Session2 and the Diameter client P-CSCF and the Diameter server CCF. Mapping relationship, the specific conference mapping table format is as follows:

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

5504. 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 a charging response ACA message to the proxy.

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

The processing flow of the foregoing steps S501-S505 may be included in the process, and the Diameter client identifier and the Diameter server identifier are saved in the session mapping table according to the session identifier, where the session identifier is generated by the proxy unit and carried in the forwarding In the Diameter message of the CCF;

S507-508, P-CSCF does not end the charging normally due to some sudden reasons, the normal end does not end, for example: no STR message is sent to end the session; then in the conference capability request CER sent after restarting the P-CSCF The value of the AVP parameter Origin-State-Id will change to the current time, which may be set to 20111128T152530Z;

S509. The proxy proxy exchanges the data content of the received and saved Origin-State-Id for the same Origin-Host identifier according to the Origin-Host in the CER of the receiving capability exchange request, and receives the data of the Origin-State-Id. When the content value is larger, it is analyzed that the P-CSCF restarts due to the 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 — Sessionl

Termination-Cause=CLIENT—REBOOT indicates that the reason for the transmission is the client restart, the restart identifier CLIENT-REBOOT is a custom identifier, and the corresponding identifier is parsed and operated in the CCF. When the data content corresponding to the terminating session identifier Terminat_session contains the original host name identifier and the corresponding session mapping table, the AVP parameter original host name identifier HW_OriginHostName in the session termination request STR is optional, and a complete STR message is as follows: :

< Session-Id >

{ Origin-Host }

{ Origin-Realm }

{ Destination-Realm }

{ Auth- Application-Id }

{ Termination-Cause }

[ User-Name ]

[ Destination-Host ]

* [ Class ]

[ Origin- State-Id ]

* [ Proxy-Info ]

* [ Route-Record ]

* [ AVP ]

{ HW OriginHostName

{ Terminat— Session }

The Terminat-Session is the AVP parameter added to the invention. The format of the AVP that meets the standard is as follows:

AVP code

AVP Length Vendor ID (optional) Data

The data content is for the Origin-State-Id, which is 20111128T152000Z, and

The Origin-Host is a session mapping table generated by the P-CSCF; the data content optionally includes only the session identifier in the session mapping table, and the HW_EuropeHostName identifier is preferred at this time; 5510. After the CCF is identified as the charging request message ACR according to the command code of the Diameter message, the CCF is learned from the data content CLIENT_REBOOT of the Termination-Cause that the P-CSCF needs to abandon the session resource before the restart because of the abnormal restart, so the new session is started. The processing function is configured to release the resource corresponding to the session identifier according to the session identifier Session-Id corresponding to the content of the Terminate_Schedule in the ACR message or the session mapping table of the P-CSCF;

5511. The CCF sends a session end response STA message to the proxy unit proxy, where the successfully terminated session identifier Session-Id or the error message during the termination of the session is carried;

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

In this embodiment, the Diameter client identifier and the Diameter proxy are forwarded to the Diameter client.

A session mapping table between the session identifier of the Diameter service and the Diameter server; the session identifier is generated by the Diameter agent, and the Diameter server and the Diameter client are visible to the Diameter for the direct interaction node, for the maintenance session mapping The table can provide more efficient processing, which increases the processing complexity of the Diameter agent based on 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: a first receiver 601, which 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 and the first original state identifier that are stored by the user, and the result of the comparison is different to generate the identifier of the first network node and Restart the identified session end request;

The first transmitter 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 the first network from the session mapping table. The node identifier is related to the session identifier, and the session resource corresponding to the related session identifier is released.

The proxy device 600 further includes:

The first receiver 601 is further configured to receive a session request from the first network node, where the first configurator 602 is further configured to generate a session request that carries the first network node identifier and the session identifier. The first transmitter 603 is further configured to forward, to the third network node, the session request that carries the first network node identifier and the session identifier, so that the third network node can add the identifier to the first network node identifier. The session is identified to a session mapping table, which is stored in the third network node.

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

a first receiver 701, 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, according to the restart identifier, that the first network node is restarted, 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. Resources.

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 the 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 an apparatus 800 for releasing resources after a network element is restarted, including:

a 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;

a second configurator 802, configured to compare a second original state identifier corresponding to the first network node that is stored by itself and the first original state identifier, where the result of the comparison is different, and the corresponding correspondence is searched from the stored session mapping table. And determining, by the third network node identifier and the related session identifier of the first network node identifier, a session end request carrying the related session identifier and the restart identifier;

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

The apparatus 800 further includes:

The second receiver 801 is further configured to receive a session request from the first network node, where the second configurator 802 is further configured to add the session identifier to the third network node identifier and the first network node identifier to a session mapping table, the session mapping table being stored in the second network node. Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or by software plus necessary general hardware platform. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

A person skilled in the art can understand that the drawings are only a schematic diagram of a preferred embodiment, and the modules or processes in the drawings are not necessarily required to implement the invention.

Those skilled in the art can understand that the modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the description of the embodiments, or the corresponding changes may be located in one or more apparatuses different from the embodiment. The modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.

In conclusion, the above is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for releasing resources after a network element is restarted, which is characterized by:

Receiving, by the second network node, a capability exchange request from the first network node, where the capability exchange request carries a first original state identifier; and further comparing, by the second network node, a second original state identifier corresponding to the first network node The first original state identifier;

If the result of the comparison is different, a session end request is sent to the third network node, where the session end request carries the first network node identifier and the restart identifier, so that the third network node can confirm that the first network node is restarted according to the restart identifier. And searching for the session identifier associated with the first network node identifier from the session mapping table stored by the third network node, and releasing the session resource corresponding to the related session identifier.

2. The method of claim 1, wherein the method further comprises: receiving a session request from the first network node, and forwarding, to the third network node, the first network node identifier and the session identifier The session request enables the third network node to add the session identifier to the session mapping table corresponding to the first network node identifier.

The method according to claim 2, wherein the first network node is a gateway GPRS support node, the session request is a credit control request, and the third network node is a convergent charging access point. The method specifically includes:

Receiving a credit control request from the gateway GPRS support node, and forwarding, to the convergent charging access point, a credit control request carrying the gateway GPRS support node identifier and the session identifier, so that the convergent charging access point can correspond to the gateway GPRS support node identifier The session identifier is added to a session mapping table, and the session mapping table is stored in a convergent charging access point.

The method according to claim 1, 2 or 3, wherein the first network node is a gateway GPRS support node, the second network node is a Diameter credit control agent, and the third network node is Converging the charging access point, the method specifically includes:

The Diameter credit control agent receives the capability exchange request from the gateway GPRS support node, and further compares the second original state identifier corresponding to the gateway GPRS support node and the first original state identifier stored by the Diameter Credit Control Agent;

If the result of the comparison is different, a session end request is sent to the convergent charging access point, where the session end request carries the gateway GPRS support node identifier and the restart identifier, so that the convergent charging access point can And determining, according to the restart identifier, that the gateway GPRS support node is abnormally restarted, and further searching for the session identifier related to the gateway GPRS support node identifier from the session mapping table, and releasing the session resource corresponding to the related session identifier.

5. A method for releasing resources after a network element is restarted, and the method includes:

Receiving a session end request from the second network node, the session end request carrying the first network node identifier and the restart identifier, further confirming that the first network node restarts according to the restart identifier, and searching and searching from the stored session mapping table The first network node identifies the related session identifier, and releases the session resource corresponding to the related session identifier.

The method of claim 5, wherein the method further comprises: receiving a session request from the second network node, the session request carrying the first network node identifier and the session identifier, corresponding to the The first network node identifier adds the session identifier to a session mapping table, and the session mapping table is stored in a third network node.

The method of claim 6, wherein the first network node is a gateway GPRS support node, the session request is a credit control request, and the third network node is a convergent charging access point, and the method specifically includes:

The convergent charging access point receives a credit control request from a credit management agent, where the credit control request carries a gateway GPRS support node identifier and a session identifier, and the session identifier is added to the session mapping table corresponding to the gateway GPRS support node identifier The session mapping table is stored in the converged charging access point.

8. The method of claim 5, 6 or 7, wherein the first network node is a gateway

The GPRS support node, the second network node is a Diameter credit control agent, and the third network node is a fusion charging access point. The method specifically includes:

The converged charging access point receives a session end request from the credit management agent, where the session end request carries a gateway GPRS support node identifier and a restart identifier, and further determines, according to the restart identifier, that the gateway GPRS support node is restarted, and is stored from the The session mapping table is configured to search for a session identifier associated with the gateway GPRS support node identifier, and release the session resource corresponding to the related session identifier.

9. A method for releasing resources after a network element is restarted, and the method includes: Receiving, by the second network node, a capability exchange request from the first network node, where the capability exchange request carries a first original state identifier; and further comparing, by the second network node, a second original state identifier corresponding to the first network node The first original state identifier;

If the result of the comparison is different, the related session identifier corresponding to the third network node identifier and the first network node identifier is searched from the session mapping table stored by the second network node, and the correlation is sent to the third network node. The session identifier and the session end request of the restart identifier enable the third network node to confirm that the first network node restarts according to the restart identifier, and release the session resource corresponding to the related session identifier.

10. The method according to claim 9, wherein the method further comprises: receiving a session request from the first network node, forwarding the session request carrying the session identifier to the third network node; and further the second network node And adding the session identifier to the session mapping table corresponding to the third network node identifier and the first network node identifier, where the session mapping table is stored in the second network node.

A proxy device for releasing resources after a network element is restarted, comprising: a first receiver, configured to receive a capability exchange request from a first network node, where the capability exchange request carries a first original Status identifier

a first configurator, configured to compare a second original state identifier corresponding to the first network node and the first original state identifier that are stored by the first configurator, and the result of the comparison is different to generate a first network node identifier and restart The identified session end request;

a first transmitter, 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 the first network node from the session mapping table. Identify the related session identifier, and release the session resource corresponding to the related session identifier.

12. The device of claim 11, further comprising:

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

The first configurator is further configured to generate a session request that carries the first network node identifier and the session identifier;

The first transmitter is further configured to forward, to the third network node, the session request that carries the first network node identifier and the session identifier, so that the third network node can add the session to the first network node identifier. The session mapping table is identified, and the session mapping table is stored in the third network node.

A server for releasing resources after a network element is restarted, comprising: a first receiver, configured to receive a session end request from a second network node, where the session end request carries a first network node identifier And restart the logo;

a first processor, configured to confirm that the first network node is restarted 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 resource corresponding to the related session identifier .

The server according to claim 13, further comprising:

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

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

A proxy device for releasing resources after a network element is restarted, comprising: a second receiver, the application receives a capability exchange request from a first network node, where the capability exchange request carries a first original state Identification

a second configurator, configured to compare the second original state identifier corresponding to the first network node and the first original state identifier that are stored by the first configurator, and the result of the comparison is different from the stored session mapping table And determining, by the third network node identifier and the related session identifier of the first network node identifier, a session end request carrying the related session identifier and the restart identifier;

And a second transmitter, configured to send the session end request to the third network node, so that the third network node can confirm that the first network node restarts according to the restart identifier, and release the session resource corresponding to the related session identifier.

The device according to claim 15, comprising:

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

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