KR20140005320A - Systems and methods for inter-radio access technology(rat) mobility - Google Patents

Abstract

Methods and apparatus are described for providing inter-RAT mobility between 2G / 3G and 4 networks. A UE camped or connected to a GERAN or UTRAN network may be configured to move to the LTE network directly or via network-controlled functions to conduct a data call.

Description

SYSTEMS AND METHODS FOR INTER-RADIO ACCESS TECHNOLOGY (RAT) MOBILITY}

The present application relates generally to wireless communication systems. In particular, but not exclusively, the present application provides systems, apparatus and apparatus for providing mobility between radio access technology (RAT) between 2G / 3G networks, such as GERAN and UTRAN networks, and 4G networks, such as LTE networks. It is about methods.

Wireless communication systems are effectively deployed to provide various types of communication content such as voice, data, video, etc., and deployments are the introduction of new data-oriented systems such as Long Term Evolution (LTE) systems. Is likely to increase. Wireless communication systems may be multi-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth and transmit power). Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, 3GPP long term evolution (LTE) systems, and other orthogonal systems. Frequency division multiple access (OFDMA) systems.

In general, a wireless multiple-access communication system can simultaneously support communication for multiple wireless terminals (also known as user equipments (UEs), user terminals, or access terminals (ATs)). Each terminal communicates with one or more base stations (also known as access points (APs), EnodeBs or eNBs) via transmissions on the forward and reverse links. The forward link (also referred to as downlink or DL) refers to the communication link from the base stations to the terminals, and the reverse link (also known as uplink or UE) refers to the communication link from the terminals to the base stations. do. These communication links can be established through a single-input-single-output, single-input-multi-output, multiple-input single-output, or multiple-input-multi-output (MIMO) system.

A feature of interest in many communication systems is multimode operation. In multimode operation, communication devices such as user terminals can be configured to operate on different types of communication networks using different radio access technologies (RATs) and radio access networks (RANs). In some cases, user terminals or other communication devices may be redirected from one network that supports the first technology to a second network that supports a different technology.

For example, some LTE networks may not support voice connections or in some cases an operator may determine the location of a voice-oriented device on a 2G or 3G network or with mobility, loading, usage type, or other reasons. For various same reasons, one may want to move a voice connection to another network under the control or coordination of LTE networks.

In one case, in a data-centric LTE system, an operator may want to move a user attempting to conduct a voice call to another network that supports a different technology, such as circuit switched (CS) connections. Alternatively, the operator may want to move the user who receives the incoming voice call. For example, an operator may support a UTRAN or GERAN network (eg, native CS connections) from an LTE network and associated cells, using a procedure known as circuit switched fallback (CSFB), for example, as defined in 3GPP TS 23.272. To redirect the user to another network (such as a network). In some cases, the user may want to perform voice and data communications simultaneously but changing the direction to other networks may cause problems with voice and data simultaneous operation.

In other cases, an operator may direct a user with an LTE capable device to a 2G or 3G network if the device is voice centric or if the carrier prioritizes a device using a 2G or 3G network.

The present disclosure relates generally to wireless communication systems. In particular but non-exclusively, the present application provides systems, apparatus and methods for providing inter-radio access mobility (RAT) mobility between 2G / 3G networks such as GERAN and UTRAN networks and 4G networks such as LTE networks. It is about the field.

For example, in one aspect, the present disclosure relates to a method for providing inter-radio access technology (RAT) -mobility in a wireless communication system. The method may comprise, for example, camping an idle mode user terminal in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network. The first wireless network cell may be a 2G or 3G network cell. The method may further include changing the user terminal usage mode from voice-centric mode to data-centric mode and initiating a Routing Area Update (RAU) procedure from the user terminal based on the application running on the user terminal. . The RAU procedure may include providing information associated with the usage mode change from the user terminal and receiving new cell priority information from the wireless network. The method may further comprise selecting an E-UTRAN cell and performing data communications associated with an application and a base station of the E-UTRAN cell.

In another aspect, the present disclosure relates to a method for providing inter-radio access technology (RAT) -mobility in a wireless communication system. The method may comprise, for example, camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network, and moving the E-UTRAN cell during a predefined class of data calls. Receiving new cell priority information including the grant. The cell priority information may define the priority or restriction for cell types accessible by the user terminal based on carrier-preference. The method may further include receiving a trigger from an application running on the user terminal to initiate a data call and ignoring the assigned cell priority based on the new cell priority information. The new call priority information may allow for escalation of services for user terminals from 2G or 3G networks to 4G networks, such as LTE networks. The processor may further include selecting an E-UTRAN network cell and establishing a connection with a base station of the E-UTRAN network. The method may further comprise performing data communications associated with the application on the selected E-UTRAN cell.

In another aspect, the present disclosure relates to a method for providing inter-radio access technology (RAT) -mobility in a wireless communication system. The method may comprise, for example, camping an idle mode user terminal in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network. The method comprises receiving, from an application running on a user terminal, a request message including a trigger for a data call, determining an appropriate E-UTRAN network cell, and a cause indicator for the data call. The method may further include transmitting. The method may further comprise receiving a release message with direction change information from the first wireless network to the E-UTRAN network cell.

In another aspect, the present disclosure relates, in whole or in part, to a non-transitory computer-readable medium comprising instructions for implementing the methods described above.

In another aspect, the present disclosure relates, in whole or in part, to systems, devices, and apparatus for performing the above-described methods.

In another aspect, the present disclosure relates, in whole or in part, to means for performing the methods described above.

Further aspects, features and functions are described further below in connection with the appended drawings.

The present application may be fully appreciated in connection with the following detailed description taken with reference to the accompanying drawings.

1A illustrates details of circuit switched fallback (CSFB) procedures for various call scenarios.
FIG. 1B illustrates details of packet switched (PS) encapsulation procedures similar to the CSFN procedures illustrated in FIG. 1A, for various call scenarios.
2 illustrates details of an example logical information exchange during attach / TAU / RAU procedures.
3 illustrates details of an example communications system including multiple user terminals and a base station.
4 illustrates details of an example communications system that includes multiple cells that may use different RATs that may use different RATs.
5 shows details of an exemplary network configuration of nodes of a wireless communication system.
6 illustrates an example configuration of network nodes configured in a multimode communication system.
7 shows details of an exemplary embodiment of a multimode communication system including 2G / 3G cells and 4G cell.
8 illustrates details of one embodiment of an example connection flow in which an application triggers a change in UE operating mode and packet switched (PS) escalation.
9 illustrates details of one embodiment of a process consistent with the workflow of FIG. 8 for performing PS escalation at a user terminal.
10 illustrates the details of one embodiment of an exemplary attach workflow where the network provided cell selection priority information and authorization to perform PS escalation based on a predefined class of calls.
FIG. 11 illustrates the details of one embodiment of a process consistent with the workflow of FIG. 10 for performing PS escalation at a user terminal.
12 illustrates details of one embodiment of a process consistent with the workflow of FIG. 10 for performing PS escalation at a base station.
FIG. 13 illustrates the details of one embodiment of an example access workflow in which the network provided cell selection priority information and authorization to perform PS escalation based on cause information provided from the user terminal to the network.
14 illustrates details of one embodiment of a process consistent with the workflow of FIG. 13 for performing PS escalation at a user terminal.
FIG. 15 shows details of one embodiment of a process consistent with the workflow of FIG. 13 for performing PS escalation at a base station.
16 shows details of one embodiment of an example attach workflow using RRC release-based escalation.
17 illustrates details of one embodiment of an example attach workflow using PSHO-based PS escalation.
18 illustrates details of one embodiment of an exemplary attach workflow using CCO-based PS escalation in a GERAN network.
19 illustrates an embodiment of a base station and a user terminal in a multimode communication system.
20 illustrates details of one embodiment of a user terminal that may be used in a multimode communication system.
21 illustrates details of one embodiment of a base station that may be used in a multimode communication system.

Various aspects and features of the disclosure are further described below. The teachings herein may be embodied in a wide variety of forms and it should be apparent that any particular structure, function, or both disclosed herein is merely representative, not limiting. Based on the teachings herein, one of ordinary skill in the art should appreciate that an aspect disclosed herein may be implemented independent of any other aspects and that two or more of these aspects may be combined in various ways. For example, such an apparatus may be implemented or such a method may be practiced using any number of aspects set forth herein. Moreover, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. For example, a method may be implemented as part of a system, device, apparatus, and / or as instructions stored on a computer readable medium for execution on a processor or computer. In addition, one aspect may include at least one element of the claims.

This disclosure relates generally to coordination and management of operation in wireless communication systems, such as multimode communication systems. In various aspects, the techniques and apparatus described herein include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks. It may be used for wireless communication networks such as single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks as well as other communication networks. As described herein, the terms “systems” and “networks” may be used interchangeably.

CDMA networks may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, and the like. UTRA includes Low Chip Rate (LCR) as well as Wideband-CDMA (W-CDMA). cdma2000 covers IS-2000, IS-95 and IS-856 standards.

The TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). 3GPP defines standards for the GSM Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (RAN), also referred to as GERAN. GERAN is a radio component of GSM / EDGE with a network that combines base stations (eg, Alter and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents a major component of the GSM network, through which telephone calls and packet data are transmitted from public switched telephone networks (PSTNs) and the Internet to subscriber handsets, also known as user terminals or user equipments (UEs) and such subscriber handsets. To the public switched telephone network (PSTN) and the Internet. The mobile telephone operator's network may comprise one or more GERANs that may be coupled with UTRANs in the case of a UMTS / GSM network. The operator network may also include one or more LTE networks and / or one or more other networks. Various different network types may use different radio access technologies (RATs) and radio access networks (RANs).

An OFDMA network may implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDMA, and the like. UTRA, E-UTRA and GSM are part of the Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization named "3rd Generation Partnership Project (3GPP)", and cdma2000 is an organization named "3rd Generation Partnership Project 2 (3GPP2)". Are described in documents from. These various radio technologies and standards are known or under development. For example, the Third Generation Partnership Project (3GPP) is a collaboration between groups of telecommunications associations that aim to define globally applicable third generation (3G) mobile telephony specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP defines the specifications of next generation mobile networks, mobile systems and mobile devices. For clarity, certain aspects of the apparatus and techniques are described below for LTE implementations or in an LTE-centric manner, where LTE terminology is used in much of the description below, but the description is not intended to be limited to LTE applications. Do not. Thus, it will be apparent that the systems, apparatus, and methods described herein may be applied to other communication systems and applications.

Logical channels in wireless communication systems may be classified as control channels and traffic channels. Logical control channels include a Broadcast Control Channel (BCCH), which is a downlink (DL) channel for broadcasting system control information, a Paging Control Channel (PCCH), which is a DL channel that carries paging information, and multimedia broadcast and Multicast Service (MBMS) includes multicast control channel (MCCH), which is a point-to-multipoint DL channel used for scheduling and transmitting control information for one or several MTCHs can do. In general, after establishing a Radio Resource Control (RRC) connection, this channel is used only by UEs receiving MBMS. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional channel used by UEs that transmit dedicated control information and have RRC connections.

Logical traffic channels are multi-point for a dedicated traffic channel (DTCH), a point-to-point bidirectional channel, dedicated to one UE, for the delivery of user information, and a point-to-multipoint DL channel for transmitting traffic data. Cast traffic channel (MTCH).

Transport channels are classified into downlink (DL) and uplink (UL) transport channels. The DL transport channel may include a broadcast channel (BCH), a downlink shared data channel (DL-SDCH), and a paging channel (PCH). PCH can be used to support UE power savings (eg, when a Discontinuous Receive (DRX) cycle is indicated to the UE by the network), broadcast for the entire cell and used for other control / traffic channels. Mapped to physical layer (PHY) resources. The UL transport channels may include a random access channel (RACH), a request channel (REQCH), an uplink shared data channel (UL-SDCH), and a plurality of PHY channels. PHY channels may include DL channels and a set of UL channels. DL PHY channels may include the following channels.

The common pilot channel (CPICH)

Sync channel (SCH)

Common Control Channel (CCCH)

Shared DL Control Channel (SDCCH)

The multicast control channel (MCCH)

Shared UL Allocation Channel (SUACH)

The acknowledgment channel (ACKCH)

DL Physical Shared Data Channel (DL-PSDCH)

UL Power Control Channel (UPCCH)

Paging indicator channel (PICH)

Load Indicator Channel (LICH)

UL PHY channels may include the following channels.

Physical random access channel (PRACH)

Channel quality indicator channel (CQICH)

The acknowledgment channel (ACKCH)

Antenna subset indicator channel (ASICH)

The shared request channel (SREQCH)

UL Physical Shared Data Channel (UL-PSDCH)

Broadband Pilot Channel (BPICH)

The term "exemplary" is used herein to mean "acting as an example, case, or illustration." Any aspect and / or embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects and / or embodiments.

For the purpose of describing various aspects and / or embodiments, the following terms and abbreviations may be used herein.

AM acknowledgment mode

AMD Acknowledgment Mode Data

ARQ Auto Repeat Request

BCCH Broadcast Control Channel

BCH Broadcast Channel

C-control

CCCH common control channel

CCH control channel

CCTrCH Coded Synthetic Transport Channel

CP cyclic prefix

CRC Cyclic Redundancy Check

CTCH Common Traffic Channel

DCCH dedicated control channel

DCH Dedicated Channel

DL downlink

DSCH Downlink Shared Channel

DTCH Dedicated Shared Channel

FACH Forward Link Access Channel

FDD frequency division duplex

L1 Tier 1 (Physical Tier)

L2 Layer 2 (Data Link Layer)

L3 Layer 3 (Network Layer)

LI length indicator

LSB least significant bit

MAC media access control

MBMS Multimedia Broadcast Multicast Service

MCCH MBMS Point-to-Multipoint Control Channel

MRW Move Receive Window

MSB most significant bit

MSCH MBMS point-to-multipoint scheduling channel

MTCH MBMS point-to-multipoint traffic channel

PCCH Paging Control Channel

PCH Paging Channel

PDU protocol data unit

PHY physical layer

PhyCH Physics Channel

RACH Random Access Channel

RLC radio link control

RRC Radio Resource Channel

SAP service access point

SDU service data unit

SHCCH shared channel control channel

SN sequence number

SUFI Super Field

TCH Traffic Channel

TDD Time Division Duplex

TFI Transport Format Indicator

TM transparent mode

TMD transparent mode data

TTI Transmit Time Interval

U- User-

UE user equipment

UL uplink

UM non-acknowledgement mode

UMD non-acknowledgement mode data

UMTS Universal Mobile Telecommunication System

UTRA UMTS Ground Radio Access

UTRAN UMTS terrestrial radio access network

MBSFN Multimedia Broadcast Single Frequency Network

MCE MBMS Coordination Entity

MCH Multicast Channel

DL-SCH Downlink Shared Channel

MSCH MBMS Control Channel

PDCCH Physical Downlink Control Channel

PDSCH Physical Downlink Shared Channel

LTE systems support time division duplex (TDD) and frequency division duplex (FDD) implementations. In a TDD system, the forward and reverse link transmissions use the same frequency, with the result that the reciprocity principle enables estimation of the forward link channel from the reverse link channel. This allows the access point to extract the transmit beamforming gain on the forward link when multiple antennas are available at the access point.

System designs may support various time-frequency reference signals for the downlink and uplink to enable beamforming and other functions. The reference signal is a signal generated based on known data, and may also be referred to as a pilot, preamble, training signal, sounding signal, or the like. The reference signal may be used by the receiver for various purposes such as channel estimation, coherent demodulation, channel quality measurement, signal strength measurement, and the like. MIMO systems using multiple antennas generally coordinate transmitting reference signals between the antennas, but LTE systems generally do not coordinate transmitting reference signals from multiple base stations or eNBs.

3GPP Regulation 362110-900 defines in paragraph 5.5 certain reference signals for demodulation associated with transmission of a PUSCH or PUCCH as well as sounding not associated with transmission of a PUSCH or PUCCH. For example, Table 1 lists some reference signals for LTE implementations that can be transmitted on the downlink and uplink and provides a short description of each existing signal. The cell-specific reference signal may also be referred to as a common pilot, broadband pilot, or the like. The UE-specific reference signal may also be referred to as a dedicated reference signal.

link Reference signal Explanation Downlink Cell specific
Reference signal Transmitted by Node B and used by UEs for channel estimation and channel quality measurement. Downlink UE specific
Reference signal Sent by a Node B to a particular UE and used for demodulation of downlink transmissions from the Node B. Uplink Sounding
Reference signal Transmitted by the UE and used by the Node B for channel estimation and channel quality measurement. Uplink Demodulation
Reference signal Transmitted by the UE and used by the Node B for demodulation of uplink transmissions from the UE.

In some implementations, the system can utilize time division duplexing (TDD). In the case of TDD, the downlink and uplink share the same frequency spectrum or channel, and the downlink and uplink transmissions are transmitted on the same spectrum. Thus, the downlink channel response can be correlated with the uplink channel response. Mutuality may cause the downlink channel to be estimated based on transmissions transmitted on the uplink. These uplink transmissions may be uplink control channels or reference signals (which may be used as reference symbols after demodulation). Uplink transmissions may enable estimation of the space-selective channel via multiple antennas.

In LTE implementations, orthogonal frequency division multiplexing is used for the downlink, i.e., downlink from a base station, access point or Node B (eNB) to a user terminal or UE. The use of OFDM meets the LTE requirement for spectrum flexibility, enables cost-effective solutions for very wide carriers with high peak rates, and is well-established. established technology). For example, OFDM is used in standards such as IEEE 802.11a / g, 802.16, HIPERLAN-2, DVB and DAB.

Time frequency physical resource blocks (also referred to herein as resource elements or “REs” for short) are referred to as groups of intervals or transport carriers (eg, sub-carriers) assigned to transport data. It can be defined in OFDM systems. RBs are defined over time and frequency periods. Resource blocks consist of time-frequency resource elements (also referred to herein as resource elements or “REs” for short), which can be defined by indices of time and frequency in a slot. Further details of LTE RBs and REs are described in 3GPP specifications, such as 3GPP TS 36.211, for example.

UMTS LTE supports carrier bandwidths that scale from 20MHz to 1.4MHZ. In LTE, RB is defined as 12 sub-carriers when the subcarrier bandwidth is 15 kHz or 24 sub-carriers when the sub-carrier bandwidth is 7.5 kHz. In an exemplary implementation, there is a defined radio frame in the time domain that is 10 ms long and consists of 10 subframes of 1 millisecond (ms) each. Every subframe consists of two slots, where each slot is 0.5 ms. In this case, the subcarrier spacing in the frequency domain is 15 kHz. Twelve subcarriers of these subcarriers together form the RB (per slot), so in this implementation one resource block is 180 kHz. Six resource blocks match a carrier of 1.4 MHz, and 100 resource blocks match a carrier of 20 MHz.

There are typically multiple physical channels in the downlink as described above. In particular, the physical downlink control channel (PDCCH) is used to transmit control, the physical hybrid ARQ indicator channel (PHICH) is used to transmit ACK / NACK, and the physical control format indicator channel (PCFICH) The physical downlink shared channel (PDSCH) is used for data transmission, and the physical multicast channel (PMCH) is used for broadcast transmission using a single frequency network (SFN). In other words, a physical broadcast channel (PBCH) is used to transmit important system information in a cell. The modulation formats supported on PDSCH in LTE are QPSK, 16 QAM and 64 QAM. Various modulation and coding schemes are defined for various channels in the 3GPP standards.

There are typically three physical channels in the uplink. The physical random access channel (PRACH) is only used for initial access, while when the UE is not uplink synchronized, data is transmitted on the physical uplink shared channel (PUSCH). If there is no data to be transmitted on the uplink for the UE, control information will be sent on the physical uplink control channel (PUCCH). The modulation formats supported on the uplink data channel are QPSK, 16 QAM and 64 QAM.

If virtual MIMO / space division multiple access (SDMA) is introduced, the data rate in the uplink direction may increase with the number of antennas at the base station. Using this technique, two or more mobiles can reuse the same resources. During the MIMO operation, a single user MIMO for enhancing the data throughput of the user and a multi-user MIMO for enhancing the cell throughput are distinguished.

CS fallback overview

3GPP describes, for example, configurations for implementing CS fallback (CSFB) in a standard such as 3GPP TS 23.272. The SGS interface is described in 3GPP TS 29.118. Further aspects of the CSFB are described in 3GPP TS 23.401. Each of these documents is incorporated herein by reference.

The CSFB may, for example, depend on the state of the user terminal or UE, whether the UE is idle or connected, or whether the associated circuit switched (CS) domain service is mobile originated (MO call) or mobile incoming (mobile terminated) (MT call) or may be performed in various ways depending on other state conditions. CS domain services generally refer to video services, although it can also be used to refer to CS domain data services such as video or CS multimedia.

1A illustrates various examples of CS fallback cases in diagram 100. In each of these cases the core portion of the CSFB procedure is non-accessible from the user terminal (UE) to the mobile management entity (MME) via the E-UTRAN (when the UE is operating in a 4G network such as E-UTRAN / LTE). Start sending a Non-Access Stratum (NAS) Extended Service Request (ESR) message.

Upon receipt of an ESR message at the MME, the MME may determine one of the different procedures shown in FIG. 1A based on the support provided by the network and the UE. As defined in TS 23.272, the three main types of core CSFB procedures are: 1) radio resource control (RRC) based procedure; 2) packet switched (PS) handover (PSHO) based procedures; And 3) Cell Change Order (CCO) based procedures with or without network assistance (NACC).

CCO without NACC base CSFB applies only to A / Gb GERAN networks. PSHO-based CSFB use requires both a network and a UE to support PS handover to an individual radio access technology (RAT), but PSHO is typically not supported in GERAN networks. RRC release and PSHO based CSFB have different changes based on the RAT and UE and network capabilities used for CS domain.

For example, as shown in FIG. 1A, a UE originating MO CS from an idle mode UE (stage 112) or a connected mode UE (stage 114) camping on an E-UTRAN / LTE cell. The call (stage 110) may cause the UE to transmit an external service request (stage 170). Similarly, paging may be performed at stage 162 so that the MT CS call (stage 150) is input to the UE 152 camping on the 4G / LTE network. Similarly, the UE receives the MT call in the connected (active) mode, and the MME may transmit a CS service notification at stage 164.

In each of these cases, the UE may transmit an external service request at stage 170 resulting in various operations depending on the UE and network configuration. For example, an RRC release using a change of direction can be provided at stage 182. Alternatively, a PSHO (typically for a UTRAN network) or a CCO without NACC (for GERAN networks) may be provided at stages 184 and 186, respectively.

Service domain selection overview

Service-domain selection for CSFB-capable user terminals / UEs supporting E-UTRAN and GERAN or UTRAN, which provides for the selection of RATs between the PS and CS domains, is in 3GPP specifications, in particular in 3GPP TS 23.221. Are described, which are incorporated herein by reference. This specification describes, among other features, control of UE operation during initial registration and location updates, for example during UE movement.

