HK1206160B - Method, system and apparatus of time-division-duplex (tdd) uplink-downlink (ul-dl) configuration management - Google Patents

Description

Method, system and apparatus for Time Division Duplex (TDD) uplink-downlink (UL-DL) configuration management

Background

Traffic carried in a communication network (e.g., a cellular network) may typically be asymmetric in the time domain or small area. For example, the amount of Downlink (DL) and Uplink (UL) traffic may be significantly different and may vary in time and/or across different cells. Such traffic variations can be handled efficiently by adapting the amount of time resources allocated to DL and UL, e.g., using different Time Division Duplex (TDD) frame configurations.

TDD provides flexible placement without requiring a pair of spectrum resources. Generally for TDD layouts, interference between UL and DL needs to be considered, including Base Station (BS) to BS interference and User Equipment (UE) to UE interference. One example includes a hierarchical heterogeneous network topology, where it may be of interest to consider different uplink-downlink configurations in different cells. Also of interest are layouts involving: different carriers deployed by different operators are included within the same frequency band and employ the same or different uplink-downlink configurations, where possible interference may include adjacent channel interference as well as co-channel interference such as remote BS-to-BS interference.

Currently, Long Term Evolution (LTE) TDD allows asymmetric UL-DL allocations by providing semi-static allocations of uplink-downlink configurations using seven different semi-static configurations. The semi-static allocation may or may not match the actual instantaneous traffic situation.

Drawings

For simplicity and clarity of illustration, elements illustrated in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.

Fig. 1 is a schematic block diagram illustration of a cellular system, according to some demonstrative embodiments.

Fig. 2 is a schematic block diagram illustration of a cellular node, in accordance with some demonstrative embodiments.

Fig. 3 is a schematic flow chart illustration of a Time Division Duplex (TDD) uplink-downlink (Ul-DL) configuration management method, in accordance with some demonstrative embodiments.

Fig. 4 is a schematic illustration of a product according to some example embodiments.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by those of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and/or circuits have not been described in detail so as not to obscure the discussion.

The discussion herein, using terms such as, for example, "processing," "computing," "calculating," "determining," "establishing," "analyzing," "checking," or the like, may refer to an operation and/or process of a computer, computing platform, computing system, or other electronic computing device, that manipulates and/or transforms data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform the operations and/or processes.

The terms "plurality" and "a plurality" as used herein include, for example, "a plurality" or "two or more". For example, "a plurality of entries" includes two or more entries.

References to "one embodiment," "an exemplary embodiment," "various embodiments," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, repeated usage of the phrase "in one embodiment" does not necessarily refer to the same embodiment, although it may.

As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

Some embodiments may be used in conjunction with various devices and systems, such as, for example, a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a smartphone device, a server computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, an in-vehicle device, an off-vehicle device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio-video (A/V) device, a wired or wireless network, a cellular network, a wireless communication station, a wireless communication device, an Access Point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio, A cellular node, a multiple-input multiple-output (MIMO) transceiver or device, a single-input multiple-output (SIMO) transceiver or device, a multiple-input single-output (MISO) transceiver or device, a device with one or more internal and/or external antennas, a Digital Video Broadcasting (DVB) device or system, a multi-standard radio device or system, a wired or wireless handheld device (e.g., a smartphone), a Wireless Application Protocol (WAP) device, a vending machine, a vending terminal, and so forth.

