METHOD AND APPARATUS FOR AN I-CSCF TO ASSIGN TO A USER EQUIPMENT A S-CSCF SERVER IN AN IMS SYSTEM

• US 20170026423A1
• Filed: 11/29/2013
• Published: 01/26/2017
• Est. Priority Date: 11/29/2013
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: BERK, Ingo, MERINO VAZQUEZ, Emiliano, BEJARANO GARCIA, Francisca
• Granted Patent: US 9,992,239 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A method for assigning to a terminal device (UE) a service server (SS) carried out by an IS, by any of the SSs, and by the UDB in a cooperative/corresponding manner. A “first reallocation (IS/SS/UDB) procedure” and a “second reallocation (IS/SS/UDB) procedure” are correspondingly performed within the IS, the SS and the UDB. The first reallocation procedure allows, via IS/SS/UDB processing and interactions, storing by the UDB, in relationship with at least one of the user identifiers of a UE, a mark indicating that the UE has been assigned to a replacement SS to substitute another SS that has failed. The second reallocation procedure allows, also via IS/SS/UDB processing and interactions, utilization of the mark to trigger a new SS reallocation of the UE to a SS when the UE sends a subsequent registration message.

Claims

1. A method for assigning to a terminal device, UE, a service server, SS, in a telecommunications system, TS, the TS comprising:

a plurality of SSs configured to control communication sessions one of originated by the UE and addressed to the UE;

at least one database server, UDB, configured to store in relationship at least one identifier identifying one of the UE and the user of the UE, hereinafter referred to as “

user identifiers”

, and at least one of an identifier of the SS currently assigned to the UE and information about the capabilities required for an SS to be assigned to the UE, hereinafter referred to as “

SS capabilities”

; and

at least one interrogating server, IS, configured to query the UDB to obtain at least one of an identifier of the SS currently assigned to a UE and the SS capabilities, the method comprising at the IS;

a first reallocation IS procedure, comprising;

receiving a message one of from the UE and addressed to the UE including at least one user identifier, querying the UDB and obtaining an identifier of one of the SS currently assigned to the UE and SS capabilities, and determining one of that the SS currently assigned to the UE and that the SS that can be assigned to the UE according to the received SS capabilities is unable to one of receive and process the received message; and

sending the received message to another SS of the plurality, hereinafter referred to as “

replacement SS”

, further including an information element, hereinafter referred to as a “

user reallocated indication”

, indicating that the UE is to be assigned to the replacement SS in substitution of another SS that has failed, thereby asking the replacement SS to request the UDB to store, in relationship with at least one of the user identifiers;

an identifier of the replacement SS as the currently assigned SS; and

a data, hereinafter as “

user reallocated data mark”

,

indicating that the UE has been assigned to a replacement SS to substitute another SS that has failed; and

a second reallocation IS procedure, comprising;

receiving a registration message from the UE including at least one user identifier, querying the UDB and obtaining an identifier of the SS currently assigned to the UE and an information element, hereinafter referred to as “

user reallocated notification from UDB”

, if a user reallocated data mark is stored by the UDB in relationship with at least one of the user identifiers;

selecting one SS among the plurality of SSs according to SS capabilities; and

sending to the selected SS the registration message received from the UE, the registration message sent to the selected SS not including a user reallocated indication, thereby asking the selected SS to request the UDB to store, in relationship with at least one of the user identifiers, an identifier of the selected SS as the currently assigned SS, and to delete the user reallocated data mark.

2. The method of claim 1, wherein the second reallocation IS procedure further comprises, when a user reallocated notification from UDB is received:

determining that the SS identified by the UDB as the SS currently assigned to the UE rejects to process the received registration message, and then selecting one SS among the plurality of SSs according to SS capabilities.

3. The method of claim 2, wherein determining that the identified SS rejects to process the received registration message comprises:

sending to the identified SS the received registration message further including an information element, hereinafter referred to as “

user fall back indication”

, indicating that the UE was assigned to the SS in substitution of another SS that failed; and

receiving a negative response from the identified SS indicating an unavailability condition of the SS to process the registration message.

4. The method of claim 1, wherein

the TS comprises an Internet Protocol Multimedia Subsystem, IMS, and wherein the IS is configured as an Interrogating-Call Session Control Function, I-CSCF.

5. The method of claim 4, wherein the messages one of received from the UE and addressed to the UE, are Session Initiation Protocol, SIP, messages, and wherein the I-CSCF queries the UDB by sending DIAMETER protocol messages.

6. A method for assigning to a terminal device, UE, a service server, SS, in a telecommunications system, TS, the TS comprising:

a plurality of SSs configured to control communication sessions one of originated by the UE and addressed to the UE;

