Device, system and method for voltaic setup

Abstract

User equipment, including: a transceiver configured to establish a connection to an LTE (Long Term Evolution) network and an IMS (Internet Protocol Multimedia Subsystem); and a processor configured to run a VoLTE (Voice over LTE) calling application with additional user equipment, wherein the processor is configured to receive an input to run the VoLTE calling application, and wherein the processor is configured to generate a data packet, including an instruction to trigger a procedure to establish a dedicated carrier, where the transceiver is configured to transmit the data packet to one of the LTE network and the IMS, where the specification triggers the procedure for setting up a dedicated carrier, which is to be performed during a SIP (Session Initiation Protocol) signal exchange procedure.

Description

BACKGROUND INFORMATION

[0001] A first station can be configured to communicate wirelessly with a second station. Specifically, the first station can send data to or receive data from the second station over a wired or wireless communication network. The first and second stations can use the network to communicate using a variety of different applications. For example, the first station can be a MO-UE (Mobile Originating, mobile phone as the calling device, UE = User Equipment), while the second station can be an MT-UE (Mobile Terminating, mobile phone as the destination device) for a voice call. The voice call can be conducted in a variety of ways. For example, if the MO-UE or MT-UE is connected to a legacy network, the voice call can be conducted using circuit switching.In another example, if the MO or MT UEs are connected to an IP (Internet Protocol) data transmission network, the voice call can be made using Voice over IP (VoIP). More precisely, if the network is an LTE (Long Term Evolution) network, the VoIP call can be a VoLTE (Voice over LTE) call.

[0002] When a VoLTE call is initiated, the MO and MT UEs can perform a setup procedure. First, when the MO and MT UEs connect to the LTE network, each UE can be assigned to one or more standard carriers that provide a best-effort service when exchanging data with the LTE network. Furthermore, when a specific application such as VoLTE calling is used, each UE can be assigned to a dedicated carrier that provides a dedicated tunnel for data to be transmitted in relation to the VoLTE call (e.g., voice data). The dedicated carrier can provide a variety of functionalities, such as improving throughput or guaranteeing a specific bit rate for the transmitted data. The setup procedure involves various operations.However, due to the sequence of processes, the timing of the processes, the execution of the processes, etc., user-friendliness can be negatively affected, for example by introducing delays.

[0003] The state of the art document WO 2015 / 016546 A1 describes a paging method and paging device for an IMS service.

[0004] The state-of-the-art document US 2014 / 0256343 A1 describes a solution for improving RAN bandwidth efficiency in VoLTE call scenarios.

[0005] The state of the art document US 2014 / 0369343 A1 describes methods, systems and computer-readable media for allocating separate dedicated carriers for separate audio and video streams of a test simulation environment. SUMMARY

[0006] The present invention is defined in independent claims 1 and 9. Advantageous embodiments are specified in the dependent claims. A first embodiment relates to user equipment comprising: a transceiver configured to establish a connection to an LTE (Long Term Evolution) network and an IP-IMS (Internet Protocol Multimedia Subsystem);and a processor configured to run a VoLTE (Voice over LTE) calling application with other user equipment, wherein the processor is configured to receive an input to run the VoLTE calling application, wherein the processor is configured to generate a data packet including a signal to trigger a procedure for establishing a dedicated carrier, wherein the transceiver is configured to transmit the data packet to one of the LTE network and the IMS, wherein the signal triggers the execution of the procedure for establishing a dedicated carrier during a SIP (Session Initiation Protocol) signal exchange procedure.

[0007] Another embodiment relates to a method comprising, on a UE configured to make a VoLTE call with another UE, wherein the UE is connected to an LTE network and an IMS: receiving an input to execute a VoLTE call application; generating a data packet, including a signal to trigger a procedure for establishing a dedicated carrier; and transmitting the data packet to a device connected to the LTE network and the IMS, wherein the signal triggers the execution of the procedure for establishing a dedicated carrier during a SIP signal exchange procedure.

[0008] Another embodiment relates to a network component of an IMS, the network component comprising a transceiver configured to establish a connection to an LTE network and first and second user equipment configured to make a VoLTE call; and a processor configured to receive a SIP invitation from the first user equipment to make the VoLTE call with the second user equipment, wherein the processor is configured to generate a data packet to trigger a procedure for setting up a dedicated carrier, wherein the processor is configured to perform a forwarding operation to transmit the SIP invitation to the second user equipment and to transmit the data packet to a gateway of the IMS, wherein the data packet enables the setup of the dedicated carrier during further SIP signal exchange operations.

[0009] Another embodiment relates to a method comprising: establishing a connection on a network component of an IMS to an LTE network and first and second user equipment configured to make a VoLTE call; receiving a SIP invitation from the first user equipment to make the VoLTE call with the second user equipment; generating a data packet to trigger a method for setting up a dedicated carrier; and performing a forwarding operation to transmit the SIP invitation to the second user equipment and to transmit the data packet to a gateway of the IMS, wherein the data packet enables the setup of the dedicated carrier during further SIP signal exchange operations. BRIEF DESCRIPTION OF THE DRAWINGS Fig. Figure 1 shows an exemplary network arrangement according to some embodiments. Fig. Figure 2 shows an exemplary user equipment configured to set up a dedicated carrier, according to some embodiments. Fig. Figure 3 shows a first exemplary signal transmission diagram for setting up a dedicated carrier by a user equipment operation according to some embodiments. Fig. Figure 4 shows a second exemplary signal transmission diagram for setting up a dedicated carrier by a user equipment operation according to some embodiments. Fig. Figure 5 shows a third exemplary signal transmission diagram for setting up a dedicated carrier by a user equipment operation according to some embodiments. Fig. Figure 6 shows an exemplary method for setting up a dedicated carrier by a user equipment operation according to some embodiments. Fig. Figure 7 shows an exemplary signal transmission diagram for setting up a dedicated carrier through a network operation according to some embodiments. Fig. Figure 8 shows an exemplary method for setting up a dedicated carrier by a network operation according to some embodiments. DETAILED DESCRIPTION

[0010] The exemplary embodiments can be further understood with reference to the following description and the attached drawings, where identical elements are designated by the same reference numerals. The exemplary embodiments relate to a device, a system, and a method for setting up a dedicated carrier for a VoLTE (Voice over Long Term Evolution) call. In particular, the exemplary embodiments provide a mechanism by which the dedicated carrier can be set up or its setup prepared to eliminate a delay in performing a setup procedure for the VoLTE call. In a first embodiment, a MO-UE (Mobile Originating User Equipment) can perform an operation to prepare the setup of the dedicated carrier.In a second embodiment, a network component can perform a process to set up the dedicated carrier based on an early trigger.

