[go: up one dir, main page]

WO2018104060A1 - Continuité de service après un repli de serveur d'application - Google Patents

Continuité de service après un repli de serveur d'application Download PDF

Info

Publication number
WO2018104060A1
WO2018104060A1 PCT/EP2017/080124 EP2017080124W WO2018104060A1 WO 2018104060 A1 WO2018104060 A1 WO 2018104060A1 EP 2017080124 W EP2017080124 W EP 2017080124W WO 2018104060 A1 WO2018104060 A1 WO 2018104060A1
Authority
WO
WIPO (PCT)
Prior art keywords
scc
identifier
node
atcf
received
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
Application number
PCT/EP2017/080124
Other languages
English (en)
Inventor
Prasanna FERNANDO
Maria Cruz BARTOLOMÉ RODRIGO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2018104060A1 publication Critical patent/WO2018104060A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H04W36/00226—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB] wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance

Definitions

  • the present invention generally relates to Application Server restoration in an IP Multimedia Subsystem; and, more specifically, the invention relates to achieving call continuity after an Application Server failover and fall-back.
  • IMS IP Multimedia Subsystem
  • SCC-AS i.e. SCC- ASl where a user equipment (UE) is registered
  • SCC-AS2 a new available SCC-AS, i.e. SCC-AS2
  • S-CSCF Serving Call Session Control Function
  • a SCC-AS may be defined as primary and the rest as secondary, or a prioritized list of selectable SCC-Ass could be defined.
  • the preferred SCC-AS e.g. SCC-ASl
  • fails a new available SCC-AS e.g. SCC-AS2
  • the preferred SCC-ASl should be reselected again.
  • 3 GPP TS 23.380 V13.4.0 does not disclose how to recover the traffic via the preferred SCC-AS 1.
  • SRVCC Single Radio Voice Call Continuity
  • the SCC-AS 1 transmits toward the S-CSCF, and the latter toward the ATCF, access transfer information comprising the Access Transfer Update - Session Transfer Identifier (ATU-STI) of the SCC-AS 1, i.e. the ATU-STIl, and the C- MSISDN of the UE-A.
  • ATU-STI Access Transfer Update - Session Transfer Identifier
  • the ATCF, or both S-CSCF and ATCF stores the received ATU-STIl .
  • SRVCC-HOs for UE-A originated calls are successful because the ATU-STI stored at the ATCF, in this case the ATU-STIl, identifies the SCC-AS 1 and is used during the SRVCC-HO.
  • a similar behaviour can be observed during SRVCC-HOs for UE-A terminated calls.
  • a second exemplary case is where the preferred SCC-AS, i.e. SCC-AS 1, is unreachable during registration of the UE-A, as illustrated in Fig. 2.
  • the S- CSCF selects a new available SCC-AS, i.e. SCC-AS2, and once the UE-A is registered via ATCF, S-CSCF and SCC-AS2, the SCC-AS2 transmits toward the S-CSCF, and the latter toward the ATCF, access transfer information comprising the ATU-STI of the SCC-AS2, i.e. the ATU-STI2, and the C-MSISDN of the UE-A.
  • the ATCF or both S- CSCF and ATCF, stores the received ATU-STI2. That is, the S-CSCF starts using SCC- AS2 for UE-A originating and terminating calls and the ATCF uses the ATU-STI2.
  • SRVCC-HOs for UE-A originated calls are also successful because the ATU-STI stored at the ATCF, in this case the ATU-STI2, identifies the SCC-AS2 and is used during the SRVCC-HO.
  • a similar behaviour can be observed during SRVCC-HOs for UE-A terminated calls.
  • the preferred SCC-AS i.e. SCC-AS 1
  • the S-CSCF selects a new available SCC-AS, i.e.
  • the SCC- AS2 transmits toward the S-CSCF, and the latter toward the ATCF, access transfer information comprising the ATU-STI of the SCC-AS2, i.e. the ATU-STI2, and the C- MSISDN of the UE-A.
  • the ATCF or both S-CSCF and ATCF, stores the received ATU-STI2. That is, the S-CSCF starts using SCC-AS2 for UE-A originating and terminating calls and the ATCF uses the ATU-STI2.
  • the SCC-AS 1 becomes reachable again and, if there is a preference to use the SCC-AS 1, the S-CSCF will select the SCC-AS 1 for the next initial call setup.
  • an initial call setup message e.g. a Session Initiation Protocol (SIP) Invite message
  • SIP Session Initiation Protocol
  • the initial call setup message may be progressed toward a terminating UE, if this is the case.
  • a corresponding acknowledge e.g. a SIP 200 OK, is returned back through the entities involved.
  • SIP Session Initiation Protocol
  • SRVCC-HOs for UE-A originated calls are unsuccessful because the ATU-STI currently stored at the ATCF is in this case the ATU-STI2, which identifies the SCC-AS2 and is used during the SRVCC-HO.
  • the ATCF transmits toward the SCC-A2 an SRVCC-HO setup message such as e.g. SIP Invite message and, since the SCC-AS2 is not aware of the initial call setup message that the S-CSCF transmitted to the SCC-AS 1, the SCC-AS2 returns back to the ATCF an unsuccessful result, e.g. SIP error 400, and the SRVCC-HO fails.
  • the present invention is aimed to at least minimize the above drawbacks and provides for a new method of handling IMS Restoration Procedures for service interruption of an SCC-AS, as well as network nodes cooperating to carry out such method.
  • this method is useful to facilitate a SRVCC-HO for UE originated and terminating calls.
  • a new method of handling IMS Restoration Procedures for service interruption of an SCC- AS the method executed at a network node implementing the ATCF, i.e. ATCF node.
  • This method comprises receiving, at the ATCF node from a selected SCC- AS via a S-CSCF node, access transfer information with an SCC-AS identifier, which identifies the selected SCC-AS, and a UE identifier, which identifies a UE, storing at the ATCF node the received SCC-AS identifier, receiving at the ATCF node an initial call setup message, and transmitting, from the ATCF node toward the selected SCC-AS via the S-CSCF node, the received initial call setup message along with the stored SCC-AS identifier
  • the SCC-AS identifier may correspond to an Access Transfer Update - Session Transfer Identifier (ATU-STI) of the SCC-AS.
  • ATU-STI Access Transfer Update - Session Transfer Identifier
  • the UE identifier may correspond to a Correlation Mobile Station ISDN number, C-MSISDN.
  • the initial call setup message may correspond to a Session Initiation Protocol, SIP, Invite message.
  • this method may further comprise storing at the ATCF node the received UE identifier and, where this is the case, the received initial call setup message may be transmitted along with the stored UE identifier, which identifies the UE.
  • a new method of handling IMS Restoration Procedures for service interruption of an SCC-AS the method executed at a network node implementing the S-CSCF, i.e. S-CSCF node.
  • This method comprises receiving, at the S-CSCF node from a selected SCC- AS, an access transfer information that comprises an SCC-AS identifier, which identifies the selected SCC-AS, and a UE identifier, which identifies a UE; transmitting, from the S-CSCF node toward an ATCF node, the received access transfer information with the received SCC-AS identifier and the received UE identifier; receiving, at the S-CSCF node from an ATCF node, an initial call setup message along with an access transfer information that comprises an SCC-AS identifier and a UE identifier; and transmitting, from the S-CSCF node toward the selected SCC-AS, the received initial call setup message with the received SCC-AS identifier.
  • the SCC-AS identifier may correspond to an ATU-STI of the SCC-AS.
  • the UE identifier may correspond to a C-MSISDN.
  • the initial call setup message may correspond to a SIP Invite message.
  • the received initial call setup message may be transmitted along with the received UE identifier.
  • receiving the access transfer information may be responsive to, and this method may further comprise receiving, at the S-CSCF node, a SIP Register message originated from a UE; selecting, at the S-CSCF node, an available SCC-AS; and transmitting, from the S-CSCF node toward the selected SCC-AS, the SIP Register message.
  • a new method of handling IMS Restoration Procedures for service interruption of an SCC- AS the method executed at a network node implementing the SCC-AS, i.e. SCC-AS node.
  • This method comprises receiving, at the SCC-AS node from an S-CSCF node, an initial call setup message along with an access transfer information that comprises an SCC-AS identifier and a UE identifier; determining, at the SCC-AS node, a mismatch between the received SCC-AS identifier and its own SCC-AS identifier; and transmitting, from the SCC-AS node toward the S-CSCF node, a new access transfer information that comprises the own SCC-AS identifier of the SCC-AS node.
  • the SCC-AS identifier may correspond to an ATU-STI of the SCC-AS node.
  • the UE identifier may correspond to a C- MSISDN.
  • the initial call setup message may correspond to a SIP Invite message.
  • the new access transfer information may also comprise the received UE identifier.
  • an ATCF node Participating in the above methods and exemplary embodiments there are provided an ATCF node, an S-CSCF node and an SCC-AS node.
  • This ATCF node is configured to receive, from a selected SCC-AS via an S- CSCF node and via a receiver of the ATCF node, access transfer information with an SCC-AS identifier, which identifies the selected SCC-AS, and a UE identifier, which identifies a UE; the ATCF node is configured to store a plurality of SCC-AS identifiers identifying a respective plurality of SCC-ASs; and the ATCF node is configured to receive, via the receiver, an initial call setup message, and transmit, toward the selected SCC-AS via a transmitter of the ATCF node and via the S-CSCF node, the received initial call setup message along with the stored SCC-AS identifier, which identifies the selected SCC-AS.
  • the SCC-AS identifier may correspond to an ATU-STI of the SCC-AS.
  • the UE identifier may correspond to a C-MSISDN.
  • the initial call setup message may correspond to a SIP Invite message.
  • the ATCF node may be configured to store a plurality of UE identifiers respectively associated with the plurality of SCC-AS identifiers and, where this is the case, the received initial call setup message may be transmitted along with the stored UE identifier, which identifies the UE.
  • the ATCF node may comprise at least one processor, and at least one memory that stores processor-executable instructions.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, so that the ATCF node is operable to perform the actions disclosed above.
  • This S-CSCF node is configured to receive, from a selected SCC-AS node via a receiver of the S-CSCF node, an access transfer information that comprises an SCC-AS identifier, which identifies the selected SCC-AS, and a UE identifier, which identifies a UE, and transmit, toward an ATCF node via a transmitter of the S-CSCF node, the received access transfer information with the received SCC-AS identifier and the received UE identifier.
  • This S-CSCF node is also configured to receive, from the ATCF node via the receiver, an initial call setup message along with an access transfer information that comprises an SCC-AS identifier and a UE identifier, and transmit, toward the selected SCC-AS via the transmitter, the received initial call setup message with the received SCC-AS identifier.
  • the SCC-AS identifier may correspond to an ATU-STI of the SCC-AS.
  • the UE identifier may correspond to a C-MSISDN.
  • the initial call setup message may correspond to a SIP Invite message.
  • the S-CSCF node may be configured to store a plurality of UE identifiers respectively associated with the plurality of SCC-AS identifiers and, where this is the case, the received initial call setup message may be transmitted along with the stored UE identifier.
  • receiving the access transfer information may be responsive to, and this S-CSCF node may further be configured to receive, via the receiver of the S-CSCF node, a SIP Register message originated from a UE; select an available SCC-AS; and transmit, toward the selected SCC-AS via the transmitter of the S-CSCF node, the SIP Register message.
  • the S-CSCF node may comprise at least one processor, and at least one memory that stores processor-executable instructions.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, so that the S-CSCF node is operable to perform the actions disclosed above.
  • This SCC-AS node is configured to receive, from an S-CSCF node via a receiver, an initial call setup message along with an access transfer information that comprises an SCC-AS identifier and a UE identifier; this SCC-AS node is also configured to determine a mismatch between the received SCC-AS identifier and its own SCC-AS identifier, and transmit, toward the S-CSCF node via a transmitter, a new access transfer information that comprises the own SCC-AS identifier of the SCC-AS node.
  • the SCC-AS node may be configured to receive, from an S-CSCF node via the receiver, a SIP Register message; and transmit, toward the S- CSCF node via the transmitter, an access transfer information comprising an own SCC- AS identifier, which identifies the SCC-AS node, and a UE identifier, which identifies a UE.
  • the SCC-AS identifier may correspond to an ATU-STI of the SCC-AS node.
  • the UE identifier may correspond to a C- MSISDN.
  • the initial call setup message may correspond to a SIP Invite message.
  • the new access transfer information may also comprise the received UE identifier.
  • the SCC-AS node may be configured to store registration and/or call related data, e.g. C-MSISDN, for each UE served by the SCC-AS node.
  • the SCC-AS node may comprise at least one processor, and at least one memory that stores processor-executable instructions.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, so that the SCC-AS node is operable to perform the actions disclosed above.
  • the invention may be practised by one or more computer programs, in accordance with a seventh aspect of the invention, each computer program being loadable into an internal memory of a computer with a processor, and comprising executable code adapted to carry out the above method steps.
  • this executable code may be recorded in a carrier readable in the computer.
  • FIG. 1 represents a basic sequence of actions to perform an SRVCC-HO for UE-A originating calls, where the preferred SCC-AS is reachable, in accordance with an exemplary first embodiment.
  • FIG. 2 represents a basic sequence of actions to perform an SRVCC-HO for UE-A originating calls, where the preferred SCC-AS is not reachable, in accordance with an exemplary second embodiment.
  • FIG. 3 represents a basic sequence of actions to perform an SRVCC-HO for UE-A originating calls, where the preferred SCC-AS becomes reachable again, in accordance with an exemplary third embodiment.
  • FIG. 4 represents a basic sequence of actions to perform an SRVCC-HO for UE-A originating calls, where the preferred SCC-AS becomes reachable again, in accordance with an embodiment of the invention.
  • FIG. 5 shows a basic component structure of an ATCF node in accordance with an embodiment.
  • FIG. 6 shows a basic component structure of an S-CSCF node in accordance with an embodiment.
  • FIG. 7 shows a basic component structure of an SCC-AS node in accordance with an embodiment.
  • FIG. 8 illustrates an exemplary sequence of actions carried out by the ATCF node in accordance with one or more embodiments.
  • FIG. 9 illustrates an exemplary sequence of actions carried out by the S- CSCF node in accordance with one or more embodiments.
  • FIG. 10 illustrates an exemplary sequence of actions carried out by the SCC- AS node in accordance with one or more embodiments.
  • FIG. 11 shows a basic component structure of an ATCF node in accordance with another embodiment.
  • FIG. 12 shows a basic component structure of an S-CSCF node accordance with another embodiment.
  • FIG. 13 shows a basic component structure of an SCC-AS node accordance with another embodiment. DETAILED DESCRIPTION
  • embodiments of this method are useful to facilitate SRVCC- HOs for UE-A originated and terminating calls, and to ensure that an identifier of the SCC-AS, like e.g. the ATU-STI, stored at the ATCF is always correct, i.e. it always identifies the SCC-AS used during a call setup. This allows that even though the S-CSCF may select a new SCC-AS, e.g. a preferred SCC-AS recovered from a failure, the call will be properly routed towards such new SCC-AS.
  • an identifier of the SCC-AS like e.g. the ATU-STI
  • Fig. 4 illustrates a sequence of actions that may be followed in accordance with embodiments of the invention.
  • the preferred SCC-AS i.e. SCC- AS 1
  • the S-CSCF 3 receives during step S-405 a SIP Register message originated from a UE-A 1.
  • the S-CSCF 3 may transmit the SIP Register message toward a preferred SCC-AS, i.e. SCC-AS 1 4, during step S-410 and determine that the preferred SCC-AS 1 is unreachable. Then, the S-CSCF selects a new available SCC-AS, i.e. SCC-AS2 5, and transmits during step S-415 the SIP Register message toward the selected SCC-AS2. The registration is completed by transmitting, from the SCC-AS2 toward the UE-A 1 though network nodes, a 200 OK message during step S-420.
  • the SCC-AS2 5 transmits during step S-425 toward the S-CSCF 3, and the latter transmits during step S-430 toward the ATCF 2, access transfer information comprising the ATU- STI of the SCC-AS2, i.e. the ATU-STI2, and the C-MSISDN of the UE-A.
  • the ATCF 2, or both S-CSCF 3 and ATCF 2 stores the received ATU-STI2. That is, the S-CSCF starts using SCC-AS2 for UE-A originating and terminating calls and the ATCF uses the ATU-STI2, as for the background third case commented above with reference to Fig. 3.
  • the SCC-ASl becomes reachable and running again, so that the S-CSCF 3 can start using the SCC-ASl 4 for a next initial call setup.
  • the initial call setup message e.g. SIP Invite message
  • the ATCF 2 is received at the ATCF 2 during step S-440 and transmitted during step S-445 from the ATCF 2 toward the S-CSCF 3 along with the access transfer information comprising the ATU-STI2 of the SCC-AS2 5, which was stored at the ATCF 2, and the C-MSISDN.
  • the initial call setup message received from the ATCF with the ATU-STI2 of the SCC-AS2 5 and the C-MSISDN, is progressed during step S-450 from the S- CSCF 3 toward the SCC-ASl 4 and, from the SCC-ASl, the initial call setup message may be progressed during step S-455 toward a terminating UE-B, if this is the case.
  • a corresponding acknowledge e.g. a SIP 200 OK, is returned back through the entities involved during step S-460.
  • the SCC-ASl 4 determines during step S-465 a mismatch between the received ATU-STI2 and its own ATU-STI, which in this exemplary embodiment is ATU-STIl . Then, the SCC-ASl 4 transmits during step S-470 toward the S-CSCF 3, and the latter transmits during step S-475 toward the ATCF 2, a new access transfer information now comprising the ATU-STI of the SCC-ASl 4, i.e. the ATU-STIl, and the C-MSISDN.
  • the ATCF 2, or both ATCF 2 and S-CSCF 3 stores the received ATU-STIl and C-MSISDN.
  • Fig. 4 illustrates, apart from communicating during steps S-495 and S-496 with a terminating UE-B, if this is the case, a corresponding successful acknowledge, i.e. a SIP 200 OK, is returned back during step S-497, from the SCC-AS 1 4 through the entities involved, and the SRVCC-HO is considered successful.
  • a corresponding successful acknowledge i.e. a SIP 200 OK
  • a network node implementing the ATCF may further be referred to as an ATCF.
  • a Proxy Call Session Control Function may play the same role as the ATCF.
  • a network node implementing an SCC-AS may further be referred to as an SCC-AS
  • a network node implementing a P-CSCF may further be referred to as a P-CSCF
  • a network node implementing an S-CSCF may further be referred to as an S-CSCF.
  • Embodiments of the above method i.e. method of handling IMS Restoration Procedures for service interruption of a SCC-AS, when executed at a network node implementing the ATCF, i.e. ATCF node, are disclosed in the following with reference to Fig. 8 and any ones of them may be combined in any manner without restrictions.
  • the above method comprises receiving S-810, at the ATCF node from a selected SCC-AS via a S-CSCF node, access transfer information with an SCC-AS identifier, such as e.g. an ATU-STI, which identifies the selected SCC- AS, and a UE identifier, such as e.g. a C-MSISDN, which identifies a UE, and storing S- 820 at the ATCF node the received SCC-AS identifier, e.g. ATU-STI, and optionally the received UE identifier, e.g. C-MSISDN.
  • SCC-AS identifier such as e.g. an ATU-STI
  • a UE identifier such as e.g. a C-MSISDN
  • the above method comprises receiving S-830 at the ATCF node an initial call setup message, e.g. a SIP Invite message, and transmitting S- 840, from the ATCF node toward the selected SCC-AS via the S-CSCF node, the received initial call setup message along with the stored SCC-AS identifier, e.g. ATU- STI, which identifies the selected SCC-AS, and optionally with the stored UE identifier, e.g. C-MSISDN, which identifies the UE.
  • the above method i.e.
  • the above method comprises receiving S-910, at the S- CSCF node, a SIP Register message originated from a UE, selecting S-920, at the S- CSCF node, an available SCC-AS and transmitting S-930, from the S-CSCF node toward the selected SCC-AS, the SIP Register message.
  • the above method comprises receiving S-940, at the S- CSCF node from a selected SCC-AS, an access transfer information that comprises an SCC-AS identifier, such as e.g. an ATU-STI, which identifies the selected SCC-AS, and a UE identifier, such as e.g.
  • a C-MSISDN which identifies a UE, and transmitting S- 950, from the S-CSCF node toward an ATCF node the received access transfer information with the received SCC-AS identifier, e.g. ATU-STI, and the received UE identifier, e.g. C-MSISDN.
  • the above method comprises receiving S-960, at the S- CSCF node from an ATCF node an initial call setup message, e.g. SIP Invite message, along with an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, and a UE identifier, e.g. C-MSISDN, and transmitting S-970, from the S- CSCF node toward the selected SCC-AS, the received initial call setup message with the received SCC-AS identifier, e.g. ATU-STI, and optionally the received UE identifier, e.g. C-MSISDN.
  • SCC-AS identifier e.g. ATU-STI
  • UE identifier e.g. C-MSISDN
  • Embodiments of the above method i.e. method of handling IMS Restoration Procedures for service interruption of a SCC-AS, when executed at a network node implementing the SCC-AS, i.e. SCC-AS node, are disclosed in the following with reference to Fig. 10 and any ones of them may be combined in any manner without restrictions.
  • the above method comprises receiving S-1030, at the SCC-AS node from an S-CSCF node, an initial call setup message, e.g. SIP Invite message, along with an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, and a UE identifier, e.g. C-MSISDN, determining S-1040, at the SCC- AS node, a mismatch between the received SCC-AS identifier, e.g. received ATU-STI, and its own SCC-AS identifier, e.g.
  • an initial call setup message e.g. SIP Invite message
  • an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, and a UE identifier, e.g. C-MSISDN
  • S-1040 at the SCC- AS node, a mismatch between the received SCC-AS identifier, e.g. received ATU-STI, and its own SCC-
  • a new access transfer information that comprises the own SCC-AS identifier, e.g. own ATU-STI, of the SCC-AS node and optionally the received UE identifier, e.g. C-MSISDN.
  • ATCF node implementing an ATCF
  • Embodiments of this ATCF node are illustrated in Fig. 5 and Fig. 11.
  • the ATCF node 2 is configured to receive, from a selected SCC-AS 4 via an S-CSCF node 3 and via a receiver 530 of the ATCF node, access transfer information with an SCC-AS identifier, which identifies a selected SCC-AS, and a UE identifier, which identifies a UE; the ATCF node 2 is configured to store a plurality of SCC-AS identifiers identifying a respective plurality of SCC-ASs; and the ATCF node 2 is configured to receive, via the receiver 530, an initial call setup message, and transmit, toward the selected SCC-AS 4 via a transmitter 540 of the ATCF node and via the S-CSCF node 3, the received initial call setup message along with the stored SCC-AS identifier, which identifies the selected SCC-AS.
  • the ATCF node 2 may comprise, as shown in Fig. 5 and Fig. 11, an SCC-AS handler 524 configured to receive, from a selected SCC-AS 4 via S-CSCF node 3 and via receiver 530 of the ATCF node 2, access transfer information with an SCC-AS identifier, such as e.g. an ATU-STI, which identifies a selected SCC-AS, and a UE identifier, such as e.g. a C-MSISDN, which identifies a UE; a data memory configured to store a plurality of SCC-AS identifiers, e.g.
  • an SCC-AS handler 524 configured to receive, from a selected SCC-AS 4 via S-CSCF node 3 and via receiver 530 of the ATCF node 2, access transfer information with an SCC-AS identifier, such as e.g. an ATU-STI, which identifies a selected SCC-AS, and a UE identifier, such as
  • ATU-STIs identifying a respective plurality of SCC-ASs and to optionally store a plurality of UE identifiers, e.g. C-MSISDNs, respectively associated with the plurality of SCC-AS identifiers; and a call handler 527 configured to receive, via the receiver 530, an initial call setup message, e.g. a SIP Invite message, and transmit, toward the selected SCC-AS 4 via transmitter 540 of the ATCF node 2 and via the S-CSCF node 3, the received initial call setup message along with the stored SCC-AS identifier, e.g. ATU- STI, which identifies the selected SCC-AS, and the UE identifier, e.g.
  • an initial call setup message e.g. a SIP Invite message
  • the ATCF node 2 may comprise a data memory 518 configured to store the plurality of SCC-AS identifiers and to optionally store the plurality of UE identifiers; whereas in the embodiment illustrated in Fig. 11, any one of the SCC-AS handler 524 and the call handler 527 may be configured to store the plurality of SCC-AS identifiers and to optionally store the plurality of UE identifiers.
  • the ATCF node 2 may comprise, as shown in Fig. 5, at least one processor 520, and at least one memory 510 that stores processor-executable instructions 514.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, so that the ATCF node 2 is operable to perform the actions disclosed above.
  • the ATCF node 2 may comprise at least one processor 520 and at least one memory 510, both in communication with each other, with the SCC-AS handler 524, the call handler 527, the receiver 530 and the transmitter 540, and with other elements or units of the ATCF node 2.
  • the at least one memory 510 may comprise volatile and/or non- volatile memory.
  • the at least one memory 510 may have a computer program 514 and data 518 stored therein.
  • the computer program 514 may be loaded in the at least one memory 510 from a computer program product 550, such as any non-transitory computer readable medium, in which the computer program is stored.
  • the data 518 may comprise a plurality of SCC-AS identifiers, e.g. ATU-STIs, identifying a respective plurality of SCC-ASs and optionally a plurality of UE identifiers, e.g. C-MSISDNs, respectively associated with the plurality of SCC-AS identifiers.
  • the at least one processor 520 may be configured to carry out the functions of the SCC-AS handler 524 and the call handler 527.
  • S-CSCF node e.g. ATU-STIs
  • UE identifiers e.g. C-MSISDNs
  • the S-CSCF node 3 is configured to receive, from a selected SCC-AS node 4 via receiver 630 of the S-CSCF node 3, an access transfer information that comprises an SCC-AS identifier, which identifies the selected SCC-AS, and a UE identifier, which identifies a UE, and transmit, toward an ATCF node 2 via transmitter 640 of the S-CSCF node 3, the received access transfer information with the received SCC-AS identifier and the received UE identifier.
  • This S-CSCF node 3 is also configured to receive, from the ATCF node 2 via the receiver 630, an initial call setup message along with an access transfer information that comprises an SCC-AS identifier and a UE identifier, and transmit, toward the selected SCC-AS 4 via the transmitter 640, the received initial call setup message with the received SCC-AS identifier.
  • the S-CSCF node 3 may comprise, as shown in Fig. 6 and Fig. 12, an SCC-AS handler 627 configured to receive, from the selected SCC-AS node 4 via the receiver 630 of the S-CSCF node 3, an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, which identifies the selected SCC-AS 4 and a UE identifier, e.g. C-MSISDN, which identifies a UE, and transmit, toward an ATCF node 2 via the transmitter 640 of the S-CSCF node 3, the received access transfer information with the received SCC-AS identifier, e.g. ATU-STI, and the received UE identifier, e.g. C-MSISDN.
  • SCC-AS identifier e.g. ATU-STI
  • C-MSISDN which identifies a UE
  • the S-CSCF node 3 may also comprise, as shown in Fig. 6 and Fig. 12, a call handler 624 configured to receive, from an ATCF node 2 via the receiver 630, an initial call setup message, e.g. SIP Invite message, along with an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, and a UE identifier, e.g. C-MSISDN, and transmit, toward the selected SCC-AS 4 via the transmitter 640, the received initial call setup message with the received SCC-AS identifier, e.g. ATU-STI, and optionally the received UE identifier, e.g. C-MSISDN.
  • an initial call setup message e.g. SIP Invite message
  • an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, and a UE identifier, e.g. C-MSISDN
  • the received initial call setup message with the received SCC-AS
  • the call handler 624 shown in Fig. 6 and Fig. 12 may be configured to receive, via the receiver 630, a SIP Register message originated from a UE-A 1, select an available SCC-AS and transmit, toward the selected SCC-AS 4 via transmitter 640, the SIP Register message;
  • the S-CSCF node 3 may also comprise a data memory 618 configured to store a plurality of SCC-AS identifiers, e.g. ATU-STIs, identifying a respective plurality of SCC-ASs and to optionally store a plurality of UE identifiers, e.g. C-MSISDNs, respectively associated with the plurality of SCC-AS identifiers; whereas in the embodiment illustrated in Fig. 12, any one of the SCC-AS handler 627 and the call handler 624 may be configured to store the plurality of SCC-AS identifiers and to optionally store the plurality of UE identifiers.
  • SCC-AS identifiers e.g. ATU-STIs
  • UE identifiers e.g. C-MSISDNs
  • the S-CSCF node 3 may comprise, as shown in Fig. 6, at least one processor 620, and at least one memory 610 that stores processor-executable instructions 614.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, so that the S-CSCF node 3 is operable to perform the actions disclosed above.
  • the S-CSCF node 3 may comprise at least one processor 620 and at least one memory 610, both in communication with each other, with the call handler 624, the SCC-AS handler 627, the receiver 630 and the transmitter 640, and with other elements or units of the S-CSCF node 3.
  • the at least one memory 610 may comprise volatile and/or non- volatile memory.
  • the at least one memory 610 may have a computer program 614 and data 618 stored therein.
  • the computer program 614 may be loaded in the at least one memory 610 from a computer program product 650, such as any non-transitory computer readable medium, in which the computer program is stored.
  • the data 618 may comprise a plurality of SCC-AS identifiers, e.g. ATU-STIs, identifying a respective plurality of SCC-ASs and optionally a plurality of UE identifiers, e.g. C-MSISDNs, respectively associated with the plurality of SCC-AS identifiers.
  • the at least one processor 620 may be configured to carry out the functions of the call handler 624 and the SCC-AS handler 627.
  • SCC-AS node Participating in the above methods and exemplary embodiments of IMS Restoration Procedures for service interruption of a SCC-AS there is also provided a network node implementing an SCC-AS, hereinafter SCC-AS node.
  • SCC-AS node Embodiments of this SCC-AS node are illustrated in Fig. 7 and Fig. 13.
  • the SCC-AS node 4 is configured to receive, from an S-CSCF node 3 via a receiver 730 of the SCC-AS node, an initial call setup message along with an access transfer information that comprises an SCC-AS identifier and a UE identifier; this SCC-AS node 4 is also configured to determine a mismatch between the received SCC-AS identifier and its own SCC-AS identifier, and transmit, toward the S-CSCF node 3 via a transmitter 740 of the SCC-AS node, a new access transfer information that comprises the own SCC-AS identifier of the SCC-AS node.
  • the SCC-AS node 4 may comprise, as shown in Fig. 7 and Fig. 13, a call handler 724 configured to receive, from an S-CSCF node 3 via receiver 730 of the SCC-AS node, an initial call setup message, e.g. SIP Invite message, along with an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, and a UE identifier, e.g. C-MSISDN, and an SCC-AS handler 727 configured to determine a mismatch between the received SCC-AS identifier, e.g. ATU-STI, and its own SCC-AS identifier, e.g.
  • an initial call setup message e.g. SIP Invite message
  • an access transfer information that comprises an SCC-AS identifier, e.g. ATU-STI, and a UE identifier, e.g. C-MSISDN
  • SCC-AS handler 727 configured to determine a mismatch between the
  • a new access transfer information that comprises the own SCC-AS identifier, e.g. own ATU-STI, of the SCC- AS node 4 and, optionally, the received UE identifier, e.g. C-MSISDN.
  • the call handler 724 may be configured to receive, from an S-CSCF node 3 via the receiver 730, a SIP Register message; and the SCC-AS handler 727 may be configured to transmit, toward the S-CSCF node 3 via the transmitter 740, an access transfer information comprising an own SCC-AS identifier, e.g. own ATU-STI, identifying the SCC-AS node 4 and a UE identifier, e.g. C- MSISDN, identifying a UE.
  • an own SCC-AS identifier e.g. own ATU-STI
  • identifying the SCC-AS node 4 e.g. C- MSISDN
  • the SCC-AS node 4 may also comprise a data memory 718 configured to store registration and/or call related data, e.g. C-MSISDN, for each UE served by the SCC-AS node; whereas in the embodiment illustrated in Fig. 13, any one of the SCC-AS handler 727 and the call handler 724 may be configured to store the registration and/or call related data, e.g. C-MSISDN, for each UE served by the SCC-AS node.
  • registration and/or call related data e.g. C-MSISDN
  • the SCC-AS node 4 may comprise, as shown in Fig. 7, at least one processor 720, and at least one memory 710 that stores processor-executable instructions 714.
  • the at least one processor interfaces with the at least one memory to execute the processor- executable instructions, so that the SCC-AS node 4 is operable to perform the actions disclosed above.
  • the SCC-AS node 4 may comprise at least one processor 720 and at least one memory 710, both in communication with each other, with the call handler 724, the SCC-AS handler 727, the receiver 730 and the transmitter 740, and with other elements or units of the SCC-AS node 4.
  • the at least one memory 710 may comprise volatile and/or non- volatile memory.
  • the at least one memory 710 may have a computer program 714 and data 718 stored therein.
  • the computer program 714 may be loaded in the at least one memory 710 from a computer program product 750, such as any non-transitory computer readable medium, in which the computer program is stored.
  • the data 718 may comprise registration and/or call related data, e.g. C-MSISDN, for each UE served by the SCC- AS node.
  • the at least one processor 720 may be configured to carry out the functions of the call handler 724 and the SCC-AS handler 727.
  • a terminating SCC- AS node may transmit its own SCC-AS identifier, e.g. own ATU-STI, along with an outgoing call setup message, e.g. SIP Invite message, toward a terminating ATCF node, and the terminating ATCF node may store the SCC-AS identifier, e.g. ATU-STI, received with the incoming call setup message, e.g. SIP Invite message.
  • SCC-AS identifier e.g. own ATU-STI
  • the invention may also be practised by one or more computer programs, each one loadable into an internal memory of a computer with input and output units as well as with a processor.
  • This computer program comprises to this end executable code adapted to carry out the above method steps when running in the computer.
  • the executable code may be recorded in a carrier readable means in a computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention aborde le problème de la resélection d'un serveur d'application de continuité d'appel de service préféré (SCC-AS) après que ce SCC-AS préféré est à nouveau accessible après une défaillance. Pour résoudre ce problème, la présente invention propose un nœud de fonction de commande de transfert d'accès (ATCF) recevant et stockant un identifiant SCC-AS, qui identifie un SCC-AS sélectionné, qui n'est pas le SCC-AS préféré, et transmet un autre message d'établissement d'appel initial reçu vers le SCC-AS sélectionné par l'intermédiaire d'une fonction de commande de session d'appel de desserte (S-CSCF) conjointement avec l'identifiant SCC-AS stocké. La S-CSCF constate que le SCC-AS préféré est à nouveau accessible et transmet le message d'établissement d'appel initial reçu avec l'identifiant SCC-AS reçu vers le SCC-AS préféré. Le SCC-AS préféré détermine que l'identifiant SCC-AS reçu n'est pas concordant avec son propre identifiant SCC-AS et met à jour le nœud ATCF par l'intermédiaire du nœud S-CSCF avec son propre identifiant SCC-AS qui identifie le SCC-AS préféré.
