WO2010076376A1

WO2010076376A1 - Techniques to report supported frequency bands for wireless networks

Info

Publication number: WO2010076376A1
Application number: PCT/FI2009/050972
Authority: WO
Inventors: Seppo Alanärä; Henri Koskinen
Original assignee: Nokia Corporation
Priority date: 2008-12-30
Filing date: 2009-12-02
Publication date: 2010-07-08

Abstract

According to one general aspect, an apparatus may include a processor (204). In various embodiments, the processor (204) may be configured to transmit a message to a base station, the message including frequency band support information that indicates support for one or more frequency bands, the message including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type. According to another aspect, the processor (204) may be configured to transmit a message to a base station, the message including a band list that indicates support for one or more frequency bands, wherein the band list includes, for each band in the band list: a first bit for each band in the band list, the band list including only the first bit for a band if the first bit for the band is in a first state indicating no support for the band, and the band list further including a duplex bit if the first bit for the band is in a second state indicating support for the band, the duplex bit indicating either half duplex operation or full duplex operation for the supported band.

Description

TECHNIQUES TO REPORT SUPPORTED FREQUENCY BANDS FOR WIRELESS

NETWORKS

TECHNICAL FIELD

[0001] This description relates to wireless communications, and more specifically to techniques to report supported frequency bands for wireless networks.

BACKGROUND

[0002] Long Term Evolution (LTE) describes the latest standardization work by 3rd

Generation Partnership Project (3GPP) in the area of mobile network technology. In preparation for further increasing user demands and tougher competition from new radio access technologies, LTE is generally being enhanced with a new radio access technique called LTE-Advanced. Via this technology LTE is expected to improve end-user throughput, increase sector capacity, reduce user plane latency, and consequently offer superior user experience with full mobility.

[0003] The Evolved UMTS Terrestrial Radio Access (E-UTRA) standard typically includes the air interface of 3GPP's LTE for mobile networks. An E-UTRA network or, as it is occasionally referred to, a LTE network, includes a network that is substantially in compliance with the LTE standards, their derivatives, or predecessors (hereafter, "the LTE standard" or "Release 8 standard"). There are a number of specifications included as part of the LTE standard or Release 8 standard. One LTE specification is the 3rd Generation Partnership Project, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification, 3GPP TS 36.331 version 8.4.0 Release 8, December 2008 ("TS 36.331 ").

[0004] TS 36.331 specifies a UE-EUTRA capability information element that allows a user equipment (UE) or mobile station (MS) to signal or identify the UE 's capabilities to an enhanced Node B (eNB) or base station (BS). The UE-EUTRA capability information element (IE) includes a SupportedEUTRA-BandList, which is a RF-parameter signaled by the UE, indicating a band list of one or more radio frequency bands supported by the UE or MS and identifying duplex information for each supported band. For each of one or more supported frequency bands (up to a maximum number of bands or maxBands), two parameters are provided including: a eutra-Band parameter of type integer (between 1 and 64) identifying the band number as defined in TS 36.101 , and a halfduplex parameter of type Boolean. If halfduplex is set to true (e.g., "1"), only half duplex operation (where the UE may transmit or receive via the band, but not at the same time) is supported by the UE or MS for the band, otherwise (e.g., if halfduplex is false or "0") full duplex operation (where the UE may transmit via one band and receive via a second band associated with the band number at the same time) is supported by the UE or MS for the band. RF-Parameters ::= SEQUENCE { supportedEUTRA-BandList SupportedEUTRA-BandList

}

