EP3873005B1

Asymmetric tdd in flexible use spectrum

Abstract

This record has no abstract on file.

EP3873005B1, drawing sheet 1 — Sheet 1 of 16

Term

3.1 yearsleft in the term

Expires 13 November 2029.

8 claims: 3 independent, 5 dependent

1
A method, comprising:sending a first time division duplex (TDD) signal via a TDD uplink portion (610, 630, 1210) of a time division duplex (TDD) communication path operating over a first frequency band (604, 624, 1204);receiving a second TDD signal via a TDD downlink portion (612, 632, 1212) of the TDD communication path operating over the first frequency band;the TDD communication path operating during a communication time (TU + TD) including an uplink period (TU) and a downlink period (TD);the TDD uplink portion (610, 630, 1210) occurring during the uplink period (TU);the TDD downlink portion (612, 632, 1212) occurring during the downlink period (TD);the first frequency band being disposed between, contiguous with, and mutually exclusive of a second frequency band (602, 622, 1202) and a third frequency band (606, 626, 1206);further configured by one of: a first implementation in which, each of the second and third frequency bands (602, 606) provide respective first and second FDD uplink communication paths during the communication time;during the uplink period: the TDD uplink portion (610) uses the entirety of the first frequency band (604);during the downlink period: the TDD downlink portion (612) uses less than the entirety of the first frequency band (604);the TDD downlink portion (612) is disposed between a first downlink guard band portion (614) and a second downlink guard band portion (616);each of the first and second downlink guard band portions (614, 616) is allocated from portions of the first frequency band (604) not used by the TDD downlink portion (612);wherein the first downlink guard band portion (614) and the second downlink guard band portion (616) utilize the same spectrum bandwidth;a second implementation in which, each of the second and third frequency bands (622, 626) provide respective first and second FDD downlink communication paths during the communication time;during the uplink period: the TDD uplink portion (630) uses less than the entirety of the first frequency band (624);the TDD uplink portion (630) is disposed between a first uplink guard band portion (634) and a second uplink guard band portion (636);and each of the first and second uplink guard band portions (634, 636) is allocated from portions of the first frequency band (624) not used by the TDD uplink portion (630);the first uplink guard band portion (634) and the second uplink guard band portion (636) utilize the same spectrum bandwidth;and during the downlink period: the TDD downlink portion (632) uses the entirety of the first frequency band (624);a third implementation in which, the second frequency band (1202) is associated with a wireless broadcast;the third frequency band (1206) provides an FDD downlink communication path during the communication time;during the uplink period: the TDD uplink portion (1210) uses less than the entirety of the first frequency band (1204);the TDD uplink portion (1210) is disposed between a first uplink guard band portion (1214) and a second uplink guard band portion (1216);the first uplink guard band portion (1214) and the second uplink guard band portion (1216) utilize the same spectrum bandwidth;and each of the first and second uplink guard band portions (1214, 1216) is allocated from portions of the first frequency band (1204) not used by the TDD uplink portion (1210);and during the downlink period: the TDD downlink portion (1212) uses the entirety of the first frequency band (1204).
4
The method of any of the above claims, further characterized by :the TDD uplink portion (610, 630, 1210) being associated with a first time-bandwidth product;and the TDD downlink portion (612, 632, 1212) being associated with a second time-bandwidth product;and further characterized by one of: a) wherein the first time-bandwidth product is substantially the same as the second time-bandwidth product;and the TDD communication path operates as a symmetric TDD communication path;or b) wherein the uplink period is substantially the same as the downlink period;and the TDD communication path operates as an asymmetric TDD communication path.
8
An apparatus, comprising a communications device configured to carry out the method of any one of the above claims.

Independent claims3

128 paragraphs in 6 sections, as filed

0001This application is a continuation of and claims the benefit of U.S. Application Serial No. <patcit id="pcit0001" dnum="US20100124183A1"><text>US2010/0124183A1</text></patcit>.

BACKGROUND

0002The invention relates generally to wireless communication systems and more particularly to a communication method that uses time division duplexing.

0003In addition to traditional voice services, next generation wireless communication systems have to support various different types of multimedia services, including broadcasts, video conferencing, and interactive applications, for example. Many of these multimedia services may require flexibility in their use of spectrum capacity to operate effectively. The typical spectrum management approach is to assign frequencies to a particular use. This approach, however, has become somewhat limited in view of the complexity and overlap between the operations of next generation services and applications. One regulatory solution has been the introduction of flexible-use spectrum in which users of assigned portions of spectrum have more freedom to decide which technologies and services to deploy. In this regard, flexible-use spectrum can allow spectrum users to make timely commercial choices and can let market forces determine which competing technologies and services will be offered in a particular frequency band. Such approach can result in a more effective use of spectrum than that which occurs by imposing a technology or a service by regulation. As a result of these efforts to open up the spectrum, new user-based communication techniques are being considered that address aspects that are particular to next generation services and applications. For example, communication methods that include duplexing techniques or schemes that incorporate the inherent asymmetry in data flow that is characteristic of many multimedia services are being considered for next generation wireless communication systems.

0004Duplexing techniques include time division duplexing (TDD), frequency division duplexing (FDD), and/or hybrid duplexing, the latter of which includes aspects of both TDD and FDD schemes. In TDD, bidirectional communication or data flow is implemented through a communication link by separating the communication time within a given frequency band associated with the communication link into alternating transmission time slots and reception time slots. A time guard is used between time slots to reduce or minimize the likelihood of interference. In this scheme, a satellite or a base station, for example, can allocate a number of transmission time slots different from a number of reception time slots to a mobile device within a given time interval to produce asymmetric data communication. As the area of coverage provided by the satellite or the base station increases significantly, the guard time between time slots may be increased to compensate for delays that result from a longer signal round-trip between the satellite or base station and the mobile device. The increased delay can reduce the communication efficiency of the TDD scheme. In many instances, however, the time guard is sufficiently small even when large areas of coverage are concerned such that the TDD scheme efficiency remains adequate for many services or applications.

0005In FDD, bidirectional communication or data flow is implemented through a communication link by partitioning a given frequency band associated with the communication link into separate transmission and reception frequency bands that operate concurrently. Because the transmission and reception bands are separate from each other to reduce the likelihood of interference, no time delays occur associated with the transmission or reception of signals (i.e., no round-trip delays). Although the FDD scheme may be suitable for large areas of coverage because time delays do not play a significant role, the fixed and balanced nature of the transmission and reception frequency bands limit the flexibility that is necessary for asymmetric data communication in next generation wireless communication services. Some FDD schemes achieve asymmetry by using an auxiliary frequency band separate from the paired transmission and reception frequency bands to provide additional capacity in one direction of the data flow. This approach, however, requires the communication system to include additional hardware and/or software to handle the separate frequency band through which asymmetry is achieved.

0006<patcit id="pcit0002" dnum="US20060126546A1"><text>US 2006/0126546 A1</text></patcit> refers to a wireless communication system in an overlay network where systems using different frequency bands coexist. The wireless communication system includes at least one first duplexing system utilizing a first duplexing technique through a first frequency band, and at least one second duplexing system utilizing a second frequency band and a part of the first frequency band. The second duplexing system overlaps with the first duplexing system in coverage. <patcit id="pcit0003" dnum="US20070286156A1"><text>US 2007/0286156 A1</text></patcit> refers to a wireless system and method includes a FDD system configured to provide at least a first FDD channel operating within a first frequency band. A TDD system is configured to provide at least a first TDD channel operating within a second frequency band. The first frequency band and the second frequency band are separated by a third frequency band, and a half-duplex frequency division duplex (H-FDD) system is configured to provide at least a first H-FDD channel operating within the third frequency band. A transmission of the first H-FDD channel may be synchronized with one of an uplink transmission and a downlink transmission of the first TDD channel. <patcit id="pcit0004" dnum="US2004165547A1"><text>US 2004/165547 A1</text></patcit> describes that the amount of interference to communications in Time Division Duplexing (TDD) mode between a TDD mobile and a TDD base station from a mobile operating in Frequency Division Duplexing (FDD) mode that is located near to the TDD base station can be reduced by changing at least the frequency channel allocated to a particular TDD communications channel, and also by changing the timeslot allocated to that particular TDD communications channel. Thus, instead of allocating particular frequency channels to particular operators for TDD communication, the frequency channels used by any particular operator for TDD communication can change from frame to frame. The timeslots within a frame on a frequency channel may stay the same or may also change. Thus, any particular communications channel (6,8) will not remain on the same frequency channel, nor, possibly, on the same timeslot within a frame, from one frame to the next, so that no one TDD channel will have continuous interference from an FDD channel, but all the TDD communications channels will have the interference shared between them. Thus, a need exists for new methods for asymmetric communication in wireless communication systems.

SUMMARY

0007The invention is defined by the appended independent claim to which reference is now directed. Optional features are set out in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

0008<ul id="ul0001" list-style="none"><li><figref idref="f0001">FIG. 1</figref> is a schematic representation of a wireless communication system, according to an example.</li><li><figref idref="f0002">FIG. 2</figref> is a schematic representation of coexisting mobile devices, according to examples.</li><li><figref idref="f0003">FIG. 3</figref> is a diagram illustrating an asymmetric time division duplexing (TDD) scheme in AWS-3 flexible use spectrum, according to an example.</li><li><figref idref="f0004">FIG. 4</figref> is a diagram illustrating aspects of an asymmetric TDD communication scheme for use in the AWS-3 portion of the wireless spectrum, according to an example.</li><li><figref idref="f0005">FIGS. 5A-5B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent frequency division duplexing (FDD) schemes, according to examples.</li><li><figref idref="f0006">FIGS. 6A-6B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD schemes, according to embodiments of the invention.</li><li><figref idref="f0007">FIGS. 7A-7B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD and synchronous TDD schemes, according to examples.</li><li><figref idref="f0008">FIGS. 7C-7D</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD and synchronous TDD schemes, according to examples.</li><li><figref idref="f0009">FIGS. 8A-8B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent synchronous TDD and asynchronous TDD schemes, according to embodiments.</li><li><figref idref="f0010">FIGS. 9A-9B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent synchronous TDD and temporally-asymmetric TDD schemes, according to examples.</li><li><figref idref="f0011">FIGS. 10A-10B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent temporally-asymmetric TDD schemes, according to examples.</li><li><figref idref="f0012">FIGS. 11A-11B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent temporally-asymmetric TDD schemes, according to examples.</li><li><figref idref="f0013">FIG. 12A</figref> is a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD and broadcast schemes, according to an embodiment of the invention. <figref idref="f0013">FIG. 12B</figref> is a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD and broadcast schemes, according to an example.</li><li><figref idref="f0014 f0015 f0016">FIGS. 13-15</figref> are flow charts illustrating a method for a TDD scheme, according to examples.</li></ul>

DETAILED DESCRIPTION

0009The devices and methods described herein are generally related to wireless communication systems. For example, the devices and methods are suitable for use in cellular (terrestrial) communication systems, satellite communication systems, and/or hybrid satellite and terrestrial (satellite/terrestrial) communication systems, such as a Mobile Satellite Services (MSS) system with an Ancillary Terrestrial Component (ATC). An example of such a hybrid satellite/terrestrial communication system is described in U.S. patent application <patcit id="pcit0005" dnum="US20080268838A"><text>US 2008/0268838</text></patcit> to Zufall et, al An MSS MSS/ATC system can use one or more satellites to support a wide geographic coverage of mobile satellite interactive (i.e., bidirectional) services. For example, a portion of the 2 GHz spectrum allocated for MSS satellite communications can be used to provide effective service coverage to rural and remote areas. Along with the MSS network, the land-based ATC network can facilitate service penetration in urban and suburban areas through effective satellite and terrestrial frequency reuse.

