[go: up one dir, main page]

WO2008025216A1 - Procédé et système de mise à jour de ressources - Google Patents

Procédé et système de mise à jour de ressources Download PDF

Info

Publication number
WO2008025216A1
WO2008025216A1 PCT/CN2007/002314 CN2007002314W WO2008025216A1 WO 2008025216 A1 WO2008025216 A1 WO 2008025216A1 CN 2007002314 W CN2007002314 W CN 2007002314W WO 2008025216 A1 WO2008025216 A1 WO 2008025216A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
refresher
unit
header field
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2007/002314
Other languages
English (en)
Chinese (zh)
Inventor
Weiqiang Yang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2008025216A1 publication Critical patent/WO2008025216A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for implementing resource release. Background technique
  • IMS is a voice and data service system that can shield users' access methods and control the openness of service capabilities according to user data, thus providing a multimedia communication experience.
  • IMS which combines innovative voice, data, and multimedia applications, can generate new services such as presence services, multimedia chat, conferencing, push to talk, and push to conference.
  • IMS IMS services
  • call control for controlling user registration, session control, etc.
  • media gateway control/IMS media gateway function MGCF I IM-MGW
  • CSCF call control
  • MGCF I IM-MGW media gateway control/IMS media gateway function
  • the main devices in the IMS include an application server (AS) that provides various business logic control functions and a home subscriber server (HSS) for centrally managing user subscription data.
  • AS application server
  • HSS home subscriber server
  • the CSCF is divided into: a current local proxy node (P-CSCF), a registered home domain service node (S-CSCF), and an information node (I-CSCF) according to functions in the network.
  • P-CSCF is the access point of the user in the IMS system, and all SIP signaling flows from the UE or to the UE must pass through the P-CSCF.
  • the I-CSCF is the point of contact for all users connected to this carrier in an operator network.
  • the S-CSCF is in the core control position in the IMS core network and is located in the home network. Responsible for the UE Registration authentication and session control, performing basic session routing functions for the calling end and the called end IMS user, and triggering corresponding rules according to the IMS signed by the user.
  • the user accesses the IMS through the current local proxy node P-CSCF, and the session and service trigger control and the service control interaction with the AS are completed by the home domain service node S-CSCF of the registered place; the IMS uses the SIP protocol as the application layer interaction signaling.
  • the interface protocol between the terminal and the CSCF, between the CSCF, and between the CSCF and the AS is the SIP protocol.
  • the SIP protocol does not define a protocol that enables the intermediate node to detect whether the session is active after the session is established. This causes the intermediate node in the IMS system to fail to release the resource when the terminal sends a release indication message.
  • the Session Timers protocol complements the SIP protocol for this issue and is an extension of the SIP protocol.
  • the Session Timers protocol allows a terminal in the session to initiate a session update request periodically to ensure that the session is active. If the session update request is not received within the period or the session update request fails to be sent, the session is already inactive. Then the terminal releases the relevant resources. Intermediate nodes in the IMS system, such as the P-CSCF or S-CSCF, directly release the session-related resources after a timeout. This ensures the timely release of relevant resources.
  • Session Timers protocol it is convenient to implement as a proxy server (PROXY).
  • PROXY proxy server
  • P-CSCF and S-CSCF are usually only used as PROXY units.
  • AS which is usually used as a back-to-back user agent (B2BUA) unit
  • B2BUA back-to-back user agent
  • the Session Timers protocol is not specified. If the protocol is directly hardened, the session update request is repeatedly meaninglessly forwarded or collided during the session. It cannot be implemented smoothly, so the resource release problem of the B2BUA unit has not been solved well.
  • FIG. 1 is a schematic diagram of a process of meaningless forwarding of a session update request by a calling terminal.
  • Step 100 The calling terminal sends a session establishment request message to the B2BUA1 unit.
  • the session establishment request message sent by the calling terminal includes a Session-Expires header field, and may also include a supported (timer) header field and/or a minimum session termination (Min_SE) header field.
  • a Session-Expires header field may also include a supported (timer) header field and/or a minimum session termination (Min_SE) header field.
  • Step 101 The B2BUA1 unit receives the session establishment request message and performs related processing specified by the Session Timers protocol.
  • the User Agent Server (UAS) side of the B2BUA1 unit checks if there is a supported :timer header field in the message.
  • the session establishment request message has a supported:timer header field and the value of the Session-Expires header field is less than the value of the local Min_SE header field, a response is sent to the calling terminal indicating that the session update interval is too short and is in response With the value of the local Min_SE header field, after receiving the reply response, the calling terminal changes the value of the Session-Expires header field to a value not less than the value of the Min_SE header field, and sends it to the B2BUA1 unit again.
  • the session establishment request message does not have a supported:timer header field, and the value of the Session-Expires header field is smaller than the value of the local Min_SE header field, when there is an Mm_SE header field in the message, the message will be in the Min_SE The value of the header field is increased to be equal to the value of the local Min_SE header field and is the value of the Session-Expires header field.
  • the Min_SE header field is inserted in the request message, and its value is the local Mm— The value of the SE header field, and this value is used as the value of the Session-Expires header field.
  • the value of the Session-Expires header field may not be modified or may be not less than The value of the Min_SE header field in the message is not less than the value of the local Mm_SE header field, and the value of the Session-Expires header field is appropriately reduced.
  • the User Agent Client (UAC) of the B2BUA1 unit constructs a new session establishment request message according to the session establishment request message processed by the UAS.
  • Step 102 The B2BUA1 unit sends the processed session establishment request message to the PROXY unit. If there are multiple PROXY units, each PROXY unit forwards the session establishment request message; if there is no PROXY unit, B2BUA1 directly sends a session establishment request message to B2BUA2.
  • Step 103 The PROXY unit sends the received session establishment request message to the AS (B2BUA2 unit).
  • Step 104 The B2BUA2 unit receives the session establishment request message and performs a Session Timers protocol. The relevant processing.
  • the processing is the same as the processing of step 101.
  • Step 105 The B2BUA2 unit sends the processed session establishment request message to the called terminal. If there is a PROXY unit between the B2BUA2 and the called terminal, the PROXY unit forwards the received session establishment request message.
  • Step 106 The called terminal sends a 200 response message indicating success to the B2BUA2 unit.
  • PROXY unit If there is a PROXY unit between B2BUA2 and the called terminal, the PROXY unit will receive
  • Step 107 The B2BUA2 unit receives the 200 response message and performs related processing specified by the Session Timers protocol.
  • the UAC end of the B2BUA2 unit sets the refresher to uac according to the time of the Session-Expires header field and the refresher parameter in the response message. Therefore, the UAC end of the B2BUA2 unit starts the session update request timer and the timeout release timing. Timer.
  • the UAS end of the B2BUA2 unit starts the timeout release timer according to the value of the Session-Expires header field.
  • the session negotiation sets the refresher to uac, so the UAS end of the B2BUA2 unit does not start the send session update request timer.
  • Step 108 The B2BUA2 unit sends the processed 200 response message to the PROXY unit.
  • Step 109 The PROXY unit sends the received 200 response message to the AS (B2BUA1 unit). If there are multiple PROXY units, each PROXY unit forwards the message; if there is no PROXY unit, B2BUA2 sends the message directly to B2BUA1.
  • Step 110 The B2BUA1 unit receives the 200 response message for related processing specified by the Session Timers protocol.
  • the processing is the same as the processing of step 107.
  • Step 111 The B2BUA1 unit sends the processed 200 response message to the calling terminal.
  • Step 112 According to the parameter determined by the negotiation, the refresher is uac, and the calling terminal is responsible for initiating the session update request, and then the session update timer of the calling terminal expires (Session Expires / 2) seconds to notify the calling terminal to issue a session update to the B2BUA1 unit. request.
  • Step 113 According to the parameter determined during negotiation, the refresher is uac, and the UAC end of the B2BUA1 unit is responsible for initiating a session update request, and the session update timer of the B2BUA1 unit expires (SesExpires / 2) seconds to notify the UAC end of the B2BUA1 unit to issue a session to the PROXY unit. Update request.
  • Step 114 The B2BUA1 unit processes the session update sent by the calling terminal and sends it to the PROXY unit.
  • Step 115 The PROXY unit sends a session update request sent by the B2BUA1 unit to the AS (B2BUA2 unit).
  • Step 116 The PROXY unit sends a session update request sent by the B2BUA1 unit to the AS (B2BUA2 unit).
  • Step 117 According to the parameter determined by the negotiation, the refresher is uac, and the UAC end of the B2BUA2 unit is responsible for initiating a session update request, and the session update timer of the B2BUA2 unit expires (SessionExpires / 2) seconds to notify the B2BUA2 unit to issue a session update request to the called terminal. .
  • Step 118 The B2BUA2 unit processes the session update request sent by the PROXY unit and sends the session update request to the called terminal.
  • Step 119 The B2BUA2 unit processes the session update request sent by the PROXY unit and sends the session update request to the called terminal.
  • FIG. 1B is a schematic diagram of a collision process for issuing a session update request by a calling terminal.
  • Step 1000 The calling terminal sends a session establishment request message to the B2BUA1 unit.
  • the PROXY unit forwards the received session establishment request message.
  • Step 1001 The B2BUA1 unit receives the session establishment request message and performs related processing specified by the Session Timers protocol.
  • the UAS end of the B2BUA1 unit checks whether the message has the supported:timer header field.
  • the session establishment request message has a supported:timer header field, and Session-Expires If the value of the header field is smaller than the value of the local Min_SE header field, the response is sent to the calling terminal indicating that the session update interval is too short, and the value of the local Min SE header field is brought in the response, and the calling terminal receives the reply response. Change the value of the Session-Expires header field to a value no smaller than the Min_SE header field and send it back to the B2BUA1 unit.
  • the session establishment request message does not include the supported:timer header field, it indicates that the calling terminal does not support the Session Timers protocol, and the Session-Expires header i or the threshold is smaller than the local Min SE header field threshold, and there is a Min_SE in the message.
  • the value of the Mm_SE header field in the request message is increased to be equal to the value of the local Min SE header field and used as the value of the Session-Expires header field.
  • the Min_SE header field which is the value of the local Min_SE header field, and uses this value as the Session-Expires header; t or ⁇ ) value.
  • the value of the Session-Expires header field may not be modified or may be not less than The value of the Min-SE header field in the message is not less than the value of the local Mm_SE header field, and the value of the Session-Expires header field is appropriately reduced.
  • the UAC end of the B2BUA1 unit constructs a new request message according to the request message processed by the UAS.
  • Step 1002 The B2BUA1 unit sends the processed session establishment request message to the PROXY unit.
  • each PROXY unit forwards the session establishment request message; if there is no PROXY unit, B2BUA1 directly sends a session establishment request message to B2BUA2.
  • Step 1003 The PROXY unit sends the received session establishment request message to the AS (B2BUA2 unit).
  • Step 1004 The B2BUA2 unit receives the request message and performs related processing specified by the Session Timers protocol.
  • the processing is the same as the processing of step 1001.
  • Step 1005 The B2BUA2 unit sends the processed session establishment request message to the called terminal. If there is a PROXY unit between the B2BUA2 and the called terminal, the PROXY unit will receive The session establishment request message is forwarded.
  • Step 1006 The called terminal sends a 200 response message indicating success to the B2BUA2 unit.
  • the PROXY unit forwards the received 200 response message.
  • Step 1007 The B2BUA2 unit receives the 200 response message to perform the specified related processing.
  • the UAC end of the B2BUA2 unit sets the refresher between the B2BUA2 and the called terminal according to the time and session negotiation of the Session-Expires header field in the response message.
  • the UAS end of the B2BUA2 unit starts the related timer according to the value of the Session-Expires header field and the refresher parameter.
  • Step 1008 The B2BUA2 unit sends the processed 200 response message to the PROXY unit.
  • Step 1009 The PROXY unit sends the received 200 response message to the AS (B2BUA1 unit). If there are multiple PROXY units, each PROXY unit forwards the message; if there is no PROXY unit, B2BUA2 sends the message directly to B2BUA1.
  • Step 1010 The B2BUA1 unit receives the 200 response message for related processing specified by the Session Timers protocol.
  • the UAC end of the B2BUA1 unit starts the relevant timer according to the time and refresher parameters of the Session-Expires header field in the response message.
  • the UAS end of the B2BUA1 unit starts the related timer according to the value of the Session-Expires header field and the refresher parameter.
  • Step 1011 The B2BUA1 unit sends the processed 200 response message to the calling terminal.
  • the session is successfully established and the Session Timers are also negotiated successfully.
  • the session update timer of the calling terminal starts timing.
  • the calling terminal is responsible for initiating a session update request, and the session update timer of the calling terminal (Session Expires / 2) seconds informs the calling terminal to issue a session update request to the B2BUA1 unit.
  • Step 1013 The B2BUA1 unit processes and processes the session update request sent by the calling terminal to the PROXY unit.
  • Step 1014 The PROXY unit sends a session update request sent by the B2BUA1 unit to the AS (B2BUA2 unit).
  • Step 1015 The B2BUA2 unit processes the session update request sent by the PROXY unit and sends the session update request to the called terminal.
  • the session update timer of the B2BUA2 unit expires (SessionExpires / 2) seconds to notify the B2BUA2 unit to issue a session update request to the PROXY unit.
  • Step 1017 The PROXY unit sends a session update request sent by the B2BUA2 unit to the AS (B2BUA1 unit).
  • Step 1018 The B2BUA1 unit processes the session update request sent by the PROXY unit and sends the session update request to the calling terminal.
  • the session update timer of the B2BUA2 unit expires (SessionExpires / 2) seconds to notify the B2BUA2 unit to send a call to the called terminal. Update request.
  • the session update request of step 1012 and step 1017 collides, and the B2BUA1 unit forwards the redundant session update request.
  • the session resource needs to be released, and the calling terminal or the called terminal is required to have at least one session that supports the Session Timers protocol, and the calling terminal that supports the Session Timers protocol is Call a session update request from the terminal. If neither the calling terminal nor the called terminal supports the Session Timers protocol, each B2BUA unit will not be able to release the resources allocated for the session.
  • each B2BUA unit receives a session update request, and therefore cannot generate a new session update request because it cannot determine whether the request message is a session update or a normal service negotiation message. And sending the received session update request and the new session update request to the next B2BUA unit of the session establishment path until the called terminal.
  • each B2BUA unit also sends the received session update request and the generated new session update request to the calling side until the calling terminal . Therefore, since each B2BUA unit forwards and initiates a session update request, the user terminal receives a large number of meaningless session update requests. If the B2BUA unit sends a new session update request to both sides after receiving the session update request, Will cause a collision of session update requests.
  • the main purpose of the embodiments of the present invention is to provide a method and a system for implementing resource release, so that when the terminal does not support the Session Timers protocol, the resource release can be implemented when the session is in an inactive state.
  • Another object of the present invention is to provide a back-to-back user agent device, which is applied to a resource release system. When the terminal does not support the Session Timers protocol, if the session is in an inactive state, resource release can be implemented.
  • the back-to-back user agent B2BUA unit determines whether the supported header field with the time timer tag is included. If yes, the session establishment request message is forwarded. Otherwise, the timer tag is added to the message. Supported header field, and forwards the session establishment request message;
  • the node device performs the refresher negotiation between the node devices to determine that the node device is the refresher. After the session is established, the node devices determined to be the refresher by the negotiation respectively initiate a session update request to the other network nodes.
  • a system for implementing resource release according to an embodiment of the present invention includes: one or more back-to-back user agent B2BUA units;
  • Each B2BUA unit is configured to: after receiving the session establishment request message, determine whether the supported header field with the time timer tag is included, and if yes, forward the session establishment request message; otherwise, add a timer to the message.
  • the network nodes on which the session is routed on both sides of the connection initiate a session update request.
  • the session protocol judging module is configured to: after receiving the session establishment request message, determine whether the received session establishment request message has a Supported header field with a timer tag, and if yes, directly forward the session establishment request message, otherwise, Adding a Supported header field with a timer tag to the session establishment request message, and forwarding the session establishment request message;
  • a refresher negotiation module configured to perform a refresher negotiation with the node device to determine whether it is a refresher
  • the session update request module is configured to, if it is determined that it is a refresher, initiate a session update request to the network node of the current session on both sides connected to itself after the session is established.
  • the B2BUA unit determined by the refresher negotiation initiates a session update request to the calling terminal and the called terminal, so that the resource release can be realized even if the calling terminal and the called terminal do not support the Session Timers protocol.
  • the behavior of other B2BUA units actively initiating a session update request is cancelled, and only the request is forwarded after receiving the session update request. It avoids the problem of meaningless forwarding and collision of session update requests during the session.
  • FIG. 1 is a schematic flowchart of a meaningless forwarding of a session update request issued by a calling terminal
  • FIG. 1B is a schematic flowchart of a session update request collision of a session update request by a calling terminal
  • FIG. 2 is a system for releasing resources according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a B2BUA device according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for implementing resource release according to an embodiment of the present invention.
  • FIG. 5A is a schematic flow chart of a specific embodiment 1 for implementing the method of the present invention.
  • 5B is a schematic flow chart of a specific embodiment 2 of the method for implementing the present invention.
  • FIG. 6 is a schematic flow chart of a third embodiment of a method for implementing the method of the present invention.
  • FIG. 7 is a schematic flow chart of a fourth embodiment of a method for implementing the present invention.
  • FIG. 8 is a schematic structural diagram of a B2BUA device performing a refresher negotiation according to an embodiment of the present invention. detailed description
  • the B2BUA unit of the refresher actively initiates a session update request
  • the B2BUA unit of the refresher actively initiates a session update request.
  • the other B2BUA units do not initiate a session update request, thereby solving the above problem.
  • the B2BUA unit can actively initiate a session update request to the calling terminal and the called terminal, thereby realizing that both the calling terminal and the called terminal do not support the Session Timers protocol, Successfully established the Session Timers protocol.
  • the B2BUA unit determines the session. Whether the support request header field with the time timer tag is included in the request message, if yes, the session establishment request message is directly forwarded to the next node device; if not, the timer tag is added to the session establishment request message. The Supported header field will be added again. The session establishment request message of the Supported header field with the timer tag is forwarded to the next node device.
  • the refresher negotiation can also be performed between the node devices.
  • the refreshers determined by the negotiation respectively initiate a session update request to other node devices.
  • each node device After receiving the session update request, each node device sends a session update request to the upstream or downstream according to the received session update request until the calling terminal and the called terminal; each node device determines that the session is inactive. Next, release the resources that it has allocated for the session.
  • the B2BUA unit After the session is established, after the B2BUA unit receives the session establishment request message, if it determines that the message contains the Supported header field with the timer tag, the session update request is no longer generated, and only the session update is sent to the next node device of the session path. request.
  • FIG. 2 is a schematic structural diagram of a system for releasing resources according to an embodiment of the present invention.
  • the system of the present invention includes: one or more B2BUA units,
  • Each B2BUA unit is configured to: after receiving the session establishment request from the previous node device, determine whether the session establishment request carries a Supported header field of the timer tag, and if so, forward the session establishment request message to the next node device. Otherwise, a Supported header field with a timer tag is added to the session establishment request message, and the session establishment request message is forwarded to the next node device; after the session is established, if the session is determined to be inactive, the self is released. The resources allocated by the session.
  • the B2BUA unit After the session is established, if the B2BUA unit receives the session update request, the B2BUA unit is further configured to determine whether the session update request has a Supported header field with a timer tag, and if so, only according to the received session update request to the session. The next network node sends a session update request.
  • the B2BUA unit in the embodiment of the present invention includes: a session protocol determining module and a resource releasing module.
  • the session protocol judging module is configured to determine whether the received session establishment request message has a support header field with a timer tag, and if yes, directly forward the session establishment request message, otherwise, add the session establishment request message.
  • the Supported header field with a timer tag forwards the session establishment request message;
  • the source release module is configured to update the response message according to the received session Determine whether the session state is normal, and release the resources allocated for the session when the session is inactive.
  • the B2BUA unit may further include: a refresher negotiation module and a session update request module.
  • the refresher negotiation module is configured to add a refresher parameter in the session termination Session-Expires header field in the session establishment request message, and determine whether it is a refresher according to the received session establishment response message; the session update request module After the session is established, if it is determined that it is a refresher, a session update request is initiated to each of the network nodes that have established the session on both sides; if it is determined that it is not a refresher, it is determined whether the received session update request is carried.
  • the Supported header field of the timer tag if yes, sends a session update request only to the next network node of the session path.
  • FIG. 4 is a schematic diagram of a process for implementing resource release by using a first B2BUA unit to receive a session update request.
  • the first B2BUA unit is the first B2BUA unit that receives the session establishment request message during the session establishment process, and the other B2BUA units are similar to the first B2BUA unit method, and are not illustrated.
  • the method for implementing resource release in the embodiment of the present invention includes:
  • Step 400 After receiving the session establishment request message, the first B2BUA unit determines whether the message includes a Supported header field with a timer tag. If yes, indicating that the calling terminal supports the Session Timers protocol, step 401 is performed; otherwise, directly The session is forwarded to the next node device until the called terminal, and step 407 is performed.
  • Step 401 After receiving the session establishment request message, the first B2BUA unit inserts the supported:timer header field in the session establishment request message, and the refresh-expires header field in the session establishment request message Set to uac.
  • Step 402 The first B2BUA unit sends a support:timer header field session establishment request message to the next B2BUA unit.
  • Step 403 After receiving the session establishment request message, each B2BUA unit directly sends the session establishment request message to the next node device until the called terminal.
  • Step 404 After receiving the session establishment request message, the called terminal returns to the B2BUA unit connected thereto. After the session establishment response message is received, each B2BUA unit only starts the session timeout release timer, and sends the session establishment response message to the B2BUA unit to the first B2BUA unit.
  • Step 406 After the call is established, the first B2BUA unit initiates a session update request to both sides.
  • Step 407 After receiving the session update request, each B2BUA unit determines whether the session update request includes a Supported header field with a timer tag. If yes, and directly forwards the session update request to the next node device, no new session is generated here. For the session update request, go to step 410.
  • Step 408 After receiving the session establishment request message, the called terminal returns a session establishment response message to the B2BUA unit connected thereto. After receiving the session establishment request message, each B2BUA unit starts the session timeout release timer and establishes the session. The response message is sent to the B2BUA unit at the first level until the first
  • Step 409 After the call is established, the calling terminal or the called terminal sends a session update request to the B2BUA unit connected thereto, and step 410 is performed.
  • Step 410 When each B2BUA unit determines that the session is in an inactive state, it releases the resources allocated by itself for the session.
  • the above steps 401 ⁇ 405 are the process of the refresher negotiation.
  • the node device can perform refresher negotiation according to its own situation and determine that it is a refresher.
  • the process of the refresher negotiation between the first B2BUA unit and the called terminal can be implemented in the following two manners.
  • the B2BUA unit adds a refresher parameter in the Session-Expires header field in the session establishment request message forwarded to the node device of the session establishment path, and sets the refresher refresher as the user agent client uac for indicating the present
  • the B2BUA unit is responsible for initiating a session update request to the called terminal; (2) After the called terminal receives the session establishment request message and determines that it is not the refresher, the node device returns a session establishment response message to the B2BUA that is not the refresher.
  • the B2BUA unit After receiving the session establishment response message, the B2BUA unit determines that it is a refresher, and adds a refresher parameter in the Session-Expires header field in the session establishment response message replied to the calling terminal, and sets the refresher to User agent server side uas.
  • the B2BUA unit sends the session establishment request message to the node device in the path establishment session, and the support header field with the timer tag is received. After receiving the session establishment request message, each node device forwards the message to the next node device. Until the called terminal;
  • the node device After the called terminal receives the session establishment request message, if it determines that it is a refresher, the node device returns a session establishment response message to the B2BUA, where the Session-Expires header field is uas, and if it is determined that it is not refreshed Then, the node device returns a session establishment response message to the B2BUA that is not the refresher.
  • the B2BUA unit After receiving the session establishment response message, the B2BUA unit determines whether the called terminal is a refresher, and if yes, performs step (4), otherwise, it uses itself as a refresher, and performs step (4);
  • the B2BUA unit adds a refresher parameter in the Session-Expires header field in the session establishment response message replied to the calling terminal, and sets the refresher to the user proxy server side uaS o
  • the refresher is B2BUA1, and the B2BUA1 initiates a session update request to the calling and called terminals.
  • Step 500 The calling terminal sends a session establishment request message to the B2BUA1 unit.
  • Step 501 The B2BUA1 unit receives the session establishment request message, and the UAS end of the B2BUA1 unit checks whether the message carries the supported:timer header field.
  • the Session Timers protocol The specific process of processing the message by the Session Timers protocol is as follows:
  • the value of the Min_SE header field in the message is increased to be equal to the value of the local Min_SE header field and used as the value of the Session-Expires header field.
  • the request is made. Insert the Min_SE header field into the message, which is the value of the local Min_SE header field, and treat the value as
  • the processing method is the same as in the prior art.
  • Step 502 The B2BUA1 unit sends the processed session establishment request message to the PROXY unit.
  • Step 503 The PROXY unit sends the received session establishment request message to the AS (B2BUA2) unit.
  • Step 504 The B2BUA2 unit receives the session establishment request message, and the UAS end of the B2BUA2 unit compares the value of the Session-Expires header i or the value of the local Min SE header i or. ⁇ The value of the Session-Expires header field is small, and the response to the B2BUA1 unit indicates that the session update interval is too short and the value of the local Min_SE header field is brought in the response. After the B2BUA1 receives the reply response, the Session-Expires header field is obtained. The value is changed to the value of the Min_SE header field and sent to the B2BUA2 unit.
  • the processing method is the same as in the prior art.
  • the UAC end of the B2BUA2 unit constructs a new request message according to the session establishment request message processed by the UAS.
  • Step 505 The B2BUA2 unit sends the processed session establishment request message to the called terminal.
  • Step 506 The called terminal sends a 200 response message indicating success to the B2BUA2 unit.
  • Step 507 The B2BUA2 unit receives the 200 response message, and the UAC end of the B2BUA2 unit does not start the session timeout release timer according to the value of the Session-Expires header field and the refresher parameter in the response message. Session update timer.
  • the UAS end of the B2BUA2 unit starts the session timeout release timer according to the value of the Session-Expires header field, and does not start the session update timer.
  • Step 508 The B2BUA2 unit sends a 200 response message sent by the called terminal to the PROXY unit.
  • the UAS end of the B2BUA1 unit starts the session timeout release timer and the session update timer according to the value of the Session-Expires header field.
  • Step 511 The B2BUA1 unit sends a 200 response message to the calling terminal. After the calling terminal receives the 200 response message, the session is successfully established and the Session Timers protocol is negotiated successfully.
  • Step 513 The calling terminal receives the session update request, and returns a 200 response message to the B2BUA1.
  • Step 516 The PROXY unit sends the received session update request to the AS (B2BUA2 unit).
  • the related processing of the session update message by the B2BUA2 unit is the same as in the prior art.
  • Step 518 The called terminal receives the session update request and replies to the B2BUA2 unit with a 200 response message.
  • Step 520 The B2BUA2 unit sends the received 200 response message to the PROXY unit.
  • Step 521 The PROXY unit sends the received 200 response message to the AS (B2BUA1 unit).
  • the refresher is the called terminal, and the called terminal initiates a session update request.
  • Step 5000 The calling terminal sends a session establishment request message to the B2BUA1 unit.
  • Step 5001 The B2BUA1 unit receives the session establishment request message, and the UAS end of the B2BUA1 unit checks whether the message carries the supported:timer header field.
  • the flow is skipped. Otherwise, the session is processed by the Session Timers protocol.
  • the steps for processing the Session Timers protocol include:
  • the value of the Session-Expires header field is less than the value of the local Min_SE header field, when the Min SE header field exists in the message, the value of the Min SE header field in the message is increased to the value of the local Min SE header field. And as the value of the Session-Expires header field, when there is no Min_SE header field in the message, insert the Min_SE header field in the request message, its value is the value of the local Min-SE header field, and the value is made The value for Session-Expires.
  • the processing method is the same as in the prior art.
  • the UAC end of the B2BUA1 unit inserts a supported:timer header field into the message according to the session establishment request message processed by the UAS, and constructs a new session establishment request message.
  • Step 5002 The B2BUA1 unit sends the processed session establishment request message to the PROXY unit.
  • Step 5004 The B2BUA2 unit receives the session establishment request message, and the UAS end of the B2BUA2 unit compares the value of the Session-Expires header i or the value of the local Min SE header i or. ⁇ The value of the Session-Expires header field is small, and the B2BUA1 unit is replied with a response indicating that the session update interval is too short and the value of the local Mm_SE header field is brought in the response. After the B2BUA1 receives the reply response, the Session-Expires header field is received. The value is changed to the value of the Min_SE header field and sent to the B2BUA2 unit.
  • the processing method is the same as in the prior art.
  • the UAC end of the B2BUA2 unit constructs a new session establishment request message according to the session establishment request message processed by the UAS.
  • Step 5005 The B2BUA2 unit sends the processed session establishment request message to the called terminal.
  • Step 5006: The called terminal sends a 200 response message indicating success to the B2BUA2 unit, and inserts a supported: timer header field in the response message, and sets the parameter refresher in the Session-Expires header field to refresher uas.
  • Step 5007 The B2BUA2 unit receives the 200 response message, and the UAC end of the B2BUA2 unit starts the session timeout release timer according to the value of the Session-Expires header field and the refresher parameter in the response message, and does not update the session timer.
  • the UAS end of the B2BUA2 unit does not start the session timeout release according to the value of the Session-Expires header field. Timer and session update timer.
  • Step 5008 The B2BUA2 unit sends a 200 response message sent by the called terminal to the PROXY unit.
  • Step 5009 The PROXY unit sends the received 200 response message to the AS (B2BUA1 unit).
  • the UAS end of the B2BUA1 unit does not start the session timeout release timer and the session update timer according to the value of the Session-Expires header field.
  • Step 5011 The B2BUA1 unit sends a 200 response message to the calling terminal. After the calling terminal receives the 200 response message, the session is successfully established and the Session Timers protocol is negotiated successfully.
  • Step 5013 After receiving the session update request, the B2BUA2 unit determines that the message includes a support:timer header field, performs related processing on the message, and sends the message to the PROXY unit.
  • the processing related to the session update request by the B2BUA2 unit is the same as in the prior art.
  • Step 5014 The PROXY unit sends the received session update request to the AS (B2BUA1 unit).
  • Step 5015 After receiving the session update request, the B2BUA1 unit determines that the message includes a support:timer header field, performs related processing on the message, and sends the message to the calling terminal.
  • the processing related to the session update request by the B2BUA1 unit is the same as in the prior art.
  • Step 5016 The calling terminal receives the session update message and replies to the B2BUA1 unit with a 200 response message.
  • Step 5018 The B2BUA1 unit sends the received 200 response message to the PROXY unit.
  • Step 5019 The PROXY unit sends the received 200 response message to the AS (B2BUA2 unit).
  • Step 5020 The B2BUA2 unit receives the 200 response message, and determines whether the session is active according to the rules of the proxy server. If the session is active, the session timeout release timer is refreshed; if it is inactive, the resources allocated for the session are directly released, and the connection is terminated.
  • Step 5021 The B2BUA2 unit sends the received 200 response message to the called terminal.
  • the called terminal After the called terminal receives the 200 response message, it determines whether the session is active according to the rules of the refresher. If the session is active, the session timeout release timer is refreshed, the Session Timers completes the session update, and the session update request is sent to the B2BUA2 unit after (SessionExpires / 2) seconds, until the entire session ends normally, and the Session Timers protection is terminated; If it is inactive, it sends a session release request to the B2BUA2 unit, and releases the resources allocated for the session. The connection is terminated. After receiving the request, the B2BUA2 unit releases the resources allocated for the session and requests the request. After being sent to the PROXY unit, the PROXY unit releases the resource allocated for the session and sends the request to the B2BUA1 unit. After receiving the request, the B2BUA1 unit releases the resource allocated for the session.
  • Step 600 The calling terminal sends a session establishment request message to the B2BUA1.
  • Step 601 The B2BUA1 unit receives the session establishment request message, and the UAS end of the B2BUA1 unit checks whether the message carries the supported:timer header field.
  • the steps for processing the Session Timers protocol include:
  • the B2BUA1 unit sends.
  • the processing method is The prior art is the same.
  • the UAC end of the B2BUA1 unit constructs a new session establishment request message according to the session establishment request message processed by the UAS.
  • Step 602 The B2BUA1 unit sends the processed session establishment request message to the PROXY unit.
  • Step 603 The PROXY unit sends the received session establishment request message to the AS (B2BUA2 unit).
  • Step 604 The B2BUA2 unit receives the session establishment request message.
  • the UAS end of the B2BUA2 unit checks the value of the Session-Expires header field. ⁇ The value of the Session-Expires header i or less is less than the value of the local Min_SE header field, and the B2BUA1 replies to the calling terminal with a response indicating that the session update interval is too short and brings the locally allowed Min_SE header field in the response. Value, after receiving the reply response, the calling terminal changes the value of the Session-Expires header field to the value of the Min_SE header field and resends it.
  • the processing method is the same as in the prior art.
  • the UAC end of the B2BUA2 unit constructs a new session establishment request message according to the session establishment request message processed by the UAS.
  • Step 605 The B2BUA2 unit sends a session establishment request message to the called terminal.
  • Step 606 The called terminal agrees to send a request message sent by the B2BUA2 unit, and sends a 200 response message indicating success to the B2BUA2 unit.
  • Step 607 The B2BUA2 unit receives the 200 response message, and the UAC end of the B2BUA2 unit does not start the session timeout release timer and the session update timer according to the value of the Session-Expires header field and the refresher parameter in the response message.
  • the UAS end of the B2BUA2 unit starts the session timeout release timer according to the value of the Session-Expires header field, and does not start the session update timer.
  • Step 608 The B2BUA2 unit sends a 200 response message sent by the called terminal to the PROXY unit.
  • the UAS end of the B2BUA1 unit starts the session timeout release timer according to the value of the Session-Expires header field, and does not start the session update timer.
  • Step 611 The B2BUA1 unit sends the 200 response message sent by the PROXY unit to the calling terminal. After the calling terminal receives the 200 response message, the session is successfully established and the Session Timers are also negotiated successfully.
  • Step 613 After receiving the session update request, the B2BUA1 unit determines that the message includes a support: timer header field, performs related processing on the message, and sends the message to the PROXY unit.
  • the processing related to the session update request by the B2BUA1 unit is the same as in the prior art.
  • Step 614 The PROXY unit sends the received session update request to the AS (B2BUA2 unit).
  • the processing related to the session update request by the B2BUA2 unit is the same as in the prior art.
  • Step 616 The called terminal receives the session update message and replies to the B2BUA2 unit with a 200 response message.
  • Step 618 The B2BUA2 unit sends the received 200 response message to the PROXY unit.
  • Step 619 The PROXY unit sends the received 200 response message to the AS (B2BUA1 unit).
  • Step 621 The B2BUA1 unit sends the received 200 response message to the calling terminal.
  • the calling terminal determines whether the session is active according to the rules of the refresher. If the session is active, the session timeout release timer is refreshed, the Session Timers completes the session update, and waits (SessionExpires / 2) seconds before sending a session update to the B2BUA1 unit. Request, until the entire session ends normally, the Session Timers protection is terminated; if it is inactive, it sends a session release request to the B2BUA1 unit, and releases the resources allocated for the session, and ends the connection. After receiving the request, the B2BUA1 unit receives the request. Release the resource allocated for the session and send the request to the PROXY unit. After receiving the request, the PROXY unit releases the resource allocated for the session and sends the request to the B2BUA2 unit. The B2BUA2 unit releases the request and then releases it. The resources that are themselves allocated for the session.
  • the embodiment shown in FIG. 6 is to issue a session update request by the calling terminal.
  • the parameter of the refresher is uac during the negotiation, and each B2BUA unit does not start the session update request timer, and does not generate new after receiving the session update request.
  • the session update request avoids the forwarding of redundant session update requests in FIGS. 1A and 1B, while solving the problem of message collision in FIG. 1B.
  • the embodiment shown in Fig. 7 is to issue a session update request by the called terminal.
  • the parameter of the refresher is uas during negotiation, but only in the direction of sending the request message with FIG.
  • the UAS starts the session timeout release timer. The other steps are the same.
  • Step 713 After receiving the session update request, the B2BUA2 unit determines that the message includes a support: timer header field, performs related processing on the message, and sends the message to the PROXY unit.
  • the processing related to the session update request by the B2BUA2 unit is the same as in the prior art.
  • Step 714 The PROXY unit sends the received session update request to the AS (B2BUA1 unit).
  • the processing related to the session update request by the B2BUA1 unit is the same as in the prior art.
  • Step 716 The calling terminal receives the session update message and returns a 200 response message to the B2BUA1 unit.
  • Step 718 The B2BUA1 unit sends the received 200 response message to the PROXY unit.
  • Step 719 The PROXY unit sends the received 200 response message to the AS (B2BUA2 unit).
  • Step 721 The B2BUA2 unit sends the received 200 response message to the called terminal.
  • the called terminal After the called terminal receives the 200 response message, it determines whether the session is active according to the rules of the refresher. If the session is active, the session timeout release timer is refreshed, the Session Timers completes the session update, and the session update request is sent to the B2BUA2 unit after (SessionExpires / 2) seconds, until the entire session ends normally, and the Session Timers protection is terminated; If it is inactive, it sends a session release request to the B2BUA2 unit, and releases the resources allocated for the session. The connection is terminated. After receiving the request, the B2BUA2 unit releases the resources allocated for the session and requests the request. After being sent to the PROXY unit, the PROXY unit releases the resource allocated for the session and sends the request to the B2BUA1 unit. After receiving the request, the B2BUA1 unit releases the resource allocated for the session.
  • the B2BUA device provided by the embodiment of the present invention includes: a session protocol determining module, a session update requesting module, and a refresher negotiation module.
  • the session protocol judging module is configured to: after receiving the session establishment request message, determine whether the received session establishment request message has a Supported header field with a timer tag, and if yes, directly forward the session establishment request message, otherwise, A Supported header field with a timer tag is added to the session establishment request message, and the session establishment request message is forwarded.
  • the refresher negotiation module is configured to perform a refresher negotiation with the node device to determine whether it is a refresher.
  • the session update request module is configured to, if it is determined that it is a refresher, initiate a session update request to the network node of the current session on both sides connected to itself after the session is established.
  • the B2BUA device may further include: a processing module, a forwarding module, and a resource release module.
  • the forwarding module is configured to: after receiving the session update request, when the session update request includes a Supported header field with a timer tag, send a session update to the next node device of the session path according to the received session update request.
  • the resource release module is configured to release the resource allocated for the session after the session is established, if it is determined that the session is inactive.
  • the refresher negotiation module may further include: an adding module and a receiving module.
  • the adding module is configured to add a session refresher parameter in the Session-Expires header field in the session establishment request message received by the session protocol determining module.
  • the receiving module is configured to determine, according to the received session establishment response message, whether it is a refresher, if the Supported header field with a timer tag in the session establishment response message determines that the self is not a refresher, if the session establishment response message does not The Supported header field of the timer tag determines that it is a refresher.