In summary, the UE has configuration settings describing the Home Public Land Mobile Network (HPLMN) operator (also hereafter abbreviated herein as "operator") preferences for voice services. Open Mobility Alliance) or Device Management (DM) or OMA DM. The operator, depending on the operator, network configuration and device configurations,

1) CS voice only

2) IMS PS Voice Only

3) CS voice preference for IMS PS voice secondary

3) For CS voice secondary, IMS PS voice preference

Preferences or other preferences may be selected. These preferences may also be indicated here as cell priorities, and are typically only controlled by the operator.

Moreover, the user terminal or UE may also be configured by default during manufacturing, may be configured by provisioning by an operator, and / or may be configured by a user to be “voice centric” or “data centric”. . Such a configuration may also be referred to herein as a UE operational mode setting or a usage mode setting. The use mode setting is typically assumed to be controlled only by having an initial default setting or by the user of the device, which is generally performed only once by the user to a minimum. Later settings during device operation, for example by an application or operator / carrier, have not been considered in existing devices and systems.

These parameters as well as other parameters that the UE receives in the attach accept and TAU / RAU accept messages govern the voice domain (CS to PS) RAT selection. In particular, the following indicators are: 1) "IMS Voice Over PS Selection Support" indication; 2) "SMS only" indication; And 3) "CSFB Not Preferred" indication. Table 2 below summarizes the UE operation for RAT selection according to the success or failure of the attach / TAU combining procedure and indicators provided in the accept messages. For example, a "voice-centric" UE tunes to a 2G / 3G network when "CSFB non-preferred" is indicated by the network or when CSFB is not supported (eg, an indication of "SMS only"). In this case, there is no obvious way for the UE to return back to the E-UTRAN / LTE network when the configuration does not change from "voice-centric" to "data-centric".

According to the parameters provided in the accept messages UE  action Combined Attachment or TAU Accept Message UE behavior Attachment result SMS only CSFB Preferred Voice centric Data-centric success


- - Stay on E-UTRAN and use CSFB -

2G / 3G reselection Stay on E-UTRAN and use CSFB (SMS with SG support)

- 2G / 3G reselection Stay on E-UTRAN, no voice (SMS with SG support)

Error case failure X X 2G / 3G reselection Stay on E-UTRAN, no voice

Selective idle mode  Camping outline

The concept of "selective idle mode camping" was introduced in 3GPP Release 9 to improve the user experience for CS voice calls. As shown in FIG. 1B, this function is to allow UEs configured as "voice-centric" to camp on 2G / 3G networks, such as GERAN and UTRAN networks, in idle mode. 2 shows an example diagram 200 illustrating a process. Diagram 200 includes example entities, namely UE 210, base station or RAN 230, MME or SGSN 250, and HSS 270. At stage 211, the UE 210 has its voice capabilities (eg, IMS and / or CS enabled, CSFB capabilities, etc.) and configuration settings (eg, "voice center" or "data center"). , IMS / CS voice preferences) may be sent to the MME or SGSN 250 in attach / TAU / RAU request messages. As part of the location update procedure, the HSS 270 provides the "subscriber RFSP index" to the MME or SGSN 250 in the update location Ack message 213 as part of other subscription information. At stage 215, MME / SGSN 250 selects “RFSP index in use” based on “subscriber RFSP index” and “UE voice capabilities / settings” provided by HSS 270. At stage 217, the “RFSP index in use” may be provided from the MME / SGSN 250 to the RAN 230 (eg, eNB of LTE or BSC / RNC of GERAN / UTRAN). At stage 219, the RAN 230 selects an idle mode camping policy based on the “RFSP index in use” received from the MME / SGSN 250 at stage 217. At stage 221, idle mode mobility information, including cell reselection priorities, is transmitted to the UE 210 (eg, in an RRC connection release message or other message).

As used herein, RFSP refers to RAT / frequency selection priority. This term is used by SA2 for the "Subscriber Profile ID for RAT / Frequency Selection Priority" IE as defined in 3GPP TS 36.300, TS 36.331 and TS 25.413. To achieve the desired functionality, the RFSP index selected by the MME / SGSN 250 at stage 215 is determined based on the knowledge of the UE configuration parameters. For example, for a “voice centric” UE, the index may refer to a table entry stored at the RAN node 230 that prioritizes 2G / 3G cells relative to 4G / LTE cells.

LTE  System overview

Before describing further aspects and details associated with the movement between 2G / 3G networks such as GERAN or UTRAN and 4G networks such as E-UTRAN / LTE, details of example LTE system and device implementations are added below. Is explained.