0010In one or more embodiments, a method associated with terrestrial, satellite, and/or hybrid satellite/terrestrial wireless communication systems includes receiving and transmitting signals over an asymmetric time division duplex (TDD) communication path. Signals are received over the asymmetric TDD communication path via a first portion of a first frequency band. The first frequency band is adjacent to a second frequency band and to a third frequency band. The first frequency band is different from the second frequency band and from the third frequency band. The first frequency band, the second frequency band, and the third frequency band can be mutually exclusive. A first frequency division duplex (FDD) communication path can be operated in the second frequency band. A second FDD communication path can be operated in the third frequency band. Signals are transmitted over the TDD communication path via a second portion of the first frequency band that is different from the first portion of the first frequency band.

0011It is noted that, as used in this written description and the appended claims, the singular forms "a," "an" and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, the term "a frequency" is intended to mean a single frequency or a combination of frequencies. Similarly, the term "a time slot" is intended to mean, for example, a single time slot or more than one time slot.

0012<figref idref="f0001">FIG. 1</figref> is a schematic representation of a wireless communication system 100, according to an embodiment. The wireless communication system 100 is configured to provide next generation wireless communication services and applications, including interactive services, for example. The wireless communication system 100 includes a terrestrial antenna 140 and a mobile device 110. In some embodiments, the wireless communication system 100 can include at least one of a satellite 130 and a broadcast antenna 120. In some embodiments, the wireless communication system 100 can include multiple terrestrial antennas, multiple satellites, and/or multiple broadcast antennas, for example.

0013The terrestrial antenna 140 is configured to communicate multicast and/or interactive data with the mobile device 110 via a terrestrial communication path, channel, or link, for example, which includes a downlink portion 142 and/or an uplink portion 144. In this example, the downlink portion 142 refers to the portion of the terrestrial communication path in which data or information flows from the terrestrial antenna 140 to the mobile device 110. The terrestrial antenna 140 is thus configured to send, transmit, or transfer data to the mobile device 110 via the downlink portion 142 of the terrestrial communication path, while the mobile device 110 is configured to receive data at downlink portion 142. The uplink portion 144 refers to a portion of the terrestrial communication path in which data or information flows from the mobile device 110 to the terrestrial antenna 140. The mobile device 110 is thus configured to send, transmit, or transfer data to the terrestrial antenna 140 via the uplink portion 144 of the terrestrial communication path, while the terrestrial antenna 140 is configured to receive at uplink portion 144. The terrestrial antenna 140 can be associated with a wireless base station used, for example, in cellular or like communication systems. In some embodiments, the downlink portion 142 of the terrestrial communication path and the uplink portion 144 of the terrestrial communication path operate over the same frequency band. In other embodiments, the downlink portion 142 of the terrestrial communication path operates over a first frequency band and the uplink portion 144 of the terrestrial communication path operates over a second frequency band different from the first frequency band.

0014The terrestrial antenna 140 is configured to communicate with the mobile device 110 via the terrestrial communication path, for example, by using a duplexing scheme such as a TDD scheme, an FDD scheme, and/or a hybrid TDD/FDD scheme. The terrestrial antenna 140 is thus configured to establish and/or operate an asymmetric TDD communication scheme with the mobile device 110 via the terrestrial communication path. An asymmetric TDD communication scheme refers to a TDD communication path, channel, or link, for example, between the terrestrial antenna 140 and the mobile device 110 in which the amount of data flowing in one direction (uplink or downlink) is larger than the amount of data flowing in the opposite direction. For example, in interactive multimedia applications, the amount of data (e.g., video) flowing from the terrestrial antenna 140 to the mobile device 110 is larger than the amount of data (e.g., user selections) flowing from the mobile device 110 to the terrestrial antenna 140. The amount of data flowing in a given direction can be based on a spectrum bandwidth associated with that direction and/or a time interval associated with the flow of data in that direction. An asymmetric TDD communication scheme may provide the asymmetry that is desirable in many next generation services and applications without the need for an auxiliary frequency band to increase capacity in one direction or another.

0015The broadcast antenna 120 is configured to communicate with the mobile device 110 via a broadcast 122. In this example, data flows from the broadcast antenna 120 to the mobile device 110. In one embodiment, the broadcast antenna 120 can be a directional antenna and can be configured such that the broadcast 122 occurs in a particular direction. In another embodiment, the broadcast antenna 120 can be an omni-directional antenna and can be configured such that the broadcast 122 occurs uniformly in every direction.

0016The satellite 130 is configured to communicate multicast and/or interactive data with the mobile device 110 via a satellite communication path, channel, or link, for example, which includes a downlink portion 132 and/or an uplink portion 134. In this example, the downlink portion 132 refers to the portion of the satellite communication path in which data or information flows from the satellite 130 to the mobile device 110. The satellite 130 is thus configured to send, transmit, or transfer data (e.g., video content) to the mobile device 110 via the downlink portion 132 of the satellite communication path, while the mobile device 110 is configured to receive data from the satellite 130 via that downlink portion 132. The uplink portion 134 refers to a portion of the satellite communication path in which data or information flows from the mobile device 110 to the satellite 130. The mobile device 110 is thus configured to send, transmit, or transfer data (e.g., interactive data) to the satellite 130 via the uplink portion 134 of the satellite communication path, while the satellite 130 is configured to receive data from the mobile device 110 via that uplink portion 134. In some embodiments, the downlink portion 132 of the satellite communication path and the upstream portion 134 of the satellite communication path operate over the same frequency band. In other embodiments, the downlink portion 132 of the satellite communication path operates over a first frequency band and the upstream portion 134 of the satellite communication path operates over a second frequency band different from the first frequency band.

0017The satellite 130 is configured to communicate with the mobile device 110 via the satellite communication path, for example, by using a duplexing scheme such as a TDD scheme, an FDD scheme, and/or a hybrid TDD/FDD scheme. The satellite 130 is configured to establish and/or operate an asymmetric TDD communication scheme with the mobile device 110 via the satellite communication path. For example, in interactive travel assistance applications, the amount of data (e.g., navigation data) flowing from the satellite 130 to the mobile device 110 is larger than the amount of data (e.g., user queries) flowing from the mobile device 110 to the satellite 130. The amount of data flowing in a given direction can be based on a spectrum bandwidth associated with that direction and/or a time interval associated with that direction.

0018In some embodiments, the satellite 130 and the terrestrial antenna 140 can be used in a hybrid satellite/terrestrial communication system to communicate with the mobile device 110. For example, the satellite 130 can be configured to communicate with the terrestrial antenna 140 such that data can flow from the satellite 130 to the mobile device 110 via the terrestrial antenna 140. In this example, the satellite 130 can be configured to send data to the terrestrial antenna 140 via a downlink portion of a given satellite communication path (not shown) with the terrestrial antenna 140. The terrestrial antenna 140 can be configured to send the data received from the satellite 130 to the mobile device 110 via the downlink portion 142 of the terrestrial communication path. In another example, the terrestrial antenna 140 can be configured to communicate with the satellite 130 via a network (not shown) and/or a ground station (not shown).

0019The mobile device 110 can include a handheld device, a laptop, and/or an in-vehicle system, for example. The mobile device 110 is configured to communicate with the satellite 130 and/or the terrestrial antenna 140. For example, the mobile device 110 can be configured to communicate with the satellite 130 via an asymmetric TDD communication scheme (e.g., TDD downlink and TDD uplink) over a satellite communication path. In another example, the mobile device 110 can be configured to communicate with the terrestrial antenna 140 via an asymmetric TDD communication scheme (e.g., TDD downlink and TDD uplink) over a terrestrial communication path. The mobile device 110 can also be configured to receive broadcast data from the broadcast antenna 120. The functionality of the mobile device 110 can be software-based (e.g., set of instructions executable at a processor, software code) and/or hardware-based (e.g., circuit system, processor, application-specific integrated circuit (ASIC), field programmable gate array (FPGA)). The mobile device 110 can include a processor and a related processor-readable medium having instructions or computer code thereon for performing various processor-implemented operations. Such processors can be implemented as hardware modules such as embedded microprocessors, microprocessors as part of a computer system, Application-Specific Integrated Circuits ("ASICs"), and Programmable Logic Devices ("PLDs"). Such processors can also be implemented as one or more software modules in programming languages as Java, C++, C, assembly, a hardware description language, or any other suitable programming language.

0020A processor according to some embodiments of the mobile device 110 includes media and computer code (also can be referred to as code) specially designed and constructed for the specific purpose or purposes. Examples of processor-readable media include, but are not limited to: magnetic storage media such as hard disks, floppy disks, and magnetic tape; optical storage media such as Compact Disc/Digital Video Discs ("CD/DVDs"), Compact Disc-Read Only Memories ("CD-ROMs"), and holographic devices; magneto-optical storage media such as optical disks, and read-only memory ("ROM") and random-access memory ("RAM") devices. Examples of computer code include, but are not limited to, micro-code or micro-instructions, machine instructions, such as produced by a compiler, and files containing higher-level instructions that are executed by a computer using an interpreter. For example, an embodiment of the mobile device 110 may be implemented using Java, C++, or other object-oriented programming language and development tools. Additional examples of computer code include, but are not limited to, control signals, encrypted code, and compressed code.

0021In some embodiments, at least a portion of the wireless communication system 100 can be pre-configured to support an asymmetric TDD communication scheme. In other embodiments, at least a portion of the wireless communication system 100 can be dynamically configured (e.g., after deployment) to support an asymmetric TDD communication scheme.

0022<figref idref="f0002">FIG. 2</figref> is a schematic representation showing mobile devices 210, 220, and 230 operating in an area 200, according to embodiments. The mobile device 220 is configured to communicate with a given wireless communication system (not shown), such as the wireless communication system 100 described above with respect to <figref idref="f0001">FIG. 1</figref>. The mobile device 220 can communicate with that wireless communication system via an asymmetric TDD communication scheme. For example, the mobile device 220 can communicate via an uplink portion 224 and a downlink portion 222 of an asymmetric TDD communication scheme associated with a particular frequency band (frequency band 1).

0023The mobile device 210 and the mobile device 230 are each configured to communicate with a wireless communication system (not shown) via a communication path that includes one of multiple communication methods such as an FDD communication scheme, a TDD communication scheme synchronous with the asymmetric TDD communication scheme associated with the mobile device 220, a TDD communication scheme asynchronous with the asymmetric TDD communication scheme associated with the mobile device 220, a temporally-asymmetric TDD communication scheme, or a broadcast, for example. In some embodiments, the mobile device 210 can communicate with its associated wireless communication system via a communication path having an uplink portion 214 and a downlink portion 212. Each of the uplink portion 214 and the downlink portion 212 of the communication path is associated with a frequency band 2. Similarly, the mobile device 230 can communicate with its associated wireless communication system via a communication path having an uplink portion 234 and a downlink portion 232. Each of the uplink portion 234 and downlink portion 2232 is associated with a frequency band 3. In some embodiments, the frequency band 2 and/or the frequency band 3 can include multiple frequency bands or frequency subbands.

0024The frequency bands 1, 2, and 3 can be adjacent (i.e., adjoining or neighboring) frequency bands. For example, frequency band 1 can be adjacent to frequency band 2 and adjacent to frequency band 3. The frequency bands 1, 2, and 3 can be mutually exclusive frequency bands, for example. In some embodiments, the frequency band 1 can be associated with a flexible-use spectrum, for example.