SupportedEUTRA-BandList : := SEQUENCE (SIZE (1..maxBands)) OF SEQUENCE { eutra-Band INTEGER (1..64), halfDuplex BOOLEAN

SUMMARY

[0005] According to an example embodiment, an apparatus may include a processor. The processor may be configured to receive a request for capability information from a base station; and transmit a response message (e.g., a user equipment or mobile station capability information message) to the base station, the response message including at least frequency band support information that indicates support for one or more frequency bands, the message including a band list type field identifying a format, out of a plurality of formats, for the frequency band support information.

[0006] According to another example embodiment, a method may include receiving a request for capability information from a base station; and, transmitting a response message (e.g., UE or MS capability information message) to the base station, the response message including at least frequency band support information that indicates support for one or more frequency bands, the message including a band list type field identifying a format, out of a plurality of formats, for the frequency band support information.

[0007] According to an example embodiment, an apparatus may include a processor. The processor may be configured to transmit a message (e.g., UE or MS capability information message) to a base station, the message including frequency band support information that indicates support for one or more frequency bands, the message including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type.

[0008] According to another example embodiment, a method may include transmitting a message (e.g., a UE or MS capability information message), from a user equipment or mobile station to a base station in a wireless network, the message including frequency band support information that indicates support for one or more frequency bands, the message including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type.

[0009] According to an example embodiment, an apparatus may include a processor. The processor may be configured to transmit a message (e.g., a UE or MS capability information message) to a base station, the message including a band list that indicates support for one or more frequency bands, wherein the band list includes, for each band in the band list: a choice bit for each band in the band list, the band list including only the choice bit for a band if the choice bit for the band is a first state indicating no support for the band, and the band list further including a duplex bit if the choice bit for the band is a second state indicating support for the band, the duplex bit indicating either half duplex operation or full duplex operation for the supported band.

[0010] According to an example embodiment, an apparatus may include a processor. The processor may be configured to transmit a message (e.g., UE or MS capability information message) to a base station, the message including a band list that indicates support for one or more frequency bands, wherein the band list includes, for each band in the band list: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either half duplex operation or full duplex operation for the supported band.

[0011 ] According to an example embodiment, a method may include transmitting a message

(e.g., a UE or MS capability information message) from a user equipment or mobile station to a base station in a wireless network, the message including a band list that indicates support for one or more frequency bands, wherein the band list includes, for each band in the band list: a choice bit (or first bit) having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0012] According to an example embodiment, an apparatus may include a processor. The processor may be configured to transmit a message to a base station, the message (e.g., UE or MS capability information message) including a FDD band list that indicates support for one or more frequency division duplex frequency bands, wherein the FDD band list includes, for each supported band in the band list: a half duplex only field of type Boolean that is selected and present only when there is support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported FDD band.

[0013] According to an example embodiment, a method may include transmitting a message

(e.g., UE or MS capability information message) from a user equipment or mobile station to a base station, the message including a FDD band list that indicates support for one or more frequency division duplex frequency bands, wherein the FDD band list includes, for each supported band in the band list: a half duplex only field of type Boolean that is selected and present only when there is support for the band, the half duplex only field indicating either half duplex operation or full duplex operation for the supported FDD band.

[0014] According to an example embodiment, an apparatus may include a processor. The processor may be configured to transmit a message (e.g., UE or MS capability information message) to a base station, the message including a TDD band list that indicates support for one or more time division duplex frequency bands, wherein the TDD band list includes a band supported field of type Boolean for each of a plurality of TDD bands, each band supported field indicating support or not for the TDD band, each supported TDD band being half duplex only operation.

[0015] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG. 1 is a block diagram of an example embodiment of a system in accordance with the disclosed subject matter.

[0017] FIG. 2 is a block diagram of an example embodiment of a system or apparatus 201 according to an example embodiment.

[0018] FIG. 3 illustrates a format of a band list according to an example embodiment.

[0019] FIG. 4 is a diagram illustrating a flexible format for reporting frequency band support information according to an example embodiment.

[0020] FIG. 5 is a flow chart illustrating operation of a mobile station or user equipment according to an example embodiment.

[0021] FIG. 6 is a flow chart illustrating operation of a mobile station or user equipment according to another example embodiment.

[0022] FIG. 7 is a flow chart illustrating operation of a mobile station or user equipment according to another example embodiment.

[0023] FIG. 8 is a flow chart illustrating operation of a mobile station or user equipment according to another example embodiment.

DETAILED DESCRIPTION

[0024] Referring to the Figures in which like numerals indicate like elements, FIG. 1 is a block diagram of a wireless network 102 including an evolved Node B (eNB) or base station (BS) 104 and user equipment(s) (UE) or mobile stations (MSs) 106, 108, 110, according to an example embodiment. Each of the MSs 106, 108, 110 may be associated with BS 104, and may transmit data in an uplink (UL) direction to BS 104, and may receive data in a downlink (DL) direction from BS 104, for example. Although only one BS 104 and three mobile stations (MSs 106, 108 and 110) are shown, any number of base stations and mobile stations may be provided in network 102. Also, although not shown, mobile stations 106, 108 and 110 may be coupled to base station 104 via relay stations or relay nodes, for example. The base station 104 may be connected via wired or wireless links to another network (not shown), such as a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, etc. In various embodiments, the base station 104 may be coupled or connected with the other network 120 via an access network controller (ASN) or gateway (GW) 112 that may control, monitor, or limit access to the other network. [0025] The wireless network 102 may include, for example, a EUTRA or LTE network, an