For example, FIG. 3 illustrates details of an implementation of a multiple access wireless communication system, which may be an LTE system, in which frequently described aspects may be implemented. A base station such as a Node B (NB) or an evolved Node B (eNB) 300 such as an LTE eNB may include a number of antenna groups, one group comprising 304 and 306, and the other group 308 And 310, further groups include 312 and 314. In FIG. 3, only two antennas are shown for each antenna group, but more or fewer antennas may be utilized for each antenna group. A multi-RAT capable user terminal or user equipment (UE) 316 (also known as an access terminal or AT) communicates with antennas 312 and 314, where the antennas 312 and 314 are forward links (also Information is transmitted to the UE 316 via a 320 (known as a downlink), and receives information from the UE 316 via a reverse link (also known as an uplink) 318. The second UE 322 can communicate with the antennas 306, 308, where the antennas 306, 308 transmit information to the UE 322 over the forward link 326, and access terminal 322. Information is received over the reverse link 324. UEs 316 and / or 322 may be configured to communicate with cells and associated base stations in multiple wireless networks, in addition to LTE networks, such as GERAN and / or UTRAN networks (not shown in FIG. 3).

In a frequency division duplexing (FDD) system, communication links 318, 320, 324, 326 may use different frequencies to communicate with the RAT. For example, forward link 320 may then use a different frequency than that used by reverse link 318. In a time division duplexing (TDD) system, downlinks and uplinks may be shared with the RAT.

Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of a base station or eNB. Each of the antenna groups may be designed to communicate to UEs in a sector of the areas covered by the eNB 300. In communication over forward links 320 and 326, the transmit antennas of eNB 300 may utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 316, 322. .

In addition, an eNB using beamforming to transmit to UEs randomly spread throughout its coverage may cause less interference to UEs in neighboring cells than an eNB transmitting to all its UEs via a single antenna. have. As previously discussed, UEs such as UEs 316 and 322 may be further configured to operate with other nodes (not shown) of other communication networks such as, for example, GERAN and / or UTRAN networks. Moreover, base stations, such as eNB 300, may perform handovers of served UEs to base stations (not shown) of other networks, for example, through the use of direction change commands, circuit switched fallback (CSFB) procedures, and / or other mechanisms. It may be configured to facilitate.

4 illustrates details of one implementation of a multiple access wireless communication system 400, such as an LTE system, in which aspects such as those described frequently herein can be implemented. Multiple access wireless communication system 400 includes a number of cells, including cells 402, 404, 406. These may be cells of a common RAT type, such as LTE cells, and / or may include cells of other RAT types, such as GERAN and / or UTRAN cells. Although cell coverage is shown as being contiguous, coverage areas may overlap in whole or in part.

In one aspect, the cells 402, 404, 406 may include a Node B (NB) or an Enhanced Node B (eNB) that includes multiple sectors. Multiple sectors can be formed by groups of antennas, each antenna serving to communicate with UEs within a portion of the cell. For example, in cell 402, antenna groups 412, 414, 416 may each correspond to a different sector. In cell 404, antenna groups 418, 420, 422 respectively correspond to different sectors. In cell 206, antenna groups 424, 426, 428 each correspond to a different sector.

Cells 402, 404, 406 can include various wireless communication devices, eg, user equipment or UEs, that can communicate with one or more sectors of each cell 402, 404, or 406. For example, the UEs 430, 432 can communicate with the eNB 442, the UEs 434, 436 can communicate with the eNB 444, and the UEs 438, 440 can communicate with the eNB ( 446).

The cells and associated base stations can be coupled to the system controller 450, which can be part of a core or backhaul network or function as further described herein in connection with multimode coordination and operation. As well as provide access to core or backhaul networks including, for example, MME and SGW that may be used to perform other aspects described herein. The core network may include components under the control of a carrier or operator, described in more detail herein below.

5 illustrates details of an example embodiment 500 for connections between various network nodes. The network 500 may include a macro-eNB 502 and / or multiple additional eNBs, which may be, for example, picocell eNBs 510, femtocell eNBs, macrocell eNBs or other base station nodes. Network 500 may include HeNB gateway 534 for scalability reasons. The macro-eNB 502 may communicate with a pool 540 of one or more mobility management entities (MMEs) 542 and / or a pool 544 of one or more serving gateways (SGWs) 546, respectively. Can be.

The eNB gateway 534 may be seen as a C-plane and U-plane relay for dedicated S1 connections 536. The S1 connection 536 may be a logical interface defined as a boundary between an evolved packet core (EPC) and an evolved universal terrestrial access network (EUTRAN). Thus, the S1 connection provides an interface to core network (CN) components such as MME and SGW that may be further coupled to other components and / or networks (not shown). The eNB gateway 534 may act as a macro-eNB 502 from an EPC perspective. The eNB gateway 534 may be S1-MME and the U-plane interface may be S1-U. The network 500 may include a number of additional eNBs and macro-eNB 502, which may be picocell or femtocell eNBs 510.

The eNB gateway 534 may operate towards the eNB 510 as a single EPC node. The eNB gateway 534 may ensure an S1-plex connection to the eNB 510. The eNB gateway 534 may provide a 1: n relay function such that a single eNB 510 can communicate with n MMEs 542. The eNB gateway 534 registers towards the pool 540 of the MMEs 542 when performing the operation via the S1 setup procedure. The eNB gateway 534 may support the setup of the eNBs 510 and S1 interfaces 536.

Network 500 may also include a self-organizing network (SON) server 538. SON server 538 may provide for automated optimization of 3GPP LTE networks. SON server 538 may be the primary driver for improving operation management and maintenance (OAM) functions in wireless communication system 500. The X2 link 520 may exist between the macro-eNB 502 and the eNB gateway 534. X2 links 520 may also exist between each eNB 510 that is connected to a common eNB gateway 534. If the X2 link 520 cannot be established, the S1 link 536 can be used, for example, to transfer information between different cells or networks.

Backhaul signaling may be used in network 500 to manage the various functions described further herein, for example, between eNBs and other network nodes and / or other networks. For example, these connections may be used as described further successively herein to facilitate multimode operation using, for example, other network types such as GERAN or UTRAN networks. The UEs 512 can be coupled to various eNBs and can also communicate between cells associated with the eNBs as well as communicate with cells of other network types (not shown).

For example, the operator's system may include a number of networks that may be of many types (eg, in addition to the LTE network configurations shown in FIGS. 3 and 4). For example, one type may be a data centric LTE system. Another type may be a UTRAN system, such as a W-CDMA system. Another type may be a GERAN system (also indicated herein as a DTM GERAN) that may in some cases be capable of dual delivery mode (DTM). Some GERAN networks may be non-DTM capable. Multimode user terminals such as UEs may be configured to operate in these networks as well as multimode networks such as other networks (eg, WiFi or WiMax networks, etc.).

For example, DTM, defined in 3GPP TS 43.055, is a protocol based on the GSM standard that allows simultaneous delivery of CS (voice) and PS (data) over the same radio channel. A DTM capable mobile phone (eg, user terminal or UE) may be involved in both CS and PS calls in DTM GERAN networks, and may simultaneously perform voice and packet data connections in DTM GERAN networks.

In some LTE implementations, devices can support a function known as idle-mode signaling reduction (ISR). ISR is a mechanism that allows user terminals, such as UEs, to continue to be registered simultaneously in the UTRAN or GERAN routing area (RA) and E-UTRA tracking area lists. This allows the UE to perform cell reselections between LTE and UTRAN / GERAN networks without the need to send a Tracking Area Update (TAU) or Routing Area Update (RAU) request while the UE remains in the registered RA and TA lists. Can be. Thus, ISR can be used to reduce mobility signaling and can improve battery life of UEs. This may be particularly important in early deployments of LTE systems where coverage may be limited and inter-RAT changes may occur frequently. Moreover, this may also be important until the usefulness of PS-based voice implementations such as Voice Over IP (VOIP) has evolved, which often requires operators to operate between LTE and GERAN or UTRAN networks to support CS voice calls. This is because it can be switched. In order to support ISR, the home subscriber server (HSS) needs to maintain two PS registrations: one PS registration from the mobility management entity (MME) and another PS registration from the serving GPRS support node (SGSN). . Moreover, ISRs require more complex paging procedures. In an exemplary embodiment, the state of the ISR may be on or off, indicating whether the ISR is in use.

MME is an important control-node for LTE access-network. The MME is responsible for idle mode UE tracking and paging procedures including retransmissions. The MME is also involved in the bearer activation / deactivation process and is responsible for selecting a serving gateway (SGW) for the UE at the time of in- LTE handover and at initial attachment that involves core network (CN) node relocation.

The MME is also responsible for authenticating the user (by interacting with the HSS). Non-access layer (NAS) signaling ends at the MME, which is responsible for generating and assigning temporary identifiers to UEs. For example, the MME checks the UE's permission to camp on to the service provider's public terrestrial mobile network (PLMN) and enforces UE roaming restrictions. The MME is the termination point of the network, for encryption / integrity protection for NAS signaling. Lawful interception of signaling is also supported by the MME.

Another important function of the MME is to provide control plane functionality for mobility between LTE and 2G / 3G access networks, such as UTRAN and GERAN networks, using the S3 interface terminating at the MME from SGSN. The MME also terminates the S6a interface towards the home HSS for roaming UEs.

The Serving Gateway (SGW) also acts as a mobility anchor for the user plane during inter-NodeB handovers and as an anchor for movement between LTE and other 3GPP technologies (eg, exiting the S4 interface and exiting 2G / Routing and forwarding user data packets) while relaying traffic between 3G systems and a packet gateway (PGW). For idle UEs, the SGW terminates the DL data path and triggers paging when DL data arrives at the UE. The SGW manages and stores UE contexts, such as parameters of an IP bearer service, network internal routing information, and the like. The SGW may also perform replication of user traffic in case of legitimate interception.

The PDN Gateway provides a connection from the UE to external packet data networks as being the entry and exit of traffic to the UE. The UE may have simultaneous connections with two or more PGWs to access multiple PDNs. PGW performs policy enforcement, packet filtering, charging support, legal interception and packet screening for each user.

Packet Switched (PS) Escalation Implementations

FIG. 6 illustrates an example configuration 600 of network nodes for multimode operation between an LTE network and other networks, such as UTRAN or GERAN networks, that may be used to provide the functionality as described herein. . The multimode UE 612 may be connected to the LTE network 622, for example an eNB such as the eNB 615 of FIG. 4, and may be served by a base station such as a Node B (NB) or a UTRAN or GERAN. It may be moved between the network 632 and the LTE network. The LTE network may include the SGW 640 as shown in FIG. 5 as well as the MME 624 as previously shown in FIG. 5.

The SGW can be connected to the PGW (not shown) and the MME can be connected to the legacy mobile switching center (MSC0) via the SG interface. The SG interface is between legacy 2G or 3G networks, such as GERAN or UTRAN, and LTE and LTE networks. Provide access to

When the UE 612 moves between networks, the UE 612 may perform a Tracking Area Update (TAU) procedure when moving to an LTE network or may perform a Routing Area Update (RAU) procedure when moving to a UTRAN or GERAN network. Can be done. The RAU or TAU may be initiated when the UE 612 detects a new tracking or routing area. An example thereof is illustrated in 3GPP TS 23.401, an exemplary call flow is illustrated in the appendix of TS 23.401, all of which are incorporated herein by reference.

The user terminal or UE may be in the coverage area of several networks of different types. These may be controlled or operated by a common carrier or operator, and the devices in the various networks may be configured to reliably work with different network types as described later herein.

An example of this is illustrated in FIG. 7, where a user terminal 730, such as a multi-mode UE 730, is configured to include a first RAT as well as a second RAT as well as a first radio network cell 710 of a first radio access technology (RAT). An example network 700 is shown within coverage of the second wireless network 750. In this example shown, the second wireless network is a 4G LTE network and the first wireless network is a 2G / 3G GERAN or UTRAN network. Corresponding base stations 712 serving the first wireless network and base station 752 serving the second wireless network are within range of the UE 730. In operation, the UE between the first wireless network and the second wireless network to facilitate movement or for other reasons, for example to control the operation based on user / device and / or network operator preferences. It may be desirable to move 730. For example, as previously described with reference to FIGS. 1-3, the user terminals or UEs may be configured with a voice preference or user terminal usage mode, which may be one of "voice-centric" and "data-centric". . Likewise, carriers may specify a preference for a UE when on a network, for example via cell priority information that may be transmitted from the network and the base station in one or more information elements (IE).

FIG. 8 illustrating an example of a process flow 800 in one of a user terminal or UE 810 in an idle mode camping on a 2G / 3G cell at stage 812 as previously described with respect to FIG. 1B. Note now. The UE 810 may be served by a base station node, such as a base station controller (BSC) or radio network controller (RNC) 850, depending on the type of 2G / 3G network. The BSC / RNC 850 is a serving GPRS support node (SGSN) that is responsible for the transfer, routing and delivery of data to and from the served mobile stations, mobility management, logical link management, authentication and charging functions, as well as other functions. 870 may be further coupled.

The UE 810 may be configured in a "voice-centric" (VC) user terminal usage mode, which may be set on the device by the user, for example, or pre-programmed during manufacture or upon carrier activation. In general, the mode of use is a parameter set on the device by the user or pre-programmed based on the type of device. For example, handset user terminal devices, such as mobile phones, can be configured to be in voice-centric mode, so that priority can be given to voice-oriented calls and associated support networks, while notebook computer dongles and the like. Other user terminal devices may be configured in a “data centric (DC)” mode to prioritize data-oriented calls / communications and associated networks. The device mode is assumed to be a device specific parameter set by the user or a default value programmed in the device and not configured by the network or by the applications running on the device.

At stage 814, a trigger event may occur to initiate a change in the configuration of the UE from voice-centric mode to data-centric mode. Such an event may be a trigger generated from an application running on a UE based on requirements such as, for example, quality of service (QoS) requirements. For example, an application may require high data throughput, which is only supported on 4G networks or preferably performed on 4G networks, such as LTE networks. To support this trigger, the UE may be allowed to change the user mode of the UE from the voice center to the data center and vice versa. For example, as part of an application trigger, the application can change the UE device mode setting from voice center to data center (and then back on completion of the data call as described below later).

At stage 831, a Routing Area Update (RAU) procedure may be initiated by the UE in response to a change in operating priority (eg, from voice domain priority to data priority) and associated UE device mode setting. have. For example, a change in configuration setting may trigger the RAU procedure according to 3GPP TS 23.060 (Release 9).

If selective idle mode camping is applied, the UE should receive new cell selection priorities (also indicated as cell priority) from the 2G / 3G network to give the E-UTRAN higher priority. Then, for example, the UE 810 may receive a new dedicated priority information IE (information element) as part of the procedure corresponding to the network-provided cell priority information. For example, cell priority may be varied such that the highest priority network types supported by the device vary from 2G / 3G to 4G and / or between 2G / 3G networks available.

In some embodiments, the UE may begin the procedure of selecting an LTE cell and associated base station at stage 816 before completion of the RAU procedure of stage 631. For example, the LTE selection process may be performed as part of an application trigger at stage 814 or may be performed before the completion of the RAU procedure and delivery of new dedicated priority information from the network at stage 831. As shown in FIG. 8, stage 816 may be performed concurrently with stage 831 or prior to completion of stage 831, wherein received cell priority information from SGSN 870 is selected when selecting an LTE network. Can be ignored.

Once the UE selects an appropriate LTE cell and base station, such as an eNB, the UE 810 subsequently performs a data call in stage 833 in packet switched (PS) mode using, for example, standard LTE signaling and data delivery. can do. Thereafter, upon completion of the data call, the UE may reconfigure its usage mode from the data centric mode to the voice centric mode at stage 818. This may be done automatically at the completion of the data connection and / or by the completion or termination of the execution of the triggering application.

At stage 835, a tracking area update (TAU) procedure may be initiated. This may in turn respond to a change in the operating setting of the UE to speech center. If selective idle mode camping is applied, the UE 810 should receive new cell selection priorities from the network and give higher priority to 2G / 3G (eg, GERAN / UTRAN). For example, as part of stage 835, the network may provide a new IdleModeMobilityControlInfo IE to the UE. Based on this information, the UE may later select the appropriate circuit switched (CS) cell and associated base station at stage 818. For example, the UE may return to the previous 2G / 3G cell camped on at stage 812 or select a new 2G / 3G cell. This can be done as part of the standard cell selection procedure.

FIG. 9 illustrates details of one embodiment of a process 900 that may be implemented by a user terminal, such as UE 810 of FIG. 8. At stage 910, a user terminal operating in idle mode on a first wireless network cell, such as a 2G or 3G network cell, may be camped on the first wireless network cell. The first wireless network may be a GERAN or UTRAN network. At stage 920, the data-oriented application can be executed on the user terminal. Data-oriented applications may be applications requiring high QoS, such as high data rate video or other connections. At stage 930, the user terminal usage mode may be changed based at least in part on an application running on the user terminal. For example, the user mode may change from voice centric mode to data centric mode. At stage 940, a Routing Area Update (RAU) procedure is initiated. The RAU procedure may include providing information associated with the usage mode change from the user terminal and receiving new cell priority information from the wireless network at stage 950.

Process 900 may further include selecting an E-UTRAN cell at stage 960. Stage 960 may be performed in parallel with stage 940 and / or stage 950 or before stage 940 and / or stage 950 in some implementations. At stage 960, an E-UTRAN cell, such as an LTE cell, may be selected by the UE and a connection with the E-UTRAN cell may be established. The E-UTRAN cell may be an LTE cell served by an eNB. At stage 970, the data call may be performed between the UE and the eNB in a packet line (PS) format. After completing the data communication between the UE and the eNB, the UE may return to the 2G or 3G network cell at stage 980, which may be the same cell where the UE was originally camped on or may be a different cell.

Stage 960 for selecting an E-UTRAN cell may be initiated, for example, before receipt of new cell priority information. Alternatively or additionally, the stage of selecting an E-UTRAN cell may be initiated in response to a change in user mode on the user terminal. The usage mode can be changed by the application, such as a change in configuration parameters on the UE from the application.

Process 900 may further include initiating a tracking area update (TAU) procedure from the user terminal after completing stage 970 data communication. The 2G / 3G wireless network cell may be selected in response to the new information received in the TAU procedure. The second wireless network cell may be a GERAN or UTRAN cell. The method may further comprise camping the user terminal on the second wireless network cell.

Process 900 can be implemented in a tangible medium. For example, process 900 may be implemented as a computer program product comprising a computer-readable medium having codes for causing a computer to perform one or more of the stages shown in FIGS. 8 and / or 9. Can be.

Process 900 may be implemented in a communication system or communication device, such as a user terminal or UE, configured to perform one or more of the stages shown in FIGS. 8 and / or 9.

Alternatively or additionally, the communication system or communication apparatus may include one or more means for performing one or more of the stages shown in FIGS. 8 and / or 9 in a device such as a user terminal or a UE.

FIG. 10 illustrating an example of a process flow 1000 in one of a user terminal or UE 1010 in idle mode camping on a 2G / 3G cell at stage 1012 as previously described with respect to FIG. 1B. Note now. The process flow 1000 is similar to the process flow 800 shown in FIG. 8, but in process flow 1000 the UE 1010 does not change the configuration settings (eg, user terminal usage mode) without changing 4G /. It is allowed to reselect another cell such as an LTE cell. In general, it may not be desirable to automatically decide to reselect cells (when camping on 2G / 3G cells) by ignoring cell reselection priorities provided by the network (without network control). Thus, as described below in connection with FIG. 10, a UE may be provided with limited permission to reselect a cell based on cells of a particular type or class, such as cells requiring a high data rate connection.

To implement this approach, as shown in FIG. 10, the UE 1010 is served by a base station node, such as a base station controller (BSC) or radio network controller (RNC) 1050, depending on the type of 2G / 3G network. Can be. The BSC / RNC 1050 may be further coupled to the OMA DM server node 1070. At stage 1012, the UE 1010 may be camped on a 2G / 3G cell as shown in FIG. 1B. At stage 1031, the “voice centric” UE 1010 may receive permission to reselect a new cell (eg, a 4G / LTE cell) for certain types of applications and associated data requirements. This may be signaled from the OMA DM server 1070 at stage 1031. The decision to reselect the 4G / LTE cell may be based on the UE's configuration settings (eg, internal usage mode settings) as well as the grant. At stage 1014, the application triggers a data call, and if the data call is in a licensed class, at stage 1016 the UE may select the appropriate 4G / LTE cell and connect to the associated base station / eNB. When doing this, the UE 1010 may ignore reselection priorities (eg, cell priority information) provided from the network to the 4G / LTE cell. At stage 1033, the UE 1010 may perform a data call on the selected packet switched 4G / LTE network and the associated eNB. At stage 1018, the UE may later reselect the 2G / 3G cell, which may be the original 2G / 3G cell or another cell that UE 1010 camped on at stage 1012. .

Policies that define the appropriate classes of currencies for authorized PS escalation can be defined by the operator. For example, they may be based on the required QoS and / or data throughput or other requirements. One example policy criterion is listed below.

GBR> 64 kpbs service must comply with LTE

GBR <64 kpbs services must comply with 2G / 3G.

MBR / AMBR> 16 Mbps services must comply with LTE.

MBR / AMBR> 2 Mbps services must comply with LTE.

MBR / AMBR <2Mbps services should conform to 2G / 3G.

FIG. 11 illustrates details of one embodiment of a process 1100 that may be implemented by a user terminal, such as UE 1010 of FIG. 10, consistent with process flow 1000 shown in FIG. 10. At stage 1110, the user terminal in idle mode may be camped on a first wireless network cell, such as a GERAN or UTRAN cell. At stage 1120, new cell priority information that may be assigned by the network may be received at the user terminal. The new cell priority information may include cell selection priority and may further include permission from the user terminal to move to the E-UTRAN cell for calls of a predetermined class. The move to the E-UTRAN cell may be initiated in response to an application running on a user terminal that requires a high QoS such as a high data rate. At stage 1130, the application may trigger a data call or connection, which may require a data rate within the predefined class of calls (eg, a data rate above a predefined threshold). . Call priority information may include defined cell selection priorities, such as limited cell selection for a 2G or 3G network when the UE enables 4G connection and a 4G network such as an LTE network is available.

At stage 1140, the UE may ignore cell priority information subject to the grant. By ignoring the defined cell priority, at stage 1150 the UE can select the E-UTRAN network cell and associate the base station / eNB (if the call requirements are within the authorized classes of predefined class). . At stage 1160, the UE may be connected to the eNB to conduct a data call and transfer data between the UE and the eNB. Upon completion of the call, at stage 1170, the UE may return to the 2G or 3G network, which may be the original network or the newly selected network.

Cell priority information may be defined based on restrictions on cell types accessible by the user terminal, such as, for example, carrier-preference, priority or restrictions on 2G or 3G network cells. Process 1100 may further include receiving a trigger from an application running on the user terminal to initiate a data call and in response to the trigger, ignoring the assigned cell priority that matches the grant. For example, the new call priority information may allow for escalation of services for user terminals from 2G or 3G networks to 4G networks, such as LTE networks, subject to predefined call classifications.

The first wireless network cell may be, for example, a GERAN cell, and the E-UTRAN cell may be an LTE cell served by an eNB. Alternatively, the first wireless network cell may be a UTRAN cell and the E-UTRAN cell may be an LTE cell. The user terminal may be a multi-mode UE.

Predefined classes of data calls may include, for example, data calls requiring bit rates exceeding a predefined threshold. The predefined threshold may be 64 kilobits per second, 2 megabits per second, 16 megabits per second, or other predefined value that may be based on network, device, and / or application capabilities or requirements.

Process 1100 may be implemented with a tangible medium. For example, process 1100 may be implemented as a computer program product comprising a computer-readable medium having codes for causing a computer to perform one or more of the stages shown in FIGS. 10 and / or 11. .

Process 1100 may be implemented in a communication system or communication device, such as a user terminal or UE, configured to perform one or more of the stages shown in FIGS. 10 and / or 11.

Alternatively or additionally, the communication system or communication apparatus may include one or more means for performing one or more of the stages shown in FIGS. 10 and / or 11 in a device such as a user terminal or a UE.

FIG. 12 illustrates details of one embodiment of a process 1200 that may be implemented by a base station or NB, such as the BSC or RNC of FIG. 10. Process 1200 may be performed in connection with process 1100 described in FIG. 11. At stage 1210, cell priority information for a user terminal, such as UE 1010 of FIG. 10, may be received or generated at base stations, such as base station 1050 of FIG. 10. Furthermore, data defining the permission to allow the user terminal to move to a different cell type, such as an LTE cell, may be provided when the cell priority information limits the cell types to 2G / 3G cells. The grant may be a binary on / off grant and / or may include information about the classification of predefined currencies authorized for escalation. At stage 1220, cell priority information may be sent to the user terminal with permission. For example, the user terminal may be camped on a 2G or 3G cell, such as a GERAN or UTRAN cell, and preferences may limit the user terminal to operation on 2G or 3G cells. The authorization information may cause the user terminal to move to a 4G cell, such as an LTE cell, when the associated call is in predefined class of calls, such as high data rate calls.

Process 1200 may be implemented with a tangible medium. For example, the process 1200 may be implemented as a computer program product comprising a computer-readable medium having codes for causing a computer to perform one or more of the stages shown in FIGS. 10, 11 and / or 12. Can be.

Process 1200 may be implemented in a communication system or communication device, such as a base station or Node B, configured to perform one or more of the stages shown in FIGS. 10, 11, and / or 12.

Alternatively or additionally, the communication system or communication apparatus may include one or more means for performing one or more of the stages shown in FIGS. 10, 11 and / or 12 in a device such as a base station or Node B. .

13 is now illustrating an example of a process flow 1200 between a user terminal or UE 1310 in idle mode camping on a 2G / 3G cell at stage 1312 as previously described with respect to FIG. 1B. It is noted. The process flow 1300 is similar to the process flow 800 shown in FIG. 8 and the process flow 1000 shown in FIG. 10, but in the process flow 1300 radio resource control (RRC) protocols of 2G / 3G RAT are Used while preventing signaling at the NAS level.

At stage 1331, the UE 1310 triggered by the executing application may send an RRC Connection Request message (to UTRAN) or a Channel Request message (on GERAN). The message includes, for example, a cause indicator defining call requirements for "data call with special QoS parameters" (eg, the required high data rate / throughput). Typically, the CAUSE indicator should only be used after the UE 1310 finds an appropriate 4G / LTE cell.

The RAN entity (e.g., RNC or BSC 1350) is then stage 1335 to redirect the UE 1310 to the identified 4G / LTE network without involving core entities or associated functions. Immediate decision can be performed at. This may be advantageous when the UE may want to set up a connection with the GERAN / UTRAN network and avoid problems that should not be redirected to the LTE network by mistake. At stage 1335, the RAN 1350 may send a corresponding RRC Release Message (UTRAN) or Channel Release (GERAN) message containing appropriate redirection information to the 4G / LTE network cell and associated base station. Then, at stage 1316, the UE may establish a connection with the LTE base station and perform the desired data call.

FIG. 14 illustrates details of one embodiment of a process 1400 that may be implemented by a user terminal or UE, such as UE 1310 of FIG. 13. Process 1400 may be performed in connection with process 1300 described in FIG. 13. At stage 1410, the user terminal may be camped in an idle mode in the first wireless network cell. The first wireless network may be a GERAN or UTRAN network cell. At stage 1420, a trigger may be received from an application running on a user terminal. The trigger can be a trigger for data calls with specific QoS requirements. At stage 1430, an appropriate E-UTRAN network cell, such as a 4G / LTE cell, may be identified. At stage 1440, after identification of the E-UTRAN cell, the request message may be sent to the first wireless network with a message that includes a cause indicator for the data call. The cause indicator may be associated with a particular required QoS and / or data rate as described previously with respect to FIG. 13. At stage 1450, a release message with direction change information to the E-UTRAN network cell associates the base station / eNB. At stage 1460, data calls and data communications may be performed between the UE and the eNB.

The first wireless network cell may for example be a GERAN cell and the E-UTRAN cell may be an LTE cell. The request message may be a GERAN channel request message, and the release message may be a GERAN channel release message. Alternatively, the first wireless network cell may be a UTRAN cell and the E-UTRAN cell may be an LTE cell. The request message may be a UTRAN RRC connection request message, and the release message may be a UTRAN RRC release message. The user terminal may be a multimode UE.

The cause indicator may include information defining a requirement for a data call with specific quality of service (QoS) parameters or requirements. QoS parameters or requirements may relate to the minimum requirement data rate.

Process 1400 may further include, for example, redirecting the user terminal to an E-UTRAN network cell and performing data communications associated with an application on the selected E-UTRAN cell. The user terminal may be redirected to the E-UTRAN network cell without performing a full RRC connection establishment procedure. The user terminal may be redirected to an E-UTRAN network cell without performing a non-access layer (NAS) procedure for secure setup.

Process 1400 may be implemented with tangible media. For example, process 1200 may be implemented as a computer program product comprising a computer-readable medium having codes for causing a computer to perform one or more of the stages shown in FIGS. 13 and / or 14. Can be.

Process 1400 may be implemented with a communication system or communication device, such as a base station or Node B, configured to perform one or more of the stages shown in FIGS. 13 and / or 14.

Alternatively or additionally, the communication system or communication apparatus may include one or more means for performing one or more of the stages shown in FIGS. 13 and / or 14 in a device such as a user terminal or a UE.

FIG. 15 illustrates details of one embodiment of a process 1500 that may be implemented by a base station or Node B, such as the BSC / RNC 1350 shown in FIG. 13. Process 1500 may be performed in connection with process 1400 described in FIG. 14, consistent with process flow 1300 of FIG. 13. At stage 1510, a connection message may be received, which includes a new cause provided from a user terminal, such as UE 1310 of FIG. 13. At stage 1520, the connection release information may be transmitted from the base station. The connection release information may include direction change information for changing the direction of the UE to the 4G / LTE network identified by the user terminal.

Process 1500 may be implemented with a tangible medium. For example, the process 1500 may comprise a computer-readable medium having code for causing a computer to perform one or more of the stages shown in FIGS. 13, 14 and / or 15. It can be implemented as.

Process 1500 may be implemented with a communication system or communication device, such as a base station or node B, configured to perform one or more of the stages shown in FIGS. 13, 14, and / or 15.

Alternatively or additionally, the communication system or communication apparatus may include one or more means for performing one or more of the stages shown in FIGS. 13, 14 and / or 15 in a device such as a base station or Node B. have.

In some implementations, a non-access layer (NAS) -based implementation can be used to provide PS escalation. Such implementations require NAS level signaling and may be similar to the CS fallback solutions previously described herein. Examples of similar procedures for various call scenarios are illustrated in FIG. 1B. In particular, a user terminal or UE camped on or connected to a 2G or 3G network at stages 112B, 114B, 152B or 154B may move to 4G networks, such as an LTE network, as shown in FIG. 1B. For example, paging may be used for an idle mode UE at stage 152B, while for the active mode UE at stage 154B (as will be described further below), SGSN is responsible for PDP context activation. Can trigger. At stage 170B, the UE may transmit a service request in lu mode depending on the network type, and PS escalation ends at stages 182B, 184B, or 186B. In general, these are three types of solutions: 1) RRC / channel release of GERAN / UTRAN, with a change of direction to E-UTRAN; 2) PS handover from GERAN / UTRAN to E-UTRAN; 3) may be classified as an Inter-RAT Cell Change Order (CCO) (not applicable to UTRAN) from GERAN to E-UTRAN.

