Signaling extended EARFCN and E-UTRA bands in UMTS networks

Embodiments of a user equipment (UE) and Node-B to operate in a wireless communication network using extended evolved absolute radio frequency channel numbers (EARFCN) and evolved Universal Terrestrial Radio Access (E-UTRA) frequency bands are disclosed herein. The UE may comprise transceiver and processing circuitry to receive a multiple frequency band indicators (MFBI) list that includes list elements corresponding to E-UTRA frequency bands on which neighboring LTE cells are operated. The MFBI list corresponds to an entry in the E-UTRA frequency and priority list or the E-UTRA frequency and priority extension list. The number of list elements for E-UTRA frequency and priority information corresponds to a sum of the number of entries in an E-UTRA frequency and priority list and a number of entries in an E-UTRA frequency and priority extension list. Other embodiments are disclosed.

TECHNICAL FIELD

Embodiments pertain to wireless communications. Some embodiments relate to cellular communication networks including long-term evolution (LTE) networks and universal mobile telecommunications system (UMTS) networks. Some embodiments relate to multiple frequency band indicator (MFBI) signaling to support extended value ranges of evolved absolute radio frequency channel numbers (EARFCNs) and evolved Universal Terrestrial Radio Access (E-UTRA) frequency bands in UMTS.

BACKGROUND

Multiple Frequency Band Indicator (MFBI) signaling was introduced recently in 3rd Generation Partnership Project (3GPP) standards to allow elements of a cell, such as a Node-B or evolved Node-B (eNodeB) to broadcast in more than one band if the absolute frequency of the cell fell into multiple overlapping bands. However, there are ambiguities and signaling inefficiency concerns regarding MFBI support in universal mobile telecommunications system (UMTS) networks.

DETAILED DESCRIPTION

FIG. 1shows a wireless communication network100, according to some embodiments described herein. The wireless communication network100may include a Node-B102, and user equipment (UEs)111and112. Node-B102and UEs111and112may operate to wirelessly communicate with each other in the wireless communication network100. While some embodiments herein are described regarding a Node-B102operating in accordance with3rd Generation Partnership Project (3GPP) Universal Mobile Telecommunications System (UMTS) systems, other embodiments can be applicable to systems operating in accordance with standards for 3GPP Long Term Evolution (LTE). The term “Node-B” should be understood as a simplification that references the combination of Node-B elements (e.g., radio frequency (RF), physical layer (PHY), and parts of a medium access control layer (MAC) sublayer) and Radio Network Controller (RNC) elements (e.g., parts of a MAC sublayer, RLC, PDCP and Radio Resource Control (RRC)) in accordance with UMTS standards.

The wireless communication network100can include a universal terrestrial radio access network (UTRAN) using 3GPP-UMTS standards operating in time division duplex (TDD) mode, frequency division duplex (FDD), or dual-mode operation. The wireless communication network100can further support an evolved UTRAN (EUTRAN) using 3GPP LTE standards operating in TDD mode or in FDD mode. Additional examples of wireless communication network100include Worldwide Interoperability for Microwave Access (WiMax) networks, 3rd generation (3G) networks, Wi-Fi networks, and other wireless data communication networks.

Examples of UEs111and112include cellular telephones (e.g., smartphones), tablets, e-readers (e.g., e-book readers), laptops, desktops, personal computers, servers, personal digital assistants (PDAs), web appliances, set-top boxes (STBs), network routers, network switches, network bridges, parking meters, sensors, and other devices. Some devices (e.g., parking meters) among these example devices may include machine-type communications (MTC) devices. An MTC device may not need user interaction to initiate communication with the network (e.g., the wireless communication network100).

The Node-B102may operate as a serving Node-B in a geographic area, such as a cell104in the wireless communication network100.FIG. 1shows the wireless communication network100including only one Node-B (e.g., Node-B102) as an example. The wireless communication network100, however, may include multiple Node-Bs (e.g., multiple eNodeBs similar to, or identical to, the Node-B102), or eNodeBs, etc. Each of the multiple Node-Bs may serve a particular cell in the wireless communication network100and may or may not neighbor the Node-B102.