Some embodiments may be used in connection with devices and/or networks operating in accordance with existing Long Term Evolution (LTE) specifications, such as, for example: 3GPP TS 36.423: evolved universal terrestrial radio access network (E-UTRAM); x2 application protocol (X2AP) ("RAN 3"), 3GPP TS 36.201: "evolved universal terrestrial radio access (E-UTRA); physical layer-generic description "(" RAN 1 ").

Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, such as: radio Frequency (RF), Frequency Division Multiplexing (FDM), Orthogonal FDM (OFDM), single carrier frequency division multiple access (SC-FDMA), Time Division Multiplexing (TDM), Time Division Multiple Access (TDMA), extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), BluetoothGlobal Positioning System (GPS), wireless fidelity (Wi-Fi), Wi-Max and ZigBee^TMUltra Wideband (UWB), global system for mobile communications (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, Long Term Evolution (LTE) cellular systems, LTE advanced cellular systems, High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access (HSPA), HSPA +, single carrier radio transmission technology (1XRTT), evolution data optimized (EV-DO), advanced data rates for GSM evolution (EDGE), and so forth. Other embodiments may be used in various other devices, systems, and/or networks.

The phrase "wireless device" as used herein includes, for example, devices capable of wireless communication, communication stations capable of wireless communication, portable or non-portable devices capable of wireless communication, and the like. In some demonstrative embodiments, the wireless device may be or may include a peripheral device integrated with the computer, or a peripheral device attached to the computer. In some demonstrative embodiments, the phrase "wireless device" may optionally include a wireless device.

The term "communicating" as used herein with respect to wireless communication signals may include transmitting wireless communication signals and/or receiving wireless communication signals. For example, a wireless communication unit capable of communicating wireless communication signals may include: a wireless transmitter for transmitting a wireless communication signal to at least one other wireless communication unit; and/or a wireless communication receiver for receiving wireless communications from at least one other wireless communication unit.

Some exemplary embodiments are described herein with respect to an LTE cellular system. However, other embodiments may be implemented in any other suitable cellular network, such as a 3G cellular network, a 4G cellular network, a WiMax cellular network, and so forth.

The term "antenna" as used herein may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, elements and/or arrays. In some embodiments, the antenna may implement transmit and receive functions using separate transmit and receive antenna elements. In some embodiments, the antenna may implement transmit and receive functions using common and/or integrated transmit/receive elements. The antennas may include, for example, phased array antennas, single element antennas, dipole antennas, a set of switched beam antennas, and so forth.

As used herein, a "cell" may include a combination of multiple network resources, such as downlink and optionally uplink resources. Resources may be controlled and/or allocated, for example, by a cellular node (also referred to as a "base station") or the like. The link between the carrier frequency of the downlink resource and the carrier frequency of the uplink resource may be indicated in system information transmitted on the downlink resource.

Referring now to fig. 1, fig. 1 schematically illustrates a block diagram of a cellular system 100, in accordance with some demonstrative embodiments. For example, the cellular system 100 may include a fourth generation cellular system, such as, for example, a WiMAX cellular system, a Long Term Evolution (LTE) or LTE advanced cellular system, or the like.

As shown in fig. 1, in some demonstrative embodiments, system 100 may include a plurality of cellular nodes (e.g., including cellular nodes 106 and 108) capable of transmitting content, data, information and/or signals corresponding to a plurality of cells (e.g., including cells 102 and 104). For example, node 106 may communicate with a plurality of User Equipment (UE) devices 110 within cell 102 and/or node 108 may communicate with a plurality of User Equipment (UE) devices 112 within cell 104.

In some demonstrative embodiments, nodes 106 and/or 108 may include evolved node bs (enbs). For example, nodes 106 and/or 108 may be configured to perform: radio Resource Management (RRM), radio bearer control, radio admission control (access control), connection mobility management, scheduling of resources between the UE and the eNB (e.g., dynamic allocation of resources to the UE on both uplink and downlink), header compression, link encryption of user data flows, packet routing of user data towards a destination (e.g., another eNB or an Evolved Packet Core (EPC)), scheduling and/or transmitting paging messages (e.g., incoming calls and/or connection requests), broadcast information coordination, measurement reporting, and/or any other operations.

In other embodiments, nodes 106 and/or 108 may include any other functionality and/or may perform the functionality of any other cellular node (e.g., node b (nb)).

In some demonstrative embodiments, UEs 110 and/or 112 may include, for example, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a mobile internet device, a handheld computer, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionality with PDA device functionality), a consumer device, an on-board device, an off-board device, a mobile or portable device, a mobile phone, a cellular phone, a PCS device, a mobile or portable GPS device, a DVB device, a relatively Small-sized computing device, a non-desktop computer, a "flip-up, life-sharing" (CSLL) device, an ultra-mobile device (UMD), an ultra-mobile pc (umpc), a Mobile Internet Device (MID), "Origami" device, or a computing device, Video devices, audio devices, a/V devices, gaming devices, media players, smart phones, and the like.

Referring to fig. 2, fig. 2 schematically illustrates a cellular node 200 according to some demonstrative embodiments. For example, cellular node 200 may perform the functions of node 106 (fig. 1) and/or node 108 (fig. 1).

In some demonstrative embodiments, cellular node 200 may include one or more wireless communication units 202 to perform wireless communication between node 200 and one or more other devices (e.g., one or more other cellular nodes, UEs, and the like).

In some demonstrative embodiments, wireless communication unit 202 may include, or may be associated with, one or more antennas. In one example, wireless communication unit 202 may be associated with at least two antennas (e.g., antennas 208 and 210).

In some demonstrative embodiments, antennas 208 and/or 210 may include any type of antenna suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas 208 and/or 210 may include any suitable configuration, structure, and/or arrangement of one or more antenna elements, components, units, components, and/or arrays. For example, antennas 208 and/or 210 may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like.

In some embodiments, antennas 208 and/or 210 may implement transmit and receive functions using separate transmit and receive antenna elements. In some embodiments, antennas 208 and/or 210 may implement transmit and receive functions using common and/or integrated transmit/receive elements.

In some demonstrative embodiments, wireless communication unit 202 may include, for example, at least one radio 204 and at least one controller 206 for controlling communications performed by radio 204. For example, radio 204 may include one or more wireless transmitters, receivers, and/or transceivers capable of transmitting and/or receiving wireless communication signals, RF signals, frames, blocks, transport streams, packets, messages, data items, and/or data.