Attention is now directed to FIG. 16, which illustrates an example of a process flow 1600 between a user terminal or UE 1610 in idle mode camping on a 2G / 3G cell as previously described with respect to FIG. 1B. At stage 1612, the UE 1610 may initiate a radio resource control (RRC) connection establishment. In a similar case, if the UE is in an active state, this step need not be performed. At stage 1615, the UE 1610 may transmit a Non-Access Layer (NAS) Service Request message to the Serving GPRS Support Node (SGSN) 1640 (which may be S4-SGSN). The SGSN 1640 may then initiate a change of direction of the UE 1610 to the E-UTRAN network, and at stage 1617 a Radio Access Network Application Part (RANAP) with a PS escalation indicator. Application Part) message can be sent. An existing common ID message may be used and extended for this part (eg, corresponding to an initial context setup request or a UE context modification request as defined in 3GPP TS 36.413). At stage 1622, the network may optionally request message reporting from the UE, after which LTE channels are measured at the UE and reporting information is provided. Then, at stage 1623, the RNC 1620 may send an RRC Connection Release message (instead of accepting the connection), which may include direction change information (to the target E-UTRAN cell). Moreover, the RNC 1620 may send an Iu Release Request message to the SGSN 1640 (informing the SGSN that the UE remains) at stage 1625. The signaling connection may be released locally to both the UE 1610 and the SGNS 1640. If inter-system signaling reduction (ISR) is not active, the TAU procedure must be performed at stage 1628, then any existing bearers between SGSN 1640 and serving gateway (SGW) 1660 may be released. have. At stage 1633, the UE may establish a PS connection with an E-UTRAN network cell and a base station, which may be an LTE eNB, such as eNB 1630. Thereafter, data may be transferred between the UE 1610 and the eNB 1630 in a packet switched mode.