IEEE 802.16 Wireless Metropolitan Area Network (WiMAX), an IEEE 802.11 Wireless Local Area Network (WLAN), a cellular telephone network, or any other wireless network, according to example embodiments. The base station 104 may include an eNB, a cellular or WiMAX base station (BS), an 802.11 access point, or other infrastructure node, according to various example embodiments. The mobile stations 106, 108, 110 may include any wireless device or user equipment (UE), such as, for example, laptop or notebook computers, smartphones, personal digital assistants (PDAs), cellular telephones, WiMAX device, subscriber station, LTE/3GPP UE, or any other wireless device, according to example embodiments. While the present disclosure may use some of the terminology of 3GPP/LTE or other wireless standards or specifications in one or more examples or illustrations, the techniques and aspects of the present disclosure may be applicable to any networking or wireless technologies.

[0026] FIG. 2 is a block diagram of an example embodiment of a system or apparatus 201 according to an example embodiment. The apparatus or wireless station 201 (e.g., base station 104, mobile station 106, relay station, etc.) may include, for example, an RF (radio frequency) or wireless transceiver 202, including a transmitter to transmit signals and a receiver to receive signals, a processor 204 to execute instructions or software and control transmission and receptions of signals, and a memory 206 to store data and/or instructions.

[0027] Processor 204 may also make decisions or determinations, generate frames or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 204, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 202. Thus, processor 204 may transmit and/or receive messages or data via wireless transceiver 202. Processor 204 may control transmission of signals or messages over a wireless network, and may receive signals or messages, etc., via a wireless network (e.g., after being down- converted by wireless transceiver 202, for example). Processor 204 may be programmable and capable of executing software, firmware, or other instructions stored in memory or on other computer media to perform the various tasks and functions or methods described herein. Processor 204 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 204 and transceiver 202 together may be considered as a wireless transmitter/receiver system, for example.

[0028] In addition, a controller (or processor) 208 may execute software and instructions, and may provide overall control for the station 201, and may provide control for other systems not shown in FIG. 2, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 201 , such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.

[0029] In addition, a storage medium, such as memory 206, may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 204, or other controller or processor, performing one or more of the functions or tasks described herein.

[0030] According to an example embodiment, a MS (or UE) may receive a capability request message, where the BS (or eNB) is requesting the capabilities of the MS. In response to the capabilities request message (or on its own initiative), the MS may send a message to the BS to indicate one or more capabilities of the MS. For example, this capability information may be provided to the BS as part of the registration process, or at other times. The MS may indicate a number of different types of capabilities to the BS.

[0031 ] One capability that may be indicated to the BS may be frequency band support information for the MS, which may include, for example, an indication of which of one or more frequency bands are supported by the MS, and for each supported band, whether the operation of such band is half duplex only or full duplex for the MS. This information may be used, for example, to allow a BS to assign frequency bands for the MSs in the network or cell.

[0032] One example format is described above for a band list, which may provide frequency band support information for a MS to a BS. The format of the band list described above includes two parameters for each of one or more frequency bands, including a 6-bit Band parameter to identify a band number, and a 1 -bit duplex bit to identify whether the band is for half duplex operation only or full duplex operation. Such a format may work well for reporting support of a few (or a relative small number) of frequency bands. However, if a relatively large number of frequency bands are supported by a MS, then this band list format may provide significant overhead, because 7 bits are provided for each supported band (1 bit duplex information, 6 bits for band number).

[0033] FIG. 3 illustrates a format of a band list according to an example embodiment. The band list format 310 in FIG. 3 has a format that may be referred to as Type 1 , or BandListType 1. According to an example embodiment, the band list 310 (format illustrated in FIG. 3) may include information for each of a number maxBands of bands, where maxBands may be a fixed number, e.g., 32, or 64 or other number. According to an example embodiment, as shown in FIG. 3, the band list may include: a choice bit 312 for each band in the band list (a total of maxBands in the band list). For example, the choice bit 312 for a band may be a first state (e.g., 0) if the MS does not support the band (no support for the band), and may be a second state (e.g., 1) if the band is supported by the MS.

[0034] In an example embodiment, the word "Choice" in the band list format in FIG. 3 may indicate that a choice is made from the next two parameters (only one of the next two parameters are selected or present in the message or information element), based on the value of the choice bit (or choice field). As shown in FIG. 3, after the choice bit 312, the next two parameters for a band are a eutra-BandNotSupported field 320 of type null, and a halfDuplexOnly field 330 of type Boolean (e.g., either a 0 or 1). Thus, for example, if the choice bit is a first state or 0 (indicating no support for the band), then the eutra-BandNotSupported field 320 (of type null) is selected. Since this field 320 is of type null, this means that nothing or no bit is provided here. If the choice bit is a second state, e.g., 1, then the halfDuplexOnly field 330, of type Boolean, is selected. The halfDuplexfield 330 may be a first state or a 1 , for example, to indicate half duplex only operation for this band, and may be a second state or a 0, for example, to indicate full duplex operation for this band. Therefore, only a choice bit is provided for a band that is not supported (since the null-type information element BandNotSupported is selected in such case), and two bits (the choice bit and the duplex bit or, e.g., halfDuplexOnly field or bit 330) are provided for bands that are supported. This format of the band list 310 illustrated in FIG. 3 may provide a relatively efficient format to communicate frequency band support information to the BS.