In some demonstrative embodiments, radio 204 may include a multiple-input multiple-output (MIMO) transmitter-receiver system (not shown), which may be capable of performing the antenna beamforming method as desired.

In some demonstrative embodiments, radio 204 may include a turbo decoder and/or a turbo encoder (not shown) for encoding and/or decoding the data bits into data symbols, as desired.

In some demonstrative embodiments, radio 204 may include an OFDM and/or SC-FDMA modulator and/or demodulator (not shown) configured to transmit OFDM signals over a Downlink (DL) channel, e.g., between cellular node 200 and the UE, and SC-FDMA signals over an Uplink (UL) channel, e.g., between the UE and cellular node 200.

In some demonstrative embodiments, node 200 may include a Time Division Duplex (TDD) UL-DL configuration controller 230 to control a TDD UL-DL configuration of time resources allocated for UL and DL communications within a cell controlled by node 200. For example, node 106 (fig. 1) may include a TDD UL-DL configuration controller 230 for controlling TDD UL-DL configurations of time resources allocated for UL and DL communications within cell 102 (fig. 1); and/or node 108 (fig. 1) may include a TDD UL-DL configuration controller 230 for controlling TDD UL-DL configurations of time resources allocated for UL and DL communications within cell 104 (fig. 1).

In some demonstrative embodiments, TDD UL-DL configuration controller 230 may be implemented as part of wireless communication unit 202. In other embodiments, TDD UL-DL configuration controller 230 and wireless communication unit 202 may be implemented as separate elements of node 200, or as separate network entities that control dynamic allocation of UL-DL configurations for multiple cells.

In some demonstrative embodiments, cellular node 200 may include, for example, one or more of a processor 220, a memory unit 222, and a storage unit 224. In one example, one or more of the processor 220, memory 222, and/or memory 224 may be implemented as one or more elements separate from the wireless communication unit 202 and/or TDD UL-DL configuration controller 230. In another example, one or more of the processor 220, memory 222, and/or memory 224 may be implemented as part of the wireless communication unit 202 and/or TDD UL-DL configuration controller 230.

Processor 220 includes, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multi-core processor, a microprocessor, a main processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, a circuit, a logic unit, an Integrated Circuit (IC), an application specific IC (asic), or any other suitable multi-purpose or special-purpose processor or controller. Processor 220 executes instructions, for example, of an Operating System (OS) of node 200 and/or one or more suitable applications.

The memory unit 222 includes, for example, Random Access Memory (RAM), Read Only Memory (ROM), Dynamic RAM (DRAM), synchronous DRAM (SD-RAM), flash memory, volatile memory, non-volatile memory, cache memory, buffers, short term memory units, long term memory units, or other suitable memory units. Storage unit 224 includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. The memory unit 222 and/or the storage unit 224 may, for example, store data processed by the node 200.

Referring back to fig. 1, in some demonstrative embodiments, nodes 106 and 108 may be configured to perform tdd ul-DL configuration management, e.g., as described in detail below.

In some demonstrative embodiments, nodes 106 and 108 may communicate TDD UL-DL configuration information. For example, node 106 may transmit TDD UL-DL configuration information to node 108 regarding the TDD UL-DL configuration of cell 102; and/or node 108 may transmit TDD UL-DL configuration information to node 106 regarding the TDD UL-DL configuration of cell 104, e.g., as described below. In other embodiments, the TDD UL-DL configuration information may be shared with other network entities, which may define the TDD UL-DL configuration to be used at nodes 106 and 108.

Some demonstrative embodiments are described with reference to an eNB-to-eNB interface for communicating TDD UL-DL configuration information between two enbs. However, other embodiments may be implemented with respect to any other interface, e.g., an eNB-to-OAM interface to communicate TDD UL-DL configuration information between an eNB and an operations and management (QAM) interface between the eNB and an Element Management System (EMS), e.g., a Mobility Management Entity (MME), etc.

In some demonstrative embodiments, nodes 106 and 108 may utilize TDD UL-DL configuration information, e.g., for enhanced interference management and traffic adaptation (eIMTA) and/or for any other purpose.

In some demonstrative embodiments, nodes 106 and 108 may utilize TDD UL-DL configuration information, e.g., for dynamic TDD UL-DL configuration. For example, a first node (e.g., node 106) may transmit TDD UL-DL configuration information to a second node (e.g., node 108) regarding TDD UL-DL configurations of a cell (e.g., cell 102) controlled by the first node. The second node (e.g., node 108) may adapt (e.g., dynamically adapt) the TDD UL-DL configuration of a cell (e.g., cell 104) controlled by the second node based at least on the TDD UL-DL of the first cell. For example, node 108 may dynamically adapt the TDD UL-DL configuration of cell 104 by dynamically taking into account uplink and downlink traffic and other conditions of cell 102.