UEs111and112may be served by the Node-B102in cell104(e.g., serving cell104). UEs111and112can select cell104on which to “camp” to obtain services through the Node-B102.FIG. 1shows the wireless communication network100including only two UEs (e.g., UEs111and112) served by the Node-B102in the cell104as an example. The wireless communication network100, however, may include more than two UEs served by the Node-B102. The Node-B102and each of the UEs111and112may operate to communicate with each other using a code division multiple access (CDMA) technique.

The Node-B102can communicate with the UEs111and112on a downlink connection114and the UEs111and112can communicate with the Node-B102on an uplink connection116. The carrier frequency in the uplink116and downlink114is designated by the absolute radio frequency channel numbers (ARFCN). The UEs111and112, and the Node-B102can also each support 3GPP LTE communication. The Node-B102can provide system information block (SIB)19(SIB-19) signals (e.g., “E-UTRA frequency and priority info list” information elements described later herein) that the UE111or112shall use for potential cell reselection to LTE.

3GPP Radio Access Network (RAN) working groups have recently introduced support for extended value ranges of evolved ARFCNs (EARFCNs) and E-UTRA frequency bands for long-term evolution (LTE) networks to support the growing demand for E-UTRA frequency bands. The legacy value range for EARFCNs includes values in the range 0-65535, and the legacy value range for E-UTRA operating bands includes values in the range of 1-64. An extended value range for EARFCNs includes values in the range of 65536 to 262143, and an extended value range for E-UTRA operating bands includes values in the range of 65-256, however embodiments should not be understood as being limited to any particular range for EARFCNs or E-UTRA operating bands.

MFBI signaling allows a Node-B, such as the Node-B102, to broadcast in more than one band if the absolute frequency of the cell104falls into multiple overlapping bands. However, ambiguities and inefficiencies remain in MFBI support in some UMTS systems, at least for extended EARFCN ranges and extended E-UTRA operating band ranges that are signaled in radio resource control (RRC) signaling in SIB-19.

For example, according to current RRC specifications, the tabular description given in 3GPP TS 25.331 §10.3.7.115 of the information element (IE) “E-UTRA frequency and priority info list” references different IEs than the procedural description of that IE specified in 3GPP TS 25.331 §8.6.7.3c. The tabular description specifies that each entry of the IE “Multiple E-UTRA frequency info list” and of the IE “Multiple E-UTRA frequency info extension list,” corresponds to an entry in the “E-UTRA frequency and priority” IE. This relationship is shown graphically inFIG. 2. As can be seen inFIG. 2, according to the tabular description no MFBI signaling, from either the legacy202or the extended204E-UTRA frequency band range C and D, is possible for the extended EARFCN range B. It will be understood thatFIG. 2(as well asFIG. 3, described later herein) depicts only the relevant top level IEs of “E-UTRA frequency and priority,” “E-UTRA frequency and priority extension,” “Multiple E-UTRA frequency info list,” and “Multiple E-UTRA frequency info extension list,” and the value ranges for EARFCNs and E-UTRA frequency bands covered by those IEs, and that other fields, values or portions of those IEs can be specified in current and future versions of standards of the 3GPP family of standards.

On the other hand, the procedural description given in current versions of 3GPP TS 25.331 §8.6.7.c specifies that:

TABLE 13GPP TS 8.6.7.3c (partial)1>for each occurrence of the IE “E-UTRA frequency and priority”: ...2> if the UE supports multi-band signalling and if the UE doesnot recognise the EARFCN in the IE “EARFCN” and the IE“Multiple E-UTRA frequency info list” is present:3> if the IE “Multiple E-UTRA frequency band indicatorlist” is present and the UE supports at least one of the indicatedE-UTRA bands:...1> if the UEsupports E-UTRA band 65 or higher, for each occurrenceof the IE “E-UTRA frequency and priority extension”:...2> if the UE supports multi-band signalling and if the UE doesnot recognise the EARFCN in the IE “EARFCN extension” and theIE “Multiple E-UTRA frequency info extension list” is present:3> if the IE “Multiple E-UTRA frequency band indicatorextension list” is present and the UE supports at least one of theindicated E-UTRA bands:...