[0035] Therefore, according to an example embodiment shown in FIG. 3, the band list 310 may include only the choice bit for a band if the choice bit for the band is a first state indicating no support for the band. The band list 310 may further include (in addition to the choice bit) a duplex bit 330 if the choice bit for the band is a second state indicating support for the band. The duplex bit 330 may indicate either only half duplex operation or full duplex operation for the supported band.

[0036] Referring to the format of the band list in FIG. 3, according to an example embodiment, the band list 310 may include, for each band in the band list: a choice bit 312 having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field 320 of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field 330 of type Boolean that is selected and present when the choice bit is the second state indicating support for the band.

[0037] FIG. 4 is a diagram illustrating a flexible format for a band list or for reporting frequency band support information according to an example embodiment. Referring to the band list 410 shown in FIG. 4, a high level (or bandListType) choice bit 411 is provided. If the bandListType choice bit 411 is a first state (e.g., 0), then a first branch 414 of the band list 410 is selected, which includes using a band list of Type 1 or BandListType 1. On the other hand, if the bandListType choice bit 411 is a second state (e.g., 1), then a second branch 416 is selected to a partial bands list which may allow a MS to report frequency band support using one or more optional band lists. This flexible format shown in FIG. 4 for reporting frequency band support will now be described in greater detail.

[0038] If the bandListType choice bit 411 is a first state (or, e.g., 0), the first branch 414 is selected. The first branch 414 indicates that a band list 310 of type 1 or BandListType 1 is used. The band list of type 1 may use an efficient choice/null/Boolean format, as described in detail with respect to FIG. 3. The band list 310 of type 1 (via selectable branch 1 in FIG. 4) may allow a MS to efficiently report frequency band support information for a relatively large number of frequency bands, for example.

[0039] If the bandListType choice bit 411 is a second state (or, e.g., 1), the second branch

416 is selected to allow the MS to report frequency band support information using one or more optional band lists. A selection field, e.g., which may, for example, include three additional optionality-bits or fields (418, 420 and 422) to indicate which of the optional band list types (419, 421 and 423) are being used via branch 2 to report frequency band support information.

[0040] As shown in the example of FIG. 4, a first optionality-bit or field 418, shown as the attribute OPTIONAL of the information element of type SupportedEUTRA-BANDListType2 418 is set to a first state (e.g., 1) if frequency band support information is being reported for one or more bands using BandListType 2 440 (and is set to a second state, e.g., 0 to indicate that this band list type is not being used). This Type 2 or BandListType2 format 440 may be the same format as described above in the background. As shown in FIG. 4, for the BandListType2 format 440, for each of one or more supported frequency bands (up to a maximum number of bands or maxBands), two parameters are provided including: a eutra-Band parameter or field 442 of type integer (between 1 and 64) identifying the band number, and a halfduplex parameter or field 444 of type Boolean (shown as halfDuplexOnly 444). If halfDuplexOnly field 444 is set to true (e.g., "1"), this indicates to the BS that only half duplex operation is supported by the UE or MS for the band, otherwise (e.g., if halfduplex is false or "0") full duplex operation is supported by the UE or MS for the band.

[0041 ] Referring to FIG. 4, and continuing along the second branch 416, a second optionality-bit or field 420, shown as the attribute OPTIONAL of the information element of type SupportedEUTRA-FDDBandListRel8 421, is set to a first state (or 1), if frequency band support information is being reported for one or more frequency division duplex (FDD) frequency bands using the SupportedEUTRA-FDDBandListRel8 format (or FDD band list) 450. In one example embodiment, the FDD band list 450 may include an entry for each of the FDD bands; or, in another example embodiment, the FDD band list 450 may include an entry for each of the bands in the Release 8 of one or more LTE or 3GPP or EUTRA specifications. There may be maxEUTRAFDDBands (e.g., 15 FDD bands) included in the FDD band list 450.

[0042] The FDD band list 450 in FIG. 4 may use the same choice/null/Boolean format as the band list illustrated in FIG. 3, for example. Thus, the FDD band list 450 may include a choice bit 452, a bandNotSupported field 454 of type null that is selected when choice bit 452 is a first state indicating no support for the band. FDD band list 450 may also include a halfDuplexOnly field 456 that is selected and provided when the choice bit 452 is a second state indicating support for the band.