Landscapes

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

Abstract

L'invention concerne un procédé de mise à jour de ressources. Selon le procédé, une fois que l'unité B2BUA de l'agent utilisateur jumelé a reçu le message de demande d'établissement de session du champ d'en-tête supporté sans l'étiquette de temporisateur, le champ d'en-tête supporté avec l'étiquette de temporisateur est ajouté au message de la demande; le programme de mise à jour intervient entre le dispositif nodal, le programme informe le dispositif nodal par le biais duquel cette session n'initie par la demande de mise à jour de session à l'exception du programme de mise à jour; une fois la session établie, le procédé consiste à déterminer le dispositif nodal du programme de mise à jour distinctement, pour initier la demande de mise à jour de session du noeud nodal par le biais duquel la session est traitée, cette session se connecte d'elle même sur les deux côtés. Ce procédé permet de résoudre le problème de transfert de la demande de mis à jour sans intérêt pendant la session et le conflit de message, en permettant au terminal appelé et appelant de ne pas avoir à supporter le protocole des temporisateurs de session, et peut également mettre à jour la ressource. Un mode de réalisation concerne également un système permettant de procéder à la mise à jour de la ressource.
PCT/CN2007/002314 2006-08-28 2007-08-01 Procédé et système de mise à jour de ressources Ceased WO2008025216A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610111582.6 2006-08-28
CN200610111582A CN101137104B (zh) 2006-08-28 2006-08-28 一种实现资源释放的方法和系统

