WO2007012270A1 - A method for realizing the ims network reliability - Google Patents
A method for realizing the ims network reliability Download PDFInfo
- Publication number
- WO2007012270A1 WO2007012270A1 PCT/CN2006/001834 CN2006001834W WO2007012270A1 WO 2007012270 A1 WO2007012270 A1 WO 2007012270A1 CN 2006001834 W CN2006001834 W CN 2006001834W WO 2007012270 A1 WO2007012270 A1 WO 2007012270A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- entity
- user
- cscf
- network
- network entity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
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/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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- 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
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
Definitions
- the present invention relates to an IP Multimedia Subsystem (IMS) technology in the field of communications, and more particularly to a method for implementing IMS network reliability.
- IMS IP Multimedia Subsystem
- IMS Internet multimedia subsystem
- Many IMS related specifications including network architecture, interfaces, protocols, etc., are defined in 3GPP and TISPAN standards.
- the IMS uses the SIP protocol as call control signaling.
- the subscription data of the IMS user is centralized in the Home Subscriber Server (HSS) management, the service is provided by the Application Server (AS), and the session control is performed by the Service-Call Session Control Function (S-CSCF) entity, and the S-CSCF entity Separated from the AS in the network structure, the service is triggered by the S-CSCF entity to the AS, and multiple ASs can work together.
- HSS Home Subscriber Server
- AS Application Server
- S-CSCF Service-Call Session Control Function
- the user accesses the IMS through the current location proxy node proxy-call session control function (P-CSCF) entity, and the session and service control are completed by the home domain service node of the registered location, so the user can get the same service at different access points.
- P-CSCF proxy-call session control function
- the IMS network implements separation of service management, session control, and bearer access, as well as service provision independent of access and location.
- each IMS network device usually has multiple processing boards.
- the processing board is configured as a primary standby relationship.
- the service is provided by the active working board.
- the corresponding standby working board switches to work as the primary replacement fault board.
- IMS network reliability In addition to the reliability mechanism within the device, operators are also concerned about the disaster tolerance of the network.
- the IMS network contains the above multiple network entities and has strong correlation with each other.
- the IMS network is based on the SIP protocol.
- RFC3263 Locating SIP Servers
- DNS domain name server
- This mechanism is used to deliver a message to its backup entity when an entity in the SIP message path fails.
- FIG. 1A The user obtains the addresses of the network entities P1 and P2 through DNS resolution, and knows that the network entity P1 has a higher priority than the network entity P2.
- the network entity PI fails and the user fails, the user can send a call request to the low priority backup network entity P2.
- I-CSCF query-call session control function
- P-CSCF entity or S-CSCF entity fails, this mechanism cannot be used because the entity saves the state related to the user service, even if the message can be sent to another P-CSCF entity or S-CSCF entity, because there is no relevant state data, Unable to process the received message.
- 3GPP TS23228 describes the process of user registration and re-registration.
- the method for implementing the IMS network reliability by using the existing user registration/re-registration process is as shown in FIG. 1B:
- the 200 response sent by the S-CSCF entity to the terminal indicating that the registration is successful carries the interval duration for requesting the terminal to initiate re-registration.
- the terminal initiates re-registration before the interval duration expires.
- the I-CSCF entity routes the re-registration request REGISTER to the S-CSCF entity that the user has registered.
- the J-CSCF entity acquires the S-CSCF entity capability set requested by the user from the HSS, and the I-CSCF entity reselects an S-CSCF entity according to the capability set information, and routes the REGISTER request to The newly selected S-CSCF entity.
- the S-CSCF entity considers that this is a new user registration request, and responds to the 401 response to authenticate the user. After the authentication succeeds, the response to 200 indicates that the registration is successful.
- the process of re-selecting the S-CSCF entity by the I-CSCF entity ensures that the subsequent service requested by the user can be new.
- the S-CSCF entity continues to be available.
- the 3GPP stipulates that in the registration success 200 response returned by the S-CSCF entity to the user terminal (UE), the terminal re-registration duration is 600000s (equivalent to one week:). Of course, the S-CSCF entity may also decide to shorten the user's weight according to the local policy. Registration time. However, if the re-registration time of the user is too short, a large number of re-registration messages will be generated, occupying network resources and wireless air interface resources. In RFC3261, the default re-registration duration is 7200s. When the user registers successfully until the user initiates the re-registration, if the corresponding S-CSCF entity fails, the user will not be able to get the service.
- the user will not be able to pick up the incoming call during this time.
- the network load and excessive network resources are increased.
- the above solution is only applicable to the S-CSCF entity failure situation, and is not applicable to the case where other IMS network entities such as the P-CSCF entity are faulty. Summary of the invention
- the present invention provides a method for implementing IMS network reliability, which solves the problem that the user service may be interrupted for a long time due to the failure of the network entity during the registration of the user to the re-registration of the user in the existing IMS.
- a method for implementing IMS network reliability includes the following steps:
- the stateful heartbeat server subscribes to the state of the second network entity to learn whether the second network entity is invalid.
- the user terminal subscribes to the first network entity to the state of the second network entity, and the first network entity notifies the user to re-register according to the maintained subscription relationship when the second network entity is notified that the second network entity is invalid.
- the first network entity notifies the user terminal to re-register using the registration status event package that the user terminal has subscribed to.
- the user identifier and the network storing the data related to the user registration The network entity is associated with the specified network entity, and the first network entity obtains the registered users related to the failed second network entity from the specified network entity, and issues a notification to the users for re-registration.
- the first network entity is a device management server in the OMA device management architecture, and the device management server sends an extended notification message to instruct the user terminal to re-initiate registration.
- the second network entity includes a Proxy-Call Session Control Function (P-CSCF) entity; the first network entity is an S-CSCF entity, and the identity of the P-CSCF entity and related users are included in the user registration process.
- the identity association is saved on the S-CSCF entity; the S-CSCF entity notifies the relevant user to re-register when the P-CSCF entity fails.
- P-CSCF Proxy-Call Session Control Function
- the second network entity includes a Proxy-Call Session Control Function (P-CSCF) entity; the first network entity is another P-CSCF entity; in the user registration process, the identity of the P-CSCF entity and related The user identity is associated and saved on the another P-CSCF entity.
- P-CSCF Proxy-Call Session Control Function
- the other: -CSCF entity notifies the affected user to re-register.
- the second network entity includes an S-CSCF entity, and when the S-CSCF entity fails, the first network entity notifies the user of the re-registration by the P-CSCF entity serving the user when the user registers.
- the first network entity is another S-CSCF entity.
- the user identifier, the identifier information of the P-CSCF entity serving the user, and the identifier of the S-CSCF entity are associated with and saved in the On the Home Subscriber Server (HSS), the another S-CSCF entity learns the related user and the P-CSCF entity that provides the service for the user from the HSS according to the identification information of the S-CSCF entity.
- HSS Home Subscriber Server
- the second network entity includes an HSS; the first network entity is an S-CSCF entity, and the S-CSCF entity learns that the P-CSCF entity that provides services for the user when the user is registered after the HSS is invalid is notified to register with the HSS. User re-registered.
- the second network entity includes an application server (AS).
- AS application server
- the P-CSCF entity that provides services for the user when the user registers is notified by the network entity to notify the user to re-register.
- the first network entity is an S-CSCF entity.
- the pre-acquisition standby P-CSCF is utilized.
- the address of the entity verifies the source address of the notification message to determine if the notification message is authentic and initiates a re-registration to the network after determining that the notification message is trusted.
- the terminal device After receiving the re-registration notification message, the terminal device carries the authentication challenge in the response message, and the network entity that sends the notification message generates a corresponding authentication response according to the authentication challenge and sends the corresponding authentication response to the terminal device, where the terminal device authenticates the authentication.
- the response is verified to determine if the notification message is authentic and initiates a re-registration to the network after determining that the notification message is trusted.
- a method for obtaining a state change of a network entity in an IMS network comprising the steps of: subscribing a heartbeat server in an IMS network with a state change of a monitored network entity, wherein the heartbeat server sends a SIP message to the network entity and receives a corresponding response Message to detect its status;
- the heartbeat server maintains a subscription relationship and notifies the subscriber when it detects a change in the state of the monitored network entity.
- the heartbeat server and the detected network entity respectively count the SIP messages sent and received, and the detected network entity carries the counting result in the response message sent to the heartbeat server, and the heartbeat server performs the counting result on both ends.
- a comparison determines if the state of the detected network entity has changed.
- the present invention can timely notify the user to re-register through the standby network entity, thereby shortening the interruption time of the user service and improving the reliability of the network. .
- FIG. 1A is a schematic diagram of a location query server through a DNS query in the prior art
- FIG. 1B is a flowchart of realizing the reliability of an IMS network by using user registration/re-registration in the prior art
- FIG. 2 is a schematic diagram of simultaneous failure of a network entity in the same place
- FIG. 3A and FIG. 3B are flowcharts respectively for notifying a user terminal to re-register when an S-CSCF entity and a P-CSCF entity fail in the present invention
- 4 is a schematic diagram of a network device involved in user registration
- FIG. 5 is a process flow diagram of a subscription status event and a corresponding event notification of a prior art user terminal
- FIG. 6A and FIG. 6B are flowcharts of the terminal receiving the re-registration notification for authentication
- FIGS. 7A and 7B are flowcharts of detecting a state of a network device by using a heartbeat server
- Figure 8 is a flow chart of the state of the subscribed device to the heartbeat server. detailed description
- the first network entity in the IMS network knows that the user registration related data is saved. Whether the second network entity fails; and when the first network entity learns that the second network entity is invalid, notifying the registered user re-registration related to the failed second network entity.
- failure refers to a situation in which a network device is restarted after a failure, or the network device is completely damaged due to uncontrollable factors.
- the second network entity that stores user registration related data in the network includes: a Proxy-Call Session Control Function (P-CSCF) entity, a Service-Call Session Control Function (S-CSCF) entity, a Home Subscriber Server (HSS), and an application server (
- P-CSCF Proxy-Call Session Control Function
- S-CSCF Service-Call Session Control Function
- HSS Home Subscriber Server
- the logical function of the first network entity that informs the user to re-register may be implemented by an existing entity of the IMS network associated with each second network entity, or of course, by a dedicated network entity.
- the present invention uses a network device identifier associated with the registered user on a specified network entity of the IMS network during the user registration process.
- the first network entity can obtain the specified network entity from the designated network entity. Get the information needed to notify the user to re-register.
- the identifier of the network entity may be the name of the network entity or the address of the network entity.
- Service-Call Session Control Function S-CSCF
- the entity downloads the user subscription number from the HSS during the user terminal registration process, and saves information about the user registration status such as Contact and PATH.
- the S-CSCF entity is invalid.
- the user registered in the S-CSCF entity will not be able to make the call to initiate the call.
- the user can actively try to re-register.
- the I-CSCF entity in the registration selects the S-CSCF entity with normal status. After the registration is successful, the registration continues. business. However, if the user is in the standby state, the user loses all incoming call services, and only after the re-registration timer expires, the re-registration is initiated and registered to the normal S-CSCF entity before being restored.
- the first network entity sends a notification to the affected user to request the user terminal to re-register to continue the user service.
- the S-CSCF associates and stores the user identifier and the S-CSCF entity and the corresponding P-CSCF entity identification information in the designated network entity;
- the first network entity of the CSCF entity detects that the S-CSCF entity is invalid, and obtains the affected user identifier and the corresponding P-CSCF entity identifier from the specified network entity according to the identifier information of the failed S-CSCF entity, the first network.
- the entity notifies the affected user to re-register through the corresponding P-CSCF entity.
- the P-CSCF entity fails, and the user registration related data (such as SA) saved by the P-CSCF entity is lost, and the user terminal cannot initiate and answer the call.
- the user can re-initiate the registration through another P-CSCF entity to continue the calling service. If the user is in the standby state, only when the re-registration timer expires, the terminal finds that the P-CSCF entity has failed, and the user has lost all incoming calls.
- the present invention uses the first network entity to send a notification to the affected user, requesting the user to re-register, so that the user continues to obtain the service.
- the user terminal is registered by the P-CSCF entity in the S-CSCF entity, and the first network entity of the P-CSCF entity may be the corresponding S-CSCF entity.
- the user terminal is registered by the P-CSCF entity in the S-CSCF entity, and the P-CSCF entity carries its own address in the Path header field to the S-CSCF entity.
- the P-CSCF entity also carries the relevant P-CSCF entity identification information
- S The CSCF entity stores the address of the P-CSCF entity and the address of the associated P-CSCF entity in the user registration data.
- the affected user is learned from the user registration status data according to the identity of the failed P-CSCF entity, and the notification is sent to the user terminal by the relevant P-CSCF entity saved in the user registration status data.
- the present invention may also actively notify the user by using the first network entity device in the same roaming domain as the failed P-CSCF entity, and the user re-registers to continue the service.
- the first network entity is another P-CSCF entity that is in the same IMS roaming domain as the failed P-CSCF entity.
- the user receives the notification and re-registers to continue to obtain the service.
- the user's home domain and roaming domain usually do not belong to the same carrier. In this way, roaming domain network device failures are resolved by roaming domain operators, thereby avoiding coupling between different operators.
- the HSS also stores user registration related data, usually records the user registration status, and records the S-CSCF entity assigned to the user.
- the HSS is faulty and subsequent user services are affected. For example, under normal circumstances, the user makes a called, the called home domain I-CSCF entity queries the HSS to decide to route the call request to the corresponding S-CSCF entity, the HSS fails, and the I-CSCF entity cannot know which S is currently registered by the called party. - The CSCF entity eventually causes the user to be unable to answer incoming calls.
- the present invention may also employ a method by which the first network entity notifies the affected user to re-register that the user continues to receive the service.
- the first network device may be an S-CSCF entity.
- the S-CSCF entity determines the HSS corresponding to the registered user by interacting with the SLF through the Dx interface, and records the corresponding HSS address of the registered user in the user registration status data. .
- all S-CSCF entities in the home domain send notifications to the user terminals affected by the HSS failure according to the corresponding relationship between the registered users and HSSs saved by the HSS.
- the HSS fails, and the S-CSCF entity sends a notification to all registered users.
- some application servers AS that provide services for users save user registration related data.
- an AS provides an online presence service for the user.
- the S-CSCF entity initiates a third-party registration with the AS according to the initial filtering rule of the user, so that the AS knows that the user is registered and reachable.
- the first network entity may be an S-CSCF entity.
- the S-CSCF entity checks the registered user data saved by itself, sends a notification to all user terminals involved in the failed AS, and the user terminal re-registers after receiving the notification. During the re-registration process, the S-CSCF entity chooses to send a third party registration to another AS that can provide the same service.
- the first network entity sends a notification to the user terminal in a sequence.
- the terminal still does not know. You will receive a corresponding re-registration notice, although it will cause the terminal to register again, but this will not cause an error.
- the above methods for processing various types of network devices that have user registration related data may be used separately or in combination with each other.
- the method of the present invention is used to notify the user to re-register only for the failure of the S-CSCF entity, and other network reliability implementation methods are adopted for the P-CSCF entity failure.
- the foregoing methods for failure of various types of network devices can also be applied to the same IMS network.
- the first network entity when the AS fails, the first network entity notifies the relevant user, and when the S-CSCF entity fails, the first network entity also notifies the relevant user.
- the first network entities S-CSCF1 and S-CSCF2, which are the S-CSCF3 acquire the users affected by the S-CSCF3 failure from the HSS to these users.
- the terminal sends a notification.
- the first network entities of AS3, S-CSCF1, S-CSCF2 and S-CSCF3 each of the users served by them should check the services provided by AS3 and send notifications to the corresponding user terminals.
- S-CSCF3 is also faulty, it cannot be sent to the relevant user as the first network entity of AS3, but since S-CSCF1 and S-CSCF2 are the first network entity of S-CSCF3, they have been registered on the S-CSCF3. All user terminals have sent notifications, and users affected by AS3 failures are naturally included.
- Step 1 - 2 The user terminal (UE) sends a registration request REGISTER to the home domain through the P-CSCF1,
- Steps 3 - 5 After the I-CSCF interacts with the HSS, the REGISTER request is forwarded to the corresponding S-CSCF1 o
- Steps 6 - 7 S-CSCF1 authenticates the registration request and accepts user registration.
- S-CSCF1 saves the P-CSCF1 address in the PATH header field to the user's registration status data.
- the S-CSCF1 interacts with the HSS through SAR/SAA (Server Allocation Request/Server Allocation Response), notifying the HSS of the S-CSCF1 name serving the registered user and downloading the subscriber subscription data.
- the SAR also carries the P-CSCF1 address serving the corresponding registered user, and the HSS stores the corresponding association between the registered user and the S-CSCF1 and the P-CSCF1.
- Step 8-10 The S-CSCF1 returns a 200 response to the user terminal indicating that the registration is successful.
- Step 50 The S-CSCF1 entity is faulty.
- Steps 51 - 52 In the present invention, after the S-CSCF2 learns that the S-CSCF1 is faulty, the S-CSCF2 sends an SRR (Service Restore Request) request to the HSS, which includes the S-CSCF1 identifier. In the SRA (Service Restore Answer) response, the HSS returns information about the user registered with the S-CSCF1, including the user ID and the corresponding P-CSCF1 address. After the user related information is transmitted to the S-CSCF2 through the SRA, the HSS deletes the registration status information related to the user. SRR and SRA are the new processes of the invention.
- SRR Service Restore Request
- SRA Service Restore Answer
- Steps 53-56 The S-CSCF2 notifies the user to re-register by sending a NOTIFY to the user who has registered with the S-CSCF1 by obtaining the relevant information from the HSS.
- the user terminal When the user terminal is authenticated, it needs to pass the corresponding P-CSCF1 entity serving the user terminal.
- the first network entity of the S-CSCF1 is not limited to the S-CSCF2, for example, the first network entity may also have S-CSCF3 and S-CSCF4, etc., and the HSS configuration S-CSCF1 corresponds to the corresponding first network entity. Relationships, only other S-CSCFs belonging to the first network entity of the S-CSCF1 are allowed to interact with the HSS through the SRR/SRA to obtain user-related information registered to the S-CSCF1 entity. When receiving multiple SRR requests from the first network entity, the HSS may register on the S-CSCF1 entity. User information is evenly distributed to each of the first network entities. The first network entity S-CSCF sends a re-registration notification to the user in parallel, speeding up the notification and making the network load more uniform.
- the HSS can also configure the importance level of the user to preferentially transmit user-related data of high importance level to the first network entity S-CSCF, so that these users can obtain priority notification.
- the logical function performed by the first network entity may exist in the S-CSCF, or may exist in other types of network entities, such as an AS.
- the S-CSCF first network entity may also be a network device of the roaming domain, such as a P-CSCF.
- the P-CSCF senses the failure of the S-CSCF, the P-CSCF notifies the relevant affected UE to re-initiate registration.
- the process of actively notifying the user terminal to re-register when the P-CSCF fails is as follows (the authentication for the user registration is omitted):
- Step 1 - 2 The user terminal (UE) sends a registration request to the home domain through the P-CSCF1.
- P-CSCF1 is configured with its associated P-CSCF2 address (when P-CSCF1 fails, P-CSCF2 acts as a channel for the notification request message to reach the user terminal).
- P-CSCF1 adds the PATH header field to include its own address, and also adds a parameter in the PATH header field to carry the P-CSCF2 address.
- Steps 3 - 5 After the I-CSCF interacts with the HSS, forward the REGISTER request to the corresponding S-CSCFL
- Steps 6 - 7 S-CSCF1 authenticates the registration request and accepts user registration.
- S-CSCF1 saves the P-CSCF1 address in the PATH header field in the user registration data, and also stores the P-CSCF2 address associated with P-CSCF1.
- Step 8-10 The S-CSCF1 returns a 200 response to the user terminal indicating that the registration is successful.
- Step 80 The P-CSCF1 entity is faulty.
- Steps 81-82 The S-CSCF1 learns that the P-CSCF1 is faulty, and according to its own user registration data, it is known which users are affected by the P-CSCF1 failure, and the NOTIFY notification request sent by these users is saved by the P-CSCF1.
- the associated P-CSCF2 address reaching the user terminal, to Notify the user terminal to initiate re-registration.
- Steps 83-84 The user terminal returns a 200 response.
- the P-CSCF2 associated with the P-CSCF1 refers to the P-CSCF2 receiving the request message sent by the S-CSCF to the UE originally registered by the P-CSCF1, and may send the message to the corresponding UE. This requires at least the P-CSCF2 entity to be in the same IP address domain as the P-CSCF1 entity.
- the first network entity of the P-CSCF1 is an S-CSCF.
- the first network entity of the P-CSCF1 may also be other network devices.
- the P-CSCF2 may also serve as the first network entity of the P-CSCF1.
- the first network entity discovers users affected by the failure of a certain network device according to different policies.
- the present invention can also employ a uniform method to obtain a user identity that is affected by a network device failure.
- Figure 4 depicts the various types of network devices involved in the user terminal registration process.
- the S-CSCF entity acts as a core device that provides a registration function for the user.
- the S-CSCF entity can obtain the P-CSCF entity and the I-CSCF entity address from the SIP request REGISTER.
- the S-CSCF entity can know the exact HSS address of the corresponding user data through the SLF.
- the S-CSCF entity also performs third-party registration for the user to the relevant service server according to the initial filtering rule of the user, and the S-CSCF entity thus knows the AS1 and AS2 addresses related to the user registration.
- the S-CSCF entity sends a message to a designated network device, which includes the successfully registered user identifier and various types of network device identification information associated with the user registration. For example, in Figure 4, the S-CSCF entity saves this information in the OMC. In this way, any first network entity in the network can obtain the user identifier of the related user affected by the failure of a certain network device through the OMC, and then send a notification to these users.
- the OMC can also be configured with the first network entity corresponding to a second network entity.
- the second network entity may have multiple corresponding first network entities at the same time, and according to the configuration information, determine whether to allow the query request of the first network entity, and determine the data returned in the corresponding query response, for example, with the second network entity. All related user IDs are evenly distributed among different query responses.
- the IMS network considers that the corresponding user needs to be notified when the related network device fails, which is equivalent to the user performing the corresponding "network device failure" event package.
- the default subscription is an implicit subscription relationship.
- the user terminal may send a SUBSCRIBER explicit subscription to the corresponding "network device failure" event packet to the first network entity.
- the first network entity sends a notification to the user terminal based on the existing subscription of the user terminal.
- the first network entity When the user implicitly subscribes to the "network device failure" event package by signing the contract, after the corresponding network device fails, the first network entity notifies by sending a NOTIFY request to the terminal, and the format of the NOTIFY request message body is agreed by the operator and the mobile terminal. .
- the present invention can utilize the existing IMS registration status event notification mechanism to notify the user terminal that the corresponding registration status is invalid, and requires the user to re-initiate the registration to continue to obtain the service.
- the user registration status event notification mechanism applied to the IMS network. For details, refer to IETF RFC3680 (A SIP Event Package for Registrations), 3GPP TS24.229 (related descriptions of user terminal and P-CSCF subscription user registration status events, such as 5.1). .1.3 Initial subscription to the registration-state event package ).
- Steps 310 - 340 After the UE passes the authentication of the S-CSCF, the S-CSCF is successfully registered. .
- Steps 350 - 360 The UE receives a 200 response to the registration request REGISTER, and subscribes to the registration status event package for the user identity that has been successfully registered in the S-CSCF. After receiving the 200 response to the SUBSCRIBER subscription, the UE maintains the corresponding Dialog status and subscription status.
- Steps 370 - 380 Due to certain service requirements, if the operator changes the user subscription data, the S-CSCF sends a NOTIFY request to the UE to notify the terminal to initiate re-registration. The sending of this NOTIFY request is based on the Dialog and subscription created between the user terminal and the S-CSCF in steps 350-360. State.
- the S-CSCF acts as the first network entity of the HSS or AS
- the HSS or AS fails, it needs to send a notification to some users registered in itself, and can use the existing mechanism to subscribe to the established Dialog based on the user registration status event. Subscribe to the status to send.
- the S-CSCF when the S-CSCF accepts the user's subscription to the registration status event, in addition to maintaining the Dialog and related subscription status, the S-CSCF saves the status information on the corresponding first network entity.
- the S-CSCF fails, it is based on the current The mechanism, the corresponding first network entity may send a NOTIFY to notify the terminal that the corresponding registration status is inactive (deactive) based on the saved Dialog and the subscription status, thereby requiring the terminal to initiate re-registration.
- the first network entity notifies the terminal to re-register through the display subscription of the "network device failure" event by the user terminal or the subscription of the registration status event by the terminal, and the UE can match its own maintained Dialog and subscription status after receiving the NOTIFY notification. (by information such as call-id), according to which it is confirmed that the notification is an event that it has subscribed to.
- the notification is trusted because there is no more than a trusted network device.
- the three parties can obtain the relevant status information of the user's subscription to their own registration status event, and can not spoof the corresponding NOTIFY notification.
- an IMS network device fails, only one NOTIFY notification is sent to each user, and then the terminal initiates a new registration and subscription. Therefore, even if the NOTIFY is not protected by a secure channel during transmission to the user terminal, it is meaningless to be intercepted by a third party. .
- the S-CSCF2 entity sends a notification request NOTIFY to the terminal through the P-CSCF1 entity.
- a secure channel is established between the UE and the P-CSCF1, and the NOTIFY received by the secure channel is sent by the trusted home domain device, so the UE can initiate the user re-registration process according to the NOTIFY indication.
- the secure channel established between the UE and the P-CSCF1 entity will be lost.
- S-CSCF1 entity passes the P-CSCF2 entity
- the NOTIFY notification message is sent to the UE. Since there is no secure channel between the UE and the P-CSCF2 entity, the UE cannot confirm whether the sender of the NOTIFY is a trusted network device.
- the user terminal when the user terminal receives the notification of the first network entity, only the UE trusts the sender of NOTIFY to perform the re-registration operation. For example, the user can decide whether to trust to receive the NOTIFY request according to whether the received NOTIFY matches the Dialog maintained by itself and the subscription status. In addition, the user terminal can also authenticate the notification request of the network by the following mechanism.
- the UE can verify the sender S-CSCF in the following two ways:
- the S-CSCF carries the WWW-Authorization header field in the NOTIFY sent to the user.
- the nonce parameter of the WWW-Authorization header field includes AKA-related parameters such as RAND and AUTN.
- the NOTIFY request received by the UE includes the header field, and the identity of the network device can be verified according to information such as RAND, AUTN, and the like.
- the UE performs Digest authentication on the received NOTIFY request.
- Steps 100 - 130 After receiving the NOTIFY request, the user returns to 401 to respond to the sender of the request for Digest identity authentication.
- the UE carries the WWW-Authenticate authentication challenge header field in 401.
- Steps 140 - 150 After receiving the 401, the S-CSCF interacts with the HSS through the MAR/MAA to obtain the HA1 value for the Digest authentication calculation Response parameter. Based on HA1, the S-CSCF calculates the Response parameter and generates the WWW-Authorization header field.
- Steps 160 - 190 The S-CSCF carries the WWW-Authorization header field in the NOTIFY request sent to the terminal UE. After the terminal authentication succeeds, a response is sent back to 200. Indicates that the network has received notification of the event.
- the HA1 value may also be acquired and stored in the S-CSCF by the S-CSCF in the process of acquiring the user subscription information through the SRR/SRA interaction with the HSS before sending the first NOTIFY.
- the user terminal can trust the P-CSCF that sent the notification request by the following method. This applies to the first network entity that sends the notification is the P-CSCF of the roaming domain, and when the user terminal trusts the P-CSCF that sends the request, because the S-CSCF and the P-CSCF trust each other, according to the trust transfer relationship, the user The terminal also trusts the S-CSCF, so the following method can also be applied to the authentication of the NOTIFY sent by the S-CSCF.
- the P-CSCF1 and P-CSCF2 addresses are obtained through the DHCP process. If the IP network between the UE and the P-CSCF has been ensured by the IP layer network that the IP address is not spoofable (as required by Early IMS), the UE receives the notification request from the P-CSCF2, and if the source IP is checked, The P-CSCF2 address obtained by the DHCP process can be considered to be from a trusted network device.
- Each P-CSCF has a corresponding digital certificate (the digital certificate is the P-CSCF public key signed by the issuing authority).
- the P-CSCF acts as a client to initiate a TLS connection to the user terminal.
- Request (ClientHello)
- the P-CSCF provides its own digital certificate to the user terminal, so the terminal can trust the P-CSCF.
- the P-CSCF sends a notification request to the user terminal.
- the OMA standards organization defines the corresponding architecture and protocols for device management Device Management requirements.
- This architecture interacts with the user terminal through the Device Management Server (DM Server) to complete the management of the user terminal, such as the automatic upgrade of the user terminal software by the operator.
- DM Server Device Management Server
- the user terminal cannot passively wait for a connection request from the DM Server, or the terminal cannot open the port to wait for a connection from the DM Server for security reasons.
- the DM Server can send a "notification" notification terminal to the terminal. Proactively establish a connection to the DM Server to complete the corresponding device management service. For details, see OMA-TS-DM-Notification-Vl-2-20050607-C.
- the present invention regardless of which network entity the second network entity is, the logical function of the first network entity Both can be implemented by the DM Server in the OMA device management architecture.
- the DM Server learns that the second network entity is invalid, it learns the user affected by the failure of the second network entity by querying a specific database (for example, querying the OMC with the registered successful user identifier and the associated network entity identifier in FIG. 4), based on the foregoing
- the DM Server sends a notification message to the user terminal, and sends a notification to the corresponding user terminal, requesting the user terminal to re-initiate the registration process to the IMS network.
- the present invention requires an extension of the format of the existing notification message "trigger-messsage", by which the DM Server can instruct the user terminal to re-initiate registration instead of establishing a device management session with the DM Server.
- the first network entity needs to know the failure of the related network device.
- the specific method can manually send an instruction through the network management interface to explicitly indicate that a network device has failed.
- the following IMS network device status detection and status notification methods may also be employed:
- the heartbeat server in the carrier network to detect the status of each IMS network device. Taking the S-CSCF status as an example, as shown in FIG. 7A, the heartbeat server periodically sends a SIP request OPTION to the detected entity S-CSCF. If a response is received, it indicates that the checked entity S-CSCF status is available.
- the heartbeat server will mistakenly think that the skin detection object S -CSCF works fine.
- the heartbeat server needs to be able to detect this state due to the S-CSCF crash restart causing all user data to be lost. Therefore, the present invention keeps a counter for the number of OPTION messages between the heartbeat server and the detected entity, and when the heartbeat server receives the 200% response, the carried OPTION counter is equal to the number of OPTIONs that it has sent to the detected entity, indicating that the detected entity The status is normal. If the heartbeat server sends an OPTION, it does not receive the corresponding 200 response within the specified time, indicating that the detected entity is dead.
- the heartbeat server receives a counter value of "0" carried in the 200 response, so it knows that the detected entity has crashed and restarted. After the heartbeat server finds that the detected entity is restarted, it sends an OPTION request and carries a "counter synchronization indication" to perform both sides counting. Synchronization of the device, as shown in Figure 7B.
- the above detection method can be further applied to state detection monitoring of the internal service processing board level of the IMS network device.
- the heartbeat server saves the S-CSCF1 status and provides a "subscription service" as a Presence Server.
- Other network devices such as the S-CSCF2 entity, can initiate a subscription to the heartbeat server to obtain the status of the S-CSCF1 entity.
- the S-CSCF2 entity subscribes to the heartbeat server for the state of the S-CSCF1 entity.
- the heartbeat server detects that the state of the S-CSCF1 changes from normal to invalid.
- the S-CSCF2 entity sends a notification message.
- the operator may restrict the network devices that are not in the same domain to obtain the relevant status of the network device in some cases. This can be implemented in the heartbeat server setting subscription rules.
- the I-CSCF within the same carrier can also obtain the available status of each S-CSCF in the domain through subscription. In this way, the status information of the S-CSCF can be directly applied to the selection process of the S-CSCF, and it is not necessary to wait for other S-CSCFs after the message retransmission fails.
- the first network entity can automatically discover the state changes of the associated network device.
- the status of the network device detected by the heartbeat server is used by the network maintenance personnel to provide a basis for issuing manual commands. For example, network maintenance personnel may need to confirm whether the cause of the failure is due to a short-term network cable connection problem.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Optical Communication System (AREA)
- Train Traffic Observation, Control, And Security (AREA)
- Electrotherapy Devices (AREA)
- Small-Scale Networks (AREA)
- Signal Processing For Digital Recording And Reproducing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
一种 IMS网络可靠性实现方法
技术领域
本发明涉及通信领域的 IP多媒体子系统(IMS )技术, 尤其涉及 IMS网 络可靠性实现方法。 背景技术
IMS作为固定和移动网络的核心会话控制层, 已成为目前业界讨论的重 点, 在 3GPP以及 TISPAN标准中定义了很多 IMS相关规范, 包括网络架构、 接口、 协议等。 IMS采用 SIP协议作为呼叫控制信令。 在 IMS网络中, IMS 用户的签约数据集中在归属用户服务器( HSS )管理,业务由应用服务器( AS ) 提供, 会话控制由业务 -呼叫会话控制功能 (S-CSCF ) 实体完成, S-CSCF实 体与 AS在网络结构上分离,业务通过 S-CSCF实体触发至 AS处理,多个 AS 间可协同工作。 用户通过当前所在地代理节点代理 -呼叫会话控制功能 ( P-CSCF ) 实体接入 IMS , 会话和业务控制则由其注册地的归属域服务节点 完成, 因此用户在不同接入点能得到同样服务。 IMS 网络实现了业务管理、 会话控制及承载接入的三者分离以及与接入和位置无关的业务提供。
通常每个 IMS网络设备内部有相应的可靠性机制。 例如, 网络设备通常 有多块处理板组成, 处理板间配置为主备用关系, 业务由主用工作板提供, 当主用工作板故障, 相应的备用工作板切换为主用接替故障板的工作, 从而 保证业务提供的连续性。
除了设备内的可靠性机制外, 运营商还关心网络的容灾能力。 IMS 网络 包含以上多种网络实体, 相互间关联性强, 当某一网絡设备故障后, 如何使 该网络设备的故障对整个 IMS 网络影响最小, 对用户的影响最小, 是 "IMS 组网可靠性" 技术领域要解决的问题。
IMS网络基于 SIP协议, RFC3263 ( Locating SIP Servers )结合 SIP网络 可靠性的相关需求, 描述了如何通过域名服务器(DNS )查询定位下一跳 SIP
服务器。 利用该机制, 在 SIP 消息路径中的某一实体失效时, 将消息传送给 其备份实体。 如图 1A所示: 用户通过 DNS解析, 可获得网絡实体 P1和 P2 的地址, 并且知道网络实体 P1的优先级别高于网络实体 P2。 当网络实体 PI 故障而失效时, 用户可向低优先级的备用网络实体 P2发送呼叫请求。
将此机制应用到 IMS系统, 可解决查询 -呼叫会话控制功能(I-CSCF )实 体失效时的消息转发问题, 即当某一 I-CSCF 实体失效时将消息送往另一个 I-CSCF实体。 但 P-CSCF实体或 S-CSCF实体失效时, 无法使用此机制, 因 实体保存用户服务相关的状态, 即使消息能够送往另一个 P-CSCF 实体或 S-CSCF实体, 由于没有相关状态数据, 无法处理收到的消息。
另外, 3GPP TS23228描述了用户注册和重注册的过程。 利用现有用户注 册 /重注册流程, 实现 IMS网络可靠性的方法如图 1B所示: S-CSCF实体向终 端发送的表明注册成功的 200响应中携带了要求终端发起重注册的间隔时长, 在此间隔时长超时前,终端发起重注册。 I-CSCF实体将重注册请求 REGISTER 路由到用户已注册的 S-CSCF实体。当用户已注册的 S-CSCF实体故障 J-CSCF 实体从 HSS获取用户要求的 S-CSCF实体能力集, I-CSCF实体依据能力集信 息,重新选择一个 S-CSCF实体,并将 REGISTER请求路由到新选择的 S-CSCF 实体。 该 S-CSCF实体认为这是新的用户注册请求, 回 401响应对用户鉴权, 鉴权成功后, 回 200响应表明注册成功。
因此,在用户注册或重注册过程中, 当为该用户服务的 S-CSCF实体故障 时, 通过 I-CSCF实体对 S-CSCF实体进行重新选择的流程, 保证了用户要求 的后续服务能够由新的 S-CSCF实体继续提供。
3GPP约定, S-CSCF实体向用户终端(UE )返回的注册成功 200响应中, 终端重注册时长为 600000s (相当于一周:), 当然 S-CSCF 实体也可以根据本 地策略, 决定缩短用户的重注册时长。 但如果用户的重注册时长过短, 将导 致大量重注册消息产生, 占用网絡资源和无线空口资源。 在 RFC3261中, 缺 省重注册时长为 7200s。
用户注册成功到用户发起重注册这段时间内, 若相应的 S-CSCF 实体故 障, 用户将无法得到服务。 例如, 用户在这段时间内将无法接听入呼叫。 为 了减少在 S-CSCF 实体故障情况下用户服务中断的时间而缩短用户的重注册 时长, 会增加网络负荷和占用过多的网络资源。 另外, 以上方案仅适用于 S-CSCF实体故障情况,并不适用于 P-CSCF实体等其他 IMS网络实体故障的 情况。 发明内容
本发明提供一种 IMS网络可靠性的实现方法, 以解决现有 IMS中在用户 注册成功到用户发起重注册期间, 因网络实体失效而可能导致用户服务长时 间中断的问题。
本发明提供以下技术方案:
一种 IMS网络可靠性实现方法, 包括步驟:
由 IMS网络中的第一网络实体获知保存有用户注册相关数据的第二网络 实体是否失效; 以及
在所述第一网络实体获知所述第二网络实体失效时, 通知与失效的第二 网絡实体相关的注册用户重新注册。
通过人工方式检测所述第二网络实体是否失效, 并在确定第二网络实体 失效时通过下发命令通知所述第一网络实体; 或者, 所述第一网络实体通过 向 IMS网络中检测网络设备状态的心跳服务器订阅第二网络实体的状态来获 知该第二网络实体是否失效。
用户终端向第一网络实体订阅第二网络实体的状态, 所述第一网络实体 在获知第二网络实体失效时, 依据维护的订阅关系通知用户重新注册。
第一网络实体利用用户终端已订阅的注册状态事件包通知用户终端重新 注册。
在用户注册过程中, 将该用户标识以及保存有该用户注册相关数据的网
络实体标识关联并保存在指定网络实体上, 所述第一网络实体从该指定的网 络实体获取与失效的第二网络实体相关的注册用户, 针对这些用户下发通知, 要求其重新注册。
所述第一网络实体为 OMA设备管理架构中的设备管理服务器,该设备管 理服务器发送扩展的通知消息指示用户终端重新发起注册。
所述第二网络实体包括代理 -呼叫会话控制功能(P-CSCF )实体; 所述第 一网络实体为 S-CSCF实体, 在用户注册过程中, 将 P-CSCF实体的标识、 和 相关的用户标识关联保存在该 S-CSCF实体上; S-CSCF实体获知 P-CSCF实 体失效时通知相关用户重新注册。
所述第二网络实体包括代理 -呼叫会话控制功能(P-CSCF )实体; 所述第 一网络实体为另一 P-CSCF实体; 在用户注册过程中, 将 P-CSCF实体的标识 和相关的用户标识关联并保存在所述另一 P-CSCF实体上, 当 P-CSCF实体失 效, 由该另一: -CSCF实体通知受影响用户重新注册。
所述第二网络实体包括 S-CSCF实体,该 S-CSCF实体失效时由第一网络 实体通过用户注册时为用户提供服务的 P-CSCF实体通知用户重新注册。所述 第一网络实体为另一 S-CSCF实体, 在用户注册过程中, 所述用户标识、 为用 户提供服务的 P-CSCF实体的标识信息和所述 S-CSCF实体的标识关联并保存 在归属用户服务器(HSS )上, 所述另一 S-CSCF实体根据所述 S-CSCF实体 的标识信息从 HSS上获知所述相关用户和为用户提供服务的 P-CSCF实体。
所述第二网络实体包括 HSS; 所述第一网络实体为 S-CSCF 实体, 该 S-CSCF实体获知 HSS失效后通过用户注册时为用户提供服务的 P-CSCF实体 通知注册到所述 HSS上的用户重新注册。
所述第二网络实体包括应用服务器(AS ), 该 AS失效时, 由笫一网络实 体通过用户注册时为用户提供服务的 P-CSCF实体通知用户重新注册。所述第 一网络实体为 S-CSCF实体。
终端设备接收到进行重注册的通知消息时, 利用预先获取的备用 P-CSCF
实体的地址验证该通知消息的源地址, 以确定该通知消息是否可信, 并在确 定通知消息可信任后向网络发起重新注册。
终端设备在收到重注册的通知消息后, 在响应消息中携带认证挑战, 由 发送所述通知消息的网络实体根据该认证挑战生成相应的认证响应发送到终 端设备, 由终端设备对所述认证响应进行验证以确定该通知消息是否可信, 并在确定通知消息可信任后向网络发起重新注册。
一种获知 IMS网络中网络实体状态变化的方法, 包括如下步骤: 向 IMS网络中的心跳服务器订阅被监测的网络实体的状态变化, 其中该 心跳服务器通过向网络实体发送 SIP 消息和接收相应的响应消息以检测其状 态;
所述心跳服务器维护订阅关系, 并在检测到被监测的网络实体的状态发 生变化时通知订阅者。
心跳服务器和被检测的网络实体分别对发送和接收的 SIP消息进行计数, 并且所述被检测的网络实体在发送给心跳服务器的响应消息中携带计数结 果, 所述心跳服务器对两端的计数结果进行比较以确定被检测的网络实体的 状态是否发生变化。
本发明在 IMS网络中的 P-CSCF实体或者 S-CSCF实体失效时, 能够及 时地通过备用的网络实体通知用户进行重注册, 因而能够极在地缩短用户服 务的中断时间, 提高网络的可靠性。 附图说明
图 1A为现有技术中通过 DNS查询定位服务器的示意图;
图 1B为现有技术中利用用户注册 /重注册实现 IMS网络可靠性的流程图; 图 2为同一地网络实体同时失效的示意图;
图 3A、图 3B分别为本发明中 S-CSCF实体和 P-CSCF实体失效时通知用 户终端重注册的流程图;
图 4为用户注册时所涉及的网络设备的示意图;
图 5 为现有技术用户终端订阅注册状态事件及相应事件通知的处理流程 图;
图 6A、 图 6B为终端收到重新注册通知进行认证的流程图;
图 7A、 7B为利用心跳服务器检测网絡设备状态的流程图;
图 8为向心跳服务器订阅设备状态的流程图。 具体实施方式
为解决现有 IMS中在用户注册成功到用户发起重注册期间, 由于网络实 体失效而造成用户服务可能长时间中断的问题, 本发明由 IMS网络中的第一 网络实体获知保存有用户注册相关数据的第二网络实体是否失效; 并在所述 第一网络实体获知所述第二网络实体失效时, 通知与失效的第二网络实体相 关的注册用户重新注册。
本文所述的 "失效" 是指网络设备故障后重新启动, 或因不可控因素导 致网络设备彻底损坏的情况。
网络中保存用户注册相关数据的第二网络实体包括: 代理-呼叫会话控制 功能(P-CSCF ) 实体、 业务 -呼叫会话控制功能 (S-CSCF ) 实体、 归属用户 服务器(HSS )和应用服务器(AS )等; 通知用户重新注册的第一网络实体 的逻辑功能可以是与各第二网络实体相关联的 IMS网络现有实体实现, 当然 也可是一个专用的网络实体实现。
在针对第二网络实体失效而对受影响用户进行通知的过程中, 第一网络 实体都需要确切知道失效网絡实体对应的受影响用户到底是哪些。 因此, 本 发明采用在用户注册过程中, 在 IMS网络某个指定的网络实体上保存与该注 册用户相关的网络设备标识, 当第二网络实体故障, 第一网络实体可从该指 定的网络实体获取通知用户重新注册所需要的信息。 网络实体的标识可以是 网络实体的名称, 也可以是网络实体的地址。
业务 -呼叫会话控制功能(S-CSCF ) 实体在用户终端注册过程中从 HSS 下载用户签约数椐, 同时保存 Contact、 PATH等用户注册状态相关信息。 S-CSCF实体失效, 在该 S-CSCF实体注册的用户将无法做主叫发起呼叫, 此 时用户可主动尝试重新注册, 注册中 I-CSCF实体选择状态正常的 S-CSCF实 体, 注册成功后继续业务。 但如果用户处于待机状态, 则用户丟失所有入呼 叫业务, 只有当重注册定时器超时后, 发起重注册而注册到状态正常的 S-CSCF实体后才可恢复。
针对 S-CSCF实体失效后用户在一段时间内无法获得服务这种情况,本发 明采用第一网络实体向受影响用户发通知要求用户终端重新注册的方法以继 续用户月良务。 用户终端通过 P-CSCF实体在 S- CSCF实体注册时, S-CSCF将 用户标识以及所述 S-CSCF实体和对应的 P-CSCF实体标识信息关联并保存在 指定网络实体; 当所述 S-CSCF实体的第一网络实体检测到该 S-CSCF实体失 效,根据该失效 S-CSCF实体的标识信息从所述指定的网络实体获取受影响的 用户标识以及相应 P-CSCF实体标识,第一网络实体通过对应的 P-CSCF实体 通知受影响用户进行重注册。
P-CSCF实体失效, P-CSCF实体保存的用户注册相关数据(如 SA )丟失, 用户终端无法发起和接听呼叫。 当用户无法发起呼叫, 用户可通过另一 P-CSCF实体重新发起注册, 继续主叫业务。 如果用户处于待机状态, 只有当 重注册定时器超时,终端才发现 P-CSCF实体失效,此前用户丢失所有入呼叫。
针对 P-CSCF实体失效,本发明采用第一网络实体向受影响用户发送通知 要求用户重新注册的方法使用户继续获得服务。用户终端通过 P-CSCF实体在 S-CSCF实体注册, P- CSCF实体的笫一网络实体可以是对应的 S-CSCF实体。
用户终端通过 P-CSCF实体在 S-CSCF实体注册, P-CSCF实体将自身地 址在 Path头域带给 S-CSCF实体, 此外, 该 P-CSCF实体还携带相关 P-CSCF 实体标识信息, S-CSCF实体在用户注册数据中保存 P-CSCF实体的地址以及 相关 P-CSCF实体的地址。 当所述 S-CSCF实体检测所述 P-CSCF实体失效,
根据失效 P-CSCF实体的标识从自身的用户注册状态数据中获知受影响用户, 并通过用户注册状态数据中保存的相关 P-CSCF实体向用户终端发送通知。
针对 P-CSCF实体的失效,本发明还可以是采用与失效 P-CSCF实体处在 同一漫游域的第一网络实体设备主动通知用户, 用户重新注册以继续服务。 例如, 第一网絡实体是与失效 P-CSCF 实体处于同一 IMS 漫游域的另一个 P-CSCF实体。 当第一网络实体感知 P-CSCF实体失效,通过向用户发送通知, 用户接收通知后重新注册以继续获得服务。 在 IMS网络部署中, 用户归属域 与漫游域通常不属于同一个运营商。 采用这种方式, 漫游域网絡设备故障由 漫游域运营商解决, 从而避免了不同运营商间的耦合。
用户注册过程 HSS也保存用户注册相关数据, 通常记录用户注册状态, 记录为该用户分配的 S-CSCF实体。 HSS故障, 后续用户业务受影响。 例如 正常情况下, 用户做被叫, 被叫归属域 I-CSCF实体向 HSS查询以决定将呼 叫请求路由到相应 S-CSCF实体, HSS故障, I-CSCF实体无法获知被叫当前 注册在哪个 S-CSCF实体, 最终导致用户无法接听入呼叫。
针对 HSS故障, 本发明也可采用由第一网络实体通知受影响用户重新注 册的方法使用户继续获得服务。 第一网络设备可以是 S-CSCF实体, 归属域有 多个 HSS时, S-CSCF实体通过 Dx接口与 SLF交互确定注册用户对应的 HSS 后, 在用户注册状态数据中记录注册用户相应的 HSS地址。 某 HSS故障, 归 属域中的所有 S-CSCF实体依据自身保存的注册用户与 HSS对应关系, 各自 向因 HSS故障受影响的用户终端发送通知。当归属域中仅有一个 HSS,该 HSS 故障, S-CSCF实体向所有已注册用户发送通知。
用户注册过程中,某些为用户提供业务的应用服务器 AS保存用户注册相 关数据。 例如, 某 AS为用户提供在线状态服务, 用户注册时, S-CSCF实体 依据该用户的初始过滤规则, 向该 AS发起第三方注册, AS从而知道用户已 注册且可达。
保存用户注册相关数据的 AS故障后, 无法为用户提供相应业务, 当不提
供相应业务则影响用户正常使用时, 运营商通过第一网络实体向受影响用户 终端发送通知, 用户终端重新注册后获得服务。 第一网络实体可以是 S-CSCF 实体, 当某一个 AS故障, S-CSCF实体检查自身保存的注册用户数据, 向涉 及到故障 AS的所有用户终端发送通知, 用户终端接收通知后重新注册,在重 新注册过程中, S-CSCF实体选择向另一可提供相同业务的 AS发送第三方注 册。
网絡设备故障, 第一网络实体向用户终端发通知有先后顺序, 此过程中, 如果受网絡设备故障影响的用户终端因未正常发起呼叫而已重新注册, 因第 一网络实体不知道, 该终端仍会接到相应的重新注册通知, 虽然会导致终端 再次注册一次, 但这不会造成错误。
以上对各类存有用户注册相关数据的网络设备失效情况下的处理方法, 可以分别单独使用或相互结合使用。 例如, 根据 IMS网络实际组网情况, 仅 针对 S-CSCF实体失效情况下采用本发明的方法来通知用户重新注册,而针对 P-CSCF实体失效采用其他网络可靠性实现方法。
前述针对各类网络设备失效的方法也可应用于同一 IMS网络。 例如, AS 失效时由第一网络实体通知相关用户, S-CSCF实体失效时也由第一网络实体 通知相关用户。 如图 2所示, 当地点 2的 AS3与 S-CSCF3实体同时故障, 作 为 S-CSCF3的第一网络实体 S-CSCF1和 S-CSCF2向 HSS获取受 S-CSCF3故 障影响的用户, 向这些用户终端发送通知。 作为 AS3 的第一网络实体 S-CSCF1 , S-CSCF2和 S-CSCF3 , 应分别检查自己所服务的用户中哪些用到 AS3提供的服务,并向相应的用户终端发送通知。显然由于 S-CSCF3也故障, 不能作为 AS3 的第一网络实体向相关用户下发通知, 但由于 S-CSCF1 与 S-CSCF2作为 S-CSCF3的第一网络实体已向原注册在 S-CSCF3上的所有用户 终端发送了通知, 因 AS3故障而受影响的用户自然也包含在其中。
参阅图 3A所示, S-CSCF失效时通知用户终端重新注册的处理流程如下 (省略对用户的认证过程 ):
步骤 1 - 2 : 用户终端 (UE ) 通过 P-CSCF1 向归属域发注册请求 REGISTER,
步骤 3 - 5: I-CSCF与 HSS 交互后, 将 REGISTER请求转发给相应的 S-CSCFl o
步骤 6 - 7: S-CSCF1认证该注册请求后接受用户注册。 S-CSCF1将 PATH 头域中 P-CSCF1 地址保存在用户的注册状态数据。 依 3GPP 协议流程, S-CSCF1通过 SAR/SAA (服务器分配请求 /服务器分配响应) 与 HSS交互, 通知 HSS为注册用户服务的 S-CSCF1名字以及下载用户签约数据。 本发明, SAR还携带为相应注册用户服务的 P-CSCF1 地址, HSS保存注册用户与 S-CSCFl , P-CSCF1三者间的对应关联。
步骤 8-10: S-CSCF1向用户终端返回 200响应表明注册成功。
步骤 50: S-CSCF1实体故障。
步驟 51 - 52: 在本发明, S-CSCF2获知 S-CSCF1故障后, S-CSCF2向 HSS发送 SRR ( Service Restore Request )请求,其中包含 S-CSCFl标识。 HSS 在 SRA ( Service Restore Answer )响应中, 返回已在 S-CSCF1注册的用户的 相关信息, 包括用户标识及相应 P-CSCF1地址。 当用户相关信息通过 SRA传 给 S-CSCF2后, HSS删除与该用户相关的注册状态信息。 SRR与 SRA为本 发明新增流程。
步驟 53― 56: S-CSCF2通过由 HSS获得相关信息, 向已在 S-CSCF1注 册的用户发送 NOTIFY通知用户重新注册。 向用户终端发通^ r时, 需要通过 相应的为该用户终端服务的 P-CSCF1实体。
以上流程, S-CSCF1的第一网络实体不限于 S-CSCF2—个, 例如, 第一 网络实体还可以有 S-CSCF3和 S-CSCF4等, HSS配置 S-CSCF1与相应第一 网络实体间对应关系, 只有属于 S-CSCF1第一网络实体的其他 S-CSCF才允 许通过 SRR/SRA与 HSS交互获取注册到 S-CSCF1实体上的用户相关信息。 当收到多个第一网络实体的 SRR请求时, HSS可以将注册在 S-CSCF1实体上
的用户信息均匀的分配给各个第一网絡实体。 由这些第一网絡实体 S-CSCF 并行向用户发出重新注册通知, 加快通知速度, 使网络负荷更均匀。
HSS还可以配置用户的重要性级别, 向第一网络实体 S-CSCF优先传送 重要性级别高的用户相关数据, 以便这些用户能够获得优先通知。
在上述流程中, 第一网络实体完成的逻辑功能可以存在于 S-CSCF, 也可 以存在于其他类型的网络实体, 例如 AS等。
另外, S-CSCF第一网络实体还可以为漫游域的网络设备, 例如 P-CSCF。 由 P-CSCF感知 S-CSCF的故障后, P- CSCF通知相关受影响的 UE重新发起 注册。
参阅图 3B所示, P-CSCF失效时主动通知用户终端重新注册的处理 ϋ程 如下 (省略了对用户注册的认证):
步驟 1 - 2 : 用户终端 (UE ) 通过 P-CSCF1 向归属域发注册请求
REGISTER 本发明, P-CSCF1配置与其相关的 P-CSCF2地址(当 P-CSCF1 故障, P-CSCF2作为通知请求消息到达用户终端的通道)。 P-CSCF1增加 PATH 头域将自身地址包含在其中, 同时也在 PATH 头域中新增一个参数, 用于携 带 P-CSCF2地址。
步骤 3 - 5: I-CSCF与 HSS 交互后, 将 REGISTER请求转发给相应的 S-CSCFL
步骤 6 - 7: S-CSCF1认证该注册请求后接受用户注册。 S-CSCF1将 PATH 头域中的 P-CSCF1地址保存在用户注册数据中, 同时也保存与 P-CSCF1相关 联的 P-CSCF2地址。
步骤 8-10: S-CSCF1向用户终端返回 200响应表明注册成功。
步骤 80: P-CSCF1实体故障。
步骤 81-82: S-CSCF1获知 P-CSCF1故障, 依据自身的用户注册数据, 获知哪些用户因 P-CSCF1故障而受到影响, 对这些用户发送的 NOTIFY通知 请求, 是通过保存的与 P-CSCF1相关联的 P-CSCF2地址, 到达用户终端, 以
通知用户终端发起重新注册。
步骤 83-84: 用户终端返回 200响应。
与 P-CSCF1相关联的 P-CSCF2,是指 P-CSCF2收到由 S-CSCF发来的目 的地为原通过 P-CSCF1注册的 UE的请求消息, 可以将该消息发往相应 UE。 这至少要求 P-CSCF2实体与 P-CSCF1实体处于同一 IP地址域。
以上流程, P-CSCF1的第一网络实体为 S-CSCF。 本发明中, P-CSCF1的 第一网络实体还可以是其他网络设备, 例如, P-CSCF2也可以作为 P-CSCF1 的第一网络实体。用户终端通过 P- CSCF1注册成功后,Ρ-CSCFl告知 P-CSCF2 通过 P-CSCF1 已注册成功的用户标识, 当 P-CSCF1故障, P-CSCF2可向因 P-CSCF1故障而受影响的用户终端发送通知请求。
针对 HSS故障或 AS故障而由第一网絡实体通知用户终端重新注册的具 体流程与上述流程在原理上是相同的, 不再赘述。
以上所描述的针对各类网络设备失效的通知方法, 第一网络实体依据不 同的策略发现受某网络设备失效影响的用户。 本发明也可采用统一的方法来 获得因某网络设备失效而影响的用户标识。 图 4描述了用户终端注册过程所 涉及的各类网络设备。 在注册流程中, S-CSCF实体作为为用户提供注册功能 的核心设备, 在接收消息 5时, 可从 SIP请求 REGISTER获得 P-CSCF实体 及 I-CSCF实体地址。存在多个 HSS时, S-CSCF实体通过 SLF可知道确切的 保存相应用户数据的 HSS地址。 同时, S-CSCF实体也依据用户的初始过滤 规则, 为用户向相关的业务服务器进行第三方注册, S-CSCF实体因此知道与 用户注册相关的 AS1与 AS2地址。 S-CSCF实体在完成与用户注册相关所有 操作后, 向一个指定网络设备发送消息, 其中包含已注册成功的用户标识以 及与该用户注册相关联的各类网络设备标识信息。 例如, 图 4中, S-CSCF实 体将此信息保存在操作维护系统 OMC。 这样网络任何第一网络实体都可通过 OMC获得因某网络设备故障受影响的相关用户的用户标识, 进而向这些用户 发送通知。 OMC中还可配置某第二网络实体对应的第一网络实体有哪些(一
个笫二网络实体可以同时有多个相应第一网絡实体), 依据此配置信息决定是 否允许第一网络实体的查询请求, 以及决定在相应查询响应中返回的数据, 例如将与第二网络实体相关的所有用户标识均匀分配在不同的查询响应中。
以上所描述的针对各类网络设备失效的通知方法中, 依据用户开户的签 约信息, IMS 网络认为当相关网络设备故障时需要通知相应用户, 相当于用 户对相应 "网络设备故障" 事件包进行了缺省的订阅, 是一种隐含的订阅关 系。 或者, 用户终端可以在注册成功后, 向第一网络实体发送 SUBSCRIBER 显式订阅相应 "网絡设备故障" 事件包。 当相关网络设备故障, 第一网络实 体基于用户终端的已有订阅向用户终端发通知。
当用户是通过签约而隐式订阅 "网络设备故障" 事件包, 相应网络设备 故障后, 第一网络实体通过向终端发送 NOTIFY请求来通知, 该 NOTIFY请 求消息体的格式由运营商与手机终端商定。
当第一网絡实体是在用户归属域向用户终端发通知, 本发明可以利用现 有 IMS注册状态事件通知机制, 通知用户终端相应注册状态失效, 要求用户 重新发起注册以继续获得服务。 IMS 网络已应用的用户注册状态事件通知机 制, 详细内容可参考 IETF RFC3680 ( A SIP Event Package for Registrations ), 3GPP TS24.229 (对用户终端及 P-CSCF订阅用户注册状态事件的相关描述, 如 5.1.1.3 Initial subscription to the registration-state event package )。 如图 5所 示,该机制的主要处理流程如下(省略了 P-CSCF、 I-CSCF、 HSS等网络实体): 步骤 310 - 340: UE通过 S-CSCF的认证后, 在 S-CSCF注册成功。
步驟 350 - 360: UE收到对注册请求 REGISTER的 200响应, 针对已在 S-CSCF 注册成功的用户标识订阅注册状态事件包。 UE 收到对订阅 SUBSCRIBER的 200响应后, 维护相应的 Dialog状态以及订阅状态。
步骤 370 - 380: 因某些业务需求, 如运营商更改了用户签约数据, S-CSCF向 UE发 NOTIFY请求, 通知终端发起重新注册。此 NOTIFY请求的 发送是基于步骤 350 - 360中用户终端与 S-CSCF之间建立的 Dialog及订阅状
态。
当 S-CSCF作为 HSS或 AS的第一网络实体, 当 HSS或 AS故障, 需要 向注册在自身的某些用户发送通知, 可利用现有机制, 基于通过用户注册状 态事件订阅已建立的 Dialog及订阅状态来发送。
进一步, 当 S-CSCF 接受用户对注册状态事件的订阅后, 除自身维护 Dialog及相关订阅状态, 还将这些状态信息保存在相应第一网络实体上, 当 该 S-CSCF故障, 基于目前已有的机制, 相应第一网络实体可基于已保存的 Dialog 以及订阅状态, 发送 NOTIFY 通知终端相应的注册状态为非激活 ( deactive ), 从而要求终端发起重注册。
利用现有的注册状态事件通知机制, 不需要为实现网络设备通知用户重 新注册而扩展现有协议。 针对 S-CSCF本身故障, 仅需要 S-CSCF动态备份与 用户订阅状态相关的少量信息到相应的第一网络实体上。
如前述第一网络实体通过用户终端对 "网络设备故障" 事件的显示订阅 或通过终端对注册状态事件的订阅来通知终端重新注册, UE收到 NOTIFY通 知后可匹配其自身维护的 Dialog以及订阅状态(通过 call-id等信息),据此确 认该通知是自己曾订阅的事件,当 UE先前通过安全通道发起注册状态事件订 阅, 则该通知是可信的, 因为除可信任网络设备, 没有第三方能获取用户对 其自身注册状态事件订阅的相关状态信息, 也无法仿冒发出相应的 NOTIFY 通知。 某个 IMS网络设备故障, 对每个用户仅发送一次 NOTIFY通知, 之后 终端发起新的注册和订阅, 因此即使该 NOTIFY在向用户终端传送过程中没 有受安全通道保护, 被第三方截获也没有意义。
在上述过程中, 当 S-CSCF1实体故障, S-CSCF2实体通过 P-CSCF1实体 向终端发送通知请求 NOTIFY。 UE与 P-CSCF1间已建立安全通道, ΌΕ由安 全通道接收的 NOTIFY 是可信任的归属域设备发来的, 因此 UE 可依据 NOTIFY指示发起用户重新注册过程。 而对于 P-CSCF1实体故障的情况, UE 与 P-CSCF1实体间建立的安全通道将丟失。 S-CSCF1实体通过 P-CSCF2实体
向 UE发送 NOTIFY通知信息, 由于 UE与 P-CSCF2实体间没有安全通道, UE无法确认该 NOTIFY的发送者是否是可信任的网络设备。
在用户终端与网络设备间没有安全通道的情况下, 当用户终端接收到第 一网络实体的通知, 只有 UE信任 NOTIFY的发送者, 才进行重新注册操作。 如前述用户可根据接收到的 NOTIFY是否与自身维护的 Dialog以及订阅状态 相匹配来决定是否信任收到 NOTIFY请求。 此外, 用户终端还可以通过如下 机制来认证网络的通知请求。
当发送通知的设备为 S-CSCF 时, UE 可采用以下两种方式对发送者 S-CSCF进行验证:
1、 利用 AKA认证中的 AUTS参数认证网络设备真实性
如图 6A所示, S-CSCF在发向用户的 NOTIFY中携带 WWW-Authorization 头域,依据保存的用户養权信息, WWW-Authorization头域的 nonce参数中包 含 RAND, AUTN等 AKA相关参数。 UE收到的 NOTIFY请求中包含该头域, 可依据 RAND, AUTN等信息, 验证网络设备的身份是否可信任。
2、 UE对收到的 NOTIFY请求进行 Digest认证
如图 6B所示, 其主要流程如下:
步骤 100 - 130: 用户接收 NOTIFY请求后, 回 401响应对该请求的发送 者进行 Digest身份认证。 UE在 401中携带 WWW-Authenticate认证挑战头域。
步骤 140 - 150: S-CSCF收到 401后, 通过 MAR/MAA与 HSS交互, 获 得用于 Digest认证计算 Response参数的 HA1值。 S-CSCF依据 HA1 , 计算出 Response参数, 生成 WWW-Authorization头域。
步骤 160 - 190: S-CSCF 在发往终端 UE 的通知 NOTIFY请求中携带 WWW-Authorization头域。 终端认证成功后, 回送 200响应。 表明接受了网 络的事件通知。
HA1值也可以在发送第一个 NOTIFY之前, 由 S-CSCF在通过 SRR/SRA 与 HSS交互获取用户签约信息的过程中向 HSS获取并保存在 S-CSCF。
另外, 用户终端可以通过如下方法来信任发送通知请求的 P-CSCF。 这适 用于发出通知的第一网络实体为漫游域的 P-CSCF, 并且, 当用户终端信任发 送请求的 P-CSCF, 由于 S-CSCF与 P-CSCF间相互信任, 依据信任的传递关 系,用户终端也是信任 S-CSCF的,因此如下方法也同样可以应用在对 S-CSCF 发送的 NOTIFY进行认证的情况。
3、 利用 IP地址验证网络设备 P-CSCF的真实性
对于 IP地址不可仿冒的组网, UE获取 IP地址时, 通过 DHCP过程同时 获得 P-CSCF1和 P-CSCF2地址。 如果 UE与 P-CSCF间的 IP网络, 已由 IP 层组网保证了 IP地址不可仿冒(如 Early IMS所要求),则 UE接收到 P-CSCF2 来的通知请求,若检查其源 IP正是 DHCP过程所获取的 P-CSCF2地址,则可 认为该 NOTIFY请求来自可信任的网络设备。
4、 通过建立 TLS连接验证网络设备 P-CSCF真实性
在每个 P-CSCF 都有相应数字证书 (数字证书是经发证机构签名的 P-CSCF公有秘钥), P-CSCF向网络发通知前, P-CSCF作为客户端向用户终 端发起 TLS连接请求( ClientHello ), 在后续 P-CSCF与用户终端间为 TLS连 接建立而协商的过程中, P-CSCF向用户终端提供其自身的数字证书, 因而终 端是可以信任 P-CSCF。 TLS连接建立后, P-CSCF向用户终端发送通知请求。
OMA标准组织为了实现设备管理 Device Management需求, 定义了相应 架构和协议。此架构通过 Device Management Server ( DM Server )与用户终端 交互, 完成对用户终端管理, 例如运营商对用户终端软件的自动升级。 通常 用户终端无法被动等待来自 DM Server的连接请求, 或因为安全原因终端不 能打开端口等待来自 DM Server的连接, 当设备管理业务流程由 DM Server 端触发, DM Server可以向终端发送 "notification"通知终端主动向 DM Server 建立 连接 以 完 成相 应 设备管 理 业 务 。 详 细 流程可 参见 OMA-TS-DM-Notification-Vl— 2-20050607-C。
本发明, 无论第二网络实体是哪种网络实体, 第一网络实体的逻辑功能
都可以由此 OMA设备管理架构中的 DM Server来实现。 DM Server获知第二 网絡实体失效时, 通过查询特定数据库(例如查询图 4 中保存有注册成功用 户标识以及相关的网络实体标识的 OMC )得知第二网络实体失效所影响的用 户,基于前述现有 OMA设备管理架构中 DM Server向用户终端发送通知消息 的流程, 向相应的用户终端发送通知, 要求用户终端重新发起向 IMS网络的 注册过程。 本发明要求对现有通知消息 "trigger-messsage" 的格式有所扩展, DM Server可通过该扩展指示用户终端是重新发起注册, 而不是建立与 DM Server之间的设备管理 Session。
从上述可知, 在本发明中, 第一网络实体需要获知相关网络设备的故障。 具体方法, 可以通过网管接口采用人工方式下发指令, 显式的指明某个网络 设备已故障。 另夕卜,也可采用下述的 IMS网络设备状态检测和状态通知方法:
1、 IMS网络设备状态检测
运营商网内有 "心跳服务器", 用于检测各 IMS 网络设备状态。 以检测 S-CSCF状态为例, 如图 7A所示, 心跳服务器向被检测实体 S-CSCF周期性 发送 SIP请求 OPTION, 如收到响应, 表明被检查实体 S-CSCF状态可用。
如果 S-CSCF死机后立即重启,且这段时间没收到心跳服务器的检测消息 OPTION (即 S-CSCF的死机和重启动发生于发送 OPTION周期之间), 则心 跳服务器会误以为皮检测对象 S-CSCF正常工作。由于 S-CSCF死机重启动导 致所有用户数据丟失, 心跳服务器需能检测出这种状态。 因此, 本发明在心 跳服务器与被检测实体间保留对 OPTION消息个数的计数器, 当心跳服务器 收到 200 响应中的携带的 OPTION计数器等于自身曾向被检测实体发送的 OPTION数量, 表明被检测实体状态正常。 如心跳服务器发送 OPTION后, 在规定时间内没有收到相应 200响应, 表明被检测实体死机。
如被检测实体死机重启, 心跳服务器收到 200响应中携带的计数器值为 "0" , 因此知道被检测实体已死机并重启动。 心跳服务器发现被检测实体死 机重启动后, 发送 OPTION请求并携带 "计数器同步指示", 以进行两边计数
器的同步, 如图 7B所示。
上述这种检测方法还可进一步应用到对 IMS网络设备内部业务处理板级 别的状态检测监控。
2、 IMS网络设备状态订阅 /通知机制
心跳服务器保存 S-CSCF1状态,并作为 Presence Server提供"订阅服务", 其他网络设备如 S-CSCF2实体可向心跳服务器发起订阅获得 S-CSCF1实体的 状态。如图 8所示,在步骤 410-420, S-CSCF2实体向心跳服务器订阅 S-CSCF1 实体的状态, 在步骤 430-440, 心跳服务器在检测到 S-CSCF1状态由正常变 化为失效时, 向 S-CSCF2实体发送通知消息。
如订阅者与被订阅者属于不同运营商, 运营商可能在某些情况下限制不 属同一域的网絡设备获取自己网络设备的相关状态, 这可在心跳服务器设定 订阅规则实现。
同一运营商内部的 I-CSCF也可以通过订阅获取域内各个 S-CSCF的可用 状态。 这样 S-CSCF的状态信息可直接应用于 S-CSCF的选择过程, 而不需要 等消息重传失败后, 再尝试其他 S-CSCF。
利用以上状态检测和订阅通知的方法, 第一网络实体可以自动发现相关 网络设备的状态变化。 或者, 由心跳服务器检测到的网络设备状态, 供网络 维护人员参考, 为是否下发人工指令提供依据。 如, 网络维护人员可能需要 确认故障原因是否是由于短时间内的网线连接问题。
本领域的普通技术人员根据上述的说明, 可以得知采用网络中 S-CSCF 实体和 P-CSCF实体之外的其他网络实体作为第一网络实体,其实现过程与上 述同理, 在此不再赞述。
显然 , 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本 发明的精神和范围。 这样, 倘若对本发明的这些修改和变型属于本发明权利 要求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在内。
Claims
1、 一种 IMS网络可靠性实现方法, 其特征在于, 包括如下步骤: 由 IMS网络中的第一网络实体获知保存有用户注册相关数据的第二网络 实体是否失效; 以及
在所述第一网絡实体获知所述第二网络实体失效时, 通知与失效的第二 网络实体相关的已注册用户重新注册。
2、 如权利要求 1所述的方法, 其特征在于, 通过人工方式检测所述第二 网络实体是否失效, 并在确定第二网络实体失效时通过下发命令通知所述第 一网络实体; 或者,
所述第一网絡实体通过向 IMS网络中检测网络设备状态的心跳服务器订 阅第二网络实体的状态来获知该第二网络实体是否失效。
3、 如权利要求 1所述的方法, 其特征在于, 用户终端向第一网络实体订 阅第二网络实体的状态, 所述笫一网络实体在获知第二网络实体失效时, 依 据维护的订阅关系通知用户终端重新注册。
4、 如权利要求 3所述的方法, 其特征在于, 所述订阅关系包括隐含的订 阅关系。
5、 如权利要求 1所述的方法, 其特征在于, 第一网络实体利用用户终端 注册成功后已订阅的注册状态事件包通 p用户终端重新注册。
6、 如权利要求 3或 5所述的方法, 其特征在于, 终端设备收到所述通知 消息后进一步匹配自身维护的订阅状态, 以确定该通知消息是否可信任, 并 在确定通知消息可信任后发起重新注册。
7、 如杈利要求 4或 5所述的方法, 其特征在于, 在用户注册过程中, 将 该用户标识以及保存有该用户注册相关数据的网络实体标识关联并保存在指 定网络实体上, 所述第一网络实体从该指定的网络实体获取与失效的第二网 络实体相关的注册用户, 针对这些用户下发通知, 要求其重新注册。
8、 如权利要求 1所述的方法, 其特征在于, 所述第一网络实体为 OMA
设备管理架构中的设备管理服务器, 该设备管理服务器发送扩展的通知消息 指示用户终端重新发起注册。
9、 如杈利要求 1所述的方法, 其特征在于, 所述第二网络实体包括代理 -呼叫会话控制功能 P-CSCF实体; 所述第一网络实体为 S-CSCF实体, 在用 户注册过程中, 将 P-CSCF 实体的标识、 和相关的用户标识关联保存在该 S-CSCF实体上; S-CSCF实体获知 P-CSCF实体失效时通知相关用户重新注 册。
10、 如权利要求 9所述的方法, 其特征在于, 所述 S-CSCF实体发出的通 知消息经另一 P-CSCF实体传送到用户终端,该另一 P-CSCF实体的标识在用 户注册过程中携带给 S-CSCF实体, 由 S-CSCF实体保存。
' 11、 如权利要求 1 所述的方法, 其特征在于, 所述第二网络实体包括代 理 -呼叫会话控制功能 P-CSCF实体; 所述第一网络实体为另一 P-CSCF实体; 在用户注册过程中,将 P-CSCF实体的标识和相关的用户标识关联并保存在所 述另一 P-CSCF实体上, 当 P-CSCF实体失效, 由该另一 P-CSCF实体通知受 影响用户重新注册。
12、 如权利要求 1 所述的方法, 其特征在于, 所述第二网络实体包括 S-CSCF实体, 该 S-CSCF实体失效时由第一网络实体通过用户注册时为用户 提供服务的 P-CSCF实体通知用户重新注册。
13、 如权利要求 12所述的方法, 其特征在于, 所述第一网络实体为另一 S-CSCF实体,在用户注册过程中,所述用户标识、为用户提供服务的 P-CSCF 实体的标识信息和所述 S-CSCF 实体的标识关联并保存在归属用户服务器 HSS上, 所述另一 S-CSCF实体根据所述 S-CSCF实体的标识信息从 HSS上 获知所述相关用户和为用户提供服务的 P-CSCF实体。
14、如权利要求 1所述的方法,其特征在于,所述第二网络实体包括 HSS; 所述第一网络实体为 S-CSCF实体, 该 S-CSCF实体获知 HSS失效后通过用 户注册时为用户提供月良务的 P-CSCF实体通知注册到所述 HSS上的用户重新 注册。
15、 如权利要求 1 所述的方法, 其特征在于, 所述第二网络实体包括应 用服务器 AS, 该 AS失效时, 由第一网络实体通过用户注册时为用户提供服 务的 P-CSCF实体通知用户重新注册。
16、如权利要求 15所述的方法,其特征在于,所述第一网络实体为 S-CSCF 实体。
17、 如权利要求 1、 2、 3、 4或 5所述的方法, 其特征在于, 终端设备接 收到进行重注册的通知消息时,利用预先获取的 P-CSCF实体的地址验证该通 知消息的源地址, 以确定该通知消息是否可信, 并在确定通知消息可信任后 向网络发起重新注册。
18、 如权利要求 1、 2、 3、 4或 5所述的方法, 其特征在于, 终端设备在 收到重注册的通知消息后, 在响应消息中携带认证挑战, 由发送所述通知消 息的网络实体根据该认证挑战生成相应的认证响应发送到终端设备, 由终端 设备对所述认证响应进行验证以确定该通知消息是否可信, 并在确定通知消 息可信任后向网络发起重新注册。
19、 一种获知 IMS网络中网络实体状态变化的方法, 其特征在于, 包括 如下步骤:
向 IMS网络中的心跳服务器订阅被监测的网络实体的状态变化, 其中该 心跳服务器通过向网絡实体发送 SIP 消息和接收相应的响应消息以检测其状 态;
所述心跳服务器维护订阅关系, 并在检测到被监测的网络实体的状态发 生变化时通知订阅者。
20、 如权利要求 19所述的方法, 其特征在于, 心跳服务器和被检测的网 络实体分别对发送和接收的 SIP 消息进行计数, 并且所述被检测的网络实体 在发送给心跳服务器的响应消息中携带计数结果, 所述心跳服务器对两端的 计数结果进行比较以^
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP06761564A EP1914937B2 (en) | 2005-07-27 | 2006-07-25 | Method and system for realizing ims network reliability |
| DE602006010087T DE602006010087D1 (de) | 2005-07-27 | 2006-07-25 | Verfahren und system zum realisieren von ims-netzwerkzuverlässigkeit |
| AT06761564T ATE447272T1 (de) | 2005-07-27 | 2006-07-25 | Verfahren und system zum realisieren von ims- netzwerkzuverlässigkeit |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200510085400A CN1905472B (zh) | 2005-07-27 | 2005-07-27 | 一种ims网络可靠性实现方法 |
| CN200510085400.8 | 2005-07-27 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2007012270A1 true WO2007012270A1 (en) | 2007-02-01 |
Family
ID=37674609
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2006/001834 Ceased WO2007012270A1 (en) | 2005-07-27 | 2006-07-25 | A method for realizing the ims network reliability |
Country Status (5)
| Country | Link |
|---|---|
| EP (1) | EP1914937B2 (zh) |
| CN (1) | CN1905472B (zh) |
| AT (1) | ATE447272T1 (zh) |
| DE (1) | DE602006010087D1 (zh) |
| WO (1) | WO2007012270A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009006942A1 (en) * | 2007-07-10 | 2009-01-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, apparatuses and computer program for ims recovery upon restart of a s-cscf |
| WO2009039894A1 (en) * | 2007-09-28 | 2009-04-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Failure recovery in an ip multimedia subsystem network |
Families Citing this family (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101383725B (zh) | 2007-09-28 | 2013-03-13 | 华为技术有限公司 | Ip多媒体子系统及容灾恢复方法 |
| CN101217407B (zh) * | 2008-01-04 | 2012-12-19 | 中兴通讯股份有限公司 | 一种代理呼叫会话控制功能故障的处理方法 |
| CN101448319B (zh) * | 2008-04-11 | 2012-02-29 | 中兴通讯股份有限公司 | 一种s-cscf故障恢复处理方法 |
| CN101621501B (zh) * | 2008-07-01 | 2012-06-27 | 中国移动通信集团公司 | 通信系统的用户注册控制方法和会话功能控制实体 |
| CN101621772B (zh) * | 2008-07-02 | 2012-06-06 | 中国移动通信集团公司 | 一种会话控制方法及设备 |
| FR2942361A1 (fr) | 2009-02-16 | 2010-08-20 | France Telecom | Procede et systeme de gestion de la signalisation dans un reseau de telecommunications |
| CN104394146B (zh) | 2009-04-13 | 2017-10-20 | 黑莓有限公司 | 用于确定sip消息的可信度的系统和方法 |
| CN102035805B (zh) * | 2009-09-25 | 2015-05-20 | 中兴通讯股份有限公司 | 用于ims的第三方注册失败处理方法及装置 |
| CN101895915B (zh) * | 2010-07-28 | 2013-01-02 | 中国电信股份有限公司 | 应用服务器旁路方法及服务型呼叫会话控制功能设备 |
| CN102595361B (zh) * | 2011-01-05 | 2017-03-22 | 中兴通讯股份有限公司 | 呼叫处理方法及系统 |
| CN102769835A (zh) * | 2011-05-05 | 2012-11-07 | 阿尔卡特朗讯公司 | 一种处理呼叫的方法和装置 |
| CN103138984B (zh) * | 2011-12-02 | 2016-09-28 | 中兴通讯股份有限公司 | 容灾倒回服务呼叫会话控制功能实体的方法及系统 |
| IN2014DN08788A (zh) | 2012-05-21 | 2015-05-22 | Ericsson Telefon Ab L M | |
| WO2014072407A1 (en) * | 2012-11-09 | 2014-05-15 | Telefonaktiebolaget L M Ericsson (Publ) | Notifying ue of a core network element failure in ims |
| CN104838678B (zh) * | 2012-12-17 | 2021-05-04 | 皇家Kpn公司 | 方法、电信节点和电信终端 |
| US9509811B2 (en) | 2012-12-28 | 2016-11-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatus for resolving data inconsistencies in an IMS network |
| CN107276811B (zh) | 2013-08-07 | 2021-02-09 | 华为技术有限公司 | 一种实现终端被叫业务恢复的方法、相关装置及系统 |
| CN103560913A (zh) * | 2013-10-31 | 2014-02-05 | 华为技术有限公司 | 一种容灾切换方法、设备及系统 |
| CN103763144B (zh) * | 2014-01-26 | 2017-04-05 | 杭州华三通信技术有限公司 | 一种用户续费上线的方法和设备 |
| CN104284360B (zh) * | 2014-10-21 | 2018-05-25 | 中国联合网络通信集团有限公司 | P-cscf故障处理方法和系统 |
| CN106412855B (zh) * | 2016-06-30 | 2020-11-27 | 北京小米移动软件有限公司 | 信息提醒、传输方法及装置 |
| US10383164B2 (en) * | 2016-10-06 | 2019-08-13 | T-Mobile Usa, Inc. | Network terminal having configurable retry or changeover |
| CN108234184B (zh) * | 2016-12-22 | 2021-01-15 | 上海诺基亚贝尔股份有限公司 | 用于管理用户信息的方法和设备 |
| WO2019122494A1 (en) * | 2017-12-20 | 2019-06-27 | Nokia Technologies Oy | Method and apparatus for disaster resilience in mobile networks |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003061236A1 (en) | 2002-01-21 | 2003-07-24 | Nokia Corporation | Method and system for changing a subscription |
| WO2003084257A1 (en) | 2002-03-28 | 2003-10-09 | Nokia Corporation | Method and system for re-authentication in ip multimedia core network system (ims) |
| WO2004084510A1 (en) * | 2003-03-17 | 2004-09-30 | Nokia Corporation | Method, system and network device for routing a message to a temporarily unavailable network user |
| WO2004089023A1 (en) * | 2003-03-31 | 2004-10-14 | Nokia Corporation | Method and system for deactivating a service account |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100563999B1 (ko) * | 2001-05-09 | 2006-03-29 | 노키아 코포레이션 | 사용자에게 등록을 표시하기 위한 방법 |
| GB0111290D0 (en) * | 2001-05-09 | 2001-06-27 | Nokia Corp | Registration in a communication system |
| CN1423197A (zh) * | 2002-12-16 | 2003-06-11 | 华中科技大学 | 基于多tcp连接映像的高可用系统 |
-
2005
- 2005-07-27 CN CN200510085400A patent/CN1905472B/zh not_active Expired - Fee Related
-
2006
- 2006-07-25 DE DE602006010087T patent/DE602006010087D1/de active Active
- 2006-07-25 AT AT06761564T patent/ATE447272T1/de not_active IP Right Cessation
- 2006-07-25 WO PCT/CN2006/001834 patent/WO2007012270A1/zh not_active Ceased
- 2006-07-25 EP EP06761564A patent/EP1914937B2/en not_active Not-in-force
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003061236A1 (en) | 2002-01-21 | 2003-07-24 | Nokia Corporation | Method and system for changing a subscription |
| WO2003084257A1 (en) | 2002-03-28 | 2003-10-09 | Nokia Corporation | Method and system for re-authentication in ip multimedia core network system (ims) |
| WO2004084510A1 (en) * | 2003-03-17 | 2004-09-30 | Nokia Corporation | Method, system and network device for routing a message to a temporarily unavailable network user |
| WO2004089023A1 (en) * | 2003-03-31 | 2004-10-14 | Nokia Corporation | Method and system for deactivating a service account |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009006942A1 (en) * | 2007-07-10 | 2009-01-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, apparatuses and computer program for ims recovery upon restart of a s-cscf |
| WO2009039894A1 (en) * | 2007-09-28 | 2009-04-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Failure recovery in an ip multimedia subsystem network |
| JP2010541349A (ja) * | 2007-09-28 | 2010-12-24 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Ipマルチメディア・サブシステム・ネットワークにおける障害復旧 |
Also Published As
| Publication number | Publication date |
|---|---|
| ATE447272T1 (de) | 2009-11-15 |
| CN1905472B (zh) | 2010-05-05 |
| DE602006010087D1 (de) | 2009-12-10 |
| EP1914937B1 (en) | 2009-10-28 |
| EP1914937A4 (en) | 2008-12-10 |
| EP1914937B2 (en) | 2013-01-23 |
| CN1905472A (zh) | 2007-01-31 |
| EP1914937A1 (en) | 2008-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1905472B (zh) | 一种ims网络可靠性实现方法 | |
| EP1758323B1 (en) | A method for terminal identifying capability interaction route control while ims and cs are coinstantaneous | |
| RU2386219C2 (ru) | Способ обработки отказов в представлении обслуживания | |
| KR100912628B1 (ko) | 단말 장치의 서스펜드된 네트워크 상태의 종결을 처리하는방법, 장치 및 컴퓨터 프로그램 생성물 | |
| CN100379316C (zh) | 传统终端用户接入ims域的实现方法及系统 | |
| CN101719912B (zh) | 数据处理方法及数据处理系统以及相关设备 | |
| CN101035036B (zh) | 合法监听系统和方法 | |
| WO2009094852A1 (en) | Proxy call session control function malfunction processing method | |
| JP2006517064A (ja) | 一時的に利用不可能なネットワークユーザーへのメッセージのルーティング方法、システム、およびネットワーク装置 | |
| CN102035798B (zh) | 一种实现容灾的业务处理方法、系统及装置 | |
| WO2022083552A1 (zh) | 呼叫处理方法、装置及存储介质 | |
| JP2006517064A5 (zh) | ||
| WO2010075689A1 (zh) | 网络容灾方法、终端和呼叫会话控制功能实体 | |
| US9021300B2 (en) | Method of changing over from a primary HSS to a backup HSS in an IP network | |
| WO2007025480A1 (en) | Method of session processing in an ims and interrogating-call state control function | |
| CN101621772A (zh) | 一种会话控制方法及设备 | |
| CN101667936A (zh) | 接入会话控制服务器的故障处理方法、设备及系统 | |
| US7899036B2 (en) | Assignment of a serving entity in a communication system | |
| WO2009036629A1 (en) | Processing method after core network element restarting or recovering form failure | |
| WO2007003140A1 (en) | An authentication method of internet protocol multimedia subsystem | |
| WO2008134975A1 (en) | Method, apparatus and system for deregistering the connection address of wireless ip access network | |
| KR101453971B1 (ko) | 무선 네트워크와 유선 네트워크의 연동을 위한 장치 및방법 | |
| US8036659B2 (en) | Method for requesting an unregistered UE to perform registration in the IMS | |
| KR101620809B1 (ko) | Sip 프록시 장애 극복을 위한 방법 | |
| WO2010139279A1 (zh) | 一种ims网络中处理s-cscf变更的方法及系统 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2006761564 Country of ref document: EP |
|
| WWP | Wipo information: published in national office |
Ref document number: 2006761564 Country of ref document: EP |