0025The mobile devices 220 and 210 are configured to coexist in the area 200 such that minimal (if any) interference occurs between the asymmetric TDD communication scheme being used by the mobile device 220 (and associated with frequency band 1) and the communication method being used by the mobile device 210 (and associated with frequency band 2). Similarly, the mobile devices 220 and 230 are configured to coexist in the area 200 such that minimal (if any) interference occurs between the asymmetric TDD communication scheme being used by the mobile device 220 (and associated with frequency band 1) and the communication method being used by the mobile device 230 (and associated with frequency band 3). The size of the area 200 may be associated with the minimum distance between the mobile device 220 and the mobile device 210, and/or the minimum distance between the mobile device 220 and the mobile device 230 such that the mobile devices 210, 220, and/or 230 can effectively operate (i.e., coexist) without interfering with each other.

0026<figref idref="f0003">FIG. 3</figref> is a diagram illustrating an asymmetric TDD scheme in an advanced wireless services (AWS) spectrum, according to an example. The wireless spectrum 300 is a portion of the radio frequency spectrum that includes a portion 310 (AWS-1 F Block), a portion 320 (AWS-3), a portion 330 (J Block), a portion 340 (MSS-1), and a portion 350 (MSS-2). The AWS-1 and AWS-3 are each a portion of an AWS frequency band plan associated with next generation voice and data services and applications. The AWS-1 includes multiple frequency blocks, such as blocks A, B, C, D, E, and F. Each frequency block has an associated mobile frequency band and base frequency band. The portion 310 of the wireless spectrum 300 is associated with the base frequency band of the AWS-1 F block of the AWS frequency band plan. The AWS-1 F block includes frequencies from about 1745 megahertz (MHz) to about 2155 MHz and is used for downlink communication via a downlink portion 312 of a communication path between, for example, a base station (e.g., terrestrial antenna) and a mobile device. The AWS-1 F block is shown as being adjacent to the AWS-3 portion of the AWS frequency band plan.

0027The J block is a frequency band being proposed for use with an AWS-2 portion (not shown) of the AWS frequency band plan. The J block includes frequencies from about 2175 MHz to about 2180 MHz. The J block is shown as being adjacent to the AWS-3 portion of the AWS frequency band plan and adjacent to the MSS-1 portion of the wireless spectrum 300. The J block is used for downlink communication via a downlink portion 332 of a communication path between, for example, a terrestrial antenna and a mobile device.

0028Each of the MSS-1 and MSS-2 is a portion of the wireless spectrum 300 that is used for mobile satellite services systems. The MSS-1 portion of the wireless spectrum 300 is associated with a frequency band that includes frequencies from about 2180 MHz to about 2190 MHz. The MSS-2 portion of the wireless spectrum 300 is associated with a frequency band that includes frequencies from about 2190 MHz to about 2200 MHz. Each of the MSS-1 and MSS-2 portions of the wireless spectrum 300 can be used in hybrid satellite/terrestrial wireless communication systems, for example. The MSS-1 portion of the wireless spectrum 300 is used for downlink communication via a downlink portion 342 of a communication path between, for example, a base station or a satellite, and a mobile device. The MSS-2 portion of the wireless spectrum 300 is used for downlink communication via a downlink portion 352 of a communication path between, for example, a base station or a satellite, and a mobile device. The MSS-1 portion of the wireless spectrum 300 is shown as being adjacent to the J block and adjacent to the MSS-2 portion of the wireless spectrum 300. The MSS-2 portion of the wireless spectrum 300 is shown as being adjacent to the MSS-1 portion of the wireless spectrum 300.

0029The AWS-3 portion of the AWS frequency band plan is being proposed for flexible-use spectrum services and applications. The AWS-3 portion of the AWS frequency band plan can be used for services and applications that use different communication methods. For example, the AWS-3 portion of the AWS frequency band plan can be used for an asymmetric TDD communication scheme via a communication path between, for example, a base station or a satellite, and a mobile device. The communication path associated with the asymmetric TDD communication scheme includes a downlink portion 322 and an uplink portion 324. Because the AWS-3 portion of the AWS frequency band plan is adjacent to the AWS-1 F block and the J block, it is desirable that the downlink portion 322 and the uplink portion 324 be configured such that minimal (if any) interference occurs between the frequency band associated with the AWS-3 portion of the AWS frequency band plan and the frequency bands associated with the AWS-1 F block and the J block.

0030<figref idref="f0004">FIG. 4</figref> is a diagram illustrating aspects of an asymmetric TDD communication scheme for use in the AWS-3 portion of the wireless spectrum 300 described above with respect to <figref idref="f0003">FIG. 3</figref>, according to an example. The asymmetric TDD communication scheme allocates or assigns frequencies from about 2160 MHz to about 2170 MHz to a first portion 410 of a frequency band 440 and associated with a frequency band 430. The asymmetric TDD communication scheme also allocates or assigns frequencies from about 2155 MHz to about 2175 MHz to a second portion 420 associated with the frequency band 440. The first portion 410 is different from the second portion 420 of the asymmetric TDD communication scheme. For example, a spectrum bandwidth associated with the frequency band 440 of the second portion 420 is larger than a spectrum bandwidth associated with the frequency band 420 of the first portion 410.

0031The first portion 410 is associated with an uplink portion or uplink communication portion (↑) of the asymmetric TDD communication scheme. The first portion 410 has an uplink time interval or uplink time slot, TU, associated with the interval between time instances t1 and t2. The second portion 420 is associated with a downlink portion or downlink communication portion (↓) of the asymmetric TDD communication scheme. The second portion 420 has a downlink time interval or downlink time slot, TD, associated with the interval between time instances t0 and t1. In some examples, the interval between time instances t1 and t2 can have substantially the same duration as the interval between time instances t0 and t1. In other examples, the interval between time instances t1 and t2 can have a different duration than the duration of the interval between time instances t0 and t1.

0032Asymmetric data flow in the TDD communication scheme occurs when a time-bandwidth product associated with the first portion 410 is different from a time-bandwidth product associated with the second portion 420. The time-bandwidth product associated with the first portion 410 refers to the product of TU and the spectrum bandwidth associated with the frequency band 430. The time-bandwidth product associated with the first portion 410 is proportional to the amount of data that can flow in the direction of the first portion 410. The time-bandwidth product associated with the second portion 420 refers to the product of TD and the spectrum bandwidth associated with the frequency band 440. The time-bandwidth product associated with the second portion 420 is proportional to the amount of data that can flow in the direction of the second portion 420. When TU and TD are substantially the same, the amount of data flow in a given direction is proportional to the spectrum bandwidth of the frequency band associated with that direction. In this example, when TU and TD are substantially the same, the amount of data flow is larger in the downlink direction associated with the second portion 420 of the asymmetric TDD communication scheme than in the uplink direction associated with the first portion 410 of the asymmetric TDD communication scheme.

0033The asymmetric TDD communication scheme also includes an uplink guard band 450 that separates the first portion 410 from a frequency band (e.g., AWS-1 F block) that is adjacent to the 2155 MHz frequency of the frequency band 440. The asymmetric TDD communication scheme further includes an uplink guard band 460 that separates the first portion 410 from a frequency band (e.g., J block) that is adjacent to the 2175 MHz frequency of the frequency band 440. The uplink guard bands 450 and 460 are used to minimize or reduce the interference that can occur between the downlink portions of the adjacent frequency bands and the uplink portion of the asymmetric TDD communication scheme described in <figref idref="f0004">FIG. 4</figref>.

0034<figref idref="f0005">FIGS. 5A-5B</figref> are each a diagram depicting the time and frequency aspects of a TDD scheme with adjacent FDD schemes, according to examples. <figref idref="f0005">FIG. 5A</figref> shows a diagram 500 that illustrates a first frequency band 504 associated with a TDD communication path. The TDD communication path can be symmetric or asymmetric. In some examples, it may be desirable that the TDD communication path be asymmetric to be used in next generation applications and services. The diagram 500 also illustrates a second frequency band 502 associated with an uplink portion of an FDD communication path and a third frequency band 506 associated with a downlink portion of an FDD communication path. The second frequency band 502 and the third frequency band 506 need not (but can) be paired FDD frequency bands associated with the same FDD communication path.

0035The first frequency band 504 is associated with a spectrum bandwidth that includes frequencies in the range f1 to f4. The second frequency band 502 is associated with a spectrum bandwidth that includes frequencies in the range f0 to f1. The third frequency bandwidth 506 is associated with a spectrum bandwidth that includes frequencies in the range f4 to f5. The first frequency band 504 is adjacent to the second frequency band 502 (e.g., at f1). The first frequency band 504 is adjacent to the third frequency band 506 (e.g., at f4). The first frequency band 504, the second frequency band 502, and the third frequency band 506 can be mutually exclusive frequency bands. In some examples, the first frequency band 504, the second frequency band 502, and the third frequency band 506 are wireless frequency bands.

0036The first frequency band 504 includes a first portion 510 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f3. The first frequency band 504 includes a second portion 512 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f4. The first portion 510 of the first frequency band 504 is different from the second portion 512 of the first frequency band 504 and overlaps the second portion 512 of the first frequency band 504. The spectrum bandwidth associated with the first portion 510 of the first frequency band 504 can be different (or the same) from the spectrum bandwidth associated with the second portion 512 of the first frequency band 504.

0037The first portion 510 of the first frequency band 504 is associated with an uplink portion or uplink communication portion of the TDD communication path. The first portion 510 has an uplink time interval or uplink time slot, TU, associated with the interval between time instances t1 and t2. The second portion 512 of the first frequency band 504 is associated with a downlink portion or downlink communication portion of the TDD communication path. The second portion 512 has a downlink time interval or downlink time slot, TD, associated with the interval between time instances t0 and t1.

0038When the time-bandwidth product associated with the first portion 510 of the first frequency band 504 is substantially the same as the time-bandwidth product associated with the second portion 512 of the first frequency band 504, the TDD communication path associated with the first frequency band 504 operates as a symmetric TDD communication path. The time-bandwidth product associated with the first portion 510 of the first frequency band 504 refers to the product of TU and the spectrum bandwidth between frequencies f1 and f3. The time-bandwidth product associated with the second portion 512 of the first frequency band 504 refers to the product of TD and the spectrum bandwidth between frequencies f2 and f4. When the time-bandwidth product associated with the first portion 510 of the first frequency band 504 is different from the time-bandwidth product associated with the second portion 512 of the first frequency band 504, the TDD communication path associated with the first frequency band 504 operates as an asymmetric TDD communication path.

0039<figref idref="f0005">FIG. 5A</figref> shows the first portion 510 of the first frequency band 504 as being adjacent to the second frequency band 502 and separate from the third frequency band 506 by an uplink guard band 516. Because the first portion 510 of the first frequency band 504 and the uplink portion of the FDD communication path associated with the second frequency band 502 are both either transmitting or receiving signals in a same direction, no guard band may be desirable between the first portion 510 of the first frequency band 504 and the second frequency band 502 given that minimal (if any) interference occurs. On the other hand, the first portion 510 of the first frequency band 504 and the downlink portion of the FDD communication link associated with the third frequency band 506 may need a guard band (e.g., uplink guard band 516) because they are either transmitting or receiving signals in opposite directions, which may result in significant levels of interference.

0040Similarly, the second portion 512 of the first frequency band 504 is shown as being adjacent to the third frequency band 506 and separate from the second frequency band 502 by a downlink guard band 514. Because the second portion 512 of the first frequency band 504 and the downlink portion of the FDD communication path associated with the third frequency band 506 are both either transmitting or receiving signals in a same direction, no guard band may be desirable given that minimal (if any) interference occurs between the second portion 512 of the first frequency band 504 and the third frequency band 506. On the other hand, the second portion 512 of the first frequency band 504 and the uplink portion of the FDD communication path associated with the second frequency band 502 may need a guard band (e.g., downlink guard band 514) because they are either transmitting or receiving signals in opposite directions, which may result in significant levels of interference. The uplink guard band 516 and the downlink guard band 514 need not (but can) have the same spectrum bandwidth.

