WO2009092310A1 - Procédé et dispositif de fourniture de services pour un utilisateur - Google Patents
Procédé et dispositif de fourniture de services pour un utilisateur Download PDFInfo
- Publication number
- WO2009092310A1 WO2009092310A1 PCT/CN2009/070112 CN2009070112W WO2009092310A1 WO 2009092310 A1 WO2009092310 A1 WO 2009092310A1 CN 2009070112 W CN2009070112 W CN 2009070112W WO 2009092310 A1 WO2009092310 A1 WO 2009092310A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- data
- service
- cscf
- registered
- Prior art date
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
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
Definitions
- the present invention relates to the field of network technologies, and in particular, to a method and device for providing services to users. Background technique
- IMS IP Multimedia Subsystem
- the existing IMS includes a CSCF (Call Session Control Function), which is in the core control position of the IMS core network, and is responsible for registration authentication and session control of the UE (User Equipment);
- the Home Subscriber Server (HSS) is a user database server that stores the IMS subscription information set when the operator opens an account, and supports customization and modification of the subscription data by the operator or the terminal user through the interface with the service management system.
- the CSCF includes an S-CSCF (Serving-CSCF, Serving Call Session Control Function), a P-CSCF (Proxy-CSCF, Proxy Call Session Control Function), and an I-CSCF (Interrogating-CSCF, Interrogation Call Session Control Function).
- the S-CSCF when the S-CSCF receives the session request sent by the user, because the S-CSCF does not have corresponding user data, the S-CSCF sends a SAR (Server Assignment Request) requesting user data to the HSS, and the HSS finds The S-CSCF recorded in the S-CSCF and the HSS are the same, but the user status of the requested operation is registered in the HSS, and the HSS will not return the user's service information, so the service will fail.
- SAR Server Assignment Request
- the embodiments of the present invention provide a method and a device for providing services for a user, so that the S-CSCF in the network can continue to provide services for users after a downtime or abnormal restart.
- an embodiment of the present invention provides a method for providing a service for a user, including:
- the S-CSCF determines that the user data of the user is not saved.
- the S-CSCF obtains user data of the user, and provides a service for the user according to the user data.
- the embodiment of the present invention further provides a service call session control function entity S-CSCF, including:
- the determining unit when receiving the service request of the user, determines that the user data of the user is not saved by itself; and the user data of the user is obtained when the user data is used;
- a processing unit configured to provide a service for the user according to user data acquired by the data acquiring unit.
- the embodiment of the invention has the following advantages:
- the S-CSCF fails to provide services to the user after a downtime or abnormal restart in the network, the user's data is obtained, and the user is provided with the originating service or the final service according to the user's data, thereby avoiding the abnormality of the network entity. Poor business volume brought by users DRAWINGS
- Figure 1 is a functional architecture diagram of an IMS network
- FIG. 2 is a schematic diagram of a session flow initiated by a user
- FIG. 3 is a schematic diagram of a session flow in which an AS initiates a call in place of a user;
- FIG. 4 is a flowchart of a method for providing a service to a user in an embodiment of the present invention
- FIG. 5 is a flowchart of service recovery after the S-CSCF is restarted in the first embodiment of the present invention
- FIG. 6 is a flowchart of service recovery after the S-CSCF is down in the second embodiment of the present invention
- FIG. 7 is an S-CSCF in the embodiment of the present invention. Schematic diagram of the structure
- FIG. 8 is a schematic structural diagram of an S-CSCF according to an embodiment of the present invention. detailed description
- the CSCF is in the core control position of the IMS core network. It is responsible for the registration authentication and session control of the UE. The execution is for the calling and called terminals.
- the basic session routing function of the IMS user, and according to the IMS filtering rule signed by the user, the value-added service route triggering and service control interaction to the AS (Application Server, Application Server) are performed when the conditions are met.
- the HSS is a user database server, which stores the IMS subscription information set when the operator opens an account, and supports customization and modification of the subscription data by the operator or the terminal user through the interface with the service management system.
- the HSS registers the S-CSCF domain name routing information in the IMS registration process through the Cx interface based on the Diameter protocol with the S-CSCF, and supports downloading the basic IMS subscription information to the S-CSCF through the interface; the HSS passes the I-CSCF
- the Cx interface based on the Diameter protocol implements the S-CSCF for user selection in the user registration or provides the I-CSCF with the name of the S-CSCF currently serving the user, so that the I-CSCF can route the registration message or session to the correct one.
- the S-CSCF provides the Sh interface based on the Diameter protocol with the SIP AS. It is a Session Initiation Protocol (SIP) or an Open Access Architecture (SCS) (Service Capability Servers). Service Capability Server) Provides remote database access interfaces for contract data and business logic scripts.
- SIP Session Initiation Protocol
- SCS Open Access Architecture
- the HSS is only responsible for the transparent storage of the value-added service data of the specific contracted user, and is not semantically parsed.
- the SLF Subscribescription Locator Function
- the SLF Subscribescription Locator Function
- This mechanism enables the I-CSCF, S-CSCF, and AS to find The HSS address where the subscription data of the user identity is located can be physically combined with the HSS.
- the AS obtains or updates user service related data and user status information through the Sh interface of the HSS, and the S-CSCF obtains the user's subscription information through the Cx interface with the HSS.
- the UE After the UE registers in the network, it can use various services provided by the IMS network. At the same time, the UE may choose to subscribe to the unregistered service. When the UE is not registered in the network, the network may still provide the user with unregistered services such as incoming call forwarding, incoming call records, and the like.
- the S-CSCF and the HSS authenticate the user and the service data through the SAR/SAA (Server Assignment Answer) command of the Cx interface.
- SAR/SAA Server Assignment Answer
- SAR/SAA application scenario When the S-CSCF receives a registration request from a UE sent by the P-CSCF or receives a session establishment request INVITE message from the I-CSCF.
- the S-CSCF performs the following operations to the HSS through the SAR command:
- Diameter AVP Public User Public-Identity C One or more public Identities/Public (conditions are required, except for the service identity other than the registration). Must be included and can only contain one. You must include this account when you go to the registration operation but the private identity does not exist.
- Private User User-Name C Private identity for S-CSCF Identity/Private (when the condition is met, it must be included. When you select Service Identity), if the public identity does not exist, you must include the private share.
- the S-CSCF asks for an Assignment Assignment to the HSS.
- the S-CSCF tells the HSS that Available Available data is available.
- NO_ASSIGNMENT(0) Used by the S-CSCF to request user data from the HSS without affecting the registration status of the user;
- RE_REGISTRATION(2) used for re-registration of an identity
- UNREGISTERED_USER(3) Used to instruct the S-CSCF to receive an INVITE request for a call to an unregistered user;
- TIMEOUT_DEREGISTRATION (4) used to deregister due to the registration timer timeout
- USER_DEREGISTRATION(5) Used by the S-CSCF to receive a user-initiated deregistration request
- TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME (6) Used for deregistration due to the registration timer timeout, while the S-CSCF saves the user data and requests the HSS to save the name of the S-CSCF;
- AUTHENTIC ATION_FAILURE 9: used to indicate user authentication failure
- AUTHENTIC ATION_TIMEOUT(10) Used to indicate the authentication timeout; 12.
- the HSS will not replace the original with the name of the new S-CSCF, but return the Experimental-Result-Code to
- DIAMETER_E OR_IDENTITY_ALREADY_REGISTERED indicates that the user has been assigned an S-CSCF.
- the Server Assignment Type is UNREGISTERED—the USER indicates that the S-CSCF has received an INVITE request to terminate the call to an unregistered IMPU, but the IMPU in the HSS is Registered, HSS will return Experimental-Result-Code to DIAMETER_E OR_IN_ASSIGNMENT_TYPE, indicating that the S-CSCF has been assigned to the user, and the user's current state does not allow the operation.
- Table 2 Main application layer parameters carried in the message Category description of IE name mapping
- Registration result Result- M Result-Code is used to indicate
- AVP does not exist.
- the HSS may download the user data and billing function address when the operation type is NO_ASSIGNMENT, REGISTRATION, RE_REGISTRATION, UNREGISTERED_USER.
- the initial call session process of the user registered in the network includes the following steps:
- Step s201 The UE initiates an INVITE message, and may select to fill in a P-Preferred-Identity header field with a Public User Identity that can identify itself.
- Step s202 After receiving the INVITE message, the P-CSCF checks whether there is any message in the message. P-Preferred-Identity header field and check whether its value matches a registered Public User Identity recorded in the P-CSCF. If there is and matches, the P-CSCF uses the Public User Identity as the session initiator and fills in the P. - Asserted-Identity; if there is no match or no P-Preferred-Identity header field, the P-CSCF selects a default Public User Identity for the user as the session initiator and fills in the P-Asserted-Identity;
- Step s203 After receiving the INVITE message, the S-CSCF performs service triggering according to the identity of the calling user in the P-Asserted-Identity header field in the message, and then performs routing of the subsequent session according to the Request-URI in the INVITE message. .
- the AS replaces the initial call session process of the user who has registered in the network. As shown in FIG. 3, the following steps are included:
- Step s301 If the AS can obtain the name of the S-CSCF where the user is located before the user initiates the initial call, perform step s301a of FIG. 3, that is, the AS directly routes the session to the S-CSCF where the user is located. If the name of the S-CSCF where the user is located cannot be obtained, the following steps s301bl need to be performed;
- Step s301a routing the session to the S-CSCF of the home domain where the user is located;
- Step s301bl routing the session to the I-CSCF of the home domain where the user is located;
- Step s301b2 The I-CSCF initiates a location information request (LIR) message to the HSS, fills in the identity of the calling user in the P-Asserted-Identity header field in the message, and adds an initial call request flag. Query the current location information of the user, that is, the information of the S-CSCF where the user is located;
- LIR location information request
- Step s301b3 the HSS queries the information corresponding to the user in the database according to the identity of the user in the LIR, and returns the name of the S-CSCF where the user is located or the capability set of the S-CSCF to the I through the LIA (Location Info Request).
- -CSCF the HSS queries the information corresponding to the user in the database according to the identity of the user in the LIR, and returns the name of the S-CSCF where the user is located or the capability set of the S-CSCF to the I through the LIA (Location Info Request).
- Step s301b4 if the HSS returns the capability set of the S-CSCF, the I-CSCF needs to select the S-CSCF according to the capability set;
- Step s301b5 the I-CSCF routes the INVITE message to the S-CSCF returned by the HSS, or the S-CSCF selected by the user according to the capability set of the S-CSCF returned by the HSS;
- Step s302 If the S-CSCF does not have the information of the user, the S-CSCF will message The user identity in the P-Asserted-Identity header field carries the user subscription data in the SAR to the HSS; if there is information about the user, step s304 is directly performed;
- Step s303 The HSS returns the requested user subscription data to the S-CSCF through the SAA.
- Step s305 The S-CSCF performs subsequent processing.
- An embodiment of the present invention provides a method for providing a service to a user. As shown in FIG. 4, the method includes the following steps:
- Step s401 The S-CSCF receives the service request of the user.
- the service request of the received user may be: an AS originating service request initiated by the AS, or an originating service request initiated by the I-CSCF instead of the user, or a user terminal forwarded by the I-CSCF.
- Step s402 The S-CSCF finds that the data of the user does not exist locally.
- the S-CSCF may be restarted due to downtime or abnormality, resulting in loss of user data; or the S-CSCF is an alternative S selected by the I-CSCF when the S-CSCF providing services for the user fails. -CSCF, so there is no data for this user.
- Step s403 The S-CSCF acquires data of the user.
- the S-CSCF may send a request message to the HSS to obtain data of the user.
- Step s404 The S-CSCF determines a registration status of the user according to the acquired data, and provides a service for the user.
- the data of the user includes at least the subscription service configuration data of the user, and the S-CSCF performs service matching and triggering according to the initial filtering rule in the subscription service configuration data of the user; and may also include the registered backup data of the user.
- the registration backup data includes, but is not limited to, the address of the P-CSCF stored by the S-CSCF at the time of registration and the CONTACT address of the user equipment. Based on the acquired data of the user, the S-CSCF can learn the registration status of the user, and then process the service request of the user to provide services for the user.
- the S-CSCF restarted by the downtime receives an originating service request initiated by the AS instead of the user, or receives an AS that is transferred from the I-CSCF instead.
- the processing flow of the service request is as shown in FIG. 5, and includes the following steps:
- Step s501 The S-CSCF receives the AS sent by the AS or the I-CSCF instead of the user-originated originating service request, where step 501a, step 501bl-501b4 is the same as the prior art, or the S-CSCF receives as shown in step 501c.
- Step s502 If the S-CSCF does not have the data of the user, request the unregistered service data of the user from the HSS through the SAR according to a normal process;
- Step s503a the HSS determines the name of the S-CSCF requesting the data.
- the HSS returns The indication information that the user identity of the user has been registered does not return the user subscription data and the registration backup data, wherein the indication information may be indicated by a DIAMETER_ERROR_IN_ASSIGNMENT_TYPE error code, and the HSS may also add an indication to the SAA that the request is not registered.
- the user identity of the business is registered;
- Step s503b After receiving the error code, the S-CSCF re-requests the user data to the HSS by using the SAR with the recovery indication;
- Step s504 The HSS brings the subscription data of the user to the S-CSCF through the SAA, and the HSS may also add an indication to the SAA that the identity of the user requesting the unregistered service is registered;
- the HSS may have the same name of the S-CSCF in the discovery request data and the name of the saved S-CSCF, and when the registration status of the user is registered, the user's subscription data is brought to the S- via the SAA while returning the DIAMETER_ERROR_IN_ASSIGNMENT_TYPE error code. CSCF; Then step s503a, step s503b may not be performed. If the HSS saves the user's registered backup data, you can choose to bring the registered backup data together to the S-CSCF through the SAA;
- the S-CSCF can determine that the user is registered by receiving the DIAMETER_E OR_IN_ASSIGNMENT_TYPE, and the S-CSCF can also determine that the user is registered by receiving the registered backup data of the user, S-CSCF. It is also possible to request unregistered services through the instructions carried in the SAA.
- the user identity is the registered information, and it is determined that the user is registered.
- Step s505 When the S-CSCF receives the originating service request from the AS or the I-CSCF, and the S-CSCF determines that the user is in the registered state by using the step s503a or the step s504, the triggering of the originating registration is triggered.
- the S-CSCF determines, by step s503a or step s504, that the user is in the registered state, and At the same time, when the registered backup data is received, the matching terminated service is triggered; if the user is in the registered state but does not receive the registered backup data, the matching unregistered service is triggered.
- Step s506 The S-CSCF performs an initial service request.
- the I-CSCF receives the final service request, or receives the originating service request initiated by the AS instead of the user, or receives the P-
- the processing flow of the service request is as shown in FIG. 6, and includes the following steps:
- Step s601 The I-CSCF forwards the service request to the S-CSCF1 that provides the service for the user; Step s601a, S-CSCF1 returns a failure response indicating that an abnormality cannot continue to provide services for the user; or step s601b, I-CSCF does not receive the S - The response of the CSCF1; Step s602, the I-CSCF explicitly requests the capability set of the S-CSCF to the HSS; if the I-CSCF has received the service request message and has learned that the S-CSCF1 is down or abnormal, the above step s601 may not be performed. Step s601a and step s601b;
- Step s603 the HSS returns the capability set of the S-CSCF;
- step s602 If the previous I-CSCF has obtained the capability set of the S-CSCF serving the user from the HSS, the above step s602, step s603 may not be performed;
- Step s604 The I-CSCF reselects an S-CSCF2 for the user according to the capability set of the S-CSCF, and forwards the service request to the new S-CSCF2, optionally, may bring a recovery indication in the message, and explicitly tells S -CSCF2 needs to recover data from HSS;
- Step s605 The S-CSCF2 has no user data, and requests the user data to the HSS through the SAR with the recovery indication;
- Step s606 The HSS returns the user data to the S-CSCF2 through the SAA, and the HSS may also add an indication to the SAA indicating whether the user identity of the requested data has been injected. Booklet.
- the user data includes at least the subscription service configuration data of the user, and may optionally include
- Step s607 After receiving the user subscription service configuration data and the registration backup data, the S-CSCF2 triggers the matched registered service. If only the user's subscription service configuration data is received, the user identity of the requested data is not received. The registered information triggers the matching unregistered service; if the user's subscription service configuration data is received, and the information indicating that the user identity of the requested data is registered is received, the start of the matching is triggered for the initial service request. The registered service is sent; for the final service request, the matching unregistered service is triggered.
- Step s608, S-CSCF2 performs subsequent routing.
- the method provided by the embodiment of the present invention when the S-CSCF in the network fails to provide services to the user after a downtime or abnormal restart, obtains the user's data, and continues to provide the user with the originating service according to the user data.
- the final service avoids the poor service experience brought by the network entity exception to the user.
- the embodiment of the present invention further provides a service call session control function entity S-CSCF, and its structure is as shown in FIG. 7, which includes:
- the determining unit 10 when receiving the service request of the user, determines that the user data of the user is not saved by itself;
- the processing unit 30 is configured to provide a service for the user according to the user data acquired by the data acquiring unit 20.
- the data obtaining unit 20 further includes:
- a first obtaining sub-unit 21, configured to send a request for acquiring user data to the HSS
- a second obtaining sub-unit 22 configured to: when receiving the HSS, returning the user that is returned when the S-CSCF is registered
- the indication that the user identity of the user has been registered sends a request for carrying the recovery indication to the HSS, and receives data of the user sent by the HSS.
- a third obtaining subunit 23 configured to send the acquiring user to the HSS a request for data, and receiving indication information that the HSS has registered the user identity of the user returned when the user has registered at the S-CSCF, and user data sent by the HSS.
- the first determining sub-unit 31 is configured to: when the data obtaining unit receives the indication information that the user identity of the user has been registered or the registered backup data in the received user data, determine that the user has been registered;
- the first processing sub-unit 32 is configured to perform processing according to the determination result of the first determining sub-unit 31, and trigger the originating registered service according to the user data for the originating service request of the registered user; for the unregistered user The originating service request, triggering the originating unregistered service according to the user data; and for the final service request of the registered user, if the received user data of the user includes the registered backup data, according to the user data Triggering the terminated service, otherwise triggering the unregistered service; triggering the unregistered service for the unregistered user.
- the embodiment of the present invention further provides a service call session control function entity S-CSCF, and its structure is as shown in FIG. 8, which includes:
- the determining unit 50 when receiving the service request of the user, determines that the user data of the user is not saved by itself;
- the data obtaining unit 60 is configured to acquire user data of the user when the determining unit 50 determines that the user data of the user does not exist locally;
- the processing unit 70 is configured to provide a service for the user according to the user data acquired by the data acquiring unit 60.
- the fourth obtaining subunit 61 is configured to send a request for carrying the recovery indication to the HSS, and receive user data sent by the HSS.
- processing unit 70 further includes:
- a second determining sub-unit 71 configured to determine whether the user data acquired by the data acquiring unit includes registration backup data, or information that the HSS indicates that the user identity of the requested data is registered;
- the second processing sub-unit 72 is configured to perform processing according to the determination result of the second determining sub-unit 71, if the user data includes registration backup data, or when the user identity of the requested data is received as the registered indication information , for the originating service request or the final service request of the user, triggering the originating registered service or the terminally registered service of the user;
- the start of the user is triggered for the originating service request or the final service request of the user.
- Sending an unregistered service or a terminal unregistered service if the user data does not include the registered backup data, but the user identity of the requested data is the registered indication information, triggering on the initial service request of the user
- the originating service of the user is registered; for the final service request of the user, the unregistered service of the user is triggered.
- the S-CSCF in the network fails to provide services for the user after a downtime or abnormal restart, obtains the user's data, and continues to provide the user with the originating service according to the user data.
- the final service avoids the poor service experience brought by the network entity exception to the user.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
L'invention concerne un procédé de fourniture de services pour un utilisateur. Ledit procédé comprend les étapes suivantes: lorsqu'une entité de fonction de contrôle de session d'appel de services (S-CSCF) reçoit une demande de services de l'utilisateur, elle détermine que l'entité S-CSCF elle-même ne stocke pas de données utilisateur de l'utilisateur. L'entité S-CSCF obtient des données utilisateur de l'utilisateur, et fournit des services pour l'utilisateur en fonction de données utilisateur. Une entité de fonction de contrôle de session d'appel de services (S-CSCF) est également prévue. Après arrêt ou rédémarrage anormal de l'entité S-CSCF du réseau, elle ne peut fournir en continu les services pour l'utilisateur. L'entité S-CSCF redémarrée ou une entité S-CSCF de substitution obtient des données utilisateur et fournit des services initiaux ou des services terminaux en continu pour l'utilisateur en fonction de données utilisateur, ce qui permet d'éviter à l'utilisateur l'expérience de moins bons services causée par l'anomalie de l'entité du réseau.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200810001411.7 | 2008-01-18 | ||
CN 200810001411 CN101489215A (zh) | 2008-01-18 | 2008-01-18 | 为用户提供业务的方法和设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009092310A1 true WO2009092310A1 (fr) | 2009-07-30 |
Family
ID=40891843
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/070112 WO2009092310A1 (fr) | 2008-01-18 | 2009-01-12 | Procédé et dispositif de fourniture de services pour un utilisateur |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101489215A (fr) |
WO (1) | WO2009092310A1 (fr) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1655546A (zh) * | 2004-02-10 | 2005-08-17 | 华为技术有限公司 | 一种减轻归属签约用户服务器接口负荷的方法 |
CN1852289A (zh) * | 2005-08-03 | 2006-10-25 | 华为技术有限公司 | 一种对用户标识存在性进行约束的方法及系统 |
CN1878087A (zh) * | 2006-03-20 | 2006-12-13 | 华为技术有限公司 | 服务呼叫会话控制功能实体备份方法及其系统 |
DE102005055147A1 (de) * | 2005-11-18 | 2007-05-24 | Siemens Ag | Verfahren zum Aufbau zumindest einer geschützten Datenverbindung nach einem Wechsel des Zugangsnetzes in einem mobilen Kommunikationssystem |
-
2008
- 2008-01-18 CN CN 200810001411 patent/CN101489215A/zh active Pending
-
2009
- 2009-01-12 WO PCT/CN2009/070112 patent/WO2009092310A1/fr active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1655546A (zh) * | 2004-02-10 | 2005-08-17 | 华为技术有限公司 | 一种减轻归属签约用户服务器接口负荷的方法 |
CN1852289A (zh) * | 2005-08-03 | 2006-10-25 | 华为技术有限公司 | 一种对用户标识存在性进行约束的方法及系统 |
DE102005055147A1 (de) * | 2005-11-18 | 2007-05-24 | Siemens Ag | Verfahren zum Aufbau zumindest einer geschützten Datenverbindung nach einem Wechsel des Zugangsnetzes in einem mobilen Kommunikationssystem |
CN1878087A (zh) * | 2006-03-20 | 2006-12-13 | 华为技术有限公司 | 服务呼叫会话控制功能实体备份方法及其系统 |
Also Published As
Publication number | Publication date |
---|---|
CN101489215A (zh) | 2009-07-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11638230B2 (en) | Method, apparatus and system for processing registration backup data | |
EP2763377B1 (fr) | Procédé et système et élément de réseau pour le traitement de service après l'invalidation de données d'élément et la survenue d'une panne | |
CN101345748B (zh) | 将用户状态通知应用服务器的方法、系统及装置 | |
EP2192742B1 (fr) | Contrôleur de session locale, sous-système multimédia ip et procédé d'enregistrement de session | |
US20100293261A1 (en) | Methods, apparatuses and computer program for ims recovery upon restart of a s-cscf | |
WO2007025480A1 (fr) | Procede de traitement d'une session dans un ims et module de controle de la session lors d'une recherche de controle de la session lors d'une recherche d'appel | |
WO2010075689A1 (fr) | Procédé pour tolérance aux désastres des réseaux, terminal, et entité fonctionnelle de commande de session d'appel | |
US20110145388A1 (en) | Method, system, and device for realizing registration mechanism of ip multimedia subsystem | |
WO2009036629A1 (fr) | Procédé de traitement après redémarrage ou récupération sur sinistre d'un élément de réseau central | |
JP2012249291A (ja) | ネットワーク内サービスの移行及び活性化 | |
US9578068B2 (en) | Methods and apparatus for processing an IMS session | |
KR100703426B1 (ko) | 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 발신 및 착신 호를 가능하게 하는 방법 및 장치 | |
KR101075614B1 (ko) | 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 착신호를 가능하게 하는 방법 | |
WO2009092310A1 (fr) | Procédé et dispositif de fourniture de services pour un utilisateur | |
WO2012083775A1 (fr) | Procédé et dispositif de mise en œuvre de reprise sur sinistre hors site dans un réseau ims |
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: 09704511 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09704511 Country of ref document: EP Kind code of ref document: A1 |