WO2012109953A1 - Procédé et système pour la protection d'une session sip - Google Patents

Procédé et système pour la protection d'une session sip Download PDF

Info

Publication number
WO2012109953A1
WO2012109953A1 PCT/CN2012/070502 CN2012070502W WO2012109953A1 WO 2012109953 A1 WO2012109953 A1 WO 2012109953A1 CN 2012070502 W CN2012070502 W CN 2012070502W WO 2012109953 A1 WO2012109953 A1 WO 2012109953A1
Authority
WO
WIPO (PCT)
Prior art keywords
sip
entity
sip entity
session
standby
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/CN2012/070502
Other languages
English (en)
Chinese (zh)
Inventor
郝振武
彭永林
陶全军
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2012109953A1 publication Critical patent/WO2012109953A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1094—Inter-user-equipment sessions transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to the field of SIP (Session Initiation Protocol) and its service processing and communication, and in particular to a SIP session protection method and system.
  • SIP Session Initiation Protocol
  • SIP is an application layer signaling control protocol used to create, modify, and release sessions for one or more participants. These sessions can be Internet multimedia conferencing, IP (Internet Protocol) telephony or multimedia distribution.
  • the SIP protocol is widely used in Softswitch (Softswitch) and IMS (IP Multimedia Subsystem).
  • Softswitch Softswitch
  • IMS IP Multimedia Subsystem
  • a single node uses a normal PC (Personal Computer) or even a user-side device. Its single node capacity is small, and its reliability and stability are relatively low. When these nodes fail, even when they leave the service, the service user's ongoing SIP call is interrupted, which increases call loss and reduces overall network availability. Therefore, the user's session needs to be protected to ensure high reliability and high availability of the network.
  • P2P Peer to Peer
  • PC Personal Computer
  • URI Uniform Resource Identifier
  • U User Agent
  • SIP Proxy an intermediate entity that performs message routing and guarantee policy enforcement
  • Registrar (registration server), receives the registration request, and puts the information into the Location Service Server (location server);
  • Location Service Server A location server that is a database that stores user binding information (SIP URI and location mapping).
  • Figure 2 is a way to implement the registration process, including:
  • Step 201 The UA discovers that the access point is a SIP Proxy.
  • Step 202 The UA sends a registration message Register to the SIP Proxy, and its contact address (contact) carries its own address in the header field;
  • Step 203 The SIP Proxy inserts its own address in the path (head) header field, and then sends a Register message to the Registrar;
  • Step 204 After receiving the Register message, the Registrar obtains and saves the contact address of the user and the address of the SIP Proxy from the contact header field and the path header field, and then returns a 200 OK response message to the SIP Proxy, and the service in the 200 OK response message.
  • -route service routing
  • the header field carries the Registrar's own address
  • Step 205 After receiving the 200 OK response message, the SIP Proxy obtains and saves the address of the Registrar from the service-route header field, and then forwards the 200 OK response message to the UA, and the UA also obtains the service-route header field. And save the address of Registrar.
  • the UA, the SIP Proxy, and the Registrar establish their own route sets, which are used for message routing in the subsequent session establishment process.
  • the UA establishes a route set (SIP Proxy, Registrar).
  • the path expected by the session is UA-->SIP Proxy ⁇ >Registrar, so the UA first sends the session establishment request to the SIP Proxy, and the SIP Proxy further saves the path according to the path specified in the session.
  • the path information sends a call setup request to the Registrar.
  • the Registrar obtains the UA's route set (SIP Proxy, UA).
  • the Registrar first sends a call setup request to the SIP Proxy, which is then sent by the SIP Proxy to the UA.
  • FIG. 3 is a session establishment process implemented by the foregoing solution, and shows a process in which the UA-A calls the UA-B.
  • Step 301 The UA-A sends a session establishment request Invite message to the SIP Proxy-1, and the contact address (header) carries its own address information, and carries the route set acquired in the registration process in the route header field;
  • Step 302 The SIP Proxy-1 sends an Invite message to the SIP Proxy-2 according to the indication in the routing header field or the locally saved routing information, and adds its own address information in the header field of the record-route field. ;
  • Step 303 After receiving the Invite message, the SIP Proxy-2 adds its own address information in the record-route header field, and then forwards the Invite message to the UA-B.
  • Step 304 After receiving the Invite message, the UA-B returns a ringing response message 180 ringing to the SIP Proxy-2, and carries its own address in the contact header field of the response message. At the same time, the record-route header field in the Invite request is copied into the response message;
  • Steps 305 ⁇ 306 SIP Proxy-2 forwards the received ringing response message to the UA-A via SIP Proxy-1;
  • Steps 307 ⁇ 309 The UA-B returns a 200 OK response message to the UA-A via the SIP Proxy-2 and the SIP Proxy-1, and the record-route header field information of the response message is the same as the record-route header field in steps 304-306. information.
  • each node on the path establishes a route set for the session.
  • the route set of this session is (UA-A, SIP Proxy-1, SIP Proxy-2, UA-B), when UA -A
  • the path indicating the message is displayed in the session, and the path is transmitted.
  • the intra-session message sent from the UA-B is similar.
  • Step 401 The UA-A has established a SIP session with the UA-B through the SIP Proxy-1 and the SIP Proxy-2, and the specific establishment process is as shown in FIG. 3; Step 402: During the SIP session, SIP Proxy- 1 An abnormality has occurred and the service cannot be continued; Step 403: The UA-A fails to send the SIP session message to the SIP Proxy-1.
  • Step 404 This session is forced to be interrupted.
  • the technical problem to be solved by the present invention is to overcome the deficiencies of the prior art and provide a general SIP session protection method and system to overcome the problem of ongoing session interruption when the SIP network element exits the service in the current network. .
  • the present invention provides a session initiation protocol session protection method, which includes:
  • the primary session initiation protocol (SIP) entity selects a backup SIP entity for the SIP session to be protected, backs up the related data of the SIP session to be protected to the standby SIP entity, and notifies the address information of the standby SIP entity. It is adjacent to the SIP entity;
  • SIP session initiation protocol
  • the standby SIP entity When the standby SIP entity receives the session request message, it processes the related session message instead of the primary SIP entity.
  • the foregoing method may further have the following feature: the step that the primary SIP entity notifies the neighboring SIP entity of the address information of the standby SIP entity includes: the primary SIP entity in the SIP session to be protected In the route set construction process, the address information of the standby SIP entity is notified to the neighboring SIP entity, and in the process of constructing the route set, the neighboring SIP entity is informed that it has the capability of supporting session protection.
  • the route set construction process includes one or a combination of the following: a boundary SIP entity discovery process, a SIP registration process, and a SIP session establishment process.
  • the foregoing method may further have the following feature: when the route set construction process is a border SIP entity discovery process, the primary SIP entity notifies the neighboring SIP entity of the address information of the standby SIP entity by: The address information of the border SIP entity carries the SIP session guarantee The support capability and the address information of the standby SIP entity.
  • the foregoing method may further have the following feature: when the route set construction process is a SIP registration process, the primary SIP entity notifies the neighboring SIP entity of the address information of the standby SIP entity by: The (Contact) header field, or the path (head) header field, or the service-route header field carries the SIP session protection support capability and the address information of the alternate SIP entity.
  • the foregoing method may further have the following feature: when the routing set construction process is a SIP session establishment process, the primary SIP entity notifies the neighboring SIP entity of the address information of the standby SIP entity by: The header field, or the record-route header field, carries the SIP session protection support capability and the address information of the alternate SIP entity.
  • the foregoing method may further have the following feature: the neighboring SIP entity finds whether the primary SIP entity can provide a service by: performing a keepalive between the adjacent SIP entity and the primary SIP entity. a mechanism, the neighboring entity sends a request message to the active SIP entity, does not receive a response message after a set time, the primary SIP entity or the standby SIP entity actively notifies the neighboring SIP entity, and the neighboring SIP entity The three-party server queries whether the primary SIP entity can provide the service.
  • the foregoing method may further have the following features, the method further comprising: when the next hop SIP entity of the standby SIP entity receives the session request message of the standby SIP entity, first authenticating the standby SIP entity The session request message continues to be processed when the authentication is passed.
  • the invention also provides a session initial protocol session protection system, including a primary session initial protocol.
  • SIP Session SIP entity, adjacency SIP entity and alternate SIP entity, where:
  • the primary SIP entity is configured to: select a standby SIP entity for the SIP session to be protected, back up the related data of the SIP session to be protected to the standby SIP entity, and inform the neighboring SIP entity of the address information of the standby SIP entity.
  • SIP entity ;
  • the contiguous SIP entity is configured to: when the session request message is sent to the active SIP entity, if the primary SIP entity is found to be unable to provide a service, send the session request message to the standby SIP entity;
  • the SIP entity is set to: when the session request message is received, instead of the primary use
  • the SIP entity processes related session messages.
  • the foregoing system may further have the following feature: the primary SIP entity is configured to: notify the neighboring SIP entity of the address information of the standby SIP entity in the routing set construction process of the SIP session to be protected. And, in the routing set construction process, informing the neighboring SIP entity that it has the ability to support session protection.
  • the route set construction process includes one or a combination of the following: a boundary SIP entity discovery process, a SIP registration process, and a SIP session establishment process.
  • the foregoing system may further have the following feature: the primary SIP entity is configured to: carry the SIP session protection support capability and the standby SIP entity in the address information of the border SIP entity in the border SIP entity discovery process. Address information.
  • the primary SIP entity is set to: in the SIP registration process, in the contact address (Contact) header field, or the path (path) header field, or the service route (service- The route) header field carries the SIP session protection support capability and the address information of the standby SIP entity.
  • the above system may also have the following features, the primary SIP entity is set to:
  • the SIP header protection support capability and the address information of the standby SIP entity are carried in the Contact header field or the record-route header field.
  • the contiguous SIP entity is configured to: discover whether the primary SIP entity can provide a service by: one of a neighboring SIP entity and the primary SIP entity Performing a keep-alive mechanism, the neighboring entity sends a request message to the primary SIP entity, and the response message is not received, the primary SIP entity or the standby SIP entity actively notifies the adjacent SIP entity, The adjoining SIP entity queries the third party server whether the primary SIP entity can provide the service.
  • the system may further have the following feature, the system further includes a next hop SIP entity of the standby SIP entity, where the next hop SIP entity is set to: when receiving the session request message of the standby SIP entity First, the standby SIP entity is authenticated, and the session request message sent by the standby SIP entity is continued to be processed when the authentication succeeds.
  • the system further includes a next hop SIP entity of the standby SIP entity, where the next hop SIP entity is set to: when receiving the session request message of the standby SIP entity First, the standby SIP entity is authenticated, and the session request message sent by the standby SIP entity is continued to be processed when the authentication succeeds.
  • a Session Initiation Protocol (SIP) entity including an active SIP entity, adjacency SIP entity and alternate SIP entity, where:
  • the primary SIP entity is configured to: select a backup SIP entity for the SIP session to be protected, back up the related data of the SIP session to be protected to the standby SIP entity, and notify the address information of the standby SIP entity Adjacent SIP entity;
  • the contiguous SIP entity is configured to: when the session request message is sent to the active SIP entity, if the primary SIP entity is found to be unable to provide a service, send the session request message to the standby SIP entity;
  • the SIP entity is configured to: when the session request message is received, process the related session message instead of the primary SIP entity.
  • the primary SIP entity is configured to: notify the neighboring SIP entity of the address information of the standby SIP entity, and the routing set in the routing set construction process of the SIP session to be protected. During the construction process, the neighboring SIP entity is informed that it has the ability to support session protection.
  • the route set construction process includes one or a combination of the following: a boundary SIP entity discovery process, a SIP registration process, and a SIP session establishment process.
  • the primary SIP entity is configured to: carry the SIP session protection support capability and the address information of the standby SIP entity in the address information of the border SIP entity in the border SIP entity discovery process.
  • the primary SIP entity is configured to: in a SIP registration process, a contact domain (Contact) header field, or a path (head) header field, or a service-route header field carrying SIP session protection Support capability and address information of the alternate SIP entity.
  • Contact contact domain
  • head path
  • service-route header field carrying SIP session protection Support capability and address information of the alternate SIP entity.
  • the primary SIP entity is configured to: in a Contact header field, or a record-route header field, carry SIP session protection support capability and address information of the standby SIP entity in a SIP session establishment process. .
  • the adjacency SIP entity is configured to: discover the primary use by one of the following manners
  • the SIP entity can provide a service: a keep-alive mechanism is performed between the adjacency SIP entity and the active SIP entity, and the neighboring entity does not receive a response message after sending the request message to the active SIP entity for more than a set time. And the primary SIP entity or the standby SIP entity actively notifies the adjacent SIP entity, The contiguous SIP entity queries a third party server to query whether the primary SIP entity can provide a service.
  • the SIP entity further includes a next hop SIP entity, and the next hop SIP entity is configured to: when receiving the session request message of the standby SIP entity, first perform authentication on the standby SIP entity, and the authentication is passed. The session request message sent by the standby SIP entity continues to be processed.
  • the standby SIP entity can provide the service support instead of the primary SIP entity, thereby achieving the purpose of uninterrupted SIP conference service.
  • Figure 1 is a schematic diagram of a SIP network application model
  • Figure 2 is a way of implementing the registration process
  • Figure 3 is a way to implement a session establishment process
  • Figure 4 is a flow of session interruption that occurs in one mode
  • FIG. 5 is a schematic diagram of a method for implementing session protection through a registration process according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a method for implementing session protection through a session establishment process according to an embodiment of the present invention
  • FIG. 7 is a flowchart of implementing session protection information interaction through a registration process implemented by an embodiment of the present invention.
  • FIG. 8 is a flowchart of implementing session protection information interaction through a session establishment process according to an embodiment of the present invention.
  • FIG. 10 is a second flowchart of a session protection implementation implemented by an embodiment of the present invention.
  • the core idea of the present invention is that a SIP entity supporting session protection informs other SIP entities on the session routing path to support session protection by itself. If the primary SIP entity has a backup SIP entity, Informing the neighboring SIP entity of the address of the standby SIP entity, etc., so that when the primary SIP entity cannot provide the service, the standby SIP entity can replace the primary SIP entity for subsequent SIP service processing, and A SIP message corresponding to the interaction with the associated SIP entity.
  • the present invention provides a SIP session protection method, including:
  • the primary SIP entity selects a backup SIP entity for the SIP session to be protected, and backs up the SIP session related data to be protected to the standby SIP entity; during the session, when the session state changes, the session related data is backed up. To the alternate SIP entity.
  • the primary SIP entity informs the neighboring SIP entity in the routing set that it has the capability of supporting session protection and the address information of the selected standby SIP entity.
  • the primary SIP entity selects one or more standby SIP entities according to a locally configured backup node policy or a selection algorithm.
  • the multiple standby SIP entities may be sorted or the priority information may be added.
  • the neighboring SIP entity selects a standby SIP entity according to the sorting or priority, and sends a session request message to the standby SIP entity.
  • the route set construction process includes one or a combination of the following: a boundary SIP entity discovery process, a SIP registration process, and a SIP session establishment process.
  • step B if the adjacent SIP entity in the route set supports the SIP session protection mechanism, it needs to inform the primary SIP entity to support the SIP protection mechanism, and if it also has the backup SIP entity, further inform the primary SIP entity of the adjacent SIP entity.
  • the address information of the alternate SIP entity That is, any primary SIP entity in the SIP session routing path, if there is a backup SIP entity, informs the neighboring SIP entity of its own standby SIP address information.
  • step B if the route set construction process is a border SIP entity discovery process, the SIP session protection support capability and the backup SIP entity location need to be carried in the address information of the border SIP entity. Address information.
  • step B if the route set construction process is a SIP registration process, the primary SIP entity and/or the neighboring SIP entity use a Contact header field, or a Path header field, or Service- according to its location in the route set.
  • the Route header field carries SIP session protection support capabilities and/or alternate SIP entity address information.
  • step B if the route set construction process is a SIP session establishment process, the primary SIP entity and/or the neighboring SIP entity are carried according to their location in the route set, using a Contact header field, or a record-route header field. SIP session protection support capability and/or alternate SIP entity address information.
  • the SIP entity discovers that the route set neighboring SIP entity cannot provide the service, and may include a keep-alive mechanism, a request no response, a primary SIP entity or a standby SIP entity, and a third-party server query mode.
  • the keep-alive mechanism refers to: performing a keep-alive mechanism between the neighboring SIP entity and the active SIP entity;
  • Requesting no response means: after the neighboring entity sends a request message to the active SIP entity, the response message is not received after the set time;
  • the primary SIP entity or the standby SIP entity actively notifies that: the primary SIP entity actively informs that the neighboring SIP entity will no longer provide the service, but the standby SIP entity provides the service, or the standby SIP entity actively notifies the adjacent SIP entity to actively use the primary SIP entity.
  • the SIP entity will no longer provide the service, but will take over the service;
  • the third-party server query refers to: The third-party server collects the running status of the SIP entity, and the neighboring SIP entity queries the third-party server whether the primary SIP entity can provide the service.
  • step C the SIP entity generates a route header field by using the address of the standby SIP entity obtained in the route set construction process, and sends the session request to the standby SIP entity specified by the route header field according to the route header field.
  • the session request message includes an initial session establishment request message and a transaction request message in the session.
  • the standby SIP entity receives the session request message of the last hop SIP entity, After processing the session request message, if the next hop SIP entity needs to forward the session request message, the next hop SIP entity needs to allow the session request message sent by the standby SIP entity to be obtained through the path construction process.
  • the address information of the alternate SIP entity authenticates the request and protects security. Specifically, when receiving the session request message of the standby SIP entity, the next hop SIP entity of the standby SIP entity first authenticates the standby SIP entity, and continues to process the session request message when the authentication succeeds.
  • the authentication method is: judging the standby of sending the session request message
  • FIG. 5 is a schematic diagram of a method for implementing session protection through a registration process implemented by the present invention. The specific principles are as follows:
  • Network element SIP Proxy-l selects SIP Proxy-2 as its own backup SIP entity according to certain policies.
  • UA-A informs SIP Proxy-1 that it supports session protection.
  • SIP Proxy-l informs Registrar of its own support for session protection and the address of its own SIP entity SIP Proxy-2.
  • Registrar-A tells SIP Proxy-l or UA-A to support session protection.
  • SIP Proxy-l informs UA-A of its own support for session protection and the address of its own SIP entity SIP Proxy-2.
  • the UA-A or Registrar sends a session message, if it is aware that the target primary network element SIP Proxy-l of the route next hop cannot provide the service, it sends a session message to the SIP proxy X1 of the SIP Proxy-1. .
  • the method for discovering the target primary network element of the next hop SIP Proxy-l cannot provide services may include keep-alive mechanism, request no response, active notification by the active node or standby node, and third-party server query mode.
  • the standby SIP entity SIP Proxy-2 replaces the primary SIP entity SIP Proxy-1 to process the corresponding session message.
  • each SIP entity obtains the session keep-alive support information of the related SIP entity in the process of registration. If the primary SIP entity fails to provide the service in the subsequent process, the backup entity can replace the subsequent service. , thus ensuring the stability of the business.
  • Method for implementing session protection through session establishment process
  • FIG. 6 is a schematic diagram of a method for implementing session protection through a session establishment process. The specific principles are as follows:
  • the network element SIP Proxy-1 selects SIP Proxy-2 as its own backup SIP entity according to a certain policy.
  • the network element SIP Proxy-3 selects SIP Proxy-4 as its own backup SIP entity according to a certain policy, and the network element UA- 1 Select UA-2 as its own backup SIP entity according to certain policies.
  • UA-A informs SIP Proxy-1 that it supports session protection.
  • SIP Proxy-1 informs SIP Proxy-3 that it supports session protection and its own SIP entity SIP Proxy-2.
  • SIP Proxy-3 tells UA-1 to support session protection and the address of its own alternate SIP entity SIP Proxy-4.
  • UA-1 informs SIP Proxy-3 that it supports session protection and the address of its own alternate SIP entity UA-2.
  • SIP Proxy-3 informs SIP Proxy-1 that it supports session protection and its own SIP entity SIP.
  • Information such as the address of Proxy-4, SIP Proxy-1 tells UA-A to support session protection and the address of its own SIP entity SIP Proxy-2.
  • the SIP entity is the standby SIP entity SIP Proxy-2 of the target primary network element.
  • the method for discovering that the target primary network element of the next hop cannot provide the service may include a keep-alive mechanism, a request no response, an active notification by the active node or the standby node, and a third-party server query manner.
  • the standby SIP entity SIP Proxy-2 or SIP Proxy-4 or UA-2 replaces the primary network element to process the corresponding session message.
  • each SIP entity obtains the session keep-alive support information of the related SIP entity in the process of session establishment, and if the main SIP entity fails to provide the service in the subsequent process, The standby entity can replace the subsequent services to ensure the stability of the service.
  • each SIP entity needs to inform and learn about other SIP entities about SIP session protection during the routing process of the registration message.
  • the specific process is shown in Figure 7:
  • Step 701 If the SIP Proxy-1 supports session protection, the SIP session protection support capability identifier and the backup SIP entity address information are added to the SIP Proxy-1 host name or address, and the SIP session protection support capability identifier can be set according to requirements.
  • the sp parameter is used as the SIP session protection support capability identifier, indicating that SIP Proxy-1 supports session protection. In this way, when the UA discovers the outbound (Boundary) SIP Proxy by using the packet protocol discovery process or the dynamic address configuration protocol, it can know whether the SIP Proxy supports session protection according to the session protection support capability identifier carried in the SIP Proxy host name or address;
  • Step 702 The UA-A carries the identifier sp in the contact header field that sends the Register message to the SIP Proxy-1, indicating that it supports session protection. In this way, after receiving the Register request, the SIP Proxy-1 can know that the UA-A supports session protection.
  • Step 703 The SIP Proxy-1 carries the identifier sp in the path header field of the Register message sent to the Registrar, indicating that it supports session protection and carries the address information of its own SIP entity SIP Proxy-2. In this way, the Registrar can know that SIP Proxy-1 supports session protection after receiving the Register request, and knows that its standby SIP entity is SIP Proxy-2;
  • Step 704 After receiving the Register request, the Registrar returns a response message to the SIP Proxy-1, and carries the identifier sp in the service-route header field of the response message, indicating that the session protection is supported. In this way, SIP Proxy-1 can know that Registrar supports session protection after receiving the response message.
  • Step 705 After receiving the response message, the SIP Proxy-l may further add an identifier sp in the service-route header field of the response message, indicating that it supports session protection, and increases the address of its own standby SIP entity SIP Proxy-2. Information, then forward it to UA-A. After receiving the response message, the UA-A can know that SIP Proxy-1 supports session protection and knows that its standby SIP entity is SIP Proxy-2.
  • Step 706 The SIP Proxy-1 backs up the registration data of the UA-A to its own standby SIP entity SIP Proxy-2. In this way, each SIP entity knows each other that the related entity supports the session protection and the address information of the standby entity.
  • the primary task of implementing session protection through the session establishment process is to interactively protect information so that each SIP entity informs and learns about other SIP entities' information about SIP session protection during the routing process of session establishment messages.
  • the specific process is shown in Figure 8:
  • Step 801 The UA-A carries the identifier sp in the contact header field that sends the Invite message to the SIP Proxy-1, indicating that it supports session protection. After receiving the Invite request, SIP Proxy-1 can know that UA-A supports session protection.
  • Step 802 The SIP Proxy-1 carries the identifier sp in the record-route header field of the Invite message sent to the SIP Proxy-3, indicating that it supports session protection and carries the address information of its own SIP entity SIP Proxy-2. After receiving the Invite request, SIP Proxy-3 knows that SIP Proxy-1 supports session protection and knows that its standby SIP entity is SIP Proxy-2.
  • Step 803 The SIP Proxy-3 adds the identifier sp in the record-route header field of the received Invite message, indicating that it supports session protection and carries the address information of its own SIP entity SIP Proxy-4.
  • the Invite message is then forwarded to UA-1. After receiving the Invite request, the UA-1 can know that SIP Proxy-3 supports session protection, and its standby SIP entity is SIP Proxy-4;
  • Step 804 After receiving the Invite request, the UA-1 returns a ringing response message to the SIP Proxy-3, and carries the identifier sp in the contact header field of the ringing response message, indicating that it supports session protection and carries its own standby SIP. Address information of the entity UA-2. At the same time, the record-route header field in the Invite request is copied to the ringing response message. In this way, SIP Proxy-3 can know that UA-1 supports session protection, and its standby SIP entity is UA-2;
  • Steps 805 ⁇ 806 The SIP Proxy-3 forwards the received ringing response message to the UA-A via the SIP Proxy-1.
  • SIP Proxy-1 and UA-A can know that SIP Proxy-3 and SIP Proxy-1 support session protection, and their standby SIP entities are SIP Proxy-4 and SIP Proxy-2, respectively;
  • Steps 807a ⁇ 807c SIP Proxy-1, SIP Proxy-3, UA-1 back up session data to their own backup SIP entities SIP Proxy-2, SIP Proxy-4, UA-2 respectively;
  • Steps 808 ⁇ 810 UA-1 returns 200 OK to UA-A via SIP Proxy-3 and SIP Proxy-1
  • the header field of the response message is the same as 804 ⁇ 806.
  • SIP Proxy-3, SIP Proxy-1, and UA-A can know that UA-1, SIP Proxy-3, and SIP Proxy-1 support session protection, and corresponding standby SIP entities UA-2 and SIP Proxy-4. Address information of SIP Proxy-2;
  • Step 81 la ⁇ 81 lc SIP Proxy-1, SIP Proxy-3, and UA-1 respectively back up session data to their own backup entities SIP Proxy-2, SIP Proxy-4, and UA-2.
  • each SIP entity knows each other that the related entity supports the session protection and the address information of the alternate entity.
  • Step 901 The UA-A establishes a SIP session with the UA-1 through the SIP Proxy-1 and the SIP Proxy-3.
  • Step 902 During the progress of the SIP session, the SIP Proxy-1 has an abnormality and cannot continue to provide the service;
  • Step 903 After the UA-A learns that the SIP Proxy-l is abnormal, select the SIP Proxy-2 of the SIP Proxy-1 obtained in the route set construction process;
  • SIP Proxy-1 cannot provide services by means of keep-alive mechanism, request no response, active notification by active node or standby node, and third-party server query.
  • Step 904 The UA-A redirects the SIP request message originally sent to the SIP Proxy-1 to the SIP.
  • Step 905 After receiving the request message, the SIP Proxy-2 performs related service processing, and forwards the request message to the SIP Proxy-3, and adds its own address in the via field.
  • Steps 906-907 After the SIP Proxy-3 receives the request message sent by the standby SIP entity SIP Proxy-2, it compares with the standby SIP entity obtained during the registration or session establishment process, and if it is consistent, the SIP Proxy-2 is considered to be legal. , forward the request message to UA-1;
  • Steps 908 ⁇ 910 After receiving the request message, the UA-1 processes the message, and then returns a corresponding SIP response to the UA-A via the SIP Proxy-3 and the SIP Proxy-2. In this way, the system can continue to provide the SIP session service instead of the SIP Proxy-2 in the case of the SIP Proxy-1 exception, thereby avoiding the SIP session interruption caused by partial entity anomalies.
  • a session establishment request such as SIP Invite, can be secured at this time.
  • Step A01 UA-A is successfully registered through SIP Proxy-1 and Registrar, SIP Proxy-1 selects SIP Proxy-2 as the standby entity, and notifies UA-A and Registrar/SIP Proxy-3;
  • Step A02 When the SIP session is established, the SIP Proxy-1 has an abnormality and cannot continue to provide services.
  • Step A03 After the SIP Proxy-1 is abnormal, the UA-A selects the SIP Proxy-2, which is the standby entity of the SIP Proxy-1 obtained during the route set construction process;
  • SIP Proxy-1 cannot provide services by means of keep-alive mechanism, request no response, active notification by active node or standby node, and third-party server query.
  • Step A04 The UA-A redirects the Invite request message originally sent to the SIP Proxy-1 to the SIP Proxy-2, and the address of the SIP Proxy-2 is filled in the first route header field of the Invite request message;
  • Step A05 After receiving the Invite request message, the SIP Proxy-2 performs related service processing, and forwards the Invite request message to the SIP Proxy-3, and adds its own address in the via header field.
  • Steps A06 ⁇ A07 After the SIP Proxy-3 receives the Invite request message sent by the standby SIP entity SIP Proxy-2, it compares with the standby SIP entity obtained during the registration process. If the SIP Proxy-2 is consistent, the SIP Proxy-2 is considered to be legal. Invite request message is forwarded to UA-1;
  • Steps A08 ⁇ A10 The UA-1 receives the Invite request message and processes it, and then returns the corresponding SIP response to the UA-A via SIP Proxy-3 and SIP Proxy-2.
  • the session routing set is also constructed during the call process described in FIG.
  • Each node on the path, and thus the path, can establish a route set containing session protection information so that the process in the session can be protected using the process of Figure 9.
  • the system can continue to provide SIP session service instead of SIP Proxy-2 in the case of SIP Proxy-1 exception, thereby avoiding SIP session interruption caused by partial entity anomalies.
  • the present invention provides a session initiation protocol session protection system, including a primary session initiation protocol (SIP) entity, a neighboring SIP entity, and a standby SIP entity, where:
  • SIP session initiation protocol
  • the primary SIP entity is configured to: select a backup SIP entity for the SIP session to be protected, back up related data of the SIP session to be protected to the standby SIP entity, and notify the neighboring SIP entity of the address information of the standby SIP entity SIP entity;
  • the adjacency SIP entity is configured to: when the session request message is sent to the active SIP entity, if the primary SIP entity is unable to provide a service, send the session request message to the standby SIP entity;
  • the standby SIP entity is configured to: when the session request message is received, process the related session message instead of the primary SIP entity.
  • the primary SIP entity is configured to: in the process of constructing the route set of the SIP session to be protected, notify the neighboring SIP entity of the address information of the standby SIP entity, and in the process of constructing the route set The neighboring SIP entity is informed that it has the ability to support session protection.
  • the routing set construction process includes one or a combination of the following: a boundary SIP entity discovery process, a SIP registration process, and a session establishment process.
  • the primary SIP entity is configured to: carry the SIP session protection support capability and the address information of the standby SIP entity in the address information of the border SIP entity in the border SIP entity discovery process.
  • the primary SIP entity is used to: carry a SIP session protection support in a contact address (Contact) header field, or a path (head) header field, or a service-route header field in a SIP registration process. Capability and address information of the alternate SIP entity.
  • the primary SIP entity is used to: in the SIP session establishment process, in the Contact header
  • the domain, or record-route header field carries SIP session protection support capabilities and address information of the alternate SIP entity.
  • the contiguous SIP entity is configured to discover whether the primary SIP entity can provide a service by using one of the following manners: performing a keep-alive mechanism between the contiguous SIP entity and the primary SIP entity, and the neighboring entity After the request message is sent to the active SIP entity, there is no response message, the primary SIP entity or the standby SIP entity actively notifies the neighboring SIP entity, and the neighboring SIP entity queries the third party server whether the primary SIP entity can provide service.
  • the system further includes a next hop SIP entity of the standby SIP entity, where the next hop SIP entity is configured to: when receiving the session request message of the standby SIP entity, first perform the standby SIP entity Authentication, the session request message sent by the standby SIP entity continues to be processed when the authentication is passed.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention se rapporte à un procédé et à un système pour la protection d'une session de protocole d'ouverture de session. Le procédé selon l'invention comprend les étapes suivantes : une entité primaire de protocole d'ouverture de session (SIP, Session Initiation Protocol) sélectionne une entité SIP de secours pour une session SIP devant être protégée ; elle sauvegarde les données associées à la session SIP devant être protégée dans l'entité SIP de secours ; et elle communique à une entité SIP adjacente des informations d'adresse relatives à l'entité SIP de secours ; quand un message de demande d'ouverture de session est envoyé à l'entité SIP primaire, s'il est déterminé que l'entité SIP primaire n'est pas apte à fournir un service, l'entité SIP adjacente envoie le message de demande d'ouverture de session à l'entité SIP de secours ; quand l'entité SIP de secours reçoit le message de demande d'ouverture de session, l'entité SIP de secours traite le message de demande d'ouverture de session associé, à la place de l'entité SIP primaire. Dans la présente invention, quand l'entité SIP primaire n'est pas apte à fournir un service, l'entité SIP de secours est apte à remplacer l'entité SIP primaire afin de fournir un soutien en service. Dans ces conditions, l'objectif visant à ce que le service d'une session SIP ne soit pas interrompu est totalement atteint.
