WO2015050547A1 - Scénarios de mobilité volte avec des supports vocaux ims et non-ims - Google Patents

Scénarios de mobilité volte avec des supports vocaux ims et non-ims Download PDF

Info

Publication number
WO2015050547A1
WO2015050547A1 PCT/US2013/063239 US2013063239W WO2015050547A1 WO 2015050547 A1 WO2015050547 A1 WO 2015050547A1 US 2013063239 W US2013063239 W US 2013063239W WO 2015050547 A1 WO2015050547 A1 WO 2015050547A1
Authority
WO
WIPO (PCT)
Prior art keywords
radio access
access bearer
network element
call continuity
bearer
Prior art date
Application number
PCT/US2013/063239
Other languages
English (en)
Inventor
Srinivasan Selvaganapathy
Curt Wong
Parthasarathi RAVINDRAN
Dario Serafino TONESI
Original Assignee
Nokia Siemens 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 Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/US2013/063239 priority Critical patent/WO2015050547A1/fr
Publication of WO2015050547A1 publication Critical patent/WO2015050547A1/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/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • 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/1069—Session establishment or de-establishment
    • 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/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing

Definitions

  • the present invention relates to enhancements to Voice over LTE (Long Term Evolution) mobility scenarios to handle co-existence of IMS (Internet protocol Multimedia Subsystem) and non-IMS voice bearers with QoS (Quality of Service).
  • IMS Internet protocol Multimedia Subsystem
  • QoS Quality of Service
  • the present invention relates to LTE networks which support voice services along with voice-call continuity during mobility scenarios with 3G networks.
  • voice support is enabled by interworking of the LTE network with IMS network elements.
  • the signaling related to voice-call setup is handled by the IMS network elements along with IMS client at UE (User Equipment) side.
  • UE User Equipment
  • 3G UTRAN Universal Terrestrial Radio Access Network
  • CS RAB Circuit Switched Radio Access Bearer
  • SRVCC Single Radio Voice Call Continuity
  • Fig . 1 shows an example of the VoLTE (Voice over Long Term Evolution) architecture along with SRVCC functionality support towards UTRAN 15.
  • VoLTE Voice over Long Term Evolution
  • VoLTE Architecture is modified as follows.
  • IMS subsystem 11 should be connected to MSC 12 for routing the voice related signaling via 3G MSC.
  • MME 13 should be connected to MSC 12 for requesting for conversion of IMS PS (Packet Switched) bearer to CS Voice bearer.
  • Further elements of the VoLTE architecture shown in Fig . 1 are the SGW/PGW (Serving Gateway / Packet data network Gateway) 14, the UTRAN (Universal Terrestrial Radio Access Network) 15, the eNB (evolved NodeB) 16, the HSS (Home Subscriber Server) 17 and the PCRF (Policy and Charging Rule Function) 18.
  • the SGW/PGW 14 implements a PCEF (Policy and Charging Enforcement Function) and is connected to the PCRF via a Gx-interface, as defined in document [1] .
  • PCEF Policy and Charging Enforcement Function
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • VoLTE VoLTE
  • SRVCC SRVCC
  • the voice EPS (Evolved Packet System) bearer is identified based on QCI (QoS (Quality of Service) Class Indicator) value 1 among all the bearers.
  • QCI Quality of Service
  • ERAB EPS Radio Access Bearer
  • IMS based voice services In addition to IMS based voice services, other browser based applications (for example, webRTC (Web Real-Time-Communication Services)) also provide voice services. Voice calls can also be setup via these applications. When such applications are used in LTE UE, by default, this traffic is handled without any QoS treatment.
  • webRTC Web Real-Time-Communication Services
  • Fig . 2 shows an example of high level architecture for interworking of IMS and webRTC services.
  • the new architectures have two main aspects
  • the application servers interwork with IMS components in such a way that the webRTC sessions are handled as same as IMS sessions in IMS components.
  • the LTE system supports IMS based voice services along with other voice applications such as webRTC.
  • the decision to trigger SRVCC is done just based on QCI value of ERAB, it will result in SRVCC handover trigger for the voice bearer of non-IMS based applications (e.g . webRTC) and the handover will fail eventually.
  • AF (Application Function) 19 represents the application-interworking-node which interacts with IMS and PCRF to enable voice-session setup via existing IMS and PCRF components.
  • this node represents the webRTC interworking function.
  • the remaining elements shown in Fig . 2 correspond to those shown in Fig . 1 and the same elements in Fig . 2 are denoted with the same reference signs as used in Fig . 1.
  • webRTC is one such non-IMS based voice application which can be triggered from any browser.
  • the call setup signaling is happening via application layers (http) instead of SIP (Session Initiation Protocol).
  • https application layers
  • SIP Session Initiation Protocol
  • Many of the operators who are having VoLTE deployments request for support of this application with QoS so that it will allow them to provide new avenue of application and revenue.
  • Standardization discussions in IETF (Internet Engineering Task Force) and 3GPP (3 Generation Partnership Project) are ongoing to allow enabling the QoS for the voice bearers of these applications via IMS architecture and high level candidate architectures are captured in document [3] .
  • MME checks with HSS for subscription details for IMS services as well as for SRVCC capability.
  • HSS also provides STR-SN (Session-Transfer- Sequence-Number) for this UE to MME. This number should be used later during SRVCC mobility between MME and MSC as well as between MSC and IMS.
  • STR-SN Session-Transfer- Sequence-Number
  • MME informs to eNB the SRVCC allowed indication to the UE.
  • This parameter is set based on the stored information related to UE capability and presence of STR-SN for this UE.
  • eNB decides on SRVCC Handover based on the below condition
  • eNB sets the SRVCC-HO-Indication in the Handover Required message.
  • MME When MME receives the Handover Required message with SRVCC-HO- indication, MME splits the bearers as follows
  • o Remaining bearers are relocated via SGSN as normal PS handover.
  • MME requires MSC for PS-CS conversion along with STR-SN number.
  • MSC interacts with IMS components to change the media and signaling path towards MSC.
  • MME on getting response from SGSN and MSC triggers the Inter-RAT (Radio Access Technology) handover to UE.
  • Inter-RAT Radio Access Technology
  • Use-case 1 UE subscribed for VoLTE and SRVCC makes voice call via webRTC application.
  • the radio access bearer supports call continuity, performing conversion from packet switched to circuit switched handover for the radio access bearer.
  • an apparatus for use in a first network element comprising:
  • the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform :
  • an apparatus comprising:
  • the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform :
  • an apparatus comprising:
  • the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform :
  • an apparatus comprising:
  • processor at least one processor, at least one interface to at least one other network element, and at least one memory for storing instructions to be executed by the processor, wherein
  • the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform :
  • the radio access bearer supports call continuity, performing conversion from packet switched to circuit switched handover for the radio access bearer.
  • an apparatus comprising:
  • an apparatus comprising:
  • an apparatus comprising:
  • an apparatus comprising:
  • a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
  • a computer program product as defined above, wherein the computer program product comprises a computer-readable medium on which the software code portions are stored .
  • Fig . 1 is a diagram illustrating an example of a VoLTE architecture
  • Fig . 2 is a diagram illustrating an example for high level architecture for interworking of IMS and webRTC services
  • Fig . 3 is a signaling diagram illustrating a message sequence for creation of dynamic PCC (Policy Control and Charging) rule followed by creation of dedicated ERAB for voice bearer according to certain aspects of the present invention
  • Fig . 4 is a signaling diagram illustrating a message sequence of a mobility procedure according to certain aspects of the present invention.
  • Fig . 5 is a flowchart illustrating an example of a method according to certain embodiments of the present invention.
  • Fig . 6 is a flowchart illustrating another example of a method according to certain embodiments of the present invention.
  • Fig . 7 is a flowchart illustrating another example of a method according to certain embodiments of the present invention.
  • Fig . 8 is a flowchart illustrating another example of a method according to certain embodiments of the present invention.
  • Fig . 9 is a diagram illustrating an example of an apparatus according to certain embodiments of the present invention.
  • the basic system architecture of a communication network where examples of embodiments of the invention are applicable may comprise a commonly known architecture of one or more communication systems comprising a wired or wireless access network subsystem and a core network.
  • Such an architecture may comprise one or more access network control elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station or eNB, which control a coverage area also referred to as a cell and with which one or more communication elements or terminal devices such as a user equipment (UE) or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like, are capable to communicate via one or more channels for transmitting several types of data.
  • core network elements such as gateway network elements, policy and charging control network elements, mobility management entities and the like may be comprised .
  • network elements such as communication network control elements, like an eNB, and the like, as well as corresponding functions as described herein may be implemented by software, e.g., by a computer program product for a computer, and/or by hardware.
  • nodes or network elements may comprise several means and components (not shown) which are required for control, processing and communication/signaling functionality.
  • Such means may comprise, for example, one or more processor units including one or more processing portions for executing instructions, programs and for processing data, memory means for storing instructions, programs and data, for serving as a work area of the processor or processing portion and the like (e.g ., ROM, RAM, EEPROM, and the like), input means for inputting data and instructions by software (e.g ., floppy disc, CD-ROM, EEPROM, and the like), user interface means for providing monitor and manipulation possibilities to a user (e.g ., a screen, a keyboard and the like), interface means for establishing links and/or connections under the control of the processor unit or portion (e.g ., wired and wireless interface means, an antenna, etc.) and the like.
  • processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors.
  • the above problem is solved by having additional identification for IMS-voice bearer and based on the same triggering handover without causing mobility failures.
  • PDN-GW Packet Data Network Gateway
  • PCEF Policy and Charging Enforcement Function
  • the application-server (AF) or the IMS component will request for the bearer creation to PCRF.
  • the MME/PGW can downgrade the QoS to lower value for the non-IMS bearer to allow this bearer to continue with reduced QoS.
  • the webRTC (non- IMS) application / IMS component should indicate whether the traffic flow requested is SRVCC capable or not to PCRF. Based on the above indication, PCRF will inform the additional parameter to PDN-GW indicating that the bearer is SRVCC capable or not.
  • PDN-GW as part of bearer setup will include additional parameter RAB-SRVCC capability towards MME.
  • MME will also inform the attribute towards eNB as part of ERAB setup / modify procedure.
  • IMS component or webRTC application server sets up the voice bearer, it informs the PCRF the Service Data-flow information via Rx Interface procedures. As part of this procedure an additional attribute bearer-type is included in the message.
  • IMS component sets the SRVCC-Indicator to TRUE.
  • Other (non-IMS) application components will set the SRVCC-Indicator to FALSE.
  • PCRF creates the dynamic PCC rule for the subscriber to PCEF at PDN-GW.
  • PCRF provides additional parameter SRVCC-Indicator as it is received from IMS/webRTC (non-IMS) application server.
  • the PDN-GW When the PDN-GW creates dedicated bearer corresponding to the voice SDF, it includes the additional parameter RAB-SRVCC-capability . This parameter value is set as per the additional info received as part of dynamic PCC rule.
  • the eNB behavior modified during mobility procedure is as follows.
  • RTP Real-time Transport Protocol
  • Another option for MME implementation is to trigger the ERAB modification towards PGW to use lower QoS profile which is supported at target.
  • the video bearers of the IMS call will be created with an additional flag vSRVCC indicator towards MME.
  • MME uses this parameter of the bearer to identify the video bearer which needs to be transferred via CS.
  • the MME will not trigger the SRVCC towards MSC.
  • Fig . 3 is a signaling diagram illustrating the message sequence for creation of dynamic PCC rule followed by creation of dedicated ERAB for voice bearer according to certain aspects of the present invention for IMS based voice services.
  • Step S31 denotes the IMS registration and IMS signaling until trigger of voice bearer setup.
  • step S32 When the voice call is setup via webRTC application or if the IMS is setting up the voice bearer for webRTC-type of applications, the above message sequence is modified as below.
  • step S33 SRVCC-Indicator will be set to FALSE
  • step S34 the ERAB created for this bearer will have the RAB-SRVCC-Capability set to FALSE.
  • the message sequence illustrated in Fig . 4 provides the mobility procedure modified according to certain aspects of the present invention for LTE to UTRAN handover for both IMS and non-IMS (e.g ., WebRTC) originated voice bearers.
  • the SRVCC HO decision is modified as follows:
  • the SRVCC HO Indication will be set to TRU E.
  • o SRVCC HO indication is set as per the logic mentioned above.
  • PDN-GW will release the mapping corresponding to this SDF and further RTP packets via default bearer with default-QoS.
  • MME can modify the bearer QoS with PDN-GW to a lower value which can be supported at target-node as part of relocation procedure.
  • the eNB shall not trigger the SRVCC handover and continue with normal handover.
  • This new eNB internal behavior does not require any interface impact in order to allow the non-IMS voice bearer to be relocated without failure.
  • PDN-GW can use such parameters also to decide whether the RAB-SRVCC-Capability is to be set to TRU E or to FALSE (i.e., if the HO for the voice bearer is executed by means of SRVCC or as a PS-Handover).
  • This alternative implementation is possible for operators having IMS, PDN-GW and PCRF components from same vendor.
  • Fig . 5 is a flowchart illustrating an example of a method according to certain embodiments of the present invention.
  • the method may be implemented in a network element and comprises composing, at a first network element, a message including an indication whether or not a voice bearer supports call continuity in a step S51, and causing transmission of the message to a second network element in a step S52.
  • the first network element is a component of a multimedia subsystem
  • the message is a request for setting up the call
  • the indication indicates that the voice bearer supports call continuity
  • the second network element includes a policy charging and rules function.
  • the first network element is a component of an application function other than a multimedia subsystem
  • the message is a request for setting up the call
  • the indication indicates that the voice bearer does not support call continuity
  • the second network element includes a policy charging and rules function.
  • the first network element includes a policy charging and rules function
  • the message is a policy and charging control rule
  • the second network element is a gateway including a policy and charging enforcement function
  • the first network element is a gateway including a policy and charging enforcement function
  • the message is a message for setting up a radio access bearer
  • the second network element is a base station.
  • the gateway is a serving gateway / packet data network gateway, PGW/SGW, and the message is transmitted from the gateway via a mobility management entity to the base station.
  • Fig . 6 is a flowchart illustrating another example of a method according to certain embodiments of the present invention.
  • the method may be implemented in a base station, like e.g . an eNode B, and comprises determining, at a base station, whether there exists a radio access bearer having a predetermined quality of service and supporting call continuity in a step S61, and if it is determined that there exists a radio access bearer having a predetermined quality of service and supporting call continuity, composing a handover required message including an indication that the radio access bearer supports call continuity in a step S62.
  • a base station like e.g . an eNode B
  • Fig . 7 is a flowchart illustrating another example of a method according to certain embodiments of the present invention.
  • the method may be implemented in a base station, like e.g . an eNode B, and comprises determining, at a base station, whether there exists a first radio access bearer having a predetermined quality of service and a second radio access bearer having a predetermined quality of service related to internet protocol multimedia subsystem, IMS, signaling in a step S71, and if it is determined that there exists the first radio access bearer but not the second radio access bearer, composing a handover required message including an indication for packet switched handover in a step S72.
  • a base station like e.g . an eNode B
  • the method further comprises causing transmission of the handover required message including the indication to a mobility management entity (MME).
  • MME mobility management entity
  • Fig . 8 is a flowchart illustrating another example of a method according to certain embodiments of the present invention.
  • the method may be implemented in a network element, like e.g . mobility management entity (MME), and comprises causing reception, at a network element, of a handover required message including an indication whether or not a radio access bearer supports call continuity in a step S81, determining, at the network element, whether or not the radio access bearer supports call continuity based on the received indication in a step S82, and, if it is determined that the radio access bearer supports call continuity, performing conversion from packet switched to circuit switched handover for the radio access bearer in a step S83.
  • MME mobility management entity
  • the method further comprises causing deactivation of the radio access bearer.
  • the method further comprises causing transmission of the radio access bearer with reduced quality of service.
  • the call includes voice call and video call
  • the call continuity includes voice call continuity and video call continuity
  • Fig . 9 is a block diagram showing an example of an apparatus according to certain embodiments of the present invention.
  • FIG. 9 a block circuit diagram illustrating a configuration of an apparatus 90, such as of a network element or part of a network element, is shown, which is configured to implement the above described aspects of the invention.
  • the apparatus 90 shown in Fig . 9 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention.
  • the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of a network element or attached as a separate element to a network element, or the like.
  • the apparatus 90 may comprise a processing function or processor 91, such as a CPU or the like, which executes instructions given by programs or the like related to the flow control mechanism.
  • the processor 91 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example.
  • Reference sign 92 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 91.
  • the I/O units 92 may be used for communicating with one or more management entities and or user equipments.
  • the I/O units 92 may be a combined unit comprising communication equipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements.
  • Reference sign 93 denotes a memory usable, for example, for storing data and programs to be executed by the processor 91 and/or as a working storage of the processor 91.
  • the processor 91 is configured to execute processing related to the above described aspects.
  • the processor 91 is configured to perform composing, at a first network element, a message including an indication whether or not a voice bearer supports call continuity, and causing transmission of the message to a second network element.
  • the first network element is a component of a multimedia subsystem
  • the message is a request for setting up the call
  • the indication indicates that the voice bearer supports call continuity
  • the second network element includes a policy charging and rules function.
  • the first network element is a component of an application function other than a multimedia subsystem
  • the message is a request for setting up the call
  • the indication indicates that the voice bearer does not support call continuity
  • the second network element includes a policy charging and rules function.
  • the first network element includes a policy charging and rules function
  • the message is a policy and charging control rule
  • the second network element is a gateway including a policy and charging enforcement function
  • the first network element is a gateway including a policy and charging enforcement function
  • the message is a message for setting up a radio access bearer
  • the second network element is a base station.
  • the gateway is a serving gateway / packet data network gateway, PGW/SGW, and the message is transmitted from the gateway via a mobility management entity to the base station.
  • the processor 91 is configured to perform determining, at a base station, whether there exists a radio access bearer having a predetermined quality of service and supporting call continuity, and if it is determined that there exists a radio access bearer having a predetermined quality of service and supporting call continuity, composing a handover required message including an indication that the radio access bearer supports call continuity.
  • the processor 91 is configured to perform determining, at a base station, determining whether there exists a first radio access bearer having a predetermined quality of service and a second radio access bearer related to internet protocol multimedia subsystem, IMS, signaling, and if it is determined that there exists the first radio access bearer but not the second radio access bearer, composing a handover required message including an indication for packet switched handover.
  • the processor 91 is configured to perform causing transmission of the handover required message including the indication to a mobility management entity (MME).
  • MME mobility management entity
  • the processor 91 is configured to perform causing reception of a handover required message including an indication whether or not a radio access bearer supports call continuity, determining whether or not the radio access bearer supports call continuity based on the received indication, if it is determined that the radio access bearer supports call continuity, performing conversion from packet switched to circuit switched handover for the radio access bearer.
  • the processor 91 is configured to perform, if it is determined that the radio access bearer does not support call continuity, causing deactivation of the radio access bearer.
  • the processor 91 is configured to perform, if it is determined that the radio access bearer does not support call continuity, causing transmission of the radio access bearer with reduced quality of service.
  • the call includes voice call and video call
  • the call continuity includes voice call continuity and video call continuity
  • the apparatus may comprise further units/means that are necessary for its respective operation as network element, base station, management entity, and the like, respectively. However, a description of these units/means is omitted in this specification.
  • the arrangement of the functional blocks of the apparatus is not construed to limit the invention, and the functions may be performed by one block or further split into sub-blocks.
  • processor or corresponding circuitry 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 circuitry or means for performing the respective function (i.e. the expression "unit configured to” is construed to be equivalent to an expression such as "means for").
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the aspects/embodiments and its modification in terms of the functionality implemented;
  • - method steps and/or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components; - devices, units or means (e.g. the above-defined apparatuses, or any one of their respective units/means) can be implemented as
  • an apparatus 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des procédés, des appareils et un produit-programme d'ordinateur concernant des améliorations apportées à des scénarios de mobilité VoLTE (voix sur LTE (évolution à long terme)) permettant de traiter une coexistence de supports vocaux IMS IP (sous-systèmes multimédias) et des supports vocaux non-IMS avec qualité de service (QoS). La présente invention consiste à composer, sur un premier élément de réseau, un message comportant une indication précisant si un support vocal prend en charge ou non une continuité d'appel, et à déclencher une transmission du message à un second élément de réseau.
PCT/US2013/063239 2013-10-03 2013-10-03 Scénarios de mobilité volte avec des supports vocaux ims et non-ims WO2015050547A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2013/063239 WO2015050547A1 (fr) 2013-10-03 2013-10-03 Scénarios de mobilité volte avec des supports vocaux ims et non-ims

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2013/063239 WO2015050547A1 (fr) 2013-10-03 2013-10-03 Scénarios de mobilité volte avec des supports vocaux ims et non-ims

Publications (1)

Publication Number Publication Date
WO2015050547A1 true WO2015050547A1 (fr) 2015-04-09

Family

ID=52779001

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/063239 WO2015050547A1 (fr) 2013-10-03 2013-10-03 Scénarios de mobilité volte avec des supports vocaux ims et non-ims

Country Status (1)

Country Link
WO (1) WO2015050547A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017035691A1 (fr) * 2015-08-28 2017-03-09 Apple Inc. Dispositif, système et procédure d'établissement d'un appel volte
WO2017035697A1 (fr) * 2015-08-28 2017-03-09 华为技术有限公司 Procédé permettant d'établir un support vocal et dispositif de réseau d'accès
CN106856472A (zh) * 2015-12-09 2017-06-16 展讯通信（上海）有限公司 基于VoLTE的视频通话方法、装置及移动终端
WO2018045834A1 (fr) * 2016-09-08 2018-03-15 华为技术有限公司 Procédé et appareil de traitement de service volte
CN108811006A (zh) * 2017-05-02 2018-11-13 电信科学技术研究院 一种信息处理方法及装置
CN109792799A (zh) * 2017-03-20 2019-05-21 华为技术有限公司 一种业务通信方法及设备
CN109964505A (zh) * 2016-12-05 2019-07-02 华为技术有限公司 一种创建语音承载的方法和装置
US10986219B2 (en) 2018-06-19 2021-04-20 At&T Intellectual Property I, L.P. LTE fault-tolerant signaling approach
CN115834549A (zh) * 2022-11-24 2023-03-21 中国联合网络通信集团有限公司 通话切换方法、装置、电子设备和计算机可读介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100296484A1 (en) * 2009-05-21 2010-11-25 Htc Corporation Method of handling call in handover in wireless communication system and wireless communication device using the same
US20100329243A1 (en) * 2009-06-29 2010-12-30 Adrian Buckley System And Method For Voice Service In An Evolved Packet System
US20120069750A1 (en) * 2010-09-16 2012-03-22 Apple Inc. Method to control reconfiguration of multiple radio access bearers in a wireless device
US20120189016A1 (en) * 2011-01-21 2012-07-26 Research In Motion Limited Network Apparatus and Process to Determine the Connection Context for Connections Used for (Local) Offloading
US20120224564A1 (en) * 2009-11-09 2012-09-06 Samsung Electronics Co. Ltd. Method and system to support single radio video call continuity during handover

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100296484A1 (en) * 2009-05-21 2010-11-25 Htc Corporation Method of handling call in handover in wireless communication system and wireless communication device using the same
US20100329243A1 (en) * 2009-06-29 2010-12-30 Adrian Buckley System And Method For Voice Service In An Evolved Packet System
US20120224564A1 (en) * 2009-11-09 2012-09-06 Samsung Electronics Co. Ltd. Method and system to support single radio video call continuity during handover
US20120069750A1 (en) * 2010-09-16 2012-03-22 Apple Inc. Method to control reconfiguration of multiple radio access bearers in a wireless device
US20120189016A1 (en) * 2011-01-21 2012-07-26 Research In Motion Limited Network Apparatus and Process to Determine the Connection Context for Connections Used for (Local) Offloading

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017035697A1 (fr) * 2015-08-28 2017-03-09 华为技术有限公司 Procédé permettant d'établir un support vocal et dispositif de réseau d'accès
WO2017035691A1 (fr) * 2015-08-28 2017-03-09 Apple Inc. Dispositif, système et procédure d'établissement d'un appel volte
CN106856472B (zh) * 2015-12-09 2019-10-25 展讯通信（上海）有限公司 基于VoLTE的视频通话方法、装置及移动终端
CN106856472A (zh) * 2015-12-09 2017-06-16 展讯通信（上海）有限公司 基于VoLTE的视频通话方法、装置及移动终端
WO2018045834A1 (fr) * 2016-09-08 2018-03-15 华为技术有限公司 Procédé et appareil de traitement de service volte
CN109964505B (zh) * 2016-12-05 2021-02-12 华为技术有限公司 一种创建语音承载的方法和装置
CN109964505A (zh) * 2016-12-05 2019-07-02 华为技术有限公司 一种创建语音承载的方法和装置
US11228936B2 (en) 2017-03-20 2022-01-18 Huawei Technologies Co., Ltd. Service communication method and device
CN109792799A (zh) * 2017-03-20 2019-05-21 华为技术有限公司 一种业务通信方法及设备
CN109792799B (zh) * 2017-03-20 2021-06-01 华为技术有限公司 一种业务通信方法及设备
CN108811006B (zh) * 2017-05-02 2022-01-07 大唐移动通信设备有限公司 一种信息处理方法及装置
CN108811006A (zh) * 2017-05-02 2018-11-13 电信科学技术研究院 一种信息处理方法及装置
US11758442B2 (en) 2017-05-02 2023-09-12 Datang Mobile Communications Equipment Co., Ltd. Information processing method and device
US10986219B2 (en) 2018-06-19 2021-04-20 At&T Intellectual Property I, L.P. LTE fault-tolerant signaling approach
US11457102B2 (en) 2018-06-19 2022-09-27 At&T Intellectual Property I, L.P. LTE fault-tolerant signaling approach
CN115834549A (zh) * 2022-11-24 2023-03-21 中国联合网络通信集团有限公司 通话切换方法、装置、电子设备和计算机可读介质
CN115834549B (zh) * 2022-11-24 2024-04-02 中国联合网络通信集团有限公司 通话切换方法、装置、电子设备和计算机可读介质

Similar Documents

Publication Publication Date Title
CN106664616B (zh) 解决无线网络中的竞争切换条件
US8848666B2 (en) Handover of emergency calls from a circuit switched to a packet switched access network
WO2015050547A1 (fr) Scénarios de mobilité volte avec des supports vocaux ims et non-ims
CN108476448B (zh) 一种业务处理方法及ims核心网设备
KR102176923B1 (ko) 이동 통신 시스템에서 호 서비스의 품질을 높이는 방법 및 장치
CN110741678A (zh) 一种切换业务承载网络的方法、设备及计算机存储介质
US9521590B2 (en) Multi-bearer connection control
EP3096584B1 (fr) Optimisation de retard de transfert
US10966260B2 (en) Device, system and method for VoLTE setup
WO2013110293A9 (fr) Etablissement d'une session vocale ims par l'intermédiaire d'un réseau à commutation de paquets et d'une session vocale d'urgence par l'intermédiaire d'un réseau à commutation de circuits
WO2017220158A1 (fr) Contrôle de politique d'applications de bord mobile
CN110719613B (zh) 一种建立语音业务的方法及装置
JPWO2016185962A1 (ja) 移動通信システム、通信制御装置、移動管理エンティティ及び移動通信方法
US8483182B1 (en) Single radio voice call continuity handover of calls with video media from a circuit switched access network
US10506421B2 (en) Methods, apparatuses, system, related computer programs and data structures for subscription information delivery
US8908643B2 (en) Handover of priority calls from a circuit switched access network with single radio voice call continuity
WO2020049347A1 (fr) Transfert de session vocale de réseau local sans fil (wlan) à cellulaire déclenché par l'utilisateur
KR20160084516A (ko) VoLTE(Voice over Long Term Evolution) 시스템 및 그 제어방법과 및 이 시스템에 포함되는 PGW(PDN Gateway) 및 CSCF(Call Session Control Function)과 그 제어방법
WO2017063668A1 (fr) Rétention de données pour itinérance à routage de rattachement s8
WO2016023587A1 (fr) Coordination d'initiation de modification de qualité de service
JP2015115767A (ja) 移動通信システム、移動局、ネットワーク装置及び移動通信方法
KR20150026235A (ko) 호 처리 통합형 통화 연속성 제공 방법 및 장치

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

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

Country of ref document: EP

Kind code of ref document: A1