WO2013107402A1 - Procédé, dispositif et système de libération de ressources après le redémarrage d'un élément de réseau - Google Patents

Procédé, dispositif et système de libération de ressources après le redémarrage d'un élément de réseau Download PDF

Info

Publication number
WO2013107402A1
WO2013107402A1 PCT/CN2013/070752 CN2013070752W WO2013107402A1 WO 2013107402 A1 WO2013107402 A1 WO 2013107402A1 CN 2013070752 W CN2013070752 W CN 2013070752W WO 2013107402 A1 WO2013107402 A1 WO 2013107402A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
identifier
network node
request
mapping table
Prior art date
Application number
PCT/CN2013/070752
Other languages
English (en)
Chinese (zh)
Inventor
陆敬石
杨斌
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2013107402A1 publication Critical patent/WO2013107402A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • 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.
  • 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 is the most suitable for future authentication, authorization, and accounting of mobile communication systems.
  • 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.
  • a Diameter protocol such a series of information interaction from initiation to suspension.
  • 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.
  • ASR Abort Session Request
  • ASA Abort Session Answer
  • 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.
  • the Diameter agent 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.
  • 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.
  • 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.
  • 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 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 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.
  • DCC Diameter Credit Control
  • 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.
  • CCR credit control request
  • ASR Abort Session Request
  • DPR Disconnect Peer Request
  • STR Session Termination Request
  • 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.
  • 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. .
  • 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.
  • the corresponding session identifier is deleted from the session mapping table.
  • 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.
  • 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.
  • 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. .
  • 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.
  • 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.
  • the first network node that is, the Diameter client
  • the first network node 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).
  • GGSN, DCCproxy, and CBP are all Diameter entities.
  • the specific implementation process is as follows:
  • 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.
  • 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.
  • the DCCproxy 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.
  • 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;
  • the storage area finds that the corresponding Origin-State-Id is the same, it returns a capability interaction response CEA message to the GGSN.
  • 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.
  • 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:
  • 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
  • the credit control request CCR message identified by OriginHostName, and the CCR message forwarded by DCCproxy to CBP mainly includes:
  • 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:
  • CBP sends a credit control response CCA message to the DCCproxy, which includes
  • 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.
  • 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.
  • 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.
  • 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
  • the main parameters in the message also include:
  • Termination-Cause CLIENT— REBOOT
  • 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.
  • 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;
  • 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;
  • the DCCproxy replies to the GGSN with a capability interaction response CEA message according to the success information carried in the received STA.
  • 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.
  • 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.
  • 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.
  • Diameter client A can be any Diameter client A.
  • 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.
  • HSS Home Subscriber Server
  • FIG. 5 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.
  • ACR Accounting-Request
  • ACA Accounting Answer
  • STR/STA STR/STA
  • 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
  • the P-CSCF sends a Diameter message to the proxy unit proxy, where the Diameter message is an accounting request ACR message.
  • the original state identifier Origin-State-Id value in the ACR message remains unchanged.
  • you may wish to use the time parameter method, and set the starting value to 20111128T152000Z; a complete ACR message is as follows:
  • 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:
  • the proxy unit proxy forwards the generated ACR message to the CCF.
  • 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.
  • 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;
  • 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;
  • 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.
  • 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
  • Terminat — Session Terminat — Sessionl
  • the restart identifier CLIENT-REBOOT is a custom identifier
  • the corresponding identifier is parsed and operated in the CCF.
  • 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: :
  • Terminat-Session is the AVP parameter added to the invention.
  • the format of the AVP that meets the standard is as follows:
  • 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.
  • 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;
  • 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;
  • 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.
  • the Diameter client identifier and the Diameter proxy are forwarded to the Diameter client.
  • 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:
  • 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.
  • 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 non-volatile storage medium which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention s'applique au domaine de la communication informatique et concerne principalement un procédé, un dispositif et un système de libération de ressources après le redémarrage d'un élément de réseau. Selon l'invention, le procédé fait appel : à la réception, par un deuxième nœud de réseau, d'une requête d'échange de capacité provenant d'un premier nœud de réseau et transportant un premier identificateur d'état d'origine ; à la comparaison d'un second identificateur d'état d'origine, qui correspond au premier nœud de réseau et qui est mémorisé dans le deuxième nœud de réseau, avec le premier identificateur d'état d'origine ; si les identificateurs sont différents, à la transmission d'une requête de fin de session à un troisième nœud de réseau, la requête de fin de session transportant le premier identificateur de nœud de réseau et un identificateur de redémarrage. Ainsi, le gaspillage de passages de réseau provoqué par un redémarrage anormal du premier nœud de réseau est réduit.
PCT/CN2013/070752 2012-01-21 2013-01-21 Procédé, dispositif et système de libération de ressources après le redémarrage d'un élément de réseau WO2013107402A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210020513.X 2012-01-21
CN201210020513.XA CN102612164B (zh) 2012-01-21 2012-01-21 一种针对网元重启后释放资源的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2013107402A1 true WO2013107402A1 (fr) 2013-07-25

Family

ID=46529230

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/070752 WO2013107402A1 (fr) 2012-01-21 2013-01-21 Procédé, dispositif et système de libération de ressources après le redémarrage d'un élément de réseau