PCT/CN2012/070502 2011-02-17 2012-01-18 Procédé et système pour la protection d'une session sip Ceased WO2012109953A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110039955.4 2011-02-17
CN201110039955.4A CN102647397B (zh) 2011-02-17 2011-02-17 一种sip会话保护的方法和系统

Publications (1)

Publication Number Publication Date
WO2012109953A1 true WO2012109953A1 (fr) 2012-08-23

Family

ID=46659976

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/070502 Ceased WO2012109953A1 (fr) 2011-02-17 2012-01-18 Procédé et système pour la protection d'une session sip

Country Status (2)

Country Link
CN (1) CN102647397B (fr)
WO (1) WO2012109953A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103078966B (zh) * 2012-12-28 2017-02-08 侯荣涛 一种基于sip协议的无中心通信系统的快速寻址方法
CN107070950B (zh) * 2017-05-24 2021-04-20 深圳市万普拉斯科技有限公司 Ims注册控制的方法、装置和计算机可读存储介质
CN115514516B (zh) * 2022-08-09 2026-01-23 慧之安信息技术股份有限公司 一种基于会话拷贝的sip会话保护方法和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1893432A (zh) * 2006-01-11 2007-01-10 华为技术有限公司 会话初始协议应用系统的网络级备份方法、设备和系统
CN101459545A (zh) * 2009-01-13 2009-06-17 北京邮电大学 一种提高会话初始化协议会议系统可靠性的实现方法
JP4425841B2 (ja) * 2005-09-15 2010-03-03 株式会社日立製作所 中継システムおよび呼救済方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005229273A (ja) * 2004-02-12 2005-08-25 Fujitsu Ltd サーババックアップ装置
DE102005009107B3 (de) * 2005-02-28 2006-07-13 Siemens Ag Bereitstellung von redundanten SIP Proxy Ressourcen

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4425841B2 (ja) * 2005-09-15 2010-03-03 株式会社日立製作所 中継システムおよび呼救済方法
CN1893432A (zh) * 2006-01-11 2007-01-10 华为技术有限公司 会话初始协议应用系统的网络级备份方法、设备和系统
CN101459545A (zh) * 2009-01-13 2009-06-17 北京邮电大学 一种提高会话初始化协议会议系统可靠性的实现方法