The relationship spelled out in Table 1 between EARFCNs and E-UTRA frequency bands with MFBI is shown graphically inFIG. 3. As can be observed upon examination ofFIG. 3, no MFBI signaling302from the extended range of E-UTRA frequency bands D is done for the legacy EARFCN range A. Likewise, no MFBI signaling304from the legacy range C of E-UTRA frequency bands is done for the extended EARFCN range B. Embodiments provide a signaling relationship, described later herein with respect toFIG. 5, wherein MFBI signaling is provided from the extended range D of E-UTRA frequency bands to both the extended EARFCN range B and the legacy EARFCN range A. Similarly, embodiments provide a signaling relationship, wherein MFBI signaling is provided from the legacy range C of E-UTRA frequency bands to both the extended EARFCN range B and the legacy EARFCN range A.

Embodiments also reduce or eliminate the occurrence of superfluous IE signaling.FIG. 4is a block diagram for illustrating superfluous E-UTRA frequency and priority IEs that may be transmitted in some available systems.

The signaling structure in current versions of 3GPP provide that, if an EARFCN value within the EARFCN extended value range is to be signaled to the UE111,112, then the Node-B102will indicate this to the UE111,112by using the legacy maximum value of 65535 in the IE “EARFCN,” as shown in example blocks402,404, and406, along with other IEs, including two mandatory default (MD) IEs and five mandatory present (MP) IEs. The UE111,112will ignore the legacy value in blocks402,404, and406and the UE111,112instead uses corresponding extension EARFCNs and IEs in blocks408,410, and412. However, this approach results in wasted signaling to signal the unused IEs. Embodiments reduce or eliminate this superfluous IE signaling according to signaling optimizations described later herein with respect toFIG. 6.

Embodiments provide a signaling relationship as shown inFIG. 5, wherein MFBI signaling502,504is provided from the extended range D of E-UTRA frequency bands to both the extended EARFCN range B and the legacy EARFCN range A. Similarly, MFBI signaling506,508is provided from the legacy range C of E-UTRA frequency bands to both the extended EARFCN range B and the legacy EARFCN range A. A receiving UE111or112can then merge received signaling according to criteria discussed later herein.

FIG. 6is a block diagram to illustrate E-UTRA frequency and priority information elements that may be transmitted in accordance with some embodiments in order to reduce or eliminate extraneous MFBI signaling as briefly described earlier herein.

In embodiments, the Node-B102will signal an IE “Number of applicable EARFCN.” The UE111or112will then concatenate the IEs “E-UTRA frequency and priority,” illustrated in blocks602and604, and “E-UTRA frequency and priority extension,” illustrated by blocks606,608, and610based on the value signaled in IE “Number of applicable EARFCN.” In other words, the value signaled in IE “Number of applicable EARFCN” refers to the number of occurrences of IE “E-UTRA frequency and priority,” and the value represented by the IE “maxNumEUTRAFreqs” minus the value specified in IE “Number of applicable EARFCN” refers to the maximum number of occurrences of IE “E-UTRA frequency and priority extension.” In the example illustrated inFIG. 6, therefore, it will be understood that “Number of applicable EARFCN” equals 2, so that two “E-UTRA frequency and priority” IEs are used, and the IE “maxNumEUTRAFreqs” is at least five, so that three “E-UTRA frequency and priority extension” IEs can be used.

Additionally, the IE “Multiple E-UTRA frequency info extension list”612will be considered first in some embodiments to provide values for “E-UTRA frequency and priority” and “E-UTRA frequency and priority extension.” Only when a list element in “Multiple E-UTRA frequency info extension list”612is set to absent (e.g., list elements614,616,618, and620) shall a corresponding entry (e.g., list elements622and624) from “Multiple E-UTRA frequency info list”626be merged and used for generating an entry in the concatenated “E-UTRA frequency and priority” and “E-UTRA frequency and priority extension” lists. As will be appreciated upon examination ofFIG. 6, embodiments described herein will eliminate the need to use reserved values of 65535 for EARFCN and 64 for E-UTRA frequency bands in the legacy IEs to refer to the corresponding extension EARFCN and E-UTRA frequency band IEs. While “Multiple E-UTRA frequency info extension list” is shown as having no legacy information, it will be understood that in some embodiments the “Multiple E-UTRA frequency info extension list” can include legacy information. Similarly, the “Multiple E-UTRA frequency info list” can include extension information in addition to, or instead of, legacy information.