In some demonstrative embodiments, node 106 may transmit a message including a TDD UL-DL configuration update to update at least one other node, e.g., node 108, with the TDD UL-DL configuration allocated by node 106, e.g., by TDD UL-DL configuration controller 230 (fig. 1) of node 106, for communication within cell 102, e.g., as described in detail below.

In some demonstrative embodiments, node 108 may receive the message from node 106 and may allocate a TDD UL-DL configuration for communication within the cell based on the TDD UL-DL configuration update received from node 106. For example, TDD UL-DL configuration controller 230 (fig. 1) of node 108 may allocate a TDD UL-DL configuration for communication within cell 104 based on a TDD UL-DL configuration update received from node 106.

In some demonstrative embodiments, the messages may include X2 application protocol (X2AP) messages and X2 application protocol (X2AP) messages may be configured for communication between the plurality of enbs. In other embodiments, the message may comprise any other message configured for communication between any other cellular node.

In some demonstrative embodiments, the TDD UL-DL configuration update may be transmitted as part of a dedicated field of the X2AP message, e.g., an existing message type, which may include other fields for other predefined purposes.

In some demonstrative embodiments, the TDD UL-DL configuration update may be communicated as part of a dedicated X2AP message, e.g., a new message type, which may be dedicated to communicating the TDD UL-DL configuration update.

In some demonstrative embodiments, it may be advantageous to communicate the TDD UL-DL configuration update as part of an existing message type, e.g., with reduced standardization impact.

In some demonstrative embodiments, transmitting the TDD UL-DL configuration update as part of the dedicated message may enable the TDD UL-DL configuration update to be provided in a timing and/or frequency, which may be independent of and/or different from the timing of transmitting the existing message. For example, communicating a TDD UL-DL configuration update as part of a dedicated message may enable TDD UL-DL updates to be provided at a frequency that may be higher than the frequency of resource status updates (e.g., a frequency of less than one second).

In some demonstrative embodiments, the message may also include a cell identifier identifying a cell corresponding to the TDD UL-DL configuration update. For example, node 106 may transmit a message that includes an identifier of cell 102 and TDD UL-DL information corresponding to cell 102.

In some demonstrative embodiments, the TDD UL-DL configuration update may be included as part of a predefined Information Element (IE) ("dynamic subframe allocation IE").

In some demonstrative embodiments, the TDD UL-DL configuration update may be included as part of a message defined for communicating load and interference coordination information.

For example, TDD UL-DL configuration updates may be included as part of a load information X2AP message, which may be transmitted from an eNB (e.g., node 106) to one or more neighboring enbs (e.g., including eNB 108).

In an example, the dynamic subframe allocation IE may be included as part of the load information X2AP message, e.g., as follows:

TABLE 1

The marker enumeration (sa0, sa1, sa2, sa3, sa4, sa5, sa6, …) (enumered (sa0, sa1, sa2, sa3, sa4, sa5, sa6, …)) used in table 1 indicates that the dynamic subframe allocation IE may include one of the values marked as "sa". The value labeled "sa" may include a value indicating a different TDD UL-DL configuration. For example, the values sa0, sa1, sa2, sa3, sa4, sa5, sa6 may indicate seven respective predefined TDD UL-DL configurations. In one embodiment, the seven predefined TDD UL-DL configurations may include, for example, a TDD UL-DL configuration defined by the LTE specifications, such as by 3GPP TS 36.211 ("evolved universal terrestrial radio access (E-UTRA); physical channel and modulation"). For example, a value sa0 may represent a first predefined allocation of time resources, a value sa1 may represent a second predefined allocation of time resources, and so on. In other embodiments, the dynamic subframe allocation IE may comprise any other representation of the TDD UL-DL configuration, e.g., selected from any other predefined set of TDD UL-DL configurations and/or defined in any other suitable manner, e.g., with or without reference to one or more predefined configurations.

According to table 1, the load information X2AP message may include a "cell ID" IE that includes a cell identifier identifying the cell to which the dynamic subframe allocation IE corresponds and a target cell identifier (labeled "target cell ID") identifying the cell of the node intended to receive the dynamic subframe allocation IE.

In some demonstrative embodiments, the TDD UL-DL configuration update may be included as part of a message broadcast by the eNB and including a configuration update corresponding to the eNB.

For example, TDD UL-DL configuration updates may be included as part of a configuration update X2AP message, which may be transmitted from an eNB (e.g., node 106) to one or more neighboring enbs (e.g., including eNB 108).

In one example, the dynamic subframe allocation IE may be included as part of the served cell information IE of the configuration update X2AP message, e.g., as follows:

TABLE 2

In some demonstrative embodiments, the TDD UL-DL configuration update may be included as part of a dedicated message defined for communicating the dynamic subframe allocation IE.

In an example, the dynamic subframe allocation IE may be included as part of a dedicated TDD configuration update X2AP message, e.g., as follows:

TABLE 3

In some demonstrative embodiments, nodes 106 and 108 may communicate one or more additional information to facilitate dynamic allocation of UL and DL resources and/or to communicate additional information related to a tdd UL-DL configuration used by nodes 106 and/or 108 with respect to cells 102 and/or 104, e.g., as detailed below.

In some demonstrative embodiments, a node (e.g., node 106) may transmit a status report to one or more other nodes (e.g., including node 108) regarding UL and/or DL queue status of one or more cells controlled by the node, e.g., as described below.

In some demonstrative embodiments, the UL-DL queue status may include one or more parameters characterizing the current cell requirements of the UL and/or DL required. In an example, the status report may include an estimated number of bits representing an estimated buffer size for UL and/or DL transmissions.

In some demonstrative embodiments, nodes 106 and 108 may transmit a status report corresponding to the UL-DL queue status of cells 102 and/or 104, e.g., as described below.

In some demonstrative embodiments, a node (e.g., node 106) may receive a status request message from another node (e.g., a "target node") (e.g., node 108) indicating the request, requesting a status report of the UL-DL queue status corresponding to at least one cell (e.g., cell 102) controlled by the node from the node. The node may send a status update message including the requested report, e.g., in response to the status request message.

In some demonstrative embodiments, the status request message and the status update message may be transmitted as part of an X2AP resource status reporting procedure.

In some demonstrative embodiments, the status request message may include a resource status request message including a reporting feature IE including a bit having a predefined value indicating the request for the status report, and a reporting period IE defining a requested period (e.g., a minimum period) for the node to send the status report to the target node.

For example, the resource status request message may include a reporting feature IE including a sixth bit indicating whether a status report is requested, and a reporting period IE for indicating the requested period, e.g., as follows:

TABLE 4

For example, the "UL-DL queue size periodicity" bit may be set to a predefined value, e.g., 1, to indicate that a RESOURCE STATUS UPDATE (RESOURCE STATUS UPDATE) message will include UL-DL queue STATUS information and will be sent from the target node at the period indicated at the reporting period IE, e.g., as defined below.

In some demonstrative embodiments, the status update message may include a resource status update message including a UL/DL queue status IE including a UL queue status and a DL queue status.

For example, the resource status update message may include UL/DL queue size IE, UL queue status and DL queue status, e.g., as follows:

TABLE 5

The UL-DL queue size IE may indicate the estimated buffer size to be transmitted in the DL and UL for a particular cell of the eNB transmitting the resource status update, e.g. as follows:

IE/group name	Presence of	Range of	IE type and reference	Semantic description
					UL queue size	M		Integer (0 … FFS)
DL queue size	M		Integer (0 … FFS)

TABLE 6

In some demonstrative embodiments, the status request message and the status update message may be transmitted as part of a dedicated UL/DL queue status X2AP message.

In some demonstrative embodiments, the status request message may be transmitted from the first node to the second node and may include a dedicated buffer status request message including a reporting period IE defining a requested period at which the second node is to update the first node with the UL-DL queue status. The use of a dedicated buffer status request message may enable the first node to request the second node to report the UL-DL status at a different frequency (e.g., a higher frequency) than, for example, the frequency at which the second node sends the resource status update message.

In an example, the buffer status request message may include one or more identifiers of one or more cells for which UL-DL queue status is requested, and a requested reporting period at which UL-DL queue status is to be provided, e.g., as follows:

TABLE 7

In some demonstrative embodiments, the status update message may be transmitted from the second node to the first node and may include a dedicated buffer status update message including the UL-DL queue status of the cell identified by the status request message. In an example, the dedicated buffer status update message may be sent in response to a dedicated buffer status request message. In another example, the dedicated buffer status update message may be sent in response to the resource status request message described above.

In an example, the dedicated buffer status update message may include a UL-DL queue status IE, e.g., as follows:

TABLE 8

In some demonstrative embodiments, nodes 106 and 108 may transmit a timing message including timing information indicating a timing at which node 106 is allowed to update the TDD UL-DL configuration allocated for cell 102 and/or a timing at which node 108 is allowed to update the TDD UL-DL configuration allocated for cell 104. In an example, timing updates can be synchronized across multiple cells as needed.

In some demonstrative embodiments, the timing information may be transmitted as part of an IE including cell configuration information of one or more cells (e.g., a served cell information IE).

In an example, a first node (e.g., node 106) may transmit, e.g., to a second node, an eNB configuration update message including a served cell information IE, which may include a configuration update time scale field indicating how frequently the first node is allowed to update the TDD UL-DL configuration. For example, the served cell information IE may include a configuration update time scale field, e.g., as follows:

TABLE 9