0041<figref idref="f0005">FIG. 5B</figref> shows a diagram 520 that illustrates a first frequency band 524 associated with a TDD communication path. The diagram 520 also illustrates a second frequency band 522 associated with a downlink portion of an FDD communication path and a third frequency band 526 associated with an uplink portion of an FDD communication path. The second frequency band 522 and the third frequency band 526 need not (but can) be paired FDD frequency bands associated with the same FDD communication path.

0042The first frequency band 524, the second frequency band 522, and the third frequency band 526 are similar to the first frequency band 504, the second frequency band 502, and the third frequency band 506 described above with respect to <figref idref="f0005">FIG. 5A</figref>. The first frequency band 524 includes a first portion 530 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f4. The first frequency band 524 includes a second portion 532 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f3. The first portion 530 of the first frequency band 524 is different from the second portion 532 of the first frequency band 524 and overlaps the second portion 532 of the first frequency band 524. The spectrum bandwidth associated with the first portion 530 of the first frequency band 524 can be different (or the same) from the spectrum bandwidth associated with the second portion 532 of the first frequency band 524.

0043The first portion 530 of the first frequency band 524 is associated with an uplink portion of the TDD communication path and has an associated uplink time slot, TU, described above with respect to <figref idref="f0005">FIG. 5A</figref>. The second portion 532 of the first frequency band 524 is associated with a downlink portion of the TDD communication path and has an associated downlink time slot, TD, also described above with respect to <figref idref="f0005">FIG. 5A</figref>. The TDD communication path associated with the first frequency 524 can be symmetric or asymmetric based on the time-bandwidth product associated with the first portion 530 of the first frequency band 524 and the time-bandwidth product associated with the second portion 532 of the first frequency band 524.

0044<figref idref="f0005">FIG. 5B</figref> shows the first portion 530 of the first frequency band 524 as being adjacent to the third frequency band 526 and separate from the second frequency band 524 by an uplink guard band 534. The first portion 530 of the first frequency band 524 and the downlink portion of the FDD communication path associated with the second frequency band 524 may need a guard band because they are either transmitting or receiving signals in opposite directions, which may result in significant levels of interference.

0045Similarly, the second portion 532 of the first frequency band 524 is shown as being adjacent to the second frequency band 522 and separate from the third frequency band 526 by a downlink guard band 536. The second portion 532 of the first frequency band 524 and the uplink portion of the FDD communication path associated with the third frequency band 526 may need a guard band because they are either transmitting or receiving signals in opposite directions, which may result in significant levels of interference. The uplink guard band 534 and the downlink guard band 536 need not (but can) have the same spectrum bandwidth.

0046<figref idref="f0006">FIGS. 6A-6B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD schemes, according to other embodiments. <figref idref="f0006">FIG. 6A</figref> shows a diagram 600 that illustrates a first frequency band 604 associated with a TDD communication path. The diagram 600 also illustrates a second frequency band 602 associated with an uplink portion of an FDD communication path and a third frequency band 606 associated with an uplink portion of an FDD communication path different from the FDD communication path associated with the second frequency band 602.

0047The first frequency band 604 is associated with a spectrum bandwidth that includes frequencies in the range f1 to f4. The second frequency band 602 is associated with a spectrum bandwidth that includes frequencies in the range f0 to f1. The third frequency bandwidth 606 is associated with a spectrum bandwidth that includes frequencies in the range f4 to f5. The first frequency band 604 is adjacent to the second frequency band 602 (e.g., at f1). The first frequency band 604 is adjacent to the third frequency band 606 (e.g., at f4). The first frequency band 604, the second frequency band 602, and the third frequency band 606 can be mutually exclusive frequency bands. In some embodiments, the first frequency band 604, the second frequency band 602, and the third frequency band 606 are wireless frequency bands.

0048The first frequency band 604 includes a first portion 610 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f4. The first frequency band 604 includes a second portion 612 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f3. The first portion 610 of the first frequency band 604 is different from the second portion 612 of the first frequency band 604 and overlaps the second portion 612 of the first frequency band 604. The spectrum bandwidth associated with the first portion 610 of the first frequency band 604 is different from the spectrum bandwidth associated with the second portion 612 of the first frequency band 604.

0049The first portion 610 of the first frequency band 604 is associated with an uplink portion or uplink communication portion of the TDD communication path. The first portion 610 has an uplink time interval or uplink time slot, TU, associated with the interval between time instances t1 and t2. The second portion 612 of the first frequency band 604 is associated with a downlink portion or downlink communication portion of the TDD communication path. The second portion 612 has a downlink time interval or downlink time slot, TD, associated with the interval between time instances t0 and t1.

0050When the time-bandwidth product associated with the first portion 610 of the first frequency band 604 is substantially the same as the time-bandwidth product associated with the second portion 612 of the first frequency band 604, the TDD communication path associated with the first frequency band 604 operates as a symmetric TDD communication path. When the time-bandwidth product associated with the first portion 610 of the first frequency band 604 is different from the time-bandwidth product associated with the second portion 612 of the first frequency band 604, the TDD communication path associated with the first frequency band 604 operates as an asymmetric TDD communication path. Because the spectrum bandwidth associated with the first portion 610 of the first frequency band 604 is different from the spectrum bandwidth associated with the second portion 612 of the first frequency band 604, when the time intervals associated with the time slots TU and TD are the same, the TDD communication path associated with the first frequency band 604 operates as an asymmetric TDD communication path.

0051<figref idref="f0006">FIG. 6A</figref> shows the first portion 610 of the first frequency band 604 as being adjacent to the second frequency band 602 and to the third frequency band 606. Because the first portion 610 of the first frequency band 604, the uplink portion of the FDD communication path associated with the second frequency band 602, and the uplink portion of the FDD communication path associated with the second frequency band 606 are either transmitting or receiving signals in a same direction, no guard band is used given that minimal (if any) interference may occur.

0052The second portion 612 of the first frequency band 604 is shown as being separated from the second frequency band 602 by a downlink guard band 614 and separate from the third frequency band 606 by a downlink guard band 616. The downlink guard bands 614 and 616 are used because the second portion 612 of the first frequency band 604, the uplink portion of the FDD communication path associated with the second frequency band 602, and the uplink portion of the FDD communication path associated with the second frequency band 606 are either transmitting or receiving signals in opposite directions, which may result in significant levels of interference. The downlink guard band 614 and 616 have the same spectrum bandwidth.

0053<figref idref="f0006">FIG. 6B</figref> shows a diagram 620 that illustrates a first frequency band 624 associated with a TDD communication path. The diagram 620 also illustrates a second frequency band 622 associated with a downlink portion of an FDD communication path and a third frequency band 626 associated with a downlink portion of an FDD communication path different from the FDD communication path associated with the second frequency band 622.

0054The first frequency band 624, the second frequency band 622, and the third frequency band 626 are similar to the first frequency band 604, the second frequency band 602, and the third frequency band 606 described above with respect to <figref idref="f0006">FIG. 6A</figref>. The first frequency band 624 includes a first portion 630 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f3. The first frequency band 624 includes a second portion 632 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f4. The first portion 630 of the first frequency band 624 is different from the second portion 632 of the first frequency band 624 and overlaps the second portion 632 of the first frequency band 624. The spectrum bandwidth associated with the first portion 630 of the first frequency band 624 is different from the spectrum bandwidth associated with the second portion 632 of the first frequency band 624.

0055The first portion 630 of the first frequency band 624 is associated with an uplink portion of the TDD communication path and has an associated uplink time slot, TU, described above with respect to <figref idref="f0006">FIG. 6A</figref>. The second portion 632 of the first frequency band 624 is associated with a downlink portion of the TDD communication path and has an associated downlink time slot, TD, also described above with respect to <figref idref="f0006">FIG. 6A</figref>. The TDD communication path associated with the first frequency 624 can be symmetric or asymmetric based on the time-bandwidth product associated with the first portion 630 of the first frequency band 624 and the time-bandwidth product associated with the second portion 632 of the first frequency band 624. Because the spectrum bandwidth associated with the first portion 630 of the first frequency band 624 is different from the spectrum bandwidth associated with the second portion 632 of the first frequency band 624, when the time intervals associated with the time slots TU and TD are the same, the TDD communication path associated with the first frequency band 624 operates as an asymmetric TDD communication path.

0056<figref idref="f0006">FIG. 6B</figref> shows the first portion 630 of the first frequency band 624 as being separated from the second frequency band 622 by an uplink guard band 634 and separate from the third frequency band 626 by an uplink guard band 636. The uplink guard bands 634 and 636 have the same spectrum bandwidth. The second portion 632 of the first frequency band 624 is shown as being adjacent to the second frequency band 622 and adjacent to the third frequency band 626.

0057<figref idref="f0007">FIGS. 7A-7B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD and synchronous TDD schemes, according to examples. <figref idref="f0007">FIG. 7A</figref> shows a diagram 700 that illustrates a first frequency band 704 associated with a TDD communication path. The diagram 700 illustrates a second frequency band 702 associated with a TDD communication path that is synchronized to the TDD communication path in the first frequency band 704. The diagram 700 also illustrates a third frequency band 706 associated with an uplink portion of an FDD communication path.

0058The first frequency band 704 is associated with a spectrum bandwidth that includes frequencies in the range f1 to f3. The second frequency band 702 is associated with a spectrum bandwidth that includes frequencies in the range f0 to f1. The third frequency bandwidth 706 is associated with a spectrum bandwidth than includes frequencies between frequencies f3 and f4. The first frequency band 704 is adjacent to the second frequency band 702 (e.g., at f1). The first frequency band 704 is also adjacent to the third frequency band 706 (e.g., at f3). The first frequency band 704, the second frequency band 702, and the third frequency band 706 can be mutually exclusive frequency bands. In some examples, the first frequency band 704, the second frequency band 702, and the third frequency band 706 are wireless frequency bands.

0059The first frequency band 704 includes a first portion 710 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f3. The first frequency band 704 includes a second portion 712 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f2. The first portion 710 of the first frequency band 704 is different from the second portion 712 of the first frequency band 704 and overlaps the second portion 712 of the first frequency band 704. The spectrum bandwidth associated with the first portion 710 of the first frequency band 704 is different from the spectrum bandwidth associated with the second portion 712 of the first frequency band 704.

0060The first portion 710 of the first frequency band 704 is associated with an uplink portion or uplink communication portion of the TDD communication path. The first portion 710 has an uplink time interval or uplink time slot, TU, associated with the interval between time instances t1 and t2. The second portion 712 of the first frequency band 704 is associated with a downlink portion or downlink communication portion of the TDD communication path. The second portion 712 has a downlink time interval or downlink time slot, TD, associated with the interval between time instances t0 and t1.

0061When the time-bandwidth product associated with the first portion 710 of the first frequency band 704 is substantially the same as the time-bandwidth product associated with the second portion 712 of the first frequency band 704, the TDD communication path associated with the first frequency band 704 operates as a symmetric TDD communication path. When the time-bandwidth product associated with the first portion 710 of the first frequency band 704 is different from the time-bandwidth product associated with the second portion 712 of the first frequency band 704, the TDD communication path associated with the first frequency band 704 operates as an asymmetric TDD communication path.