[0043] Referring to FIG. 4, and continuing along the second branch 416, a third optionality- bit or field 422, shown as the attribute OPTIONAL of the information element of type SupportedEUTRA-TDDBandListRel8 423, is set to a first state (or 1), if frequency band support information is being reported for one or more time division duplex (TDD) frequency bands using the SupportedEUTRA-TDDBandListRel8 format (or TDD band list) 460. The TDD band list 460 may include a band supported field (shown as eutraBandSupported) of type Boolean, indicating whether or not the TDD band is supported (e.g., 1 to indicated that the band is supported and a 0 to indicate no support for the band). According to an example embodiment, all TDD bands may operate in half duplex only operation. Thus, there is no need to include a duplex bit for each of the TDD bands, according to an example embodiment. Thus, there may a overhead or signaling savings by separately reporting capability of the FDD bands in the FDD band list 450 (which may be either half duplex only or full duplex operation) and reporting the TDD bands in the TDD band list 460, since duplex bits may be omitted from the TDD band list 460. In such an example embodiment, duplex information for TDD bands is redundant, and thus, may be omitted.

[0044] In one example embodiment, the TDD band list 460 may include an entry for each of the TDD bands; or, in another example embodiment, the TDD band list 460 may include an entry for each of the bands in the Release 8 of one or more LTE or 3GPP or EUTRA specifications. There may be maxEUTRATDDBands (e.g., 8 TDD bands) included in the TDD band list 460. For example, non-release 8 TDD and FDD bands may be reported in the type 2 band list 440, for branch 2, according to one example embodiment. In another embodiment, the capability of all FDD and TDD bands may be reported via FDD band list 450 and TDD band list 460, for example. Also, for branch 2 416, the optional band lists 440, 450 and 460 may be included in various combinations, either alone or in combination, according to example embodiments. For example, the type 2 band list 440 may be omitted, leaving only the FDD and TDD band lists in branch 2. Or, in another embodiment, only the type 2 band list 440 may be provided in branch 2. Or, all three band lists 440, 450 and 460 may be provided as optional band lists in branch 2 for reporting frequency band support information, as shown in FIG. 4, for example.

[0045] The signaling cost of this scheme or band list structure illustrated in FIG. 4 may be variable, but can be broken down as follows:

• Using branch 1 : (65 -bit fixed cost) + (1 bit per supported band)

• Using branch 2: (4-bit fixed cost) + (if Re 1-8 FDD bands signaled: 15 bits + 1 bit per supported band)

+ (if Rel-8 TDD bands signaled: 8 bits) + (if other bands signaled: 6 bits + 7 bits per supported band)

Signaling-cost comparison in example cases

[0046] According to an example embodiment, an apparatus may include a processor. The processor may be configured to: receive a request for capability information from a base station; and transmit a response message to the base station, the response message including at least frequency band support information that indicates support for one or more frequency bands, the message including a band list type field identifying a format, out of a plurality of formats, for the frequency band support information.

[0047] In an example embodiment, the band list type field may indicate the presence in the message of one or more band lists that indicate support for one more frequency bands. The band list type field may indicate the presence of either a band list of a first type if the band list field is a first state, or the presence of a group of one or more optional band lists if the band list type field is a second state.

[0048] FIG. 5 is a flow chart illustrating operation of a mobile station or user equipment according to an example embodiment. Operation 510 may include receiving receive a request for capability information from a base station. Operation 520 may include transmitting a response message to the base station, the response message including at least frequency band support information that indicates support for one or more frequency bands, the message including a band list type field identifying a format, out of a plurality of formats, for the frequency band support information.

[0049] In an example embodiment of the flow chart of FIG. 5, the band list type field may indicate the presence in the message of one or more band lists that indicate support for one more frequency bands.

[0050] In an example embodiment of the flow chart of FIG. 5, the band list type field may indicate the presence of either a band list of a first type if the band list field is a first state, or the presence of a group of one or more optional band lists if the band list type field is a second state.

[0051] According to an example embodiment, an apparatus may include a processor. The processor may be configured to: transmit a message to a base station, the message including frequency band support information that indicates support for one or more frequency bands, the message including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type.

[0052] In an example embodiment, the frequency band support information may identify support, by a user equipment or mobile station, for one or more radio frequency bands, and indicates whether each of the supported bands is supported only for half duplex operation or supported for full duplex operation.

[0053] In an example embodiment, the band list of a first type may include a choice bit for each band in the band list of the first type, the band list of the first type including only the choice bit for a band if the choice bit for the band is a first state indicating no support for the band, and the band list of the first type further including a duplex bit for a band if the choice bit is a second state indicating support for the band, the duplex bit indicating either only half duplex operation or full duplex operation for the supported band.

