WO2015018248A1 - 一种实现终端被叫业务恢复的方法、相关装置及系统 - Google Patents

一种实现终端被叫业务恢复的方法、相关装置及系统 Download PDF

Info

Publication number
WO2015018248A1
WO2015018248A1 PCT/CN2014/081582 CN2014081582W WO2015018248A1 WO 2015018248 A1 WO2015018248 A1 WO 2015018248A1 CN 2014081582 W CN2014081582 W CN 2014081582W WO 2015018248 A1 WO2015018248 A1 WO 2015018248A1
Authority
WO
WIPO (PCT)
Prior art keywords
cscf
user terminal
request
registration
user
Prior art date
Application number
PCT/CN2014/081582
Other languages
English (en)
French (fr)
Inventor
李鹤
叶进洲
徐日东
张彪
时书锋
罗伯强
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to EP14833808.0A priority Critical patent/EP3024177B1/en
Priority to ES14833808T priority patent/ES2701822T3/es
Priority to KR1020167005555A priority patent/KR101902949B1/ko
Priority to JP2016532216A priority patent/JP6355113B2/ja
Priority to EP18183112.4A priority patent/EP3515014B1/en
Priority to EP20209163.3A priority patent/EP3843336B1/en
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2015018248A1 publication Critical patent/WO2015018248A1/zh
Priority to US15/015,008 priority patent/US9894110B2/en
Priority to US15/827,959 priority patent/US10142376B2/en
Priority to US16/146,813 priority patent/US10735480B2/en
Priority to US16/455,749 priority patent/US11005899B2/en
Priority to US17/214,540 priority patent/US11627168B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1069Session establishment or de-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • H04L12/1407Policy-and-charging control [PCC] architecture
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1016IP multimedia subsystem [IMS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1073Registration or de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1083In-session procedures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0893Assignment of logical groups to network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1046Call controllers; Call servers

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, a related device, and a system for implementing recovery of a called service of a terminal.
  • CSCF Call Session Control Function
  • IMS IP Multimedia Subsystem
  • P-CSCF Proxy CSCF, Proxy CSCF
  • I-CSCF Interrogating CSCF, Query CSCF
  • S-CSCF Server CSCF, Stanley CSCF
  • the P-CSCF fails, the user terminal registered by the P-CSCF, if it is called, the S-CSCF finds that the P-SCCF is faulty when managing the called service, then The end user cannot be contacted through the P-CSCF, causing the service to fail.
  • the primary and backup devices are composed by two P-CSCFs.
  • P-CSCF1 and P-CSCF2 are configured with the same IP address IP1.
  • P-CSCF1 advertises its own route
  • P-CSCF2 does not advertise its own address.
  • the user terminal sends a registration request to IP1 to register with the primary P-CSCF1, and the P-CSCF1 simultaneously backs up the user registration information to the standby P-CSCF2.
  • the P-CSCF2 can detect the P-CSCF1 failure through the heartbeat.
  • the P-CSCF2 will advertise its own route, and then the service of the terminal will be routed to the P-CSCF2 for processing. Since the user's information has been backed up at the time of registration, the new P-CSCF2 will be able to correctly process the user's request.
  • the main disadvantages of the solution for backup of active and standby data are as follows:
  • the heartbeat detection is easy to cause a double-master failure.
  • the active and standby NEs cannot provide services.
  • the active and standby NEs need to support the same IP address.
  • the technical problem to be solved by the embodiments of the present invention is to provide a method, a related device and a system for realizing the recovery of the called service of the terminal, which can quickly recover the called service of the user terminal when the P-CSCF fails.
  • an embodiment of the present invention provides a method for implementing recovery of a called service of a terminal, including: querying an initial proxy call session control function entity currently registered by the user terminal when receiving a called request for a user terminal P-CSCF;
  • the initial P-CSCF fails, select an available P-CSCF, and send a notification message to the available P-CSCF to trigger the user terminal to re-register the P-CSCF;
  • the available P-CSCF triggers the user terminal to re-register the P-CSCF through the policy and charging rule function entity PCRF.
  • the sending the notification message to the available P-CSCF to trigger the user terminal to re-register the P-CSCF includes: providing the available P-CSCF Sending a notification message carrying a disaster tolerance identifier, the disaster tolerance identifier is used to instruct the available P-SCCF to trigger the user terminal to re-register the P-CSCF.
  • the sending the notification message to the available P-CSCF to trigger the user terminal to re-register the P-CSCF includes: providing the available P-CSCF Sending a called request of the user terminal;
  • the embodiment of the present invention further provides another method for implementing recovery of a called terminal service, including: receiving a notification message carrying a user name sent by a serving call session control function entity S-CSCF;
  • the notification message further includes a disaster tolerance identifier, generating a reselection request carrying the P-CSCF reselection identifier and the username; Transmitting, by the policy and charging rule function entity PCRF of the user terminal indicated by the user name, the reselection request, so that the PCRF notifies the user terminal indicated by the user name according to the P-CSCF reselection identifier Selecting a P-CSCF to carry the called service of the user terminal;
  • the notification message carrying the disaster tolerant identifier is generated by the S-CSCF when the P-CSCF registered by the user terminal corresponding to the received called request is faulty, and the disaster recovery identifier is used to indicate the triggering location.
  • the user terminal re-registers the P-CSCF.
  • the sending, by the policy and charging rule function entity PCRF of the user terminal indicated by the user name, the reselection request includes: reselecting the reselection The request is sent to the routing proxy node DRA such that the DRA sends the reselection request to the PCRF managing the user terminal indicated by the username according to the username in the reselection request.
  • the P-CSCF reselection is generated. Before identifying the reselection request with the username, it also includes:
  • the re-selection request that includes the P-CSCF reselection identifier and the username is generated.
  • the method further includes:
  • the registration completion message is sent to the S-CSCF to which the user terminal belongs to complete the registration of the user terminal.
  • the embodiment of the present invention further provides another method for implementing recovery of a called service of a terminal, including:
  • the reselection request is generated by the P-CSCF according to a notification message that is sent by the S-CSCF and carries a notification message for indicating that the user terminal that is triggered by the user name re-registers the P-CSCF.
  • generating a registration trigger request including: receiving When the P-CSCF sends a reselection request carrying the P-CSCF reselection identifier and the username, generating a registration trigger request carrying the session release message;
  • the session release message is used to indicate that the gateway connected to the user terminal indicated by the username requests the mobility management entity MME to delete the user bearer of the user.
  • generating a registration trigger request including: receiving When the P-CSCF sends a reselection request carrying the P-CSCF reselection identifier and the username, generating a registration trigger request carrying the updated P-CSCF address information;
  • the update P-CSCF address information is used to indicate that the gateway connected to the user terminal indicated by the user name generates an available P-CSCF address list and sends the information to the user terminal indicated by the user name.
  • the embodiment of the present invention further provides another method for implementing recovery of a called service of a terminal, including:
  • the registration trigger request is generated when the PCRF receives a reselection request carrying a P-CSCF reselection identifier and a username sent by the P-CSCF; the reselection request is the P-CSCF according to the S - a notification message sent by the CSCF carrying a user name and indicating a disaster recovery identifier for triggering the user terminal to re-register the P-CSCF indicated by the username.
  • the triggering, by the user terminal indicated by the user name, to re-register the P-CSCF includes: When the registration triggering request carries the session release message, the mobile management entity MME sends a release request carrying the username, so that the MME deletes the user bearer of the user terminal indicated by the username; or
  • the available P-CSCF address list is sent to the user terminal indicated by the user name, so that the user terminal is from the available P-CSCF address list.
  • the P-CSCF is selected and registered to the selected P-CSCF.
  • the embodiment of the present invention further provides another method for implementing recovery of a called service of a terminal, including:
  • a registration request is registered to the P-CSCF, so as to carry the called service through the re-registered P-CSCF when the initial P-CSCF fails;
  • the P-CSCF When receiving the list of available P-CSCF addresses sent by the gateway, the P-CSCF is selected from the list of available P-CSCF addresses and registered to the selected P-CSCF, so as to be re-registered when the initial P-CSCF fails.
  • the P-CSCF carries the called service.
  • selecting the P-CSCF from the available P-CSCF address list and registering to the selected P -CSCF including:
  • the gateway When receiving the available P-CSCF address list sent by the gateway, determining whether the available P-CSCF address list includes the host name of the initial P-CSCF currently registered by the user terminal;
  • an embodiment of the present invention provides an apparatus for implementing recovery of a called service of a terminal, including: a querying module, configured to query an initial proxy currently registered by the user terminal when receiving a called request for a user terminal Call session control function entity P-CSCF;
  • a processing module configured to: if an initial P-CSCF is detected to be faulty, select an available P-CSCF, and send a notification message to the available P-CSCF to trigger the user terminal to re-register the P-CSCF; And the available P-CSCF triggers the user terminal to re-register the P-CSCF by using a policy and charging rule function entity PCRF.
  • the processing module is specifically configured to: after selecting an available P-CSCF, send, to the available P-CSCF, a notification message that carries a disaster tolerance identifier, where The disaster tolerance identifier is used to indicate that the available P-SCCF triggers the user terminal to re-register the P-CSCF.
  • the processing module is specifically configured to: after selecting an available P-CSCF, send the to the available P-CSCF The called request of the user terminal, so that the available P-CSCF determines that the registration data of the called user is not stored, triggering the user terminal to re-initiate the IMS registration.
  • the embodiment of the present invention further provides another apparatus for implementing recovery of a called service of a terminal, including:
  • a receiving module configured to receive a notification message carrying a username sent by the serving call session control function entity S-CSCF;
  • a processing module configured to: if the solution to the notification message further includes a disaster tolerance identifier, generate a reselection request that carries the P-CSCF reselection identifier and the username;
  • a sending module configured to send the reselection request to a policy and charging rule function entity PCRF that manages the user terminal indicated by the user name, so that the PCRF notifies the user name according to the P-CSCF reselection identifier
  • the instructed user terminal reselects the P-CSCF to carry the called service of the user terminal; wherein the notification message carrying the disaster recovery identifier is that the S-CSCF registers with the user terminal corresponding to the received called request
  • the disaster recovery identifier is used to indicate that the user terminal is triggered to re-register the P-CSCF.
  • the sending module is specifically configured to send the reselection request to a routing proxy node DRA, so that the DRA is based on a user in the reselection request
  • the name is sent to the PCRF that manages the user terminal indicated by the username.
  • the method further includes:
  • a determining module configured to determine whether the user terminal indicated by the user name is registered at the local end, and if the result of the determination is that the user terminal is not registered at the local end, notifying the processing module to perform the parsing into the notification message further includes
  • the disaster tolerance identifier generates a reselection request carrying the P-CSCF reselection identifier and the username.
  • a registration module configured to: when receiving a registration request of the user terminal, to the user terminal
  • the S-CSCF sends a registration completion message to complete the registration of the user terminal.
  • the embodiment of the present invention further provides another device for implementing recovery of a called service of a terminal, including:
  • a generating module configured to generate a registration trigger request when receiving a reselection request sent by the P-CSCF and carrying a P-CSCF reselection identifier and a username;
  • a sending module configured to send the generated registration trigger request to a gateway connected to the user terminal indicated by the user name, so that the gateway triggers the user terminal indicated by the user name to re-register the P-CSCF to carry the The called service of the user terminal;
  • the reselection request is generated by the P-CSCF according to a notification message that is sent by the S-CSCF and carries a notification message for indicating that the user terminal that is triggered by the user name re-registers the P-CSCF.
  • the generating module is specifically configured to generate a carrying session when receiving a reselection request that carries a P-CSCF reselection identifier and a username sent by the P-CSCF Release the registration trigger request for the message;
  • the session release message is used to indicate that the gateway connected to the user terminal indicated by the username requests the mobility management entity MME to delete the user bearer of the user.
  • the generating module is specifically configured to generate a carrying update when receiving a reselection request that carries a P-CSCF reselection identifier and a username sent by the P-CSCF.
  • the update P-CSCF address information is used to indicate that the gateway connected to the user terminal indicated by the user name generates an available P-CSCF address list and sends the information to the user terminal indicated by the user name.
  • the embodiment of the present invention further provides another apparatus for implementing recovery of a called service of a terminal, including:
  • a receiving module configured to receive a carrying username sent by a policy and charging rule function entity PCRF Registration trigger request
  • a triggering module configured to trigger a user terminal indicated by the user name to re-register the P-CSCF to carry the called service of the user terminal;
  • the registration trigger request is generated when the PCRF receives a reselection request carrying a P-CSCF reselection identifier and a username sent by the P-CSCF; the reselection request is the P-CSCF according to the S - a notification message sent by the CSCF carrying a user name and indicating a disaster recovery identifier for triggering the user terminal to re-register the P-CSCF indicated by the username.
  • the triggering module includes: a first sending unit, configured to: when the registration triggering request carries a session release message, send a carrying place to a mobility management entity MME Deleting a request for releasing the username, so that the MME deletes a user bearer of the user terminal indicated by the username; or
  • a second sending unit configured to: when the registration triggering request carries the updated P-CSCF address information, obtain an available P-CSCF address list and send the information to the user terminal indicated by the user name, so that the user terminal Select the P-CSCF from the list of available P-CSCF addresses and register to the selected P-CSCF.
  • the embodiment of the present invention further provides another apparatus for implementing recovery of a called service of a terminal, including:
  • a registration initiation module configured to initiate a registration request to the P-CSCF when the access failure is detected, so as to carry the called service by the re-registered P-CSCF when the initial P-CSCF fails;
  • a registration selection module configured to: when receiving a list of available P-CSCF addresses sent by the gateway, select a P-CSCF from the list of available P-CSCF addresses and register with the selected P-CSCF, so as to occur in the initial P-CSCF The called service is carried by the re-registered P-CSCF in case of failure.
  • the registration selection module includes: a determining unit, configured to determine the available P-CSCF address list when receiving a list of available P-CSCF addresses sent by the gateway Whether the host name of the initial P-CSCF currently registered by the user terminal is included in the registration; a registration selection unit, if not included, selects the P-CSCF from the available P-CSCF address list and registers with the selected P-CSCF.
  • the embodiment of the present invention further provides a system for implementing recovery of a called service of a terminal, including: a service proxy call session control function entity S-CSCF, at least two proxy call session control function entities P-CSCF, and a user a terminal, where the at least two P-CSCFs include a second P-CSCF and a first P-CSCF currently registered by the user terminal, where
  • the S-CSCF is configured to: when receiving a called request for the user terminal, query a first P-CSCF currently registered by the user terminal; if detecting that the first P-CSCF is faulty, select Sending, by the second P-CSCF, a notification message carrying a disaster tolerance identifier to the second P-CSCF, where the disaster tolerance identifier is used to indicate that the available P-CSCF triggers the user terminal to re-register P- CSCF;
  • the second P-CSCF is configured to trigger the user terminal to re-register the P-CSCF;
  • the S-CSCF is further configured to: when receiving the registration completion message sent by the P-CSCF re-registered by the user terminal, send the called request to the re-registered P-CSCF to carry the The called service of the user terminal;
  • the second P-CSCF triggers the user terminal to re-register the P-CSCF by using the policy and charging rule function entity PCRF.
  • the method further includes: a DNS server, where the S-CSCF is further configured to configure, according to the host name of the first P-CSCF, in the DNS server An identifier and a second identifier, where the first identifier includes an IP address of the first P-CSCF, and the second identifier includes an IP address of the second P-CSCF.
  • the method further includes: a policy and charging rule function entity PCRF;
  • the second P-CSCF is specifically configured to generate, according to the notification message that carries the user name and the disaster tolerance identifier sent by the S-CSCF, a reselection request that carries the P-CSCF reselection identifier and the username, and Sending a reselection request to the PCRF;
  • the PCRF is configured to notify the user terminal indicated by the user name to reselect the P-CSCF according to the P-CSCF reselection identifier to carry the called service of the user terminal.
  • the method further includes: a routing proxy node DRA;
  • the DRA is configured to receive a reselection request sent by the second P-CSCF, and send the reselection request to the PCRF.
  • system further includes: connecting to the user terminal Gateway
  • the PCRF is specifically configured to: when receiving a reselection request that carries a P-CSCF reselection identifier and a username sent by the P-CSCF, generate a registration trigger request, and send the registration trigger request to the gateway; And a gateway, configured to trigger, according to the registration trigger request, the user terminal indicated by the username to re-register the P-CSCF to carry the called service of the user terminal.
  • the gateway is specifically configured to: when the registration trigger request carries a session release message, to the mobility management entity MME Sending a release request carrying the username, so that the MME deletes a user bearer of the user terminal indicated by the username; or
  • the available P-CSCF address list is sent to the user terminal indicated by the user name, so that the user terminal is from the available P-CSCF address list.
  • the P-CSCF is selected and registered to the selected P-CSCF.
  • the user terminal is further configured to initiate a registration request for registration to the P-CSCF when the access failure is detected, In order to carry the called service through the re-registered P-CSCF when the initial P-CSCF fails; or to select P from the available P-CSCF address list when receiving the list of available P-CSCF addresses sent by the gateway.
  • the -CSCF registers with the selected P-CSCF to facilitate the called service through the re-registered P-CSCF when the initial P-CSCF fails.
  • the embodiment of the present invention provides a method for implementing recovery of a called service of a terminal, including: receiving a called request for a user terminal;
  • an embodiment of the present invention provides an apparatus for implementing recovery of a called service of a terminal, including: a receiving module, configured to receive a called request to a user terminal;
  • a processing module configured to: when the receiving module receives the called request, determine that the registration data of the called user is not stored; and the sending module is configured to: after the processing module determines that the registration data of the called user is not stored, Sending a request to the PCRF managing the user terminal to trigger the user terminal to re-initiate the IMS registration.
  • the embodiment of the present invention After receiving the called request, the embodiment of the present invention detects that the P-CSCF currently registered by the user terminal corresponding to the called request fails, and finally generates a corresponding message carrying the disaster tolerance identifier to finally trigger the terminal to re-register P- The CSCF, and the called service of the user terminal is carried in the re-registered P-CSCF, which avoids the double-master failure problem caused by the heartbeat detection between the active and standby network elements in the prior art, and the need to externally present the same IP handles complex problems; and can quickly complete fault recovery in existing network architectures.
  • FIG. 1 is a schematic flow chart of a first embodiment of a method for realizing recovery of a called service of a terminal according to the present invention
  • FIG. 2 is a schematic flowchart of a second embodiment of a method for realizing recovery of a called service of a terminal according to the present invention
  • 2B is a schematic flow chart of a method for implementing recovery of a called service of a terminal according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a third embodiment of a method for realizing recovery of a called service of a terminal according to the present invention
  • FIG. 4 is a schematic flowchart of a fourth embodiment of a method for realizing recovery of a called service of a terminal according to the present invention
  • FIG. 6 is a schematic flowchart diagram of a sixth embodiment of a method for implementing recovery of a called service of a terminal according to the present invention
  • FIG. FIG. 8 is a schematic flowchart of a seventh embodiment of a method for realizing recovery of a called service of a terminal according to the present invention
  • FIG. 8 is a schematic flowchart of a method for implementing recovery of a called service of a terminal according to an embodiment of the present invention
  • FIG. 9 is a schematic flowchart of a method for implementing recovery of a called service of a terminal according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a first embodiment of an apparatus for implementing recovery of a called service of a terminal according to the present invention
  • FIG. 11A is a schematic flow chart of a second embodiment of an apparatus for implementing recovery of a called service of a terminal according to the present invention
  • FIG. 11B is a schematic structural diagram of an apparatus for implementing recovery of a called service of a terminal according to an embodiment of the present invention
  • FIG. 12 is a schematic flowchart of a third embodiment of an apparatus for implementing recovery of a called service of a terminal according to the present invention
  • FIG. 14 is a schematic structural diagram of a fifth embodiment of an apparatus for recovering a called service of a terminal according to the present invention
  • FIG. 15 is a schematic diagram of implementing a terminal called service according to an embodiment of the present invention
  • FIG. 16 is a schematic structural diagram of a network device according to an embodiment of the present invention
  • FIG. 17A is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • FIG. 17B is a schematic structural diagram of an apparatus for implementing recovery of a called service of a terminal according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of still another network device according to an embodiment of the present invention.
  • FIG. 19 is a schematic structural diagram of still another network device according to an embodiment of the present invention.
  • FIG. 20 is a schematic structural diagram of a user equipment according to an embodiment of the present invention.
  • P-CSCF pool When a user conducts a called service through a user terminal, if the user terminal is currently registered with the P-CSCF Fault, triggering the user terminal to re-register the new P-CSCF through other P-CSCFs in the P-CSCF POOL (P-CSCF pool).
  • FIG. 1 is a schematic flowchart of a method for implementing a method for recovering a called service of a terminal according to the present invention.
  • the method in the embodiment of the present invention may be specifically implemented in an S-CSCF or an IBCF (Interconnection Border Control Function).
  • the method of the present invention includes:
  • the P-CSCF After the user terminal registers with the P-CSCF, the P-CSCF sends the corresponding registration completion information to the S-CSCF, which is authenticated and authenticated by the S-CSCF, and performs the registration of the user name of the user terminal and its registered P- The host name of the CSCF is processed. Therefore, the S-CSCF can query and determine the initial P-CSCF currently registered by the user terminal according to the user name of the user terminal corresponding to the received called request.
  • the user name of the user terminal is used to identify the user terminal, and specifically, an IP address, a user service authority, and other user configuration information of the user terminal.
  • the S-CSCF may perform heartbeat detection with each P-CSCF in the current P-CSCF POOL through a heartbeat mechanism, and determine an initial registration of the user terminal according to data of heartbeat detection or according to whether heartbeat data can be normally received. Whether the P-CSCF has failed, for example, when the ping command (a command to check whether the network is unobstructed or the speed of the network connection) is unreachable, or the detected message fails, the initial P-CSCF may be determined to be faulty.
  • the ping command a command to check whether the network is unobstructed or the speed of the network connection
  • the notification message may be sent to the available P-CSCF in any of the following manners to achieve the purpose of triggering the user terminal to re-register the P-CSCF:
  • Manner 1 Sending, to the available P-CSCF, a notification message carrying a disaster tolerant identifier, where the disaster tolerance identifier is used to instruct the available P-SCCF to trigger the user terminal to re-register the P-CSCF;
  • Manner 2 Send the called request of the user terminal to the available P-CSCF; when the available P-CSCF determines that the registration data of the called user is not stored, trigger the user terminal to re-initiate the IMS registered.
  • the notification message is specifically the called request.
  • the available P-CSCF determines that the registration data of the called user is not stored in the available P-CSCF, the user terminal is triggered to re-initiate the IMS registration.
  • the called user is a called user who uses the user terminal.
  • triggering the user terminal to re-register the P-CSCF means triggering the user terminal to re-initiate the IMS registration.
  • an available P-CSCF is selected from the current P-CSCF POOL, and the available P-CSCF may be a P- that has been determined to be faultless by means of heartbeat detection or the like. CSCF.
  • the first P-CSCF may be configured with two identifiers, that is, the first identifier and the second identifier, where the first identifier includes an IP address of the initial P-CSCF,
  • the second identity includes an IP address of a P-CSCF other than the initial P-CSCF.
  • the first identifier is an IP address advertised by the initial P-CSCF
  • the second identifier is an IP address of the P-CSCF except the initial P-CSCF in the P-CSCF POOL (corresponding to S102
  • the available P-CSCF when detecting that the initial P-CSCF fails in the S102, may send the notification message directly to the available P-CSCF according to the configured second identity.
  • the two identifiers configured for the initial P-CSCF may be configured to configure the first identifier and the second identifier according to the host name of the initial P-CSCF in a DNS (Domain Name System) server.
  • DNS Domain Name System
  • the S102 may include: obtaining a first identifier and a second identifier configured for the initial P-CSCF, where the query may be performed by using a host name of the initial P-CSCF to obtain a second identifier and a second identifier; if the initial P-CSCF corresponding to the first identifier is detected to be faulty according to the obtained first identifier, the P-CSCF corresponding to the second identifier is used as an available P-CSCF, such as The first identifier sends a heartbeat message, and if the response message is not received normally, the first P-CSCF corresponding to the first identifier may be determined to be faulty; and the notification message is sent to the available P-CSCF according to the second identifier.
  • the notification message is sent according to the second identifier of the configuration.
  • the user name of the user terminal is also carried in the notification message, so that the available P-CSCF initiates a process of triggering the user terminal to re-register the P-CSCF according to the user name.
  • S103 Optionally, when the registration completion message sent by the P-CSCF re-registered by the user terminal is received, the called request is sent to the re-registered P-CSCF to carry the user terminal. Called business.
  • the available P-CSCF triggers the user terminal to re-register the P-CSCF by using a Policy and Charging Rules Function (PCRF).
  • PCRF Policy and Charging Rules Function
  • the available P-CSCF may initiate a process of triggering the user terminal to re-register the P-CSCF after the current P-CSCF registered by the user terminal fails, according to the disaster tolerance identifier in the notification message. Specifically, the available P-CSCF may notify the user terminal to re-register the new P-CSCF by managing the policy and charging rule function entity PCRF of the user terminal and the path of the gateway connected to the user terminal. In order for the S-CSCF to send the called request to the new P-CSCF, the new P-CSCF carries the called service of the user terminal.
  • the available P-CSCF may also determine the current P-CSCF registered by the user terminal when it is determined that the available P-CSCF does not store the registration data of the called user when receiving the called request of the user terminal. To send a fault, a process of triggering the user terminal to re-register the P-CSCF needs to be initiated.
  • the sending the called request to the re-registered P-CSCF to carry the called service of the user terminal includes: sending the called request to the re-registered P- The CSCF, so that the re-registered P-CSCF sends the called request to the user terminal to perform called service. That is, the S-CSCF sends the called request to the re-registered P-CSCF, and then the called P-CSCF sends the called request to the user terminal to complete the called service.
  • the terminal After receiving the called request, if the P-CSCF currently registered by the user terminal corresponding to the called request fails, the terminal triggers the terminal to perform re-registration by generating a corresponding message carrying the disaster tolerance identifier.
  • -CSCF and the called service of the user terminal is carried in the re-registered P-CSCF, which avoids the double-master failure problem caused by the heartbeat detection between the active and standby network elements in the prior art and the external presentation The complex problem caused by the same IP; and the ability to quickly complete fault recovery in the existing network architecture.
  • FIG. 2A is a schematic flowchart of a second embodiment of a method for implementing recovery of a called service of a terminal according to the present invention.
  • the method in the embodiment of the present invention may be implemented in a P-CSCF, and the root of the P-CSCF is implemented.
  • the user terminal is triggered to re-register the P-CSCF according to the notification message sent by the S-CSCF of the front end.
  • the method in the embodiment of the present invention includes:
  • S201 Receive a notification message carrying a user name sent by the serving call session control function entity S-CSCF; the user name includes the identifier of the user terminal corresponding to the called request received by the S-CSCF, that is, the user of the called segment
  • the terminal identifier may be an IP address, a user service authority, and other user configuration information of the user terminal as the called end.
  • the notification message carrying the disaster recovery identifier is generated when the P-CSCF registered by the user terminal corresponding to the called request received by the S-CSCF is faulty, and the disaster recovery identifier is used to indicate that the The user terminal re-registers the P-CSCF. That is, when the P-CSCF registered as the user terminal of the called end fails, the process of re-registering is triggered.
  • the process of generating the notification message including the disaster tolerance identifier by the S-CSCF may refer to the description in the first embodiment of the foregoing method.
  • a P-CSCF in the P-CSCF POOL performs a related step, and the P-CSCF corresponds to the available P-CSCF in the foregoing first embodiment.
  • the bearer service of the corresponding user terminal may be carried according to the username in the notification message.
  • S203 Send the reselection request to a policy and charging rule function entity PCRF that manages the user terminal indicated by the user name, so that the PCRF notifies the user indicated by the user name according to the P-CSCF reselection identifier. Reselecting the P-CSCF to carry the called service of the user terminal;
  • the reselection request carrying the P-CSCF reselection identifier and the username generated in the S202 may be specifically an STR (Session-Termination-Request), and the P-CSCF defined in the STR is carried in the STR.
  • Re-Select Flag, and the username is used to instruct the PCRF to determine the user terminal that needs to perform reselection registration.
  • the STR is sent to the PCRF in the S203.
  • the available P-CSCF may not know the PCRF to which the user terminal corresponding to the user name belongs.
  • the S203 specifically includes:
  • the reselection request is sent to a routing proxy node DRA (Diameter Routing Agent), so that the DRA sends the reselection request to the user indicated by the username according to the username in the reselection request.
  • the PCRF of the terminal That is, the available P-CSCF may first send the STR to the DRA, and then the DRA determines the PCRF of the user terminal corresponding to the user name according to the username in the STR.
  • the method may further include:
  • the process proceeds to S202. If the local end has been registered, the registration completion message may be directly sent to the S-CSCF, and the user name of the user terminal and the host name of the local end are registered in the S-CSCF, so that the S-CSCF will The called request of the user terminal is sent to the local end, and the local end carries the called service of the user terminal as the called end.
  • the available P-CSCF may notify the user terminal to re-register a new P-CSCF by managing a PCRF of the user terminal and a notification path of a gateway connected to the user terminal, so that the S-CSCF will The called request of the user terminal is sent to the new P-CSCF, and the called service of the user terminal is carried by the new P-CSCF. After the user terminal is notified to re-register the new P-CSCF, the user terminal may select the available P-CSCF. Therefore, in the embodiment of the present invention, the following S204 may be further included.
  • S204 When receiving the registration request of the user terminal, send a registration completion message to the S-CSCF to which the user terminal belongs to complete registration of the user terminal.
  • the user terminal can complete the registration to the P-CSCF by using the existing registration process. After determining that the user terminal is successfully registered, the P-CSCF sends a registration completion message to the front-end S-CSCF, so as to notify the front-end S. The called request that the CSCF can receive is sent to the P-CSCF to carry the called service of the user terminal.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the need to pass the heartbeat check between the active and standby NEs in the prior art.
  • FIG. 2B Another embodiment of the present invention provides a method for implementing recovery of a called service of a terminal, as shown in FIG. 2B.
  • the method shown in Figure 2B can be implemented in a P-CSCF. Specifically, the method includes:
  • step 201 a called request for the user terminal sent by the S-CSCF or the IBCF may be received.
  • step S202' the P-CSCF determines whether the P-CSCF stores the registration data of the called user. When it is determined that the P-CSCF does not store the registration data of the called user, step S203 is performed.
  • S203' Send a request to the PCRF that manages the user terminal to trigger the user terminal to re-initiate IMS registration.
  • the request for triggering the user terminal to re-initiate the IMS registration may be a request for carrying a re-registration identifier, where the re-registration identifier is used to trigger the user terminal to re-initiate the IMS registration.
  • the request carrying the re-registration identifier may be an STR or an AAR (Authorization Authorization Request).
  • FIG. 3 it is a schematic flowchart of a third embodiment of a method for implementing recovery of a called service of a terminal according to the present invention.
  • the method in the embodiment of the present invention can be applied to a policy and charging rule function entity PCRF of a management user terminal.
  • the PCRF performs the steps of the method in the embodiment of the present invention when receiving a reselection request, such as an STR, that carries a P-CSCF Re-Select Flag, and the method includes:
  • S301 Generate a registration trigger request when receiving a reselection request that is sent by the P-CSCF and carries a P-CSCF reselection identifier and a username.
  • the user name includes a corresponding request received by the S-CSCF.
  • the identifier of the user terminal that is, the identifier of the user terminal at the called end, may specifically be the IP address of the user terminal as the called end, the user service authority, and other user configuration information.
  • S302 Send the generated registration to a gateway connected to the user terminal indicated by the username Trimming a request, so that the gateway triggers the user terminal indicated by the username to re-register the P-CSCF to carry the called service of the user terminal;
  • the reselection request is generated by the P-CSCF according to a notification message that is sent by the S-CSCF and carries a notification message for indicating that the user terminal that is triggered by the user name re-registers the P-CSCF.
  • the reselection request may be an STR or the like.
  • the PCRF After receiving the reselection request of the STR carrying the P-CSCF Re-Select Flag, the PCRF needs to perform the called service recovery process of the user terminal corresponding to the user name, that is, generate the registration trigger request, and the registration trigger request is generated.
  • the gateway sent to the user terminal corresponding to the user name the gateway may be a P-GW (Packet Data Network Gateway) or an S-GW (Serving Gateway), and the gateway directly triggers the user terminal to reselect. New P-CSCF.
  • P-GW Packet Data Network Gateway
  • S-GW Serving Gateway
  • the S301 may specifically include:
  • the gateway connected to the user terminal requests the mobility management entity MME (Mobility Management Entity) to delete the user bearer of the user.
  • MME Mobility Management Entity
  • the registration trigger request may be a RAR (Re-Auth-Request) carrying a Session-Release-Cause AVP (Attribute Length Value) (the attribute value pair of the message release reason), that is, in the RAR. Carrying the session release reason attribute field and the field value, indicating that the gateway requests to delete all bearers of the user terminal, and the gateway directly requests to release the IMS (IP Multimedia Subsystem IP Multimedia Subsystem) PDN (Packet Data) of the user terminal corresponding to the user name.
  • Network packet data network
  • the user terminal After the MME deletes the IMS PDN, the user terminal will drop the line. If the user terminal detects that the access fails, the new registration process will be automatically performed to complete the registration including the registration of the P-CSCF.
  • the user terminal initiates selection of an available third P-CSCF3, and initiates a SIP (Session Initiation Protocol) initial registration to the third P-CSCF, and the third P-CSCF sends the user registration request to the user.
  • the home S-CSCF completes the registration request.
  • the third P-CSCF can pass the I-CSCF Determining the S-CSCF to which the user terminal belongs, and then completing the registration request to the S-CSCF to which the queried user terminal belongs.
  • the S-CSCF then delivers the called request of the user to the third P-CSCF to carry the called service.
  • the S301 includes:
  • the gateway connected to the user terminal indicated by the username When receiving a reselection request that carries the P-CSCF reselection identifier and the username sent by the P-CSCF, generating a registration trigger request carrying the updated P-CSCF address information; wherein the updated P-CSCF address information is used to indicate
  • the gateway connected to the user terminal indicated by the username When receiving a reselection request that carries the P-CSCF reselection identifier and the username sent by the P-CSCF, generating a registration trigger request carrying the updated P-CSCF address information; wherein the updated P-CSCF address information is used to indicate
  • the gateway connected to the user terminal indicated by the username generates a list of available P-CSCF addresses and sends the list to the user terminal indicated by the username.
  • the registration trigger request is an RAR that carries an Update P-CSCF Address request.
  • the gateway sends an Update PDP (Packet Data Protocol) content Update PDP Context message to the user terminal, so that the user terminal completes the re-registration.
  • the user terminal updates the local P-CSCF list according to the available P-CSCF address list in the Update PDP Context, and checks whether the initial P-CSCF registered by the local end is in the list. If not, the user terminal will The process of re-registering the P-CSCF is initiated. Specifically, the third P-CSCF3 line registration can be selected from the new P-CSCF List (list) delivered by the gateway to carry the called service of the user terminal.
  • the third P-CSCF may determine the S-CSCF to which the user terminal belongs through the I-CSCF, and then complete the registration request to the S-CSCF to which the queried user terminal belongs. The S-CSCF then delivers the called request of the user to the third P-CSCF to carry the called service.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • FIG. 4 is a schematic flowchart of a fourth embodiment of a method for implementing recovery of a called service of a terminal according to the present invention.
  • the method in the embodiment of the present invention may be applied to, for example, a P-GW or an S-GW.
  • the steps of the method in the embodiment of the present invention are performed when a request for triggering a RAR, such as a RAR, is sent by the PCRF.
  • the method includes: S401: Receive a registration trigger request carrying a user name sent by the policy and charging rule function entity PCRF; the user name includes an identifier of the user terminal corresponding to the called request received by the S-CSCF, that is, as a called party
  • the identifier of the user terminal of the terminal may be an IP address, a user service authority, and other user configuration information of the user terminal that is the called end.
  • S402 Trigger the user terminal indicated by the username to re-register the P-CSCF to carry the called service of the user terminal.
  • the registration trigger request is generated when the PCRF receives a reselection request carrying a P-CSCF reselection identifier and a username sent by the P-CSCF; the reselection request is the P-CSCF according to the S - a notification message sent by the CSCF carrying a user name and indicating a disaster recovery identifier for triggering the user terminal to re-register the P-CSCF indicated by the username.
  • the reselection request and the generation process of the registration trigger request can be referred to the descriptions in the second embodiment and the third embodiment, respectively.
  • the S402 may specifically include:
  • the mobile management entity MME sends a release request carrying the username, so that the MME deletes the user bearer of the user terminal indicated by the username;
  • the available P-CSCF address list is sent to the user terminal indicated by the user name, so that the user terminal is from the available P-CSCF address list.
  • the P-CSCF is selected and registered to the selected P-CSCF.
  • the gateway After receiving the RAR carrying the Session-Release-Cause AVP, the gateway instructs the MME to delete the IMS PDN of the user, and triggers the user terminal to re-register the P-CSCF.
  • the gateway receives the RAR that carries the Update P-CSCF Address request sent by the PCRF, it obtains an Update PDP Context message, and sends an Update PDP Context message to the user terminal to trigger the user terminal to obtain an available P-in the Update PDP Context message.
  • the local P-CSCF list is updated in the CSCF address list, and after determining that the updated local P-CSCF list does not include the initial P-CSCF registered by the local end, the new P-CSCF is selected and registered to the selected P- CSCF, complete re-registration.
  • the P-CSCF currently registered by the user terminal is faulty, and the fault tolerance identifier is carried according to the carrying
  • the message is used to trigger the terminal to re-register the P-CSCF, and the called service of the user terminal is carried in the re-registered P-CSCF, which avoids the need for heartbeat detection between the active and standby network elements in the prior art.
  • FIG. 5 is a schematic flowchart of a fifth embodiment of a method for implementing recovery of a called service of a terminal according to the present invention.
  • the method in the embodiment of the present invention may be applied to a user terminal, where the user terminal is determined in the MME.
  • the IMS PDN deletes or receives the available P-CSCF address list sent by the P-GW or the S-GW, the related steps of the method in the embodiment of the present invention are performed.
  • the method includes:
  • S501 When detecting an access failure, initiate a registration request to register with the P-CSCF, so as to carry the called service by the re-registered P-CSCF when the initial P-CSCF fails;
  • the MME After the MME deletes the IMS PDN, the MME will drop the line. If the user terminal detects the access failure, it will automatically perform a new registration process to complete the registration including the P-CSCF to implement network access.
  • the user terminal initiates selection of an available third P-CSCF3 and initiates a SIP initial registration to the third P-CSCF. After receiving the user registration request, the third P-CSCF completes the registration request to the S-CSCF to which the user belongs.
  • the third P-CSCF may determine, by the I-CSCF, the S-CSCF to which the user terminal belongs, and then complete the registration request to the S-CSCF to which the queried user terminal belongs.
  • the S-CSCF then delivers the called request of the user to the third P-CSCF to carry the called service.
  • S502 When receiving the available P-CSCF address list sent by the gateway, select the P-CSCF from the available P-CSCF address list and register to the selected P-CSCF, so as to re-create the failure when the initial P-CSCF fails.
  • the registered P-CSCF carries the called service.
  • the S502 may include: when receiving the available P-CSCF address list sent by the gateway, determining whether the available P-CSCF address list includes the host name of the initial P-CSCF currently registered by the user terminal, If not, the P-CSCF is selected from the list of available P-CSCF addresses and registered to the selected P-CSCF.
  • the registration trigger request is an RAR that carries an Update P-CSCF Address (Update P-CSCF Address) request.
  • the gateway After the gateway receives the RAR, it will send the update PDP content Update PDP Context
  • the user terminal is provided to facilitate the user terminal to complete the re-registration.
  • the user terminal After receiving the Update PDP Context, the user terminal updates the local P-CSCF list according to the available P-CSCF address list in the Update PDP Context, and checks whether the initial P-CSCF registered by the local end is in the list.
  • the user terminal will The process of re-registering the P-CSCF is initiated, and the third P-CSCF3 line that is available for selection may be selected from the new P-CSCF List ( ⁇ ' j table) delivered by the gateway to carry the called service of the user terminal.
  • the third P-CSCF may determine, by the I-CSCF, the S-CSCF to which the user terminal belongs, and then complete the registration request to the S-CSCF to which the queried user terminal belongs.
  • the S-CSCF then delivers the called request of the user to the third P-CSCF to carry the called service.
  • S501 and S502 are performed in any order, and may first detect whether the access fails and perform the S502, or first detect whether the available P-CSCF address list sent by the gateway is received and execute the S502. .
  • the terminal when the P-CSCF currently registered by the user terminal fails, the terminal can re-register the new P-CSCF according to the structure of the network side recovery processing based on the DR information, and carry the new P-CSCF in the new P-CSCF.
  • the called service of the user terminal avoids the double-master failure problem caused by the heartbeat detection between the active and standby network elements in the prior art, and the complicated processing caused by the need to externally present the same IP; Fast recovery from failures in existing network architectures.
  • FIG. 6 it is a schematic flowchart of a sixth embodiment of a method for implementing recovery of a called service of a terminal according to the present invention.
  • the method in the embodiment of the present invention uses user terminals UE, S-CSCF, P-CSCF, PCRF, and The gateway can quickly reply to the called service of the user terminal when the P-CSCF currently registered by the user terminal fails.
  • the method includes:
  • the S-CSCF After receiving the called request to the user terminal, the S-CSCF queries the initial P-CSCF currently registered by the user terminal; the S-CSCF queries the IP address of the P-CSCF according to the host name of the P-CSCF, On the DNS, P-CSCF 1 is the host name of the initial P-CSCF, and two IPs are configured, namely IP1 and IP2, respectively corresponding to P-CSCF1 and P-CSCF2.
  • the S-CSCF detects that the initial P-CSCF is faulty, selects an available P-CSCF, and sends a notification message carrying the disaster tolerant identifier to the available P-CSCF, where the disaster recovery identifier is used. Instructing the available P-CSCF to trigger the user terminal to re-register the P-CSCF. After the S-CSCF senses the P-CSCF (P-CSCF 1 ) corresponding to IP1, it sends a NOTIFY with a disaster-tolerant flag to the available P-CSCF (P-CSCF2) corresponding to IP2, and notifies the user terminal to re-register P. -CSCF.
  • the P-CSCF2 After receiving the notification message carrying the disaster recovery identifier and the username, the P-CSCF2 generates a reselection request carrying the P-CSCF reselection identifier and the username, and sends the reselection request to the PCRF, where the PCRF is used to manage the indication by the username.
  • the PCRF is used to manage the indication by the username.
  • the P-CSCF2 initiates the DR process when it detects that the message has a DR label or a DR label and is not registered with the local end.
  • P-CSCF2 will send an STR (that is, a reselection request) to the PCRF, and the STR carries a custom P-CSCF Re-Select Flag. If the P-CSCF2 does not know the PCRF of the user, the STR will be sent to the DRA first, and the DRA will be routed to the PCRF where the user is located.
  • the PCRF After receiving the reselection request of the P-CSCF reselection identifier and the username sent by the P-CSCF, the PCRF generates a registration trigger request and sends the registration trigger request to the gateway, where the gateway is an S-GW or a P-GW, and the user terminal Connected.
  • the PCRF After receiving the STR with the P-CSCF Re-Select Flag, the PCRF needs to perform the DR recovery process.
  • the PCRF sends an RAR to the P/S-GW to request to delete all bearers of the user terminal.
  • the P/S-GW triggers the user terminal indicated by the user name to re-register the P-CSCF when receiving the registration trigger request carrying the username sent by the policy and charging rule function entity PCRF.
  • the P/S-GW After receiving the RAR of the PCRF, the P/S-GW will instruct the MME to delete the IMS PDN of the user and trigger the user to re-register.
  • the user terminal selects an available P-CSCF3 and initiates an initial SIP registration to the P-CSCF3;
  • the P-CSCF3 After receiving the user terminal registration request, the P-CSCF3 initiates a SIP registration to the S-CSCF to which the user belongs, and completes the registration request, and the P-CSCF3 can determine the S-CSCF to which the user terminal belongs by querying the I-CSCF.
  • the S-CSCF further sends the called request to the P-CSCF3.
  • the P-CSCF3 sends a called request to the UE, to complete the called service of the user terminal according to the called request to carry the called service of the user terminal.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • FIG. 7 is a schematic flowchart of a seventh embodiment of a method for implementing recovery of a called service of a terminal according to the present invention.
  • the method in the embodiment of the present invention uses a user terminal, an S-CSCF, a P-CSCF, a PCRF, and a gateway.
  • the P-CSCF currently registered by the user terminal fails, the called service is quickly replied to the called terminal.
  • the method includes:
  • the S-CSCF After receiving the called request, the S-CSCF queries the initial P-CSCF currently registered by the user terminal corresponding to the called request, that is, the initial P-CSCF of the user terminal as the called end; and the S-CSCF according to the P - The host name of the CSCF queries the IP address of the P-CSCF.
  • P-CSCF1 that is, the host name of the initial P-CSCF, is configured with two IPs, IP1 and IP2, respectively, corresponding to P-CSCF1 and P-. CSCF2.
  • the S-CSCF detects that the initial P-CSCF is faulty, selects an available P-CSCF, and sends a notification message carrying the disaster tolerant identifier to the available P-CSCF, where the disaster recovery identifier is used. Instructing the available P-CSCF to trigger the user terminal to re-register the P-CSCF.
  • the S-CSCF After the S-CSCF senses that the P-CSCF (P-CSCF1) corresponding to IP1 is faulty, it sends a NOTIFY with a disaster-tolerant flag to the available P-CSCF (P-CSCF2) corresponding to IP2, and notifies the user terminal to re-register P- CSCF.
  • the P-CSCF2 After receiving the notification message carrying the disaster recovery identifier and the username, the P-CSCF2 generates a reselection request carrying the P-CSCF reselection identifier and the username, and sends the reselection request to the PCRF, where the PCRF is used to manage the indication by the username.
  • the PCRF is used to manage the indication by the username.
  • the P-CSCF2 When the P-CSCF2 detects that the message has a DR label or a DR label and does not register with the local end, the P-CSCF2 initiates the DR process. P-CSCF2 will send an STR (ie reselection request) to the PCRF, and the STR carries a custom P-CSCF Re-Select Flag. If the P-CSCF2 does not know the PCRF of the user, the STR will be sent to the DRA first, and the DRA will be routed to the PCRF where the user is located.
  • STR ie reselection request
  • the PCRF After receiving the reselection request of the P-CSCF reselection identifier and the username sent by the P-CSCF, the PCRF generates a registration trigger request and sends the registration trigger request to the gateway, where the gateway is an S-GW or a P-GW, and the user terminal Connected.
  • the PCRF disaster recovery method is to send an RAR to the P-GW, and the Update P-CSCF Address request is carried in the RAR, and the request may be private.
  • the P/S-GW obtains the available P-CSCF address list and sends the information to the user terminal indicated by the username.
  • the P/S-GW After receiving the RAR, the P/S-GW sends an Update PDP Context message to the user terminal, and the Update PDP Context message includes a list of available P-CSCF addresses.
  • the user terminal When receiving the available P-CSCF address list sent by the gateway, the user terminal selects a P-CSCF from the available P-CSCF address list; so as to facilitate the re-registered P-CSCF bearer when the initial P-CSCF fails. Called business.
  • the user terminal After receiving the Update PDP Context, the user terminal updates the P-CSCF list and checks whether the P-CSCF1 registered by itself is in the list. If not, the UE initiates a re-registration process. And select the available P-CSCF3 from the new P-CSCF List issued by the P-GW to register.
  • the P-CSCF3 After receiving the user terminal registration request, the P-CSCF3 completes the registration request to the S-CSCF to which the user belongs, and the P-CSCF3 may determine the S-CSCF to which the user terminal belongs by querying the I-CSCF.
  • the S-CSCF further sends a called request to the P-CSCF3.
  • the P-CSCF3 sends a called request to the UE, to complete the called service of the user terminal according to the called request to carry the called service of the user terminal.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • FIG. 8 is a schematic flowchart of a method for implementing recovery of a called service of a terminal according to an embodiment of the present invention.
  • the method in the embodiment of the present invention implements a user by using a user terminal UE, an S-CSCF, a P-CSCF, a PCRF, and a gateway.
  • the P-CSCF that is currently registered by the terminal is faulty, the user terminal is re-registered.
  • the method includes:
  • the S-CSCF After receiving the called request to the user terminal, the S-CSCF obtains the address of the P-CSCF1 saved when the called user registers successfully.
  • the address of one or more spare devices may be pre-configured on the S-CSCF.
  • Another way to obtain the alternate P-CSCF address is to obtain the address of the alternate P-CSCF2 through the DNS query when the address of the saved P-CSCF is the domain name.
  • the S-CSCF detects that the P-CSCF has failed (for example, through the options heartbeat detection), and the S-CSCF selects the low-standby P-CSCF2 when routing.
  • S802 The S-CSCF sends a called request to the available P-CSCF2.
  • the P-CSCF2 After receiving the called request, the P-CSCF2 finds that the registration data of the called user is not stored, and returns an error response to the S-CSCF to reject the current call.
  • the P-SCCF2 finds that the registration data of the called user is not stored in the P-CSCF2, it returns an error response to the S-CSCF.
  • the P-CSCF2 sends a request to the PCRF to trigger the user terminal to re-initiate the IMS registration.
  • the request may carry a re-registration identifier, where the re-registration identifier is used to trigger the user terminal to re-initiate the IMS registration.
  • the request that P-CSCF2 will send to the PCRF may be STR or AAR. It should be noted that, if the P-CSCF2 can also send a request for triggering the user terminal to re-initiate the IMS registration to the DRA, the DRA routes the request for triggering the user terminal to re-initiate the IMS registration to the PCRF to which the user terminal belongs.
  • the PCRF After receiving the request sent by the P-CSCF to trigger the user terminal to re-initiate the IMS registration, the PCRF generates a registration trigger request and sends the request to the gateway.
  • the gateway can be an S-GW or a P-GW.
  • the P-GW or the S-GW When receiving the registration trigger request by the PCRF, the P-GW or the S-GW triggers the user terminal to re-register. Specifically, the P-GW or the S-GW will instruct the MME to delete the IMS PDN connection of the user, triggering the user to re-register.
  • the user terminal selects an available P-CSCF, for example, the user terminal selects P-CSCF3, and initiates a SIP initial registration request to the P-CSCF3;
  • the P-CSCF currently registered by the user terminal is faulty, and the S-CSCF finally triggers the terminal to re-register through the standby P-CSCF, so that the terminal user who needs to use the service resumes the service after completing the registration.
  • FIG. 9 is a schematic flowchart of a method for implementing recovery of a called service of a terminal according to an embodiment of the present invention.
  • the method of the embodiment of the present invention describes that a user terminal UE, an IBCF, a P-CSCF, a PCRF, and a gateway are implemented in a user terminal.
  • the user terminal is triggered to re-register.
  • the method includes:
  • the IBCF Interconnection Border Control Function acquires the address of the next hop P-CSCF1 from the requested route header field after receiving the called request from the user terminal.
  • the address of one or more spare devices may be pre-configured on the IBCF.
  • Another way to obtain the alternate P-CSCF address is to obtain the address of the alternate P-CSCF2 by querying the DNS when the address of the saved P-CSCF is the domain name.
  • the alternate P-CSCF2 will be selected.
  • S902 The IBCF sends a called request to the available P-CSCF2.
  • the P-CSCF2 After receiving the called request, the P-CSCF2 finds that the registration data of the called user is not stored, and returns an error response to the IBCF to reject the current call.
  • the P-SCCF2 finds that the registration data of the called user is not stored in the P-CSCF2, it returns an error response to the S-CSCF.
  • the P-CSCF2 sends a request to the PCRF to trigger the user terminal to re-initiate the IMS registration.
  • the request may carry a re-registration identifier, where the re-registration identifier is used to trigger the user terminal to re-initiate the IMS registration.
  • the request that P-CSCF2 will send to the PCRF may be STR or AAR. It should be noted that, if the P-CSCF2 can also send a request for triggering the user terminal to re-initiate the IMS registration to the DRA, the DRA routes the request for triggering the user terminal to re-initiate the IMS registration to the PCRF to which the user terminal belongs.
  • the PCRF After receiving the request sent by the P-CSCF to trigger the user terminal to re-initiate the IMS registration, the PCRF generates a registration trigger request and sends the request to the gateway.
  • the gateway can be an S-GW or a P-GW.
  • the P-GW or the S-GW triggers the user terminal to re-register when receiving the registration trigger request by the PCRF.
  • the P-GW or S-GW will instruct the MME to delete the IMS PDN of the user, triggering the user to re-register.
  • the user terminal selects an available P-CSCF, for example, the terminal selects the P-CSCF3, and initiates a SIP initial registration request to the P-CSCF3.
  • the P-CSCF currently registered by the user terminal is faulty, and the S-CSCF finally triggers the terminal to re-register through the standby P-CSCF, so that the terminal user who needs to use the service can resume the service after completing the registration in advance.
  • the apparatus and system for realizing recovery of the called service of the terminal according to the embodiment of the present invention are described in detail below.
  • FIG. 10 is a schematic structural diagram of a first embodiment of an apparatus for implementing recovery of a called service of a terminal according to the present invention.
  • the apparatus in the embodiment of the present invention may be an S-CSCF or an IBCF.
  • the apparatus includes:
  • the query module 11 is configured to: when receiving the called request to the user terminal, query the initial proxy call session control function entity P-CSCF currently registered by the user terminal;
  • the processing module 12 is configured to: if it is detected that the initial P-CSCF fails, select an available P-CSCF, and send a notification message to the available P-CSCF to trigger the user terminal to re-register the P-CSCF.
  • the processing module 12 may be specifically configured to: after selecting an available P-CSCF, send, to the available P-CSCF, a notification message that carries a disaster tolerant identifier, where the disaster recovery identifier is used. Instructing the available P-SCCF to trigger the user terminal to re-register the P-CSCF.
  • the processing module 12 may be specifically configured to: after selecting an available P-CSCF, send a called request of the user terminal to the available P-CSCF, so that the available When the P-CSCF determines that the registration data of the called user is not stored, the user terminal is triggered to re-initiate the IMS registration.
  • the device may further comprise an allocation module 13.
  • the allocating module 13 is configured to send the called request to the re-registered P-CSCF to carry the user terminal when receiving the registration completion message sent by the P-CSCF re-registered by the user terminal. Call the business.
  • the available P-CSCF triggers the user terminal to re-register the P-CSCF by using the PCRF.
  • the P-CSCF sends the corresponding registration completion information to the S-CSCF, which is authenticated and authenticated by the S-CSCF, and performs the registration of the user name of the user terminal and its registered P-
  • the host name of the CSCF is processed, and the query module 11 can query and determine the initial P registered by the user terminal according to the user name of the user terminal corresponding to the called request (the user name of the user terminal as the called end).
  • the user name of the user terminal is used to identify the user terminal, and specifically, an IP address, a user service authority, and other user configuration information of the user terminal.
  • the processing module 12 may specifically perform heartbeat detection with each P-CSCF in the current P-CSCF POOL through a heartbeat mechanism, and determine that the user terminal is currently registered according to data of heartbeat detection or according to whether heartbeat data can be normally received. Whether the initial P-CSCF fails, for example, when the ping command fails or the detected message fails, the initial P-CSCF may be determined to be faulty.
  • the processing module 12 When it is detected that the initial P-CSCF fails, the processing module 12 specifically selects an available P-CSCF from the current P-CSCF POOL, and the available P-CSCF may be determined by means of heartbeat detection, etc. For the P-CSCF without failure. The processing module 12 can also be based on the beginning The two identifiers of the initial P-CSCF configuration are selected as the candidate P-CSCF of the initial P-CSCF as the available P-CSCF.
  • the available P-CSCF may initiate a process of triggering the user terminal to re-register the P-CSCF after the current P-CSCF registered by the user terminal fails, according to the disaster tolerance identifier in the notification message. Specifically, the available P-CSCF may notify the user terminal to re-register the new P-CSCF by managing the policy and charging rule function entity PCRF of the user terminal and the path of the gateway connected to the user terminal. So that the allocation module 13 delivers the called request of the user terminal to the new P-CSCF, and the new P-CSCF carries the called service of the user terminal.
  • the available P-CSCF may also determine the current P-CSCF registered by the user terminal when it is determined that the available P-CSCF does not store the registration data of the called user when receiving the called request of the user terminal. To send a fault, a process of triggering the user terminal to re-register the P-CSCF needs to be initiated.
  • the apparatus may further include:
  • the configuration module 14 is configured to configure a first identifier and a second identifier for the initial P-CSCF, where the first identifier includes an IP address of the initial P-CSCF, and the second identifier includes the initial IP address of the P-CSCF outside the P-CSCF.
  • configuration module 14 is specifically configured to configure the first identifier and the second identifier according to the host name of the initial P-CSCF in the domain name system DNS server.
  • the first P-CSCF may be configured with two identifiers, that is, the first identifier and the second identifier, and the first identifier includes an IP address of the initial P-CSCF, and the second identifier is configured by the configuration module 14
  • the identity includes the IP address of the P-CSCF other than the initial P-CSCF.
  • the first identifier is an IP address advertised by the initial P-CSCF
  • the second identifier is an IP address of other P-CSCFs other than the initial P-CSCF in the P-CSCF POOL, in the processing
  • the second identifier configured by the configuration module 14 may directly send the notification message to the available P-CSCF.
  • processing module 12 may specifically include:
  • the obtaining unit 121 is configured to acquire the first identifier and the second identifier configured for the initial P-CSCF, and the detecting unit 122 is configured to: if the first identifier is detected according to the acquired first identifier, The initial P-CSCF is faulty, and the P-CSCF corresponding to the second identifier is used as an available P-CSCF.
  • the processing unit 123 is configured to send the notification message to the available P-CSCF according to the second identifier. That is, the processing module 12 sends the notification message according to the second identifier configured by the configuration module 14.
  • the allocating module 13 is specifically configured to send the called request to the re-registered P-CSCF, so that the re-registered P-CSCF sends the called request to the user.
  • the terminal performs the called service.
  • the embodiment of the present invention After receiving the called request, the embodiment of the present invention detects that the P-CSCF currently registered by the user terminal of the called terminal in the called request is faulty, and finally triggers the terminal by generating a corresponding message carrying the disaster recovery identifier. Re-registering the P-CSCF, and carrying the called service of the user terminal in the re-registered P-CSCF, avoiding the problem of double master failure caused by the heartbeat detection between the active and standby network elements in the prior art and Due to the need to externally present the same IP to handle the complex problems; and can quickly complete the failure recovery in the existing network architecture.
  • the device in the embodiment of the present invention may be a P-CSCF.
  • the device includes: a receiving module. And a notification message for carrying the user name sent by the service call session control function entity S-CSCF; the user name includes an identifier of the user terminal corresponding to the called request received by the S-CSCF, that is, the called party
  • the identifier of the user terminal of the terminal may be an IP address, a user service authority, and other user configuration information of the user terminal that is the called end.
  • the processing module 22 is configured to: if the solution to the notification message further includes a disaster tolerance identifier, generate a reselection request that carries the P-CSCF reselection identifier and the username;
  • the sending module 23 is configured to send the reselection request to a policy and charging rule function entity PCRF that manages the user terminal indicated by the user name, so that the PCRF notifies the user according to the P-CSCF reselection identifier.
  • PCRF policy and charging rule function entity
  • the notification message carrying the disaster tolerant identifier is generated by the S-CSCF when the P-CSCF registered by the user terminal corresponding to the received called request is faulty, and the disaster recovery identifier is used to indicate triggering.
  • the user terminal re-registers the P-CSCF. That is, a notification message is generated when the initial P-CSCF of the user terminal at the called end fails.
  • the process of the S-CSCF generating the notification message including the disaster tolerance identifier may refer to the description in the first embodiment of the foregoing apparatus.
  • the processing module 22 of the P-CSCF may perform the bearer of the called service of the corresponding user terminal according to the username in the notification message.
  • the reselection request carrying the P-CSCF reselection identifier and the username generated by the processing module 22 may specifically be an STR, and the P-CSCF Re-Select Flag (P-CSCF reselection) is carried in the STR. Identification), the sending module 23 sends the STR to the PCRF.
  • the sending module 23 when the sending module 23 performs the sending of the reselection request, the PCRF to which the user terminal corresponding to the user name belongs may not be known. In this case, the sending module 23 is specifically configured to be used. Sending the reselection request to the routing proxy node DRA, so that the DRA sends the reselection request to the user terminal indicated by the user name according to the username in the reselection request.
  • the sending module 23 may first send the STR to the DRA, and then the DRA determines the PCRF of the user terminal corresponding to the user name according to the user name in the STR.
  • the device may specifically include:
  • the determining module 24 is configured to determine whether the user terminal indicated by the user name is registered at the local end, and if the result of the determination is that the local terminal is not registered, the processing module 22 is notified to perform the parsing into the notification message.
  • the disaster recovery identifier is further included, and a reselection request carrying the P-CSCF reselection identifier and the username is generated.
  • the P-CSCF may directly send a registration completion message to the S-CSCF, and register the user name of the user terminal and the host of the local end in the S-CSCF. For example, the S-CSCF sends the received request to the local end, and the local end carries the called service of the user terminal.
  • the device may further include: a registration module. 25. For receiving a registration request of the user terminal, sending a registration completion message to the S-CSCF to which the user terminal belongs to complete registration of the user terminal.
  • the user terminal can complete the registration to the P-CSCF by using the existing registration process.
  • the registration module 25 sends a registration completion message to the front-end S-CSCF, so as to notify the front end.
  • the S-CSCF may send the received called request to the P-CSCF to carry the called service of the user terminal.
  • the present invention also provides an apparatus for realizing recovery of a called service of a terminal, as shown in Fig. 11B.
  • the device shown in Figure 11B can be a P-CSCF, the device comprising:
  • a receiving module 2 ⁇ configured to receive a called request to the user terminal
  • the receiving module 21 ′ may be specifically configured to receive a called request sent by the S-CSCF or the IBCF to the user terminal;
  • the processing module 22 is configured to, when the receiving module 21 receives the called request, determine that the registration data of the called user is not stored;
  • the sending module 23 is configured to, after the processing module 22 determines that the registration data of the called user is not stored, send a request to the PCRF that manages the user terminal to trigger the user terminal to re-initiate the IMS registration.
  • the sending module 23 is configured to send a request for carrying the re-registration identifier to the PCRF, where the re-registration identifier is used to trigger the user terminal to re-initiate the IMS registration.
  • the request to carry the re-registration identifier may be an STR or an AAR.
  • the processing module 22 is specifically configured to determine that the apparatus shown in FIG. 11B does not store registration data of the called user.
  • the P-CSCF currently registered by the user terminal is faulty, and the fault tolerance identifier is carried according to the carrying
  • the message is used to trigger the terminal to re-register the P-CSCF, and the called service of the user terminal is carried in the re-registered P-CSCF, which avoids the need for heartbeat detection between the active and standby network elements in the prior art.
  • FIG. 12 it is a schematic flowchart of a third embodiment of an apparatus for implementing recovery of a called service of a terminal according to the present invention.
  • the apparatus in the embodiment of the present invention may be a PCRF.
  • the apparatus includes: a generating module 31. And configured to generate a registration trigger request when receiving a reselection request carrying a P-CSCF reselection identifier and a username sent by the P-CSCF; the user name includes a user terminal corresponding to the called request received by the S-CSCF
  • the identifier of the user terminal of the called end may be the IP address of the user terminal as the called end, the user service authority, and other user configuration information.
  • the sending module 32 is configured to send the generated registration trigger request to the gateway connected to the user terminal indicated by the user name, so that the gateway triggers the user terminal indicated by the user name to re-register the P-CSCF to carry the Describe the called service of the user terminal;
  • the reselection request is generated by the P-CSCF according to a notification message that is sent by the S-CSCF and carries a notification message for indicating that the user terminal that is triggered by the user name re-registers the P-CSCF.
  • the generating module 31 After receiving the reselection request of the STR carrying the P-CSCF Re-Select Flag, the generating module 31 needs to execute the called service recovery process of the user terminal corresponding to the user name, that is, generate the registration trigger request, and
  • the registration trigger request is sent to the gateway of the user terminal corresponding to the username, and the gateway may be a P-GW or an S-GW, and the gateway directly triggers the user terminal to reselect the new P-CSCF.
  • the generating module 32 is specifically configured to: when receiving a reselection request that carries the P-CSCF reselection identifier and the username sent by the P-CSCF, generate a registration trigger request that carries the session # put message;
  • the session release message is used to indicate that the gateway connected to the user terminal indicated by the username requests the mobility management entity MME to delete the user bearer of the user.
  • the registration trigger request may be a RAR (Re-Auth-Request, which carries a Session-Release-Cause AVP (Attribute Length Value) (the attribute value pair of the message release reason).
  • the re-authentication request that is, the attribute field and the field value of the session release reason are carried in the RAR, indicating that the gateway requests to delete all bearers of the user terminal, and the gateway directly requests to release the IMS PDN of the user terminal corresponding to the user name.
  • the MME After the MME deletes the IMS PDN, the MME will drop the line. If the user terminal detects the access failure, it will automatically perform a new registration process to complete the registration including the P-CSCF to implement network access.
  • the user terminal initiates selection of an available third P-CSCF, and initiates a SIP initial registration to the third P-CSCF. After receiving the user registration request, the third P-CSCF completes the registration request to the S-CSCF to which the user belongs.
  • the third P-CSCF may determine, by the I-CSCF, the S-CSCF to which the user terminal belongs, and then complete the registration request to the S-CSCF to which the queried user terminal belongs.
  • the S-CSCF then sends a called request to the third P-CSCF to carry the called service.
  • the generating module 32 is specifically configured to generate a registration trigger that carries the updated P-CSCF address information when receiving the reselection request carrying the P-CSCF reselection identifier and the username sent by the P-CSCF. Request
  • the update P-CSCF address information is used to indicate that the gateway connected to the user terminal indicated by the user name generates an available P-CSCF address list and sends the information to the user terminal indicated by the user name.
  • the registration trigger request is an RAR that carries an Update P-CSCF Address request.
  • the gateway After receiving the RAR, the gateway sends an Update PDP Content Update PDP Context message to the user terminal, so that the user terminal completes the re-registration.
  • the user terminal After receiving the Update PDP Context, the user terminal updates the local P-CSCF list according to the available P-CSCF address list in the Update PDP Context, and checks whether the initial P-CSCF registered by the local end is in the list. If not, the user terminal will The process of re-registering the P-CSCF is initiated, and the third P-CSCF line that is available for selection may be selected from the new P-CSCF List ( ⁇ ' j table) delivered by the gateway to carry the called service of the user terminal.
  • the third P-CSCF may determine, by the I-CSCF, the S-CSCF to which the user terminal belongs, and then complete the registration request to the S-CSCF to which the queried user terminal belongs.
  • the S-CSCF then sends a called request to the third P-CSCF to carry the called service.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and is carried in the re-registered P-CSCF.
  • the called service of the user terminal avoids the double-master failure problem caused by the heartbeat detection between the active and standby network elements in the prior art, and the complicated processing caused by the need to externally present the same IP; Fast recovery from failures in existing network architectures.
  • FIG. 13 is a schematic flowchart of a fourth embodiment of an apparatus for implementing recovery of a called service of a terminal according to the present invention.
  • the apparatus in the embodiment of the present invention may be a gateway such as a P-GW or an S-GW, and specifically,
  • the device includes:
  • the receiving module 41 is configured to receive a registration trigger request for carrying a username sent by the policy and charging rule function entity PCRF;
  • the triggering module 42 is configured to trigger the user terminal indicated by the username to re-register the P-CSCF to carry the called service of the user terminal;
  • the registration trigger request is generated when the PCRF receives a reselection request carrying a P-CSCF reselection identifier and a username sent by the P-CSCF; the reselection request is the P-CSCF according to the S - a notification message sent by the CSCF carrying a user name and indicating a disaster recovery identifier for triggering the user terminal to re-register the P-CSCF indicated by the username.
  • the triggering module 42 may specifically include:
  • the first sending unit 421 is configured to: when the registration triggering request carries the session release message, send a release request carrying the username to the mobility management entity MME, so that the MME deletes the user terminal indicated by the username User bearer; or
  • the second sending unit 422 is configured to: when the registration trigger request carries the updated P-CSCF address information, obtain an available P-CSCF address list and send the information to the user terminal indicated by the user name, so that the user terminal The P-CSCF is selected from the list of available P-CSCF addresses and registered to the selected P-CSCF.
  • the first sending unit 421 instructs the MME to delete the IMS PDN of the user, and triggers the user terminal to re-register the new P-CSCF.
  • the second sending unit 422 obtains an Update PDP Context message, and sends an Update PDP Context message to the user terminal to trigger the user terminal according to the Update PDP.
  • the local P-CSCF list is updated in the available P-CSCF address list, and after determining that the updated local P-CSCF list does not include the initial P-CSCF registered by the local end, the new P-CSCF is selected and registered to The selected P-CSCF completes the re-registration.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • FIG. 14 is a schematic structural diagram of a fifth embodiment of an apparatus for implementing recovery of a called service of a terminal according to the present invention.
  • the apparatus of the embodiment of the present invention may be a user terminal that is a called end corresponding to a called party request, specifically
  • the device includes:
  • the registration initiation module 51 is configured to initiate a registration request to the P-CSCF when the access failure is detected, so as to carry the called service by the re-registered P-CSCF when the initial P-CSCF fails; the registration selection module 52, configured to: when receiving a list of available P-CSCF addresses sent by the gateway, select a P-CSCF from the available P-CSCF address list and register to the selected P-CSCF, so that when the initial P-CSCF fails The called service is carried by the re-registered P-CSCF.
  • the registration initiation module 51 detects that the access fails, and automatically performs a new registration process to complete registration including the P-CSCF to implement network access.
  • the registration initiation module 51 initiates selection of an available third P-CSCF, and initiates SIP initial registration to the third P-CSCF, and the third P-CSCF sends the user registration request to the S-CSCF to which the user belongs. Complete the registration request.
  • the third P-CSCF may determine, by the I-CSCF, the S-CSCF to which the user terminal belongs, and then complete the registration request to the S-CSCF to which the queried user terminal belongs.
  • the S-CSCF then sends a called request to the third P-CSCF to carry the called service.
  • the registration selection module 52 may specifically include: a determining unit, configured to determine, in the list of available P-CSCF addresses, when receiving an available P-CSCF address list sent by the gateway Whether to include the host name of the initial P-CSCF currently registered by the user terminal; a registration selection unit, if not included, selecting the P-CSCF from the list of available P-CSCF addresses And register to the selected P-CSCF.
  • the registration trigger request is an RAR carrying an Update P-CSCF Address request.
  • the gateway After receiving the RAR, the gateway sends an Update PDP Context message to the user terminal, so that the user terminal completes the re-registration.
  • the registration selection module 52 updates the local P-CSCF list according to the available P-CSCF address list in the Update PDP Context, and checks whether the initial P-CSCF registered by the local end is in the list, if not The user terminal initiates a process of re-registering the P-CSCF, and specifically selects an available third P-CSCF3 line registration from a new P-CSCF List (list) delivered by the gateway to carry the called service of the user terminal. .
  • the third P-CSCF may determine, by the I-CSCF, the S-CSCF to which the user terminal belongs, and then complete the registration request to the S-CSCF to which the queried user terminal belongs.
  • the S-CSCF then sends a called request to the third P-CSCF to carry the called service.
  • the terminal when the P-CSCF currently registered by the user terminal fails, the terminal can re-register the new P-CSCF according to the structure of the network side recovery processing based on the DR information, and carry the new P-CSCF in the new P-CSCF.
  • the called service of the user terminal avoids the double-master failure problem caused by the heartbeat detection between the active and standby network elements in the prior art, and the complicated processing caused by the need to externally present the same IP; Fast recovery from failures in existing network architectures.
  • FIG. 15 is a schematic structural diagram of a system for implementing recovery of a called service of a terminal according to an embodiment of the present invention.
  • the system of the embodiment of the present invention may specifically include: a service proxy call session control function entity S-CSCF1, at least two a proxy call session control function entity P-CSCF and a user terminal 4, wherein the at least two P-CSCFs include a second P-CSCF3 and a first P-CSCF2 currently registered by the user terminal
  • the S-CSCF is configured to query, when receiving the called request for the user terminal 4, the first P-CSCF2 currently registered by the user terminal 4; if it is detected that the first P-CSCF2 is faulty And the second P-CSCF3 is selected, and the notification message carrying the disaster tolerance identifier is sent to the second P-CSCF3, where the disaster recovery identifier is used to indicate that the available P-CSCF triggers the user terminal 4 to restart Register P-CSCF;
  • the second P-CSCF3 is configured to trigger the user terminal 4 to re-register the P-CSCF;
  • the S-CSCF is further configured to be sent by the P-CSCF that receives the re-registration of the user terminal 4.
  • the called request is sent to the re-registered P-CSCF to carry the called service of the user terminal 4;
  • the second P-CSCF triggers the user terminal to re-register the P-CSCF by using the policy and charging rule function entity PCRF.
  • the system further includes: a DNS server 5;
  • the S-CSCF is further configured to configure, in the DNS server 5, the first identifier and the second identifier according to the host name of the first P-CSCF2, where the first identifier includes the first P- The IP address of the CSCF2, the second identifier including the IP address of the second P-CSCF3.
  • system may further include: a policy and charging rule function entity PCRF6;
  • the second P-CSCF3 is specifically configured to generate, according to the notification message that carries the user name and the disaster tolerance identifier sent by the S-CSCF, a reselection request carrying the P-CSCF reselection identifier and the username, and Sending a reselection request to the PCRF6;
  • the PCRF6 is configured to: according to the P-CSCF reselection identifier, notify the user terminal 4 indicated by the username to reselect the P-CSCF to carry the called service of the user terminal 4.
  • the system may further include: a routing proxy node DRA7; the DRA7, configured to receive a reselection request sent by the second P-CSCF3, and send the reselection request Send to the PCRF6.
  • a routing proxy node DRA7 configured to receive a reselection request sent by the second P-CSCF3, and send the reselection request Send to the PCRF6.
  • system may further include: a gateway 8 connected to the user terminal 4;
  • the PCRF6 is specifically configured to: when receiving a reselection request that carries a P-CSCF reselection identifier and a username sent by the P-CSCF, generate a registration trigger request, and send the registration trigger request to the gateway 8;
  • the gateway 8 is configured to trigger the user terminal 4 indicated by the username to re-register the P-CSCF to carry the called service of the user terminal 4 according to the registration trigger request.
  • the gateway 8 is specifically configured to: when the registration triggering request carries a session release message, send a release request carrying the username to the mobility management entity MME, so that the MME Deleting the user bearer of the user terminal 4 indicated by the username; or
  • the available P-CSCF address list is sent to the user terminal 4 indicated by the user name, so that the user terminal 4 is from the available P-CSCF.
  • the P-CSCF is selected in the address list and registered to the selected P-CSCF.
  • the user terminal 4 is further configured to: when the access failure is detected, initiate a registration request to register with the P-CSCF, so as to carry the called by the re-registered P-CSCF when the initial P-CSCF fails. Or; for receiving a P-CSCF from the list of available P-CSCF addresses and registering with the selected P-CSCF when receiving the list of available P-CSCF addresses sent by the gateway 8, so that the initial P-CSCF occurs The called service is carried by the re-registered P-CSCF in case of failure.
  • the specific implementation of the foregoing user terminal 4 may refer to the description of the user terminal as the called end corresponding to the called request in the foregoing method embodiment and the device embodiment.
  • the specific implementation of the foregoing S-CSCF1 may be implemented by referring to the foregoing method.
  • the description of the S-CSCF in the device embodiment; the specific implementation of the foregoing first P-CSCF2 and the second P-CSCF3 may refer to the foregoing method embodiment and the device embodiment for the failed P-CSCF and the available
  • PCRF6 For the specific implementation of the above-mentioned PCRF6, reference may be made to the foregoing method embodiments and the description of the PCRF in the device embodiment.
  • the foregoing gateway 8 may be an S-GW or a P-GW. A description of the gateway in the device embodiment. I will not go into details here.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • a network device is further provided.
  • the network device may be an S-CSCF or an IBCF, and may include a receiving device 1200.
  • the available P-CSCF is selected, and a notification message is sent to the available P-CSCF through the transmitting device 1300 to trigger the user terminal to re-register the P-CSCF.
  • the processor 1100 may be specifically configured to send, by using the sending apparatus 1300, a notification message carrying a disaster tolerance identifier to the available P-CSCF after selecting an available P-CSCF, where The disaster recovery identifier is used to indicate that the available P-SCCF triggers the user terminal to re-register the P-CSCF.
  • the processor 1100 may be specifically configured to send, by the sending apparatus 1300, the called request of the user terminal to the available P-CSCF after selecting an available P-CSCF. In order for the available P-CSCF to determine that the registration data of the called user is not stored, the user terminal is triggered to re-initiate the IMS registration.
  • the processor 1100 is further configured to send the called request to the re-send by the sending device 1300 when the receiving device 1200 receives the registration completion message sent by the P-CSCF re-registered by the user terminal.
  • the registered P-CSCF is to carry the called service of the user terminal.
  • the available P-CSCF triggers the user terminal to re-register the P-CSCF by using the PCRF.
  • the processor 1100 is further configured to: before detecting that the initial P-CSCF fails, select an available P-CSCF, and send the notification message to the available P-CSCF, carried out:
  • the first identifier includes an IP address of the initial P-CSCF
  • the second identifier includes a P other than the initial P-CSCF - The IP address of the CSCF.
  • processor 1100 is specifically configured to perform when configuring the first identifier and the second identifier for the initial P-CSCF:
  • the first identifier and the second identifier are configured in the domain name system DNS server according to the host name of the initial P-CSCF.
  • the processor 1100 performs, if the initial P-CSCF is detected, Obscuring, selecting an available P-CSCF, and sending the notification message to the available P-CSCF, specifically for performing:
  • the P-CSCF corresponding to the second identifier is used as an available P-CSCF;
  • the processor 1100 when the processor 1100 is configured to send the called request to the re-registered P-CSCF to carry the called service of the user terminal, the processor 1100 is specifically configured to: The request is sent to the re-registered P-CSCF, so that the re-registered P-CSCF sends the called request to the user terminal to perform the called service.
  • the terminal After receiving the called party request, if the P-CSCF that is currently registered by the user terminal corresponding to the called party is faulty, the terminal triggers the terminal by generating a corresponding message carrying the disaster tolerance identifier.
  • the P-CSCF is re-registered, and the called service of the user terminal is carried in the re-registered P-CSCF, which avoids the problem of double master failure caused by the heartbeat detection between the active and standby NEs in the prior art. Due to the need to externally present the same IP to handle the complex problems; and can quickly complete the failure recovery in the existing network architecture.
  • an embodiment of the present invention provides another network device.
  • the network device may be a P-CSCF, which may include a receiving device 2200.
  • the notification message further includes a disaster tolerance identifier, generating a reselection request carrying the P-CSCF reselection identifier and the username;
  • the notification message carrying the disaster tolerant identifier is generated by the S-CSCF when the P-CSCF registered by the user terminal corresponding to the received called request is faulty, and the disaster recovery identifier is used to indicate the triggering location.
  • the user terminal re-registers the P-CSCF.
  • the processor 2100 when the processor 2100 sends the reselection request to the policy and charging rule function entity PCRF of the user terminal indicated by the user name, the processor 2100 is specifically configured to: perform the reselection request Sending to the routing proxy node DRA, so that the DRA sends the reselection request to the user terminal indicated by the user name according to the username in the reselection request.
  • the processor 2100 is further configured to perform, before performing the re-selection request to include the P-CSCF reselection identifier and the username, if the resolving identifier is further included in the notification message, Determining whether the user terminal indicated by the username is registered at the local end;
  • the re-selection request that includes the P-CSCF reselection identifier and the username is generated.
  • processor 2100 is further configured to:
  • the registration completion message is sent to the S-CSCF to which the user terminal belongs to complete the registration of the user terminal.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • the present invention also provides an apparatus for realizing recovery of a called service of a terminal, as shown in Fig. 17B.
  • the device shown in FIG. 17B may be a P-CSCF, and the device includes a receiving device 2200, a processor 2100, and a transmitting device 2300, where the processor 2100 is configured to perform:
  • the sending device 2300 sends a request to the PCRF managing the user terminal to trigger the user terminal to re-initiate the IMS registration.
  • the processor 2100 receives, by the receiving device 2200, a called request sent by the S-CSCF or the IBCF to the user terminal.
  • the processor 2100' may be configured to send, by using the sending device 2300', a request for carrying the re-registration identifier to the PCRF, where the re-registration identifier is used to trigger the user terminal to re-initiate the IMS registration.
  • the request for carrying the re-registration identifier may be an STR or an AAR.
  • the processor 2100 is specifically configured to determine that the device shown in FIG. 17B does not store the registration data of the called user when determining that the registration data of the called user is not stored.
  • the embodiment of the present invention further provides another network device.
  • the network device may be a PCRF, which may include a receiving device 3200, and And a sending device 3300, where the processor 3100 is configured to execute:
  • a registration trigger request is generated
  • the reselection request is generated by the P-CSCF according to a notification message that is sent by the S-CSCF and carries a notification message for indicating that the user terminal that is triggered by the user name re-registers the P-CSCF.
  • the processor 3100 generates a registration trigger request when performing a reselection request that carries the P-CSCF reselection identifier and the username sent by the P-CSCF, specifically for performing: when receiving the P Generating a registration trigger request carrying a session release message when the reselection request carrying the P-CSCF reselection identifier and the username is sent by the CSCF;
  • the session release message is used to indicate that the gateway connected to the user terminal indicated by the user name requests the mobility management entity to delete the user bearer of the user.
  • the processor 3100 generates a registration trigger request when performing the reselection request that carries the P-CSCF reselection identifier and the username sent by the P-CSCF, specifically for performing: when receiving When the P-CSCF sends a reselection request carrying the P-CSCF reselection identifier and the username, generating a registration trigger request carrying the updated P-CSCF address information;
  • the update P-CSCF address information is used to indicate that the gateway connected to the user terminal indicated by the user name generates an available P-CSCF address list and sends the information to the user terminal indicated by the user name.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • the embodiment of the present invention further provides another network device.
  • the network device may be an S-GW or a P-GW.
  • the receiving device 4200 When the receiving device 4200 receives the registration trigger request carrying the username sent by the policy and charging rule function entity PCRF, triggering the user terminal indicated by the username to re-register the P-CSCF to carry the called terminal of the user terminal.
  • the registration trigger request is generated when the PCRF receives a reselection request carrying a P-CSCF reselection identifier and a username sent by the P-CSCF; the reselection request is the P-CSCF according to the S - a notification message sent by the CSCF carrying a user name and indicating a disaster recovery identifier for triggering the user terminal to re-register the P-CSCF indicated by the username.
  • the processor 4100 re-registers the P-CSCF by performing the triggering of the user terminal indicated by the username, specifically for performing:
  • the available P-CSCF address list is sent to the user terminal indicated by the user name, so that the user terminal is from the available P-CSCF address list.
  • the P-CSCF is selected and registered to the selected P-CSCF.
  • the P-CSCF currently registered by the user terminal is faulty, and the terminal is triggered to re-register the P-CSCF according to the message carrying the disaster tolerance identifier, and the called terminal of the user terminal is carried in the re-registered P-CSCF.
  • the service avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing problem caused by the need to externally present the same IP; and can be in the existing network architecture. Complete fault recovery quickly.
  • the embodiment of the present invention further provides a user equipment.
  • the user equipment includes a receiving device 5200, a processor 5100, and a sending device 5300, where the processing is performed.
  • the device 5100 is configured to execute:
  • a registration request to the P-CSCF is initiated by the transmitting device 5300, so as to carry the called service through the re-registered P-CSCF when the initial P-CSCF fails; when the receiving When the device 5200 receives the list of available P-CSCF addresses sent by the gateway, selects the P-CSCF from the available P-CSCF address list and registers with the selected P-CSCF, so as to re-register when the initial P-CSCF fails.
  • the P-CSCF carries the called service.
  • the processor 5100 when receiving the list of available P-CSCF addresses sent by the gateway, selects a P-CSCF from the available P-CSCF address list and registers with the selected P-CSCF, specifically For execution:
  • the gateway When receiving the available P-CSCF address list sent by the gateway, determining whether the available P-CSCF address list includes the host name of the initial P-CSCF currently registered by the user terminal;
  • the terminal when the P-CSCF currently registered by the user terminal fails, the terminal can re-register the new P-CSCF according to the structure of the recovery processing based on the DR-based message on the network side, and in the new
  • the P-CSCF carries the called service of the user terminal, which avoids the double-master failure problem caused by the heartbeat detection between the active and standby NEs in the prior art, and the complicated processing caused by the need to externally present the same IP.
  • the problem and the ability to quickly complete failure recovery in the existing network architecture.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Abstract

公开了一种实现终端被叫业务恢复的方法、相关装置及系统,其中,所述方法包括:当接收到对用户终端的被叫请求时,査询所述用户终端当前注册的初始代理呼叫会话控制功能实体P-CSCF;若检测到所述初始P-CSCF发生故障,选择可用的P-CSCF,并向所述可用的P-CSCF发送携带容灾标识的通知消息,所述容灾标识用于指示所述可用的P-CSCF触发所述用户终端重新注册P-CSCF;在接收到所述用户终端重新注册的P-CSCF发送的注册完成消息时,将所述被叫请求下发给所述重新注册的P-CSCF以承载所述用户终端的被叫业务。通过以上方案能够在现有的网络架构中快速完成故障恢复。

Description

一种实现终端被叫业务恢复的方法、 相关装置及系统 本申请要求于 2013年 8月 7日提交中国专利局、申请号为 201310342761.0、 发明名称为"一种实现终端被叫业务恢复的方法、相关装置及系统"的中国专利申 请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域, 尤其涉及一种实现终端被叫业务恢复的方法、 相关装置及系统。
背景技术
CSCF ( Call Session Control Function, 呼叫会话控制功能)是 IP多媒体子 系统(IP Multimedia Subsystem, IMS ) 中的功能实体, 主要负责处理多媒体呼 叫会话过程中的信令控制。 CSCF可以分为 P-CSCF (Proxy CSCF, 代理 CSCF), I-CSCF (Interrogating CSCF, 查询 CSCF), S-CSCF (Serving CSCF,月良务 CSCF)。
在业务控制过程中, 若 P-CSCF发生故障, 经过该 P-CSCF注册的用户终端 如果作为被叫, S-CSCF在对该被叫业务进行管理时, 发现了该 P-SCCF故障, 则就无法通过 P-CSCF联系到终端用户, 导致业务失败。
现有技术中, 通过两个 P-CSCF组成主备, 当一个 P-CSCF故障时, 业务可 以由备用 P-CSCF接管。 在 P-CSCF1和 P-CSCF2配置相同的 IP地址 IP1 , 通常 情况下, P-CSCF1对外发布自己的路由, 而 P-CSCF2则不发布自己的地址。 首 先, 用户终端向 IP1发送注册请求, 注册到主用的 P-CSCF1 , P-CSCF1将用户 注册信息同时备份到备用的 P-CSCF2上。 在 P-CSCF1故障时, P-CSCF2能够通 过心跳感知到 P-CSCF1故障, 这时 P-CSCF2将对外发布自身路由, 之后终端的 业务将被路由到 P-CSCF2进行处理。由于原来注册时用户的信息已经进行备份, 新的 P-CSCF2上将能够正确处理用户的请求。 现有技术中, 釆用主备数据备份的解决方案的主要缺点包括: 主备网元之 间通过心跳检测, 容易造成双主故障, 导致主备网元都无法进行业务; 且主备 网元来对外呈现同一 IP, 需要近端路由器支持, 处理较为复杂。
发明内容
本发明实施例所要解决的技术问题在于, 提供一种实现终端被叫业务恢复 的方法、相关装置及系统,可在 P-CSCF发生故障时快速地恢复用户终端的被叫 业务。
第一方面, 本发明实施例提供了一种实现终端被叫业务恢复的方法, 包括: 当接收到对用户终端的被叫请求时, 查询所述用户终端当前注册的初始代 理呼叫会话控制功能实体 P-CSCF;
若检测到所述初始 P-CSCF发生故障, 选择可用的 P-CSCF, 并向所述可用 的 P-CSCF发送通知消息, 以触发所述用户终端重新注册 P-CSCF;
其中,所述可用的 P-CSCF通过策略与计费规则功能实体 PCRF触发所述用 户终端重新注册 P-CSCF。
在第一方面的第一种可能的实现方式中,所述向所述可用的 P-CSCF发送通 知消息, 以触发所述用户终端重新注册 P-CSCF, 包括: 向所述可用的 P-CSCF发送携带容灾标识的通知消息,所述容灾标识用于指 示所述可用的 P-SCCF触发所述用户终端重新注册 P-CSCF。
在第一方面的第二种可能的实现方式中,所述向所述可用的 P-CSCF发送通 知消息, 以触发所述用户终端重新注册 P-CSCF, 包括: 向所述可用的 P-CSCF发送所述用户终端的被叫请求;
所述可用的 P-CSCF确定没有存储被叫用户的注册数据时,触发所述用户终 端重新发起 IMS注册。 第二方面, 本发明实施例还提供了另一种实现终端被叫 业务恢复的方法, 包括:接收服务呼叫会话控制功能实体 S-CSCF发送的携带用 户名的通知消息;
若解析到所述通知消息中还包括容灾标识,生成携带 P-CSCF重选标识和所 述用户名的重选请求; 向管理所述用户名所指示的用户终端的策略与计费规则功能实体 PCRF发 送所述重选请求,以使所述 PCRF根据所述 P-CSCF重选标识通知所述用户名所 指示的用户终端重选 P-CSCF以承载所述用户终端的被叫业务;
其中,携带所述容灾标识的通知消息是所述 S-CSCF在接收到的被叫请求对 应的用户终端所注册的 P-CSCF发生故障时生成的,所述容灾标识用于指示触发 所述用户终端重新注册 P-CSCF。
结合第二方面, 在第一种可能的实现方式中, 所述向管理所述用户名所指 示的用户终端的策略与计费规则功能实体 PCRF发送所述重选请求, 包括: 将所述重选请求发送给路由代理节点 DRA, 以使所述 DRA根据所述重选 请求中的用户名将所述重选请求发送给管理所述用户名所指示的用户终端的 PCRF。
结合第二方面, 或者第二方面的第一种可能的实现方式, 在第二种可能的 实现方式中, 在若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF 重选标识和所述用户名的重选请求之前, 还包括:
判断所述用户名所指示的用户终端是否在本端注册;
若未在本端注册, 则执行所述若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求。
结合第二方面, 或者第二方面的第一种可能的实现方式, 或者第二方面的 第二种可能的实现方式, 在第三种可能的实现方式中, 还包括:
当接收到用户终端的注册请求时,向所述用户终端所属的 S-CSCF发送注册 完成消息以完成用户终端的注册登记。
第三方面, 本发明实施例还提供了又一种实现终端被叫业务恢复的方法, 包括:
当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生 成注册触发请求;
向与所述用户名所指示的用户终端相连的网关发送所述生成的注册触发请 求,以使所述网关触发所述用户名所指示的用户终端重新注册 P-CSCF以承载所 述用户终端的被叫业务;
其中,所述重选请求是所述 P-CSCF根据 S-CSCF发送的携带用户名和用于 指示触发所述用户名所指示的用户终端重新注册 P-CSCF 的容灾标识的通知消 息生成的。
结合第三方面,在第一种可能的实现方式中, 所述当接收到 P-CSCF发送的 携带 P-CSCF重选标识和用户名的重选请求时, 生成注册触发请求, 包括: 当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生 成携带会话释放消息的注册触发请求;
其中, 所述会话释放消息用于指示与所述用户名所指示的用户终端相连的 网关请求移动管理实体 MME删除用户的用户承载。
结合第三方面,在第一种可能的实现方式中, 所述当接收到 P-CSCF发送的 携带 P-CSCF重选标识和用户名的重选请求时, 生成注册触发请求, 包括: 当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生 成携带更新 P-CSCF地址信息的注册触发请求;
其中,所述更新 P-CSCF地址信息用于指示与所述用户名所指示的用户终端 相连的网关生成可用 P-CSCF地址列表发送给所述用户名所指示的用户终端。
第四方面, 本发明实施例还提供了再一种实现终端被叫业务恢复的方法, 包括:
在接收到策略与计费规则功能实体 PCRF发送的携带用户名的注册触发请 求时,触发所述用户名所指示的用户终端重新注册 P-CSCF以承载所述用户终端 的被叫业务;
其中,所述注册触发请求是所述 PCRF在接收到 P-CSCF发送的携带 P-CSCF 重选标识和用户名的重选请求时生成的; 所述重选请求是所述 P-CSCF 根据 S-CSCF 发送的携带用户名和用于指示触发所述用户名所指示的用户终端重新 注册 P-CSCF的容灾标识的通知消息生成的。
结合第四方面, 在第一种可能的实现方式中, 所述触发所述用户名所指示 的用户终端重新注册 P-CSCF , 包括: 当所述注册触发请求中携带有会话释放消息时,向移动管理实体 MME发送 携带所述用户名的释放请求 ,以使所述 MME删除所述用户名所指示用户终端的 用户承载; 或者
当所述注册触发请求中携带有更新 P-CSCF地址信息时, 获取可用 P-CSCF 地址列表发送给所述用户名所指示的用户终端, 以使所述用户终端从所述可用 P-CSCF地址列表中选择 P-CSCF并注册到该选择的 P-CSCF。
第五方面, 本发明实施例还提供了再一种实现终端被叫业务恢复的方法, 包括:
当检测到接入失败时, 发起注册到 P-CSCF 的注册请求, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务;
当接收到网关发送的可用 P-CSCF地址列表时,从所述可用 P-CSCF地址列 表选择 P-CSCF并注册到选择的 P-CSCF , 以便于在初始 P-CSCF发生故障时通 过重新注册的 P-CSCF承载被叫业务。
结合第五方面, 在第一种可能的实现方式中, 所述当接收到网关发送的可 用 P-CSCF地址列表时, 从所述可用 P-CSCF地址列表选择 P-CSCF并注册到选 择的 P-CSCF, 包括:
当接收到网关发送的可用 P-CSCF地址列表时,判断所述可用 P-CSCF地址 列表中是否包括本用户终端当前注册的初始 P-CSCF的主机名;
若不包括, 从所述可用 P-CSCF 地址列表选择 P-CSCF 并注册到选择的 P-CSCF。
第六方面, 本发明实施例提供了一种实现终端被叫业务恢复的装置, 包括: 查询模块, 用于当接收到对用户终端的被叫请求时, 查询所述用户终端当 前注册的初始代理呼叫会话控制功能实体 P-CSCF;
处理模块,用于若检测到所述初始 P-CSCF发生故障,选择可用的 P-CSCF, 并向所述可用的 P-CSCF发送通知消息,以触发所述用户终端重新注册 P-CSCF; 其中,所述可用的 P-CSCF通过策略与计费规则功能实体 PCRF触发所述用 户终端重新注册 P-CSCF。 结合第六方面, 在第一种可能的实现方式中, 所述处理模块具体用于在选 择可用的 P-CSCF后, 向所述可用的 P-CSCF发送携带容灾标识的通知消息, 所 述容灾标识用于指示所述可用的 P-SCCF触发所述用户终端重新注册 P-CSCF。
结合第六方面的第一种可能的实现方式, 在第二种可能的实现方式中, 所 述处理模块具体用于在选择可用的 P-CSCF后,向所述可用的 P-CSCF发送所述 用户终端的被叫请求,以便所述可用的 P-CSCF确定没有存储被叫用户的注册数 据时, 触发所述用户终端重新发起 IMS注册。
第七方面, 本发明实施例还提供了另一种实现终端被叫业务恢复的装置, 包括:
接收模块,用于接收服务呼叫会话控制功能实体 S-CSCF发送的携带用户名 的通知消息;
处理模块, 用于若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求;
发送模块, 用于向管理所述用户名所指示的用户终端的策略与计费规则功 能实体 PCRF发送所述重选请求,以使所述 PCRF根据所述 P-CSCF重选标识通 知所述用户名所指示的用户终端重选 P-CSCF以 载所述用户终端的被叫业务; 其中,携带所述容灾标识的通知消息是所述 S-CSCF在接收到的被叫请求对 应的用户终端所注册的 P-CSCF发生故障时生成的,所述容灾标识用于指示触发 所述用户终端重新注册 P-CSCF。
结合第七方面, 在第一种可能的实现方式中, 所述发送模块, 具体用于将 所述重选请求发送给路由代理节点 DRA, 以使所述 DRA根据所述重选请求中 的用户名将所述重选请求发送给管理所述用户名所指示的用户终端的 PCRF。
结合第七方面, 或者第七方面的第一种可能的实现方式, 在第二种可能的 实现方式中, 还包括:
判断模块, 用于判断所述用户名所指示的用户终端是否在本端注册, 并在 判断结果为未在本端注册, 则通知所述处理模块执行所述若解析到所述通知消 息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求。 结合第七方面, 或者第七方面的第一种可能的实现方式, 或者第七方面的 第二种可能的实现方式, 在第三种可能的实现方式中, 还包括:
注册模块, 用于当接收到用户终端的注册请求时, 向所述用户终端所属的
S-CSCF发送注册完成消息以完成用户终端的注册登记。
第八方面, 本发明实施例还提供了又一种实现终端被叫业务恢复的装置, 包括:
生成模块,用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的 重选请求时, 生成注册触发请求;
发送模块, 用于向与所述用户名所指示的用户终端相连的网关发送所述生 成的注册触发请求, 以使所述网关触发所述用户名所指示的用户终端重新注册 P-CSCF以 载所述用户终端的被叫业务;
其中,所述重选请求是所述 P-CSCF根据 S-CSCF发送的携带用户名和用于 指示触发所述用户名所指示的用户终端重新注册 P-CSCF 的容灾标识的通知消 息生成的。
结合第八方面, 在第一种可能的实现方式中, 所述生成模块, 具体用于当 接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生成携带 会话释放消息的注册触发请求;
其中, 所述会话释放消息用于指示与所述用户名所指示的用户终端相连的 网关请求移动管理实体 MME删除用户的用户承载。
结合第八方面, 在第二种可能的实现方式中, 所述生成模块, 具体用于当 接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生成携带 更新 P-CSCF地址信息的注册触发请求;
其中,所述更新 P-CSCF地址信息用于指示与所述用户名所指示的用户终端 相连的网关生成可用 P-CSCF地址列表发送给所述用户名所指示的用户终端。
第九方面, 本发明实施例还提供了再一种实现终端被叫业务恢复的装置, 包括:
接收模块, 用于接收到策略与计费规则功能实体 PCRF发送的携带用户名 的注册触发请求;
触发模块,用于触发所述用户名所指示的用户终端重新注册 P-CSCF以承载 所述用户终端的被叫业务;
其中,所述注册触发请求是所述 PCRF在接收到 P-CSCF发送的携带 P-CSCF 重选标识和用户名的重选请求时生成的; 所述重选请求是所述 P-CSCF 根据 S-CSCF 发送的携带用户名和用于指示触发所述用户名所指示的用户终端重新 注册 P-CSCF的容灾标识的通知消息生成的。
结合第九方面, 在第一种可能的实现方式中, 所述触发模块包括: 第一发送单元, 用于当所述注册触发请求中携带有会话释放消息时, 向移 动管理实体 MME发送携带所述用户名的释放请求,以使所述 MME删除所述用 户名所指示用户终端的用户承载; 或者
第二发送单元, 用于当所述注册触发请求中携带有更新 P-CSCF 地址信息 时,获取可用 P-CSCF地址列表发送给所述用户名所指示的用户终端, 以使所述 用户终端从所述可用 P-CSCF 地址列表中选择 P-CSCF 并注册到该选择的 P-CSCF。
第十方面, 本发明实施例还提供了再一种实现终端被叫业务恢复的装置, 包括:
注册发起模块,用于当检测到接入失败时,发起注册到 P-CSCF的注册请求, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务;
注册选择模块,用于当接收到网关发送的可用 P-CSCF地址列表时,从所述 可用 P-CSCF地址列表选择 P-CSCF 并注册到选择的 P-CSCF, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务。
结合第十方面, 在第一种可能的实现方式中, 所述注册选择模块包括: 判断单元,用于当接收到网关发送的可用 P-CSCF地址列表时,判断所述可 用 P-CSCF地址列表中是否包括本用户终端当前注册的初始 P-CSCF的主机名; 注册选择单元, 用于若不包括, 从所述可用 P-CSCF地址列表选择 P-CSCF 并注册到选择的 P-CSCF。 第十一方面, 本发明实施例还提供了一种实现终端被叫业务恢复的系统, 包括: 服务代理呼叫会话控制功能实体 S-CSCF、 至少两个代理呼叫会话控制功 能实体 P-CSCF以及用户终端,其中,所述至少两个 P-CSCF中包括第二 P-CSCF 和所述用户终端当前注册的第一 P-CSCF, 其中
所述 S-CSCF, 用于当接收到对所述用户终端的被叫请求时, 查询所述用户 终端当前注册的第一 P-CSCF; 若检测到所述第一 P-CSCF发生故障, 选择所述 第二 P-CSCF , 并向所述第二 P-CSCF发送携带容灾标识的通知消息, 所述容灾 标识用于指示所述可用的 P-CSCF触发所述用户终端重新注册 P-CSCF;
所述第二 P-CSCF, 用于触发所述用户终端重新注册 P-CSCF;
所述 S-CSCF, 还用于在接收到所述用户终端重新注册的 P-CSCF发送的注 册完成消息时,将所述被叫请求下发给所述重新注册的 P-CSCF以承载所述用户 终端的被叫业务;
其中,所述第二 P-CSCF具体通过策略与计费规则功能实体 PCRF触发所述 用户终端重新注册 P-CSCF。
结合第十一方面, 在第一种可能的实现方式中, 还包括: DNS服务器; 所述 S-CSCF, 还用于在所述 DNS服务器中根据所述第一 P-CSCF的主机 名配置第一标识和第二标识, 其中, 所述第一标识包括所述第一 P-CSCF的 IP 地址, 所述第二标识包括所述第二 P-CSCF的 IP地址。
结合第十一方面, 或者第十一方面的第一种可能的实现方式中, 在第二种 可能的实现方式中, 还包括: 策略与计费规则功能实体 PCRF;
所述第二 P-CSCF, 具体用于根据所述 S-CSCF发送的携带用户名和容灾标 识的通知消息,生成携带 P-CSCF重选标识和所述用户名的重选请求, 并将所述 重选请求发送给所述 PCRF;
所述 PCRF , 用于根据所述 P-CSCF重选标识通知所述用户名所指示的用户 终端重选 P-CSCF以 载所述用户终端的被叫业务。
结合第十一方面的第二种可能的实现方式, 在第三种可能的实现方式中, 还包括: 路由代理节点 DRA; 所述 DRA, 用于接收所述第二 P-CSCF发送的重选请求, 并将所述重选请 求发送给所述 PCRF。
结合第十一方面的第二种可能的实现方式, 或者第十一方面的第三种可能 的实现方式, 在第四种可能的实现方式中, 所述系统还包括: 与所述用户终端 相连的网关;
所述 PCRF, 具体用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用 户名的重选请求时, 生成注册触发请求, 并向所述网关发送所述注册触发请求; 所述网关, 用于根据所述注册触发请求触发所述用户名所指示的用户终端 重新注册 P-CSCF 以 载所述用户终端的被叫业务。
结合第十一方面的第四种可能的实现方式, 在第五种可能的实现方式中, 所述网关, 具体用于当所述注册触发请求中携带有会话释放消息时, 向移 动管理实体 MME发送携带所述用户名的释放请求,以使所述 MME删除所述用 户名所指示用户终端的用户承载; 或者
当所述注册触发请求中携带有更新 P-CSCF地址信息时, 获取可用 P-CSCF 地址列表发送给所述用户名所指示的用户终端, 以使所述用户终端从所述可用 P-CSCF地址列表中选择 P-CSCF并注册到该选择的 P-CSCF。
结合第十一方面的第五种可能的实现方式, 在第六种可能的实现方式中, 所述用户终端,还用于当检测到接入失败时,发起注册到 P-CSCF的注册请 求, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务; 或者用于当接收到网关发送的可用 P-CSCF地址列表时,从所述可用 P-CSCF地 址列表选择 P-CSCF并注册到选择的 P-CSCF, 以便于在初始 P-CSCF发生故障 时通过重新注册的 P-CSCF 载被叫业务。
第十二方面, 本发明实施例提供一种实现终端被叫业务恢复的方法, 包括: 接收对用户终端的被叫请求;
确定没有存储被叫用户的注册数据;
向管理所述用户终端的策略与计费规则功能实体 PCRF发送触发所述用户 终端重新发起 IMS注册的请求。 第十三发明, 本发明实施例提供一种实现终端被叫业务恢复的装置, 包括: 接收模块, 用于接收对用户终端的被叫请求;
处理模块, 用于在接收模块接收到所述被叫请求时, 确定没有存储被叫用 户的注册数据; 发送模块, 用于在所述处理模块确定没有存储所述被叫用户的注册数据后, 向管理所述用户终端的 PCRF发送触发所述用户终端重新发起 IMS注册的请求。 本发明实施例接收到被叫请求后, 如果检测到该被叫请求对应的用户终端 当前注册的 P-CSCF发生故障,通过生成相应的携带容灾标识的消息来最终触发 终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载该用户终端的被叫 业务, 避免了现有技术中由于主备网元之间需要通过心跳检测所导致的双主故 障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问题; 并且能够在现 有的网络架构中快速完成故障恢复。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实施 例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述 中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付 出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1是本发明的实现终端被叫业务恢复的方法的第一实施例流程示意图; 图 2A是本发明的实现终端被叫业务恢复的方法的第二实施例的流程示意 图;
图 2B是本发明实施例提供的一种实现终端被叫业务恢复的方法的流程示意 图;
图 3是本发明的实现终端被叫业务恢复的方法的第三实施例流程示意图; 图 4是本发明的实现终端被叫业务恢复的方法的第四实施例流程示意图; 图 5是本发明的实现终端被叫业务恢复的方法的第五实施例的流程示意图; 图 6是本发明的实现终端被叫业务恢复的方法的第六实施例的流程示意图; 图 Ί是本发明的实现终端被叫业务恢复的方法的第七实施例的流程示意图; 图 8是本发明实施例提供的一种实现终端被叫业务恢复的方法的流程示意 图;
图 9是本发明实施例提供的一种实现终端被叫业务恢复的方法的流程示意 图;
图 10是本发明的实现终端被叫业务恢复的装置的第一实施例结构示意图; 图 11A是本发明的实现终端被叫业务恢复的装置的第二实施例流程示意 图;
图 11B是本发明实施例提供的实现终端被叫业务恢复的装置的结构示意图; 图 12是本发明的实现终端被叫业务恢复的装置的第三实施例流程示意图; 图 13是本发明的实现终端被叫业务恢复的装置的第四实施例流程示意图; 图 14是本发明的实现终端被叫业务恢复的装置的第五实施例结构示意图; 图 15是本发明实施例的实现终端被叫业务恢复的系统的结构示意图 图 16是本发明实施例的一种网络设备的结构示意图;
图 17A是本发明实施例的另一种网络设备的结构示意图;
图 17B是本发明实施例提供的一种实现终端被叫业务恢复的装置的结构示 意图;
图 18是本发明实施例的又一种网络设备的结构示意图;
图 19是本发明实施例的又一种网络设备的结构示意图;
图 20是本发明实施例的用户设备的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
用户通过用户终端进行被叫业务时, 如果该用户终端当前注册的 P-CSCF 故障, 通过 P-CSCF POOL ( P-CSCF池 )中其他 P-CSCF触发该用户终端重新注 册新的 P-CSCF。
请参见图 1 ,是本发明的实现终端被叫业务恢复的方法的第一实施例流程示 意图,本发明实施例的所述方法具体可在 S-CSCF或 IBCF( Interconnection Border Control Function, 互通边界控制功能)中实现, 具体的, 本发明实施例的所述方 法包括:
S101 : 当接收到对用户终端的被叫请求时, 查询所述用户终端当前注册的 初始代理呼叫会话控制功能实体 P-CSCF。
用户终端在注册到 P-CSCF 后, P-CSCF会将相应的注册完成信息发送给 S-CSCF, 由 S-CSCF进行认证、 鉴权, 并执行登记用户终端的用户名以及其注 册的 P-CSCF的主机名等处理, 因此, S-CSCF根据接收到的被叫请求对应的用 户终端的用户名,可以查询并确定所述用户终端当前注册的初始 P-CSCF。其中, 所述用户终端的用户名用于标识所述用户终端 ,具体可以该用户终端的 IP地址、 用户业务权限以及其他用户配置信息等。
S102: 若检测到所述初始 P-CSCF发生故障, 选择可用的 P-CSCF, 并向所 述可用的 P-CSCF发送通知消息, 以触发所述用户终端重新注册 P-CSCF。
S-CSCF具体可以通过心跳机制与当前的 P-CSCF POOL中的每一个 P-CSCF 进行心跳检测, 根据心跳检测的数据或者根据是否能正常接收到心跳数据来判 定所述用户终端当前注册的初始 P-CSCF是否发生故障, 例如在 ping命令(一 种用来检查网络是否通畅或者网络连接速度的命令) 不通, 或者检测的消息收 发失败时可确定该初始 P-CSCF发生故障。
其中, 可以采用下面任一方方式向所述可用的 P-CSCF发送通知消息, 以实 现触发所述用户终端重新注册 P-CSCF的目的:
方式一: 向所述可用的 P-CSCF发送携带容灾标识的通知消息, 所述容灾标 识用于指示所述可用的 P-SCCF触发所述用户终端重新注册 P-CSCF;
方式二: 向所述可用的 P-CSCF发送所述用户终端的被叫请求; 所述可用的 P-CSCF确定没有存储被叫用户的注册数据时,触发所述用户终端重新发起 IMS 注册。在方式二中,通知消息具体为所述被叫请求。可选地,所述可用的 P-CSCF 确定所述可用的 P-CSCF中没有存储被叫用户的注册数据时 ,触发所述用户终端 重新发起 IMS注册。 所述被叫用户是使用所述用户终端的、 被呼叫的用户。
需要说明的是,所谓触发所述用户终端重新注册 P-CSCF是指触发所述用户 终端重新发起 IMS注册。
当检测到所述初始 P-CSCF发生故障时, 从当前的 P-CSCF POOL中选择一 个可用的 P-CSCF, 该可用的 P-CSCF可以是通过心跳检测等方式已确定为没有 故障的 P-CSCF。
具体的,在本发明实施例中, 可以预先为所述初始 P-CSCF配置两个标识即 第一标识和第二标识, 其中, 所述第一标识包括所述初始 P-CSCF的 IP地址, 所述第二标识包括除所述初始 P-CSCF外的 P-CSCF的 IP地址。 第一标识为所 述初始 P-CSCF发布的 IP地址, 所述第二标识则是所述 P-CSCF POOL中除所 述初始 P-CSCF外的其他 P-CSCF的 IP地址(对应于 S102中的可用的 P-CSCF ), 在所述 S102中检测到初始 P-CSCF发生故障时, 根据配置的第二标识可以直接 向可用的 P-CSCF发送所述通知消息。
上述为所述初始 P-CSCF配置的两个标识具体可以是在 DNS( Domain Name System, 域名系统)服务器中根据所述初始 P-CSCF的主机名配置第一标识和第 二标识。
而所述 S102具体则可以包括: 获取为所述初始 P-CSCF配置的第一标识和 第二标识, 具体可以是到 DNS服务器中以该初始 P-CSCF的主机名进行查询获 得第二标识和第二标识; 若根据获取的所述第一标识检测到所述第一标识对应 的初始 P-CSCF发生故障,将所述第二标识对应的 P-CSCF作为可用的 P-CSCF, 如通过所述第一标识发送心跳消息, 如没有正常接收到响应消息, 则可确定所 述第一标识对应的初始 P-CSCF发生故障; 根据所述第二标识向可用的 P-CSCF 发送所述通知消息。 即根据所述配置的第二标识发送所述通知消息。 需要说明 的是, 在所述通知消息中还携带有所述用户终端的用户名, 以便于所述可用的 P-CSCF根据该用户名发起触发所述用户终端重新注册 P-CSCF的流程。 S103: 可选地,在接收到所述用户终端重新注册的 P-CSCF发送的注册完成 消息时,将所述被叫请求下发给所述重新注册的 P-CSCF以承载所述用户终端的 被叫业务。其中,所述可用的 P-CSCF通过策略与计费规则功能实体 PCRF( Policy and Charging Rules Function, 策略与计费规则功能实体)触发所述用户终端重新 注册 P-CSCF。
所述可用的 P-CSCF可以才艮据通知消息中的容灾标识,得知所述用户终端注 册的当前 P-CSCF发生故障,则发起触发所述用户终端重新注册 P-CSCF的流程。 具体的,所述可用的 P-CSCF可以通过管理所述用户终端的策略与计费规则功能 实体 PCRF、与所述用户终端相连的网关的路径通知所述用户终端重新注册新的 P-CSCF , 以便于 S-CSCF 将所述被叫请求下发给该新的 P-CSCF , 由该新的 P-CSCF承载该用户终端的被叫业务。 所述可用的 P-CSCF也可以在接收到用户 终端的被叫请求时, 当确定所述可用的 P-CSCF 没有存储被叫用户的注册数据 时,确定所述用户终端注册的当前 P-CSCF发送故障, 需要发起触发所述用户终 端重新注册 P-CSCF的流程。
进一步的,所述将所述被叫请求下发给所述重新注册的 P-CSCF以承载所述 用户终端的被叫业务, 包括: 将所述被叫请求发送给所述重新注册的 P-CSCF, 以使所述重新注册的 P-CSCF将该被叫请求发送给所述用户终端执行被叫业务。 即 S-CSCF将被叫请求发送给所述重新注册的 P-CSCF, 然后由所述重新注册的 P-CSCF将该被叫请求发送给所述用户终端, 完成被叫业务。
本发明实施例在接收到被叫请求后, 如果检测到该被叫请求对应的用户终 端当前注册的 P-CSCF发生故障,通过生成相应的携带容灾标识的消息来最终触 发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载该用户终端的被 叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检测所导致的双主 故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问题; 并且能够在 现有的网络架构中快速完成故障恢复。
再请参见图 2A, 是本发明的实现终端被叫业务恢复的方法的第二实施例的 流程示意图, 本发明实施例的所述方法可以是在 P-CSCF中实现, 由 P-CSCF根 据前端的 S-CSCF发送的通知消息触发用户终端重新注册 P-CSCF。 具体的, 在 本发明实施例中的所述方法包括:
S201 :接收服务呼叫会话控制功能实体 S-CSCF发送的携带用户名的通知消 息;所述的用户名包括所述 S-CSCF接收到的被叫请求对应的用户终端的标识即 被叫段的用户终端标识, 具体可以为该作为被叫端的用户终端的 IP地址、 用户 业务权限以及其他用户配置信息等。
S202: 若解析到所述通知消息中还包括容灾标识,生成携带 P-CSCF重选标 识和所述用户名的重选请求;
其中,携带所述容灾标识的通知消息是所述 S-CSCF接收到的被叫请求对应 的用户终端所注册的 P-CSCF发生故障时生成的,所述容灾标识用于指示触发所 述用户终端重新注册 P-CSCF。 即作为被叫端的用户终端注册的 P-CSCF发生故 障时, 触发进行重新注册的流程。
所述 S-CSCF 生成包括容灾标识的通知消息的过程可参考上述方法的第一 实施例中的描述。 本发明实施例中由 P-CSCF POOL中一个 P-CSCF执行相关步 骤, 该 P-CSCF对应于上述第一实施例中的可用的 P-CSCF。
而若在所述 S201中接收到的通知消息没有包括容灾标识, 则可以根据通知 消息中的用户名进行相应用户终端的被叫业务的承载。
S203: 向管理所述用户名所指示的用户终端的策略与计费规则功能实体 PCRF发送所述重选请求, 以使所述 PCRF根据所述 P-CSCF重选标识通知所述 用户名所指示的用户终端重选 P-CSCF以承载所述用户终端的被叫业务;
所述 S202中生成的携带 P-CSCF重选标识和所述用户名的重选请求具体可 以为一个 STR ( Session-Termination-Request , 会话中止请求) , 在该 STR中携 带上定义的 P-CSCF Re-Select Flag ( P-CSCF重选标识 ) , 而所述用户名用于指 示 PCRF确定需要进行重选注册的用户终端。 在所述 S203中将该 STR发送给 PCRF。
具体的, 在所述 S203进行重选请求的发送时, 可用的 P-CSCF可能并不知 道所述用户名对应的用户终端所属的 PCRF , 此时, 所述 S203具体包括: 将所 述重选请求发送给路由代理节点 DRA( Diameter Routing Agent,直径路由代理), 以使所述 DRA根据所述重选请求中的用户名将所述重选请求发送给管理所述用 户名所指示的用户终端的 PCRF。即:可用的 P-CSCF可以先将 STR发送给 DRA, 然后又 DRA根据 STR中的用户名来确定该用户名对应用户终端的 PCRF。
进一步地, 在执行所述 S202之前, 还可以包括:
判断所述用户名所指示的用户终端是否在本端注册;
若未在本端注册, 则执行所述 S202。 而若已在本端已经注册, 则可以直接 向 S-CSCF发送注册完成消息,在 S-CSCF中登记所述用户终端的用户名和本端 的主机名, 以便于所述 S-CSCF将对所述用户终端的被叫请求发送给本端, 由本 端来承载作为被叫端的所述用户终端的被叫业务。
即: 仅在用户终端没有在可以的 P-CSCF中注册时, 才确定是否发起恢复流 程, 使用户终端重新注册 P-CSCF。
所述可用的 P-CSCF可以通过管理所述用户终端的 PCRF、 与所述用户终端 相连的网关的通知路径通知所述用户终端重新注册新的 P-CSCF , 以便于 S-CSCF将对所述用户终端的被叫请求下发给该新的 P-CSCF,由该新的 P-CSCF 承载该用户终端的被叫业务。在通知了用户终端重新注册新的 P-CSCF后, 所述 用户终端可能选择了该可用的 P-CSCF, 因此, 进一步地, 在本发明实施例中还 可以包括下述 S204。
S204: 当接收到用户终端的注册请求时, 向所述用户终端所属的 S-CSCF 发送注册完成消息以完成用户终端的注册登记。
用户终端可以釆用现有的注册流程完成到本 P-CSCF的注册, P-CSCF在确 定了所述用户终端注册成功后, 向前端的 S-CSCF发送注册完成消息, 以便于通 知前端的 S-CSCF可以接收到的被叫请求下发给本 P-CSCF, 以承载所述用户终 端的被叫业务。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
本发明实施例还提供另一种实现终端被叫业务恢复的方法, 如图 2B所示。 图 2B所示的方法可以在 P-CSCF中实现, 具体的, 该方法包括:
S201': 接收对用户终端的被叫请求。
其中, 在步骤 201,中, 可以接收 S-CSCF或 IBCF发送的对所述用户终端的 被叫请求。
S202': 确定没有存储被叫用户的注册数据。
需要说明的是, 在步骤 S202' , P-CSCF确定该 P-CSCF是否存储有被叫用 户的注册数据, 在确定该 P-CSCF 没有存储被叫用户的注册数据时, 执行步骤 S203,。
S203': 向管理所述用户终端的 PCRF发送触发所述用户终端重新发起 IMS 注册的请求。
需要说明的是, 所述触发所述用户终端重新发起 IMS注册的请求可以是携 带重注册标识的请求, 所述重注册标识用于触发所述用户终端重新发起 IMS注 册。 作为示例而非限定, 所述携带重注册标识的请求可以是 STR 或 AAR ( Authorization and Authentication Request, 鉴权授权请求 ) 。
再请参见图 3 ,是本发明的实现终端被叫业务恢复的方法的第三实施例流程 示意图, 本发明实施例的所述方法可应用在管理用户终端的策略与计费规则功 能实体 PCRF中, 所述 PCRF在接收到 P-CSCF发送的如携带 P-CSCF Re-Select Flag的 STR等重选请求时, 执行本发明实施例的所述方法的步骤, 具体的, 所 述方法包括:
S301 : 当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求 时,生成注册触发请求; 所述的用户名包括所述 S-CSCF接收到的被叫请求对应 的用户终端的标识, 即被叫端的用户终端的标识, 具体可以为该作为被叫端的 用户终端的 IP地址、 用户业务权限以及其他用户配置信息等。
S302: 向与所述用户名所指示的用户终端相连的网关发送所述生成的注册 触发请求, 以使所述网关触发所述用户名所指示的用户终端重新注册 P-CSCF 以承载所述用户终端的被叫业务;
其中,所述重选请求是所述 P-CSCF根据 S-CSCF发送的携带用户名和用于 指示触发所述用户名所指示的用户终端重新注册 P-CSCF 的容灾标识的通知消 息生成的。 所述重选请求可以是 STR等, 其具体生成过程可参见上述第二实施 例的描述。
PCRF在接收到携带有 P-CSCF Re-Select Flag的 STR等重选请求后, 需要 执行用户名对应的用户终端的被叫业务恢复流程, 即生成所述的注册触发请求, 将该注册触发请求发送给用户名对应的用户终端的网关, 该网关可以为 P-GW ( Packet data network Gateway , 分组数据网络网关) 或者 S-GW ( Serving Gateway, 服务网关) , 由网关来直接触发用户终端重新选择新的 P-CSCF。
具体的, 所述 S301具体可以包括:
当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生 成携带会话释放消息的注册触发请求; 其中, 所述会话释放消息用于指示与所 述用户名所指示的用户终端相连的网关请求移动管理实体 MME ( Mobility Management Entity , 移动管理实体)删除用户的用户承载。
所述注册触发请求可以为携带 Session-Release-Cause AVP ( Attribute Length Value , 属性值对 ) (消息释放原因的属性值对 ) 的 RAR ( Re-Auth-Request, 重新认证请求) , 即在 RAR中携带会话释放原因这个属性字段以及字段值, 指 示网关请求删除该用户终端的所有承载, 由网关直接请求释放所述用户名对应 的用户终端的 IMS( IP Multimedia Subsystem IP多媒体子系统) PDN( Packet Data Network, 分组数据网络) , 即删除承载所述用户终端的 IMS信令的通信网络。
用户终端在 MME将 IMS PDN删除后会掉线, 用户终端检测到接入失败, 将自动进行新的注册流程以完成包括 P-CSCF的注册等实现网络接入。用户终端 发起选择一个可用的第三 P-CSCF3 , 并向该第三 P-CSCF 发起 SIP ( Session Initiation Protocol, 会话初始化协议)初始注册, 该第三 P-CSCF收到用户注册 请求后,向用户归属的 S-CSCF完成注册请求。该第三 P-CSCF可以通过 I-CSCF 确定所述用户终端所属的 S-CSCF , 然后向查询到的所述用户终端所属的 S-CSCF完成注册请求。 之后 S-CSCF再下发用户的被叫请求到该第三 P-CSCF, 以承载被叫业务。
或者, 所述 S301包括:
当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生 成携带更新 P-CSCF地址信息的注册触发请求; 其中, 所述更新 P-CSCF地址信 息用于指示与所述用户名所指示的用户终端相连的网关生成可用 P-CSCF 地址 列表发送给所述用户名所指示的用户终端。
所述注册触发请求为携带 Update P-CSCF Address (更新 P-CSCF地址 )请 求的 RAR。 网关接收到 RAR后, 将发送更新 PDP ( Packet Data Protocol ,分组 数据协议)内容 Update PDP Context消息给用户终端, 以便于用户终端完成重注 册。 用户终端在收到 Update PDP Context后,根据 Update PDP Context中的可用 P-CSCF地址列表更新本地 P-CSCF列表, 并检查本端注册的初始 P-CSCF是否 在列表中, 如果不在, 用户终端将发起重新注册 P-CSCF的流程, 具体可以从网 关下发的新的 P-CSCF List (列表 )中选择可用的第三 P-CSCF3行注册, 以承载 本用户终端的被叫业务。 该第三 P-CSCF可以通过 I-CSCF确定所述用户终端所 属的 S-CSCF, 然后向查询到的所述用户终端所属的 S-CSCF完成注册请求。 之 后 S-CSCF再下发用户的被叫请求到该第三 P-CSCF, 以承载被叫业务。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 4,是本发明的实现终端被叫业务恢复的方法的第四实施例流程 示意图, 本发明实施例的所述方法可应用在如 P-GW或者 S-GW中, 在接收到 PCRF发送的 RAR等注册触发请求时,执行本发明实施例的所述方法的各步骤, 具体的, 所述方法包括: S401 : 接收到策略与计费规则功能实体 PCRF发送的携带用户名的注册触 发请求;所述的用户名包括所述 S-CSCF接收到的被叫请求对应的用户终端的标 识, 即作为被叫端的用户终端的标识, 具体可以为该作为被叫端的用户终端的 IP地址、 用户业务权限以及其他用户配置信息等。
S402:触发所述用户名所指示的用户终端重新注册 P-CSCF以承载所述用户 终端的被叫业务;
其中,所述注册触发请求是所述 PCRF在接收到 P-CSCF发送的携带 P-CSCF 重选标识和用户名的重选请求时生成的; 所述重选请求是所述 P-CSCF 根据 S-CSCF 发送的携带用户名和用于指示触发所述用户名所指示的用户终端重新 注册 P-CSCF的容灾标识的通知消息生成的。
所述重选请求以及所述注册触发请求的生成过程可相应地参见第二实施例 和第三实施例中的描述。
具体的, 所述 S402具体可以包括:
当所述注册触发请求中携带有会话释放消息时,向移动管理实体 MME发送 携带所述用户名的释放请求 ,以使所述 MME删除所述用户名所指示用户终端的 用户承载;
当所述注册触发请求中携带有更新 P-CSCF地址信息时, 获取可用 P-CSCF 地址列表发送给所述用户名所指示的用户终端, 以使所述用户终端从所述可用 P-CSCF地址列表中选择 P-CSCF并注册到该选择的 P-CSCF。
当网关接收到 PCRF发送携带 Session-Release-Cause AVP的 RAR后, 指示 MME删除用户的 IMS PDN, 触发用户终端重新注册 P-CSCF。 而当网关接收到 PCRF发送的携带 Update P-CSCF Address请求的 RAR时, 获取 Update PDP Context消息, 并发送 Update PDP Context消息给用户终端以触发所述用户终端 根据 Update PDP Context消息中的可用 P-CSCF地址列表中更新本地 P-CSCF列 表,并在确定更新后的本地 P-CSCF列表中不包括本端已注册的初始 P-CSCF后, 选择新的 P-CSCF并注册到该选择的 P-CSCF, 完成重注册。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 5,是本发明的实现终端被叫业务恢复的方法的第五实施例的流 程示意图, 本发明实施例的所述方法可应用在用户终端中, 所述用户终端在确 定 MME中的 IMS PDN删除或者接收到 P-GW或者 S-GW发送的可用 P-CSCF 地址列表时, 执行本发明实施例的所述方法的相关步骤, 具体的, 所述方法包 括:
S501 : 当检测到接入失败时, 发起注册到 P-CSCF的注册请求, 以便于在初 始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务;
用户终端在 MME将 IMS PDN删除后会掉线, 用户终端检测到接入失败, 将自动进行新的注册流程以完成包括 P-CSCF的注册等实现网络接入。用户终端 发起选择一个可用的第三 P-CSCF3 ,并向该第三 P-CSCF发起 SIP初始注册,该 第三 P-CSCF收到用户注册请求后, 向用户归属的 S-CSCF完成注册请求。 该第 三 P-CSCF可以通过 I-CSCF确定所述用户终端所属的 S-CSCF, 然后向查询到 的所述用户终端所属的 S-CSCF完成注册请求。之后 S-CSCF再下发用户的被叫 请求到该第三 P-CSCF, 以承载被叫业务。
S502: 当接收到网关发送的可用 P-CSCF地址列表时, 从所述可用 P-CSCF 地址列表选择 P-CSCF并注册到选择的 P-CSCF, 以便于在初始 P-CSCF发生故 障时通过重新注册的 P-CSCF承载被叫业务。
具体的, 所述 S502具体可以包括: 当接收到网关发送的可用 P-CSCF地址 列表时,判断所述可用 P-CSCF地址列表中是否包括本用户终端当前注册的初始 P-CSCF的主机名, 若不包括, 从所述可用 P-CSCF地址列表选择 P-CSCF并注 册到选择的 P-CSCF。
所述注册触发请求为携带 Update P-CSCF Address (更新 P-CSCF地址 )请 求的 RAR。 网关接收到 RAR后, 将发送更新 PDP内容 Update PDP Context消 息给用户终端, 以便于用户终端完成重注册。 用户终端在收到 Update PDP Context后, 根据 Update PDP Context 中的可用 P-CSCF 地址列表更新本地 P-CSCF列表, 并检查本端注册的初始 P-CSCF是否在列表中, 如果不在, 用户 终端将发起重新注册 P-CSCF的流程, 具体可以从网关下发的新的 P-CSCF List (歹' j表) 中选择可用的第三 P-CSCF3行注册, 以承载本用户终端的被叫业务。 该第三 P-CSCF可以通过 I-CSCF确定所述用户终端所属的 S-CSCF, 然后向查 询到的所述用户终端所属的 S-CSCF完成注册请求。之后 S-CSCF再下发用户的 被叫请求到该第三 P-CSCF, 以承载被叫业务。
需要说明的是, 上述的 S501和 S502的执行过程不分先后, 可以先检测是 否接入失败并执行所述 S502, 或者先检测是否接收到网关发送的可用 P-CSCF 地址列表并执行所述 S502。
本发明实施例在用户终端当前注册的 P-CSCF发生故障,终端能够根据网络 侧基于容灾标识的消息进行恢复处理的结构, 重新注册新的 P-CSCF, 并在新的 P-CSCF中承载该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需 要通过心跳检测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的 处理复杂的问题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 6,是本发明的实现终端被叫业务恢复的方法的第六实施例的流 程示意图,本发明实施例的所述方法通过用户终端 UE、 S-CSCF、 P-CSCF、 PCRF 以及网关实现在用户终端当前注册的 P-CSCF发生故障时,快速回复该用户终端 的被叫业务, 具体的, 如图 6所示, 所述方法包括:
Sl l : S-CSCF 在接收到对用户终端的被叫请求后, 查询所述用户终端当前 注册的初始 P-CSCF; S-CSCF根据 P-CSCF的主机名查询出 P-CSCF的 IP地址, DNS上为 P-CSCF 1即所述初始 P-CSCF的主机名配置两个 IP ,分别是 IP1和 IP2 , 分别对应于 P-CSCF1和 P-CSCF2。
S12:所述 S-CSCF检测到所述初始 P-CSCF发生故障,选择可用的 P-CSCF, 并向所述可用的 P-CSCF发送携带容灾标识的通知消息,所述容灾标识用于指示 所述可用的 P-CSCF触发所述用户终端重新注册 P-CSCF。 所述 S-CSCF感知 IP1对应的 P-CSCF ( P-CSCF 1 )故障后, 则向 IP2对应 的可用的 P-CSCF ( P-CSCF2 )发送带容灾标记的 NOTIFY, 通知用户终端重注 册 P-CSCF。
S13 : P-CSCF2 接收到携带容灾标识和用户名的通知消息后, 生成携带 P-CSCF重选标识和所述用户名的重选请求发送给 PCRF, 该 PCRF用于管理所 述用户名所指示的用户终端。
P-CSCF2检查到消息中带有容灾标记, 或者带有容灾标记且未在本端注册 时, 则发起容灾流程。 P-CSCF2将向 PCRF发送 STR (即重选请求) , STR带 上自定义的 P-CSCF Re-Select Flag。 其中, 如果 P-CSCF2不知道用户的 PCRF 时, STR将先发送到 DRA, 由 DRA路由到用户所在的 PCRF上。
S14: PCRF接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选 请求后, 生成注册触发请求发送给网关, 该网关为 S-GW或者 P-GW, 与所述用 户终端相连。
PCRF收到带有 P-CSCF Re-Select Flag的 STR后, 需要执行容灾恢复流程。 PCRF向 P/S-GW发送 RAR, 请求删除所述用户终端所有承载。
S15: P/S-GW在接收到策略与计费规则功能实体 PCRF发送的携带用户名 的注册触发请求时, 触发所述用户名所指示的用户终端重新注册 P-CSCF。
P/S-GW接收到 PCRF的 RAR后, 将指示 MME删除用户的 IMS PDN, 触 发用户重新注册。
S16: 用户终端选择一个可用的 P-CSCF3 , 并向 P-CSCF3发起 SIP初始注 册;
S17: P-CSCF3收到用户终端注册请求后, 向用户归属的 S-CSCF发起 SIP 注册, 完成注册请求, P-CSCF3可以通过查询 I -CSCF 的方式确定用户终端归 属的 S-CSCF。
S18: S-CSCF再下发被叫请求到 P-CSCF3;
S19: P-CSCF3发送被叫请求给 UE, 以根据所述被叫请求承载所述用户终 端的被叫业务, 完成所述用户终端的被叫业务。 本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 7,是本发明的实现终端被叫业务恢复的方法的第七实施例的流 程示意图, 本发明实施例的所述方法通过用户终端、 S-CSCF、 P-CSCF, PCRF 以及网关实现在用户终端当前注册的 P-CSCF发生故障时,快速回复该用户终端 的被叫业务, 具体的, 如图 7所示, 所述方法包括:
S21: 所述 S-CSCF在接收到被叫请求后, 查询该被叫请求对应的用户终端 当前注册的初始 P-CSCF, 即作为被叫端的用户终端的初始 P-CSCF; S-CSCF根 据 P-CSCF的主机名查询出 P-CSCF的 IP地址, DNS上为 P-CSCF1即所述初始 P-CSCF 的主机名配置两个 IP, 分别是 IP1 和 IP2, 分别对应于 P-CSCF1 和 P-CSCF2。
S22:所述 S-CSCF检测到所述初始 P-CSCF发生故障,选择可用的 P-CSCF, 并向所述可用的 P-CSCF发送携带容灾标识的通知消息,所述容灾标识用于指示 所述可用的 P-CSCF触发所述用户终端重新注册 P-CSCF。
所述 S-CSCF感知 IP1对应的 P-CSCF ( P-CSCF1 )故障后, 则向 IP2对应 的可用的 P-CSCF ( P-CSCF2 )发送带容灾标记的 NOTIFY, 通知用户终端重注 册 P-CSCF。
S23 : P-CSCF2 接收到携带容灾标识和用户名的通知消息后, 生成携带 P-CSCF重选标识和所述用户名的重选请求发送给 PCRF, 该 PCRF用于管理所 述用户名所指示的用户终端。
P-CSCF2检查到消息中带有容灾标记, 或者带有容灾标记且未在本端注册 时, 则发起容灾流程。 P-CSCF2将向 PCRF发送 STR (即重选请求) , STR带 上自定义的 P-CSCF Re-Select Flag。 其中, 如果 P-CSCF2不知道用户的 PCRF 时, STR将先发送到 DRA, 由 DRA路由到用户所在的 PCRF上。 S24: PCRF接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选 请求后, 生成注册触发请求发送给网关, 该网关为 S-GW或者 P-GW, 与所述用 户终端相连。
PCRF收到带有 P-CSCF Re-Select Flag的 STR后, 需要执行容灾恢复流程。 PCRF容灾恢复的方法是向 P-GW发送 RAR, 在该 RAR中携带 Update P-CSCF Address请求, 该请求可能为私有。
S25: P/S-GW当所述注册触发请求中携带有更新 P-CSCF地址信息时, 获 取可用 P-CSCF地址列表发送给所述用户名所指示的用户终端;
P/S-GW接收到 RAR后,将发送 Update PDP Context消息给用户终端, Update PDP Context消息中包括可用 P-CSCF地址列表;
S26: 用户终端当接收到网关发送的可用 P-CSCF地址列表时, 从所述可用 P-CSCF地址列表选择 P-CSCF; 以便于在初始 P-CSCF发生故障时通过重新注 册的 P-CSCF承载被叫业务。
用户终端在收到 Update PDP Context后, 更新 P-CSCF列表, 并检查自己注 册的 P-CSCF1是否在列表中, 如果不在, UE将发起重注册流程。 并从 P-GW下 发的新的 P-CSCF List中选择可用的 P-CSCF3进行注册。
S27: 发送注册请求注册到选择的 P-CSCF3;
S28: P-CSCF3收到用户终端注册请求后, 向用户归属的 S-CSCF完成注册 请求, P-CSCF3可以通过查询 I -CSCF的方式确定用户终端归属的 S-CSCF。
S29: S-CSCF再下发被叫请求到 P-CSCF3;
S210: P-CSCF3发送被叫请求给 UE, 以根据所述被叫请求承载所述用户终 端的被叫业务, 完成所述用户终端的被叫业务。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。 图 8是本发明实施例提供的一种实现终端被叫业务恢复的方法的流程示意 图, 本发明实施例的所述方法通过用户终端 UE、 S-CSCF、 P-CSCF, PCRF 以 及网关实现在用户终端当前注册的 P-CSCF发生故障时 ,触发该用户终端重新注 册, 具体的, 如图 8所示, 所述方法包括:
S801 : S-CSCF在接收到对用户终端的被叫请求后, 获取被叫用户注册成功 时保存的 P-CSCF1的地址。
针对该 P-CSCF的地址,可以在 S-CSCF上预先配置一个或多个备用设备的 地址, 例如 P-CSCF2的地址。 另一种获取备用 P-CSCF地址的方式是, 当保存 的 P-CSCF的地址为域名时, 通过 DNS查询获取备用的 P-CSCF2的地址。
S-CSCF检测到所述 P-CSCF发生了故障(例如通过 options心跳检测 ) , 则 S-CSCF路由时选择低备用的 P-CSCF2。
S802: S-CSCF向所述可用的 P-CSCF2发送被叫请求。
S803: P-CSCF2接收到被叫请求后, 发现没有存储该被叫用户的注册数据, 给 S-CSCF返回错误响应, 以拒绝本次呼叫。
具体地, P-SCCF2发现 P-CSCF2中没有存储该被叫用户的注册数据时, 给 S-CSCF返回错误响应。
S804: P-CSCF2向 PCRF发送触发用户终端重新发起 IMS注册的请求。 可选地, 该请求可以携带重注册标识, 该重注册标识用于触发所述用户终 端重新发起 IMS注册。
P-CSCF2将向 PCRF发送的请求可以是 STR或 AAR。 需要说明的是, 如果 P-CSCF2也可以将该触发用户终端重新发起 IMS注册的请求发送到 DRA, 由 DRA将该触发用户终端重新发起 IMS 注册的请求路由到该用户终端所属的 PCRF上。
S805: PCRF接收到 P-CSCF发送的触发用户终端重新发起 IMS注册的请求 后, 生成注册触发请求发送给网关。 该网关可以为 S-GW或者 P-GW。
S806: P-GW或 S-GW在接收到 PCRF发送注册触发请求时,触发所述用户 终端重新注册。 具体地, P-GW或 S-GW将指示 MME删除用户的 IMS PDN连接, 触发用 户重新注册。
S807: 用户终端选择一个可用的 P-CSCF, 例如用户终端选了 P-CSCF3 , 向 P-CSCF3发起 SIP初始注册请求;
S808: P-CSCF3 收到用户终端注册请求后, 后续流程同正常的注册流程, 完成注册后, 该用户可以正常处理业务。
本发明实施例在用户终端当前注册的 P-CSCF发生故障, S-CSCF通过备用 的 P-CSCF最终触发终端进行重新注册,使得需要使用业务的终端用户在完成注 册后, 恢复业务。
图 9是本发明实施例提供的一种实现终端被叫业务恢复的方法的流程示意 图, 本发明实施例的所述方法描述用户终端 UE、 IBCF、 P-CSCF、 PCRF以及网 关实现在用户终端当前注册的 P-CSCF发生故障时, 触发该用户终端重新注册, 具体的, 如图 9所示, 所述方法包括:
S901 : IBCF ( Interconnection Border Control Function, 互通边界控制功能) 在接收到对用户终端的被叫请求后, 从请求的 route 头域中获取到下一跳 P-CSCF1的地址。
针对该 P-CSCF的地址, 可以在 IBCF上预先配置一个或多个备用设备的地 址, 例如 P-CSCF2的地址。 另一种获取备用 P-CSCF地址的方式是, 当保存的 P-CSCF的地址为域名时, 通过查询 DNS获取备用的 P-CSCF2的地址。
所述 IBCF检测到所述 P-CSCF1发生了故障 (例如通过 options心跳检测 ) 时, 将选择备用的 P-CSCF2。
S902: IBCF向所述可用的 P-CSCF2发送被叫请求。
S903: P-CSCF2接收到被叫请求后, 发现没有存储被叫用户的注册数据, 给 IBCF返回错误响应 , 以拒绝本次呼叫。
具体地, P-SCCF2发现 P-CSCF2中没有存储该被叫用户的注册数据时, 给 S-CSCF返回错误响应。
S904: P-CSCF2向 PCRF发送触发用户终端重新发起 IMS注册的请求。 可选地, 该请求可以携带重注册标识, 该重注册标识用于触发所述用户终 端重新发起 IMS注册。
P-CSCF2将向 PCRF发送的请求可以是 STR或 AAR。 需要说明的是, 如果 P-CSCF2也可以将该触发用户终端重新发起 IMS注册的请求发送到 DRA, 由 DRA将该触发用户终端重新发起 IMS 注册的请求路由到该用户终端所属的 PCRF上。
S905: PCRF接收到 P-CSCF发送的触发用户终端重新发起 IMS注册的请求 后, 生成注册触发请求发送给网关。 该网关可以为 S-GW或者 P-GW。
S906: P-GW或 S-GW在接收到 PCRF发送注册触发请求时,触发所述用户 终端重新注册。
具体地, P-GW或 S-GW将指示 MME删除用户的 IMS PDN, 触发用户重 新注册。
S907: 用户终端选择一个可用的 P-CSCF,例如终端选择到了 P-CSCF3 , 向 P-CSCF3发起 SIP初始注册请求;
S908: P-CSCF3 收到用户终端注册请求后, 后续流程同正常的注册流程, 完成注册后, 该用户可以正常处理业务。
本发明实施例在用户终端当前注册的 P-CSCF发生故障, S-CSCF通过备用 的 P-CSCF最终触发终端进行重新注册,使得需要使用业务的终端用户在完成能 提前进行注册后, 恢复业务。 下面再对本发明实施例的实现终端被叫业务恢复的装置及其系统进行详细 描述。
请参见图 10, 是本发明的实现终端被叫业务恢复的装置的第一实施例结构 示意图, 本发明实施例的所述装置可以为 S-CSCF或 IBCF, 具体的, 所述装置 包括:
查询模块 11 , 用于当接收到对用户终端的被叫请求时, 查询所述用户终端 当前注册的初始代理呼叫会话控制功能实体 P-CSCF; 处理模块 12 , 用于若检测到所述初始 P-CSCF 发生故障, 选择可用的 P-CSCF, 并向所述可用的 P-CSCF发送通知消息, 以触发所述用户终端重新注 册 P-CSCF。
在其中一种可能的实现方式中, 处理模块 12 可以具体用于在选择可用的 P-CSCF后, 向所述可用的 P-CSCF发送携带容灾标识的通知消息, 所述容灾标 识用于指示所述可用的 P-SCCF触发所述用户终端重新注册 P-CSCF。 在其中另 一种可能的实现方式中, 处理模块 12可以具体用于在选择可用的 P-CSCF后, 向所述可用的 P-CSCF发送所述用户终端的被叫请求, 以便所述可用的 P-CSCF 确定没有存储被叫用户的注册数据时, 触发所述用户终端重新发起 IMS注册。
可选地, 所述装置还可以包括分配模块 13。 分配模块 13用于在接收到所述 用户终端重新注册的 P-CSCF发送的注册完成消息时,将所述被叫请求下发给所 述重新注册的 P-CSCF以 载所述用户终端的被叫业务。
其中 ,所述可用的 P-CSCF通过 PCRF触发所述用户终端重新注册 P-CSCF。 用户终端在注册到 P-CSCF 后, P-CSCF会将相应的注册完成信息发送给 S-CSCF , 由 S-CSCF进行认证、 鉴权, 并执行登记用户终端的用户名以及其注 册的 P-CSCF的主机名等处理, 因此, 所述查询模块 11根据被叫请求对应的用 户终端的用户名 (作为被叫端的用户终端的用户名) , 可以查询并确定所述用 户终端当前注册的初始 P-CSCF。 其中, 所述用户终端的用户名用于标识所述用 户终端, 具体可以该用户终端的 IP地址、 用户业务权限以及其他用户配置信息 等。
所述处理模块 12具体可以通过心跳机制与当前的 P-CSCF POOL中的每一 个 P-CSCF进行心跳检测,根据心跳检测的数据或者根据是否能正常接收到心跳 数据来判定所述用户终端当前注册的初始 P-CSCF是否发生故障, 例如在 ping 命令不通或者检测的消息收发失败时, 可确定该初始 P-CSCF发生故障。
当检测到所述初始 P-CSCF 发生故障时, 所述处理模块 12 具体从当前的 P-CSCF POOL中选择一个可用的 P-CSCF,该可用的 P-CSCF可以是通过心跳检 测等方式已确定为没有故障的 P-CSCF。 所述处理模块 12也可以根据为所述初 始 P-CSCF配置的两个标识来选择作为所述初始 P-CSCF的备选 P-CSCF作为所 述可以的 P-CSCF。
所述可用的 P-CSCF可以才艮据通知消息中的容灾标识,得知所述用户终端注 册的当前 P-CSCF发生故障,则发起触发所述用户终端重新注册 P-CSCF的流程。 具体的,所述可用的 P-CSCF可以通过管理所述用户终端的策略与计费规则功能 实体 PCRF、与所述用户终端相连的网关的路径通知所述用户终端重新注册新的 P-CSCF, 以便于所述分配模块 13 将对所述用户终端的被叫请求下发给该新的 P-CSCF, 由该新的 P-CSCF承载该用户终端的被叫业务。 所述可用的 P-CSCF 也可以在接收到用户终端的被叫请求时,当确定所述可用的 P-CSCF没有存储被 叫用户的注册数据时,确定所述用户终端注册的当前 P-CSCF发送故障, 需要发 起触发所述用户终端重新注册 P-CSCF的流程。
进一步可选地, 如图 10所示, 所述装置还可以包括:
配置模块 14, 用于为所述初始 P-CSCF配置第一标识和第二标识, 其中, 所述第一标识包括所述初始 P-CSCF的 IP地址, 所述第二标识包括除所述初始 P-CSCF外的 P-CSCF的 IP地址。
进一步的, 所述配置模块 14具体用于在域名系统 DNS服务器中根据所述 初始 P-CSCF的主机名配置第一标识和第二标识。
通过所述配置模块 14可以预先为所述初始 P-CSCF配置两个标识即第一标 识和第二标识, 其中, 所述第一标识包括所述初始 P-CSCF的 IP地址, 所述第 二标识包括除所述初始 P-CSCF外的 P-CSCF的 IP地址。 第一标识为所述初始 P-CSCF发布的 IP地址, 所述第二标识则是所述 P-CSCF POOL中除所述初始 P-CSCF外的其他 P-CSCF的 IP地址, 在所述处理模块 12检测到初始 P-CSCF 发生故障时, 根据所述配置模块 14配置的第二标识可以直接向可用的 P-CSCF 发送所述通知消息。
进一步可选地, 如图 10所示, 所述处理模块 12具体可以包括:
获取单元 121 , 用于获取为所述初始 P-CSCF配置的第一标识和第二标识; 检测单元 122,用于若根据获取的所述第一标识检测到所述第一标识对应的 初始 P-CSCF发生故障, 将所述第二标识对应的 P-CSCF作为可用的 P-CSCF; 处理单元 123 ,用于根据所述第二标识向可用的 P-CSCF发送所述通知消息。 即所述处理模块 12根据所述配置模块 14配置的第二标识发送所述通知消 息。
进一步可选地, 所述分配模块 13具体用于将所述被叫请求发送给所述重新 注册的 P-CSCF, 以使所述重新注册的 P-CSCF将该被叫请求发送给所述用户终 端执行被叫业务。
本发明实施例在接收到被叫请求后, 如果检测到该被叫请求中对应的被叫 端的用户终端当前注册的 P-CSCF发生故障 ,通过生成相应的携带容灾标识的消 息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载该用 户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检测所 导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 11A, 是本发明的实现终端被叫业务恢复的装置的第二实施例 流程示意图,本发明实施例的所述装置可以为 P-CSCF,具体的,所述装置包括: 接收模块 21 , 用于接收服务呼叫会话控制功能实体 S-CSCF发送的携带用 户名的通知消息;所述的用户名包括所述 S-CSCF接收到的被叫请求对应的用户 终端的标识, 即被叫端的用户终端的标识, 具体可以为该作为被叫端的用户终 端的 IP地址、 用户业务权限以及其他用户配置信息等。
处理模块 22 , 用于若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求;
发送模块 23 , 用于向管理所述用户名所指示的用户终端的策略与计费规则 功能实体 PCRF发送所述重选请求,以使所述 PCRF根据所述 P-CSCF重选标识 通知所述用户名所指示的用户终端重选 P-CSCF 以 载所述用户终端的被叫业 务;
其中,携带所述容灾标识的通知消息是所述 S-CSCF在接收到的被叫请求对 应的用户终端所注册的 P-CSCF发生故障时生成的,所述容灾标识用于指示触发 所述用户终端重新注册 P-CSCF。 即在被叫端的用户终端的初始 P-CSCF发生故 障时生成通知消息。
所述 S-CSCF 生成包括容灾标识的通知消息的过程可参考上述的装置第一 实施例中的描述。
而若在所述接收模块 21接收到的通知消息没有包括容灾标识, 则 P-CSCF 的所述处理模块 22可以根据通知消息中的用户名进行相应用户终端的被叫业务 的承载。
所述处理模块 22生成的携带 P-CSCF重选标识和所述用户名的重选请求具 体可以为一个 STR, 在该 STR中携带上定义的 P-CSCF Re-Select Flag ( P-CSCF 重选标识 ) , 所述发送模块 23将该 STR发送给 PCRF。
具体的, 所述发送模块 23进行重选请求的发送时, 可能并不知道所述用户 名对应的用户终端所属的 PCRF, 此时, 进一步可选地, 所述发送模块 23 , 具 体用于将所述重选请求发送给路由代理节点 DRA, 以使所述 DRA根据所述重 选请求中的用户名将所述重选请求发送给管理所述用户名所指示的用户终端的
PCRF。即:所述发送模块 23可以先将 STR发送给 DRA,然后又 DRA根据 STR 中的用户名来确定该用户名对应用户终端的 PCRF。
进一步可选地, 如图 11A所示, 所述装置具体可以包括:
判断模块 24, 用于判断所述用户名所指示的用户终端是否在本端注册, 并 在判断结果为未在本端注册, 则通知所述处理模块 22执行所述若解析到所述通 知消息中还包括容灾标识, 生成携带 P-CSCF 重选标识和所述用户名的重选请 求。
而若所述判断模块 24的判断结果为已在本端已经注册, 则本 P-CSCF可以 直接向 S-CSCF发送注册完成消息,在 S-CSCF中登记所述用户终端的用户名和 本端的主机名, 以便于所述 S-CSCF将接收到的所述被叫请求发送给本端, 由本 端来承载所述用户终端的被叫业务。
即: 仅在用户终端没有在可以的 P-CSCF中注册时, 才确定是否发起恢复流 程, 使用户终端重新注册 P-CSCF。 可以通过管理所述用户终端的 PCRF、与所述用户终端相连的网关的通知路 径通知所述用户终端重新注册新的 P-CSCF, 以便于 S-CSCF将对所述用户终端 的被叫请求下发给该新的 P-CSCF, 由该新的 P-CSCF承载该用户终端的被叫业 务。在通知了用户终端重新注册新的 P-CSCF后, 所述用户终端可能选择了该可 用的 P-CSCF, 因此, 进一步可选地, 如图 11A所示, 所述装置还可以包括: 注册模块 25 , 用于当接收到用户终端的注册请求时, 向所述用户终端所属 的 S-CSCF发送注册完成消息以完成用户终端的注册登记。
用户终端可以釆用现有的注册流程完成到本 P-CSCF的注册,所述注册模块 25在确定了所述用户终端注册成功后, 向前端的 S-CSCF发送注册完成消息, 以便于通知前端的 S-CSCF可以将接收到的被叫请求下发给本 P-CSCF, 以承载 所述用户终端的被叫业务。
本发明还提供了一种实现终端被叫业务恢复的装置,如图 11B所示。图 11B 所示的该装置可以是 P-CSCF, 该装置包括:
接收模块 2Γ , 用于接收对用户终端的被叫请求;
其中, 接收模块 21 '可以具体用于接收 S-CSCF或 IBCF发送的对所述用户 终端的被叫请求;
处理模块 22,, 用于在接收模块 21,接收到所述被叫请求时, 确定没有存储 被叫用户的注册数据;
发送模块 23,, 用于在所述处理模块 22,确定没有存储所述被叫用户的注册 数据后, 向管理所述用户终端的 PCRF发送触发所述用户终端重新发起 IMS注 册的请求。
可选地, 发送模块 23,可以具体用于向所述 PCRF发送携带重注册标识的请 求, 所述重注册标识用于触发所述用户终端重新发起 IMS注册。 在其中一种可 能的实现方式中, 所述携带重注册标识的请求可以是 STR或 AAR。
可选地,处理模块 22,具体用于确定图 11B所示的装置没有存储被叫用户的 注册数据。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 12, 是本发明的实现终端被叫业务恢复的装置的第三实施例流 程示意图, 本发明实施例的所述装置可以为 PCRF, 具体的, 所述装置包括: 生成模块 31 , 用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户 名的重选请求时,生成注册触发请求; 所述的用户名包括 S-CSCF接收到的被叫 请求对应的用户终端的标识, 即被叫端的用户终端标识, 具体可以为该作为被 叫端的用户终端的 IP地址、 用户业务权限以及其他用户配置信息等。
发送模块 32, 用于向与所述用户名所指示的用户终端相连的网关发送所述 生成的注册触发请求, 以使所述网关触发所述用户名所指示的用户终端重新注 册 P-CSCF以承载所述用户终端的被叫业务;
其中,所述重选请求是所述 P-CSCF根据 S-CSCF发送的携带用户名和用于 指示触发所述用户名所指示的用户终端重新注册 P-CSCF 的容灾标识的通知消 息生成的。
所述生成模块 31在接收到携带有 P-CSCF Re-Select Flag的 STR等重选请求 后, 需要执行用户名对应的用户终端的被叫业务恢复流程, 即生成所述的注册 触发请求, 将该注册触发请求发送给用户名对应的用户终端的网关, 该网关可 以为 P-GW或者 S-GW, 由网关来直接触发用户终端重新选择新的 P-CSCF。
进一步可选地, 所述生成模块 32, 具体用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时, 生成携带会话#放消息的注册触发请 求;
其中, 所述会话释放消息用于指示与所述用户名所指示的用户终端相连的 网关请求移动管理实体 MME删除用户的用户承载。
所述注册触发请求可以为携带 Session-Release-Cause AVP ( Attribute Length Value , 属性值对) (消息释放原因的属性值对) 的 RAR ( Re-Auth-Request, 重新认证请求) , 即在 RAR中携带会话释放原因这个属性字段以及字段值, 指 示网关请求删除该用户终端的所有承载, 由网关直接请求释放所述用户名对应 的用户终端的 IMS PDN。
用户终端在 MME将 IMS PDN删除后会掉线, 用户终端检测到接入失败, 将自动进行新的注册流程以完成包括 P-CSCF的注册等实现网络接入。用户终端 发起选择一个可用的第三 P-CSCF, 并向该第三 P-CSCF发起 SIP初始注册, 该 第三 P-CSCF收到用户注册请求后, 向用户归属的 S-CSCF完成注册请求。 该第 三 P-CSCF可以通过 I-CSCF确定所述用户终端所属的 S-CSCF, 然后向查询到 的所述用户终端所属的 S-CSCF完成注册请求。之后 S-CSCF再下发被叫请求到 该第三 P-CSCF, 以承载被叫业务。
或者, 可选地, 所述生成模块 32, 具体用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时, 生成携带更新 P-CSCF地址信息的注 册触发请求;
其中,所述更新 P-CSCF地址信息用于指示与所述用户名所指示的用户终端 相连的网关生成可用 P-CSCF地址列表发送给所述用户名所指示的用户终端。
所述注册触发请求为携带 Update P-CSCF Address (更新 P-CSCF地址 )请 求的 RAR。 网关接收到 RAR后, 将发送更新 PDP内容 Update PDP Context消 息给用户终端, 以便于用户终端完成重注册。 用户终端在收到 Update PDP Context后, 根据 Update PDP Context 中的可用 P-CSCF 地址列表更新本地 P-CSCF列表, 并检查本端注册的初始 P-CSCF是否在列表中, 如果不在, 用户 终端将发起重新注册 P-CSCF的流程, 具体可以从网关下发的新的 P-CSCF List (歹' j表)中选择可用的第三 P-CSCF行注册, 以承载本用户终端的被叫业务。 该 第三 P-CSCF可以通过 I-CSCF确定所述用户终端所属的 S-CSCF, 然后向查询 到的所述用户终端所属的 S-CSCF完成注册请求。之后 S-CSCF再下发被叫请求 到该第三 P-CSCF, 以承载被叫业务。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 13 , 是本发明的实现终端被叫业务恢复的装置的第四实施例流 程示意图, 本发明实施例的所述装置可以为 P-GW或者 S-GW等网关, 具体的, 所述装置包括:
接收模块 41 , 用于接收到策略与计费规则功能实体 PCRF发送的携带用户 名的注册触发请求;
触发模块 42, 用于触发所述用户名所指示的用户终端重新注册 P-CSCF 以 承载所述用户终端的被叫业务;
其中,所述注册触发请求是所述 PCRF在接收到 P-CSCF发送的携带 P-CSCF 重选标识和用户名的重选请求时生成的; 所述重选请求是所述 P-CSCF 根据 S-CSCF 发送的携带用户名和用于指示触发所述用户名所指示的用户终端重新 注册 P-CSCF的容灾标识的通知消息生成的。
进一步可选地, 如图 13所示, 所述触发模块 42具体可以包括:
第一发送单元 421 , 用于当所述注册触发请求中携带有会话释放消息时, 向 移动管理实体 MME发送携带所述用户名的释放请求,以使所述 MME删除所述 用户名所指示用户终端的用户承载; 或者
第二发送单元 422, 用于当所述注册触发请求中携带有更新 P-CSCF地址信 息时,获取可用 P-CSCF地址列表发送给所述用户名所指示的用户终端, 以使所 述用户终端从所述可用 P-CSCF 地址列表中选择 P-CSCF 并注册到该选择的 P-CSCF。
当网关接收到 PCRF发送携带 Session-Release-Cause AVP的 RAR后, 所述 第一发送单元 421指示 MME删除用户的 IMS PDN, 触发用户终端重新注册新 的 P-CSCF。 而当网关接收到 PCRF发送的携带 Update P-CSCF Address请求的 RAR时, 所述第二发送单元 422获取 Update PDP Context消息, 并发送 Update PDP Context消息给用户终端以触发所述用户终端根据 Update PDP Context消息 中的可用 P-CSCF地址列表中更新本地 P-CSCF 列表, 并在确定更新后的本地 P-CSCF列表中不包括本端已注册的初始 P-CSCF后, 选择新的 P-CSCF并注册 到该选择的 P-CSCF , 完成重注册。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 14, 是本发明的实现终端被叫业务恢复的装置的第五实施例的 结构示意图, 本发明实施例的所述装置可以为被叫请求对应的作为被叫端的用 户终端, 具体的, 所述装置包括:
注册发起模块 51 , 用于当检测到接入失败时, 发起注册到 P-CSCF的注册 请求,以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务; 注册选择模块 52, 用于当接收到网关发送的可用 P-CSCF地址列表时, 从 所述可用 P-CSCF地址列表选择 P-CSCF并注册到选择的 P-CSCF , 以便于在初 始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务。
用户终端在 MME将 IMS PDN删除后会掉线,所述注册发起模块 51检测到 接入失败, 将自动进行新的注册流程以完成包括 P-CSCF 的注册等实现网络接 入。所述注册发起模块 51发起选择一个可用的第三 P-CSCF,并向该第三 P-CSCF 发起 SIP初始注册,该第三 P-CSCF收到用户注册请求后,向用户归属的 S-CSCF 完成注册请求。 该第三 P-CSCF 可以通过 I-CSCF 确定所述用户终端所属的 S-CSCF , 然后向查询到的所述用户终端所属的 S-CSCF 完成注册请求。 之后 S-CSCF再下发被叫请求到该第三 P-CSCF, 以承载被叫业务。
进一步可选地, 如图 14所示, 所述注册选择模块 52具体可以包括: 判断单元,用于当接收到网关发送的可用 P-CSCF地址列表时,判断所述可 用 P-CSCF地址列表中是否包括本用户终端当前注册的初始 P-CSCF的主机名; 注册选择单元, 用于若不包括, 从所述可用 P-CSCF地址列表选择 P-CSCF 并注册到选择的 P-CSCF。
所述注册触发请求为携带 Update P-CSCF Address请求的 RAR。网关接收到 RAR后, 将发送 Update PDP Context消息给用户终端, 以便于用户终端完成重 注册。 所述注册选择模块 52在收到 Update PDP Context后, 根据 Update PDP Context中的可用 P-CSCF地址列表更新本地 P-CSCF列表, 并检查本端注册的 初始 P-CSCF是否在列表中, 如果不在, 用户终端将发起重新注册 P-CSCF的流 程,具体可以从网关下发的新的 P-CSCF List(列表)中选择可用的第三 P-CSCF3 行注册, 以承载本用户终端的被叫业务。 该第三 P-CSCF可以通过 I-CSCF确定 所述用户终端所属的 S-CSCF, 然后向查询到的所述用户终端所属的 S-CSCF完 成注册请求。之后 S-CSCF再下发被叫请求到该第三 P-CSCF, 以承载被叫业务。
本发明实施例在用户终端当前注册的 P-CSCF发生故障,终端能够根据网络 侧基于容灾标识的消息进行恢复处理的结构, 重新注册新的 P-CSCF, 并在新的 P-CSCF中承载该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需 要通过心跳检测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的 处理复杂的问题; 并且能够在现有的网络架构中快速完成故障恢复。
再请参见图 15, 是本发明实施例的实现终端被叫业务恢复的系统的结构示 意图, 本发明实施例的所述系统具体可以包括: 服务代理呼叫会话控制功能实 体 S-CSCF1、 至少两个代理呼叫会话控制功能实体 P-CSCF以及用户终端 4, 其 中, 所述至少两个 P-CSCF中包括第二 P-CSCF3和所述用户终端当前注册的第 一 P-CSCF2
所述 S-CSCF, 用于当接收到对所述用户终端 4的被叫请求时, 查询所述用 户终端 4当前注册的第一 P-CSCF2; 若检测到所述第一 P-CSCF2发生故障, 选 择所述第二 P-CSCF3 , 并向所述第二 P-CSCF3发送携带容灾标识的通知消息, 所述容灾标识用于指示所述可用的 P-CSCF 触发所述用户终端 4 重新注册 P-CSCF;
所述第二 P-CSCF3, 用于触发所述用户终端 4重新注册 P-CSCF;
所述 S-CSCF, 还用于在接收到所述用户终端 4重新注册的 P-CSCF发送的 注册完成消息时,将所述被叫请求下发给所述重新注册的 P-CSCF以承载所述用 户终端 4的被叫业务;
其中,所述第二 P-CSCF具体通过策略与计费规则功能实体 PCRF触发所述 用户终端重新注册 P-CSCF。
进一步可选地, 如图 15所示, 所述系统还包括: DNS服务器 5;
所述 S-CSCF, 还用于在所述 DNS服务器 5中根据所述第一 P-CSCF2的主 机名配置第一标识和第二标识, 其中, 所述第一标识包括所述第一 P-CSCF2的 IP地址, 所述第二标识包括所述第二 P-CSCF3的 IP地址。
进一步可选地, 如图 15所示, 所述系统还可以包括: 策略与计费规则功能 实体 PCRF6;
所述第二 P-CSCF3 , 具体用于根据所述 S-CSCF发送的携带用户名和容灾 标识的通知消息,生成携带 P-CSCF重选标识和所述用户名的重选请求, 并将所 述重选请求发送给所述 PCRF6;
所述 PCRF6, 用于根据所述 P-CSCF重选标识通知所述用户名所指示的用 户终端 4重选 P-CSCF以承载所述用户终端 4的被叫业务。
进一步可选地, 如图 15所示, 所述系统还可以包括: 路由代理节点 DRA7; 所述 DRA7 , 用于接收所述第二 P-CSCF3发送的重选请求, 并将所述重选 请求发送给所述 PCRF6。
进一步可选地, 如图 15所示, 所述系统还可以包括: 与所述用户终端 4相 连的网关 8;
所述 PCRF6 ,具体用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用 户名的重选请求时, 生成注册触发请求, 并向所述网关 8发送所述注册触发请 求;
所述网关 8,用于根据所述注册触发请求触发所述用户名所指示的用户终端 4重新注册 P-CSCF以承载所述用户终端 4的被叫业务。
进一步的, 所述网关 8, 具体用于当所述注册触发请求中携带有会话释放消 息时, 向移动管理实体 MME发送携带所述用户名的释放请求, 以使所述 MME 删除所述用户名所指示用户终端 4的用户承载; 或者
当所述注册触发请求中携带有更新 P-CSCF地址信息时, 获取可用 P-CSCF 地址列表发送给所述用户名所指示的用户终端 4,以使所述用户终端 4从所述可 用 P-CSCF地址列表中选择 P-CSCF并注册到该选择的 P-CSCF。
进一步地, 所述用户终端 4 , 还用于当检测到接入失败时, 发起注册到 P-CSCF的注册请求,以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF 承载被叫业务; 或者用于当接收到网关 8发送的可用 P-CSCF地址列表时,从所 述可用 P-CSCF地址列表选择 P-CSCF并注册到选择的 P-CSCF, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务。
具体的, 上述的用户终端 4 的具体实现可参考上述方法实施例以及装置实 施例中对被叫请求对应的作为被叫端的用户终端的描述; 上述的 S-CSCF1的具 体实现可参考上述方法实施例以及装置实施例中对 S-CSCF的描述;上述的第一 P-CSCF2以及第二 P-CSCF3的具体实现可参考上述方法实施例以及装置实施例 中对发生故障的 P-CSCF以及可用的 P-CSCF的描述; 上述的 PCRF6具体实现 可参考上述方法实施例以及装置实施例中对 PCRF的描述; 上述的网关 8可以 为 S-GW或者 P-GW,具体实现可参考上述方法实施例以及装置实施例中对网关 的描述。 在此均不赘述。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
具体的, 本发明实施例中还提供了一种网络设备, 具体的请参见图 16所示 的网络设备的结构示意图, 该网络设备具体可以为 S-CSCF或 IBCF, 其可以包 括接收装置 1200、 处理器 1100以及发送装置 1300, 其中, 所述处理器 1100用 于执行:
当所述接收装置 1200接收到对用户终端的被叫请求时, 查询所述用户终端 当前注册的初始代理呼叫会话控制功能实体 P-CSCF;
若检测到所述初始 P-CSCF发生故障, 选择可用的 P-CSCF, 并通过所述发 送装置 1300向所述可用的 P-CSCF发送通知消息, 以触发所述用户终端重新注 册 P-CSCF。
在其中一种可能的实现方式中, 处理器 1100 可以具体用于在选择可用的 P-CSCF后, 通过所述发送装置 1300向所述可用的 P-CSCF发送携带容灾标识 的通知消息,所述容灾标识用于指示所述可用的 P-SCCF触发所述用户终端重新 注册 P-CSCF。 在其中另一种可能的实现方式中, 处理器 1100可以具体用于在 选择可用的 P-CSCF后, 通过所述发送装置 1300向所述可用的 P-CSCF发送所 述用户终端的被叫请求,以便所述可用的 P-CSCF确定没有存储被叫用户的注册 数据时, 触发所述用户终端重新发起 IMS注册。
处理器 1100还可以用于在所述接收装置 1200接收到所述用户终端重新注 册的 P-CSCF发送的注册完成消息时, 将所述被叫请求通过所述发送装置 1300 下发给所述重新注册的 P-CSCF以承载所述用户终端的被叫业务。
其中, 所述可用的 P-CSCF 具体通过 PCRF 触发所述用户终端重新注册 P-CSCF。
进一步可选地, 所述处理器 1100在执行若检测到所述初始 P-CSCF发生故 障, 选择可用的 P-CSCF, 并向所述可用的 P-CSCF发送所述通知消息之前, 还 用于执行:
为所述初始 P-CSCF配置第一标识和第二标识, 其中, 所述第一标识包括所 述初始 P-CSCF的 IP地址,所述第二标识包括除所述初始 P-CSCF外的 P-CSCF 的 IP地址。
进一步可选地, 所述处理器 1100在执行为所述初始 P-CSCF配置第一标识 和第二标识时, 具体用于执行:
在域名系统 DNS服务器中根据所述初始 P-CSCF的主机名配置第一标识和 第二标识。
进一步可选地, 所述处理器 1100在执行若检测到所述初始 P-CSCF发生故 障, 选择可用的 P-CSCF, 并向所述可用的 P-CSCF发送所述通知消息, 具体用 于执行:
获取为所述初始 P-CSCF配置的第一标识和第二标识;
若根据获取的所述第一标识检测到所述第一标识对应的初始 P-CSCF 发生 故障, 将所述第二标识对应的 P-CSCF作为可用的 P-CSCF;
根据所述第二标识向可用的 P-CSCF发送所述通知消息。
进一步可选地, 所述处理器 1100在执行所述将所述被叫请求下发给所述重 新注册的 P-CSCF以承载所述用户终端的被叫业务时,具体用于将所述被叫请求 发送给所述重新注册的 P-CSCF, 以使所述重新注册的 P-CSCF将该被叫请求发 送给所述用户终端执行被叫业务。
本发明实施例在接收到被叫请求后, 如果检测到该被叫请求对应的作为被 叫端的用户终端当前注册的 P-CSCF发生故障 ,通过生成相应的携带容灾标识的 消息来最终触发终端进行重新注册 P-CSCF , 并在重新注册的 P-CSCF中承载该 用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检测 所导致的双主故障问题以及由于需要对外呈现同一 IP 所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
具体的, 本发明实施例还提供了另一种网络设备, 具体请参见如图 17A所 述的另一种网络设备的结构示意图, 该网络设备具体可以为 P-CSCF, 其可以包 括接收装置 2200、 处理器 2100以及发送装置 2300, 其中, 所述处理器 2100用 于执行:
通过所述接收装置 2200接收服务呼叫会话控制功能实体 S-CSCF发送的携 带用户名的通知消息;
若解析到所述通知消息中还包括容灾标识,生成携带 P-CSCF重选标识和所 述用户名的重选请求;
通过所述发送装置 2300向管理所述用户名所指示的用户终端的策略与计费 规则功能实体 PCRF发送所述重选请求,以使所述 PCRF根据所述 P-CSCF重选 标识通知所述用户名所指示的用户终端重选 P-CSCF 以承载所述用户终端的被 叫业务;
其中,携带所述容灾标识的通知消息是所述 S-CSCF在接收到的被叫请求对 应的用户终端所注册的 P-CSCF发生故障时生成的,所述容灾标识用于指示触发 所述用户终端重新注册 P-CSCF。
进一步可选地, 所述处理器 2100在执行向管理所述用户名所指示的用户终 端的策略与计费规则功能实体 PCRF发送所述重选请求时, 具体用于执行: 将所述重选请求发送给路由代理节点 DRA, 以使所述 DRA根据所述重选 请求中的用户名将所述重选请求发送给管理所述用户名所指示的用户终端的
PCRF。
进一步可选地, 所述处理器 2100在执行若解析到所述通知消息中还包括容 灾标识,生成携带 P-CSCF重选标识和所述用户名的重选请求之前,还用于执行: 判断所述用户名所指示的用户终端是否在本端注册;
若未在本端注册, 则执行所述若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求。
进一步可选地, 所述处理器 2100还用于执行:
当接收到用户终端的注册请求时,向所述用户终端所属的 S-CSCF发送注册 完成消息以完成用户终端的注册登记。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
本发明还提供了一种实现终端被叫业务恢复的装置,如图 17B所示。图 17B 所示的该装置可以是 P-CSCF , 该装置包括接收装置 2200,、 处理器 2100,以及发 送装置 2300,, 其中, 所述处理器 2100,用于执行:
通过所述接收装置 2200'接收对用户终端的被叫请求;
确定没有存储被叫用户的注册数据; 通过所述发送装置 2300,向管理所述用户终端的 PCRF发送触发所述用户终 端重新发起 IMS注册的请求。
其中,处理器 2100,通过所述接收装置 2200,接收 S-CSCF或 IBCF发送的对 所述用户终端的被叫请求。
可选地, 处理器 2100'可以具体用于通过所述发送装置 2300'向所述 PCRF 发送携带重注册标识的请求, 所述重注册标识用于触发所述用户终端重新发起 IMS 注册。 在其中一种可能的实现方式中, 所述携带重注册标识的请求可以是 STR或 AAR。
可选地, 处理器 2100,在确定没有存储被叫用户的注册数据时, 具体用于确 定图 17B所示的装置没有存储被叫用户的注册数据。 具体的, 本发明实施例还提供了又一种网络设备, 具体请参见如图 18所示 的又一种网络设备的结构示意图, 该网络设备具体可以为 PCRF, 其可以包括接 收装置 3200、 处理器 3100以及发送装置 3300, 其中, 所述处理器 3100用于执 行:
当所述接收装置 3200接收到 P-CSCF发送的携带 P-CSCF重选标识和用户 名的重选请求时, 生成注册触发请求;
通过所述发送装置 3300向与所述用户名所指示的用户终端相连的网关发送 所述生成的注册触发请求, 以使所述网关触发所述用户名所指示的用户终端重 新注册 P-CSCF以承载所述用户终端的被叫业务;
其中,所述重选请求是所述 P-CSCF根据 S-CSCF发送的携带用户名和用于 指示触发所述用户名所指示的用户终端重新注册 P-CSCF 的容灾标识的通知消 息生成的。
进一步可选地, 所述处理器 3100 在执行当接收到 P-CSCF 发送的携带 P-CSCF重选标识和用户名的重选请求时, 生成注册触发请求, 具体用于执行: 当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生 成携带会话释放消息的注册触发请求; 其中, 所述会话释放消息用于指示与所述用户名所指示的用户终端相连的 网关请求移动管理实体 ΜΜΕ删除用户的用户承载。
进一步可选地, 所述处理器 3100在执行所述当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时, 生成注册触发请求, 具体用于执行: 当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时,生 成携带更新 P-CSCF地址信息的注册触发请求;
其中,所述更新 P-CSCF地址信息用于指示与所述用户名所指示的用户终端 相连的网关生成可用 P-CSCF地址列表发送给所述用户名所指示的用户终端。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
具体的, 本发明实施例还提供了再一种网络设备, 具体请参见如图 19所示 的又一种网络设备的结构示意图,该网络设备具体可以为 S-GW或者 P-GW,其 可以包括接收装置 4200、 处理器 4100以及发送装置 4300, 其中, 所述处理器 4100用于执行:
在所述接收装置 4200接收到策略与计费规则功能实体 PCRF发送的携带用 户名的注册触发请求时, 触发所述用户名所指示的用户终端重新注册 P-CSCF 以承载所述用户终端的被叫业务;
其中,所述注册触发请求是所述 PCRF在接收到 P-CSCF发送的携带 P-CSCF 重选标识和用户名的重选请求时生成的; 所述重选请求是所述 P-CSCF 根据 S-CSCF 发送的携带用户名和用于指示触发所述用户名所指示的用户终端重新 注册 P-CSCF的容灾标识的通知消息生成的。
进一步可选地, 所述处理器 4100在执行所述触发所述用户名所指示的用户 终端重新注册 P-CSCF, 具体用于执行:
当所述注册触发请求中携带有会话释放消息时,向移动管理实体 MME发送 携带所述用户名的释放请求 ,以使所述 MME删除所述用户名所指示用户终端的 用户承载; 或者
当所述注册触发请求中携带有更新 P-CSCF地址信息时, 获取可用 P-CSCF 地址列表发送给所述用户名所指示的用户终端, 以使所述用户终端从所述可用 P-CSCF地址列表中选择 P-CSCF并注册到该选择的 P-CSCF。
本发明实施例在用户终端当前注册的 P-CSCF发生故障 ,根据携带容灾标识 的消息来最终触发终端进行重新注册 P-CSCF, 并在重新注册的 P-CSCF中承载 该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需要通过心跳检 测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的处理复杂的问 题; 并且能够在现有的网络架构中快速完成故障恢复。
具体地, 本发明实施例还提供了一种用户设备, 请参见图 20所述的用户设 备的结构示意图, 所述用户设备包括接收装置 5200、 处理器 5100以及发送装置 5300, 其中, 所述处理器 5100用于执行:
当检测到接入失败时, 通过所述发送装置 5300发起注册到 P-CSCF的注册 请求,以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务; 当所述接收装置 5200接收到网关发送的可用 P-CSCF地址列表时, 从所述 可用 P-CSCF地址列表选择 P-CSCF 并注册到选择的 P-CSCF, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务。
进一步可选地, 所述处理器 5100在执行当接收到网关发送的可用 P-CSCF 地址列表时, 从所述可用 P-CSCF 地址列表选择 P-CSCF 并注册到选择的 P-CSCF , 具体用于执行:
当接收到网关发送的可用 P-CSCF地址列表时,判断所述可用 P-CSCF地址 列表中是否包括本用户终端当前注册的初始 P-CSCF的主机名;
若不包括, 从所述可用 P-CSCF 地址列表选择 P-CSCF 并注册到选择的 P-CSCF。
本发明实施例在用户终端当前注册的 P-CSCF发生故障,终端能够根据网络 侧基于容灾标识的消息进行恢复处理的结构, 重新注册新的 P-CSCF, 并在新的 P-CSCF中承载该用户终端的被叫业务, 避免了现有技术中由于主备网元之间需 要通过心跳检测所导致的双主故障问题以及由于需要对外呈现同一 IP所带来的 处理复杂的问题; 并且能够在现有的网络架构中快速完成故障恢复。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程, 是可以通过计算机程序来指令相关的硬件来完成, 所述的程序可存储于一计算 机可读取存储介质中, 该程序在执行时, 可包括如上述各方法的实施例的流程。 其中, 所述的存储介质可为磁碟、 光盘、 只读存储记忆体(Read-Only Memory, ROM )或随机存储记忆体(Random Access Memory, RAM )等。
以上所揭露的仅为本发明较佳实施例而已, 当然不能以此来限定本发明之 权利范围, 因此依本发明权利要求所作的等同变化, 仍属本发明所涵盖的范围。

Claims

权 利 要 求 书
1、 一种实现终端被叫业务恢复的方法, 其特征在于, 包括:
当接收到对用户终端的被叫请求时, 查询所述用户终端当前注册的初始代 理呼叫会话控制功能实体 P-CSCF;
若检测到所述初始 P-CSCF发生故障, 选择可用的 P-CSCF, 并向所述可 用的 P-CSCF发送通知消息, 以触发所述用户终端重新注册 P-CSCF
其中, 所述可用的 P-CSCF通过策略与计费规则功能实体 PCRF触发所述 用户终端重新注册 P-CSCF。
2、 如权利要求 1 所述的方法, 其特征在于, 所述向所述可用的 P-CSCF 发送通知消息, 以触发所述用户终端重新注册 P-CSCF , 包括:
向所述可用的 P-CSCF发送携带容灾标识的通知消息, 所述容灾标识用于 指示所述可用的 P-SCCF触发所述用户终端重新注册 P-CSCF。
3、 如权利要求 1 所述的方法, 其特征在于, 所述向所述可用的 P-CSCF 发送通知消息, 以触发所述用户终端重新注册 P-CSCF , 包括:
向所述可用的 P-CSCF发送所述用户终端的被叫请求;
所述可用的 P-CSCF确定没有存储被叫用户的注册数据时, 触发所述用户 终端重新发起 IMS注册。
4、 如权利要求 1-3中任一项所述的方法, 其特征在于, 所述若检测到所述 初始 P-CSCF发生故障, 选择可用的 P-CSCF, 并向所述可用的 P-CSCF发送通 知消息之前, 还包括:
为所述初始 P-CSCF配置第一标识和第二标识, 其中, 所述第一标识包括 所述初始 P-CSCF 的 IP 地址, 所述第二标识包括除所述初始 P-CSCF 外的 P-CSCF的 IP地址。
5、 如权利要求 4所述的方法, 其特征在于, 所述为所述初始 P-CSCF配置 第一标识和第二标识具体包括:
在域名系统 DNS服务器中根据所述初始 P-CSCF的主机名配置第一标识和 第二标识。
6、 如权利要求 1-5任一项所述的方法, 其特征在于, 所述若检测到所述初 始 P-CSCF发生故障, 选择可用的 P-CSCF , 并向所述可用的 P-CSCF发送所述 通知消息, 包括:
获取为所述初始 P-CSCF配置的第一标识和第二标识;
若根据获取的所述第一标识检测到所述第一标识对应的初始 P-CSCF发生 故障, 将所述第二标识对应的 P-CSCF作为可用的 P-CSCF;
根据所述第二标识向可用的 P-CSCF发送所述通知消息。
7、 如权利要求 1-6中任一项所述的方法, 其特征在于, 所述方法还包括: 在接收到所述用户终端重新注册的 P-CSCF发送的注册完成消息时, 将所 述被叫请求下发给所述重新注册的 P-CSCF以承载所述用户终端的被叫业务。
8、 如权利要求 7 所述的方法, 其特征在于, 所述将所述被叫请求下发给 所述重新注册的 P-CSCF以承载所述用户终端的被叫业务, 包括:
将所述被叫请求发送给所述重新注册的 P-CSCF , 以使所述重新注册的 P-CSCF将该被叫请求发送给所述用户终端执行被叫业务。
9、 一种实现终端被叫业务恢复的方法, 其特征在于,
接收对用户终端的被叫请求;
确定没有存储被叫用户的注册数据; 向管理所述用户终端的策略与计费规则功能实体 PCRF发送触发所述用户 终端重新发起 IMS注册的请求。
10、 如权利要求 9所述的方法, 其特征在于, 所述向管理所述用户终端的 策略与计费规则功能实体 PCRF发送触发所述用户终端重新发起 IMS注册的请 求, 包括:
向所述 PCRF发送携带重注册标识的请求, 所述重注册标识用于触发所述 用户终端重新发起 IMS注册。
11、 如权利要求 10 所述的方法, 其特征在于, 所述携带重注册标识的请 求是会话中止请求 STR或鉴权授权请求 AAR。
12、 一种实现终端被叫业务恢复的方法, 其特征在于, 包括:
接收服务呼叫会话控制功能实体 S-CSCF发送的携带用户名的通知消息; 若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF重选标识和 所述用户名的重选请求;
向管理所述用户名所指示的用户终端的策略与计费规则功能实体 PCRF发 送所述重选请求, 以使所述 PCRF根据所述 P-CSCF重选标识通知所述用户名 所指示的用户终端重选 P-CSCF以 载所述用户终端的被叫业务;
其中, 携带所述容灾标识的通知消息是所述 S-CSCF在接收到的被叫请求 对应的用户终端所注册的 P-CSCF发生故障时生成的, 所述容灾标识用于指示 触发所述用户终端重新注册 P-CSCF。
13、 如权利要求 12 所述的方法, 其特征在于, 所述向管理所述用户名所 指示的用户终端的策略与计费规则功能实体 PCRF发送所述重选请求, 包括: 将所述重选请求发送给路由代理节点 DRA, 以使所述 DRA根据所述重选 请求中的用户名将所述重选请求发送给管理所述用户名所指示的用户终端的
PCRF。
14、 如权利要求 12或 13所述的方法, 其特征在于, 在若解析到所述通知 消息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求 之前, 还包括:
判断所述用户名所指示的用户终端是否在本端注册;
若未在本端注册, 则执行所述若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求。
15、 如权利要求 12-14任一项所述的方法, 其特征在于, 还包括: 当接收到用户终端的注册请求时, 向所述用户终端所属的 S-CSCF发送注 册完成消息以完成用户终端的注册登记。
16、 一种实现终端被叫业务恢复的方法, 其特征在于, 包括:
当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时, 生成注册触发请求;
向与所述用户名所指示的用户终端相连的网关发送所述生成的注册触发 请求, 以使所述网关触发所述用户名所指示的用户终端重新注册 P-CSCF以承 载所述用户终端的被叫业务;
其中, 所述重选请求是所述 P-CSCF根据 S-CSCF发送的携带用户名和用 于指示触发所述用户名所指示的用户终端重新注册 P-CSCF的容灾标识的通知 消息生成的。
17、 如权利要求 16所述的方法, 其特征在于, 所述当接收到 P-CSCF发送 的携带 P-CSCF重选标识和用户名的重选请求时, 生成注册触发请求, 包括: 当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时, 生成携带会话释放消息的注册触发请求;
其中, 所述会话释放消息用于指示与所述用户名所指示的用户终端相连的 网关请求移动管理实体 MME删除用户的用户承载。
18、 如权利要求 17所述的方法, 其特征在于, 所述当接收到 P-CSCF发送 的携带 P-CSCF重选标识和用户名的重选请求时, 生成注册触发请求, 包括: 当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名的重选请求时, 生成携带更新 P-CSCF地址信息的注册触发请求;
其中, 所述更新 P-CSCF地址信息用于指示与所述用户名所指示的用户终 端相连的网关生成可用 P-CSCF 地址列表发送给所述用户名所指示的用户终 端。
19、 一种实现终端被叫业务恢复的方法, 其特征在于, 包括:
在接收到策略与计费规则功能实体 PCRF发送的携带用户名的注册触发请 求时, 触发所述用户名所指示的用户终端重新注册 P-CSCF以承载所述用户终 端的被叫业务;
其中, 所述注册触发请求是所述 PCRF 在接收到 P-CSCF 发送的携带 P-CSCF重选标识和用户名的重选请求时生成的; 所述重选请求是所述 P-CSCF 根据 S-CSCF发送的携带用户名和用于指示触发所述用户名所指示的用户终端 重新注册 P-CSCF的容灾标识的通知消息生成的。
20、 如权利要求 19 所述的方法, 其特征在于, 所述触发所述用户名所指 示的用户终端重新注册 P-CSCF, 包括:
当所述注册触发请求中携带有会话释放消息时, 向移动管理实体 MME发 送携带所述用户名的释放请求, 以使所述 MME删除所述用户名所指示用户终 端的用户承载; 或者
当所述注册触发请求中携带有更新 P-CSCF地址信息时,获取可用 P-CSCF 地址列表发送给所述用户名所指示的用户终端, 以使所述用户终端从所述可用 P-CSCF地址列表中选择 P-CSCF并注册到该选择的 P-CSCF。
21、 一种实现终端被叫业务恢复的方法, 其特征在于, 包括:
当检测到接入失败时, 发起注册到 P-CSCF 的注册请求, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务;
当接收到网关发送的可用 P-CSCF地址列表时, 从所述可用 P-CSCF地址 列表选择 P-CSCF并注册到选择的 P-CSCF,以便于在初始 P-CSCF发生故障时 通过重新注册的 P-CSCF承载被叫业务。
22、 如权利要求 21 所述的方法, 其特征在于, 所述当接收到网关发送的 可用 P-CSCF地址列表时, 从所述可用 P-CSCF地址列表选择 P-CSCF并注册 到选择的 P-CSCF , 包括:
当接收到网关发送的可用 P-CSCF地址列表时, 判断所述可用 P-CSCF地 址列表中是否包括本用户终端当前注册的初始 P-CSCF的主机名;
若不包括, 从所述可用 P-CSCF 地址列表选择 P-CSCF 并注册到选择的 P-CSCF。
23、 一种实现终端被叫业务恢复的装置, 其特征在于, 包括:
查询模块, 用于当接收到对用户终端的被叫请求时, 查询所述用户终端当 前注册的初始代理呼叫会话控制功能实体 P-CSCF;
处理模块,用于若检测到所述初始 P-CSCF发生故障,选择可用的 P-CSCF, 并向所述可用的 P-CSCF 发送通知消息, 以触发所述用户终端重新注册 P-CSCF; 其中, 所述可用的 P-CSCF通过策略与计费规则功能实体 PCRF触发所述 用户终端重新注册 P-CSCF。
24、 如权利要求 23 所述的装置, 其特征在于, 所述处理模块具体用于在 选择可用的 P-CSCF后,向所述可用的 P-CSCF发送携带容灾标识的通知消息, 所述容灾标识用于指示所述可用的 P-SCCF 触发所述用户终端重新注册 P-CSCF。
25、 如权利要求 23 所述的装置, 其特征在于, 所述处理模块具体用于在 选择可用的 P-CSCF后,向所述可用的 P-CSCF发送所述用户终端的被叫请求, 以便所述可用的 P-CSCF确定没有存储被叫用户的注册数据时, 触发所述用户 终端重新发起 IMS注册。
26、 如权利要求 23-25中任一项所述的装置, 其特征在于, 还包括: 配置模块, 用于为所述初始 P-CSCF配置第一标识和第二标识, 其中, 所 述第一标识包括所述初始 P-CSCF 的 IP地址, 所述第二标识包括除所述初始 P-CSCF外的 P-CSCF的 IP地址。
27、 如权利要求 26所述的装置, 其特征在于,
所述配置模块具体用于在域名系统 DNS服务器中根据所述初始 P-CSCF 的主机名配置第一标识和第二标识。
28、 如权利要求 24-27中任一项所述的装置, 其特征在于, 所述处理模块 包括:
获取单元, 用于获取为所述初始 P-CSCF配置的第一标识和第二标识; 检测单元, 用于若根据获取的所述第一标识检测到所述第一标识对应的初 始 P-CSCF发生故障, 将所述第二标识对应的 P-CSCF作为可用的 P-CSCF; 处理单元, 用于根据所述第二标识向可用的 P-CSCF发送所述通知消息。
29、 如权利要求 23-28中任一项所述的装置, 其特征在于, 所述装置还包 括:
分配模块, 用于在接收到所述用户终端重新注册的 P-CSCF发送的注册完 成消息时, 将所述被叫请求下发给所述重新注册的 P-CSCF以承载所述用户终 端的被叫业务。
30、 如权利要求 29所述的装置, 其特征在于,
所述分配模块, 具体用于将所述被叫请求发送给所述重新注册的 P-CSCF, 以使所述重新注册的 P-CSCF 将该被叫请求发送给所述用户终端执行被叫业 务。
31、 一种实现终端被叫业务恢复的装置, 其特征在于, 包括:
接收模块, 用于接收对用户终端的被叫请求;
处理模块, 用于在接收模块接收到所述被叫请求时, 确定没有存储被叫用 户的注册数据;
发送模块, 用于在所述处理模块确定没有存储所述被叫用户的注册数据 后, 向管理所述用户终端的策略与计费规则功能实体 PCRF发送触发所述用户 终端重新发起 IMS注册的请求。
32、 如权利要求 31 所述的装置, 其特征在于, 所述发送模块具体用于向 所述 PCRF发送携带重注册标识的请求, 所述重注册标识用于触发所述用户终 端重新发起 IMS注册。
33、 如权利要求 32 所述的装置, 其特征在于, 所述携带重注册标识的请 求是会话中止请求 STR或鉴权授权请求 AAR。
34、 一种实现终端被叫业务恢复的装置, 其特征在于, 包括:
接收模块, 用于接收服务呼叫会话控制功能实体 S-CSCF发送的携带用户 名的通知消息;
处理模块, 用于若解析到所述通知消息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求;
发送模块, 用于向管理所述用户名所指示的用户终端的策略与计费规则功 能实体 PCRF发送所述重选请求, 以使所述 PCRF根据所述 P-CSCF重选标识 通知所述用户名所指示的用户终端重选 P-CSCF以 载所述用户终端的被叫业 务;
其中, 携带所述容灾标识的通知消息是所述 S-CSCF在接收到的被叫请求 对应的用户终端所注册的 P-CSCF发生故障时生成的, 所述容灾标识用于指示 触发所述用户终端重新注册 P-CSCF。
35、 如权利要求 34所述的装置, 其特征在于,
所述发送模块,具体用于将所述重选请求发送给路由代理节点 DRA, 以使 所述 DRA根据所述重选请求中的用户名将所述重选请求发送给管理所述用户 名所指示的用户终端的 PCRF。
36、 如权利要求 34或 35所述的装置, 其特征在于, 还包括:
判断模块, 用于判断所述用户名所指示的用户终端是否在本端注册, 并在 判断结果为未在本端注册, 则通知所述处理模块执行所述若解析到所述通知消 息中还包括容灾标识, 生成携带 P-CSCF重选标识和所述用户名的重选请求。
37、 如权利要求 34-36任一项所述的装置, 其特征在于, 还包括: 注册模块, 用于当接收到用户终端的注册请求时, 向所述用户终端所属的 S-CSCF发送注册完成消息以完成用户终端的注册登记。
38、 一种实现终端被叫业务恢复的装置, 其特征在于, 包括:
生成模块, 用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用户名 的重选请求时, 生成注册触发请求;
发送模块, 用于向与所述用户名所指示的用户终端相连的网关发送所述生 成的注册触发请求, 以使所述网关触发所述用户名所指示的用户终端重新注册 P-CSCF 以 载所述用户终端的被叫业务;
其中, 所述重选请求是所述 P-CSCF根据 S-CSCF发送的携带用户名和用 于指示触发所述用户名所指示的用户终端重新注册 P-CSCF的容灾标识的通知 消息生成的。
39、 如权利要求 38所述的装置, 其特征在于,
所述生成模块, 具体用于当接收到 P-CSCF发送的携带 P-CSCF重选标识 和用户名的重选请求时, 生成携带会话释放消息的注册触发请求;
其中, 所述会话释放消息用于指示与所述用户名所指示的用户终端相连的 网关请求移动管理实体 MME删除用户的用户承载。
40、 如权利要求 38所述的装置, 其特征在于,
所述生成模块, 具体用于当接收到 P-CSCF发送的携带 P-CSCF重选标识 和用户名的重选请求时, 生成携带更新 P-CSCF地址信息的注册触发请求; 其中, 所述更新 P-CSCF地址信息用于指示与所述用户名所指示的用户终 端相连的网关生成可用 P-CSCF 地址列表发送给所述用户名所指示的用户终 端。
41、 一种实现终端被叫业务恢复的装置, 其特征在于, 包括:
接收模块, 用于接收到策略与计费规则功能实体 PCRF发送的携带用户名 的注册触发请求;
触发模块, 用于触发所述用户名所指示的用户终端重新注册 P-CSCF以承 载所述用户终端的被叫业务;
其中, 所述注册触发请求是所述 PCRF 在接收到 P-CSCF 发送的携带 P-CSCF重选标识和用户名的重选请求时生成的; 所述重选请求是所述 P-CSCF 根据 S-CSCF发送的携带用户名和用于指示触发所述用户名所指示的用户终端 重新注册 P-CSCF的容灾标识的通知消息生成的。
42、 如权利要求 41所述的装置, 其特征在于, 所述触发模块包括: 第一发送单元, 用于当所述注册触发请求中携带有会话释放消息时, 向移 动管理实体 MME发送携带所述用户名的释放请求, 以使所述 MME删除所述 用户名所指示用户终端的用户承载; 或者
第二发送单元, 用于当所述注册触发请求中携带有更新 P-CSCF地址信息 时, 获取可用 P-CSCF地址列表发送给所述用户名所指示的用户终端, 以使所 述用户终端从所述可用 P-CSCF 地址列表中选择 P-CSCF 并注册到该选择的 P-CSCF。
43、 一种实现终端被叫业务恢复的装置, 其特征在于, 包括:
注册发起模块, 用于当检测到接入失败时, 发起注册到 P-CSCF的注册请 求,以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务; 注册选择模块, 用于当接收到网关发送的可用 P-CSCF地址列表时, 从所 述可用 P-CSCF地址列表选择 P-CSCF并注册到选择的 P-CSCF ,以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业务。
44、 如权利要求 43所述的装置, 其特征在于, 所述注册选择模块包括: 判断单元, 用于当接收到网关发送的可用 P-CSCF地址列表时, 判断所述 可用 P-CSCF地址列表中是否包括本用户终端当前注册的初始 P-CSCF的主机 名;
注册选择单元,用于若不包括,从所述可用 P-CSCF地址列表选择 P-CSCF 并注册到选择的 P-CSCF。
45、 一种实现终端被叫业务恢复的系统, 其特征在于, 包括: 服务代理呼 叫会话控制功能实体 S-CSCF、 至少两个代理呼叫会话控制功能实体 P-CSCF 以及用户终端, 其中, 所述至少两个 P-CSCF中包括第二 P-CSCF和所述用户 终端当前注册的第一 P-CSCF, 其中
所述 S-CSCF , 用于当接收到对所述用户终端的被叫请求时, 查询所述用 户终端当前注册的第一 P-CSCF; 若检测到所述第一 P-CSCF发生故障, 选择 所述第二 P-CSCF, 并向所述第二 P-CSCF发送携带容灾标识的通知消息, 所 述容灾标识用于指示所述可用的 P-CSCF触发所述用户终端重新注册 P-CSCF; 所述第二 P-CSCF, 用于触发所述用户终端重新注册 P-CSCF;
所述 S-CSCF, 还用于在接收到所述用户终端重新注册的 P-CSCF发送的 注册完成消息时, 将所述被叫请求下发给所述重新注册的 P-CSCF以承载所述 用户终端的被叫业务;
其中, 所述第二 P-CSCF具体通过策略与计费规则功能实体 PCRF触发所 述用户终端重新注册 P-CSCF。
46、 如权利要求 45所述的系统, 其特征在于, 还包括: DNS服务器; 所述 S-CSCF, 还用于在所述 DNS服务器中根据所述第一 P-CSCF的主机 名配置第一标识和第二标识, 其中, 所述第一标识包括所述第一 P-CSCF的 IP 地址, 所述第二标识包括所述第二 P-CSCF的 IP地址。
47、 如权利要求 45或 46所述的系统, 其特征在于, 还包括: 策略与计费 规则功能实体 PCRF;
所述第二 P-CSCF, 具体用于根据所述 S-CSCF发送的携带用户名和容灾 标识的通知消息, 生成携带 P-CSCF重选标识和所述用户名的重选请求, 并将 所述重选请求发送给所述 PCRF;
所述 PCRF, 用于根据所述 P-CSCF重选标识通知所述用户名所指示的用 户终端重选 P-CSCF以 载所述用户终端的被叫业务。
48、如权利要求 47所述的系统,其特征在于,还包括:路由代理节点 DRA; 所述 DRA, 用于接收所述第二 P-CSCF发送的重选请求, 并将所述重选请 求发送给所述 PCRF。
49、 如权利要求 47或 48所述的系统, 其特征在于, 还包括: 与所述用户 终端相连的网关;
所述 PCRF,具体用于当接收到 P-CSCF发送的携带 P-CSCF重选标识和用 户名的重选请求时,生成注册触发请求,并向所述网关发送所述注册触发请求; 所述网关, 用于根据所述注册触发请求触发所述用户名所指示的用户终端 重新注册 P-CSCF以 载所述用户终端的被叫业务。
50、 如权利要求 49所述的系统, 其特征在于,
所述网关, 具体用于当所述注册触发请求中携带有会话释放消息时, 向移 动管理实体 MME发送携带所述用户名的释放请求, 以使所述 MME删除所述 用户名所指示用户终端的用户承载; 或者
当所述注册触发请求中携带有更新 P-CSCF地址信息时,获取可用 P-CSCF 地址列表发送给所述用户名所指示的用户终端, 以使所述用户终端从所述可用 P-CSCF地址列表中选择 P-CSCF并注册到该选择的 P-CSCF。
51、 如权利要求 50所述的系统, 其特征在于,
所述用户终端, 还用于当检测到接入失败时, 发起注册到 P-CSCF的注册 请求, 以便于在初始 P-CSCF发生故障时通过重新注册的 P-CSCF承载被叫业 务; 或者用于当接收到网关发送的可用 P-CSCF 地址列表时, 从所述可用 P-CSCF地址列表选择 P-CSCF并注册到选择的 P-CSCF,以便于在初始 P-CSCF 发生故障时通过重新注册的 P-CSCF承载被叫业务。
PCT/CN2014/081582 2013-08-07 2014-07-03 一种实现终端被叫业务恢复的方法、相关装置及系统 WO2015018248A1 (zh)

Priority Applications (11)

Application Number Priority Date Filing Date Title
ES14833808T ES2701822T3 (es) 2013-08-07 2014-07-03 Procedimiento y sistema de recuperación de un servicio llamado de un terminal
KR1020167005555A KR101902949B1 (ko) 2013-08-07 2014-07-03 단말기의 피호출 서비스를 복구하는 방법, 및 관련 장치
JP2016532216A JP6355113B2 (ja) 2013-08-07 2014-07-03 端末の着呼側サービスを回復するための方法、および関連装置
EP18183112.4A EP3515014B1 (en) 2013-08-07 2014-07-03 Method, related apparatus, and system for recovering called service of terminal
EP20209163.3A EP3843336B1 (en) 2013-08-07 2014-07-03 Method, related apparatus, and system for recovering called service of terminal
EP14833808.0A EP3024177B1 (en) 2013-08-07 2014-07-03 Method and system for recovering called service of terminal
US15/015,008 US9894110B2 (en) 2013-08-07 2016-02-03 Method, and related apparatus for recovering called service of terminal
US15/827,959 US10142376B2 (en) 2013-08-07 2017-11-30 Method, and related apparatus for recovering called service of terminal
US16/146,813 US10735480B2 (en) 2013-08-07 2018-09-28 Method, related apparatus, and system for recovering called service of terminal
US16/455,749 US11005899B2 (en) 2013-08-07 2019-06-28 Method, related apparatus, and system for recovering called service of terminal
US17/214,540 US11627168B2 (en) 2013-08-07 2021-03-26 Method, related apparatus, and system for recovering called service of terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310342761.0A CN103441862B (zh) 2013-08-07 2013-08-07 一种实现终端被叫业务恢复的方法、相关装置及系统
CN201310342761.0 2013-08-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/015,008 Continuation US9894110B2 (en) 2013-08-07 2016-02-03 Method, and related apparatus for recovering called service of terminal

Publications (1)

Publication Number Publication Date
WO2015018248A1 true WO2015018248A1 (zh) 2015-02-12

Family

ID=49695531

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/081582 WO2015018248A1 (zh) 2013-08-07 2014-07-03 一种实现终端被叫业务恢复的方法、相关装置及系统

Country Status (7)

Country Link
US (5) US9894110B2 (zh)
EP (3) EP3843336B1 (zh)
JP (1) JP6355113B2 (zh)
KR (1) KR101902949B1 (zh)
CN (2) CN103441862B (zh)
ES (2) ES2701822T3 (zh)
WO (1) WO2015018248A1 (zh)

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103441862B (zh) * 2013-08-07 2017-08-04 华为技术有限公司 一种实现终端被叫业务恢复的方法、相关装置及系统
US10148487B2 (en) * 2013-09-24 2018-12-04 Nec Corporation Methods and apparatuses for facilitating P-CSCF restoration when a P-CSCF failure has occurred
US20150195864A1 (en) * 2014-01-09 2015-07-09 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatuses for p-cscf restoration based on ue capabilities
CN104168275B (zh) * 2014-08-08 2018-03-30 中国联合网络通信集团有限公司 一种注册控制方法和装置
CN104168208B (zh) * 2014-08-27 2017-06-09 中国联合网络通信集团有限公司 一种网络异地容灾的实现方法及装置
CN105577407A (zh) * 2014-10-16 2016-05-11 中国移动通信集团公司 一种容灾处理方法、装置、终端和网络侧设备
CN104320800A (zh) * 2014-10-21 2015-01-28 中国联合网络通信集团有限公司 一种终端重注册的方法及装置
CN104284360B (zh) * 2014-10-21 2018-05-25 中国联合网络通信集团有限公司 P-cscf故障处理方法和系统
CN105592486B (zh) * 2014-10-21 2021-01-26 中兴通讯股份有限公司 一种容灾方法及网元、服务器
CN104410526B (zh) * 2014-11-28 2018-09-21 华为技术有限公司 一种呼叫控制方法、Diameter协议转发设备及系统
CN106063220B (zh) 2015-02-10 2019-09-03 华为技术有限公司 一种语音业务注册方法及数字终端
CN106330415B (zh) * 2015-06-19 2021-04-02 中兴通讯股份有限公司 一种容灾方法、装置及通信系统
CN106470441B (zh) * 2015-08-20 2019-11-29 中国电信股份有限公司 一种容灾恢复方法和系统
CN106488475B (zh) * 2015-08-28 2019-10-25 华为技术有限公司 一种实现终端被叫业务恢复的方法及装置
CN105517031B (zh) * 2015-12-07 2019-03-05 中国联合网络通信集团有限公司 Pcrf故障后业务恢复的方法及装置
US20180132291A1 (en) * 2016-11-04 2018-05-10 T-Mobile Usa, Inc. SIP Call Continuity Upon Failure
CN108124242A (zh) * 2016-11-28 2018-06-05 中国移动通信有限公司研究院 一种消息投递的系统、方法及装置
CN108632844B (zh) * 2017-03-15 2019-09-17 电信科学技术研究院 信息处理方法、装置及电子设备
CN108632936B (zh) * 2017-03-21 2022-11-22 中兴通讯股份有限公司 一种锚定核心网的方法、ue和pgw
CN108737322B (zh) * 2017-04-13 2021-01-26 展讯通信(上海)有限公司 业务恢复方法、装置及移动终端
CN108924893B (zh) * 2017-04-26 2020-12-25 中国移动通信有限公司研究院 一种承载释放方法、装置、mme及sae-gw
CN109936462B (zh) * 2017-12-15 2021-11-30 华为技术有限公司 容灾方法及装置
CN109995721B (zh) * 2017-12-29 2021-10-22 华为技术有限公司 业务请求处理方法、装置及通信系统
CN109995726B (zh) * 2017-12-30 2021-08-03 中国移动通信集团辽宁有限公司 代理呼叫会话控制功能容灾方法、装置、设备及介质
CN110049070B (zh) * 2018-01-15 2021-09-14 华为技术有限公司 事件通知方法及相关设备
US20210266349A1 (en) * 2018-07-02 2021-08-26 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced p-cscf restoration procedure
CN112954264B (zh) * 2019-12-10 2023-04-18 浙江宇视科技有限公司 一种平台备份保护方法及装置
US11343686B2 (en) * 2020-03-11 2022-05-24 Verizon Patent And Licensing Inc. Systems and methods for call session control function failover using dynamic routing techniques
US11864265B2 (en) * 2021-10-13 2024-01-02 T-Mobile Usa, Inc. Proxy-call session control function (P-CSCF) restoration
US20230217235A1 (en) * 2021-12-30 2023-07-06 T-Mobile Usa, Inc. Hss-based p-cscf restoration triggered by as

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1905472A (zh) * 2005-07-27 2007-01-31 华为技术有限公司 一种ims网络可靠性实现方法
CN101212814A (zh) * 2006-12-29 2008-07-02 中国移动通信集团公司 网元数据失效或发生故障后的业务处理方法、系统及网元
CN101217407A (zh) * 2008-01-04 2008-07-09 中兴通讯股份有限公司 一种代理呼叫会话控制功能故障的处理方法
CN101426261A (zh) * 2008-12-17 2009-05-06 华为技术有限公司 多媒体子系统业务处理的方法、p-cscf、i-cscf和多媒体子系统
CN101489242A (zh) * 2008-01-18 2009-07-22 华为技术有限公司 一种恢复业务的方法和装置
CN101489245A (zh) * 2008-12-31 2009-07-22 华为技术有限公司 网络容灾方法、终端和呼叫会话控制功能实体
CN102316435A (zh) * 2010-06-29 2012-01-11 上海贝尔股份有限公司 一种接入网络系统中用于更新用户设备p-cscf配置的方法及其装置
CN103441862A (zh) * 2013-08-07 2013-12-11 华为技术有限公司 一种实现终端被叫业务恢复的方法、相关装置及系统

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100571134C (zh) * 2005-04-30 2009-12-16 华为技术有限公司 在ip多媒体子系统中认证用户终端的方法
US7975037B2 (en) * 2005-07-29 2011-07-05 Verizon Patent And Licensing Inc. Policy engine in an Internet Protocol multimedia subsystem
CN101366311B (zh) * 2006-02-07 2011-12-14 艾利森电话股份有限公司 通信网络中使用的方法和设备
CN100512495C (zh) * 2006-02-20 2009-07-08 华为技术有限公司 一种实现被叫服务的方法和系统
CN101052054B (zh) * 2006-04-04 2010-09-08 中兴通讯股份有限公司 保持ps域和ims域ip地址注销一致性的方法
US9635062B2 (en) * 2006-06-20 2017-04-25 Telefonaktiebolaget Lm Ericsson (Publ) Loss of signalling bearer transport
JP4864797B2 (ja) * 2006-09-11 2012-02-01 Kddi株式会社 P−cscf高速ハンドオフシステム及びp−cscf高速ハンドオフ方法
PT2099156E (pt) 2006-12-29 2014-07-18 Huawei Tech Co Ltd Método, sistema e elemento de rede para processamento de serviço após invalidação de dados de elemento de rede e ocorrência de falha
KR100946900B1 (ko) * 2007-01-11 2010-03-09 삼성전자주식회사 Ims 재등록 방법 및 이를 위한 시스템
US20080182575A1 (en) * 2007-01-30 2008-07-31 Motorola, Inc. Ims reliability mechanisms
ES2619423T3 (es) * 2007-05-22 2017-06-26 Telefonaktiebolaget Lm Ericsson (Publ) Método, aparatos y programa informático para configurar dinámicamente una función de control de sesión de llamada proxy del subsistema multimedia IP desde un servidor de reglas de control de política
WO2008154955A1 (en) * 2007-06-19 2008-12-24 Telefonaktiebolaget Lm Ericsson (Publ) Ims recovery after hss failure
EP2177012B1 (en) * 2007-07-10 2018-12-26 Telefonaktiebolaget LM Ericsson (publ) Method and apparatuses for ims recovery upon restart of a s-cscf
CN101127722A (zh) * 2007-09-17 2008-02-20 中兴通讯股份有限公司 核心网元重启/故障恢复后的处理方法
CN102138312B (zh) * 2007-09-28 2016-11-23 爱立信电话股份有限公司 Ip多媒体子系统网络中的故障恢复
WO2009049684A1 (en) * 2007-10-19 2009-04-23 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for notifying an application function of resource restrictions relating to a communication session
US8949950B2 (en) * 2007-12-20 2015-02-03 Telefonaktiebolaget L M Ericsson (Publ) Selection of successive authentication methods
US9241253B2 (en) * 2008-01-24 2016-01-19 At&T Intellectual Property I, L.P. System and method of providing a user with a registration review in IMS system
US8316457B1 (en) * 2008-04-29 2012-11-20 Sprint Communications Company L.P. Partitioned IP multimedia subsystem call session control function
WO2010061119A1 (fr) * 2008-11-26 2010-06-03 France Telecom Procede et systeme de regulation du trafic de redemarrage dans un reseau de telecommunications
JP5537349B2 (ja) * 2010-02-11 2014-07-02 Kddi株式会社 端末の接続を継続した状態でsipサーバを変更する方法及びシステム
WO2011131240A1 (en) * 2010-04-21 2011-10-27 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for an ims restoration procedure
US20130100863A1 (en) * 2010-06-21 2013-04-25 Telefonaktiebolaget Lm Ericsson (Publ) Methods And Apparatuses For Handling Time Zone Information In An Internet Protocol Multimedia Subsystem, IMS, Network
CN102316438B (zh) * 2010-06-29 2016-01-20 中兴通讯股份有限公司 一种获取用户位置的方法和系统
JP5356331B2 (ja) * 2010-08-04 2013-12-04 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法及び優先度制御ノード
EP2456159B1 (en) * 2010-11-19 2018-02-21 Nokia Solutions and Networks Oy Method and apparatus for user registration in ims
JP4927213B1 (ja) * 2010-12-03 2012-05-09 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法、ゲートウェイ装置、移動管理ノード及び呼セッション制御サーバ装置
CN103096243B (zh) * 2011-11-07 2017-10-03 中兴通讯股份有限公司 终端的呼叫处理方法、装置及系统
US9467907B2 (en) * 2012-03-12 2016-10-11 Telefonaktiebolaget Lm Ericsson (Publ) Handover of user-equipment (UE) undetected emergency calls
US9294618B2 (en) * 2012-04-03 2016-03-22 Telefonaktiebolaget L M Ericsson (Publ) Call-back to a UE that has made an emergency call via a visited IMS network
EP2658202B1 (en) * 2012-04-24 2017-10-11 Telefonaktiebolaget LM Ericsson (publ) Identification of an ip-can session in a policy and charging control apparatus
EP2853072B1 (en) 2012-05-21 2018-02-14 Telefonaktiebolaget LM Ericsson (publ) Method and apparatus for handling p-cscf failure and restoring connectivity
US20150282242A1 (en) * 2012-10-01 2015-10-01 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for processing an ims session
WO2014067558A1 (en) * 2012-10-30 2014-05-08 Nokia Solutions And Networks Oy User location based network registration
CN103078846B (zh) * 2012-12-20 2017-03-15 华为技术有限公司 Ims架构下信息传送方法、装置和通信系统
US20140341085A1 (en) * 2013-05-14 2014-11-20 Qualcomm Incorporated Selecting an application server at which to register one or more user equipments for an internet protocol multimedia subsystem (ims) session
US10148487B2 (en) * 2013-09-24 2018-12-04 Nec Corporation Methods and apparatuses for facilitating P-CSCF restoration when a P-CSCF failure has occurred

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1905472A (zh) * 2005-07-27 2007-01-31 华为技术有限公司 一种ims网络可靠性实现方法
CN101212814A (zh) * 2006-12-29 2008-07-02 中国移动通信集团公司 网元数据失效或发生故障后的业务处理方法、系统及网元
CN101217407A (zh) * 2008-01-04 2008-07-09 中兴通讯股份有限公司 一种代理呼叫会话控制功能故障的处理方法
CN101489242A (zh) * 2008-01-18 2009-07-22 华为技术有限公司 一种恢复业务的方法和装置
CN101426261A (zh) * 2008-12-17 2009-05-06 华为技术有限公司 多媒体子系统业务处理的方法、p-cscf、i-cscf和多媒体子系统
CN101489245A (zh) * 2008-12-31 2009-07-22 华为技术有限公司 网络容灾方法、终端和呼叫会话控制功能实体
CN102316435A (zh) * 2010-06-29 2012-01-11 上海贝尔股份有限公司 一种接入网络系统中用于更新用户设备p-cscf配置的方法及其装置
CN103441862A (zh) * 2013-08-07 2013-12-11 华为技术有限公司 一种实现终端被叫业务恢复的方法、相关装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3024177A4 *

Also Published As

Publication number Publication date
EP3024177B1 (en) 2018-09-19
CN107276811B (zh) 2021-02-09
US11627168B2 (en) 2023-04-11
US20160156678A1 (en) 2016-06-02
US10735480B2 (en) 2020-08-04
US20190036982A1 (en) 2019-01-31
US20210218781A1 (en) 2021-07-15
CN107276811A (zh) 2017-10-20
US11005899B2 (en) 2021-05-11
KR20160038050A (ko) 2016-04-06
EP3843336B1 (en) 2022-10-26
US10142376B2 (en) 2018-11-27
US9894110B2 (en) 2018-02-13
EP3843336A1 (en) 2021-06-30
JP6355113B2 (ja) 2018-07-11
CN103441862A (zh) 2013-12-11
EP3515014B1 (en) 2020-11-25
EP3515014A1 (en) 2019-07-24
CN103441862B (zh) 2017-08-04
KR101902949B1 (ko) 2018-11-13
US20180091562A1 (en) 2018-03-29
ES2848110T3 (es) 2021-08-05
ES2701822T3 (es) 2019-02-26
EP3024177A4 (en) 2016-07-20
EP3024177A1 (en) 2016-05-25
JP2016533087A (ja) 2016-10-20
US20190319992A1 (en) 2019-10-17

Similar Documents

Publication Publication Date Title
US11627168B2 (en) Method, related apparatus, and system for recovering called service of terminal
US11412371B2 (en) Method, apparatus, and system for disaster recovery of ims
WO2018076972A1 (zh) 一种故障切换方法、装置及系统
US8719617B2 (en) Method and device for realizing IP multimedia subsystem disaster tolerance
US20150195864A1 (en) Methods and apparatuses for p-cscf restoration based on ue capabilities
WO2017036227A1 (zh) 一种实现终端被叫业务恢复的方法及装置
WO2020063412A1 (zh) 一种pdu会话重建方法、装置、系统及存储介质
WO2011054270A1 (zh) 一种实现位置区域更新的方法及系统
WO2019183846A1 (zh) 切换的方法、用户设备、网络设备及计算机存储介质

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016532216

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2014833808

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20167005555

Country of ref document: KR

Kind code of ref document: A