at least one database server, UDB, configured to store in relationship at least one identifier one of identifying the UE and identifying the user of the UE, hereinafter referred to as “

user identifiers”

, and at least one of identifier of the SS currently assigned to the UE and information about the capabilities required for an SS to be assigned to the UE, hereinafter referred to as “

SS capabilities”

; and

at least one interrogating server, IS, configured to query the UDB to obtain at least one of an identifier of the SS currently assigned to an UE and the SS capabilities, the method comprising at any of the SSs;

a first reallocation SS procedure, comprising;

receiving from the IS a message one of originated by the UE and addressed to the UE including at least one identifier, and further including an information element, hereinafter referred to as “

user reallocated indication”

, indicating that the UE is to be assigned to the SS in substitution of another SS that has failed; and

sending a server assignment message to the UDB including an identifier of the SS, at least one user identifiers included in the received message, and further including an information element, hereinafter referred to as “

user reallocated notification from SS”

, if the message received by the SS included a user reallocated indication, thereby asking the UDB to store, in relationship with at least one of the user identifiers;

an identifier of the SS as the currently assigned SS; and

a data, hereinafter as “

user reallocated data mark”

,

indicating that the UE has been assigned to a replacement SS to substitute another SS that has failed; and

a second reallocation SS procedure, comprising;

receiving from the IS a registration message originated by the UE including at least one user identifier, the registration message received from the IS not including a user reallocated indication; and

sending a server assignment message to the UDB including an identifier of the SS and at least one user identifier included in the received message, the server assignment message not including a user reallocated notification from SS, thereby asking the UDB to store, in relationship with at least one of the user identifiers, an identifier of the SS as the currently assigned SS, and to delete the user reallocated data mark.

7. The method of claim 6, wherein the second reallocation SS procedure further comprises:

receiving from the IS a registration message originated by the UE including at least one user identifier, and further including an information element, hereinafter referred to as “

user fall back indication”

, indicating that the UE was assigned to the SS in substitution of another SS that failed; and

one of;

sending a negative response message to the IS indicating an unavailability condition of the SS to process the registration message if there is an ongoing communication session controlled by the SS in respect to the UE; and

sending a positive response message to the IS indicating the availability of the SS to process the registration message if there is not an ongoing communication session controlled by the SS in respect to the UE.

8. The method of claim 7, wherein the received registration message includes a user fall back indication and further includes a requested registration time, and wherein the positive response to the IS includes a registration time shorter than the requested registration time.

9. The method of claim 6, wherein the TS comprises an Internet Protocol Multimedia subsystem, IMS, and wherein the SS is configured as a Serving-Call Session Control Function, S-CSCF.

10. The method of claim 9, wherein the messages exchanged with the IS are Session Initiation Protocol, SIP, messages, and wherein the server assignment messages to the UDB are DIAMETER protocol messages.

11. A method for assigning to a terminal device, UE, a service server, SS, in a telecommunications system, TS, the TS comprising:

a plurality of SSs configured to control communication sessions one of originated by the UE and addressed to the UE;

at least one database server, UDB, configured to store in relationship at least one identifier identifying one of the UE and the user of the UE, hereinafter referred to as “

user identifiers”

, and at least one of an identifier of the SS currently assigned to the UE and information about the capabilities required for an SS to be assigned to the UE, hereinafter referred to as “

SS capabilities”

; and

at least one interrogating server, IS, configured to query the UDB to obtain at least one of an identifier of the SS currently assigned to a UE and the SS capabilities the method comprising at the UDB;

a first reallocation UDB procedure, comprising;

receiving from a SS a server assignment message including an identifier of the SS, at least one user identifier, and further including an information element, hereinafter referred to as “

user reallocated notification from SS”

; and

storing, in relationship with at least one of the user identifiers;

an identifier of the SS as the currently assigned SS; and

a data, hereinafter as “

user reallocated data mark”

,

indicating that the UE has been assigned to a replacement SS to substitute another SS that has failed; and

a second reallocation UDB procedure, comprising;

receiving a query from the IS to obtain an identifier of the SS currently assigned to the UE including at least one user identifier, and reply to the IS query with an identifier of the currently assigned SS and with an information element, hereinafter referred to as “

user reallocated notification from UDB”

, if a user reallocated data mark is stored by the UDB in relationship with at least one of the user identifiers, thereby indicating the IS that a SS among the plurality has to be selected for the UE according to SS capabilities;

receiving from a SS a server assignment message including an identifier of the SS and at least one user identifier, the server assignment message not including a user reallocated notification from SS; and