PCT/EP2017/080124 2016-12-05 2017-11-22 Continuité de service après un repli de serveur d'application Ceased WO2018104060A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662430080P 2016-12-05 2016-12-05
US62/430,080 2016-12-05

Publications (1)

Publication Number Publication Date
WO2018104060A1 true WO2018104060A1 (fr) 2018-06-14

Family

ID=60480303

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/080124 Ceased WO2018104060A1 (fr) 2016-12-05 2017-11-22 Continuité de service après un repli de serveur d'application

Country Status (1)

Country Link
WO (1) WO2018104060A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2020004517A1 (ja) * 2018-06-27 2021-02-25 Ｍｅｉｊｉ Ｓｅｉｋａファルマ株式会社 ベンゾオキサゾール誘導体の結晶
CN116192641A (zh) * 2022-12-23 2023-05-30 中国联合网络通信集团有限公司 增值业务放通方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013156061A1 (fr) * 2012-04-17 2013-10-24 Telefonaktiebolaget L M Ericsson (Publ) Traitement de défaillance au sein d'un réseau mettant en œuvre une srvcc
WO2016101791A1 (fr) * 2014-12-22 2016-06-30 华为技术有限公司 Procédé, dispositif et système de traitement de défaillance
US20160353331A1 (en) * 2015-06-01 2016-12-01 Mitel Networks Corporation Systems and methods for single radio voice call continuity in a multi-line, multi-device service environment in a communications network
US20160352855A1 (en) * 2015-06-01 2016-12-01 Mitel Networks Corporation Systems and methods for multi-line, multi-device service in a communications network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013156061A1 (fr) * 2012-04-17 2013-10-24 Telefonaktiebolaget L M Ericsson (Publ) Traitement de défaillance au sein d'un réseau mettant en œuvre une srvcc
WO2016101791A1 (fr) * 2014-12-22 2016-06-30 华为技术有限公司 Procédé, dispositif et système de traitement de défaillance
US20170289863A1 (en) * 2014-12-22 2017-10-05 Huawei Technologies Co., Ltd. Troubleshooting method, apparatus, and system
US20160353331A1 (en) * 2015-06-01 2016-12-01 Mitel Networks Corporation Systems and methods for single radio voice call continuity in a multi-line, multi-device service environment in a communications network
US20160352855A1 (en) * 2015-06-01 2016-12-01 Mitel Networks Corporation Systems and methods for multi-line, multi-device service in a communications network

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2020004517A1 (ja) * 2018-06-27 2021-02-25 Ｍｅｉｊｉ Ｓｅｉｋａファルマ株式会社 ベンゾオキサゾール誘導体の結晶
CN116192641A (zh) * 2022-12-23 2023-05-30 中国联合网络通信集团有限公司 增值业务放通方法、装置、设备及存储介质