FIG. 17 illustrates another example of a process flow 1700 between a user terminal or UE 1710 in an idle mode camping on a 2G / 3G cell as described below in connection with FIG. 1B. The procedure 1700 is different from the procedure 1600 except that the packet switched handover (PSHO) procedure defined in 3GPP TS 23.401 is used at stage 1726 rather than the RRC release procedure shown at stage 1623 of FIG. similar. At stage 1715, UE 1710 may send a service request message to its associated base station (BSS or RNC 1730) and SGSN 1760. Thereafter, at stage 1917, the SGSN may transmit a RANAP common ID with the PS escalation indicator to the BSS / RNC 1730. The other stages of FIG. 17 are the same or similar to the corresponding stages shown in FIG.

18 illustrates another example of a process flow 1800 between a user terminal or UE 1810 in idle mode camping on a GERAN cell as previously described with respect to FIG. 1B. Process flow 1800 is similar to process flows 1600 and 1700 except that a cell change order (CCO) procedure is used instead of an RRC release or PSHO procedure. This procedure is applicable to GERAN networks. At stage 1815, a message corresponding to the service request is sent from the UE 1810 to the BSS 1830 and the SGSN 1860. At stage 1817, SGSN initiates the UE's direction to the E-UTRAN network (e.g., LTE network served by eNB 1820), and BSSGP DL-UNITDATA (Geran network) with PS escalation indicator The message may be sent to the BSC 1830. Thereafter, at stage 1823, the BSS 1830 may send a Cell Change Order (CCO) message to the UE 1810. The other stages of FIG. 18 may be the same or similar to the corresponding stages shown in FIGS. 16 and 17.

19 illustrates a base station 1910 (ie, NB, eNB, HeNB, etc.) and user terminal 1950 (ie, in an example communication system 1900 in which aspects and functions as described herein may be implemented). , A terminal, an AT or a UE, etc.) illustrates a block diagram of one embodiment of the present invention. These components may correspond to the components shown in FIGS. 3-7 and may be configured to implement the processes previously illustrated herein, as described in connection with FIGS. 8-18.

In addition to transmitting and receiving signaling from other base stations, as well as providing other functionality as described herein, various functions, such as coordination with other base stations (not shown) of other networks, are shown in base station 1910. Processors and memories (and / or other components not shown). For example, the UE 1950 may access the base stations 1910 and / or other base stations (not shown) (e.g., base stations or non-networks of other network types as previously described herein). Receiving signals from serving base stations), facilitating handovers, receiving DL signals, determining channel characteristics, performing channel estimates, demodulating received data and generating spatial information, One or more modules for determining information and / or for determining other information and / or power level information associated with base station 1910 or other base stations (not shown).

In one embodiment, base station 1910 may coordinate with other base stations, such as base stations of different network / RAT types, as previously described herein to facilitate multimode operation. This may be performed in one or more components (or other components not shown) of the base station 1910, such as processors 1914, 1930 and memory 1932. The base station 1910 may also include a transmission module that includes one or more components (or other components not shown) of the eNB 1910, such as the transmission modules 1924. The base station 1910 provides such functions as signaling direction changes of served UEs, communication with associated MMEs or other network nodes, direction change information, PS to CS switching information, and other information as described herein. May include an interference cancellation module including one or more components (or other components not shown), such as processors 1930, 1942, demodulator module 1940, and memory 9332.

The base station 1910 manages and / or herein transmitter and / or receiver modules that may be used to communicate with UEs or other nodes such as MMEs, SGWs or other nodes of the same or other network types. It may include a processor module including one or more components (or other components not shown), such as processors 1930 and 1914 and memory 1932 to perform the described base station functions. Base station 1910 may also include a control module for controlling the receiver function. The base station 1910 may provide networking with other systems, such as, for example, backhaul systems of the core network (CN) via the backhaul connection module 1990, or as shown or described in connection with FIGS. 1-7. It may include a network connection module 1990 for providing networking with other components, such as.

Similarly, the UE 1950 may include a receiving module that includes one or more components (or other components not shown) of the UE 1950, such as receivers 1954. The UE 1950 may also include one or more components (or illustrated) of the UE 1950, such as processors 1960, 1970 and memory 1972, to perform processing functions associated with user terminals as described herein. Or other components that are not included). This is for example not only receiving and searching for direction change targets and alternative targets, but also CS call setup procedures, RAU and TAU procedures, handovers to other networks and / or the other previously described herein. Performing procedures.

In one embodiment, one or more signals received at the UE 1950 are processed to receive DL signals and / or to extract information such as SIB information from the DL signals. Further processing may be associated with base stations such as base station 1910 and / or Node Bs (not shown) or other base stations such as eNBs to enable direction change commands, channel characteristics, power information, spatial information. And / or estimating other information such as UTRAN and GERAN networks as well as estimating and locating direction change targets and / or alternative targets, such as estimating other information, fallback targets, and the like. And facilitating communication with associated nodes, such as base stations or Node Bs.

The UE 1950 may include one or more receiver and transmitter modules that may be configured for modulation operation to perform communication with LTE base stations as well as other types of base stations, such as base stations in UTRAN and / or GERAN networks. Can be. The memories 1932, 1972 may be used to store computer code for execution on one or more processors, such as processors 1960, 1970, 1938, to implement processes associated with the aspects and functionality described herein. have.

In operation, at base station 1910, traffic data for multiple data streams may be provided from a data source 1912 to a transmit (TX) data processor 1914, where the data is processed to provide one or more UEs. 1950. In an aspect, each data stream is processed, the individual transmitter of the base station 1910, the sub-systems (transmitters (1924 ₁ -1924 can be transmitted through the illustrated) as _Nt TX data processor 1914 is coded Receive, format, code, and interleave the traffic data for that data stream based on a particular coding scheme selected for each data stream to provide the data that is generated. Determine a signal pattern and provide a transmission signal comprising a reference signal and / or beamforming information in the selected pattern.

The coded data for each data stream may be multiplexed with the pilot data using OFDM techniques. Pilot data is typically a known data pattern that is processed in a known manner and can be used in the receiver system to estimate the channel response. For example, the pilot data may comprise a reference signal. Pilot data is provided to the TX data processor 1914 shown in FIG. 19 and may be multiplexed with the coded data. Next, pilot multiplexed for each data stream based on a particular modulation scheme selected for each data stream (e.g., BPSK, QSPK, M-PSK, or M-QAM, etc.) to provide modulation symbols. And the coded data is modulated (ie, symbol mapped), and the data and pilot can be modulated using different modulation schemes. The data rate, coding, and modulation for each data stream is performed by the processor 1930 based on instructions stored in memory 1932 or other memory or instruction storage medium (not shown) of the UE 1950. Can be determined by them.

Modulation symbols for all data streams may then be provided to the TX MIMO processor 1920, which may further process the modulation symbols (eg, for OFDM). . TX MIMO processor 1920 may then provide Nt modulation symbol streams to Nt transmitters (TMTR) 1922 ₁ to 1922 _Nt . Various symbols may be mapped to associated RBs for transmission.

는 각각의 전송 안테나에 대응하는 가중치들의 세트로 구성된다. 빔을 따라 전송하는 것은 해당 안테나에 대한 빔 가중치에 의해 스케일링되는 모든 안테나들을 따라 변조 심볼 x를 전송하는 것에 대응하며, 즉 안테나 t를 통해 전송된 신호는

이다. 다수의 빔들이 전송될때, 하나의 안테나를 통해 전송된 신호는 상이한 빔들에 대응하는 신호들의 합이다. 이는

으로서 수학적으로 표현될 수 있으며, 여기서

빔들은 전송되며,

는 빔

를 사용하여 송신되는 변조 심볼이다. 다양한 구현들에서, 빔들은 다수의 방식들로 선택될 수 있다. 예를들어, 빔들은 UE로부터의 채널 피드백, eNB에서 이용가능한 채널 지식에 기초하여 또는 예를들어 인접 매크로셀에 대하여 간섭 완화를 용이하게 하기 위하여 UE로부터 제공되는 정보에 기초하여 선택될 수 있다.TX MIMO processor 1930 can further apply beamforming weights to one or more antennas corresponding to the symbols of the data streams, from which a symbol is transmitted. This may be done by using information such as channel estimation information provided by a network node, such as a UE, and / or with reference signals and / or spatial information provided from this network node. E.g,

Consists of a set of weights corresponding to each transmit antenna. Transmitting along the beam corresponds to transmitting a modulation symbol x along all the antennas scaled by the beam weight for that antenna, i.e., the signal transmitted over antenna t

to be. When multiple beams are transmitted, the signal transmitted through one antenna is the sum of the signals corresponding to the different beams. this is

Can be expressed mathematically as

Beams are transmitted,

The beam

Is a modulation symbol transmitted using. In various implementations, the beams can be selected in a number of ways. For example, the beams may be selected based on channel feedback from the UE, channel knowledge available at the eNB or based on information provided from the UE, for example to facilitate interference mitigation for neighboring macrocells.

Each transmitter sub-system 1922 _I through 1922 _Ny receives and processes a separate symbol stream to provide one or more analog signals, and adds analog signals to provide a modulated signal suitable for transmission over a MIMO channel. Condition (eg, amplify, filter, and upconvert). Next, N _t from transmitters (1922, 1922 ₁ to _Nt) Modulated signals are transmitted from N _t antennas 1924 ₁ to 1924 _Nt , respectively.

At the UE 1950, the transmitted modulated signals may be received by N _r antennas 1952 _I through 1952 _Nr , with the received signal from each antenna 1952 being a separate receiver (RCVR) ( 1954 _I to 1954 _Nr ). Each receiver 1954 conditions (eg, filters, amplifies, and downconverts) the individual received signal, digitizes the conditioned signal to provide samples, and digitizes the corresponding "received" symbol stream. The samples can be further processed to provide.

Then, RX data processor 1960 is N _S of "detected (detected)" N _r of the receiver based on a particular receiver processing technique to provide a symbol stream to provide estimates of the N _S of the transmitted symbol stream s is from ₍₁ to 1954 1954 _Nr) receive N _r of received symbol streams, and processing. RX data processor 1960 demodulates, de-interleaves, and decodes each detected symbol stream to recover traffic data for the data stream. Processing by the RX data processor 1960 may typically be complementary to the processing performed by the TX MIMO processor 1920 and the TX data processor 1914 at the base station 1910.