Also Published As

Publication number Publication date
CN102647397A (zh) 2012-08-22
CN102647397B (zh) 2016-12-21

Similar Documents

Publication Publication Date Title
CN101557393B (zh) Sip可存活网络配置中的同时活动注册
CN101557305B (zh) 用于维护sip可存活用户代理的通信方法、端点和系统
CN101677320B (zh) 用可生存网络的控制器列表中的控制器的滑动窗口注册端点
US8223926B2 (en) Resilient registration with a call manager
CN101547128A (zh) 在sip可存活配置中使用sip消息的故障转移/故障恢复触发
US9001664B2 (en) Methods, systems, and computer readable media for providing sedation service in a telecommunications network
US20100074100A1 (en) Proxy server, communication system, communication method and program
US9948726B2 (en) Reconstruction of states on controller failover
CN104219705B (zh) VoLTE终端重注册方法和装置
US8589498B2 (en) Phase based prioritization of IMS signaling messages for overload throttling
US9113031B2 (en) Call control for conferencing calls
US9369361B2 (en) Method and apparatus for clearing hang calls
EP2667563B1 (fr) Rétablissement d'appel en réponse à une défaillance d'application
WO2026036571A1 (fr) Procédé et système d'accès de planification de dispositif, support de stockage lisible et produit-programme
US8930768B2 (en) System and method of failover for an initiated SIP session
CN102647397B (zh) 一种sip会话保护的方法和系统
US20060092919A1 (en) Inter-enterprise telephony using a central brokerage device
CN102857536A (zh) 对等网络中实现数据备份及迁移的方法及系统
CN102546712A (zh) 一种基于分布式业务网络的消息传输方法、设备和系统
US12457167B2 (en) Alternative route propogation
GB2433376A (en) Communications system with peer-to-peer backup network
CN103138998A (zh) 一种代理状态检测方法、装置和系统
CN101517555A (zh) 用于提供地理位置分散的ip多媒体子系统实例的方法

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

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

Country of ref document: EP

Kind code of ref document: A1