The TDD UL-DL configuration update time scale IE may be defined as, for example, an integer value within a predefined range (e.g., between 10 and 640 milliseconds); enumerated values defined as a finite set of values within the range, such as 10 milliseconds, 20 milliseconds, 40 milliseconds, 80 milliseconds, 160 milliseconds, 320 milliseconds, and 640 milliseconds; or defined in any other way.

In some demonstrative embodiments, timing information may be configured, e.g., by OAM, to all enbs, e.g., to both nodes 106 and 108.

In some demonstrative embodiments, nodes 106 and 108 may transmit an indication of the UL-DL configuration subset selected by node 106 from the predefined set of UL-DL configurations and/or an indication of the UL-DL configuration subset selected by node 108 from the predefined set of UL-DL configurations.

In some demonstrative embodiments, node 106 may be configured to select a TDD UL-DL configuration from a predefined set of seven TDD UL-DL configurations (e.g., as defined by 3GPP TS 36.211).

In some demonstrative embodiments, node 106 may transmit an eNB configuration update message including a served cell information IE including a subframe allocation IE indicating one or more allowed UL-DL configurations selected by node 106 for use by one or more other nodes, e.g., node 108; and/or node 108 may transmit an eNB configuration update message including a served cell information IE including a subframe allocation IE indicating one or more allowed UL-DL configurations selected by node 108 for use by one or more other nodes (e.g., node 106). For example, the served cell information IE may include a subframe allocation IE, e.g., as follows:

watch 10

In some demonstrative embodiments, the subframe allocation subset IE may indicate which one or more subsets of, e.g., seven TDD UL-DL configurations are allowed to be used by one or more other nodes by the node transmitting the served cell information IE. In an example, the subframe allocation subset IE may be defined as a bitmap in which a bit is set to a predefined value, e.g., 1, to indicate that the corresponding TDD UL-DL configuration is allowed to be used by one or more other nodes. For example, a first bit may be set to "1" and all other bits may be set to zero to indicate that the first TDD UL-DL configuration is allowed to be used by one or more other nodes.

In an example, the node 106 may transmit a subframe allocation subset IE indicating a number of TDD-UL-DL configurations allowed to be used. Node 108 may receive the subframe allocation subset IE from node 106 and may select a TDD UL-DL configuration from a plurality of TDD UL-DL configurations indicated as allowed by the subframe allocation subset IE. Node 108 may send a TDD UL-DL configuration update indicating the TDD UL-DL configuration selected by node 108, as described above.

In some demonstrative embodiments, the TDD UL-DL may be configured to a configuration selected by, e.g., the OAM, for all enbs (e.g., both nodes 106 and 108).

In some demonstrative embodiments, a particular node may transmit a message including an indication of an average UL-DL spectral efficiency ("spectral efficiency indication") of one or more cells controlled by the particular node to another node. For example, nodes 106 and 108 may transmit an indication of the average UL-DL spectral efficiency of cells 102 and/or 104.

In some demonstrative embodiments, the X2AP resource status reporting procedure may be used to support communication of a spectral efficiency indication, e.g., as described below.

In some demonstrative embodiments, a first node may transmit a request message to a second node, the request message including a request for an indication of the average UL-DL spectral efficiency and defining a requested period for transmitting the indication of the average UL-DL spectral efficiency.

In some demonstrative embodiments, a RESOURCE status request (RESOURCE status request) may be sent by the first node to request the second node to transmit the spectral efficiency indication. For example, an IE of a resource status request (e.g., a reporting characteristics IE) may include a bit ("UL-DL spectral efficiency periodicity") that is used to represent a request for a spectral efficiency indication. In an example, the reporting characteristics IE of the resource status request of table 4 may be modified to include an additional bit (e.g., a seventh bit) to indicate a request for a spectral efficiency indication. A reporting periodicity IE may also be included, for example as described above with reference to table 4. Alternatively, a buffer status request message may be used, as described above with reference to table 7.

In some demonstrative embodiments, the second node may transmit a resource status update message including average UL and DL spectral efficiency information, e.g., whether the "UL-DL spectral efficiency periodicity" bit is set to a predefined value (e.g., 1).

In an example, the RESOURCE STATUS UPDATE (RESOURCE STATUS UPDATE) message may include a UL-DL spectral efficiency IE, e.g., as follows:

TABLE 11

The UL-DL spectral efficiency IE may include an indication of the average UL and DL spectral efficiencies. In an example, the UL-DL spectral efficiency IE may be defined as an integer value, e.g., in units (bits/sec)/hz. In another example, the UL-DL spectral efficiency IE may be defined as an enumerated value.

Referring to fig. 3, fig. 3 schematically illustrates a TDD UL-DL configuration management method according to some demonstrative embodiments. In some embodiments, one or more operations of the method of fig. 3 may be performed by a cellular system, such as system 100 (fig. 1), and/or a cellular node, such as nodes 106 and/or 108 (fig. 1).