Publications (1)

Publication Number Publication Date
WO2008025216A1 true WO2008025216A1 (fr) 2008-03-06

Family

ID=39135494

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/002314 Ceased WO2008025216A1 (fr) 2006-08-28 2007-08-01 Procédé et système de mise à jour de ressources

Country Status (2)

Country Link
CN (1) CN101137104B (fr)
WO (1) WO2008025216A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103002593A (zh) * 2011-09-16 2013-03-27 普天信息技术研究院有限公司 一种通过终端背靠背实现基站间中继的方法和系统

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102131285B (zh) * 2010-12-28 2013-09-11 华为技术有限公司 一种注册方法和网络设备
CN103812762B (zh) * 2013-11-27 2017-12-01 大唐移动通信设备有限公司 一种发送即时消息的方法和系统
CN103685286A (zh) * 2013-12-18 2014-03-26 大唐移动通信设备有限公司 一种释放会话资源的方法和装置
CN104168283B (zh) * 2014-08-22 2017-10-31 中国联合网络通信集团有限公司 更新sip会话状态的方法及装置
CN105429812A (zh) * 2014-09-12 2016-03-23 中兴通讯股份有限公司 节点状态检测方法及装置
CN104468506A (zh) * 2014-10-28 2015-03-25 大唐移动通信设备有限公司 会话状态检测方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1528745A1 (fr) * 2003-10-30 2005-05-04 Hewlett-Packard Development Company, L.P. Procédé et dispostif de communication
GB2421156A (en) * 2004-12-10 2006-06-14 Ericsson Telefon Ab L M Maintaining session across network address/port translation firewall in the event of an address change with a session manager
US20060146798A1 (en) * 2005-01-06 2006-07-06 Cisco Technology, Inc. System and method for providing a recovery mode in a session initiation protocol (SIP) environment
US20060176805A1 (en) * 2005-02-08 2006-08-10 Michael Peters Method of providing fault tolerance in a sip based contact handling environment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1528745A1 (fr) * 2003-10-30 2005-05-04 Hewlett-Packard Development Company, L.P. Procédé et dispostif de communication
GB2421156A (en) * 2004-12-10 2006-06-14 Ericsson Telefon Ab L M Maintaining session across network address/port translation firewall in the event of an address change with a session manager
US20060146798A1 (en) * 2005-01-06 2006-07-06 Cisco Technology, Inc. System and method for providing a recovery mode in a session initiation protocol (SIP) environment
US20060176805A1 (en) * 2005-02-08 2006-08-10 Michael Peters Method of providing fault tolerance in a sip based contact handling environment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103002593A (zh) * 2011-09-16 2013-03-27 普天信息技术研究院有限公司 一种通过终端背靠背实现基站间中继的方法和系统