The processor 1970 may periodically determine a precoding matrix for use as described further below. Processor 1970 can then formulate a reverse link message that can include the matrix index portion and the rank value portion. In various aspects, the reverse link message may include various types of information regarding the communication link and / or the received data stream. The reverse link message is processed by the TX data processor 1938, which can also receive traffic data for multiple data streams from the data source 1936, modulated by the modulator 1980, and the transmitters 1954 _1. To 1954 _Nr ), and may be transmitted back to the base station 1910. The information sent back to the base station 1910 may include spatial information and / or power levels that provide beamforming to mitigate interference from the base station 1910.

At the base station 1910, modulated signals from the UE 1950 are received by the antennas 1924, conditioned by the receivers 1922, and to demodulate, to extract the message sent by the UE 1950. Demodulated by 1940 and processed by RX data processor 1942. Processor 1930 then determines which precoding matrix to use to determine beamforming weights, and then processes the extracted message.

20 illustrates additional details for one embodiment of a communication device 2000 that may be a user terminal or a component of a user terminal, such as a multimode UE, as described herein. Apparatus 2000 includes one or more multimode receiver modules 2010 that may be configured to receive signals from multiple network types, such as LTE networks, UTRAN networks, GERAN networks, and / or other networks. can do. Similarly, apparatus 2000 may include one or more transmitter modules 2020 that may be configured for similar multimode capabilities. Apparatus 2000 may include one or more processor modules 2030 that may be configured to implement the processing described herein. Device 2000 may also include one or more memory spaces 2040 that may include program modules 2050, data 2060, one or more operating systems 2070, as well as other memory storage capabilities (not shown). It may include. Memory space 2000 may include a number of physical memory devices such as flash, DRAM, SRAM, optical storage and / or other memory or storage technologies.

The program module 2000 may execute applications, receive and respond to triggers to move to or from E-UTRAN / LTE networks, respond to PS escalation requests, change direction. Detecting access failures to targets such as targets, performing RAU and TAU procedures, performing CS setup procedures, and / or performing other functions or processes as previously described herein. Modules such as those described herein may be included to perform user terminal functions such as those described in FIG. Program modules 2050 may be configured to perform these various functions with respect to processor modules 2030, receiver and transmitter modules 2020, and / or other modules (not shown). Data 2060 may include data associated with the execution of program modules 2050 that may be implemented by operating system (s) 2070 or that may be implemented with operating system (s) 2070. .

21 illustrates additional details of one embodiment of a communication device 2100, which may be a base station such as a Node B (NB) or an eNB as described herein. Apparatus 2100 may include one or more transmit and receive modules (collectively depicted as transceiver module 2110) for communicating with served nodes, such as user terminals or UEs. The apparatus 2100 may also include one or more core network (CN) modules configured to communicate with core network components such as MMEs, SGWs, and the like. Apparatus 2100 may include one or more processor modules 2130 that may be configured to implement processing associated with various types of base stations described previously herein. Device 2100 may also include one or more memory spaces 2140 that may include program modules 2150, data 2160, one or more operating systems 2170, as well as other memory storage capabilities (not shown). It may include. Memory space 2140 may include a number of physical memory devices such as flash, DRAM, SRAM, optical storage, and / or other memory or storage technologies.

The program module 2150 responds to requests from UEs, for example, to coordinate and provide direction change requests, for example, to move PS connections from GERAN or UTRAN networks to E-UTRAN / LTE networks. May include modules as described herein to perform base station functions such as performing coordination PS suspension with other network components such as MMEs, SGWs, etc., as well as other base station functions as described herein. have.

Program modules 2150 may be configured to perform these various functions with respect to processor module (s) 2130, transceiver modules 2110, core network modules 2120, and / or other modules (not shown). Can be. Data 2160 may include data associated with the execution of program modules 2150 that may be implemented by operating system (s) 2170 or that may be implemented with operating system (s) 2170.

In some configurations, the apparatus for wireless communication includes means for performing various functions as described herein. In one aspect, the aforementioned means may be a processor or processors and associated memory in which embodiments such as those shown in FIG. 19 reside and configured to perform the functions recited by the aforementioned means. For example, this is illustrated here for example in FIGS. 1-7 and 19 to perform the multimode functions described herein in processes or methods such as described in connection with FIGS. 8-18, for example. Modules or devices residing in UEs, NBs, eNBs, MMEs, SGWs or other gateways, MSCs, and / or other network nodes as described. In another aspect, the aforementioned means may be a module or any apparatus configured to perform the functions recited by the aforementioned means.

In one or more embodiments, the described functions, methods or processes may be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded as one or more instructions or code on the computer-readable medium. The computer-readable medium includes computer storage media. The storage medium may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise desired program code in the form of RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or instructions or data structures. May be used to store or carry and may include any other medium that can be accessed by a computer. As used herein, disks (disks and discs) are compact discs (CDs), laser discs (disc), optical discs (disc), digital versatile discs (DVD), floppy disks, and blue. A ray disc, wherein the discs usually reproduce the data magnetically, while the discs usually reproduce the data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

It should be understood that the specific order or hierarchy of steps or stages in the processes and methods disclosed is examples of exemplary approaches. Based upon design preferences, it should be understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may refer to voltages, currents, electromagnetic waves, magnetic fields, , Light fields or light particles, or any combination thereof.

Those skilled in the art further recognize that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. something to do. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented in hardware or software depends upon the design constraints imposed on the particular application and the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The various illustrative logic blocks, modules, and circuits described in connection with the embodiments disclosed herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or Other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein may be implemented or performed. A general purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some implementations, the processors can be processors such as communication processors specifically designed to implement the functionality of communication devices or other mobile or portable devices.

The steps or stages of a method, process or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in a RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

The claims are not intended to be limited to the aspects set forth herein, but the broadest scope consistent with the literary claims should be given, wherein the elements referred to in the singular form “a and only one” unless specifically stated so. It is not intended to mean "but rather to mean" one or more ". Unless specifically stated otherwise, the term “some” refers to one or more. The phrase referring to "at least one" of the list of items refers to any combination of these items including single members. As an example, at least one of "a, b, or c" b; c; a and b; a and c; b and c; It is intended to cover a, b and c.

The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the aspects set forth herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. The following claims and equivalents thereof are intended to define the scope of the present disclosure.

Claims (108)