As shown at block 302, the method may include communicating a message between a first cellular node and at least one second cellular node, the message including an indication of a TDD UL-DL configuration allocated by the first node for communication within at least one first cell controlled by the first node. For example, nodes 106 and 108 (fig. 1) may transmit an X2-AP message that includes a cell identifier identifying cell 102 (fig. 1) and an indication of the tdd ul-DL configuration assigned by node 106 for communication within cell 102.

As shown in block 304, communicating the message may include sending the message by the first node. For example, node 106 (fig. 1) may transmit a message that includes an indication of a TDD UL-DL configuration that node 106 allocates for communication within cell 102.

As shown at block 306, transmitting the message may include receiving the message at the second node. For example, node 108 (fig. 1) may receive a message including an indication of a TDD UL-DL configuration that node 106 allocates for communication within cell 102.

As shown at block 308, the method may include allocating a TDD UL-DL configuration for communication within the second cell based on the TDD UL-DL configuration updated by the first node. For example, node 108 (fig. 1) may update the TDD UL-DL configuration allocated for cell 104 (fig. 1) based on the TDD UL-DL configuration allocated for cell 102 received from node 106 (fig. 1).

Referring to FIG. 4, FIG. 4 schematically illustrates an article of manufacture 400, according to some example embodiments. The article 400 may comprise a non-transitory machine-readable storage medium 402 to store logic 404, the logic 404 operable to perform at least a portion of the functions of the nodes 106 and/or 108 (fig. 1), the TDD UL/DL controller 230 (fig. 2), the wireless communication unit 202 (fig. 2), for example, and/or to perform one or more operations of the method of fig. 3. The phrase "non-transitory machine-readable medium" is intended to include all computer-readable media, with the sole exception of transitory, propagating signals.

In some demonstrative embodiments, product 400 and/or machine-readable storage medium 402 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, the machine-readable storage medium 402 may include RAM, DRAM, double data rate DRAM (DDR-DRAM), SDRAM, static RAM (sram), ROM, programmable ROM (prom), erasable programmable ROM (eprom), electrically erasable programmable ROM (eeprom), compact disc ROM (CD-ROM), compact disc recordable (CD-R), compact disc rewritable (CD-RW), flash memory (e.g., NOR or NAND flash memory), Content Addressable Memory (CAM), polymer memory, phase change memory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppy disk, a hard disk drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and so forth. The computer-readable storage medium may include any suitable medium that participates in downloading or transmitting a computer program from a remote computer to a requesting computer, by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., a modem, radio or network connection).

In some demonstrative embodiments, logic 404 may include instructions, data, and/or code, which, when executed by a machine, may cause the machine to perform the methods, processes and/or operations described herein. The machine may include, for example, any suitable processing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, or the like.

In some demonstrative embodiments, logic 404 may include, or may be implemented as: software, software modules, applications, programs, subroutines, instructions, instruction sets, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, Visual, compiled and/or interpreted programming language, such as C, C + +, Java, BASIC, Matlab, Pacal, Visual BASIC, assembly language, machine code, and so forth.

Functions, operations, components and/or features described herein with reference to one or more embodiments may be used in combination with, or with, one or more other functions, operations, components and/or features described with reference to one or more other embodiments, or vice versa.

While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may 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 true scope of the invention.

Claims (32)

1. An evolved node B, eNB, comprising:

circuitry for controlling communication of a message to share load information in an orthogonal frequency division multiplexing, OFDM, time division duplex, TDD, cellular system, the message having a first information element, IE, to indicate a cell identifier of a first wireless communication cell, a second IE to indicate uplink-downlink, UL-DL, configuration information intended for use by the first wireless communication cell, and a third IE to indicate a cell identifier of a second wireless communication cell; and

a transceiver coupled to the circuitry, the transceiver to transmit the message as an OFDM signal for allocating an UL-DL configuration for the second wireless communication cell based at least in part on the UL-DL configuration information.

2. The eNB of claim 1, wherein the OFDM TDD cellular system comprises a long term evolution, LTE, or LTE-advanced-a system.

3. The eNB of claim 1, wherein said message comprises an X2 application protocol X2AP message.

4. The eNB of claim 1, wherein said message comprises a load information message of X2 application protocol X2 AP.

5. The eNB of claim 1, wherein said first IE comprises a cell identifier IE of a cell information item IE group.

6. The eNB of claim 1, wherein the second IE comprises a dynamic subframe allocation IE of a cell information item IE group, the dynamic subframe allocation IE to indicate the UL-DL configuration information as a value within an enumerated value set, the value to indicate a predefined UL-DL configuration.

7. The eNB of claim 1, wherein the second IE comprises a UL-DL configuration update IE of a cell information item IE group, the UL-DL configuration update IE to indicate the UL-DL configuration information as values within a set of enumerated values, each enumerated value to indicate a different predefined UL-DL configuration.

8. The eNB of claim 1, wherein said third IE comprises a target cell identifier IE of a UL high interference information IE group.