storing, in relationship with at least one of the user identifiers, an identifier of the SS as the currently assigned SS in replacement of the SS that was stored as the currently assigned SS, and deleting the user reallocated data mark stored in relationship with any of the user identifiers.

12. The method of claim 11, wherein the second reallocation UDB procedure further comprises, wherein the server assignment message does not include a user reallocated notification from SS, and wherein a user reallocated data mark was previously stored in relationship with at least one of the user identifiers:

sending a deregistration request message to the SS that was stored as the currently assigned SS including at least one user identifier.

13. The method of claim 12, wherein the TS comprises an Internet Protocol Multimedia Subsystem, IMS, and wherein the UDB is configured as a Home Subscriber Server, HSS.

14. The method of claim 11, wherein the messages exchanged by the UDB with any of the SS and with the IS are DIAMETER protocol messages.

15. An interrogating server, IS, in a telecommunications system that comprises:

a plurality of service servers, SS, configured to control communication sessions one of originated by the UE and addressed to the UE;

at least one database server, UDB, configured to store in relationship at least one identifier identifying one of the UE and the user of the UE, hereinafter referred to as “

user identifiers”

, and at least one of an identifier of the SS currently assigned to the UE and information about the capabilities required for an SS to be assigned to the UE, hereinafter referred to as “

SS capabilities”

; and

at least one interrogating server, IS, configured to query the UDB to obtain at least one of an identifier of the SS currently assigned to a UE and the SS capabilities the IS comprising;

a unit, hereinafter referred as “

first reallocation IS unit”

, configured for;

receiving a message from the UE or addressed to the UE including at least one user identifier, querying the UDB and obtaining an identifier of one of the SS currently assigned to the UE and SS capabilities, and determining one of that the SS currently assigned to the UE and that the SS that can be assigned to the UE according to the received SS capabilities is unable to one of receive process the received message; and

sending the received message to another SS of the plurality, hereinafter referred to as “

replacement SS”

, further including an information element, hereinafter referred to as “

user reallocated indication”

, indicating that the UE is to be assigned to the replacement SS in substitution of another SS that has failed, thereby asking the replacement SS to request the UDB to store, in relationship with at least one of the user identifiers;

an identifier of the replacement SS as the currently assigned SS; and

a data, hereinafter as “

user reallocated data mark”

,

indicating that the UE has been assigned to a replacement SS to substitute another SS that has failed; and

a unit, hereinafter referred to as “

second reallocation IS unit”

, configured for;

receiving a registration message from the UE including at least one user identifier, querying the UDB and obtaining an identifier of the SS currently assigned to the UE and an information element, hereinafter referred to as “

user reallocated notification from UDB”

, if a user reallocated data mark is stored by the UDB in relationship with at least one of the user identifiers;

selecting one SS among the plurality of SSs according to SS capabilities, and

sending to the selected SS the registration message received from the UE, the registration message sent to the selected SS not including a user reallocated indication, thereby asking the selected SS to request the UDB to store, in relationship with at least one of the user identifiers, an identifier of the selected SS as the currently assigned SS, and to delete the user reallocated data mark.

16. The server of claim 15, wherein the second reallocation IS unit is further configured for, when a user reallocated notification from UDB is received:

determining that the SS identified by the UDB as the SS currently assigned to the UE rejects to process the received registration message, and then selecting one SS among the plurality of SSs according to SS capabilities.

17. The server of claim 16, wherein the second reallocation IS unit is further configured for determining that the identified SS rejects to process the received registration message by:

sending to the identified SS the received registration message further including an information element, hereinafter referred to as “

user fall back indication”

, indicating that the UE was assigned to the SS in substitution of another SS that failed; and

receiving a negative response from the identified SS indicating an unavailability condition of the SS to process the registration message.

18. The server of claim 15, wherein the TS comprises an Internet Protocol Multimedia Subsystem, IMS, and wherein the IS is configured as an Interrogating-Call Session Control Function, I-CSCF.

19. A service server, SS, in a telecommunications system that comprises:

a plurality of SSs configured to control communication sessions one of originated by the UE and addressed to the UE;

at least one database server, UDB, configured to store in relationship at least one identifier one of identifying the UE and identifying the user of the UE, hereinafter referred to as “

user identifiers”

, and at least one of identifier of the SS currently assigned to the UE and information about the capabilities required for an SS to be assigned to the UE, hereinafter referred to as “

SS capabilities”

; and

at least one interrogating server, IS, configured to query the UDB to obtain at least one of an identifier of the SS currently assigned to an UE and the SS capabilities, the SS comprising;

a unit, hereinafter referred as “

first reallocation SS unit”

, configured for;