[0011] It should first be noted that the exemplary embodiments described relate to a VoLTE call. However, the VoLTE call is only an example. In some exemplary embodiments, VoLTE may be a component of the communication carried out by the MO-UE. For example, VoLTE may be a component of video-over-LTE functionality. Thus, any use of a VoLTE call or a voice call may be representative of other communication calls, including video calls.

[0012] Fig. Figure 1 shows an exemplary network arrangement 100 according to some embodiments. The exemplary network arrangement 100 includes the UEs 110-114. In this example, it is assumed that each different user uses all UEs 100-114. For example, a first user can use UE 110, a second user can use UE 112, and a third user can use UE 114. Those skilled in the art will recognize that the UEs 110-114 can be any type of electronic component configured to communicate over a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearable devices, etc.It should also be clarified that an actual network configuration can include any number of UEs used by any number of users and assigned to any number of those users, with the users being assigned to one or more of the UEs. That is to say, the example with three (3) UEs 110-114 is provided for illustrative purposes only. However, as is evident from the description herein, the exemplary embodiments can refer to the case where at least two UEs 110-114 are present in the network configuration 100.

[0013] All UEs 110-114 can be configured to communicate with one or more networks. In this example, the networks with which the UEs 110-114 can communicate are a legacy radio access network (RAN) 120, an LTE radio access network (LTE-RAN) 122, and a wireless local area network (WLAN) 124. In this example, all networks 120-124 are wireless networks with which the UEs 110-114 can communicate wirelessly. However, it should be clarified that the UEs 110-114 can also communicate with other types of networks that use a wired connection. Regarding the exemplary embodiments, the UEs 110-114 can connect to the LTE radio access network 122 to make VoLTE calls with other UEs. For example, the UEs 110-114 can have an LTE chipset to communicate with the LTE radio access network 122.As already mentioned, the use of three (3) networks is only exemplary, and any other number of networks may exist with which the UEs 110-114 can communicate.

[0014] The legacy 120 radio access network and the LTE 122 radio access network are segments of mobile networks that can be deployed by mobile network operators (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). These 120 and 122 networks can include, for example, base stations (Node Bs, eNode Bs, HeNBs, etc.) configured to send and receive data traffic from UEs equipped with the appropriate cellular chipset. Examples of legacy 120 radio access networks include those commonly referred to as 2G and / or 3G networks and can support circuit-switched voice calls and packet-switched data operations. Experts will recognize that mobile network operators can also deploy other types of networks, including evolutions of cellular standards, within their mobile networks. The WLAN 124 can support any type of wireless local area network (WiFi, Hotspot, IEEE 802.11x networks, etc.).) include. Experts will recognize that in the United States alone, there may be thousands, hundreds of thousands, or more different types of WLAN deployed. For example, WLAN 124 could be the user's home network, the user's work network, or a public network (e.g., in a city park, café, etc.). Generally, WLAN 124 includes one or more access points that allow UEs 110-114 to communicate with WLAN 124. As stated above, the exemplary embodiments refer to UEs 110-114 using the LTE radio access network 122 to make VoLTE calls.

[0015] In addition to networks 120-124, network arrangement 100 also includes a cellular core network 130 and the Internet 140. The cellular core network 130, the legacy radio access network 120, and the LTE radio access network 122 can be considered a single cellular network associated with a specific mobile network operator (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). The cellular core network 130 can be viewed as the interconnected set of components that manages the operation and data traffic of the cellular network. The interconnected components of the cellular core network 130 can include any number of components such as servers, switches, routers, etc. The cellular core network 130 also manages the data traffic flowing between the cellular network and the Internet 140.

[0016] The Network Arrangement 100 also includes an IP-IMS (IP Multimedia Subsystem) 150. The IMS 150 can be generally described as an architecture for providing multimedia services to UEs 110-114 using the IP protocol. The IMS 150 can include a variety of components to accomplish this task. For example, a typical IMS 150 includes a HSS (Home Subscriber Server) that stores subscriber information for a user of UEs 110-114. Thus, when the user's corresponding UE registers with the IMS 150 (e.g., establishes a connection to it), the subscriber information can be used to determine various characteristics. For example, this subscriber information is used to provide the appropriate multimedia services, such as a VoLTE call, to the user. The IMS 150 can communicate with the mobile core network 130 and the Internet 140 to provide multimedia services for the UEs 110-114.The IMS 150 is shown in close proximity to the 130 mobile core network because the mobile network operator typically implements the functionality of the IMS 150. However, this is not necessarily the case, for example, if the IMS 150 is provided by another party.

[0017] Thus, the network configuration 100 enables the UEs 110-114 to perform functionalities generally associated with computers and mobile networks. For example, the UEs 110-114 can make VoLTE calls to other parties, they can search the Internet 140 for information, they can stream multimedia data to the UEs 110-114, etc.

[0018] Network arrangement 100 can also include a network services backbone 160, which communicates either directly or indirectly with the Internet 140 and the mobile core network 130. The network services backbone 160 can be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a range of services which can be used to extend the functionalities of UEs 110-114 in communication with the various networks. The network services backbone 160 can interact with UEs 110-114 and / or networks 120, 122, 124, 130, and 140 to provide these extended functionalities.

[0019] The Network Services Backbone 160 can be provided by one entity or a set of entities. In one example, the Network Services Backbone 160 is provided by the provider of one or more of the UEs 110-114. In another example, the Network Services Backbone 160 is provided by the mobile network operator. In yet another example, the Network Services Backbone 160 is provided by a third party that is not affiliated with the mobile network operator or the provider of the UEs 110-114.

[0020] The exemplary embodiments refer to UEs 110-114, which perform a VoLTE call. For example, UE 110 can be the MO-UE, which invites another UE, such as UE 112, which can be an MT-UE (Mobile Terminating UE, mobile phone as the target terminal). Initially, UEs 110-114 establish a connection to the LTE radio access network 122. Those skilled in the art will recognize that any mapping method can be used to connect UEs 110-114 to the LTE radio access network 122. As explained above, for example, the LTE radio access network 122 can be assigned to a specific mobile network operator with whom UEs 110-114 and / or their users have a contract and login credentials (e.g., stored on a SIM card). After detecting the presence of the LTE radio access network 122, the UEs 110-114 can transmit the corresponding login information for assignment to the LTE radio access network 122.More precisely, the UEs 110-114 can be assigned to a specific base station (e.g., an eNB of the LTE radio access network 122).