[0054] In an example embodiment, the band list of a first type may include a band list including, for each band in the band list of the first type: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0055] In an example embodiment, the band list of a first type may include the following format:

[0056] SupportedEUTRA-BandListTypel : := SEQUENCE (SIZE (maxBands)) OF

CHOICE { eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

} [0057] In an example embodiment, the at least the band list of the second type may include one or more optional band lists, including one or more of the following band lists: a band list of a second type having, for each of one or more supported frequency bands: a Band field of type integer identifying the band number, and a half duplex only field of type Boolean and indicating either only half duplex operation or full duplex operation for the supported band; a FDD band list for frequency division duplex frequency bands, the FDD band list including, for each of a plurality of supported FDD bands, a half duplex only field of type Boolean that is selected and present when there is support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported FDD band; and a TDD band list for time division duplex frequency bands, the TDD band list including a band supported field of type Boolean for each of a plurality of TDD bands, each band supported field indicating support or not for the TDD band, each supported TDD band being half duplex only operation.

[0058] In an example embodiment, the band list of the second type may include a bandslist field indicating the presence of one or more of: the band list of the second type, the FDD band list and/or the TDD band list.

[0059] In an example embodiment, the FDD band list may include, for each band in the

FDD band list: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0060] In an example embodiment, the FDD band list may include the following format:

[0061 ] SupportedEUTRA-FDDBandListRel8 : :=SEQUENCE (SIZE (maxEutraFDDBands))

OF CHOICE { eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

} [0062] In an example embodiment, the TDD band list may include the following format:

[0063] SupportedEUTRA-TDDBandListRel8 ::=SEQUENCE (SIZE (maxEutraTDDBands))

OF SEQUENCE { eutraBandSupported BOOLEAN

}

[0064] The apparatus may further include

[0065] a memory; and a wireless transceiver, the processor configured to transmit via the wireless transceiver. The processor may include a baseband processor.

[0066] FIG. 6 is a flow chart illustrating operation of a mobile station or user equipment according to another example embodiment. Operation 610 may include transmitting a message, from a user equipment or mobile station to a base station in a wireless network, the message including frequency band support information that indicates support for one or more frequency bands, the message including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type.

[0067] In an example embodiment of the flow chart of FIG. 6, the frequency band support information may identify support, by a user equipment or mobile station, for one or more radio frequency bands, and indicates whether each of the supported bands is supported only for half duplex operation or supported for full duplex operation.

[0068] In an example embodiment of the flow chart of FIG. 6, the band list of a first type may include a choice bit for each band in the band list of the first type, the band list of the first type including only the choice bit for a band if the choice bit for the band is a first state indicating no support for the band, and the band list of the first type further including a duplex bit for a band if the choice bit is a second state indicating support for the band, the duplex bit indicating either only half duplex operation or full duplex operation for the supported band.

[0069] In an example embodiment of the flow chart of FIG. 6, the band list of a first type may include a band list including, for each band in the band list of the first type: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0070] In an example embodiment of the flow chart of FIG. 6, the band list of a first type includes the following format:

[0071] SupportedEUTRA-BandListTypel ::=SEQUENCE (SIZE (maxBands)) OF CHOICE

{ eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

}

[0072] In an example embodiment of the flow chart of FIG. 6, the at least the band list of the second type may include one or more optional band lists, including one or more of the following band lists: a band list of a second type having, for each of one or more supported frequency bands: a Band field of type integer identifying the band number, and a half duplex only field of type Boolean and indicating either only half duplex operation or full duplex operation for the supported band; a FDD band list for frequency division duplex frequency bands, the FDD band list including, for each of a plurality of supported FDD bands, a half duplex only field of type Boolean that is selected and present when there is support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported FDD band; and a TDD band list for time division duplex frequency bands, the TDD band list including a band supported field of type Boolean for each of a plurality of TDD bands, each band supported field indicating support or not for the TDD band, each supported TDD band being half duplex only operation.

[0073] In an example embodiment of the flow chart of FIG. 6, the band list of the second type includes a bandslist field indicating the presence of one or more of the band list of the second type, the FDD band list and/or the TDD band list.

[0074] In an example embodiment of the flow chart of FIG. 6, the FDD band list may include, for each band in the FDD band list: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0075] In an example embodiment of the flow chart of FIG. 6, the FDD band list includes the following format:

[0076] SupportedEUTRA-FDDBandListRel8 : :=SEQUENCE (SIZE (maxEutraFDDBands))

OF CHOICE { eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

} [0077] In an example embodiment of the flow chart of FIG. 6, the TDD band list may includes the following format:

[0078] SupportedEUTRA-TDDBandListRel8 ::=SEQUENCE (SIZE (maxEutraTDDBands))