0062<figref idref="f0007">FIG. 7A</figref> shows the first portion 710 of the first frequency band 704 as being adjacent to the second frequency band 702. The synchronized or synchronous TDD communication path in the second frequency band 702 has an uplink portion (not shown) and a downlink portion (not shown) that operate at substantially the same time intervals (i.e., synchronously) as the time intervals TU and TD of the first portion 710 and the second portion 712 of the first frequency band 704, respectively. As a result, the first portion 710 of the first frequency band 704 and the synchronous TDD communication path associated with the second frequency band 702 are both either transmitting or receiving signals in a same direction and no guard band may be desirable given that minimal (if any) interference occurs between the first portion 710 of the first frequency band 704 and the second frequency band 702.

0063The first portion 710 of the first frequency band 704 is also adjacent to the third frequency band 706. The first portion 710 of the first frequency band 704 and the uplink portion of the FDD communication path associated with the third frequency band 706 need no guard band because they are either transmitting or receiving signals in the same direction with minimal or no interference between the frequency bands.

0064The second portion 712 of the first frequency band 704 is shown as being adjacent to the second frequency band 702 and separate from the third frequency band 706 by a downlink guard band 714. No guard band is needed between the second portion 712 of the first frequency band 704 and the synchronous TDD communication path associated with the second frequency band 702. The downlink guard band 704, however, is needed because the second portion 712 of the first frequency band 704 and the uplink portion of the FDD communication path associated with the third frequency band 706 are transmitting or receiving signals in opposite directions.

0065<figref idref="f0007">FIG. 7B</figref> shows a diagram 720 that illustrates a first frequency band 724 associated with a TDD communication path. The diagram 720 also illustrates a second frequency band 722 associated with an uplink portion of an FDD communication path and a third frequency band 726 associated with a synchronous TDD communication path.

0066The first frequency band 724, the second frequency band 722, and the third frequency band 726 are similar to the first frequency band 704, the second frequency band 702, and the third frequency band 706 described above with respect to <figref idref="f0007">FIG. 7A</figref>. The first frequency band 724 includes a first portion 730 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f3. The first frequency band 724 includes a second portion 732 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f3. The first portion 730 of the first frequency band 724 is different from the second portion 732 of the first frequency band 724 and overlaps the second portion 732 of the first frequency band 724. The spectrum bandwidth associated with the first portion 730 of the first frequency band 724 is different from the spectrum bandwidth associated with the second portion 732 of the first frequency band 724.

0067The first portion 730 of the first frequency band 724 is associated with an uplink portion of the TDD communication path and has an associated uplink time slot, TU, described above with respect to <figref idref="f0007">FIG. 7A</figref>. The second portion 732 of the first frequency band 724 is associated with a downlink portion of the TDD communication path and has an associated downlink time slot, TD, also described above with respect to <figref idref="f0007">FIG. 7A</figref>. The TDD communication path associated with the first frequency 724 can be symmetric or asymmetric based on the time-bandwidth product associated with the first portion 730 of the first frequency band 724 and the time-bandwidth product associated with the second portion 732 of the first frequency band 724.

0068<figref idref="f0007">FIG. 7B</figref> shows the first portion 730 of the first frequency band 724 as being adjacent to the second frequency band 722 and adjacent to the third frequency band 726. The first portion 730 of the first frequency band 724 and the uplink portion of the FDD communication link associated with the second frequency band 722 need no guard band because they are either transmitting or receiving signals in the same direction with minimal (if any) interference. Similarly, the first portion 730 of the first frequency band 724 and the synchronous TDD communication path associated with the third frequency band 726 need no guard band because they are synchronously transmitting or receiving signals in the same direction.

0069The second portion 732 of the first frequency band 724 is shown as being separated from the second frequency band 722 by a downlink guard band 734 and adjacent to the third frequency band 726. The second portion 732 of the first frequency band 724 and the uplink portion of the FDD communication path associated with the second frequency band 722 may need a guard band because they are either transmitting or receiving signals in opposite directions and are likely to interfere with each other. The second portion 732 of the first frequency band 724 and the synchronous TDD communication path associated with the third frequency band 726 do not need a guard band because they are synchronously transmitting or receiving signals in the same direction

0070<figref idref="f0008">FIGS. 7C-7D</figref> are each a diagram depicting time and frequency aspects of an asymmetric TDD scheme with adjacent FDD and synchronous TDD schemes, according other examples. <figref idref="f0008">FIG. 7C</figref> shows a diagram 740 that illustrates a first frequency band 744 associated with a TDD communication path that can be symmetric or asymmetric. The diagram 740 also illustrates a second frequency band 742 associated with a TDD communication path that is synchronized to the TDD communication path in the first frequency band 744. The diagram 740 also illustrates a third frequency band 706 associated with a downlink portion of an FDD communication path.

0071The first frequency band 744 is associated with a spectrum bandwidth that includes frequencies in the range f1 to f3. The second frequency band 742 is associated with a spectrum bandwidth that includes frequencies in the range f0 to f1. The third frequency bandwidth 746 is associated with a spectrum bandwidth that includes frequencies in the range f3 to f4. The first frequency band 744 is adjacent to the second frequency band 742 (e.g., at f1). The first frequency band 744 is adjacent to the third frequency band 746 (e.g., at f3). The first frequency band 744, the second frequency band 742, and the third frequency band 746 can be mutually exclusive frequency bands. In some examples, the first frequency band 744, the second frequency band 742, and the third frequency band 746 are wireless frequency bands.

0072The first frequency band 744 includes a first portion 750 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f2. The first frequency band 744 includes a second portion 752 that has allocated or assigned a spectrum bandwidth including frequencies between frequencies f1 and f3. The first portion 750 of the first frequency band 744 is different from the second portion 752 of the first frequency band 744 and overlaps the second portion 752 of the first frequency band 744. The spectrum bandwidth associated with the first portion 750 of the first frequency band 744 is different from the spectrum bandwidth associated with the second portion 752 of the first frequency band 744.

0073The first portion 750 of the first frequency band 744 is associated with an uplink portion or uplink communication portion of the TDD communication path. The first portion 750 has an uplink time interval or uplink time slot, TU, associated with the interval between time instances t1 and t2. The second portion 752 of the first frequency band 744 is associated with a downlink portion or downlink communication portion of the TDD communication path. The second portion 752 has a downlink time interval or downlink time slot, TD, associated with the interval between time instances t0 and t1.

0074When the time-bandwidth product associated with the first portion 750 of the first frequency band 744 is substantially the same as the time-bandwidth product associated with the second portion 752 of the first frequency band 744, the TDD communication path associated with the first frequency band 744 operates as a symmetric TDD communication path. When the time-bandwidth product associated with the first portion 750 of the first frequency band 744 is different from the time-bandwidth product associated with the second portion 752 of the first frequency band 744, the TDD communication path associated with the first frequency band 744 operates as an asymmetric TDD communication path.

0075<figref idref="f0008">FIG. 7C</figref> shows the first portion 750 of the first frequency band 744 as being adjacent to the second frequency band 742. The synchronized or synchronous TDD communication path in the second frequency band 742 has an uplink portion (not shown) and a downlink portion (not shown) that operate at substantially the same time intervals (i.e., synchronously) as the time intervals TU and TD of the first portion 750 and the second portion 752 of the first frequency band 744, respectively. As a result, the first portion 750 of the first frequency band 744 and the synchronous TDD communication path associated with the second frequency band 742 are both either transmitting or receiving signals in a same direction and no guard band may be desirable given that minimal (if any) interference occurs between the first portion 750 of the first frequency band 744 and the second frequency band 742.

0076The first portion 750 of the first frequency band 744 is separate from the third frequency band 746 by an uplink guard band 754 because the first portion 750 of the first frequency band 744 and the FDD communication path associated with third frequency band 746 are transmitting or receiving signals in the opposite directions. The second portion 752 of the first frequency band 744 is shown as being adjacent to the second frequency band 742 and adjacent to the third frequency band 746.

0077<figref idref="f0008">FIG. 7D</figref> shows a diagram 760 that illustrates a first frequency band 764 associated with a TDD communication path. The diagram 760 also illustrates a second frequency band 762 associated with a downlink portion of an FDD communication path and a third frequency band 766 associated with a synchronous TDD communication path.

0078The first frequency band 764, the second frequency band 762, and the third frequency band 766 are similar to the first frequency band 744, the second frequency band 742, and the third frequency band 746 described above with respect to <figref idref="f0008">FIG. 7C</figref>. The first frequency band 764 includes a first portion 770 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f3. The first frequency band 764 includes a second portion 772 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f3. The first portion 770 of the first frequency band 764 is different from the second portion 772 of the first frequency band 764 and overlaps the second portion 772 of the first frequency band 764. The spectrum bandwidth associated with the first portion 770 of the first frequency band 764 is different from the spectrum bandwidth associated with the second portion 772 of the first frequency band 764.

0079The first portion 770 of the first frequency band 764 is associated with an uplink portion of the TDD communication path and has an associated uplink time slot, TU, described above with respect to <figref idref="f0008">FIG. 7C</figref>. The second portion 772 of the first frequency band 764 is associated with a downlink portion of the TDD communication path and has an associated downlink time slot, TD, also described above with respect to <figref idref="f0008">FIG. 7C</figref>. The TDD communication path associated with the first frequency band 764 can be symmetric or asymmetric based on the time-bandwidth product associated with the first portion 770 of the first frequency band 764 and the time-bandwidth product associated with the second portion 772 of the first frequency band 764.

0080<figref idref="f0008">FIG. 7D</figref> shows the first portion 770 of the first frequency band 764 as being separated from the second frequency band 762 by an uplink guard band 774. The first portion 770 of the first frequency band 764 is adjacent to the third frequency band 766. The second portion 772 of the first frequency band 764 is shown as being adjacent to the second frequency band 762 and adjacent to the third frequency band 766.

0081<figref idref="f0009">FIGS. 8A-8B</figref> are diagrams each depicting time and frequency aspects of a TDD scheme with adjacent synchronous TDD and asynchronous TDD schemes, according to examples. <figref idref="f0009">FIG. 8A</figref> shows a diagram 800 that illustrates a first frequency band 804 associated with a TDD communication path. The diagram 800 illustrates a second frequency band 802 associated with a TDD communication path that is asynchronous with the TDD communication path in the first frequency band 804. The diagram 800 also illustrates a third frequency band 806 associated with a TDD communication path that is synchronous with the TDD communication path in the first frequency band 804.

0082The first frequency band 804 is associated with a spectrum bandwidth that includes frequencies in the range f1 to f3. The second frequency band 802 is associated with a spectrum bandwidth that includes frequencies in the range f0 to f1. The third frequency bandwidth 806 is associated with a spectrum bandwidth that includes frequencies in the range f3 to f4. The first frequency band 804 is adjacent to the second frequency band 802 (e.g., at f1). The first frequency band 804 is adjacent to the third frequency band 806 (e.g., at f3). The first frequency band 804, the second frequency band 802, and the third frequency band 806 can be mutually exclusive frequency bands. In some examples, the first frequency band 804, the second frequency band 802, and the third frequency band 806 are wireless frequency bands.

0083In this example, the first frequency band 804 includes a first portion 810 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f3. The first frequency band 804 includes a second portion 812, which is also shown as being associated with the spectrum bandwidth that includes frequencies in the range f2 to f3. The spectrum bandwidth associated with the first portion 810 of the first frequency band 804, however, need not be the same as the spectrum bandwidth associated with the second portion 812 of the first frequency band 804.