A method for providing radio access technology (RAT) inter-mobility in a wireless communication system, comprising:
Camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Changing the user terminal usage mode from the voice-centric mode to the data-centric mode based on the application running on the user terminal;
Initiating a Routing Area Update (RAU) procedure from the user terminal, the RAU procedure providing information related to the usage mode change from the user terminal and receiving new cell priority information from the wireless network. Including;
Selecting an E-UTRAN cell; And
Performing data communications associated with the application with a base station of the E-UTRAN cell. 2. The method of claim 1, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 2. The method of claim 1, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. The method of claim 1, wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. The method of claim 1, wherein selecting the E-UTRAN cell is initiated prior to receipt of the new cell priority information. 6. The method of claim 5, wherein selecting the E-UTRAN cell is initiated in response to a change of usage mode on the user terminal. 6. The method of claim 5, wherein the mode of use is changed by the application. The method of claim 1, further comprising changing the user terminal usage mode from the data centric mode to the voice centric mode after completion of the data communications. Way. The method of claim 8, further comprising: initiating a tracking area update (TAU) procedure from the user terminal; And
In response to the new information received in the TAU procedure, selecting a second radio network cell, wherein the second radio network cell is a GERAN or UTRAN cell to provide inter-radio access technology (RAT) mobility. Way. 10. The method of claim 9, further comprising camping a user terminal on the second wireless network cell. A computer program product comprising a computer-readable medium,
The computer-readable medium causes the computer to:
Camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Change the user terminal usage mode from voice-centric mode to data-centric mode based on the application running on the user terminal;
Initiating a Routing Area Update (RAU) procedure from the user terminal, the RAU procedure providing information associated with the change of the user terminal usage mode from the user terminal and receiving new cell priority information from the wireless network. Including;
Select an E-UTRAN cell; And
And codes for causing data communications associated with the application with a base station of the E-UTRAN cell. 12. The computer program product of claim 11, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 12. The computer program product of claim 11, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. The computer program product of claim 11, wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. The computer program product of claim 1, wherein the codes comprise codes for causing the computer to select the E-UTRAN wireless network cell prior to receiving the new cell priority information. 16. The computer program product of claim 15, wherein the codes comprise codes for causing the computer to select the E-UTRAN cell in response to a change of the usage mode on the user terminal. The computer program product of claim 15, wherein the usage mode is changed by the application. 12. The computer program product of claim 11, further comprising code for causing the computer to change the usage mode for the user terminal from the data centric mode to the voice centric mode after completion of the data communications. 19. The computer program of claim 18, wherein the computer is configured to:
Initiate a Tracking Area Update (TAU) procedure from the user terminal; And
And in response to the new information received in the TAU procedure, codes for selecting a second wireless network cell, wherein the second wireless network cell is a GERAN or UTRAN cell. 20. The computer program product of claim 19, wherein the codes further comprise codes for causing the computer to camp the user terminal on the second wireless network cell. A multi-network communication device,
A receiver module configured to receive signals from a first wireless network cell and to camp a user terminal in an idle mode in the first wireless network cell, wherein the first wireless network cell is a GERAN or UTRAN cell;
A processor module configured to change a user terminal usage mode from a voice-centric mode to a data-centric mode based on an application executed on the user terminal; And
A transmitter module configured to initiate a Routing Area Update (RAU) procedure from the user terminal,
The RAU procedure comprises providing information associated with the usage mode change from the user terminal;
The receiver module is further configured to receive new cell priority information from the first wireless network;
The processor module is configured to select an E-UTRAN radio network cell; And
The transmitter and receiver modules are configured to perform data communications associated with the application with a base station of a selected E-UTRAN wireless network cell. The device of claim 21, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. The device of claim 21, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. The device of claim 21, wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. 22. The multi-network communication device of claim 21, wherein the processor module is configured to select the E-UTRAN radio network cell prior to receiving the new cell priority information. 27. The multi-network communication device of claim 25, wherein the processor module is configured to select the E-UTRAN radio network cell in response to a change of usage mode on the user terminal. 27. The device of claim 25, wherein the mode of use is changed by the application. 22. The multi-network communication device of claim 21, wherein the processor module is further configured to change the user terminal usage mode from the data centric mode to the voice centric mode after completion of the data communications. 29. The system of claim 28, wherein the transmitter module is further configured to initiate a Tracking Area Update (TAU) procedure from the user terminal; And
The processor module is further configured to select a second wireless network cell in response to the new information received in the TAU procedure, wherein the second wireless network cell is a GERAN or UTRAN cell. 30. The device of claim 29, wherein the receiver module is further configured to receive signals from the user terminal and camp the user terminal on the second wireless network cell. A multi-network communication device,
Means for camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Means for changing the user terminal usage mode from voice-centric mode to data-centric mode based on an application running on the user terminal;
Means for initiating a Routing Area Update (RAU) procedure from the user terminal, the RAU procedure providing information associated with the usage mode change from the user terminal and receiving new cell priority information from the wireless network. Includes;
Means for selecting an E-UTRAN cell; And
Means for performing data communications associated with the application with a base station of the E-UTRAN cell. 32. The multi-network communication device of claim 31, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 32. The device of claim 31, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 32. The device of claim 31, wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. 32. The device of claim 31, wherein selecting the E-UTRAN cell is initiated prior to receipt of the new cell priority information. 36. The device of claim 35, wherein selecting the E-UTRAN cell is initiated in response to a change in usage mode for the user terminal. 36. The device of claim 35 wherein the mode of use is changed by the application. 32. The multi-network communication device of claim 31, further comprising changing the user terminal usage mode from the data centric mode to the voice centric mode after completion of the data communications. 39. The apparatus of claim 38, further comprising: means for initiating a tracking area update (TAU) procedure from the user terminal; And
Means for selecting a second wireless network cell in response to the new information received in the TAU procedure, wherein the second wireless network cell is a GERAN or UTRAN cell. 40. The multi-network communication device of claim 39, further comprising means for camping a user terminal on the second wireless network cell. A method for providing radio access technology (RAT) inter-mobility in a wireless communication system, comprising:
Camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Receiving new cell priority information including permission to move to an E-UTRAN cell during a predefined class of data calls
Receiving a trigger from an application running on the user terminal to initiate the data call;
Ignoring the assigned cell priority based on the new cell priority information;
Selecting an E-UTRAN network cell; And
Performing data communications associated with the application for a selected E-UTRAN cell. 42. The method of claim 41 wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 42. The method of claim 41 wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 42. The method of claim 41 wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. 42. The method of claim 41 wherein the data classes of the predefined class include data calls requiring bit rates above a predefined threshold. 46. The method of claim 45, wherein the predefined threshold is 64 kilobits per second. 46. The method of claim 45, wherein the predefined threshold is 2 megabits per second. 46. The method of claim 45, wherein the predefined threshold is 16 megabits per second. A computer program product comprising a computer-readable medium,
The computer-readable medium causes the computer to:
Camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Receive new cell priority information that includes permission to move to an E-UTRAN cell during a predefined class of data calls;
Receive a trigger from an application running on the user terminal to initiate the data call;
Ignore the assigned cell priority based on the new cell priority information;
Select an E-UTRAN network cell; And
And codes for causing the transmission of data associated with the application using a base station of a selected E-UTRAN cell. 50. The computer program product of claim 49, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 50. The computer program product of claim 49 wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 50. The computer program product of claim 49, wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. 50. The computer program product of claim 49, wherein the data classes of the predefined class include data currencies that require bit rates above a predefined threshold. 54. The computer program product of claim 53 wherein the predefined threshold is 64 kilobits per second. 54. The computer program product of claim 53 wherein the predefined threshold is 2 megabits per second. 54. The computer program product of claim 53 wherein the predefined threshold is 16 megabits per second. A multi-network communication device,
Receive signals from a first wireless network cell, camping a user terminal in an idle mode in the first wireless network cell, wherein the first wireless network cell is a GERAN or UTRAN network cell and during a predefined class of data calls A receiver module configured to receive new cell priority information including permission to move to a UTRAN cell;
A processor module, configured to initiate a cell reselection procedure to a U-TRAN cell based on the new cell priority information and an application program executed on the user terminal; And
And a transmitter module, together with the receiver module, configured to provide communications associated with an application to a selected E-UTRAN cell. 59. The multi-network communication device of claim 57, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 59. The multi-network communication device of claim 57, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 59. The device of claim 57, wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. 59. The multi-network communication device of claim 57, wherein the predefined class of data calls comprises data calls requiring bit rates above a predefined threshold. 62. The multi-network communication device of claim 61, wherein the predefined threshold is 64 kilobits per second. 62. The multi-network communications device of claim 61, wherein the predefined threshold is 2 megabits per second. 62. The method of claim 61, wherein the predefined threshold is 16 megabits per second. A multi-network communication device,
Means for camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Means for receiving new cell priority information including permission to move to an E-UTRAN cell during a predefined class of data calls
Means for receiving a trigger from an application running on the user terminal to initiate the data call;
Means for ignoring assigned cell priority based on the new cell priority information;
Means for selecting an E-UTRAN network cell; And
Means for performing data communications associated with the application for a selected E-UTRAN cell. 65. The multi-network communication device of claim 64, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 65. The multi-network communication device of claim 64, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 65. The multi-network communication device of claim 64, wherein the user terminal is a UE and the base station of the E-UTRAN cell is an LTE eNB. 65. The multi-network communication device of claim 64, wherein the predefined class of data calls comprises data calls requiring bit rates exceeding a predefined threshold. 69. The multi-network communication device of claim 68, wherein the predefined threshold is 64 kilobits per second. 69. The multi-network communication device of claim 68, wherein the predefined threshold is 2 megabits per second. 29. The multi-network communication device of claim 28, wherein the predefined threshold is 16 megabits per second. A method for providing inter-radio access technology (RAT) -mobility in a wireless communication system,
Camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Receiving a trigger for a data call from an application running on the user terminal;
Determining an appropriate E-UTRAN network cell;
Sending the first wireless network a request message comprising a cause indicator for a data call; And
Receiving, from the first wireless network, a release message with direction change information from the E-UTRAN network cell to the inter-radio access technology (RAT). 73. The method of claim 72, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 80. The method of claim 73 wherein the request message is a GERAN channel request message and the release message is a GERAN channel release message. 73. The method of claim 72 wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 76. The method of claim 75 wherein the request message is a UTRAN RRC connection request message and the release message is a UTRAN RRC release message. 73. The method of claim 72, wherein the cause indicator comprises information defining a requirement for a data call with specific quality of service (QoS) parameters. 73. The method of claim 72, further comprising: redirecting the user terminal to the E-UTRAN network cell; And
Further comprising performing data communications associated with the application for a selected E-UTRAN cell. 80. The method of claim 78 wherein the user terminal is redirected to the E-UTRAN network cell without performing a maximum RRC connection establishment procedure. 79. The inter-radio accessibility (RAT)-mobility of claim 78, wherein the user terminal is redirected to the E-UTRAN network cell without performing a Non-Access Stratum (NAS) procedure for secure setup. Method for providing. A computer program product comprising a computer-readable medium,
The computer-readable medium causes the computer to:
Camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Receiving a trigger for a data call from an application running on the user terminal;
Determine an appropriate E-UTRAN network cell;
Send the first wireless network a request message including a cause indicator for a data call; And
And codes for receiving a release message with direction change information from the first wireless network to the E-UTRAN network cell. 82. The computer program product of claim 81 wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 83. The computer program product of claim 82, wherein the request message is a GERAN channel request message and the release message is a GERAN channel release message. 82. The computer program product of claim 81 wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 85. The computer program product of claim 84 wherein the request message is a UTRAN RRC connection request message and the release message is a UTRAN RRC release message. 84. The computer program product of claim 81, wherein the cause indicator comprises information defining a requirement for a data call with specific quality of service (QoS) parameters. 84. The method of claim 81, further comprising: redirecting the user terminal to the E-UTRAN network cell; And
And performing data communications associated with the application for a selected E-UTRAN cell. 88. The computer program product of claim 87 wherein the user terminal is redirected to the E-UTRAN network cell without performing a maximum RRC connection establishment procedure. 88. The computer program product of claim 87 wherein the user terminal is redirected to the E-UTRAN network cell without performing a non-access stratum (NAS) procedure for secure setup. A multi-network communication device,
A receiver module configured to receive signals from a first wireless network cell and to camp a user terminal in an idle mode in the first wireless network cell, wherein the first wireless network cell is a GERAN or UTRAN network;
A processor module configured to receive a trigger for a data call based on an application running on the user terminal and to determine an appropriate E-UTRAN network cell with the receiver module; And
A transmitter module configured to send the first wireless network a request message including a cause indicator for a data call, the receiver module having direction change information from the first wireless network to the E-UTRAN network cell; Further configured to receive the release message. 91. The multi-network communication device of claim 90, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 91. The multi-network communication device of claim 90, wherein the request message is a GERAN channel request message and the release message is a GERAN channel release message. 91. The multi-network communication device of claim 90, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 95. The multi-network communication device of claim 93, wherein the request message is a UTRAN RRC connection request message and the release message is a UTRAN RRC release message. 91. The multi-network communication device of claim 90, wherein the cause indicator comprises information defining a requirement for a data call with specific quality of service (QoS) parameters. 91. The apparatus of claim 90, wherein the transmitter, receiver and processor modules are
Redirect the user terminal to the E-UTRAN network cell; And
And further configured to perform data communications associated with the application for a selected E-UTRAN cell. 97. The multi-network communication device of claim 96, wherein the user terminal is redirected to the E-UTRAN network cell without performing a maximum RRC connection establishment procedure. 97. The multi-network communication device of claim 96, wherein the user terminal is redirected to the E-UTRAN network cell without performing a Non-Access Stratum (NAS) procedure for secure setup. A multi-network communication device,
Means for camping a user terminal in an idle mode in a first wireless network cell, wherein the first wireless network is a GERAN or UTRAN network;
Means for receiving a trigger for a data call from an application running on the user terminal;
Means for determining an appropriate E-UTRAN network cell;
Means for sending a request message to the first wireless network including a cause indicator for a data call; And
Means for receiving a release message with direction change information from the first wireless network to the E-UTRAN network cell. 107. The device of claim 99, wherein the first wireless network cell is a GERAN cell and the E-UTRAN cell is an LTE cell. 107. The device of claim 99, wherein the request message is a GERAN channel request message and the release message is a GERAN channel release message. The multi-network communication device of claim 99, wherein the first wireless network cell is a UTRAN cell and the E-UTRAN cell is an LTE cell. 103. The multi-network communication device of claim 102, wherein the request message is a UTRAN RRC connection request message and the release message is a UTRAN RRC release message. The multi-network communication device of claim 99, wherein the cause indicator comprises information defining a requirement for a data call with specific quality of service (QoS) parameters. 107. The method of claim 99, further comprising: redirecting the user terminal to the E-UTRAN network cell; And
And performing data communications associated with the application for a selected E-UTRAN cell. 107. The device of claim 105, wherein the user terminal is redirected to the E-UTRAN network cell without performing a maximum RRC connection establishment procedure. 107. The multi-network communication device of claim 105, wherein the user terminal is redirected to the E-UTRAN network cell without performing a non-access stratum (NAS) procedure for secure setup.

Images