OF SEQUENCE { eutraBandSupported BOOLEAN

}

[0079] According to another example embodiment, an apparatus may include a processor.

The processor may be configured to transmit a message to a base station, the message including a band list that indicates support for one or more frequency bands, wherein the band list includes, for each band in the band list: a choice bit for each band in the band list, the band list including only the choice bit for a band if the choice bit for the band is a first state indicating no support for the band, and the band list further including a duplex bit if the choice bit for the band is a second state indicating support for the band, the duplex bit indicating either only half duplex operation or full duplex operation for the supported band.

[0080] According to another example embodiment, an apparatus may include a processor.

The processor may be configured to transmit a message to a base station, the message including a band list that indicates support for one or more frequency bands, wherein the band list includes, for each band in the band list: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0081] In an example embodiment, the band list may include the following format: [0082] SupportedEUTRA-BandListTypel ::=SEQUENCE (SIZE (maxBands)) OF CHOICE

{ eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN.

}

[0083] FIG. 7 is a flow chart illustrating operation of a mobile station or user equipment according to an example embodiment. Operation 710 may include transmitting a message from a user equipment or mobile station to a base station in a wireless network, the message including a band list that indicates support for one or more frequency bands, wherein the band list includes, for each band in the band list: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0084] In an example embodiment of the flow chart of FIG. 7, the band list may include the following format:

[0085] SupportedEUTRA-BandListTypel ::=SEQUENCE (SIZE (maxBands)) OF CHOICE

{ eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN.

}

[0086] According to another example embodiment, an apparatus may include a processor.

The processor may be configured to transmit a message to a base station, the message including a FDD band list that indicates support for one or more frequency division duplex frequency bands, wherein the FDD band list includes, for each supported band in the band list: a half duplex only field of type Boolean that is selected and present only when there is support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported FDD band.

[0087] In an example embodiment, the FDD band list may include, for each band in the

[0088] In an example embodiment, the FDD band list may includes the following format:

[0089] SupportedEUTRA-FDDBandListRel8 ::=SEQUENCE (SIZE (maxEutraFDDBands))

OF CHOICE { eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

}

[0090] In an example embodiment, the message may further include a TDD band list that indicates support for one or more time division duplex frequency bands, wherein the TDD band list that includes a band supported field of type Boolean for each of a plurality of TDD bands, each band supported field indicating support or not for the TDD band, each supported TDD band being half duplex only operation.

[0091] FIG. 8 is a flow chart illustrating operation of a mobile station or user equipment according to an example embodiment. Operation 810 may include transmitting a message from a user equipment or mobile station to a base station, the message including a FDD band list that indicates support for one or more frequency division duplex frequency bands, wherein the FDD band list includes, for each supported band in the band list: a half duplex only field of type Boolean that is selected and present only when there is support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported FDD band.

[0092] In the flow chart of FIG. 8, the FDD band list may include, for each band in the FDD band list: a choice bit having a first state indicating no support for the band and a second state indicating support for the band; a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either only half duplex operation or full duplex operation for the supported band.

[0093] In the flow chart of FIG. 8, the FDD band list may include the following format: [0094] SupportedEUTRA-FDDBandListRel8 ::=SEQUENCE (SIZE (maxEutraFDDBands))

OF CHOICE { eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

}

[0095] In an example embodiment of the flow chart of FIG. 8, the message may further include a TDD band list that indicates support for one or more time division duplex frequency bands, wherein the TDD band list that includes a band supported field of type Boolean for each of a plurality of TDD bands, each band supported field indicating support or not for the TDD band, each supported TDD band being half duplex only operation.

[0096] According to an example embodiment, an apparatus may include a processor. The processor may be configured to transmit a message to a base station, the message including a TDD band list that indicates support for one or more time division duplex frequency bands, wherein the TDD band list includes a band supported field of type Boolean for each of a plurality of TDD bands, each band supported field indicating support or not for the TDD band, each supported TDD band being half duplex only operation.

[0097] In an example embodiment, the TDD band list may include the following format:

[0098] SupportedEUTRA-TDDBandListRel8 ::=SEQUENCE (SIZE (maxEutraTDDBands))

OF SEQUENCE { eutraBandSupported BOOLEAN

}

[0099] In an alternative embodiment, in addition to providing frequency band support information for 3GPP/LTE bands, the UE capability information message may also include frequency band support information for frequency bands associated with one or more additional standards or specifications, such as frequency band support information for GSM (Global System for Mobile Communications). Thus, for example, frequency band support information may be provided within the UE capability information for a first wireless specification (e.g., LTE/3GPP/EUTRA), and for a second wireless specification (e.g., GSM), since many UEs or MSs are capable of communicating on multiple frequency bands. The same information element formats (or same band list types) illustrated and described herein for LTE/3GPP/EUTRA (as an example), may be used to signal or report frequency band support information to a BS for GSM or other second wireless specification (or radio access specification).