0084The first portion 810 of the first frequency band 804 is associated with an uplink portion or uplink communication portion of the TDD communication path. The first portion 810 has an uplink time interval or uplink time slot, TU, associated with the interval between time instances t3 and t5. The second portion 812 of the first frequency band 804 is associated with a downlink portion or downlink communication portion of the TDD communication path. The second portion 812 has a downlink time interval or downlink time slot, TD, associated with the interval between time instances t1 and t3.

0085When the time-bandwidth product associated with the first portion 810 of the first frequency band 804 is substantially the same as the time-bandwidth product associated with the second portion 812 of the first frequency band 804, the TDD communication path associated with the first frequency band 804 operates as a symmetric TDD communication path. When the time-bandwidth product associated with the first portion 810 of the first frequency band 804 is different from the time-bandwidth product associated with the second portion 812 of the first frequency band 844, the TDD communication path associated with the first frequency band 844 operates as an asymmetric TDD communication path.

0086<figref idref="f0009">FIG. 8A</figref> shows the first portion 810 of the first frequency band 804 as being adjacent to the third frequency band 806. The synchronized or synchronous TDD communication path in the third frequency band 806 has an uplink portion (not shown) and a downlink portion (not shown) that operate at substantially the same time intervals (i.e., synchronously) as the time intervals TU and TD of the first portion 810 and the second portion 812 of the first frequency band 804, respectively. As a result, the first portion 810 of the first frequency band 804 and the synchronous TDD communication path associated with the third frequency band 806 are both either transmitting or receiving signals in a same direction and no guard band may be desirable.

0087The first portion 810 of the first frequency band 804 is separate from the second frequency band 802 by an uplink guard band 814 because the first portion 810 of the first frequency band 804 and the asynchronous TDD communication path associated with second frequency band 802 are offset in time. For example, an uplink portion 820 of the asynchronous TDD communication path associated with the second frequency band 802 has an uplink time slot or time interval between time instances t2 and t4. The uplink time slot associated with the uplink portion 820 of the second frequency band 802 is temporally offset or misaligned with the uplink time slot, TU, associated with the first portion 810 of the first frequency band 804. This temporal offset can result in interference between the second frequency band 802 and the first frequency band 804 as at least a portion of the uplink portion 820 of the second frequency band 802 occurs during the second portion 812 of the first frequency band 804.

0088The second portion 812 of the first frequency band 804 is shown as being adjacent to the third frequency band 806. The second portion 812 of the first frequency band 804 and the synchronous TDD communication path associated with the third frequency band 806 are both either transmitting or receiving signals in a same direction and no guard band may be desirable. The second portion 812 of the first frequency band 804 is separate from the second frequency band 802 by a downlink guard band 816 because the second portion 812 of the first frequency band 804 and the asynchronous TDD communication path associated with second frequency band 802 are offset in time. For example, a downlink portion 822 of the asynchronous TDD communication path associated with the second frequency band 802 has a downlink time slot or time interval between time instances t0 and t2. The downlink time slot associated with the downlink portion 822 of the second frequency band 802 is temporally offset or misaligned with the downlink time slot, TD, associated with the second portion 812 of the first frequency band 804. This temporal offset can result in interference between the second frequency band 802 and the first frequency band 804.

0089<figref idref="f0009">FIG. 8B</figref> shows a diagram 840 that illustrates a first frequency band 844 associated with a TDD communication path. The diagram 840 also illustrates a second frequency band 842 associated with an asynchronous TDD communication path and a third frequency band 846 associated with a synchronous TDD communication path.

0090The first frequency band 844, the second frequency band 842, and the third frequency band 846 are similar to the first frequency band 804, the second frequency band 802, and the third frequency band 806 described above with respect to <figref idref="f0009">FIG. 8A</figref>. A first portion 850 of the first frequency band 844 is similar to the first portion 810 of the first frequency band 804 described above with respect to <figref idref="f0009">FIG. 8A</figref>. A second portion 852 of the first frequency band 844 is similar to the second portion 812 of the first frequency band 804 described above with respect to <figref idref="f0009">FIG. 8A</figref>.

0091<figref idref="f0009">FIG. 8B</figref> shows the first portion 850 of the first frequency band 844 and the second portion 852 of the first frequency band as being adjacent to the third frequency band 846. The first portion 850 of the first frequency band 844 is shown separate from the second frequency band 842 by an uplink guard band 854 because the first portion 850 of the first frequency band 844 and the asynchronous TDD communication path associated with second frequency band 842 are offset or misaligned in time (i.e., unsynchronized). For example, an uplink portion 860 of the asynchronous TDD communication path associated with the second frequency band 842 has an uplink time slot between time instances t3 and t5, while the uplink time slot, TU, of the first portion 850 of the first frequency band 844 is associated with time instances t2 and t4.

0092Similarly, the second portion 852 of the first frequency band 844 is shown separate from the second frequency band 842 by a downlink guard band 856 because the second portion 860 of the first frequency band 844 and the asynchronous TDD communication path associated with second frequency band 842 are offset or misaligned in time. For example, a downlink portion 862 of the asynchronous TDD communication path associated with the second frequency band 842 has a downlink time slot between time instances t1 and t3, while the downlink time slot, TD, of the second portion 852 of the first frequency band 844 is associated with time instances t0 and t2.

0093<figref idref="f0010">FIGS. 9A-9B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent synchronous TDD and temporally-asymmetric TDD schemes, according to examples. <figref idref="f0010">FIG. 9A</figref> shows a diagram 900 that illustrates a first frequency band 904 associated with a TDD communication path. The diagram 900 illustrates a second frequency band 902 associated with a temporally-asymmetric TDD communication path. The temporally-asymmetric TDD communication path can refer to a TDD communication path having an uplink time slot duration different from a downlink time slot duration. The diagram 900 further illustrates a third frequency band 906 associated with a TDD communication path that is synchronous with the TDD communication path in the first frequency band 904.

0094The first frequency band 904 is associated with a spectrum bandwidth that includes frequencies in the range f1 to f3. The second frequency band 902 is associated with a spectrum bandwidth that includes frequencies in the range f0 to f1. The third frequency bandwidth 906 is associated with a spectrum bandwidth that includes frequencies in the range f3 to f4. The first frequency band 904 is adjacent to the second frequency band 902 (e.g., at f1). The first frequency band 904 is adjacent to the third frequency band 906 (e.g., at f3). The first frequency band 904, the second frequency band 902, and the third frequency band 906 can be mutually exclusive frequency bands. In some examples, the first frequency band 904, the second frequency band 902, and the third frequency band 906 are wireless frequency bands.

0095The first frequency band 904 includes a first portion 910 that has allocated or assigned a spectrum bandwidth including frequencies in the range f2 to f3. The first frequency band 904 includes a second portion 912 that has allocated or assigned a spectrum bandwidth including frequencies in the range f1 to f3. The first portion 910 of the first frequency band 904 is different from the second portion 912 of the first frequency band 904. The spectrum bandwidth associated with the first portion 910 of the first frequency band 904 is different from the spectrum bandwidth associated with the second portion 912 of the first frequency band 904.

0096The first portion 910 of the first frequency band 904 is associated with an uplink portion of the TDD communication path. The first portion 910 has an uplink time slot, TU, associated with the interval between time instances t1 and t3. The second portion 912 of the first frequency band 904 is associated with a downlink portion of the TDD communication path. The second portion 912 has a downlink time slot, TD, associated with the interval between time instances t0 and t1.

0097The TDD communication path associated with the first frequency 904 is symmetric when a time-bandwidth product associated with the first portion 910 of the first frequency band 904 is substantially the same as a time-bandwidth product associated with the second portion 912 of the first frequency band 904. The TDD communication path associated with the first frequency 904 is asymmetric when the time-bandwidth product associated with the first portion 910 of the first frequency band 904 is different from the time-bandwidth product associated with the second portion 912 of the first frequency band 904.

0098<figref idref="f0010">FIG. 9A</figref> shows the first portion 910 of the first frequency band 904 as being adjacent to the third frequency band 906. The synchronous TDD communication path in the third frequency band 906 has an uplink portion (not shown) and a downlink portion (not shown) that operate at substantially the same time intervals as the time intervals TU and TD of the first portion 910 and the second portion 912 of the first frequency band 904, respectively.

0099The first portion 910 of the first frequency band 904 is separate from the second frequency band 902 by an uplink guard band 914 because the first portion 910 of the first frequency band 904 and the temporally-asymmetric TDD communication path associated with second frequency band 902 are offset in time. For example, an uplink portion 920 of the temporally-asymmetric TDD communication path associated with the second frequency band 802 has an uplink time slot or time interval between time instances t2 and t3. The uplink time slot associated with the uplink portion 920 of the second frequency band 902 is temporally offset or misaligned with the uplink time slot, TU, associated with the first portion 910 of the first frequency band 904. This temporal offset can result in interference between the second frequency band 902 and the first frequency band 904.

0100The second portion 912 of the first frequency band 904 is shown as being adjacent to the second frequency band 902 and adjacent to the third frequency band 906. The second portion 912 of the first frequency band 904 and the synchronous TDD communication path associated with the third frequency band 906 are both either transmitting or receiving signals in a same direction and no guard band may be desirable. The second portion 912 of the first frequency band 904 and the second frequency band 902 need no guard band because the second portion 912 of the first frequency band 904 and the temporally-asymmetric TDD communication path associated with second frequency band 902 are transmitting or receiving signals at the same time. For example, a downlink portion 922 of the temporally-asymmetric TDD communication path associated with the second frequency band 902 has a downlink time slot between time instances t0 and t2. As a result, the downlink time slot associated with the downlink portion 922 of the second frequency band 902 and the downlink time slot, TD, associated with the second portion 912 of the first frequency band 904 are common over the time instances t0 and t1 associated with the downlink time slot, TD, and no guard band may be desirable.

0101<figref idref="f0010">FIG. 9B</figref> shows a diagram 940 that illustrates a first frequency band 944 associated with a TDD communication path. The diagram 940 also illustrates a second frequency band 942 associated with a temporally-asymmetric TDD communication path and a third frequency band 946 associated with a synchronous TDD communication path.

0102The first frequency band 944, the second frequency band 942, and the third frequency band 946 are similar to the first frequency band 904, the second frequency band 902, and the third frequency band 906 described above with respect to <figref idref="f0010">FIG. 9A</figref>. The first frequency band 944 has a first portion 950 associated with an uplink portion of the TDD communication path. The first frequency band 944 has a second portion 952 associated with a downlink portion of the TDD communication path. The second frequency band 942 has a first portion 960 associated with an uplink portion of the temporally-asymmetric TDD communication path. The second frequency band 942 has a second portion 962 associated with a downlink portion of the temporally-asymmetric TDD communication path.

0103The first portion 950 of the first frequency band 944 is shown as being adjacent to the third frequency band 946 and adjacent to the second frequency band 942. The second portion 952 of the first frequency band 944 is shown as being adjacent to the third frequency band 946 and separate from the second frequency band 942 by a downlink guard band 954. The downlink guard band 954 may be desirable because the uplink portion 960 of the second frequency band 942 overlaps in time with the second portion 952 of the first frequency band 944 that is associated with the downlink portion of the TDD communication path.

0104<figref idref="f0011">FIGS. 10A-10B</figref> are each a diagram depicting time and frequency aspects of a TDD scheme with adjacent temporally-asymmetric TDD schemes, according to an example. <figref idref="f0011">FIG. 10A</figref> shows a diagram 1000 that illustrates a first frequency band 1004 associated with a TDD communication path. The diagram 1000 also illustrates a second frequency band 1002 associated with a temporally-asymmetric TDD communication path. In this example, the temporally-asymmetric TDD communication path associated with the second frequency band 1002 has an uplink time slot duration that is shorter than a downlink time slot duration. For example, the uplink time slot is between time instances t2 and t3 and the downlink time slot is between time instances t0 and t2. The diagram 1000 further illustrates a third frequency band 1006 associated with a temporally-asymmetric TDD communication path different from that of the second frequency band 1002. In this example, the temporally-asymmetric TDD communication path associated with the third frequency band 1006 also has the same uplink time slot duration and the same downlink time slot duration as the temporally-asymmetric TDD communication path associated with the second frequency band 1002.

0105The first frequency band 1004 includes a first portion 1010 and a second portion 1012. A spectrum bandwidth associated with the first portion 1010 of the first frequency band 1004 is smaller than a spectrum bandwidth associated with the second portion 1012 of the first frequency band 1004. The first portion 1010 of the first frequency band 1004 is associated with an uplink portion of the TDD communication path. The second portion 1012 of the first frequency band 1004 is associated with a downlink portion of the TDD communication path. The second frequency band 1002 includes an uplink portion 1020 and a downlink portion 1022 associated with the temporally-asymmetric TDD communication path. The third frequency band 1006 includes an uplink portion 1030 and a downlink portion 1032 associated with the temporally-asymmetric TDD communication path.

0106<figref idref="f0011">FIG. 10A</figref> shows the first portion 1010 of the first frequency band 1004 as separate from the second frequency band 1002 by an uplink guard band 1014 and separate from the third frequency band 1006 by an uplink guard band 1016. The uplink guard bands 1014 and 1016 may be desirable because the downlink portion 1022 of the second frequency band 1002 and the downlink portion 1032 of the third frequency band 1006 temporally overlap the first portion 1010 of the first frequency band 1004 that is associated with the uplink portion of the TDD communication path such that interference may occur between the bands.

0107Similarly, the second portion 1012 of the first frequency band 1004 is shown as adjacent to the second frequency band 1002 and adjacent to the third frequency band 1006. In this example, guard bands need not be used because the second portion 1012 of the first frequency band 1004 occurs during a time interval (e.g., between t0 and t1) that coincides with a time interval (e.g., between t0 and t2) associated with the downlink portion 1022 of the second frequency band 1002 and also associated with the downlink portion 1032 of the third frequency band 1006.

0108<figref idref="f0011">FIG. 10B</figref> shows a diagram 1040 that illustrates a first frequency band 1044 associated with a TDD communication path. The diagram 1040 also illustrates a second frequency band 1042 associated with a temporally-asymmetric TDD communication path and a third frequency band 1046 associated with a different temporally-asymmetric TDD communication path. In this example, the temporally-asymmetric TDD communication path associated with the second frequency band 1042 and the temporally-asymmetric TDD communication path associated with the third frequency band 1046 each has an uplink time slot duration that is longer than a downlink time slot duration.

0109The first frequency band 1044, the second frequency band 1042, and the third frequency band 1046 are similar to the first frequency band 1004, the second frequency band 1002, and the third frequency band 1006 described above with respect to <figref idref="f0011">FIG. 10A</figref>. The first frequency band 1044 has a first portion 1050 associated with an uplink portion of the TDD communication path. The first frequency band 1044 has a second portion 1052 associated with a downlink portion of the TDD communication path. The second frequency band 1042 has a first portion 1060 associated with an uplink portion of the temporally-asymmetric TDD communication path. The second frequency band 1042 has a second portion 1062 associated with a downlink portion of the temporally-asymmetric TDD communication path. The third frequency band 1046 has a first portion 1070 associated with an uplink portion of the temporally-asymmetric TDD communication path. The third frequency band 1046 has a second portion 1072 associated with a downlink portion of the temporally-asymmetric TDD communication path.

0110The first portion 1050 of the first frequency band 1044 is shown as being adjacent to the third frequency band 1046 and adjacent to the second frequency band 1042. The second portion 1052 of the first frequency band 1044 is shown as being separated from to the third frequency band 1046 by a downlink guard band 1056 and separate from the second frequency band 1042 by a downlink guard band 1054. The downlink guard bands 1054 and 1056 may be desirable because the uplink portion 1060 of the second frequency band 1042 and the uplink portion 1070 of the third frequency band 1046 each overlaps in time (e.g., between t1 and t2) with the second portion 1052 of the first frequency band 1044 that is associated with the downlink portion of the TDD communication path.

0111<figref idref="f0012">FIGS. 11A-11B</figref> are each a diagram depicting the time and frequency aspects of a TDD scheme with adjacent temporally-asymmetric TDD schemes, according examples. <figref idref="f0012">FIG. 11</figref> A shows a diagram 1100 that illustrates a first frequency band 1104 associated with a TDD communication path. The TDD communication path can be symmetric or asymmetric. The diagram 1100 also illustrates a second frequency band 1102 associated with a temporally-asymmetric TDD communication path. In this example, the temporally-asymmetric TDD communication path associated with the second frequency band 1002 has an uplink time slot duration (e.g., between t3 and t4) that is shorter than a downlink time slot duration (e.g., between t0 and t3). The diagram 1100 further illustrates a third frequency band 1106 associated with a temporally-asymmetric TDD communication path. In this example, the temporally-asymmetric TDD communication path associated with the third frequency band 1106 has an uplink time slot duration (e.g., between t1 and t4) that is longer than a downlink time slot duration (e.g., between t0 and t1).

0112The first frequency band 1104 includes a first portion 1110 and a second portion 1112. A spectrum bandwidth associated with the first portion 1110 of the first frequency band 1104 can be the same (or different) than a spectrum bandwidth associated with the second portion 1112 of the first frequency band 1104. The first portion 1110 of the first frequency band 1104 is associated with an uplink portion of the TDD communication path. The second portion 1112 of the first frequency band 1104 is associated with a downlink portion of the TDD communication path. The second frequency band 1102 includes an uplink portion 1120 and a downlink portion 1122 of the temporally-asymmetric TDD communication path. The third frequency band 1106 includes an uplink portion 1130 and a downlink portion 1132 of the temporally-asymmetric TDD communication path.S

0113<figref idref="f0012">FIG. 11A</figref> shows the first portion 1110 of the first frequency band 1104 as separate from the second frequency band 1102 by an uplink guard band 1114 and adjacent to the third frequency band 1106. The uplink guard band 1114 may be desirable because the downlink portion 1122 of the second frequency band 1102 temporally overlaps the first portion 1110 of the first frequency band 1104 that is associated with the uplink portion of the TDD communication path. Without the uplink guard band 1114, this temporal overlap can cause interference between communication schemes operating in the first frequency band 1104 and the second frequency band 1102.

0114Similarly, the second portion 1112 of the first frequency band 1104 is shown as adjacent to the second frequency band 1102 and separate from the third frequency band 1106 by a downlink guard band 1116. The downlink guard band 1116 may be desirable because the uplink portion 1130 of the third frequency band 1106 temporally overlaps the second portion 1112 of the first frequency band 1104 that is associated with the downlink portion of the TDD communication path. Without the downlink guard band 1116, this temporal overlap can cause interference between communication schemes operating in the first frequency band 1104 and in the third frequency band 1106.

0115<figref idref="f0012">FIG. 11B</figref> shows a diagram 1140 that illustrates a first frequency band 1144 associated with a TDD communication path. The diagram 1140 also illustrates a second frequency band 1142 associated with a temporally-asymmetric TDD communication path and a third frequency band 1146 associated with a different temporally-asymmetric TDD communication path. In this example, the temporally-asymmetric TDD communication path associated with the second frequency band 1142 has an uplink time slot duration (e.g., between t1 and t4) that is longer than a downlink time slot duration (e.g., between t0 and t1). The temporally-asymmetric TDD communication path associated with the third frequency band 1146 has an uplink time slot duration (e.g., between t3 and t4) that is shorter than a downlink time slot duration (e.g., between t0 and t3).

0116The first frequency band 1144, the second frequency band 1142, and the third frequency band 1146 are similar to the first frequency band 1104, the second frequency band 1102, and the third frequency band 1106 described above with respect to <figref idref="f0012">FIG. 11 A</figref>. The first frequency band 1144 has a first portion 1150 associated with an uplink portion of the TDD communication path. The first frequency band 1144 has a second portion 1152 associated with a downlink portion of the TDD communication path. The second frequency band 1142 has a first portion 1160 associated with an uplink portion of the temporally-asymmetric TDD communication path. The second frequency band 1142 has a second portion 1162 associated with a downlink portion of the temporally-asymmetric TDD communication path. The third frequency band 1146 has a first portion 1170 associated with an uplink portion of the temporally-asymmetric TDD communication path. The third frequency band 1146 has a second portion 1172 associated with a downlink portion of the temporally-asymmetric TDD communication path.

0117The first portion 1150 of the first frequency band 1144 is shown as being adjacent to the second frequency band 1142 and separate from the third frequency band 1146 by an uplink guard band 1156. The uplink guard band 1156 may be desirable because the downlink portion 1172 of the third frequency band 1146 overlaps in time with the first portion 1150 of the first frequency band 1144 that is associated with the uplink portion of the TDD communication path. The second portion 1152 of the first frequency band 1144 is shown as being separated from to the second frequency band 1142 by a downlink guard band 1154 and adjacent to the third frequency band 1146. The downlink guard band 1154 may be desirable because the uplink portion 1160 of the second frequency band 1142 overlaps in time with the second portion 1152 of the first frequency band 1144 that is associated with the downlink portion of the TDD communication path.

0118<figref idref="f0013">FIG. 12A</figref> is a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD and broadcast schemes, according to an embodiment. <figref idref="f0013">FIG. 12A</figref> shows a diagram 1200 that illustrates a first frequency band 1204 associated with a TDD communication path. The TDD communication path can be symmetric or asymmetric. The diagram 1200 also illustrates a second frequency band 1202 associated with a wireless broadcast. The diagram 1200 further illustrates a third frequency band 1206 associated with a downlink portion of an FDD communication path.

0119The first frequency band 1204 includes a first portion 1210 and a second portion 1212. A spectrum bandwidth associated with the first portion 1210 of the first frequency band 1204 is different from a spectrum bandwidth associated with the second portion 1212 of the first frequency band 1204. The first portion 1210 of the first frequency band 1204 is associated with an uplink portion of the TDD communication path. The second portion 1212 of the first frequency band 1204 is associated with a downlink portion of the TDD communication path.

0120<figref idref="f0013">FIG. 12A</figref> shows the first portion 1210 of the first frequency band 1204 as separate from the second frequency band 1202 by an uplink guard band 1214 and separate from the third frequency band 1206 by an uplink guard band 1216. The uplink guard band 1214 is provided because the wireless broadcast associated with the second frequency band 1202 could interfere with the first portion 1210 of the first frequency band 1204 associated with the uplink portion of the TDD communication path. Similarly, the uplink guard band 1216 is provided because the downlink portion of the FDD communication path associated with the second frequency band 1202 could interfere with the first portion 1210 of the first frequency band 1204 associated with the uplink portion of the TDD communication path. The second portion 1212 of the first frequency band 1204 is shown as being adjacent to both the second frequency band 1204 and adjacent to the third frequency band 1206.

0121<figref idref="f0013">FIG. 12B</figref> is a diagram depicting time and frequency aspects of a TDD scheme with adjacent FDD and broadcast schemes, according to an example. <figref idref="f0013">FIG. 12B</figref> shows a diagram 1220 that illustrates a first frequency band 1224 associated with a TDD communication path. The diagram 1220 also illustrates a second frequency band 1222 associated with a wireless broadcast and a third frequency band 1226 associated with an uplink portion of an FDD communication path.

0122The first frequency band 1224, the second frequency band 1222, and the third frequency band 1226 are similar to the first frequency band 1204, the second frequency band 1202, and the third frequency band 1206 described above with respect to <figref idref="f0013">FIG. 12A</figref>. The first frequency band 1224 has a first portion 1230 associated with an uplink portion of the TDD communication path. The first frequency band 1224 has a second portion 1232 associated with a downlink portion of the TDD communication path.

0123The first portion 1230 of the first frequency band 1224 is shown as being separated from the second frequency band 1222 by an uplink guard band 1234 and adjacent to the third frequency band 1226. The uplink guard band 1234 is used because the wireless broadcast associated with the second frequency band could would interfere with the first portion 1230 of the first frequency band 1224 associated with the uplink portion of the TDD communication path. The second portion 1232 of the first frequency band 1224 is shown as being adjacent to the second frequency band 1222 and separate from the third frequency band 1226 by a downlink guard band 1236. The downlink guard band 1236 is used because the uplink portion of the FDD communication path associated with the third frequency band 1226 could interfere with the second portion 1232 of the first frequency band 1224 that is associated with the downlink portion of the TDD communication path.

0124<figref idref="f0014">FIG. 13</figref> is a flow chart illustrating a method for using an asymmetric TDD scheme, according to an example. At 1310, after 1300, receiving signals via a portion of a first frequency band over an asymmetric TDD communication path associated with the first frequency band. The first frequency band and the associated asymmetric TDD communication path can be based on one or more examples described herein with respect to <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 3-12B</figref>. At 1320, transmitting signals via a different portion of the first frequency band over the asymmetric TDD communication path associated with the first frequency band. After 1320, the process proceeds to 1330.

0125<figref idref="f0015">FIG. 14</figref> is a flow chart illustrating a method for using an asymmetric TDD scheme, according to another example. At 1410, after 1400, an asymmetric TDD communication path is operated over a first frequency band. The first frequency band and the associated asymmetric TDD communication path can be based on one or more examples described herein with respect to <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 3-12B</figref>. At 1420, communicating signals via the first frequency band over the asymmetric TDD communication path associated with the first frequency band. After 1420, the process proceeds to 1430.

0126<figref idref="f0016">FIG. 15</figref> is a flow chart illustrating a method for using an asymmetric TDD scheme, according to yet another example. At 1510, after 1500, operating a first communication portion of an asymmetric TDD communication path via an uplink portion of a first frequency band. The first frequency band and the associated asymmetric TDD communication path can be based on one or more examples described herein with respect to <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 3-12B</figref>. At 1520, operating a second communication portion of the asymmetric TDD communication path via a downlink portion of the first frequency band. After 1520, the process proceeds to 1530.

0127In one or more examples or embodiments, the communication methods associated with asymmetric TDD communication paths described above with respect to <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 3-12B</figref> can be implemented in flexible-use spectrum. In one or more examples or embodiments, the communication methods associated with asymmetric TDD communication paths described above with respect to <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 3-12B</figref> can be implemented in spectrum having a dedicated use.

CONCLUSION

0128While various embodiments of the invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. The alternative examples described do not contribute to the invention. Although described with reference to use with flexible-use spectrum for satellite, terrestrial, and/or hybrid wireless communication systems, it should be understood that the asymmetric TDD methods described herein can be used with frequency bands dedicated for particular use and for use with certain wireless communication systems. Moreover, the asymmetric TDD methods described herein can be used with frequency bands in wired communication systems.

Contents6

Citations
Document	Relation	Office
US2004165547A1	Cites	United States of America
US2006126546A1	Cites	United States of America
US2007286156A1	Cites	United States of America

77 members in 7 offices

This recordMember, by publication date

Members77

Family members, oldest first
Document	Office	Kind
AU2009313929A1	Australia	A1	2010-05-20
CA2743501A1	Canada	A1	2010-05-20
US2010124183A1	United States of America	A1	2010-05-20
WO2010057008A1	World Intellectual Property Organization (WIPO)	A1	2010-05-20
US7969923B2	United States of America	B2	2011-06-28
EP2359499A1	European Patent Office (EPO)	A1	2011-08-24
US2011211502A1	United States of America	A1	2011-09-01
CN102362447A	China	A	2012-02-22
JP2012509032A	Japan	A	2012-04-12
US2012093042A1	United States of America	A1	2012-04-19
AU2009313929B2	Australia	B2	2012-07-26
AU2012227221A1	Australia	A1	2012-10-11
AU2012227221B2	Australia	B2	2013-01-31
AU2013200341A1	Australia	A1	2013-02-14
CA2743501C	Canada	C	2013-05-28
AU2013211523A1	Australia	A1	2013-08-22
AU2013200341B2	Australia	B2	2013-09-05
US8537732B2	United States of America	B2	2013-09-17
JP2013225913A	Japan	A	2013-10-31
JP2013229919A	Japan	A	2013-11-07
US8630214B2	United States of America	B2	2014-01-14
US2014016521A1	United States of America	A1	2014-01-16
US2014086115A1	United States of America	A1	2014-03-27
CN102362447B	China	B	2014-08-20
CN103997367A	China	A	2014-08-20
JP5588453B2	Japan	B2	2014-09-10
AU2013211523B2	Australia	B2	2014-12-04
JP5670515B2	Japan	B2	2015-02-18
AU2015200916A1	Australia	A1	2015-03-12
JP5705924B2	Japan	B2	2015-04-22
JP2015080259A	Japan	A	2015-04-23
JP2015130686A	Japan	A	2015-07-16
US9148273B2	United States of America	B2	2015-09-29
US2016233975A1	United States of America	A1	2016-08-11
US9497015B2	United States of America	B2	2016-11-15
AU2016256844A1	Australia	A1	2016-12-01
AU2015200916B2	Australia	B2	2016-12-08
JP6100817B2	Japan	B2	2017-03-22
JP6114251B2	Japan	B2	2017-04-12
JP2017108464A	Japan	A	2017-06-15
US9722762B2	United States of America	B2	2017-08-01
US2017230166A1	United States of America	A1	2017-08-10
US2017310453A1	United States of America	A1	2017-10-26
US9923709B2	United States of America	B2	2018-03-20
EP2359499B1	European Patent Office (EPO)	B1	2018-04-04
CN103997367B	China	B	2018-05-04
JP6334766B2	Japan	B2	2018-05-30
EP3361652A1	European Patent Office (EPO)	A1	2018-08-15
AU2016256844B2	Australia	B2	2018-08-16
JP2018142986A	Japan	A	2018-09-13
US2019058571A1	United States of America	A1	2019-02-21
EP3461031A1	European Patent Office (EPO)	A1	2019-03-27
EP3462640A1	European Patent Office (EPO)	A1	2019-04-03
US10263756B2	United States of America	B2	2019-04-16
JP6563071B2	Japan	B2	2019-08-21
EP3570460A1	European Patent Office (EPO)	A1	2019-11-20
JP2019205190A	Japan	A	2019-11-28
EP3462640B1	European Patent Office (EPO)	B1	2020-02-26
EP3361652B1	European Patent Office (EPO)	B1	2020-03-04
EP3651383A1	European Patent Office (EPO)	A1	2020-05-13
JP6692971B2	Japan	B2	2020-05-13
US2020195411A1	United States of America	A1	2020-06-18
JP2020109988A	Japan	A	2020-07-16
EP3683981A1	European Patent Office (EPO)	A1	2020-07-22
EP3873005A1	European Patent Office (EPO)	A1	2021-09-01
US11153062B2	United States of America	B2	2021-10-19
US2021336757A1	United States of America	A1	2021-10-28
EP3907907A1	European Patent Office (EPO)	A1	2021-11-10
EP3907907A4	European Patent Office (EPO)	A4	2021-11-10
EP3461031B1	European Patent Office (EPO)	B1	2021-12-29
EP3683981B1	European Patent Office (EPO)	B1	2021-12-29
JP7009532B2	Japan	B2	2022-01-25
EP3651383B1	European Patent Office (EPO)	B1	2022-04-13
US11546126B2	United States of America	B2	2023-01-03
EP3570460B1	European Patent Office (EPO)	B1	2023-09-27
EP3907907B1	European Patent Office (EPO)	B1	2023-09-27
EP3873005B1This record	European Patent Office (EPO)	B1	2024-02-07

86 legal events, as 9 offices reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code	Office
2026-06-01	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2026-03-30	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2026-03-06	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2026-01-08	Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP	PGFP	EP
2025-10-22	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2025-10-20	Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP	PGFP	EP
2025-10-16	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2025-10-16	Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP	PGFP	EP
2025-08-28	Lapsed because of non-payment of the annual feeLapsedMM	MM	BE
2025-07-23	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2025-07-15	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2025-07-15	Patent ceasedCeasedPL	PL	CH
2025-07-07	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2025-06-30	Patent ceasedCeasedPL	PL	CH
2025-04-24	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2025-01-15	No opposition filedOpposition26N	26N	EP
2024-12-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-12-13	No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE	PLBE	EP
2024-12-13	Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA	STAA	EP
2024-12-04	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-11-08	No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097	R097	DE
2024-10-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-29	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-23	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-23	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-14	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-10-11	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-08-30	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-08-30	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-08-30	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-08-30	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-08-01	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-08-01	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-31	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-23	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-22	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-18	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-18	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-15	Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05	MK05	AT
2024-07-15	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-09	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-07-01	Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25	PG25	EP
2024-06-12	Patent invalid in the netherlands as no translation has been filedMP	MP	NL
2024-05-27	Invalidation of extension of european patentsMG9D	MG9D	LT
2024-02-29	Dpma publication of mentioned ep patent grantGrantedR096	R096	DE
2024-02-28	European patents granted designating irelandGrantedFG4D	FG4D	IE
2024-02-15	European patent takes effect as a national patent in ch/liEP	EP	CH
2024-02-07	Divisional application: reference to earlier applicationAC	AC	EP
2024-02-07	Divisional application: reference to earlier applicationAC	AC	EP
2024-02-07	Divisional application: reference to earlier applicationAC	AC	EP
2024-02-07	Designated contracting statesAK	AK	EP
2024-02-07	European patent grantedGrantedFG4D	FG4D	GB
2024-01-05	(expected) grantORIGINAL CODE: 0009210GRAA	GRAA	EP
2024-01-05	Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA	STAA	EP
2024-01-02	Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS	GRAS	EP
2023-09-27	Intention to grant announcedINTG	INTG	EP
2023-09-13	Intention to grant announced (deleted)INTC	INTC	EP
2023-08-30	Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP	GRAP	EP
2023-08-30	Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA	STAA	EP
2023-08-08	Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deletedORIGINAL CODE: EPIDOSDIGR1GRAJ	GRAJ	EP
2023-08-08	Information on the status of an ep patent application or granted ep patentGrantedSTATUS: REQUEST FOR EXAMINATION WAS MADESTAA	STAA	EP
2023-06-28	Opt-out of the competence of the unified patent court (upc) registeredP01	P01	EP
2023-05-17	Intention to grant announcedINTG	INTG	EP
2023-04-18	Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP	GRAP	EP
2023-04-18	Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA	STAA	EP
2021-09-01	Request for examination filed17P	17P	EP
2021-09-01	Divisional application: reference to earlier applicationAC	AC	EP
2021-09-01	Divisional application: reference to earlier applicationAC	AC	EP
2021-09-01	Divisional application: reference to earlier applicationAC	AC	EP
2021-09-01	Designated contracting statesAK	AK	EP
2021-07-30	Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI	PUAI	EP
2021-07-30	Information on the status of an ep patent application or granted ep patentGrantedSTATUS: REQUEST FOR EXAMINATION WAS MADESTAA	STAA	EP

Asymmetric tdd in flexible use spectrum

Abstract