Also Published As

Publication number Publication date
CN101137104A (zh) 2008-03-05
CN101137104B (zh) 2010-05-12

Similar Documents

Publication Publication Date Title
JP5606074B2 (ja) 通信ネットワークにおける動的サービストリガ
CN101855890A (zh) 在ims中合并通信会话的方法、设备和程序产品
US20130080648A1 (en) Session initiation from application servers in an ip multimedia subsystem
JP2008503910A (ja) 端末の機能変更をネットワークに通知する方法
EP1733505A1 (fr) Systeme et procede permettant de mettre en oeuvre des politiques portant sur la messagerie en mode session
JP2014511072A (ja) Ｓｉｐを用いた企業ネットワークの生存性のためのバックアップｓｉｐサーバ
US20080250466A1 (en) Method, system and apparatus for video sharing
WO2007090347A1 (fr) Procédé, système et dispositif d'acheminement pour service de système multimédia ip
WO2008025216A1 (fr) Procédé et système de mise à jour de ressources
WO2011017889A1 (fr) Procédé et système de mise en œuvre de conférence multimédia
WO2010069176A1 (fr) Procédé de convocation d'une conférence lorsque des terminaux matériels ont été rattachés à des clients pc, à un serveur d'ouverture de session de ceux-ci, à un serveur de conférence de ceux-ci et à un client pc de ceux-ci
CN101030964B (zh) 会话控制装置和方法
WO2008000134A1 (fr) Méthode et dispositif de transmission d'un message de demande dans un système multimédia
CN101399768B (zh) 一种策略控制方法、装置及系统
WO2008011790A1 (fr) Procédé, système et appareil de réseau permettant d'établir une session
WO2011018017A1 (fr) Procédé et dispositif de gestion de session, et système de communication
EP2230814B1 (fr) Procédé pour réaliser une mise en attente
WO2008110110A1 (fr) Procédé et système de fourniture de service de sous-système multimédia ip
WO2008080297A1 (fr) Procédé, équipement et système pour mettre en rapport une session
EP1709777B1 (fr) Signalisation de protocole d'ouverture de session
EP2200254B1 (fr) Système de réseau mobile et procédé de fourniture de message de guidage
US9258367B2 (en) Technique for managing sessions with entities in a communication network
JP2010525623A (ja) 通信ネットワークにおいて使用する方法、および、装置
WO2007085199A1 (fr) Procédé, application et appareil permettant d'identifier l'état utilisateur dans des réseaux
WO2007095814A1 (fr) Procédé et système d'obtention de la capacité de session du participant à une session dans un système de communication multipartie

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: 07785228

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07785228

Country of ref document: EP

Kind code of ref document: A1