FIG. 7shows a block diagram of a UE700in accordance with some embodiments, whileFIG. 8shows a block diagram of a Node-B800in accordance with some embodiments. It should be noted that in some embodiments, the Node-B800may be a stationary non-mobile device. The UE700may be a UE111or112as depicted inFIG. 1, while the Node-B800may be a Node-B102as depicted inFIG. 1.

The UE700will include transceiver circuitry702for transmitting and receiving signals to and from the Node-B800, other Node-Bs or eNodeBs, other UEs or other devices using one or more antennas701, while the Node-B800will include transceiver circuitry802for transmitting and receiving signals to and from the UE700, other Node-Bs or eNodeBs, other UEs or other devices using one or more antennas801. The UE700also includes processing circuitry706and memory708arranged to perform the operations described herein, and the Node-B800also includes processing circuitry806and memory808arranged to perform the operations described herein. The processing circuitry706and806can include PHY, MAC, RRC and/or any other protocol sublayers.

In one embodiment, the UE700receives MFBI signaling, as described earlier herein with respect toFIG. 5, that includes an MFBI list. The MFBI list includes elements that correspond to E-UTRA frequency bands on which the neighboring LTE cells are operated. The MFBI list can include either or both of a “Multiple E-UTRA frequency info extension list” defined in accordance with a standard of the 3GPP family of standards, or a “Multiple E-UTRA frequency info list” defined in accordance with a standard of the 3GPP family of standards. Both lists can be used to signal overlapping E-UTRA frequency bands corresponding to an entry in the “E-UTRA frequency and priority list” IE or the “E-UTRA frequency and priority extension list” IE as described earlier herein with respect toFIG. 5. As described earlier herein, each entry in the “E-UTRA frequency and priority list” and in the “E-UTRA frequency and priority extension list” defines an EARFCN value and a priority value for the respective EARFCN.

Both or either of the “Multiple E-UTRA frequency info extension list” and the “Multiple E-UTRA frequency info list” can be used to signal E-UTRA frequency bands in both the legacy range of 1-64 as well as in any extended range defined in current or future versions of a standard of the 3GPP family of standards or other family of standards. The UE700will then merge the “Multiple E-UTRA frequency info extension list” and the “Multiple E-UTRA frequency info list” as described earlier with reference toFIG. 6to determine which EARFCN values and priority values should be used for corresponding E-UTRA frequency bands. For example, the UE700can select an EARFCN value to be used for the corresponding E-UTRA frequency band from a “Multiple E-UTRA frequency info extension list” element if the “Multiple E-UTRA frequency info extension list” element is not set to a placeholder value indicating that the “Multiple E-UTRA frequency info extension list” element is absent. Otherwise, the UE700can select an EARFCN value to be used for the corresponding E-UTRA frequency band from a “Multiple E-UTRA frequency info list” element. However, embodiments can merge the “Multiple E-UTRA frequency info extension list” and the “Multiple E-UTRA frequency info list” according to any other criteria or algorithm. For example, the UE700can merge the lists by assigning default higher priority to entries in the “Multiple E-UTRA frequency info list,” or the UE700or network100can assign flexible priorities to each E-UTRA frequency band, among other criteria or algorithms.

The number of list elements for E-UTRA frequency and priority information is equal to a sum of the number of entries in an “E-UTRA frequency and priority list” plus the number of entries in an “E-UTRA frequency and priority extension list.” For example, as described earlier herein, the number of list elements for E-UTRA frequency and priority information can be less than or equal to a value in the IE “maxNumEUTRAFreqs.” The number of entries in an “E-UTRA frequency and priority list” is given by the value specified in IE “Number of applicable EARFCN” and the number of entries in the “E-UTRA frequency and priority extension list” can be given by the value in the IE “maxNumEUTRAFreqs,” minus the value specified in IE “Number of applicable EARFCN.”