receiving from the IS a message one of originated by the UE and addressed to the UE including at least one identifier, and further including an information element, hereinafter referred to as “

user reallocated indication”

, indicating that the UE is to be assigned to the SS in substitution of another SS that has failed; and

sending a server assignment message to the UDB including an identifier of the SS, at least one user identifiers included in the received message, and further including an information element, hereinafter referred to as “

user reallocated notification from SS”

, if the message received by the SS included a user reallocated indication, thereby asking the UDB to store, in relationship with at least one of the user identifiers;

an identifier of the SS as the currently assigned SS; and

a data, hereinafter as “

user reallocated data mark”

,

indicating that the UE has been assigned to a replacement SS to substitute another SS that has failed; and

a unit, hereinafter referred to as “

second reallocation SS unit”

, configured for;

receiving from the IS a registration message originated by the UE including at least one user identifier, wherein the registration message received from the IS does not include a user reallocated indication; and

sending a server assignment message to the UDB including an identifier of the SS and at least one user identifier included in the received message, the server assignment message not including a user reallocated notification from SS, thereby asking the UDB to store, in relationship with at least one of the user identifiers, an identifier of the SS as the currently assigned SS, and to delete the user reallocated data mark.

20. The server of claim 19, wherein the second reallocation SS unit is further configured for:

receiving from the IS a registration message originated by the UE including at least one user identifier, and further including an information element, hereinafter referred to as “

user fall back indication”

, indicating that the UE was assigned to the SS in substitution of another SS that failed; and

one of;

sending a negative response message to the IS indicating an unavailability condition of the SS to process the registration message if there is an ongoing communication session controlled by the SS in respect to the UE; and

sending a positive response message to the IS indicating the availability of the SS to process the registration message if there is not an ongoing communication session controlled by the SS in respect to the UE.

21. The server of claim 20, wherein the received registration message includes a user fall back indication and further includes a requested registration time, and wherein the second reallocation SS unit is further configured to send the positive response to the IS including a registration time shorter than the requested registration time.

22. The server of claim 19, wherein the TS comprises an Internet Protocol Multimedia Subsystem, IMS, and wherein the SS is configured as a Serving-Call Session Control Function, S-CSCF.

23. A user database server, UDB, in a telecommunications system that comprises:

a plurality of service servers, SS, configured to control communication sessions one of originated by the UE and addressed to the UE;

at least one database server, UDB, configured to store in relationship at least one identifier identifying one of the UE and the user of the UE, hereinafter referred to as “

user identifiers”

, and at least one of an identifier of the SS currently assigned to the UE and information about the capabilities required for an SS to be assigned to the UE, hereinafter referred to as “

SS capabilities”

; and

at least one interrogating server, IS, configured to query the UDB to obtain at least one of an identifier of the SS currently assigned to a UE and the SS capabilities, the UDB comprising;

a unit, hereinafter referred to as “

first reallocation UDB unit”

, configured for;

receiving from a SS a server assignment message including an identifier of the SS, at least one user identifier, and further including an information element, hereinafter referred to as “

user reallocated notification from SS”

; and

storing, in relationship with at least one of the user identifiers;

an identifier of the SS as the currently assigned SS; and

a data, hereinafter as “

user reallocated data mark”

,

indicating that the UE has been assigned to a replacement SS to substitute another SS that has failed; and

a unit, hereinafter referred to as “

second reallocation UDB unit”

, configured for;

receiving a query from the IS to obtain an identifier of the SS currently assigned to the UE including at least one user identifier, and reply to the IS query with an identifier of the currently assigned SS and with an information element, hereinafter referred to as “

user reallocated notification from UDB”

, if a user reallocated data mark is stored by the UDB in relationship with at least one of the user identifiers, thereby indicating the IS that a SS among the plurality has to be selected for the UE according to SS capabilities;

receiving from a SS a server assignment message including an identifier of the SS and at least one user identifier, the server assignment message not including a user reallocated notification from SS; and

storing, in relationship with at least one of the user identifiers, an identifier of the SS as the currently assigned SS in replacement of the SS that was stored as the currently assigned SS, and deleting the user reallocated data mark stored in relationship with any of the user identifiers.

24. The server of claim 23, wherein the second reallocation UDB unit is further configured for, wherein the server assignment message does not include a user reallocated notification from SS, and wherein a user reallocated data mark was previously stored in relationship with at least one of the user identifiers:

sending a deregistration request message to the SS that was stored as the currently assigned SS including at least one user identifier.

25. The server of claim 23, wherein the TS comprises an Internet Protocol Multimedia Subsystem, IMS, and wherein the UDB is configured as a Home Subscriber Server, HSS.

26-28. -28. (canceled)