[00100] Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[00101 ] Method steps may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[00102] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto- optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto -optical disks; and CD-ROM and DVD- ROM disks. The processor and the memory may be supplemented by, or incorporated in special purpose logic circuitry. [00103] While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the scope of the embodiments.

Claims

WHAT IS CLAIMED IS:

1. An apparatus comprising: a processor; and wherein the processor is configured to: transmit a message to a base station, the message including frequency band support information that indicates support for one or more frequency bands, the message further including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type.

2. The apparatus of claim 1 , wherein the frequency band support information identifies support, by a user equipment for one or more radio frequency bands, and indicates whether each of the supported bands is supported for half duplex operation or supported for full duplex operation.

3. The apparatus of claim 1, wherein the band list of a first type includes a choice bit for each band in the band list of the first type, the band list of the first type including only the choice bit for a band if the choice bit for the band is a first state indicating no support for the band, and the band list of the first type further including a duplex bit for a band if the choice bit is a second state indicating support for the band, the duplex bit indicating either half duplex operation or full duplex operation for the supported band.

4. The apparatus of claim 3, wherein the band list of the first type includes a band list including, for each band in the band list of the first type: a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either half duplex operation or full duplex operation for the supported band.

5. The apparatus of claim 3, wherein the band list of the first type includes the following format: SupportedEUTRA-BandListTypel ::= SEQUENCE (SIZE (maxBands)) OF CHOICE { eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

}

6. The apparatus of claim 1 , wherein the band list of a second type includes one or more optional band lists, including one or more of the following band lists: a band list of a second type having, for each of one or more supported frequency bands: a Band field of type integer identifying the band number, and a half duplex only field of type Boolean indicating either half duplex operation or full duplex operation for the supported band; a frequency division duplex (FDD) band list for frequency division duplex frequency bands, the FDD band list including, for each of a plurality of supported FDD bands, a half duplex only field of type Boolean that is selected and present when there is support for the band, the half duplex only field of type Boolean indicating either half duplex operation or full duplex operation for the supported FDD band; and a time division duplex (TDD) band list for time division duplex frequency bands, the TDD band list including a band supported field of type Boolean for each of a plurality of TDD bands, each band supported field indicating support or not for the TDD band, each supported TDD band being half duplex only operation.

7. The apparatus of claim 6, wherein the band list of the second type includes a bandslist field indicating the presence of one or more of the band list of the second type, the FDD band list and/or the TDD band list.

8. The apparatus of claim 6, wherein the FDD band list comprises, for each band in the FDD band list: a band not supported field of type null that is selected when the choice bit is a first state indicating no support for the band; and a half duplex only field of type Boolean that is selected and present when the choice bit is the second state indicating support for the band, the half duplex only field indicating either half duplex operation or full duplex operation for the supported band.

9. The apparatus of claim 6, wherein the FDD band list includes the following format: SupportedEUTRA-FDDBandListRel8 : := SEQUENCE (SIZE (maxEutraFDDBands)) OF CHOICE { eutra-BandNotSupported NULL, halfDuplexOnly BOOLEAN

}

10. The apparatus of claim 6, wherein the TDD band list includes the following format: SupportedEUTRA-TDDBandListRel8 ::= SEQUENCE (SIZE (maxEutraTDDBands)) OF SEQUENCE { eutraBandSupported BOOLEAN

}

11. The apparatus of claim 1 , wherein the processor comprises a baseband processor.

12. A method comprising: transmitting a message, from a user equipment to a base station in a wireless network, the message including frequency band support information that indicates support for one or more frequency bands, the message further including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type.

13. The method of claim 12, wherein the frequency band support information identifies support, by a user equipment for one or more radio frequency bands, and indicates whether each of the supported bands is supported for half duplex operation or supported for full duplex operation.

14. The method of claim 12, wherein the band list of a first type includes a choice bit for each band in the band list of the first type, the band list of the first type including only the choice bit for a band if the choice bit for the band is a first state indicating no support for the band, and the band list of the first type further including a duplex bit for a band if the choice bit is a second state indicating support for the band, the duplex bit indicating either half duplex operation or full duplex operation for the supported band.

15. A computer program, comprising: code for transmitting a message, from a user equipment to a base station in a wireless network, the message including frequency band support information that indicates support for one or more frequency bands, the message further including a band list type field indicating that the frequency band support information is provided either as at least a band list of a first type or as at least a band list of a second type, when the computer program is run on a processor.

16. The computer program according to claim 15 , wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer.