Patent Application
20150181437
1. Field of the Disclosure
Example embodiments generally relate to adapting a reception via first wireless technology to reduce or avoid interference with a transmission via a second wireless technology.
2. Background
A mobile device may be capable of communicating using more than one wireless technology. When operated concurrently, certain radio technologies within such a device may operate on frequencies that cause interference. For example, wireless communications conforming to the 3rd Generation Partnership Project's (3GPP) long-term evolution (LTE) specification may operate on frequencies near or adjacent to an industrial, scientific and medical (ISM) frequency band. So, interference may result between LTE communication and communication from a technology operating in the ISM band in a device that implements both technologies. To reduce or eliminate interference, co-existence coordination may be required to schedule transmission and reception among co-existing radio technologies, while avoiding performance degradation in the co-existing radio technologies.
While the present disclosure is described herein with illustrative embodiments for particular applications, it should be understood that the disclosure is not limited thereto. A person skilled in the art with access to the teachings provided herein will recognize additional modifications, applications, and embodiments within the scope thereof and additional fields in which the disclosure would be of significant utility.
The terms “embodiments” or “example embodiments” do not require that all embodiments include the discussed feature, advantage, or mode of operation. Alternate embodiments may be devised without departing from the scope or spirit of the disclosure, and well-known elements may not be described in detail or may be omitted so as not to obscure the relevant details. In addition, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. For example, as used herein, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements, and components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.
Terms like “user equipment,” “mobile station,” “mobile,” “mobile device,” “subscriber station,” “subscriber equipment,” “access terminal,” “terminal,” “handset,” and similar terminology, refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream. The foregoing terms may be utilized interchangeably in the subject specification and related drawings. Likewise, the terms “access point,” “base station,” “base transceiver station”, “Node B.” “evolved Node B (eNode B),” home Node B (HNB),” “home access point (HAP),” or the like, may be utilized interchangeably in the subject specification and drawings, and refer to a wireless network component or apparatus that serves and receives data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream from a set of subscriber stations.
Software described throughout this disclosure may be embodied as one or more computer-readable instruction(s) on a computer-readable storage device that is tangible—such as a persistent memory device (e.g., read-only memory (ROM), flash memory, a magnetic storage device, an optical disc, and the like), a non-persistent memory device (e.g., random-access memory (RAM)), and the like—that can be executed by a processor to perform one or more operations.
Turning now to
As shown in
The LTE radio 110 and the ISM radio 120 may operate on adjacent or nearly adjacent frequencies.
Returning to
The evolved radio access network of the EPS 150 of
The ISM radio 120 may implement any technology, specification, or standard that operates in the ISM frequency band. In the example system 10 of
Turning to
Some or all of the components of the apparatus 300 may be implemented as a single integrated circuit, or may be implemented as different integrated circuits that are communicatively connected (e.g., via wires or wirelessly). In one example, the host 310, the LTE radio 320, and the ISM radio 330 are implemented as a single integrated circuit. In another example, the host 310, the LTE radio 320, and the ISM radio 330 are each implemented as separate integrated circuits. Separate integrated circuits may be mounted on a printed circuit board (PCB) along with other circuits, devices, components, and the like. Other configurations apparent to a person skilled in the art are within the scope of this disclosure.
The apparatus 300 of
As mentioned, the apparatus 300 includes the host 310. The host 310 is communicatively connected to the LTE radio 220 and the ISM radio 230. The host 310 may control the overall operation of the apparatus 300, and may include (but is not limited to) one or more: central processing units (CPU), field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), digital signal processors (DSP), and the like. The host 310 may execute one or more applications, such as an operating system (OS), to control the overall operation of the apparatus 300, and to manage co existing wireless connections in accordance with example embodiments of this disclosure. The host 310 may include one or more components (e.g., implemented in hardware, software, or any combination of hardware and software) in addition to the components shown in the embodiment of
The LTE radio 320 includes an LTE controller 322, a transmitter (TX) 324, a receiver (RX) 326, and an antenna 328. The LTE controller 322 is communicatively connected to both of the TX 324 and the RX 326 for control and data transmission and reception. The LTE controller 322 is also communicatively connected to the ISM controller 332 of the ISM radio 330, and can exchange data or other communications with the ISM controller 332. The antenna 328, which transmits and receives electromagnetic radiation, is communicatively connected to both of the TX 324 and the RX 326. In
The LTE radio 320 may include one or more components (e.g., implemented in hardware, software, or any combination of hardware and software) in addition to the components shown in the embodiment of
The ISM radio 330 includes an ISM controller 332, a transmitter (TX) 334, a receiver (RX) 336, and an antenna 338. The ISM controller 332 is communicatively connected to both of the TX 334 and the RX 336. The ISM controller 332 is also communicatively connected to the LTE controller 322 of the LTE radio 320, and can exchange data or other communications with the LTE controller 322. The antenna 338, which transmits and receives electromagnetic radiation, is communicatively connected to both of the TX 334 and the RX 336. In
The ISM radio 330 may include one or more components (e.g., implemented in hardware, software, or any combination of hardware and software) in addition to the components shown in the embodiment of
The apparatus 300, via the LTE radio 320, may be configured to receive system information from an LTE network (such as the EPS 150 of
Each SIB contains system information and is identified using the following nomenclature: SystemInformationBlockTypeN, where N is a whole number greater than zero. For example, SystemInformationBlockType1 (SIB1) contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information; SystemInformationBlockType2 (SIB2) contains radio resource configuration information that is common for certain UEs; and so on. TABLE I below summarizes information contained in various SIBs specified in 3GPP's technical specification 3GPP TS 36.331 v11.5.0 (2013-09).
SIBs other than SystemInformationBlockType1 are carried in SystemInformation (SI) messages. The mapping of SIBs to SI messages is flexibly configurable by schedulingInfoList included in SystemInformationBlockType1, with restrictions that: each SIB is contained only in a single SI message, only SIBs having the same scheduling requirement (periodicity) can be mapped to the same SI message, and SystemInformationBlockType2 is always mapped to the SI message that corresponds to the first entry in the list of SI messages in schedulingInfoList. There may be multiple SI messages transmitted with the same periodicity.
SystemInformationBlockType1 and all SI messages may be transmitted on the Downlink Shared Channel (DL-SCH). Once SystemInformationBlockType1 has been received and decoded, the SI messages and their scheduling by the network is known. So, in this disclosure, scheduling information included in SystemInformationBlockType1 may be considered a “message transmission schedule.”
An LTE-enabled device, such as UE 100 of
Turning briefly to
Example embodiments of this disclosure describe, among other things, systems, methods, and techniques for adapting an LTE reception in order to reduce or avoid interference with an ISM transmission. In one embodiment, an LTE-enabled device adapts the reception of system information provided by an LTE network (e.g., via E-UTRAN) to reduce or avoid interference with a concurrent, pending, scheduled, etc. ISM transmission. For example, the apparatus 300 may adapt a reception of system information by the LTE radio 320 to reduce or avoid interference with a transmission from the ISM radio 330. While adapting the reception of LTE system information is described throughout this disclosure, the methods and techniques described herein apply equally to the reception of any scheduled data, information, or communication at a first transceiver to achieve co-existence coordination with a second transceiver that implements different, potentially competing or interfering, technology than the first transceiver.
Various methods may be employed, alone or in combination, to achieve this co-existence coordination. In some embodiments, the LTE controller 322 or the host 310 may generally enable/disable reception of some or all communications at the LTE radio 320 to implement the various methods and achieve the co-existence coordination described throughout this disclosure. For example, the LTE controller 322 or the host 310 may specifically enable/disable reception of SI messages at the LTE radio 320, which may leave the LTE radio 320 available to receive other communications, while implementing one or more of the various methods. Also, each of the techniques described below may be implemented after receiving and decoding SystemInformationBlockType1, which indicates the SI messages that will be sent by the network and their scheduling (e.g., transmission frequency and periodicity).
A first example method, which may be referred to as “out-of-order” acquisition, may be implemented to acquire SI messages out-of-order to reduce the overall time required to receive system information. A default technique requires receiving the SI messages in order; but since SI messages may be scheduled with different transmission frequency and periodicity, in-order acquisition may require intentionally ignoring or failing to receive an available SI message. Thus, out-of-order acquisition may reduce the overall time required to receive scheduled SI messages by acquiring each SI message when available, rather than waiting for a particular message's “turn”, when part of a sequence of messages. As should be apparent to a person of ordinary skill in the art, “out-of-order” acquisition may become “in-order” acquisition when the SI messages are scheduled to be available in-order; thus, this technique may also be referred to as “when available” acquisition or the like.
The following example helps illustrate this first method. The apparatus 300 of
By contrast, the “out-of-order” acquisition method allows the LTE radio 320 to acquire SI fourth when available, instead of waiting until SIthird has been acquired. Thus, the “out-of-order” or “when available” method may require no more than 256 radio frames to acquire the four example SI messages. In this example, SI message acquisition may or may not be enabled (e.g., the LTE radio 320 may or may not be “listening” for the SI messages) for the entire period required to acquire the four example SI messages. Either way, the “out-of-order” method illustrated in this example may effectively reduce the overall period of time that the reception of system information at the LTE radio 320 could potentially interfere with transmission from the ISM radio 330. For example, circuits in the LTE radio 320 that cause interference (such as oscillators, mixers, amplifiers and the like) could be powered down, or not used, thereby decreasing potential interference with transmissions to/from the ISM radio 330.
A second example method that may be implemented to acquire SI messages may be referred to as “need-based” acquisition. In this technique, SI message acquisition is enabled to receive a given SI message transmitted from an LTE network when (at least) the following criteria are satisfied: (1) the given SI message is pending acquisition (e.g., the given SI message contains new information or information that has yet to be acquired by the LTE-enabled device), and (2) the given SI message is scheduled for transmission from the LTE network. Enabling SI message acquisition (e.g., “listening” for an SI message) when these criteria are met, and alternatively disabling SI message acquisition (or not “listening” for an SI message) when these criteria are not met may reduce the cumulative amount of time in a given period an LTE-enabled device devotes to receiving system information from the LTE network.
The following example helps illustrate the “need-based” acquisition method. The apparatus 300 of
As mentioned, each of the methods described in this disclosure may be implemented alone or in combination with one or more of the other methods. So before describing a third method for co-existence coordination, the example diagram 500 of
In
During the first group of 16 radio frames 520A, SIfirst, SIsecond, and SIfourth are available for acquisition, i.e., are scheduled to be transmitted from the LTE network. Since the acquisition bitmap 510A indicates that SIfirst has already been acquired, SI message acquisition is not enabled to acquire SIfirst—which illustrates the “need-based” acquisition method. But, since SIsecond and SIfourth are available and have yet to be acquired, SI message acquisition is enabled during the acquisition window 530A to acquire SIsecond and SIfourth. The acquisition of SIfourth prior to acquiring SIthird (which is not available in this example until the fifth group of 16 radio frames 520E) illustrates the “out-of-order” or “when available” acquisition method.
The example diagram 500 of
Turning next to a third example method, which may be referred to as “elastic information” acquisition, the acquisition of elastic system information may be delayed. Elastic system information may be information that is not time sensitive, information that does not require immediate acquisition, information that is not considered “essential,” or the like. By contrast, inelastic system information may be information that is time sensitive, information that requires immediate acquisition, information that is considered “essential,” or the like. Examples of inelastic system information may include (but are not limited to) one or more of information in the MasterInformationBlock, information in the SystemInformationBlockType1, information in the SystemInformationBlockType2, ETWS notification in SystemInformationBlockType10, ETWS notification in SystemInformationBlockType11, CMAS notification in SystemInformationBlockType12 and the like. Refer to TABLE I above.
As mentioned, the acquisition of elastic system information may be delayed when the “elastic information” acquisition method is implemented. Once a given SI message is determined to be elastic—that is, the given SI message carries an SIB that contains elastic information—delayed reception of the given SI message may be triggered when a concurrent ISM transmission is scheduled. The acquisition of the given SI message may be delayed until the ISM transmission has completed or until a maximum delay threshold for acquiring the given SI message has been exceeded. Example maximum delay thresholds for the “elastic information” acquisition technique include (but are not limited to: 10 ms, 20 ms, 50 ms, 100 ms, and 200 ms, among others. In response to exceeding a maximum delay threshold, the given SI message may be acquired.
Considering the apparatus 300 as an example, during concurrent operation of the LTE radio 320 and the ISM radio 330, the ISM radio 330 may assert or request ISM transmission priority (ISM_TX_PRIORITY) when ISM transmission is scheduled. The terms “assert” and “request” may be used interchangeably throughout this disclosure—so “asserting” priority may function as “requesting” priority, and vice versa. ISM transmission priority may be de-asserted when the scheduled ISM transmission has completed. ISM transmission may be scheduled by the ISM radio 330 (e.g., via the ISM controller 332), the host 310, or another mechanism of the apparatus 300. And, ISM transmission priority may be asserted and de-asserted by the ISM radio 330 (e.g., via the ISM controller 332), the host 310, or another mechanism of the apparatus 300.
Continuing this example, the LTE radio 320 (e.g., via the LTE controller 322) may determine—e.g., by receiving a communication indicating assertion of ISM transmission priority; or by periodically polling the ISM radio 330, the host 310, or another mechanism (e.g., a flag register) of the apparatus 300—when ISM transmission priority has been asserted and when ISM transmission priority has been de-asserted. Once the LTE radio 320 determines that ISM transmission priority is asserted, it may adapt an SI message reception, under certain circumstances, to reduce or avoid interference with the scheduled ISM transmission. The ISM radio 330 (e.g., via the ISM controller 332), the host 310, or another mechanism may send a communication indicating the assertion of ISM transmission priority to the LTE radio 320 (e.g., to the LTE controller 322).
The method 600 begins at stage 610, where an SI message transmission schedule is acquired from an LTE network. For example, the apparatus 300 of
At stage 620, it is determined whether one or more SI message acquisition criteria are satisfied. SI message acquisition criteria may be associated with one or more of the “out-of-order,” the “need-based,” or the “elastic information” acquisition methods. In one example, the method 600 implements the “out-of-order” acquisition method, and the SI message acquisition criterion at stage 620 is whether an SI message is available (regardless of order) for acquisition.
When the SI message acquisition criterion or criteria is satisfied at stage 620, the method advances to stage 630 where SI message acquisition is enabled and a scheduled SI message is acquired. As an example of stage 630, the LTE controller 322 or the host 310 may enable the LTE radio 320 to acquire an SI message during a message acquisition window (e.g., acquisition window 530A of
At stage 640, SI message acquisition may be disabled in response to completing acquisition of the scheduled SI message at stage 630. For example, LTE controller 322 or the host 310 may disable SI message acquisition at the LTE radio 320 (e.g., the LTE radio 320 may be disabled). Stage 640 may be optional—some of the methods and techniques described herein do not necessarily require disabling SI message acquisition in response to completing acquisition of a scheduled SI message. For example, the “out-of-order” acquisition method may enable SI message acquisition until all scheduled SI messages are acquired. Of course, as described above, the “out-of-order” acquisition method may alternatively disable SI message acquisition after each scheduled SI message is acquired.
Next, the method 600 advances to stage 650 where it is determined if all scheduled SI messages have been acquired. In the event that all scheduled SI messages have been acquired, the method 600 ends at stage 660. In the event that all scheduled SI messages have not been acquired, the method 600 returns to stage 620.
As mentioned,
At stage 720, it is determined whether the available SI message is pending acquisition (e.g., the available SI message contains new information or information that has yet to be acquired by the LTE-enabled device)—criterion (1) of “need-based” acquisition. When the available SI message is pending acquisition, the method 700 proceeds to stage 630; otherwise, e.g., the available SI message is a re-transmission carrying previously-acquired information, and the LTE radio 320 may be disabled and control is returned to stage 620. When the LTE radio 320 is disabled, the potentially interfering circuits (such as oscillators, mixers, amplifiers and the like) do not interfere with transmissions to/from the ISM radio 330.
At stage 820, it is determined whether a transmission from a device implementing a co-existing technology is scheduled concurrently with the scheduled acquisition of the available SI message. For example, stage 820 may determine whether an ISM transmission is scheduled concurrently with the scheduled acquisition of the available SI message. The apparatus 300 of
At stage 830, it is determined whether the maximum SI message acquisition delay threshold has been exceeded. When the delay is within (e.g., less than or equal to) the maximum threshold (Yes at stage 830), then the LTE radio 320 may be disabled and control returns to stage 810; otherwise the method 800 advances to stage 630 of
Various embodiments can be implemented, for example, using one or more well-known computer systems, such as computer system 900 shown in
Computer system 900 includes one or more processors (also called central processing units, or CPUs), such as a processor 904. Processor 904 is connected to a communication infrastructure or bus 906.
One or more processors 904 may each be a graphics processing unit (GPU). In an embodiment, a GPU is a processor that is a specialized electronic circuit designed to rapidly process mathematically intensive applications on electronic devices. The GPU may have a highly parallel structure that is efficient for parallel processing of large blocks of data, such as mathematically intensive data common to computer graphics applications, images and videos.
Computer system 900 also includes user input/output device(s) 903, such as monitors, keyboards, pointing devices, etc., which communicate with communication infrastructure xx06 through user input/output interface(s) xx02.
Computer system 900 also includes a main or primary memory 908, such as random access memory (RAM). Main memory 908 may include one or more levels of cache. Main memory 908 has stored therein control logic (i.e., computer software) and/or data.
Computer system 900 may also include one or more secondary storage devices or memory 910. Secondary memory 910 may include, for example, a hard disk drive 912 and/or a removable storage device or drive 914. Removable storage drive 914 may be a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, tape backup device, and/or any other storage device/drive.
Removable storage drive 914 may interact with a removable storage unit 918. Removable storage unit 918 includes a computer usable or readable storage device having stored thereon computer software (control logic) and/or data. Removable storage unit 918 may be a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, and/any other computer data storage device. Removable storage drive 914 reads from and/or writes to removable storage unit 918 in a well-known manner.
According to an exemplary embodiment, secondary memory 910 may include other means, instrumentalities or other approaches for allowing computer programs and/or other instructions and/or data to be accessed by computer system 900. Such means, instrumentalities or other approaches may include, for example, a removable storage unit 922 and an interface 920. Examples of the removable storage unit 922 and the interface 920 may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and/or any other removable storage unit and associated interface.
Computer system 900 may further include a communication or network interface 924. Communication interface 924 enables computer system 900 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference number 928). For example, communication interface 924 may allow computer system 900 to communicate with remote devices 928 over communications path 926, which may be wired and/or wireless, and which may include any combination of LANs, WANs, the Internet, etc. Control logic and/or data may be transmitted to and from computer system 900 via communication path 926.
In an embodiment, a tangible apparatus or article of manufacture comprising a tangible computer useable or readable medium having control logic (software) stored thereon is also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 900, main memory 908, secondary memory 910, and removable storage units 918 and 922, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 900), causes such data processing devices to operate as described herein.
Based on the teachings contained in this disclosure, it will be apparent to persons skilled in the relevant art(s) how to make and use the invention using data processing devices, computer systems and/or computer architectures other than that shown in
The aforementioned description of the specific embodiments will so fully reveal the general nature of the invention that others can, by applying knowledge within the skill of the art, readily modify and/or adapt for various applications such specific embodiments, without undue experimentation, without departing from the general concept of the present invention. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled artisan in light of the teachings and guidance.
References in the specification to “one embodiment,” “an embodiment,” “an exemplary embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
The exemplary embodiments described herein are provided for illustrative purposes, and are not limiting. Other exemplary embodiments are possible, and modifications may be made to the exemplary embodiments within the spirit and scope of the disclosure. Therefore, the specification is not meant to limit the invention. Rather, the scope of the invention is defined only in accordance with the following claims and their equivalents.
Embodiments may be implemented in hardware (e.g., circuits), firmware, software, or any combination thereof. Embodiments may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices and the like. Further, firmware, software, routines, instructions may be described herein as performing certain actions. However, it should be appreciated that such descriptions are merely for convenience and that such actions in fact results from computing devices, processors, controllers, or other devices executing the firmware, software, routines, instructions, etc. Further, any of the implementation variations may be carried out by a general purpose computer.
For purposes of this discussion, the term “module” and the like, shall be understood to include at least one of software, firmware, and hardware (such as one or more circuits, microchips, processors, or devices, or any combination thereof), and any combination thereof. In addition, it will be understood that each module can include one, or more than one, component within an actual device, and each component that forms a part of the described module can function either cooperatively or independently of any other component forming a part of the module. Conversely, multiple modules described herein can represent a single component within an actual device. Further, components within a module can be in a single device or distributed among multiple devices in a wired or wireless manner.
The present disclosure has been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries may be defined so long as the specified functions and relationships thereof are appropriately performed.
It is to be appreciated that the Detailed Description section, and not the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary embodiments of the present disclosure as contemplated by the inventor(s), and thus, are not intended to limit the present disclosure and the appended claims in any way.