Similar Documents

Publication Publication Date Title
EP2342909B1 (fr) Corrélation de sessions en cas de transfert de session dans un domaine ims
US9467907B2 (en) Handover of user-equipment (UE) undetected emergency calls
US9338625B2 (en) Geographically redundant and multiple EATF nodes
US9749981B2 (en) IMS system and method for transmitting a reregister request to an S-CSCF
EP2061212A1 (fr) Procédé, appareil et produit de programme informatique pour combiner des sessions de communication dans un IMS
US8634381B2 (en) Session transfer between different access network types
US9509811B2 (en) Methods and apparatus for resolving data inconsistencies in an IMS network
US20150282242A1 (en) Methods and apparatus for processing an ims session
TWI597992B (zh) 用於緊急回撥或點選即撥連線之單無線電語音通話連續技術
CN101742589B (zh) 一种多媒体会话转移的方法、用户设备及服务器
CN103703737A (zh) 用于支持ims服务连续性的实现的方法和设备
US9351269B2 (en) Method and system for processing service continuity
US20150365980A1 (en) Method and Device for Sending Identifier Information or Call Transfer Request
EP2577931B1 (fr) Préservation d'un état de semi-communication dans des sessions de services centralisés d'ims
CN109804609A (zh) 通信会话请求的后到先服务处理
US9392032B2 (en) Session transfer method, device and system
US20180337961A1 (en) Synchronization of UE Capability and Registration Status for SIP-Based Application Services
WO2018104060A1 (fr) Continuité de service après un repli de serveur d'application
EP3585096A1 (fr) Procédé de traitement de réservation de ressources pour commutation srvcc, et dispositif de fonction de commutation d'accès
KR101173836B1 (ko) Ｉｍｓ망에서 ｓ-ｃｓｃｆ 장애 복구 후 착신 및 발신 호 처리 방법 및 그 시스템
EP3878147B1 (fr) Procédé, appareil et programme informatique
CN105763524A (zh) Ip多媒体子系统中的注册方法、装置和系统
CN104936208B (zh) SRVCC的Refer业务处理方法、装置及系统
US10721655B2 (en) Method of processing emergency call transfer requests
JP2015177489A (ja) 情報通信制御システム及び情報通信制御方法、ならびに、この情報通信制御システムにおける複製装置

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

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

Country of ref document: EP

Kind code of ref document: A1