Country Status (2)

Country Link
CN (1) CN102612164B (fr)
WO (1) WO2013107402A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8837320B2 (en) 2012-07-23 2014-09-16 Apple Inc. Methods and systems for anchored down-selection in a coordinated multipoint transmission cluster

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102612164B (zh) * 2012-01-21 2016-06-29 华为技术有限公司 一种针对网元重启后释放资源的方法、装置和系统
CN102821011A (zh) * 2012-08-28 2012-12-12 北京星网锐捷网络技术有限公司 对端状态检测方法、装置及设备
CN106330823A (zh) * 2015-06-23 2017-01-11 中兴通讯股份有限公司 一种会话保活方法及装置
CN107872326B (zh) * 2016-09-26 2020-09-08 华为技术有限公司 一种释放会话资源的方法、装置和系统
CN111600832B (zh) * 2019-07-25 2022-09-30 新华三技术有限公司 报文处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101543030A (zh) * 2007-04-02 2009-09-23 日本电气株式会社 Ims网络系统和数据恢复方法
CN101765217A (zh) * 2009-12-15 2010-06-30 北京佳讯飞鸿电气股份有限公司 一种检测sip终端重启的方法
WO2011098155A1 (fr) * 2010-02-09 2011-08-18 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil destinés à être utilisés avec un réseau d'accès à connectivité ip
CN102612164A (zh) * 2012-01-21 2012-07-25 华为技术有限公司 一种针对网元重启后释放资源的方法、装置和系统
CN102802143A (zh) * 2011-05-26 2012-11-28 华为软件技术有限公司 一种业务恢复方法、相关装置以及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101543030A (zh) * 2007-04-02 2009-09-23 日本电气株式会社 Ims网络系统和数据恢复方法
CN101765217A (zh) * 2009-12-15 2010-06-30 北京佳讯飞鸿电气股份有限公司 一种检测sip终端重启的方法
WO2011098155A1 (fr) * 2010-02-09 2011-08-18 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil destinés à être utilisés avec un réseau d'accès à connectivité ip
CN102802143A (zh) * 2011-05-26 2012-11-28 华为软件技术有限公司 一种业务恢复方法、相关装置以及系统
CN102612164A (zh) * 2012-01-21 2012-07-25 华为技术有限公司 一种针对网元重启后释放资源的方法、装置和系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8837320B2 (en) 2012-07-23 2014-09-16 Apple Inc. Methods and systems for anchored down-selection in a coordinated multipoint transmission cluster

Also Published As

Publication number Publication date
CN102612164B (zh) 2016-06-29
CN102612164A (zh) 2012-07-25

Similar Documents

Publication Publication Date Title
EP4024922A1 (fr) Procédé pour obtenir une continuité de service et dispositifs associés
JP5847191B2 (ja) コンテンツ共有を行う中間ノード及びコンテンツリクエスト端末並びにそれらのコンテンツ共有方法
WO2013107402A1 (fr) Procédé, dispositif et système de libération de ressources après le redémarrage d'un élément de réseau
US8687511B2 (en) Secure location session manager
WO2009046678A1 (fr) Procédé et dispositif pour obtenir la capacité de fonction d'application de politique et de facturation
EP2534889B1 (fr) Procédé et appareil de redirection de trafic de données
WO2004040936A2 (fr) Procedure de mise a jour de session pour authentification, autorisation et prise en compte
JP6368042B2 (ja) オフライン課金のためのｃｄｆトラッキング
WO2013097193A1 (fr) Procédé, dispositif et système de détermination d'une fonction d'application de politique et de facturation
WO2009094945A1 (fr) Procédé d'imagerie pour entité de décision de politique, élément de réseau de gestion et système de gestion
WO2021063129A1 (fr) Procédé et système d'appel de capacité de réseau central
CN101160871A (zh) 建立聊天室数据传输通道实现聊天消息传送的方法
WO2012152155A1 (fr) Procédé et dispositif pour acquérir un état de disponibilité d'un terminal
WO2011134327A1 (fr) Procédé et système permettant de déterminer une fonction de règles de politique et de facturation
WO2007082446A1 (fr) Procede et systeme de taxation hors ligne
WO2011144083A2 (fr) Procédé et dispositif de contrôle de règles
WO2009094953A1 (fr) Procédé, système et dispositif de suppression de support
WO2009089776A1 (fr) Procédé et appareil de maintenance des informations de fonction de règle de politique et de facturation
WO2012167659A1 (fr) Procédé et dispositif de communication de données dans un protocole d'applications contraintes
WO2014169781A1 (fr) Procédé et système de fermeture de connexion par un utilisateur
WO2014040464A1 (fr) Procédé de libération de ressource, procédé de traitement de message, twag et terminal
WO2013071739A1 (fr) Procédé et dispositif de facturation d'utilisateur de double pile de protocoles ipv4/ipv6
WO2007124662A1 (fr) Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement
CN101102191B (zh) 通用鉴权框架中确定密钥请求业务类型方法
WO2012089032A1 (fr) Procédé de transmission de données utilisant de multiples procédés d'accès et dispositif d'accès

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13738298

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13738298

Country of ref document: EP

Kind code of ref document: A1