WO2015062674A1 - Transfert amélioré de domaine d'accès - Google Patents

Transfert amélioré de domaine d'accès Download PDF

Info

Publication number
WO2015062674A1
WO2015062674A1 PCT/EP2013/072937 EP2013072937W WO2015062674A1 WO 2015062674 A1 WO2015062674 A1 WO 2015062674A1 EP 2013072937 W EP2013072937 W EP 2013072937W WO 2015062674 A1 WO2015062674 A1 WO 2015062674A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
session
coding
indicative
message
Prior art date
Application number
PCT/EP2013/072937
Other languages
English (en)
Inventor
Jiadong Shen
Karl Lanzinger
Original Assignee
Nokia Solutions And Networks Oy
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 Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2013/072937 priority Critical patent/WO2015062674A1/fr
Publication of WO2015062674A1 publication Critical patent/WO2015062674A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022Control 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/00224Control 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/00226Control 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]

Definitions

  • the present invention relates to improved access domain transfer. More specifically, the present invention exemplarily relates to measures (including methods, apparatuses and computer program products) for realizing improved access domain transfer.
  • the present specification generally relates to access domain transfer of media path legs of media communication sessions.
  • the present invention relates to enhanced single radio voice call continuity (eSRVCC).
  • eSRVCC enhanced single radio voice call continuity
  • ESRVCC was introduced by 3 rd Generation Partnership Project (3GPP) in Long Term Evolution (LTE) Release 10 (LTE-A) to improve single radio voice call continuity (SRVCC) efficiency.
  • 3GPP 3 rd Generation Partnership Project
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • ATCF access transfer control function
  • ATGW access transfer gateway
  • An ATCF is a function in the serving (visited if roaming) network.
  • the ATCF is included in the session control plane for the duration of the call before and after Access Transfer.
  • An ATGW is controlled by the ATCF and, if SRVCC enhanced with ATCF is used, stays in the session media path for the duration of the call and after access transfer, based on the local policy of the serving network.
  • Figure 1 represents a procedure (according to 3GPP Technical Specification 23.237) of an access transfer from packet switching (PS) to circuit switching (CS) of a media communication session which is anchored at an ATGW (the media path is anchored at ATGW), and which utilizes eSRVCC, i.e. which utilizes enhancements of the ATCF.
  • An access leg is the call control leg between the UE and the service centralization and continuity application server (SCC-AS).
  • a remote leg is the call control leg between the SCC-AS and the remote party (e.g. second UE) from the subscriber's perspective.
  • a mobile switching center server sends a list of codecs supported (i.e. supported codecs for voice or voice and video) by an associated circuit switch media gateway (CS-MGW) necessary for circuit switched domain as a session description protocol (SDP) offer to the ATCF.
  • codecs supported i.e. supported codecs for voice or voice and video
  • CS-MGW circuit switch media gateway
  • SDP session description protocol
  • the SDP offer also includes codec parameters.
  • the media path of remote leg shall be kept unchanged, i.e. an update of remote UE shall be avoided.
  • the SDP offer does not contain the codec/codec parameter combination of the media communication session to be transferred (no codec including codec parameter matches the one used by the session to be transferred)
  • the ATGW is required to connect the new media path of CS access leg with the media path of the remote leg, even if both media paths do not match each other. That is, in such case the ATGW acts as a bridge between two media paths and has to provide media transcoding or media parameter mapping if needed. It is obvious that any transcoding may deteriorate the data transmitted via such media communication session.
  • ATGW can not (i.e., does provide the functionality to) bridge two media paths, e.g. due to lack of support of the involved voice codec, eSRVCC cannot be provided.
  • the ATCF can only fallback to normal SRVCC, where the remote terminal is updated with the SDP offer provided by the MSC-S.
  • the ATCF has to fallback to the procedure for normal SRVCC.
  • Figure 2 represents a procedure (according to 3GPP Technical Specification 23.237) of an access transfer from packet switching (PS) to circuit switching (CS) of a media communication session which is not anchored at an ATGW (the media path is not anchored at ATGW) according to normal SRVCC.
  • PS packet switching
  • CS circuit switching
  • the ATGW is not involved in the media path after access transfer. Normally, this procedure is only applied if the session to be transferred is not anchored at ATGW.
  • a method comprising transmitting a message indicative of a request of an access domain transfer of a communication endpoint of a session, receiving a message including information indicative of transmission coding of a first transmission path of said session, and transmitting a message indicative of acceptance of said transmission coding for a second transmission path of said session for a reconfiguration of an anchor point of said second transmission path based on said transmission coding.
  • a method comprising receiving a message indicative of a request of an access domain transfer of a communication endpoint of a session, transmitting a message including information indicative of transmission coding of a first transmission path of said session, and receiving a message indicative of acceptance of said transmission coding for a second transmission path of said session for a reconfiguration of an anchor point of said second transmission path based on said transmission coding.
  • an apparatus comprising at least one processor, and at least one memory for storing instructions to be executed by the processor, wherein said at least one memory and said instructions are configured to, with said at least one processor, cause said apparatus at least: to transmit a message indicative of a request of an access domain transfer of a communication endpoint of a session, to receive a message including information indicative of transmission coding of a first transmission path of said session, and to transmit a message indicative of acceptance of said transmission coding for a second transmission path of said session for a reconfiguration of an anchor point of said second transmission path based on said transmission coding.
  • an apparatus comprising at least one processor, and at least one memory for storing instructions to be executed by said processor, wherein said at least one memory and said instructions are configured to, with said at least one processor, cause said apparatus at least: to receive a message indicative of a request of an access domain transfer of a communication endpoint of a session, to transmit a message including information indicative of transmission coding of a first transmission path of said session, and to receive a message indicative of acceptance of said transmission coding for a second transmission path of said session for a reconfiguration of an anchor point of said second transmission path based on said transmission coding.
  • a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present invention), is configured to cause the computer to carry out the method according to any one of the aforementioned method-related exemplary aspects of the present invention.
  • Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computer-executable computer program code is stored, and/or the program may be directly loadable into an internal memory of the computer or a processor thereof.
  • improved access domain transfer More specifically, by way of exemplary embodiments of the present invention, there are provided measures and mechanisms for realizing improved access domain transfer.
  • Figure 1 is a schematic diagram of a procedure (according to 3GPP Technical Specification 23.237) of an access transfer from PS to CS of a media communication session utilizing eSRVCC
  • Figure 2 is a schematic diagram of a procedure (according to 3GPP Technical Specification 23.237) of an access transfer from PS to CS of a media communication session utilizing normal SRVCC
  • Figure 3 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • Figure 4 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • Figure 5 is a schematic diagram of a procedure according to exemplary embodiments of the present invention
  • Figure 6 is a schematic diagram of a procedure according to exemplary embodiments of the present invention
  • Figure 7 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • Figure 8 is a schematic diagram of an improved procedure of an access transfer from PS to CS of a media communication session utilizing eSRVCC according to exemplary embodiments of the present invention
  • Figure 9 is a schematic diagram of an improved procedure of an access transfer from PS to CS of a media communication session utilizing eSRVCC according to exemplary embodiments of the present invention
  • Figure 10 is a block diagram illustrating apparatuses according to exemplary embodiments of the present invention.
  • Figure 11 is a block diagram illustrating an apparatus according to exemplary embodiments of the present invention
  • Figure 12 is a block diagram illustrating an apparatus according to exemplary embodiments of the present invention.
  • the following description of the present invention and its embodiments mainly refers to specifications being used as non-limiting examples for certain exemplary network configurations and deployments. Namely, the present invention and its embodiments are mainly described in relation to 3GPP specifications being used as non-limiting examples for certain exemplary network configurations and deployments.
  • an access transfer from PS to CS of a media communication session is used as a non-limiting example for the applicability of thus described exemplary embodiments.
  • the description of exemplary embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples, and does naturally not limit the invention in any way. Rather, any other communication or communication related system deployment, etc. may also be utilized as long as compliant with the features described herein.
  • FIG 1 is a schematic diagram of a procedure (according to 3GPP Technical Specification 23.237) of an access transfer from PS to CS of a media communication session utilizing eSRVCC.
  • RTP real-time transport protocol
  • FIG. 1 is a schematic diagram of a procedure (according to 3GPP Technical Specification 23.237) of an access transfer from PS to CS of a media communication session utilizing eSRVCC.
  • RTP real-time transport protocol
  • step 1 of Figure 1 the MSC-S is not informed which (voice) codec and codec parameter is used by the session to be transferred.
  • step 2 the MSC-S can not adapt the list of codecs to be sent to the ATCF selectively to that used codec.
  • the MSC-S can not actively avoid that no codec including codec parameter matches the one used by the session to be transferred.
  • the ATCF as answerer of such SDP offer/answer procedure is not allowed to include any new media information of the session. Therefore, in case the media description contained in the SDP offer does not match the media description of the session to be transferred, the ATCF cannot return the media description of the session to be transferred in SDP answer in step 5 of Figure 1, but instead has to proceed further on the base of only the provided codec list. Further, even if the same codec used by the session to be transferred is contained in the SDP offer provided by MSC-S, the session description of the session to be transferred may not match with one of the elements of the list, because different codec parameters may be associated therewith, respectively.
  • the codec parameters may include dynamic payload type for the codec.
  • the CS- MGW may already transcode between the media path between UE-1 (access terminal) and CS-MGW and the media path between CS-MGW and ATGW.
  • a transcoding between narrow band adaptive multi-rate (AMR) code to wide band AMR code may be performed by the CS-MGW.
  • the ATGW would further provide transcoding due to different codecs or codec parameters, e.g., due to different mode-set of the same wide band AMR code, voice (data) quality may be additionally affected by the two-time transcoding.
  • Figure 3 is a schematic diagram of a procedure, performed e.g. on a MSC-S, according to exemplary embodiments of the present invention.
  • a procedure comprises an operation of transmitting (S31) a message indicative of a request of an access domain transfer of a communication endpoint of a session, an operation of receiving (S32) a message including information indicative of transmission coding of a first transmission path of said session, and an operation of transmitting (S33) a message indicative of acceptance of said transmission coding for a second transmission path of said session for a reconfiguration of an anchor point of said second transmission path based on said transmission coding.
  • FIG. 5 is a schematic diagram of a procedure, performed e.g. on an ATCF, according to exemplary embodiments of the present invention.
  • a procedure according to exemplary embodiments of the present invention comprises an operation of receiving (S51) a message indicative of a request of an access domain transfer of a communication endpoint of a session, an operation of transmitting (S52) a message including information indicative of transmission coding of a first transmission path of said session, and an operation of receiving (S53) a message indicative of acceptance of said transmission coding for a second transmission path of said session for a reconfiguration of an anchor point of said second transmission path based on said transmission coding.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of conducting (S64) such reconfiguration of the anchor point of said second transmission path based on said transmission coding.
  • the steps S61 to S63 of Figure 6 correspond to steps S51 toS53 of Figure 5.
  • the message indicative of a request of an access domain transfer of a communication endpoint of a session may be an invitation message sent from a MSC-S to an ATCF (compare step 2 of Figure 1).
  • the ATCF is enabled to negotiate the media description before configuring the ATGW.
  • the ATCF may insert another round of SDP negotiation with the MSC-S, before the ATGW is configured according to the access transfer.
  • the media communication session to be transferred in particular, the media path to be transferred, may be allowed to utilize the media description of the media path of the remote leg in any case the CS- MGW supports the same, such that transcoding or falling back in those cases may be avoided.
  • the SDP offer for a session initiation protocol (SIP) session may be carried in the INVITE request sent by the caller (compare step 2 of Figure 1), or in the first reliable response to the INVITE request sent by the callee (compare step 5 of Figure 1).
  • SIP session initiation protocol
  • the current 3GPP specification for eSRVCC requires the MSC-S to include SDP offer in the access transfer request (step 2 of Figure 1).
  • the SDP offer provided by MSC-S may not always match the media description of the session to be transferred, and eSRVCC can only be provided when ATGW can support transcoding.
  • said message indicative of said request of said access domain transfer does not include information indicative of supported transmission codings.
  • the MSC-S is allowed to send the access transfer request without any SDP offer.
  • the ATCF can provide the session description of the session to be transferred as SDP offer to MSC-S.
  • ATGW does not need to provide any transcoding (transcodingless ATGW) for the media path and eSRVCC can be provided though, as the media path of the remote leg is also kept unchanged.
  • FIG 8 is a schematic diagram of an improved procedure of an access transfer from PS to CS of a media communication session utilizing eSRVCC according to corresponding exemplary embodiments of the present invention, i.e., a PS to CS access transfer when using ATCF enhancements and media anchored with transcodingless ATGW according to exemplary embodiments of the present invention.
  • the INVITE request sent by MSC-S in step 2 does not contain any SDP offer (also steps S31 and S61).
  • the ATCF may return the media description of the session to be transferred as SDP offer in the first reliable response to MSC-S in step 3a of Figure 8 (also steps S32 and S62).
  • the MSC-S just needs to accept the SDP offer with its media description and provide its own media description in SDP offer in step 3b (also steps S33 and S63), which is same as the media description of the session to be transferred.
  • the ATCF then reconfigures the ATGW in steps 4 and 5 of Figure 8 (also step S64), after the SDP answer from MSC-S is received. Only the IP address and port for the media stream is changed so that the media path of the access leg is changed from PS domain to CS domain, while the media description of the voice stream is kept unchanged.
  • multiple different SIP procedures may be utilized to support such SDP-less INVITE message, e.g. SIP procedures with or without reliable provisioning response. That is, the idea behind exemplary embodiments of the present invention is independent from which SIP procedure is used for the SDP-less INVITE message.
  • step 5 of Figure 8 The steps after access transfer (step 5 of Figure 8) are not affected by this invention and are kept unchanged in comparison to the procedure as shown in Figure 1. However, additional messages may be exchanged.
  • the MSC-S may anticipate the potential need for a new round of negotiation and thus does not include an SDP offer to optimize the invite/answer exchange.
  • Summing, according to exemplary embodiments of the present invention, both, the MSC-S as well as the ATCF may be enhanced in order to improve eSRVCC.
  • a session may be modified either during session establishment or after said session establishment.
  • the current 3GPP specification for eSRVCC requires that the MSC-S includes an SDP offer in the access transfer request (compare step 2 of Figure 1).
  • the SDP offer provided by MSC-S may not always match the media description of the session to be transferred, and eSRVCC may only be provided when ATGW supports transcoding.
  • exemplary additional operations are given in Figure 4 (showing a schematic diagram of a procedure according to exemplary embodiments of the present invention), which are inherently independent from each other as such, while said message indicative of said request of said access domain transfer includes information indicative of supported transmission codings.
  • an exemplary method may comprise an operation of receiving (S42) a message indicative of inactivation of said session and including information indicative of a temporary transmission coding out of said supported transmission codings.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of comparing (S72) a portion of each of said supported transmission codings with a corresponding portion of said transmission coding of said first transmission path.
  • an exemplary method according to exemplary embodiments of the present invention may further comprise an operation of setting (S73) said session inactive, and an operation of transmitting (S74) a message indicative of inactivation of said session and including information indicative of a temporary transmission coding out of said supported transmission codings.
  • an exemplary method according to exemplary embodiments of the present invention may further comprise an operation of re-setting (S77), upon receipt of said message indicative of acceptance of said transmission coding, said session active.
  • said procedure may, however, fall back to a normal SRVCC procedure.
  • said message indicative of inactivation of said session may be a session modification request message.
  • the behaviour of the MSC-S is kept unchanged for eSRVCC, i.e. the MSC-S is kept sending the access transfer request (step 2 of Figure 1) with a SDP offer.
  • the ATCF may check whether the codec used by the session to be transferred is contained in the SDP offer. If it is not the case, the ATCF may fall-back to the normal SRVCC procedure illustrated in Figure 2 (compare the consequence of option "N", i.e. "No" in step S72a of Figure 7). If, however, the same voice code is contained in the SDP offer, the ATCF may select this codec for SDP answer and set the session to inactive session.
  • the ATCF may start session modification procedure to provide the session description of the session to be transferred as a new SDP offer to MSC-S (which is subsequently accepted by the MSC-S).
  • MSC-S which is subsequently accepted by the MSC-S.
  • ATGW does not need to provide any transcoding (transcodingless ATGW) for the media path and eSRVCC can be provided further, as the media path of the remote leg is also kept unchanged.
  • Figure 9 is a schematic diagram of an improved procedure of an access transfer from PS to CS of a media communication session utilizing eSRVCC according to exemplary embodiments of the present invention, i.e., a PS to CS access transfer when using ATCF enhancements and media anchored with transcodingless ATGW according to exemplary embodiments of the present invention.
  • the INVITE request sent by MSC-S in step 2a of Figure 9 still contains an SDP offer (also steps S41 and S71). If the same codec of the session to be transferred is contained in the SDP offer (also step S72), the ATCF may return an SDP answer to MSC-S in step 2b of Figure 9 with this codec, and with the session being set to inactive (also steps S42 and S73 and S74). The ATCF may then, in step 3a of Figure 9, send a session modification request immediately with the media description of the session to be transferred to MSC-S (also steps S43 and S75). The MSC-S may accept the new SDP offer because the same codec is contained in the new SDP offer (also steps S44 and S76).
  • the session may be set to active again (also step S77). Therefore, the MSC-S transmits its own media description in SDP answer in step 3b of Figure 9 (also steps S44 and S76), which is same as the session to be transferred.
  • the ATCF may then reconfigure the ATGW in steps 4 and 5 of Figure 9 (also step S78), after the SDP answer from MSC-S is received.
  • multiple different SIP procedures may be utilized to support such session modification message, e.g. SIP procedures with or without reliable provisioning response. That is, the idea behind exemplary embodiments of the present invention is independent from which SIP procedure is used for the SIP session modification.
  • a SIP re- INVITE (relNVITE) request is used for the session modification in step 3a of Figure 9.
  • the new SDP offer may for example also be carried in an UPDATE request (message) though.
  • step 5 of Figure 9 The steps after access transfer (step 5 of Figure 9) are not affected by this invention and are kept unchanged in comparison to the procedure as shown in Figure 1.
  • ATCF may be enhanced in order to improve eSRVCC
  • standard compliant MSC-S can be used, such that the improvement only affects ATCF. Accordingly, interoperability may be increased according to exemplary embodiments of the present invention.
  • said message indicative of acceptance of said transmission coding includes information indicative of said transmission coding.
  • said transmission coding is specified in terms of a media description.
  • said media description comprises at least one of a codec and a codec parameter.
  • said portion of each of said supported transmission codings and said corresponding portion of said transmission coding of said first transmission path is a codec.
  • said information indicative of said transmission coding is embedded in a session description protocol offer.
  • the solid line blocks are basically configured to perform respective operations as described above.
  • the entirety of solid line blocks are basically configured to perform the methods and operations as described above, respectively.
  • the individual blocks are meant to illustrate respective functional blocks implementing a respective function, process or procedure, respectively.
  • Such functional blocks are implementation-independent, i.e. may be implemented by means of any kind of hardware or software, respectively.
  • the arrows and lines interconnecting individual blocks are meant to illustrate an operational coupling there-between, which may be a physical and/or logical coupling, which on the one hand is implementation-independent (e.g. wired or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional entities not shown.
  • the direction of arrow is meant to illustrate the direction in which certain operations are performed and/or the direction in which certain data is transferred.
  • the thus described apparatus 1000 may represent a (part of a) network node such as a MSC-S or a modem (which may be installed as part of a MSC-S, but may be also a separate module, which can be attached to various devices), and may be configured to perform a procedure and/or functionality as described in conjunction with any one of Figures 3, 4, 8 and 9.
  • the thus described apparatus 2000 may represent a (part of a) network node such as a ATCF or a modem (which may be installed as part of a ATCF, but may be also a separate module, which can be attached to various devices), and may be configured to perform a procedure and/or functionality as described in conjunction with any one of Figures 5 to 9.
  • the apparatus 1000 comprises a processor 101, a memory 102 and an interface 103, which are connected by a bus 104 or the like.
  • the apparatus 2000 comprises a processor 105, a memory 106 and an interface 107, which are connected by a bus 108 or the like, and the apparatuses may be connected via link 109, respectively.
  • the processor 101/105 and/or the interface 103/107 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively.
  • the interface 103/107 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively.
  • the interface 103/107 is generally configured to communicate with at least one other apparatus, i.e. the interface thereof.
  • the memory 102/106 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the exemplary embodiments of the present invention.
  • the respective devices/apparatuses may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.
  • the processor or some other means
  • the processor is configured to perform some function
  • this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression "processor configured to [cause the apparatus to] perform xxx-ing” is construed to be equivalent to an expression such as "means for xxx-ing").
  • an apparatus representing the network node 1000 comprises at least one processor 101, at least one memory 102 including computer program code, and at least one interface 103 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 101, with the at least one memory 102 and the computer program code
  • the processor is configured to perform transmitting a message indicative of a request of an access domain transfer of a communication endpoint of a session, to perform receiving a message including information indicative of transmission coding of a first transmission path of said session, and to perform transmitting a message indicative of acceptance of said transmission coding (for a reconfiguration of an anchor point of said second transmission path based on said transmission coding) for a second transmission path of said session.
  • the apparatus 1000 may thus comprise respective means for transmitting and means for receiving.
  • FIG 11 is an alternative illustration of the network node 1000 of Figure 10 showing those means.
  • an apparatus representing the network node 2000 comprises at least one processor 105, at least one memory 106 including computer program code, and at least one interface 107 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 105, with the at least one memory 106 and the computer program code
  • the processor is configured to perform receiving a message indicative of a request of an access domain transfer of a communication endpoint of a session, to perform transmitting a message including information indicative of transmission coding of a first transmission path of said session, and to perform receiving a message indicative of acceptance of said transmission coding (for a reconfiguration of an anchor point of said second transmission path based on said transmission coding) for a second transmission path of said session.
  • the apparatus 2000 may thus comprise respective means for receiving, and means for transmitting.
  • the apparatus 2000 may comprise one or more of respective means for conducting, means for comparing, means for setting, and means for re-setting.
  • Figure 12 is an alternative illustration of the network node 2000 of Figure 10 showing those means.
  • a system may comprise any conceivable combination of the thus depicted devices/apparatuses and other network elements, which are configured to cooperate with any one of them.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor- Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field-programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP Digital Signal Processor
  • - devices, units or means can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
  • an apparatus like the user equipment and the network entity /network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • measures for improved access domain transfer exemplarily comprise transmitting a message indicative of a request of an access domain transfer of a communication endpoint of a session, receiving a message including information indicative of transmission coding of a first transmission path of said session, and transmitting a message indicative of acceptance of said transmission coding for a second transmission path of said session.

Landscapes

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

Abstract

L'invention concerne des procédés de transfert amélioré de domaine d'accès. Les procédés consistent à : transmettre un message indiquant une demande d'un transfert de domaine d'accès d'un point limite de communication d'une session; recevoir un message contenant des informations indiquant un codage de transmission d'une première voie de transmission de ladite session; et transmettre un message indiquant l'acceptation dudit codage de transmission pour une seconde voie de transmission de ladite session en vue de reconfigurer un point d'ancrage de ladite seconde voie de transmission d'après ledit codage de transmission.
PCT/EP2013/072937 2013-11-04 2013-11-04 Transfert amélioré de domaine d'accès WO2015062674A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/072937 WO2015062674A1 (fr) 2013-11-04 2013-11-04 Transfert amélioré de domaine d'accès

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/072937 WO2015062674A1 (fr) 2013-11-04 2013-11-04 Transfert amélioré de domaine d'accès

Publications (1)

Publication Number Publication Date
WO2015062674A1 true WO2015062674A1 (fr) 2015-05-07

Family

ID=49578273

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/072937 WO2015062674A1 (fr) 2013-11-04 2013-11-04 Transfert amélioré de domaine d'accès

Country Status (1)

Country Link
WO (1) WO2015062674A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016055308A1 (fr) * 2014-10-08 2016-04-14 Nokia Solutions And Networks Oy Transfert de paramètres de communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012169134A1 (fr) * 2011-06-09 2012-12-13 パナソニック株式会社 Nœud de réseau, terminal, procédé de détermination de modification de largeur de bande et procédé de modification de largeur de bande
US20130272194A1 (en) * 2012-04-17 2013-10-17 Telefonaktiebolaget L M Ericsson (Publ) Handover of calls between access networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012169134A1 (fr) * 2011-06-09 2012-12-13 パナソニック株式会社 Nœud de réseau, terminal, procédé de détermination de modification de largeur de bande et procédé de modification de largeur de bande
EP2706766A1 (fr) * 2011-06-09 2014-03-12 Panasonic Corporation Noeud de réseau, terminal, procédé de détermination de modification de largeur de bande et procédé de modification de largeur de bande
US20130272194A1 (en) * 2012-04-17 2013-10-17 Telefonaktiebolaget L M Ericsson (Publ) Handover of calls between access networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ALCATEL-LUCENT: "ATGW performing transcoding", 3GPP DRAFT; C1-112990, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Malta; 20110822, 13 August 2011 (2011-08-13), XP050533553 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016055308A1 (fr) * 2014-10-08 2016-04-14 Nokia Solutions And Networks Oy Transfert de paramètres de communication
US10425863B2 (en) 2014-10-08 2019-09-24 Nokia Solutions And Networks Oy Transfer of communication parameters

Similar Documents

Publication Publication Date Title
US10687373B2 (en) Optimizations for voice handovers over wireless data access
US9408064B2 (en) Method and system for obtaining user equipment ability by user equipment, home subscriber data server and core network element
RU2617438C2 (ru) Синхронизация состояний вызова сетевого компонента и мобильное устройство при переносе сеанса
TWI597992B (zh) 用於緊急回撥或點選即撥連線之單無線電語音通話連續技術
EP3157224B1 (fr) Procédé et système de conversion de signalisation de commande de session
CN101884205A (zh) Ims集中式服务中i1-ps信令的动态发起
WO2010089445A1 (fr) Changement d'accès pour rerouter une connexion
WO2021063134A1 (fr) Procédé et dispositif pour lire un contenu multimédia vidéo
US10863342B2 (en) Method and device for processing a signaling message related to a communication service of a client device
US9609622B2 (en) Provision of a customised alerting notification
US10749911B2 (en) Service control awareness for call routing between packet switched telephony domain and circuit switched telephony domain
US9204092B2 (en) Internet protocol video telephony with carrier grade voice
US8233417B1 (en) Femtocell architecture using internet protocol multimedia subsystem centralized services
WO2015062674A1 (fr) Transfert amélioré de domaine d'accès
CN104936262B (zh) 远端标识的发送、接收方法及装置、传输系统
US9374756B1 (en) Secure wireless device handoff
CN101969627A (zh) 单待终端业务连续性实现方法和系统
US9271330B1 (en) Internet multimedia subsystem (IMS) control over session transfer between communication networks
WO2017041818A1 (fr) Transfert du domaine d'appel d'urgence dans un système de communication mobile
JP6282964B2 (ja) 移動通信システム、呼制御装置、及び呼制御方法
JP2016046663A (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: 13789520

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

Country of ref document: EP

Kind code of ref document: A1