9. The eNB of claim 1, wherein said transceiver is to transmit said message to an eNB controlling said second wireless communication cell.

10. The eNB of claim 1, comprising one or more antennas coupled to the transceiver, the transceiver to transmit the message as an OFDM signal via the one or more antennas.

11. An evolved node B, eNB, comprising:

a transceiver for receiving a message to share load information in an orthogonal frequency division multiplexing, OFDM, time division duplex, TDD, cellular system, the message having a first information element, IE, for indicating a cell identifier of a first wireless communication cell, a second IE, for indicating uplink-downlink, UL-DL, configuration information intended for use by the first wireless communication cell, and a third IE, for indicating a cell identifier of a second wireless communication cell; and

circuitry coupled to the transceiver, the circuitry to allocate a UL-DL configuration for the second wireless communication cell based at least in part on the UL-DL configuration information intended for use by the first wireless communication cell.

12. The eNB of claim 11, wherein the OFDM TDD cellular system comprises a long term evolution, LTE, or LTE advanced-a system.

13. The eNB of claim 11, wherein said message comprises an X2 application protocol X2AP message.

14. The eNB of claim 11, wherein said message comprises a load information message of X2 application protocol X2 AP.

15. The eNB of claim 11, wherein said first IE comprises a cell identifier IE of a cell information item IE group.

16. The eNB of claim 11, wherein the second IE comprises a dynamic subframe allocation IE of a cell information item IE group, the dynamic subframe allocation IE to indicate the UL-DL configuration information as a value within an enumerated value set, the value to indicate a predefined UL-DL configuration.

17. The eNB of claim 11, wherein the second IE comprises a UL-DL configuration update IE of a cell information item IE group, the UL-DL configuration update IE to indicate the UL-DL configuration information as values within a set of enumerated values, each enumerated value to indicate a different predefined UL-DL configuration.

18. The eNB of claim 11, wherein the third IE comprises a target cell identifier IE of a UL high interference information IE group.

19. The eNB of claim 11, wherein said transceiver is to receive said message from an eNB controlling said first wireless communication cell.

20. The eNB of claim 11, comprising one or more antennas coupled to said transceiver, said transceiver to receive said message as an OFDM signal via said one or more antennas.

21. An apparatus for communication, comprising

Logic for controlling transmission of a load information message of an X2 application protocol X2AP over an orthogonal frequency division multiplexing, OFDM, time division duplex, TDD, cellular system, at least a portion of the logic being implemented in hardware, the load information message having a cell identifier information element, IE, for indicating a cell identifier of a wireless communication cell, and an uplink-downlink, UL-DL, configuration update IE, for indicating UL-DL configuration information intended for use by the wireless communication cell indicated by the cell identification number; and

a radio coupled to the logic to transmit the load information message as an OFDM signal for allocating an UL-DL configuration for a second wireless communication cell based at least in part on the UL-DL configuration information.

22. The apparatus of claim 21, wherein the cell identifier IE comprises part of a cell information item IE group.

23. The apparatus of claim 21, wherein the UL-DL configuration update IE comprises part of a set of cell information items IE, the UL-DL configuration update IE to indicate the UL-DL configuration information as values within a set of enumerated values, each enumerated value to indicate a defined UL-DL configuration.

24. The apparatus of claim 21, wherein the load information message has a target cell identifier IE for indicating a different wireless communication cell, the target cell identifier IE comprising part of a group of UL high interference information IEs.

25. The apparatus of claim 21, wherein the OFDM TDD cellular system comprises a long term evolution, LTE, or LTE advanced-a system.

26. A method for communication, comprising:

generating a message to share load information in an orthogonal frequency division multiplexing, OFDM, time division duplex, TDD, cellular system, the message having a first information element, IE, to indicate a cell identifier of a first wireless communication cell, a second IE to indicate uplink-downlink, UL-DL, configuration information intended for use by the first wireless communication cell, and a third IE to indicate a cell identifier of a second wireless communication cell; and

transmitting the load information message over a communication channel for allocating a UL-DL configuration for the second wireless communication cell based at least in part on the UL-DL configuration information.

27. The method of claim 26, comprising transmitting the load information message as an OFDM signal.

28. The method of claim 26, comprising sending the load information message over a data network.

29. The method of claim 26, wherein the cell identifier IE comprises part of a cell information item IE group and the UL-DL configuration update IE comprises part of a cell information item IE group, the UL-DL configuration update IE to indicate the UL-DL configuration information as values within a set of enumerated values, each enumerated value to indicate a defined UL-DL configuration.

30. The method of claim 26, wherein the load information message has a target cell identifier IE for indicating a different wireless communication cell, the target cell identifier IE comprising part of a group of UL high interference information IEs.

31. A computer-readable storage medium having stored thereon instructions that, when executed, cause a machine to perform the method of any of claims 26-30.

32. A computer system comprising means for performing the method of any of claims 26-30.