[0021] When UEs 110-114 are assigned to and connect to LTE radio access network 122, one or more standard carriers can be established for UEs 110-114. A carrier can determine how data is handled during transmission over the network. This means that the carrier can be a set of network parameters that determine data-specific handling based on type or application association. Accordingly, LTE radio access network 122 can handle one type of data in one way and another type of data in a different way. For example, the first type of data can be prioritized, so LTE radio access network 122 handles this data in a special way. It should be noted that the carrier can also determine the handling based on user identity or other identification parameters.

[0022] One type of carrier established upon initial connection to the LTE radio access network 122 is a default carrier. The LTE radio access network 122 can assign the default carrier via the associated eNB, which remains in place as long as the UE is connected to the LTE radio access network 122. The default carrier can provide a best-efforts service for data transmitted over the LTE radio access network 122. Depending on various network conditions currently present at the LTE radio access network 122, all available resources can be allocated to the data transmitted over the default carrier. The default carrier can be assigned to a specific IP address, and multiple default carriers can be configured for a single UE. Each default carrier can be assigned a Quality of Service (QoS) Quality Class Indicator (QCI) from 5 to 9, which applies to non-GBR (Guaranteed Bit Rate) carriers.Applications that can use the standard carrier are those where data delivery is less time-sensitive. For example, signal transmission messages such as SIP (Session Initiation Protocol) can use the standard carrier. Other examples include smartphone data traffic, including video, chat, email, browsing, etc.

[0023] Another type of carrier that can be established between the UE and the LTE radio access network 122 is a dedicated carrier. The dedicated carrier can provide a dedicated tunnel for specific data traffic. One application that uses the dedicated tunnel is VoLTE voice data, which is used when making a VoLTE call. The dedicated carrier can be an additional carrier on top of the standard carrier, established at a time after the standard carrier has been established (e.g., when making a VoLTE call). Because only standard carriers require separate IP addresses, and the dedicated carrier is provided on top of an established standard carrier, the dedicated carrier does not require a separate IP address. However, the dedicated carrier is linked to the previously established standard carrier.In particular, a value specified during the setup of the dedicated carrier can be used to link the dedicated carrier to the default carrier. The dedicated carrier can use the same QCI as the default carrier, or it can use a different QCI that relates to a GBR carrier. The dedicated carrier can use Traffic Flow Templates (TFTs) to provide special handling for specific services, such as VoLTE calling. This means that the TFTs can also determine the rules for when to use the dedicated carrier based on the application running.

[0024] Regarding the operation of the standard carrier and the dedicated carrier, the standard carrier is established after the UE connects to the LTE radio access network 122. Specifically, the LTE radio access network 122 assigns the standard carrier to the UE. Subsequently, while still connected to the LTE radio access network 122, the UE can perform VoLTE calling functionality. For example, UE 110 can be the MO-UE, while UE 112 can be the MT-UE. Therefore, the MT-UE can also be connected to the LTE radio access network 122 and can have a standard carrier assigned and configured. When the VoLTE calling functionality is performed, various signal transmission messages are transmitted between UE 110 and UE 112 via the LTE radio access network 122 and the IMS 150 through their respective standard carriers. This means that a setup procedure for VoLTE calls can be carried out.Once the VoLTE call has been established, based on the successful transmission of the various signal transmission messages, the UE 110 and UE 112 can be connected to conduct the VoLTE call. Specifically, the dedicated carrier for the UE 110 and UE 112 can be configured for the VoLTE data to be transmitted.

[0025] The setup procedure for VoLTE calls may initially involve the UE 110 establishing a connection to the IMS 150. It should be noted that this setup procedure can be a more general process performed at various other times and is not necessarily triggered by the VoLTE call itself. For example, the connection to the IMS 150 may occur every time the UE 110 connects to the LTE radio access network 122. However, it should also be noted that a connection to the IMS 150 may be required to use the VoLTE call functionality.

[0026] The connection to the IMS 150 can be established through an initial assignment to the eNB of the LTE radio access network 122. Subsequent connections to the IMS 150 can be established via various components of the IMS 150. In particular, an attachment procedure can be performed when connecting the UE 110 to the IMS 150. For example, the IMS 150 can include a Mobility Management Entity (MME) and a Packet Data Network Gateway (PGW). These components can be responsible for at least one operation when the VoLTE calling functionality is used. Specifically, the MME can be a control node for the LTE radio access network 122, performing paging and marking operations for a silent mode of the UE 110. More precisely, the MME can perform operations related to carrier activation and / or deactivation. The MME can also select an SGW (Serving Gateway) when initially attaching to the IMS 150.

[0027] The SGW can be configured to route and forward data packets for the UE 110. For example, the SGW can manage and store contexts for the UE 110, such as carrier service parameters, internal network line information, and so on. The MME can also authenticate the UE 110 (via the HSS), thus identifying the services available to the UE 110, including VoLTE calling functionality. The PGW can also be configured to provide connectivity between the UE 110 and an external PDN by acting as an entry / exit point for data packet traffic for the UE 110. It should be noted that the IMS 150 can connect to multiple PGWs to access a corresponding number of PDNs. Thus, the UE 110 can be enabled to exchange data packets with multiple PDNs via the IMS 150's PGW.During the attachment process, UE 110 can attach itself if a default APN (Access Point Name) is an IMS APN and the IMS PDN is set up during the default carrier determination. However, if the default APN is not an IMS APN, the IMS PDN can be set up after the attachment process.

[0028] Once the attachment process is complete and the UE 110 has established a connection to the IMS 150, an IMS registration process can be initiated. This process enables access to the identified multimedia services. Specifically, the IMS registration process can involve registering at least one IMPU (IP Multimedia Public Identity), such as a telephone number for the UE 110. The IMS 150 can then authenticate an IMPI (IP Multimedia Private Identity). The registration process can be initiated by the UE 110 by transmitting a SIP registration message to a P-CSCF (Proxy-CSCF (Call Session Control Function)). Using further message forwarding operations, such as an I-CSCF (Interrogating CSCF) and an S-CSCF (Serving CSCF), authentication can be performed via the HSS.Specifically regarding VoLTE calling functionality, the IMS registration process can include the P-CSCF and a PCRF (Policy and Charging Rules Function). The P-CSCF can be a SIP proxy that provides an initial point of contact between the UE 110 and the IMS 150. The P-CSCF can also be positioned along the entire signal transmission path to monitor all signals and ensure that the UE 110 is not behaving erratically, for example, by changing a known signal transmission route or disregarding a line policy. The PCRF can determine policy rules within the IMS 150. The PCRF aggregates information to and from the IMS 150 to support rule creation and policy decisions for the multimedia services provided by the UE 110.With particular regard to VoLTE call functionality, the PCRF can act as a mediator of network resources for the IMS 150 to establish the call and allocate the requested bandwidth to the dedicated carrier.

[0029] By connecting and registering the UE 110 with the IMS 150, the UE 110 user can choose to use the VoLTE calling functionality. The VoLTE calling setup process can then receive input from the user. For example, the user can launch a VoLTE calling application and provide / select an identity for the MT-UE 112. To make the VoLTE call, the UE 110 can transmit a SIP invitation to the UE 112 via the P-CSCF. Specifically, the SIP invitation can be transmitted to the P-CSCF, which is then forwarded to the UE 112. The UE 112 can respond with a SIP:100 trial signal back to the P-CSCF (e.g., an advanced search that requires a significant amount of time causes a forking proxy to send the 100 trial response), which is then forwarded back to the UE 110.The UE 112 can also respond with a SIP:183 session progress signal back to the P-CSCF (e.g., additional information for the VoLTE call during the setup phase), which is then also forwarded back to the UE 110.

[0030] Once the IMS 150 has determined that the VoLTE call is to be made via SIP signal exchange, the P-CSCF can initiate the dedicated carrier for the VoLTE call. Specifically, a corresponding signal can be forwarded from the P-CSCF to the PCRF. The PCRF can also initiate the dedicated carrier for the VoLTE call. Specifically, another corresponding signal can be forwarded from the PCRF to the PGW. Subsequently, the dedicated carrier can be configured for the UE 110. Another operation that can be performed is setting the QCI to 1 for the VoLTE call, which is signaled from the MME to the eNB. With the dedicated carrier created and configured, the VoLTE call can then be made by the UE 110.

[0031] Experts will recognize that the conventional VoLTE call setup procedure uses the PGW to trigger the dedicated carrier, which is established when the P-CSCF initiates the dedicated carrier activation for the VoLTE call and the PCRF confirms that sufficient resources are available to set up the dedicated carrier. However, this part of the VoLTE call setup procedure introduces a delay of at least one second, impacting the user experience.

[0032] Several aspects of the exemplary embodiments provide a mechanism to reduce and / or eliminate the delay. That is, the mechanism in the exemplary embodiments introduces a solution to save time during VoLTE call setup. Specifically, the activation of the dedicated carrier setup can be performed using several different operations prior to the conventional operation. As described in more detail below, these operations can be performed by the MO-UE 110 and / or the IMS 150.In a first set of mechanisms, implemented by UE 110, a first proposed mechanism can update an existing RRC (Radio Resource Control) procedure to use a new cause identification; a second proposed mechanism can update a NAS (Non-Access Stratum) used by UE 110 to request a dedicated carrier resource allocation procedure; and a third proposed mechanism can update the NAS with a new cause identification. In a second mechanism, implemented by IMS 150, a fourth proposed mechanism introduces a new PCC (Policy and Charging Control) procedure.

[0033] The first set of mechanisms implemented by UE 110 shows Fig. 2. An exemplary UE 200 configured with functionalities for dedicated carriers according to some embodiments. In particular, the UE 200 is configured to execute a plurality of applications that perform the respective functionalities of setting up the dedicated carrier for the VoLTE call according to the exemplary embodiments. Accordingly, the UE 200 can be used by Fig. 2 of the MO-UE 110. However, experts will recognize that the UE 200 can also represent the other UEs 112 and 114. It should be noted, however, that the other UEs 112 and 114 may not necessarily be able to perform the functionalities described below in relation to the UE 110.

[0034] The UE 200 can represent any electronic device configured to perform wireless functionalities, and it can be representative of one or more of the UEs 110-114. For example, the UE 200 can be a portable device, such as a smartphone, tablet, phablet, laptop, body-worn device, etc. In another example, the UE 200 can be a stationary device, such as a desktop terminal. The UE 200 can be configured to perform cellular and / or Wi-Fi functionalities. The UE 200 can include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230.The other components 230 may include, for example, an audio input device, an audio output device, a battery / accumulator, a data acquisition device, connections for the electrical connection of the UE 200 to other electronic devices, etc.

[0035] The processor 205 can be configured to run a variety of UE 200 applications. For example, these applications can include a web browser when connected to a communications network via the transceiver 225. Therefore, when connected to the LTE radio access network 122, the web browser data can use the standard carrier. In another example, the processor 205 can run a VoLTE calling application 235, which enables the UE 200 to perform VoLTE calling functionality similar to the UE 112. The VoLTE calling application 235 can also be configured to perform the VoLTE call setup procedure, such as carrying out the steps described above. In yet another example, the processor 205 can run a dedicated carrier 240 application.As described in more detail below, the Dedicated Carrier 240 application can perform the mechanism mentioned above for triggering the setup of the dedicated carrier for use in VoLTE calls. This means that the Dedicated Carrier 240 application can be used in conjunction with the VoLTE Calling application 235, specifically in the VoLTE call setup procedure.

[0036] It should be noted that the applications described above, each of which is an application (e.g., a program) executed by the Processor 205, are only examples. The functionality associated with the applications may also be represented as a separate, embedded component of the UE 200 or as a modular component coupled to the UE 200, such as an integrated circuit with or without firmware. Additionally, in some UEs, the functionality described for the Processor 205 is distributed between two processors: a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of a UE.

[0037] Memory 210 can be a hardware component configured to store data relating to operations performed by UE 200. Specifically, memory 210 can store data relating to the various applications 235-240. For example, the VoLTE calling application 235 can utilize a phonebook functionality that stores contact information for other users and UEs. Display device 215 can be a hardware component configured to show data to a user, while I / O device 220 can be a hardware component that allows the user to input data. It should be noted that display device 215 and I / O device 220 can be separate components or integrated together, such as a touchscreen.

[0038] The Transceiver 225 can be a hardware component configured to transmit and / or receive data. This means that the Transceiver 225 can enable communication with other electronic devices, directly or indirectly, over a network based on the network's operating frequency. The Transceiver 225 can operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies) related to VoLTE calling functionality. Thus, an antenna (not shown) connected to the Transceiver 225 can enable it to operate on the LTE frequency band.

[0039] Fig. Figure 3 shows a first exemplary signal transfer diagram 300 for setting up a dedicated carrier by a UE operation according to some embodiments. As described above, the exemplary embodiments include a first set of mechanisms by which the MO-UE 110 performs an operation to trigger the dedicated carrier during setup for the VoLTE call. The signal transfer diagram 300 relates to when the UE 110 executes the VoLTE call application 235 and the dedicated carrier application 240 during the VoLTE call setup procedure. In particular, the signal transfer diagram 300 relates to the operation performed on the UE 110 such that the dedicated carrier is set up in such a way as to reduce and / or eliminate the delay caused by the signal transmission between the P-CSCF and the PCRF after the SIP signal transmission.It can be assumed that the other MT-UE 112 is also capable of making the VoLTE call and will properly perform all necessary operations when establishing the VoLTE call.

[0040] Signal Transfer Diagram 300 illustrates a setup procedure for VoLTE calls. Signal Transfer Diagram 300 essentially includes similar operations to those described above. First, the MO-UE 110 can establish a connection to an eNB 122A of the LTE radio access network 122 and the IMS 150 using an append procedure 305. Specifically, the UE 110 can detect the presence of the LTE radio access network 122 and transmit a connection request to the eNB 122A. By performing an assignment procedure, the UE 110 can establish a connection to the LTE radio access network 122 via the eNB 122A. Furthermore, when establishing the connection, the eNB 122A can assign a default carrier to the LTE radio access network 122 for the UE 110 and set up the default carrier. The attachment method 305 can therefore also be used with components of the IMS 150 such as an MME 150A and a PGW 150B.Attachment procedure 305 can be essentially identical to the attachment procedure described above. The MO-UE 110 can also perform an IMS registration 310 when connecting to the IMS 150. Therefore, IMS registration 310 can also be used with components of the IMS 150 such as a PCRF 150C and a P-CSCF 150D. It should be noted that the MT-UE 112 performs essentially similar operations (not shown) to establish a connection to the LTE radio access network 122 and the IMS 150.

[0041] With the UE 110 connected to the LTE radio access network 122 and the IMS 150, and the IMS registration process completed to indicate that the UE 110 is configured to perform VoLTE calling functionality, the UE 110 can execute the VoLTE calling application 235. Initiating the VoLTE calling application 235 can be used to initiate the operations performed by the dedicated carrier application 240. In particular, the RRC device 315 can be performed according to the first exemplary mechanism. While the conventional operations of the RRC device can also be performed, the exemplary embodiments further utilize a new cause identification. Specifically, the RRC device 315 incorporates a new RRC device cause on the LTE radio access network 122 via a signal transmission to the eNB 122A.If the RRC setup relies on the MO-UE 110 conducting a voice call, the MO-UE 110 can signal a VoLTE cause identification to indicate to the LTE radio access network 122 that it should reserve a QCI1 resource (i.e., a QCI with the value 1) and trigger a dedicated carrier setup after the RRC setup 315. It should be noted that a video call can reserve both QCI1 and QCI2. Thus, triggering the dedicated carrier setup can now be an operation performed while the subsequent signal transmission in the VoLTE call setup procedure is underway. Therefore, in this mechanism, the dedicated carrier setup and the VoLTE call setup procedure can be considered to be performed in parallel.In this way, the setup procedure for VoLTE calls no longer has to wait until the SIP 183 signal transmission is completed when the dedicated carrier is triggered.

[0042] After the RRC setup procedure 315 is completed, the remaining operations of the VoLTE call setup procedure can be performed in addition to the parallel execution of the dedicated carrier triggering. Thus, the SIP signal transmission can be carried out, whereby the SIP invitation 320 can be transmitted from MO-UE 110 to P-CSCF 150D; the SIP invitation 325 can be transmitted from P-CSCF to MT-UE 112; the SIP 100 attempt 330 can be transmitted from MT-UE 112 to P-CSCF 150D; and the 100 attempt signal 335 can be transmitted from P-CSCF 150D to MO-UE 110. The SIP: 183 session progress 340 can be transferred from the MT-UE 112 to the P-CSCF 150D and the SIP: 183 session progress 345 can be transferred from the P-CSCF 150D to the MO-UE 110.While this SIP signal transmission is taking place, the signal to trigger dedicated carrier 350 can be transmitted from the PCF 150D to the PCF 150C, and the signal to trigger dedicated carrier 355 can be transmitted from the PCF 150C to the PGW 150B. Dedicated carrier 360 is then established, and the VoLTE call can be made.

[0043] Although signal transmission diagram 300 shows that the dedicated carrier is triggered after the SIP: 183 session progress signal transmission, it should be noted that this is not representative of the operations of the exemplary embodiments. In contrast, the SIP signal transmission, including the invitation, the 100 trial, and the 183 session progress, can be performed in the sequence shown, but the triggering of the dedicated carrier can be performed in parallel with this SIP signal transmission and is not performed after the SIP signal transmission.

[0044] Fig. Figure 4 shows a second exemplary signal transfer diagram 400 for setting up a dedicated carrier by a UE operation according to some embodiments. The signal transfer diagram 400 relates to when the UE 110 executes the VoLTE call application 235 and the dedicated carrier application 240 when performing the VoLTE call setup procedure. That is, the signal transfer diagram 400 also relates to the first set of mechanisms by which the MO-UE 110 performs an operation to trigger the dedicated carrier during the VoLTE call setup. Signal transmission diagram 400 refers to the operation performed on the UE 110, whereby the dedicated carrier is set up in such a way as to reduce and / or eliminate the delay caused by the signal transmission between the P-CSCF 150D and the PCRF 150C after the SIP signal transmission.It can be assumed that the other MT-UE 112 is also capable of making the VoLTE call and will properly perform all necessary operations when establishing the VoLTE call.

[0045] Signal Transfer Diagram 400 illustrates a setup procedure for VoLTE calls. Signal Transfer Diagram 400 essentially includes similar procedures to those described above, particularly in relation to Signal Transfer Diagram 300. Fig. 3. Thus, the MO-UE 110 can perform an attachment procedure 405 and an IMS registration 410. With the UE 110 connected to the LTE radio access network 122 and the IMS 150, and the IMS registration procedure completed to indicate that the UE 110 is configured to perform VoLTE calling functionality, the UE 110 can execute the VoLTE calling application 235. The initiation of the VoLTE calling application 235 can be reused to initiate the operations performed by the dedicated carrier application 240. In particular, according to the second exemplary mechanism, the RRC setup and SR (Service Request) 415 and the UL (Uplink) information transfer 420 can be performed. The RRC facility and SR 415 may refer to a conventional procedure.Therefore, conventional procedures can be performed to make the VoLTE call when setting up the RRC and transmitting the appropriate SR, for example, when the MO-UE 110 is in RRC idle mode. It should be noted that the RRC setup and SR 415 may not be performed. For example, the MO-UE 112 may already be in a connected RRC state, which may then only involve the MO-UE 110 sending UL Information Transmission 420. UL Information Transmission 420 can be a subsequent procedure after the completion of the RRC setup and SR 415, or a parallel procedure together with the RRC setup and SR 415. UL Information Transmission 420 can be a signal transmission procedure from the MO-UE 110 to the MME 150A. UL Information Transfer 420 can be a resource allocation request for dedicated carriers from UE 110.Accordingly, the PGW 150B can trigger a QCI1 setup upon receiving the request to set up the dedicated QCI1 carrier for the VoLTE call. This eliminates the need for the VoLTE call setup process to wait for the SIP 183 signal transmission to complete when the dedicated carrier is triggered.

[0046] In one particular embodiment, 3GPP-TS (Technical Specification (TS) for Third Generation Partnership Project) 24.301 defines a UE procedure. However, the resources are ultimately controlled by the LTE radio access network 122 and are not essentially used as a UE-side operation. The second mechanism described above according to the exemplary embodiments uses this procedure for QCI1 setup while the VoLTE call is being initiated. Accordingly, the UL information transfer 420 can be a message used for UL transmission of NAS or dedicated non-3GPP information. By adapting this message, the UL information transfer 420 can be used for the purposes described above.

[0047] After the UL information transmission 420 is complete, the remaining operations of the VoLTE call setup procedure can be performed in addition to the parallel execution of the dedicated carrier triggering. Thus, the SIP signal transmission can be carried out, whereby the SIP invitation 425 can be transmitted from MO-UE 110 to P-CSCF 150D; the SIP invitation 430 can be transmitted from P-CSCF to MT-UE 112; the SIP: 100 attempt 435 can be transmitted from MT-UE 112 to P-CSCF 150D; and the 100 attempt signal 335 can be transmitted from P-CSCF 150D to MO-UE 110. The SIP: 183 session progress 445 can be transferred from the MT-UE 112 to the P-CSCF 150D and the SIP: 183 session progress 450 can be transferred from the P-CSCF 150D to the MO-UE 110.While this SIP signal transmission is taking place, the signal to trigger dedicated carrier 455 can be transmitted from the PCF 150D to the PCF 150C, and the signal to trigger dedicated carrier 460 can be transmitted from the PCF 150C to the PGW 150B. Accordingly, dedicated carrier 465 is established, and the VoLTE call can be made.

[0048] Although signal transmission diagram 400 shows that the dedicated carrier is triggered after the SIP: 183 session progress signal transmission, it should be noted again that this is not representative of the operations of the exemplary embodiments. In contrast, the SIP signal transmission, including the invitation, the 100 trial, and the 183 session progress, can be performed in the sequence shown, but the triggering of the dedicated carrier can be performed in parallel with this SIP signal transmission and is not performed after the SIP signal transmission.

[0049] Fig. Figure 5 shows a third exemplary signal transfer diagram 500 for setting up a dedicated carrier by a UE operation according to some embodiments.

[0050] Signal transmission diagram 500 refers to when the UE 110 executes the VoLTE call application 235 and the dedicated carrier application 240 during the VoLTE call setup procedure. Specifically, signal transmission diagram 500 refers to the first set of mechanisms by which the MO-UE 110 performs an operation to trigger the dedicated carrier during the VoLTE call setup. Signal transmission diagram 500 describes the operation performed on the UE 110 to configure the dedicated carrier in such a way as to reduce and / or eliminate the delay caused by signal transmission between the P-CSCF 150D and the PCRF 150C following SIP signal transmission.It can be assumed that the other MT-UE 112 is also capable of making the VoLTE call and will properly perform all necessary operations when establishing the VoLTE call.

[0051] Signal Transfer Diagram 500 illustrates a setup procedure for VoLTE calls. Signal Transfer Diagram 500 essentially includes similar procedures to those described above, particularly in relation to Signal Transfer Diagram 300. Fig. 3. Thus, the MO-UE 110 can perform an attachment procedure 505 and an IMS registration 510. With the UE 110 connected to the LTE radio access network 122 and the IMS 150, and the IMS registration procedure completed to indicate that the UE 110 is configured to perform VoLTE calling functionality, the UE 110 can execute the VoLTE calling application 235. The initiation of the VoLTE calling application 235 can be reused to initiate the operations performed by the dedicated carrier application 240. In particular, according to the third exemplary mechanism, the RRC setup 515 and the SR 520 can be performed. The RRC setup 515 can refer to a conventional procedure. Therefore, conventional procedures can be performed when setting up the RRC to make the VoLTE call, for example when the MO-UE 110 is in RRC sleep mode.It should be noted again that the RRC setup 515 cannot be performed if the MO-UE 110 is already in the connected RRC state. The SR 520 can be a subsequent procedure after the completion of the RRC setup 515 or a parallel procedure together with the RRC setup 515. Although the conventional operations of the SR can also be performed, the exemplary embodiments include additional information in the SR 520. Thus, the SR 520 can provide the basis on which the setup of the dedicated carrier is triggered while the other operations of the VoLTE call setup procedure are performed. In this way, the VoLTE call setup procedure no longer has to wait until the SIP 183 signal transmission is completed when the dedicated carrier is triggered.

[0052] In one particular embodiment, the SR 520 can include a new security header type when triggered by a voice call, such as a VoLTE call. Thus, if the SR 520 is based on a voice call, the NAS can use a special security header type to indicate 122 to the LTE radio access network, reserve the QCI1 resource, and trigger the setup of the dedicated carrier after the SR 520 is complete. As mentioned earlier, and with reference to 3GPP-TS 24.301, and more specifically Table 9.3.1, the security header type (Octet 1) includes a set of variables that are not used in the defined version of the protocol. Accordingly, the values ​​can be adapted for use in the third mechanism of the exemplary embodiments.

[0053] Once SR 520 is complete, the remaining steps of the VoLTE call setup procedure can be performed in addition to the parallel execution of the dedicated carrier triggering. This allows for the SIP signal transmission, in which SIP invitation 425 can be transmitted from MO-UE 110 to P-CSCF 150D; SIP invitation 430 can be transmitted from P-CSCF to MT-UE 112; SIP 100 attempt 435 can be transmitted from MT-UE 112 to P-CSCF 150D; and 100 attempt signal 335 can be transmitted from P-CSCF 150D to MO-UE 110. The SIP: 183 session progress 445 can be transferred from the MT-UE 112 to the P-CSCF 150D and the SIP: 183 session progress 450 can be transferred from the P-CSCF 150D to the MO-UE 110.While this SIP signal transmission is taking place, the signal to trigger dedicated carrier 455 can be transmitted from the PCF 150D to the PCF 150C, and the signal to trigger dedicated carrier 460 can be transmitted from the PCF 150C to the PGW 150B. Accordingly, dedicated carrier 465 is established, and the VoLTE call can be made.

[0054] Although signal transmission diagram 400 shows that the dedicated carrier is triggered after the SIP: 183 session progress signal transmission, it should be noted again that this is not representative of the operations of the exemplary embodiments. In contrast, the SIP signal transmission, including the invitation, the 100 trial, and the 183 session progress, can be performed in the sequence shown, but the triggering of the dedicated carrier can be performed in parallel with this SIP signal transmission and is not performed after the SIP signal transmission.

[0055] It should also be noted again that the use of VoLTE calling is only exemplary, and that VoLTE can be a component of a video call. Accordingly, the preceding description can also be applied to video calls. Those skilled in the art will recognize that the use of video calls can include further aspects. The exemplary embodiments can be modified to incorporate these further aspects when conducting the video call, particularly over the LTE radio access network 122 and / or the IMS 150. For example, when using video calls, the operations of the exemplary embodiments may further require QCI2 (for video) in addition to QCI1 (for voice). In another example, when using video calls, the exemplary embodiments may use a first security header in the third mechanism for the VoLTE call and a second security header for the video call.

[0056] Fig. Figure 6 shows an exemplary method 600 for setting up a dedicated carrier by a UE operation according to some embodiments. In particular, method 600 relates to when UE 110 executes the application for dedicated carriers 240 when UE 110 is the MO in the VoLTE call. Thus, method 600 relates to the first set of mechanisms in which MO-UE 110 performs an operation to trigger the setup of the dedicated carrier. As mentioned earlier, it can be assumed that UE 112, which is the other party to the VoLTE call, has performed all the necessary operations to also participate in the VoLTE call. Method 600 is described with respect to UE 110. Method 600 is described with reference to the network arrangement 100 of Fig. 1, the UE 200 from Fig. 2 and the signal transmission diagrams 300, 400, 500 of Fig. 3, Fig. 4 or 5 described.

[0057] In step 605, the UE 110 establishes a connection to the IMS 150. As explained above, the UE 110 can initially connect to the LTE radio access network 122 via the eNB 122A. Through the various connections between the networks, the UE 110 can also connect to the IMS 150 via the LTE radio access network 122 and the mobile core network 130. Various other operations related to connecting to the different networks and the IMS 150 can be performed, such as setting up a default carrier for the UE 110. In step 610, the UE 110 can register with the IMS 150. This means that the registration process after connecting can be carried out, among other things, to determine the multimedia services that the UE 110 can or is capable of providing, such as VoLTE calling.

[0058] In step 615, the UE 110 receives an input to initiate a VoLTE call. As explained above, the UE 110 can include a VoLTE call application 235. The user can start the VoLTE call application 235. The user can also select an identity from the MT-UE 112 to perform the VoLTE call. This identity can be information or input that initiates the VoLTE call.

[0059] In step 620, the UE 110 can execute the Dedicated Carrier Application 240. The Dedicated Carrier Application 240 can perform an operation to trigger the dedicated carrier during VoLTE call setup. As explained above, the operations can refer to the first set of mechanisms, where the operation is a procedure prior to a SIP signal exchange for the VoLTE call. In the first mechanism, the RRC setup 315 can include a VoLTE cause identification that notifies the eNB 122A to trigger the dedicated carrier setup. In the second mechanism, the UL Information Transfer 420 can include a NAS update by using a dedicated carrier resource allocation request from the UE 110. The third mechanism allows the SR 520 to include a NAS update with a new cause identification using a security header type.Accordingly, the first set of mechanisms refers to the generation and transmission of a modified data packet to indicate to the LTE radio access network 122 and / or the IMS 150 to trigger the procedure for setting up the dedicated carrier.

[0060] In step 625, the VoLTE call setup procedure can be performed. Specifically, the setup procedure can include the remaining steps, including the SIP signal exchange between MO-UE 110 and MT-UE 112 (e.g., via P-CSCF 150D). Thus, the SIP invitation, SIP 100 attempt, and SIP 183 session progress can be exchanged when establishing the VoLTE call. While the SIP signal exchange is being performed, the dedicated carrier can also be set up simultaneously, starting from the initial dedicated carrier setup in step 620. This means that the dedicated carrier setup aspect of the VoLTE call setup procedure can be triggered to be performed at the same time as the SIP signals are being exchanged. The VoLTE call can then be made in step 630.

[0061] Fig. Figure 7 shows an exemplary signal transfer diagram 700 for setting up a dedicated carrier through a network operation according to some embodiments. Signal transfer diagram 700 relates to when the IMS 150 performs the setup procedure for VoLTE calls such that the dedicated carrier is set up upon receiving an indication that its use may be required. That is, signal transfer diagram 700 relates to the second mechanism by which the IMS 150 uses another policy and load control procedure to trigger the setup of the dedicated carrier for the VoLTE call.Signal transmission diagram 700 refers to the operation performed on the IMS 150, such that the dedicated carrier is set up in such a way as to reduce and / or eliminate the delay caused by the signal transmission between the P-CSCF 150D and the PCRF 150C after the SIP signal transmission.

[0062] Signal Transfer Diagram 700 illustrates a setup procedure for VoLTE calls. Signal Transfer Diagram 700 essentially includes similar procedures to those described above, particularly in relation to Signal Transfer Diagram 300. Fig. 3. Thus, the MO-UE 110 can perform an append procedure 705 and an IMS registration 710. The UE 110 can also initiate the VoLTE call. However, since the signal transmission diagram 700 refers to a network operation, the IMS 150 can determine the initiation of the VoLTE call after the P-CSCF 150D receives the SIP invitation 715.

[0063] Once the P-CSCF 150D receives the SIP invitation 715 from the MO-UE 110, the IMS 150 can perform subsequent operations. A typical operation might be to forward the SIP invitation 720 from the P-CSCF 150D to the MT-UE 112. According to the exemplary embodiments, the P-CSCF 150D also triggers the dedicated carrier operation. That is, the P-CSCF 150D can trigger the dedicated carrier 725 for the VoLTE call immediately after receiving the SIP invitation 715. The P-CSCF 150D can also mark the dedicated carrier triggering as a high-level policy and load control for the PCRF 150C. This can ensure that the PGW 150B immediately triggers the dedicated carrier 730 when the PCRF would normally only request the dedicated carrier after the SIP signal exchange is complete (or after the SIP:183 session progress exchange).

[0064] The remainder of signal transmission diagram 700 can relate to other operations in establishing the VoLTE call, in addition to the parallel execution of triggering the dedicated carrier. Thus, the SIP:100 attempt 735 can be transmitted from MT-UE 112 to P-CSCF 150D; the 100 attempt signal 740 can be transmitted from P-CSCF 150D to MO-UE 110; the SIP:183 session progress 745 can be transmitted from MT-UE 112 to P-CSCF 150D; and the SIP:183 session progress 750 can be transmitted from P-CSCF 150D to MO-UE 110. Accordingly, the dedicated carrier 755 is established, and the VoLTE call can be made. In this way, the setup procedure for VoLTE calls no longer has to wait until the SIP 183 signal transmission is completed when the dedicated carrier is triggered.

[0065] Although signal transmission diagram 700 shows that the dedicated carrier is triggered before each SIP signal transmission, it should be noted again that this is not representative of the operations of the exemplary embodiments. In contrast, the SIP signal transmission, including the invitation, the 100 trial, and the 183 session progress, can be performed in the sequence shown, but the triggering of the dedicated carrier can be performed in parallel with this SIP signal transmission and is not performed after the SIP signal transmission.

[0066] Fig. Figure 8 shows an exemplary method 800 for setting up a dedicated carrier by a network operation according to some embodiments. In particular, method 800 relates to when the IMS 150 performs an operation to trigger the setup of the dedicated carrier. Thus, method 800 relates to the second mechanism in which the P-CSCF 150D performs the operation to trigger the setup of the dedicated carrier. As mentioned earlier, it can be assumed that the UEs 110 and 112 have performed all the necessary operations to participate in the VoLTE call. Method 800 is described with reference to the IMS 150. Method 800 is described with reference to the network arrangement 100 of Fig. 1, the UE 200 from Fig. 2 and the signal transmission diagram 700 from Fig. 7 described.

[0067] In step 805, the IMS 150 receives a SIP invitation for the VoLTE call from the MO-UE 110. Specifically, the SIP invitation 715 can be received by the P-CSCF 150D. In steps 810 and 815, the IMS 150 can perform a conventional operation or an operation according to the exemplary embodiments. Specifically, in step 810, the IMS 150 can forward the SIP invitation 720 from the P-CSCF 150D to the MT-UE 112. In step 815, the IMS 150 can trigger the operation for dedicated carriers in parallel. That is, the IMS 150 can perform these operations simultaneously after the P-CSCF 150D receives the SIP invitation 715 from the MO-UE 110. In step 820, the IMS 150 can perform the remaining operations of the VoLTE setup procedure. In particular, the remaining SIP signal exchange operations (e.g., SIP 100 and SIP 183) can be carried out.Simultaneously, the IMS 150 can continue setting up the dedicated carrier for use in the VoLTE call. Thus, the VoLTE call can be made in step 825.

[0068] The exemplary embodiments provide a device, a system, and a method for improving the setup procedure for VoLTE calls. In particular, the setup procedure for VoLTE calls can be improved by reducing and / or eliminating delays caused by a modified timing sequence for triggering a setup for a dedicated carrier used in the VoLTE call. Specifically, the method can be performed during the setup of the dedicated carrier while simultaneously performing the SIP signal exchange for the VoLTE call setup procedure. In a first set of mechanisms, the improvement can be performed by an operation of the UE (Unified Device). In a second mechanism, the improvement can be performed by an operation of the IMS (Integrated Management System).

[0069] Experts in this field will recognize that the exemplary embodiments described above can be implemented in any suitable software or hardware configurations or combinations thereof. An exemplary hardware platform for implementing the exemplary embodiments might include, for example, an Intel x86-based platform with a compatible operating system, a Windows operating system, a Mac platform and macOS, a mobile device with an operating system such as iOS, Android, etc. In another example, the exemplary embodiments of the method described above can be executed as a program comprising lines of code stored on a non-volatile, machine-readable storage medium, which, upon compilation, can be executed on a processor or microprocessor.

[0070] It is apparent to those skilled in the art that various modifications of the present invention can be made without deviating from the fundamental concept and scope of protection of the invention. The present invention is therefore intended to cover modifications and variants of this invention, provided they fall within the scope of protection of the appended claims and their equivalents.

Claims

[1] User equipment, including: a transceiver configured to establish a connection to an LTE (Long Term Evolution) network and an IMS (Internet Protocol Multimedia Subsystem); and a processor configured to run a VoLTE (Voice over LTE) calling application with additional user equipment, wherein the processor is configured to receive an input to run the VoLTE calling application, and wherein the processor is configured to generate a data packet, including an instruction to trigger a procedure to establish a dedicated carrier, where the transceiver is configured to transmit the data packet to one of the LTE network and the IMS, where the specification triggers the procedure for setting up a dedicated carrier, which is to be performed during a SIP (Session Initiation Protocol) signal exchange procedure. [2] User equipment according to claim 1, wherein the transceiver first establishes a connection to the LTE network, subsequently establishes a connection to the IMS and registers with the IMS. [3] User equipment according to claim 1, wherein the data packet is included in an RRC (Radio Resource Control) procedure with the LTE network. [4] User equipment according to claim 3, wherein the data packet includes a specific cause identification to indicate to the LTE network to reserve a QoS-QCI (Quality of Service indicator) 1. [5] User equipment according to claim 1, wherein the data packet is contained in an UL information transmission (uplink information transmission) with an MME (Mobility Management Entity, mobile supply instance) of the IMS. [6] User equipment according to claim 5, wherein the UL information transmission triggers a QCI1 setup procedure on a PGW (Packet Data Network Gateway) of the IMS. [7] User equipment according to claim 1, wherein the data packet is contained in an SR (Service Request) with the LTE network. [8] User equipment according to claim 7, wherein the data packet includes a security header to reserve a QCI1 resource. [9] Procedures, comprehensive: on a user equipment (UE) configured to make a VoLTE (Voice over Long Term Evolution) call with another UE, where the UE is connected to an LTE network and an IMS (Internet Protocol Multimedia Subsystem): Receiving an input to execute a VoLTE calling application; Generating a data packet, including a statement to trigger a procedure for setting up a dedicated carrier; and Transferring the data packet to one of the LTE network and the IMS, where the specification triggers the procedure for setting up a dedicated carrier, which is to be performed during a SIP (Session Initiation Protocol) signal exchange procedure. [10] The method of claim 9, further comprising: First, establish a connection to the LTE network; Establishing a connection to the IMS; and Register with the IMS. [11] Method according to claim 9, wherein the data packet is included in an RRC (Radio Resource Control) procedure with the LTE network. [12] Method according to claim 11, wherein the data packet includes a specific cause identification to indicate to the LTE network to reserve a QoS-QCI (Quality of Service indicator) resource. [13] Method according to claim 9, wherein the data packet is contained in an UL information transmission (uplink information transmission) with an MME (Mobility Management Entity, mobile supply instance) of the IMS. [14] Method according to claim 13, wherein the UL information transfer triggers a QCI1 setup procedure on a PGW (Packet Data Network Gateway) of the IMS. [15] Method according to claim 9, wherein the data packet is contained in an SR (Service Request) with the LTE network, wherein the data packet includes a security header to reserve a QCI1 resource.

Images