WO2008053013A1 - Déplacement entre des domaines de communications - Google Patents

Déplacement entre des domaines de communications Download PDF

Info

Publication number
WO2008053013A1
WO2008053013A1 PCT/EP2007/061741 EP2007061741W WO2008053013A1 WO 2008053013 A1 WO2008053013 A1 WO 2008053013A1 EP 2007061741 W EP2007061741 W EP 2007061741W WO 2008053013 A1 WO2008053013 A1 WO 2008053013A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain transfer
message
session
transfer request
domain
Prior art date
Application number
PCT/EP2007/061741
Other languages
English (en)
Inventor
Kazuhiko Nakada
Bo ÅSTRÖM
Ralf Keller
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2008053013A1 publication Critical patent/WO2008053013A1/fr

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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols

Definitions

  • the present invention relates to the field of moving between communications networks, and in particular to moving between an IMS network and a Circuit Switched network.
  • IP Multimedia services provide a dynamic combination of voice, video, messaging, data, etc. within the same session.
  • the number of services offered to the end users will grow, and the inter-personal communication experience will be enriched. This will lead to a new generation of personalised, rich multimedia communication services.
  • IMS IP Multimedia Subsystem
  • 3 GPP Third Generation Partnership Project
  • IMS IP Multimedia Subsystem
  • 3 GPP Third Generation Partnership Project
  • IMS provides key features to enrich the end-user person-to-person communication experience through the use of standardised IMS Service Enablers, which facilitate new rich person-to-person (client- to-client) communication services as well as person-to-content (client-to-server) services over IP-based networks.
  • the IMS makes use of the Session Initiation Protocol (SIP) to set up and control calls or sessions between user terminals (or user terminals and application servers).
  • SIP Session Initiation Protocol
  • SDP Session Description Protocol
  • SIP was created as a user-to-user protocol
  • IMS allows operators and service providers to control user access to services and to charge users accordingly.
  • VCC Voice Call Continuity
  • CS Circuit Switched
  • IMS IP Multimedia Service Control
  • B2BUA Back to Back User Agent
  • Figure 1 illustrates schematically a signalling and media path change example when a VCC user 101 moves from a CS domain 102 to an IMS domain 103.
  • VCC Application When a VCC Application receives an INVITE message from a new IMS domain into which a user has just moved, the VCC Application needs to identify that this is an INVITE message requesting Domain Transfer.
  • a VCC Domain Transfer URI (VDI) is populated in a Request-URI in an INVITE message to indicate that Domain Transfer shall be performed.
  • VDI VCC Domain Transfer URI
  • the VCC Application Server 104 On receipt of an INVITE message with VDI, the VCC Application Server 104 sends a re-INVITE or UPDATE message towards the remote end 105 to inform that the access leg bearer address has changed.
  • VCC Voice Call Control
  • VDN VCC Domain Transfer Number
  • a VDN is configured at initial VCC service subscription.
  • a VDN is typically a number common to all VCC subscribers, and cannot be used to establish a call to one specific subscriber. The common number must first be translated into a user specific VDN. Customized Application for Mobile network Enhanced Logic (CAMEL) is used for this translation.
  • the user-specific VDN is used as a Public Service Identity (PSI) in a SIP Request-URI, i.e.
  • PSI Public Service Identity
  • DTF PSI Domain Transfer Function Public Service Identity
  • MGCF Media Gateway Control Function
  • the Public User ID can be used to identify the single on-going call anchored in the VCC Application Server 104.
  • a mechanism is needed in which the UE 101 can use the VDN and VDI to uniquely identify the session to be transferred between domains by the ICS-VCC or GSC application server.
  • a method of operating a node in a communications network comprises receiving a message relating to a client terminal session, and generating a domain transfer request indicator and a domain transfer telecommunication number.
  • the generated domain transfer request indicator and domain transfer telecommunication number are sent to the client terminal.
  • the domain transfer request indicator is a Voice Call Continuity Domain Transfer Uniform Resource Indicator
  • the domain transfer number is a Voice Call Continuity Domain Transfer Number.
  • the method optionally comprises sending the domain transfer request indicator and the domain transfer number in a message selected from one of a session establishment message, a Session Initiation Protocol INFO message, a Session Initiation Protocol NOTIFY message, and a Session Initiation Protocol MESSAGE message.
  • the method comprises generating the domain transfer request indicator and the domain transfer telecommunication number in response to receipt of a session establishment message. This allows the domain transfer request indicator and domain transfer telecommunications number to be used in the initial session after registration, and also in subsequent sessions.
  • the method comprises generating the domain transfer request indicator and the domain transfer telecommunication number in response to receipt of a registration message. This allows the domain transfer request indicator and domain transfer telecommunications number to be used only in the initial session after registration.
  • a plurality of generated domain transfer request indicators and domain transfer telecommunication numbers are sent to the client terminal. This allows the client terminal to receive domain transfer request indicators and domain transfer telecommunication numbers for all ongoing activities in a single message.
  • a node in a communications network comprises means for receiving a message relating to a client terminal registration or session. Means are provided for generating a domain transfer request indicator and a domain transfer telecommunication number, and means are also provided for sending to the client terminal the generated domain transfer request and domain transfer telecommunication number.
  • the domain transfer request indicator is a Voice Call Continuity Domain Transfer Uniform Resource Indicator
  • the domain transfer number is a Voice Call Continuity Domain Transfer Number
  • the node optionally comprises means to send the domain transfer request indicator and the domain transfer number in a message selected from one of a session establishment message, a Session Initiation Protocol INFO message, a Session Initiation Protocol NOTIFY message, and a Session Initiation Protocol MESSAGE message.
  • the domain transfer request indicator and the domain transfer telecommunication number are optionally generated in response to receipt of a session establishment message, which allows the domain transfer request indicator and the domain transfer telecommunication number to be used in the initial session after registration, and also in subsequent sessions.
  • the domain transfer request indicator and the domain transfer telecommunication number are generated in response to receipt of a registration message, which allows the domain transfer request indicator and the domain transfer telecommunication number to be used only in the initial session after registration.
  • means are provided for sending a plurality of domain transfer request indicators and domain transfer telecommunication numbers to the client terminal, which allows the client terminal to receive domain transfer request indicators and domain transfer telecommunication numbers for all ongoing activities in a single message.
  • a client terminal for use in a telecommunications network.
  • the client terminal comprises means to receive a domain transfer request indicator and a domain transfer telecommunication number, and means to subsequently use the received domain transfer request indicator and domain transfer telecommunication number to initiate a domain transfer.
  • Figure 1 illustrates schematically in a block diagram the signalling when a VCC user moves from a CS network to an IMS network
  • Figure 2 illustrates schematically in a block diagram the signalling when a VCC user moves from an IMS network to a CS network;
  • Figure 3 illustrates schematically in a block diagram the signalling when a VCC user moves from one IP-CAN network to another IP-CAN network;
  • Figure 4 illustrates schematically in a block diagram the signalling when an ICS-VCC user moves from a CS network to an IMS network via an ICS Terminal Adapter
  • Figure 5 illustrates schematically in a block diagram the signalling when an ICS-VCC user moves from an IMS network to a CS network via an ICS Terminal Adapter
  • Figure 6 illustrates schematically the signalling required to generate and deliver VDI/VDN using a session establishment message method where an IMS session is the source access leg;
  • Figure 7 illustrates schematically the signalling required to generate and VDI/VDN using an originating session establishment message method where an ICS session is the source access leg;
  • Figure 8 illustrates schematically the signalling required to generate and deliver VDI/VDN using a terminating session establishment message method where an ICS session is the source access leg;
  • Figure 9 illustrates schematically the signalling required to generate and deliver VDI/VDN using a SIP INFO message method where an IMS session is the source access leg;
  • Figure 10 illustrates schematically the signalling required to generate and deliver VDI/VDN using a SIP INFO message method where an ICS session is the source access leg;
  • Figure 11 illustrates schematically the signalling required to generate and deliver VDI/VDN using a SIP NOTIFY message method where an IMS session is the source access leg;
  • Figure 12 illustrates schematically the signalling required to generate and deliver VDI/VDN using a SIP NOTIFY message method where an ICS session is the source access leg
  • Figure 13 illustrates schematically the signalling required to generate and deliver VDI/VDN using a SIP MESSAGE message method where an IMS session is the source access leg;
  • Figure 14 illustrates schematically the signalling required to generate and deliver VDI/VDN using a SIP MESSAGE message method where an ICS session is the source access leg;
  • Figure 15 illustrates schematically the signalling required to generate and deliver VDI/VDN at registration where an IMS session is the source access leg;
  • Figure 16 illustrates schematically the signalling required to generate and deliver VDI/VDN at registration where an ICS session is the source access leg;
  • Figure 17 illustrates schematically in a block diagram an Application Server according to an embodiment of the invention.
  • Figure 18 illustrates schematically in a block diagram User Equipment according to an embodiment of the invention.
  • GSC Generic Session Continuity
  • IP-CAN IP Connectivity Access Network
  • GSC is an application that is typically implemented as an add-on to a VCC application, used to transfer any Communication Service (CoSe) between 2 IP-CANs 302, 303 and is implemented in an ISC connected IMS Application server 304.
  • a CoSe session is always anchored at the GSC application server, which acts as 3pcc B2BUA and updates the media address of a GSC user access leg towards the remote end when UE 301 moves from one IP-CAN 302 to another IP-CAN 303.
  • the example illustrated in Figure 3 shows the use of a VDI mechanism in a GSC application.
  • a particular Domain Transfer request is identified by a VDI, and is transferred in a Request-URI in an INVITE message 305 from the new IP-CAN 303.
  • VCC R7 assumed only one on-going voice session
  • GSC extends this assumption to multiple numbers of any CoSe sessions.
  • the GSC application needs the information to identify the corresponding source session to be transferred to a new IP- CAN 303 when it receives an INVITE message with a VDI.
  • a GSC user's Public User ID is enough to identify a GSC user, but not enough to identify the concerned session if the GSC user has ongoing multiple sessions.
  • the multiple sessions can be the same CoSe towards multiple remote users or multiple CoSe sessions to the same remote user or those combinations.
  • IMS Centralized Services is a work item in 3GPP ReI 8 that makes it possible to offer IMS services over many types of access networks, such as a CS network.
  • Service Engine (service implementation) resides in an IMS network, and the CS network is merely used as an access network to the services in the IMS network.
  • ICS also extends the VCC solution developed in 3GPP ReI 7. VDIs/VDNs can be used for ICS voice call continuity.
  • ICS IMS Centralised Service
  • IA IMS Adapter (which is a CS Terminal Adapter towards IMS)) 401 and the ICS protocol carried over USSD dialogues or any other suitable bearers between a UE 301 and the IA 401.
  • the IA 401 emulates a Proxy Call Session Control Function (P-CSCF) towards the Serving Call Session Control Function (S-CSCF) 402.
  • P-CSCF Proxy Call Session Control Function
  • S-CSCF Serving Call Session Control Function
  • MP Media Proxy
  • ICS-VCC can be implemented as an ISC connected application to transfer the voice session between an ICS CS access network and a PS access network, implemented in an IMS Application Server and typically as an extension to a VCC/GSC application.
  • ICS-VCC also acts as 3pcc B2BUA and identifies the session transfer request by VDI in an INVITE message from a new access leg.
  • ICS-VCC extends this assumption to multiple numbers of voice sessions and allows multiparty call session continuity.
  • the ICS-VCC Application Server 304 therefore needs additional information to identify the concerned existing session to be transferred to an IMS network when it receives an INVITE message 406 with a VDI.
  • the Public User ID of ICS-VCC user is not sufficient in this case since multiple sessions may be subject to domain transfer.
  • a Dynamic VDI/VDN is generated on a per session basis. Session herein is assumed to mean a dialogue as specified in RFC 3261 and is identified by a "from” tag, a "to” tag and a call ID.
  • Dynamic VDI has the following characteristics: • The VDI is a SIP URI;
  • the VDI can be recognised as a Domain Transfer request in a GSC or ICS-VCC application;
  • a Dynamic VDI must identify a particular source session for a user with a Public User ID in a GSC or in an ICS-VCC Application;
  • Dynamic VDI may be reallocated after the concerned session has been terminated (i.e. Dynamic VDI has a life time until the session expires).
  • Dynamic VDN (and DTF PSI) has the following characteristics:
  • the VDN is an E.164 number that is dialled from a UE 301, and which must be assigned per user and per source session to be transferred.
  • the VDN is translated by an IA 401 into a DTF PSI.
  • VDN and DTF PSI have a one-to-one relationship in an ICS-VCC Application Server 303.
  • the VDN (and corresponding DTF PSI) can be recognised as a Domain Transfer request in the ICS-VCC application;
  • a Dynamic VDN (and corresponding DTF PSI) identifies a particular source session of a user with a particular Public User ID in the ICS-VCC Application. (Note - DTF PSI is also dynamically allocated to identify the target leg in 3GPP Rel7, but the dynamic nature introduced here is to identify the particular source session) ;
  • Dynamic VDN (and corresponding DTF PSI) value is reallocated after the concerned session is terminated (i.e. Dynamic VDN (and corresponding DTF PSI) has a life time until the session expires).
  • a dynamic VDI/VDN is generated and delivered at session establishment.
  • VDIs/VDIs may be delivered to a UE 301 within the established session or outside the session. This method is applicable to the first session after registration as well as subsequent sessions after registration.
  • the VDI/VDN is always generated at each session establishment, and this is also the case for the target access leg, i.e. the VDI/VDN generated at source access leg is used for handover from a source access leg to a target access leg, but not re-used for subsequent handover from the target access leg to a further new access leg.
  • VDI/VDN delivery at session establishment There are several alternative methods for VDI/VDN delivery at session establishment, including the following:
  • a VDI/VDN may be delivered and generated using session establishment signalling.
  • a 200 OK message 601 delivers VDI/VDN to User Equipment (UE) 301
  • UE User Equipment
  • an ACK message 602 delivers the VDI/VDN to UE 301.
  • the VDI/VDN information can be included in the SIP body of either the 200 OK message or the ACK message using an XML body, or a new SIP Information Element.
  • a 200 OK message is mapped to an ICS call initiation result message 701 in the ICS protocol between the UE 301 and the IA 401, as shown in Figure 7.
  • the ACK message is mapped to an ICS incoming call result 801, as shown in Figure 8, in order to deliver the VDI/VDN to the UE 301.
  • the VDI/VDN may be generated and delivered to a UE 301 using a SIP INFO message 901, as illustrated in Figure 9.
  • INFO is a general mechanism to carry application level information during the session.
  • AS Application Server
  • the VDI/VDN information can be included using an XML body, or a new SIP Information Element. If the source access leg is an ICS leg, then the INFO message is mapped to ICS info 1001 in an IA 401 in order to deliver the VDI/VDN to the UE 301, as shown in Figure 10.
  • the VDI/VDN is generated and delivered using an event notification mechanism and a SIP NOTIFY message, as illustrated in Figure 11.
  • the UE 301 acts as a SUBSCRIBER and the AS 304 acts as a NOTIFIER.
  • UE 301 is subscribed to a dialogue event package of its own and receives a notification when the session is established.
  • VDI/VDN information is included in a NOTIFY message 1101.
  • the VDI/VDN information can be included in SIP using an XML body, or a new SIP Information Element.
  • the NOTIFY message 1201 is mapped to an ICS notify 1202 in the IA 401 in order to deliver VDI/VDN, as illustrated in Figure 12.
  • a SIP MESSAGE message may be used by the UE 301 to request VDIs/VDNs, and by the network to deliver VDIs/VDNs to the UE 301.
  • the SIP MESSAGE transaction is not sent over an established SIP session, and the UE 301 therefore includes information that allows the VCC/GSC/ICS application to assign VDIs/VDNs appropriately.
  • Such information includes the calling party ID, the called party ID, and a "transaction reference" that is used end-to-end between the UE 301 and the VCC/GSC/ICS Application Server 304 (and therefore, must not be altered by intermediate nodes).
  • This information and the subsequent delivery of VDIs/VDNs may be sent as an XML body, or a new SIP Information Elements.
  • This solution also allows the UE 301 to request VDIs/VDNs for all ongoing activities in one SIP message transaction.
  • the UE 301 includes several "request components" inside the SIP MESSAGE message 1301 ; one for each session that is to be transferred.
  • the VCC/GSC/ICS Application Server 304 includes several "VDI/VDN components" in the reply 1302 back to the UE 301 .
  • the SIP MESSAGE message procedure must be mapped onto an ICS procedure, as shown in Figure 14.
  • VDI/VDN is generated and delivered to UE at registration.
  • the VDI/VDN is reserved for the coming initial session. This method is only applicable to identify the initial session after registration.
  • a third party registration mechanism is used to inform the AS 304 that registration has taken place.
  • a SIP MESSAGE message 1501 is used to deliver VDI/VDN towards the UE 301, as illustrated in Figure 15.
  • the VDI/VDN information can be included in the SIP message body using XML or new SIP Information Elements.
  • a MESSAGE message 1601 is mapped to an ICS VDI/VDN delivery message 1602in the IA in order to deliver the VDI/VDN to the UE 301, as illustrated in Figure 16.
  • the dynamic VDN/VDI delivery at registration can be combined with the delivery at session establishment as follows:
  • the UE receives a first VDI/VDN during registration. These are valid for the first session that is established by the UE 301.
  • the UE receives a new pair of VDI/VDN at subsequent session establishment. Unless otherwise indicated, the new pair is to be used for the next session (hence the UE 301 keeps a record of at least two pairs).
  • the application server 304 comprises a receiver 1701 for receiving a message, as described in the various embodiments above, relating to registration of the UE 301.
  • a processor 1702 is provided for generating a VDI/VDN.
  • a database 1703 may be provided for storing VDI/VDNs to ensure no collision with previously assigned VDI/VDNs.
  • a transmitter 1704 is provided to send the VDI/VDN to the UE 301.
  • the UE 301 comprises a receiver 1801 for receiving a VDI/VDN from the AS 304, and a processor 1802 and transmitter 1803 for subsequent use of the VDI/VDN when initiating a domain transfer.
  • the invention described herein provides for identification of simultaneous sessions for the same user (Public User Identity), and allows domain transfers to be carried out for all ongoing activities. It also provides dynamic allocation of user-specific VDI/VDN, per session allocation of user-specific VDI/VDN, and subsequent per session allocation of user-specific VDI/VDN.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil pour exploiter un nœud dans un réseau de communication. Le procédé comprend les opérations consistant à recevoir un message concernant une session de terminal client; générer un indicateur de requête de transfert de domaine et un numéro de télécommunication de transfert de domaine; et envoyer au terminal client l'indicateur de requête de transfert de domaine généré et le numéro de télécommunication de transfert de domaine généré.
PCT/EP2007/061741 2006-11-03 2007-10-31 Déplacement entre des domaines de communications WO2008053013A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0621927A GB2443462A (en) 2006-11-03 2006-11-03 Identifying a session to be transferred between communications domains
GB0621927.3 2006-11-03

Publications (1)

Publication Number Publication Date
WO2008053013A1 true WO2008053013A1 (fr) 2008-05-08

Family

ID=37547280

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/061741 WO2008053013A1 (fr) 2006-11-03 2007-10-31 Déplacement entre des domaines de communications

Country Status (2)

Country Link
GB (1) GB2443462A (fr)
WO (1) WO2008053013A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070108429A (ko) * 2006-02-06 2007-11-12 엘지전자 주식회사 도메인 전환의 요청 방법, 그 단말 및 그 서버
US9124608B2 (en) * 2008-06-19 2015-09-01 Qualcomm Incorporated Conveying session continuity information in a multi-component communication session

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003001836A1 (fr) * 2001-06-20 2003-01-03 Nokia Corporation Systeme, dispositif et procede de transfert des appels dans un mode de souscription double
US7885208B2 (en) * 2003-09-11 2011-02-08 Nokia Corporation IP-based services for circuit-switched networks
SE527871C2 (sv) * 2004-03-09 2006-06-27 Ericsson Telefon Ab L M Metod och system för hantering av webbtjänster
US7978683B2 (en) * 2004-04-14 2011-07-12 Alcatel-Lucent Usa Inc. Method of transferring call transition messages between network controllers of different radio technologies

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3GPP TS 23.206 V7.0.0 (2006-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Voice Call Continuity (VCC) between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2 (Release 7)", 4 October 2006 (2006-10-04), XP002465453, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/archive/23%5Fseries/23.206/23206-700.zip> [retrieved on 20080121] *
MOTOROLA, BRIDGEPORT, TELECOM ITALIA, ECRIO: "Allocation of VDN, VDI", no. S2-063596, 23 September 2006 (2006-09-23) - 27 September 2006 (2006-09-27), Busan, Korea, XP002465452, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/html-info/TDocExMtg--S2-55--25861.htm> [retrieved on 20080121] *
RESEARCH IN MOTION: "Use of SIP 380 Alternative Service to support dynamic VDNs", INTERNET CITATION, 23 October 2006 (2006-10-23), XP002424763, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_55_Busan/Docs/S2-063605.zi> [retrieved on 20070314] *

Also Published As

Publication number Publication date
GB2443462A (en) 2008-05-07
GB0621927D0 (en) 2006-12-13

Similar Documents

Publication Publication Date Title
AU2011374206B2 (en) Methods and apparatuses for enabling an Single Radio Voice Call Continuity (SRVCC) access transfer of an emergency call back session
CN102177698B (zh) 关联通信会话
EP2751971B1 (fr) Routage domestique pour itinérance ims au moyen d&#39;une ancre de réseau vplmn
KR100940548B1 (ko) Ｓｉｐ 메세징을 이용하여 ｉｍｓ 네트워크 환경에서의 콜 연속성을 관리하는 시스템 및 방법
US20060034195A1 (en) SIP message extension for push to watch service
US8825875B2 (en) Session establishment in a communication network
EP2347562B1 (fr) Gestion d&#39;identités d&#39;utilisateurs dans un sous-système multimédia ip
WO2006111845A2 (fr) Ouverture de session a partir de serveurs d&#39;applications dans un sous-systeme multimedia ip
EP2119178B1 (fr) Procédé et appareils pour la fourniture de services réseau proposés via un ensemble de serveurs dans un réseau ims
KR100703426B1 (ko) 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 발신 및 착신 호를 가능하게 하는 방법 및 장치
EP2795865B1 (fr) Établissement de session dans un réseau de sous-système multimédia ip
US20170201605A1 (en) Method of dynamic selection, by a caller, from a plurality of terminals of a callee
WO2008053013A1 (fr) Déplacement entre des domaines de communications
KR101360151B1 (ko) Ｇｒｕｕ 사용 가입자 간의 ｉｍｓ망에서의 ｓｉｐ 메시지 전송 방법 및 그 장치
KR101117440B1 (ko) Ｉｍｓ 네트워크에서 가상번호 서비스를 제공하기 위한 방법 및 장치
JP6549526B2 (ja) フォーキングに基づくダイアログを整合する網間制御方法、ｓｉｐサーバ及びプログラム
KR100875832B1 (ko) 다양한 이벤트의 가입을 일괄적으로 처리하는 방법, 이방법을 실행하는 네트워크 장치 및 네트워크 시스템
WO2013185795A1 (fr) Interdiction d&#39;appels
JP2017216584A (ja) 要求先端末のオプション機能の非使用を整合する網間制御方法、ｓｉｐサーバ及びプログラム
WO2013044988A1 (fr) Suppression d&#39;un appel de services camel pour le réacheminement d&#39;usagers

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

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07822088

Country of ref document: EP

Kind code of ref document: A1