The Node-B800can transmit MFBI signaling that is included in the above-described “E-UTRA frequency and priority info list”. The antennas701,801may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas701,801may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

Referring toFIG. 9a method900of supporting multi-band signaling in a network is shown. It is important to note that embodiments of the method900may include additional or even fewer operations or processes in comparison to what is illustrated inFIG. 9. In addition, embodiments of the method900are not necessarily limited to the chronological order that is shown inFIG. 9. In describing the method900, reference may be made toFIGS. 1-8, although it is understood that the method900may be practiced with any other suitable systems, interfaces and components.

In addition, while the method900and other methods described herein may refer to Node-Bs102or UEs111and112operating in accordance with 3GPP or other standards, embodiments of those methods are not limited to just those Node-Bs102and UEs111,112and may also be practiced on other mobile devices, such as a Wi-Fi access point (AP) or user station (STA). Moreover, the method900and other methods described herein may be practiced by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various IEEE standards such as IEEE 802.11.

At operation902, the UE111or112will receive signaling that includes an “E-UTRA frequency and priority info list” at least somewhat similar to that described earlier herein with respect toFIG. 1-8. For example, the “E-UTRA frequency and priority info list” can include list elements corresponding to overlapping E-UTRA frequency bands on which neighboring LTE cells are operated. As described earlier herein, a total count of list elements for E-UTRA frequency and priority information is representative of a sum of a number of entries in an “E-UTRA frequency and priority list” IE and a number of entries in an “E-UTRA frequency and priority extension list” IE.

In operation904, the UE111or112will connect to a neighboring LTE cell using information in an element of the MFBI list.

The UE111or112will determine the overlapping E-UTRA frequency bands corresponding to an entry in the “E-UTRA frequency and priority list” or the “E-UTRA frequency and priority extension list” based on a “Multiple E-UTRA frequency info extension list” and a “Multiple E-UTRA frequency info list” according to merging algorithms described earlier herein.

It should be noted that the discussion of the method900and other discussions herein may refer to SIBs, which may be broadcast messages transmitted by the Node-B102that are receivable by UEs operating in a cell. In some embodiments, the SIB may be a SystemInformationBlockType19 message of the 3GPP or other standards, which may also be referred to as “SIB-19” or as a “SIB-19” message. The operations and techniques described herein are not limited to SIB-19 messages, however, and may be applied to other types or embodiments of System Information Blocks of 3GPP or other standards. The operations and techniques described herein are also not limited to SIBs, and similar operations and techniques may also be applied to other messages transmitted by the Node-B102, including paging messages for individual UEs or groups of UEs or other control messages.

A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors to perform operations supporting multi-band signaling in a network is disclosed herein. The operations may configure the one or more processors to receive, in MFBI signaling, an MFBI list that includes list elements corresponding to E-UTRA frequency bands on which the neighboring LTE cells are operated, wherein a count of list elements for E-UTRA frequency and priority information is representative of a sum of a number of entries in an “E-UTRA frequency and priority list” and a number of entries in an “E-UTRA frequency and priority extension list,” wherein each list element of the MFBI list corresponds to an entry in the E-UTRA frequency and priority list or the E-UTRA frequency and priority extension list, and wherein each entry in the E-UTRA frequency and priority list and the E-UTRA frequency and priority extension list defines an EARFCN value and a priority value for the respective EARFCN.

In some embodiments, mobile devices or other devices described herein may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly. In some embodiments, the mobile device or other device can be a User Equipment (UE) or an Evolved Node-B (eNB) configured to operate in accordance with 3GPP standards. In some embodiments, the mobile device or other device may be configured to operate according to other protocols or standards, including IEEE 802.11 or other IEEE standards. In some embodiments, the mobile device or other device may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.