WO2015018248A1 - 一种实现终端被叫业务恢复的方法、相关装置及系统 - Google Patents
一种实现终端被叫业务恢复的方法、相关装置及系统 Download PDFInfo
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 128
- 238000011084 recovery Methods 0.000 claims abstract description 123
- 238000012545 processing Methods 0.000 claims description 53
- 238000001514 detection method Methods 0.000 claims description 28
- 230000001960 triggered effect Effects 0.000 claims description 25
- 230000000977 initiatory effect Effects 0.000 claims description 6
- 238000013475 authorization Methods 0.000 claims description 4
- 239000000725 suspension Substances 0.000 claims 2
- 230000006870 function Effects 0.000 description 41
- 238000010586 diagram Methods 0.000 description 14
- 230000004044 response Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000009966 trimming Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
- H04L12/1407—Policy-and-charging control [PCC] architecture
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1046—Call 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).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
Abstract
Description
Claims
Priority Applications (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020167005555A KR101902949B1 (ko) | 2013-08-07 | 2014-07-03 | 단말기의 피호출 서비스를 복구하는 방법, 및 관련 장치 |
ES14833808T ES2701822T3 (es) | 2013-08-07 | 2014-07-03 | Procedimiento y sistema de recuperación de un servicio llamado de un 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 |
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 |
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.0 | 2013-08-07 | ||
CN201310342761.0A CN103441862B (zh) | 2013-08-07 | 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) | EP3024177B1 (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 (31)
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 | 中国移动通信集团公司 | 一种容灾处理方法、装置、终端和网络侧设备 |
CN105592486B (zh) * | 2014-10-21 | 2021-01-26 | 中兴通讯股份有限公司 | 一种容灾方法及网元、服务器 |
CN104320800A (zh) * | 2014-10-21 | 2015-01-28 | 中国联合网络通信集团有限公司 | 一种终端重注册的方法及装置 |
CN104284360B (zh) * | 2014-10-21 | 2018-05-25 | 中国联合网络通信集团有限公司 | P-cscf故障处理方法和系统 |
CN104410526B (zh) * | 2014-11-28 | 2018-09-21 | 华为技术有限公司 | 一种呼叫控制方法、Diameter协议转发设备及系统 |
EP3249872B1 (en) | 2015-02-10 | 2021-04-07 | Huawei Technologies Co., Ltd. | Voice service registration method and digital terminal |
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 | 华为技术有限公司 | 事件通知方法及相关设备 |
WO2020008292A1 (en) * | 2018-07-02 | 2020-01-09 | 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 |
US11729656B2 (en) * | 2021-02-01 | 2023-08-15 | T-Mobile Usa, Inc. | P-CSCF registration and discovery mechanism |
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)
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)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100571134C (zh) * | 2005-04-30 | 2009-12-16 | 华为技术有限公司 | 在ip多媒体子系统中认证用户终端的方法 |
US8325905B2 (en) * | 2005-07-29 | 2012-12-04 | Verizon Patent And Licensing Inc. | Routing calls in a network |
JP4903816B2 (ja) * | 2006-02-07 | 2012-03-28 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | 通信ネットワークにおいて用いる方法及び装置 |
CN100512495C (zh) * | 2006-02-20 | 2009-07-08 | 华为技术有限公司 | 一种实现被叫服务的方法和系统 |
CN101052054B (zh) * | 2006-04-04 | 2010-09-08 | 中兴通讯股份有限公司 | 保持ps域和ims域ip地址注销一致性的方法 |
CN101467418B (zh) * | 2006-06-20 | 2013-05-08 | 艾利森电话股份有限公司 | 用于请求和获取有损的信令承载传输的通知的方法和装置 |
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 |
US8560890B2 (en) * | 2007-06-19 | 2013-10-15 | Telefonaktiebolaget Lm Ericsson (Publ) | IMS recovery after HSS failure |
US8438257B2 (en) * | 2007-07-10 | 2013-05-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, apparatuses and computer program for IMS recovery upon restart of a S-CSCF |
CN101127722A (zh) * | 2007-09-17 | 2008-02-20 | 中兴通讯股份有限公司 | 核心网元重启/故障恢复后的处理方法 |
WO2009039894A1 (en) * | 2007-09-28 | 2009-04-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Failure recovery in an ip multimedia subsystem network |
US8688814B2 (en) * | 2007-10-19 | 2014-04-01 | Telefonaktiebolaget L M 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サーバを変更する方法及びシステム |
US9083714B2 (en) * | 2010-04-21 | 2015-07-14 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for an IMS restoration procedure |
WO2011162644A1 (en) * | 2010-06-21 | 2011-12-29 | Telefonaktiebolaget L M 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 |
EP2835027B1 (en) * | 2012-04-03 | 2015-12-30 | Telefonaktiebolaget L M Ericsson (publ) | Call-back to a ue that has made an emergency call in 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 |
CN104335544B (zh) | 2012-05-21 | 2018-05-15 | 瑞典爱立信有限公司 | 用于处理p-cscf故障和恢复连接的方法和装置 |
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 |
-
2013
- 2013-08-07 CN CN201310342761.0A patent/CN103441862B/zh active Active
- 2013-08-07 CN CN201710500666.7A patent/CN107276811B/zh active Active
-
2014
- 2014-07-03 ES ES14833808T patent/ES2701822T3/es active Active
- 2014-07-03 EP EP14833808.0A patent/EP3024177B1/en active Active
- 2014-07-03 JP JP2016532216A patent/JP6355113B2/ja active Active
- 2014-07-03 EP EP20209163.3A patent/EP3843336B1/en active Active
- 2014-07-03 WO PCT/CN2014/081582 patent/WO2015018248A1/zh active Application Filing
- 2014-07-03 KR KR1020167005555A patent/KR101902949B1/ko active IP Right Grant
- 2014-07-03 EP EP18183112.4A patent/EP3515014B1/en active Active
- 2014-07-03 ES ES18183112T patent/ES2848110T3/es active Active
-
2016
- 2016-02-03 US US15/015,008 patent/US9894110B2/en active Active
-
2017
- 2017-11-30 US US15/827,959 patent/US10142376B2/en active Active
-
2018
- 2018-09-28 US US16/146,813 patent/US10735480B2/en active Active
-
2019
- 2019-06-28 US US16/455,749 patent/US11005899B2/en active Active
-
2021
- 2021-03-26 US US17/214,540 patent/US11627168B2/en active Active
Patent Citations (8)
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)
Title |
---|
See also references of EP3024177A4 * |
Also Published As
Publication number | Publication date |
---|---|
ES2701822T3 (es) | 2019-02-26 |
US20190319992A1 (en) | 2019-10-17 |
JP6355113B2 (ja) | 2018-07-11 |
US20180091562A1 (en) | 2018-03-29 |
US11627168B2 (en) | 2023-04-11 |
US20210218781A1 (en) | 2021-07-15 |
CN103441862A (zh) | 2013-12-11 |
EP3024177A4 (en) | 2016-07-20 |
EP3515014B1 (en) | 2020-11-25 |
KR20160038050A (ko) | 2016-04-06 |
JP2016533087A (ja) | 2016-10-20 |
EP3024177B1 (en) | 2018-09-19 |
EP3515014A1 (en) | 2019-07-24 |
EP3024177A1 (en) | 2016-05-25 |
US20160156678A1 (en) | 2016-06-02 |
CN107276811B (zh) | 2021-02-09 |
US20190036982A1 (en) | 2019-01-31 |
EP3843336B1 (en) | 2022-10-26 |
CN103441862B (zh) | 2017-08-04 |
EP3843336A1 (en) | 2021-06-30 |
KR101902949B1 (ko) | 2018-11-13 |
US10142376B2 (en) | 2018-11-27 |
US9894110B2 (en) | 2018-02-13 |
US10735480B2 (en) | 2020-08-04 |
US11005899B2 (en) | 2021-05-11 |
CN107276811A (zh) | 2017-10-20 |
ES2848110T3 (es) | 2021-08-05 |
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 |