TWI493944B - Reference oscillator arbitration and scheduling for multiple wireless subsystems - Google Patents

Description

Communication system, communication method, and communication device

The present invention relates to cellular communication and, more particularly, to a reference oscillator for cellular communication.

In an electronic device, an oscillator (eg, a digitally controlled crystal oscillator (DCXO)) can be used to generate a periodic signal (eg, a sine wave) at a certain frequency. These repeated signals generated by the oscillator can be used, for example, as clock signals input to various subsystems of the electronic device. Due to the higher cost of manufacturing the oscillator, as more oscillators are incorporated into the device, the cost of manufacturing the device increases. In addition, the inclusion of multiple oscillators in the device can take up board area or semiconductor substrate area that would otherwise be used by other components.

Different subsystems can be associated with different standards. The Bluetooth (BT) subsystem can be designed to meet the requirements of the first standard, and the Wireless Local Area Network (WLAN) subsystem can be designed to meet the requirements of the second standard. These standards have different specifications and requirements for their oscillators. For example, during operation (eg, frequency shifts or abrupt frequency steps performed within the platform using DCXO), each subsystem and associated standard pair reference oscillator characteristics (eg, noise, thermal stability, etc.) And reference oscillator performance, can have different specifications. In addition, a standard can prohibit behaviors such as transmitting at a certain power level, performing some transmissions, and interfering with adjacent channels. Moreover, in some cases, hardware and/or software for implementing various subsystems may impose additional requirements.

According to the present invention, there is provided a communication system comprising: a plurality of subsystems; a reference oscillator coupled to the subsystem, wherein the reference oscillator is Configuring to provide a reference signal to the subsystem; and a controller coupled to the reference oscillator and the subsystem, wherein the controller is configured to: receive a change reference oscillation from a first one of the plurality of subsystems A request for a characteristic of the device; determining whether to process the request based on the priority of the request; in response to determining that the request should be processed, starting the reconfiguration of the reference oscillator to satisfy the preferred request of the first subsystem.

Preferably, the controller is further configured to send a notification to the subsystem that the characteristic of the reference oscillator is about to change before starting the reconfiguration of the reference oscillator. The subsystem is configured to adjust its internal circuitry to compensate for an imminent change in the characteristics of the reference oscillator in response to receiving the notification. The subsystem is configured to temporarily fail in response to receiving the notification.

Preferably, the request contains information about preferred characteristics of the reference oscillator.

Preferably, the first subsystem is a cellular subsystem, and wherein the communication system is implemented on a cellular handset, preferably the subsystem comprises: a Global Positioning System (GPS) subsystem; a Wireless Local Area Network (WLAN) subsystem; Bluetooth subsystem; and Near Field Communication (NFC) subsystem.

Preferably, the controller is further configured to: detect a change in a geographic location of the communication system; determine a new configuration for the reference oscillator based on a current geographic location of the communication system; notify the subsystem that the configuration of the reference oscillator is about to change; The reference oscillator is initially reconfigured as a new configuration. The controller is further configured to: scan the available cellular network after the communication system has begun to wake up; receive information from the available cellular network; and detect the geographic of the communication system based on information from the available cellular network Change in location.

Preferably, the controller is further configured to: determine whether a frequency of communication for the second subsystem conflicts with a frequency requirement of the first subsystem; and if a frequency and communication for communication of the second subsystem If the frequency requirements of the first subsystem conflict, the second subsystem is reconfigured. The controller is further configured to reconfigure the second subsystem by assigning a smaller frequency range to the second subsystem. The controller is further configured to configure the second subsystem by assigning a second time slot that is inconsistent with the first time slot assigned to the first subsystem to the second subsystem. The controller is further configured to reconfigure the second subsystem by assigning the second time slot to the second subsystem, and wherein the second time slot is discontinuously received/transmitted by the first subsystem (DRX) /DTX) The gap is consistent.

Preferably, the controller is further configured to: determine whether assisted GPS (AGPS) support is available to the communication system; and in response to determining that AGPS support is available: to initiate a handover to the AGPS for the location detection function of the communication system, and based on AGPS switches and reconfigures the subsystem.

According to another aspect of the present invention, a method is provided, comprising: receiving a request to change a characteristic of a reference oscillator from a first one of a plurality of subsystems of a communication system; determining whether to process the location based on a priority order of the request And in response to determining that the request should be processed: transmitting a notification that the characteristics of the reference oscillator are about to change to the subsystem, and beginning to reconfigure the reference oscillator to satisfy the preferred requirements of the first subsystem.

Advantageously, the method further comprises: detecting a change in a geographic location of the communication system; determining a new configuration for the reference oscillator based on a current geographic location of the communication system; notifying the subsystem that the configuration of the reference oscillator is imminent Change; and start reconfiguring the reference oscillator as a new match Set.

Advantageously, the method further comprises: determining if a frequency of communication for the second subsystem conflicts with a frequency requirement of the first subsystem; and if the frequency of communication for the second subsystem is related to the first subsystem If the frequency requirements conflict, a smaller frequency range is assigned to the second subsystem.

Advantageously, the method further comprises: determining if a frequency of communication for the second subsystem conflicts with a frequency requirement of the first subsystem; and if the frequency of communication for the second subsystem is related to the first subsystem If the frequency requirements conflict, a second time slot that is inconsistent with the first slot allocated to the first subsystem is assigned to the second subsystem.

Advantageously, the method further comprises: determining whether assisted GPS (AGPS) support is available to the communication system; and in response to determining that AGPS support is available: initiating a switch to AGPS for the location detection function of the communication system, and based on Switch to AGPS and reconfigure the subsystem.

According to still another aspect of the present invention, a communication apparatus includes: a plurality of wireless subsystems; a reference oscillator coupled to a wireless subsystem, wherein the reference oscillator is configured to provide a reference signal to the wireless subsystem; a controller coupled to the reference oscillator and the subsystem, wherein the controller is configured to receive, from the subsystem, a plurality of requests to change a frequency of the reference oscillator; The requests are arranged in order of priority; based on the priority order of the request, the first request is selected; based on the frequency of the reference oscillator, determining whether to process the first request; in response to determining that the first request should be processed; Notifying the subsystem that the characteristics of the reference oscillator are about to change; and initiating the first reconfiguration of the reference oscillator to satisfy the preferred requirements of the first subsystem; A second reconfiguration of the reference oscillator should be initiated to determine that all of the plurality of requests have been processed to adjust the frequency of the reference oscillator to a nominal value.

In the following description, numerous specific details are set forth in the However, it is apparent to those skilled in the art that the present invention, including structures, systems and methods, can be implemented without these specific details. The descriptions and representations herein are the general methods used by those skilled in the art to best convey the substance of their operation to those skilled in the art. In other instances, well-known methods, procedures, components, and circuits have not been described in detail to avoid unnecessarily obscuring aspects of the invention.

The embodiments described with reference to "one embodiment", "an embodiment", "embodiment embodiment", etc., may include specific features, structures, or characteristics, but each embodiment does not need to include specific features or structures. Or characteristics. Moreover, such phrases are not necessarily used in the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with the embodiments, it can be considered that it is within the knowledge of those skilled in the art to make such a feature, structure, or characteristic in combination with other embodiments, whether or not explicitly described.

1. Overview

Embodiments of the present invention provide systems and methods for controlling reference oscillators shared by multiple subsystems within a communication system and for arbitrating the use of reference oscillators in such subsystems. By varying the performance of the reference oscillator as needed by a particular subsystem (eg, by tuning the reference oscillator), the communication system can configure the reference oscillator to meet those particular subsystems. Specifications are required and the reference oscillator can be reconfigured later to meet the requirements of other subsystems.

For example, a central controller and/or an arbiter within the communication system can receive requests from the one or more subsystems using the reference oscillator and adjust the reference oscillator to achieve the characteristics required by the requested subsystem. The central controller can also ensure that other subsystems with conflicting reference oscillator requirements are not adversely affected by the upcoming adjustment of the reference oscillator. For example, the controller can notify each subsystem that the reference oscillator performance is about to change. If the new operational characteristics of the reference oscillator have a negative impact on a particular subsystem, the controller can also allow or disable the operation of the subsystem. In some cases, multiple subsystems can continue to operate even after the reference oscillator has been retuned (eg, because the characteristics of the retuned reference oscillator still meet the requirements of these subsystems). In other cases, some subsystems must be adjusted or disabled before tuning the reference oscillator (for example, because the retuned reference oscillator no longer meets the requirements of these subsystems).

If multiple subsystems require the use of a reference oscillator at the same time, the controller can execute an arbitration scheme to prioritize requests from the subsystem. In one embodiment, the controller can be configured to use a prioritized list to prioritize incoming requests. If the controller receives a higher priority request while the reference oscillator has been configured to be provisioned for a lower priority request, the controller can reconfigure the reference oscillator to meet the need for a higher priority request. For example, when an incoming call is detected, the priority order of the cellular subsystem may be higher than the priority order of the Bluetooth subsystem so that the incoming call is not missed. If the reference oscillator is currently configured to meet the requirements of the Bluetooth subsystem, the controller can reconfigure the parameters. The oscillator is tested to meet the needs of the honeycomb subsystem. After the call has been processed, the controller can selectively re-adjust the reference oscillator to meet the requirements of the Bluetooth subsystem.

By implementing a reference oscillator arbitration scheme in accordance with an embodiment of the present invention, multiple subsystems of a communication system can share a single reference oscillator, which advantageously enables production communication since fewer reference oscillators are needed to support multiple subsystems The manufacturing cost of the system is reduced. Moreover, reducing the number of reference oscillators required within the communication system advantageously reduces the required board area or semiconductor substrate area, which enables the fabrication of smaller and/or more compact devices.

2. Use of a reference oscillator shared in the arbitration subsystem

A system for arbitrating the use of a reference oscillator shared in a subsystem will now be described with reference to FIG. 1 is a block diagram of a communication system 100 including a plurality of subsystems in accordance with an embodiment of the present invention. In an embodiment, communication system 100 is implemented on a communication device (eg, a mobile device such as a cellular handset, smart phone, etc.). However, it should be understood that the components of Figure 1 can be implemented on any electronic device having multiple subsystems that require operation with reference to an oscillator input signal.

In FIG. 1, controller 101 controls reference oscillator 102 (eg, by issuing control commands 118 to reference oscillator 102) and arbitrating the use of reference oscillator 102 in various subsystems of FIG. 1 (eg, by way of an image) System 104-116 issues arbitration information or command 120). In an embodiment, the controller 101 can be implemented as a function internal to discrete components or larger components (eg, data machines). The controller 101 interfaces with a cellular radio frequency (RF) module 104 to provide a cellular communication function as a whole (e.g., for a cellular handset). The controller 101 is also used to provide wireless functions for the communication system Several subsystems are joined. In an embodiment, these wireless subsystems include a Global Positioning System (GPS)/Global Navigation Satellite System (GNSS) subsystem 106, a Wireless Local Area Network (WLAN) subsystem 108, a Bluetooth (BT) subsystem 110, and a frequency modulation (FM) sub- System 112, and near field communication (NFC) subsystem 114. For clarity, the subsystems used to support the wireless function are shown in FIG. However, it should be understood that a number of other subsystems of the communication system (eg, a microphone subsystem, an audio device, a display subsystem, an input/output subsystem, etc.) may be coupled to the controller 101. These other subsystems are represented by square block 116 in FIG.

As noted above, each such subsystem can have different requirements for the reference oscillator 102. Controller 101 can receive requests from each of these subsystems and configure reference oscillator 102 to meet the needs of a particular requested subsystem. In an embodiment, the request sent from the subsystem may include information related to preferred operational characteristics of the reference oscillator, which may include, for example, noise level, oscillation frequency, signal amplitude, or other known oscillator requirements. . The controller 101 can reconfigure the reference oscillator 102 (e.g., using the control command 118) to change the characteristics of the reference oscillator 102 to match (or more closely satisfy) the preferred operational characteristics transmitted in the request from the subsystem. . Although the requests outlined herein are derived from subsystems 104-116, it should be understood that controller 101 may also begin to change the characteristics of reference oscillator 102 based on system performance or common knowledge of the requirements themselves. For example, in an embodiment, controller 101 can detect conditions (eg, potential RF performance impairments) and can generate control commands 118 to re-tune reference oscillator 102.

2.1 Priority of the request

Controller 101 can be configured to perform arbitration on subsystems 104-116 The reference oscillator 102 can be configured to satisfy the needs of the subsystems 104-116 in accordance with a prioritization order. In an embodiment, the arbitration scheme is performed using a prioritized list that is accessible through controller 101 (or implemented on the controller). For example, the controller 101 can access a prioritized list stored in a memory (not shown). In an embodiment, the prioritized list may specify the relative priority of the subsystems 104-116. For example, in an embodiment, the priority order of the Bluetooth subsystem 110 is above the GPS/GNSS subsystem 106, while the priority of the cellular system 104 is above both. The priority list can also specify certain high priority events. For example, an incoming call can be placed in a prioritized list as an event with a very high priority. Although the arbitration scheme performed by controller 101 is described with reference to a prioritized list, it should be understood that controller 101 can be configured to support a variety of methods for determining and prioritizing the subsystems of FIG. Moreover, in an embodiment, the prioritization of subsystems 104-116 can be configured and/or reconfigured by the user based on the needs or requirements of the user.

When controller 101 receives a request from a subsystem for a reference oscillator signal, controller 101 may determine the priority order of the requested subsystem (eg, by checking the prioritized list). If multiple requests are received, the controller 101 can determine the priority order of each of the requests, sort the requests according to their priority order, and store them (eg, stored in queues, stacks, linked lists, Arrays, etc., so that they can be processed in the order of their priorities. When a new request is received, the controller determines its priority and decides when it should be executed based on its prioritization and the priority of the stored request. For example, if the controller 101 currently stores requests from the NFC subsystem 114 and the Bluetooth subsystem 110 and receives indications from the hive subsystem 104 that it has been detected A new request for an incoming call, even if the request of the NFC subsystem 114 and the Bluetooth subsystem 110 has been received earlier, the controller 101 may decide to process the incoming call.

The controller 101 can be configured to assign a priority order in a variety of ways. For example, in an embodiment, the controller 101 may consider the timing of the request when determining how to prioritize the assignment. For example, the controller 101 can assign a higher priority order to earlier requests for earlier requests, thereby ultimately processing all requests. For example, the controller 101 can queue the requests in a prioritized order and can process the events in the order in which they are received, unless a higher priority event is encountered. In another embodiment, each subsystem may be associated with a particular priority order and the requests may be processed according to the priority order of the subsystems, regardless of the order in which the requests are received. For example, in an embodiment, the highest priority order can be assigned to the hive subsystem 104, the second highest priority can be assigned to the GPS/GNSS subsystem 106, the third highest priority can be assigned to the WLAN subsystem 108, and the like.

In some embodiments, upon determining how to prioritize a pending request, the controller 101 will consider the reference oscillator request associated with all pending requests. For example, some subsystems may be associated with less urgent reference oscillator requests than other subsystems. By selecting feature values (eg, frequency, amplitude, etc.) for the reference oscillator to meet the needs of the largest possible number of requested subsystems, the controller 101 can satisfy the subsystems by starting a single reconfiguration of the reference oscillator 102 (relatively Loose) requirements to handle several requests simultaneously.

2.2 Notification Reconfiguration Reference Oscillator

After the controller 101 determines which request should be processed, the controller 101 can determine if the reference oscillator 102 needs to be reconfigured. For example, in some situations In this case, the current configuration of the reference oscillator 102 can support requests from multiple subsystems, so no reconfiguration is required. If the controller 101 determines that the reference oscillator 102 needs to be reconfigured, the controller 101 issues a control command 118 to begin reconfiguring the reference oscillator 102 to satisfy the request of the subsystem associated with the request to be processed. However, in an embodiment, the controller 101 first notifies the subsystems 104-116 that the reference oscillator 102 is about to change to mitigate any potential negative effects that the reconfiguration reference oscillator 102 may have on the subsystems 104-116. For example, in an embodiment, controller 101 can send a message to subsystems 104-116 informing them that the characteristics of reference to oscillator 102 are about to change. The message may contain information relating to upcoming changes in the frequency, amplitude, noise, thermal stability, etc. of the reference oscillator.

In an embodiment, subsystems 104-116 may take action if subsystems 104-116 determine that new characteristics of reference oscillator 102 do not satisfy their subsystem's request (eg, as specified by standard or hardware requests) To mitigate the negative effects of reconfiguring the reference oscillator 102. For example, in an embodiment, each subsystem 104-116 has a corresponding frequency synthesizer and/or phase locked loop (PLL) 122, and subsystems 104-116 use the signal from reference oscillator 102 as an input to its PLL. And the reference, the PLL can include another oscillator, such as a voltage controlled oscillator (VCO). By tuning this internal oscillator, subsystems 104-116 can adjust their own internal circuitry in response to upcoming changes in the frequency of reference oscillator 102 so that they are not subject to the negative effects of reconfiguring reference oscillator 102. influences. When the reference oscillator 102 is reconfigured to its original "nominal" state, these internal oscillators can be retuned to their original frequency or settings.

In some cases, re-tuning the internal oscillator within subsystems 104-116 may not be sufficient to compensate for variations in the characteristics of reference oscillator 102. In such cases, subsystems 104-116 may take further action to mitigate the negative effects of reconfiguring reference oscillator 102. For example, subsystems 104-116 may be temporarily turned off, go to sleep, reduce data rate, etc. until reference oscillator 102 returns to a nominal state that is more advantageous to their operation.

In some embodiments, controller 101 can instruct subsystems 104-116 to take some action before reconfiguring reference oscillator 102. For example, in some embodiments, controller 101 accesses information related to reference oscillator requirements and/or specifications for each subsystem. If the controller 101 determines that the reconfigured reference oscillator 102 no longer meets the requirements of the subsystem, the controller 101 can instruct the subsystem to change its internal circuitry to compensate for the imminent change of the reference oscillator 102. Alternatively, controller 101 may instruct subsystems 104-116 to temporarily turn off, sleep, reduce data rate, etc., to mitigate the effects of reconfiguring reference oscillator 102.

In an embodiment, subsystems 104-116 may take steps to mitigate the negative effects of the reconfigured reference oscillator after reference oscillator 102 has been reconfigured. For example, in an embodiment, subsystems 104-116 can detect changes to reference oscillator 102 without receiving any notification of reconfiguration from controller 101. For example, subsystems 104-116 can detect that the frequency, amplitude, noise, etc. of the signal of reference oscillator 102 no longer meet subsystem requirements. In such cases, the subsystem can change its internal circuitry to make adjustments relative to the upcoming changes in the reference oscillator 102, or to decide to temporarily turn off, sleep, reduce the data rate, and the like.

As mentioned above, some subsystems must be temporarily disabled (for example, closed, Sleep, reduced data rate, etc.) to avoid the potential negative effects of reconfiguring the reference oscillator 102. However, once the reference oscillator 102 is reconfigured, these subsystems can be restarted. In an embodiment, once the reference oscillator 102 has been reconfigured to meet the requirements of these subsystems, the controller 101 can issue instructions to the currently stopped subsystem. For example, once the reference oscillator is reconfigured to meet the operational state of the various requirements of the reference oscillator, the controller 101 can instruct these subsystems to reconfigure the internal circuitry, power up, exit sleep mode, increase data rate, and the like. In some embodiments, subsystems 104-116 can automatically detect reconfiguration of the reference oscillator and can reconfigure internal circuitry, power up, exit sleep mode, increase data rate, etc. without having to receive this from controller 101. instruction.

2.3 Reconfiguring the Reference Oscillator

After the controller 101 has notified the subsystems 104-116 that the reference oscillator 102 is about to be reconfigured, the controller 101 can issue a control command 118 to begin reconfiguring the reference oscillator 102 to satisfy the request to be processed (ie, prioritization The highest request) the requirements of the relevant subsystem. For example, to process an incoming call, the controller 101 issues a control command 118 to begin reconfiguring the reference oscillator 102 to satisfy the request of the cellular subsystem 104. As noted above, in an embodiment, the preferred operational characteristics of the reference oscillator 102 may specify these requests within the request. After the highest priority request has been processed, the controller 101 can process all remaining requests in order of priority until all requests are processed. If there are no unprocessed requests, the controller 101 can issue a command to reconfigure the reference oscillator 102 to a nominal (ie, default) state.

As described above, the controller 101 issues a control command 118 to begin re-starting The reference oscillator 102 is configured. With control command 118, controller 101 retunes reference oscillator 102 to meet the requirements of the subsystem associated with the highest priority request. In an embodiment, control command 118 is a set of one or more instructions that begin to reconfigure one or more capabilities of reference oscillator 102. For example, control command 118 may reconfigure reference oscillator 102 to support, for example, a center based on a request from a related subsystem (eg, a request imposed by a corresponding standard or hardware and/or software used to implement various subsystems) Different requests for performance such as frequency, signal amplitude, noise, and thermal stability.

As described above, the requesting subsystem can notify controller 101 of the new preferred characteristics of the oscillator within the request. However, it should be understood that in an embodiment, the controller 101 does not necessarily reconfigure the reference oscillator 102 using the preferred characteristics transmitted within the request. For example, in an embodiment, controller 101 may access a table of optimal reference oscillator characteristics for each subsystem. When the controller 101 decides to process a request from a particular subsystem, the controller 101 can access the table, determine the best reference oscillator characteristics for the particular subsystem based on the information in the table, and based on these The best feature is to reconfigure the reference oscillator 102.

2.4 Method of Arbitration Request

A method of arbitrating a request to change the frequency of a reference oscillator shared among a plurality of subsystems will be described with reference to FIGS. 1 and 2. In step 200, a plurality of requests to configure the frequency of the reference oscillator are received. For example, controller 101 can receive multiple requests from subsystems 104-116 to configure the frequency of reference oscillator 102. In step 202, the priority order of these requests is determined. For example, controller 101 may determine (eg, based on a prioritized list) that the priority order requested based on cellular system 104 should be greater than that of WLAN subsystem 108 The priority is high. After the controller 101 prioritizes these requests, in step 204, the controller 101 begins processing the request with the highest priority. However, in an embodiment, prior to beginning the reconfiguration, the controller 101 first notifies the other subsystems that the reference oscillator 102 is about to change.

In step 206, the subsystem reference oscillator can be notified of an imminent change. For example, in an embodiment, controller 101 sends a message to subsystems 104-116 informing them that controller 101 will soon change the frequency of reference oscillator 102 to a new value. These subsystems can then take action to mitigate any potential negative effects caused by reconfiguring the reference oscillator 102. Controller 101 can also selectively take action to mitigate the effects of reconfiguring reference oscillator 102 on subsystems 104-116. For example, if the characteristics of the reconfigured reference oscillator 102 no longer meet the specifications and/or requirements of any of the subsystems 104-116, the controller 101 can minimize the impact of such reconfiguration on these subsystems (eg, By instructing these subsystems to reconfigure internal circuitry, power down, go into sleep mode, reduce their data rate, etc.).

In step 208, the configuration of the oscillator's request that satisfies the highest priority request is initiated (e.g., by control command 118). For example, controller 101 may begin to configure reference oscillator 102 to meet specifications and/or requests of cellular subsystem 104. As described above, the controller 101 issues a control command 118 to begin reconfiguring the reference oscillator 102 to satisfy the request of the subsystem associated with the highest priority request. In an embodiment, control command 118 is a set of one or more instructions that begin to reconfigure one or more performance of reference oscillator 102.

After the controller 101 has processed the request, the controller 101 You can then start processing the next highest priority request. If there are no unprocessed requests, the controller 101 can issue a command to reconfigure the reference oscillator 102 to a nominal (ie, original) state. The reference oscillator 102 can remain in this nominal state until the controller 101 receives another request for reconfiguration.

2.5 examples

An example of a request to arbitrate changing the frequency of a reference oscillator shared among a plurality of subsystems will now be described with reference to FIG. During the hive conversion, if the frequency of the reference oscillator 102 is within a certain range, the hive subsystem 104 can be directed to a particular channel where RF performance is known to be impaired. Since this can cause problems for proper cellular operation, a request can be sent to controller 101 to adjust the frequency of reference oscillator 102 to a frequency outside of the problem range. The request optionally includes information identifying the frequency region of the request for proper operation of the hive subsystem 104. In one embodiment, the hive subsystem 104 can generate the request for the controller 101. In another embodiment, the controller 101 can detect potential RF performance impairments and generate requests themselves.

Since the request involves the hive subsystem 104, the request may have a higher priority. After the controller 101 determines that the request should be processed (e.g., the request becomes the highest priority request), the controller 101 takes action to mitigate any negative effects caused by the reconfiguration reference oscillator 102 to the subsystems 104-116. For example, in one embodiment, controller 101 can notify subsystems 104-116 that the characteristics of reference oscillator 102 are about to change, and/or indicate that these subsystems are adjusted as necessary (eg, by instructing these subsystems to reconfigure internals) Circuit, temporarily shut down, go to sleep, reduce data rate, etc.). Then, the controller 101 The configuration of the reference oscillator 102 is changed by transmitting control commands 118 (e.g., to change its frequency), which causes the frequency of the reference oscillator 102 to be moved to the requested region for proper operation of the cellular subsystem 104.

When the honeycomb is handed over to a non-impaired channel, the honeycomb subsystem 104 may request that the frequency of the reference oscillator 102 be restored to a nominal operational state (eg, a nominal operating frequency). Once the request becomes the highest priority request, the controller 101 can notify the subsystems 104-116 that the characteristics of the reference oscillator 102 are about to change, and/or can indicate these subsystems to make adjustments if necessary (eg, by indicating these subsystems) Reconfigure the internal circuit, restart, wake up from sleep, increase the nominal data rate t, etc.). Controller 101 can then begin to reconfigure reference oscillator 102 to a nominal operational state.

3. Arbitration based on parameters affecting multiple subsystems

In some embodiments, controller 101 can configure subsystems 104-116 based on parameters affecting multiple subsystems, including: geographic awareness, spectrum occupancy awareness, and determining the availability of assisted GPS (AGPS) functionality. To this end, the controller 101 is in communication with each subsystem 104-116 and knows the status of each subsystem. The communication system 100 can be further optimized by considering these additional parameters when configuring the subsystems 104-116. Systems and methods for implementing geographic awareness, spectrum occupancy awareness, and AGPS functionality are now described.

3.1 Geographical awareness

Supports specific hive/WiFi/Bluetooth band mixing in multiple geographic regions of the Earth. This band mixing can be different from the band mixing supported in other areas. For example, a frequency band assigned to any of the subsystems 104-116 within the first geographic area (eg, North America) is assigned to the second geographic area (eg, The frequency bands of any of the subsystems 104-116 within Japan can vary. Since the optimal band configuration of subsystems 104-116 can vary with geographic location, subsystems 104-116 should ideally be configured based on existing geographic locations. Moreover, by configuring communication system 100 based on the current geographic location, certain requirements imposed by local standards can be ignored when the communication system is not within a certain geographic area. For example, if there is no Global System for Mobile Communications (GSM) network in the current geographic location (eg, Japan), then communication system 100 does not need to meet the requirements of the GSM standard, which allows for more flexible configuration of other subsystems 104-116.

In one embodiment, subsystems 104-116 may be configured according to spectrum allocations within a particular geographic area. Subsystems 104-116 may be configured to recognize the current geographic area when awake, when exiting standby mode, or by periodically checking the current geographic area. For example, when the hive subsystem 104 scans and identifies the cellular network, it can determine which geographic area the communication system 100 is in based on the unique identification of the cellular service provider. Alternatively, the GPS/GNSS subsystem 106 may also begin to check the current geographic area and may send information to the controller 101 if the current geographic area has changed.

In one embodiment, the controller 101 can remember the current geographic area and can determine if the current geographic area has changed (eg, by starting the check after waking up the communication system 100). If the controller 101 detects a change in the current geographic area, the controller 101 can begin reconfiguring the communication system 100 for the new geographic area. In one embodiment, reconfiguring communication system 100 may require access to information related to the supported frequency bands for subsystems 104-106 in the new geographic area. Band information can be obtained in a variety of ways. For example, you can represent Information on the range of frequencies supported in the geographic location for cellular communication is communicated to the communication system 100 when the cellular system 104 is connected to the server provider. Controller 101 can then select a frequency for reference oscillator 102 based on the supported frequency range. For example, controller 101 can determine that reference oscillator 102 should be tuned to the middle of this frequency range. In one embodiment, the frequency bands for WLAN subsystem 108, Bluetooth subsystem 110, and NFC subsystem 114 may also be obtained in a similar manner when communication system 100 scans local Bluetooth devices, NFC devices, and WiFi networks. News.

In one embodiment, the band information may be stored in a memory (not shown) of communication system 100 that controller 101 may acquire. For example, the stored frequency band information can include information related to the optimal frequency bands for the subsystems 104-106 that depend on the geographic location of the communication system 100. In one embodiment, the stored frequency band information may be updated periodically to ensure accuracy. Alternatively, the band information may be downloaded (eg, from one or more service providers) whenever the controller 101 detects a change in the current geographic location. The controller 101 can use the band information to determine a new best or preferred frequency band for the subsystem.

Once controller 101 has determined a new optimal frequency band for subsystems 104-116, controller 101 may begin to reconfigure reference oscillator 102 as a new optimal frequency value based on the current geographic location. Prior to retuning the reference oscillator 102, the subsystems 104-116 can adjust their internal circuitry (eg, an internal PLL with a VCO) with changes to the expected reference oscillator 102. If one or more of the subsystems 104-116 are not adequately supported in any geographic area, the subsystems may be temporarily turned off, put to sleep, or operated at a reduced data rate. Reference oscillation After the device 102 and the subsystems 104-116 are reconfigured, the communication system 100 should be ideally configured to operate within a new geographic location.

A method of configuring a plurality of subsystems sharing one reference oscillator based on geographic awareness will be described with reference to FIGS. 3 and 1. In step 300, a change in the geographic location of the communication system 100 is detected. For example, when the hive subsystem 104 scans and identifies the cellular network, it can determine the geographic area in which the communication system 100 is located based on the unique identification of the cellular service provider and can forward the information to the controller 101. In one embodiment, the service provider may also notify the communication system of the supported frequency ranges for cellular communication within the geographic area. In step 302, a new frequency (or other new configuration of reference oscillator performance, such as noise performance) for the reference oscillator is determined based on the new geographic location. For example, in one embodiment, controller 101 may select a new frequency for reference oscillator 102 based on a supported frequency range for cellular communication within the geographic region to improve cellular communication. In another embodiment, controller 101 can select new noise performance for reference oscillator 102.

In step 304, the subsystems 104-116 may be notified that the reference oscillator is about to change. For example, in one embodiment, controller 101 can send a message to subsystems 104-116 informing them that controller 101 will soon change the frequency of reference oscillator 102 or some other characteristic to a new value. These subsystems can then take action to mitigate any negative effects that may result from reconfiguring the reference oscillator 102. In step 306, controller 101 tunes the reference oscillator to a new frequency or modifies some other characteristics of reference oscillator 102. For example, controller 101 can begin to configure reference oscillator 102 using control commands 118.

3.2 Spectrum occupation awareness

Each subsystem 104-116 can occupy a portion of the spectrum (simultaneously or sequentially). As noted above, the particular spectrum segments for the reception and transmission of data for any of the subsystems 104-116 may vary based on geographic location. In some cases (eg, due to current spectrum allocation and/or congestion), the operation of one subsystem can negatively impact the operation of another subsystem.

For example, in one embodiment, the honeycomb subsystem 104 can be allocated approximately forty frequency bands from 700 MHz to 3.5 GHz for cellular operations (eg, 3G and 4G). The WLAN subsystem 108 can be allocated a frequency band from 2.5 GHz to 5 GHz for WLAN/WiFi functionality. The Bluetooth subsystem 110 can operate at 2.5 GHz, while the GPS/GNSS subsystem 106 can operate at 1.5 GHz. However, it should be understood that these values are used as examples and are not limiting. As described in the values provided above, the frequency bands assigned to the subsystems may overlap. This overlap can have a negative impact on performance. For example, if the spectrum allocated to the WLAN is too close to the spectrum allocated to the 4G channel, the WiFi communication using the WLAN subsystem 108 can negatively impact the 4G (fourth generation cellular wireless standard) channel. In one embodiment, the controller 101 can be configured to use spectrum occupancy awareness to avoid such collisions between subsystems.

For example, in one embodiment, controller 101 recognizes the occupancy of the current broadcast spectrum and arbitrates from the subsystem based on which subsystems are receiving and transmitting and which frequencies and/or spectrum segments are being used for receiving and transmitting data. 104-106 request. The controller 101 can use this information to minimize congestion, thereby minimizing unnecessary subsystem downtime by optimally utilizing subsystems 104-116 to better address quality of service (QoS) requirements, and/or Reducing the blocking state of the RF receiver (ie, the state within the receiver in which a cutoff frequency signal causes the connection The received signal is suppressed).

In one embodiment, channel assignments for non-homed subsystems (eg, WLAN subsystem 108 and Bluetooth subsystem 110) may be specified by communication system 100 (eg, by controller 101). However, the channel assignment for the cellular function is specified by the cellular service provider network. For example, when communication system 100 is in communication with a cellular service provider (e.g., via a base station), information about the spectrum used for cellular communication can be transmitted to communication system 100. Thus, in one embodiment, the controller 101 can redistribute the channels used by the non-homed subsystems such that the channels do not interfere with the channels specified by the cellular network.

For example, if the spectrum allocated to the WLAN is close to the 4G spectrum, the controller 101 can ensure that the WLAN does not operate at the spectrum that negatively affects the 4G communication. In one embodiment, if the 4G communication is active, the controller 101 may temporarily allocate a different and/or smaller spectrum to the WLAN. For example, controller 101 can send a message to WLAN subsystem 108 indicating that the internal circuitry of WLAN subsystem 108 is tuned to use a different frequency range or a smaller spectrum within the current frequency range.

By placing different (e.g., non-simultaneous) time slots to non-homed subsystems (e.g., WLAN subsystem 108 or Bluetooth subsystem 110) such that the non-homed subsystems are placed while the cellular subsystem 104 is active Inactive, the controller 101 can also prevent non-homed subsystems from adversely affecting the honeycomb subsystem 104. In addition, controller 101 may utilize cellular discontinuous receive/transmit (DRX/DTX) gaps (gaps) to allow non-homed subsystems to be active (ie, transmit and receive data) while cellular subsystem 104 is active. In other words, the controller 101 can assign time slots to non-homed subsystems such that they are only in the cellular subsystem 104 is active when it encounters a DRX/DTX gap. Alternatively, if the 4G communication is active, the controller 101 may temporarily disable the WLAN (eg, by temporarily disconnecting the WLAN subsystem 108 or bringing the WLAN subsystem 108 into a sleep mode).

A method of configuring a plurality of subsystems sharing one reference oscillator based on spectrum occupancy awareness will now be described with reference to FIGS. 4 and 1. In step 400, a determination is made as to whether the frequency of communication for the non-homed subsystem conflicts with the request of the hive subsystem 104. For example, WiFi communication using WLAN subsystem 108 may conflict with requests from cellular subsystem 104 due to overlapping frequency ranges for WiFi and cellular communications. This overlapping frequency range can cause, for example, undesired interference, blocking conditions, blockages, unnecessary subsystem downtime, and/or RF receiver blocking conditions.

If no subsystem conflicts are detected in step 400, then no subsystems are reconfigured in step 401. If a subsystem conflict is detected in step 400, then a new configuration of the non-homed subsystem is determined in step 402. For example, controller 101 may determine that conflicts between subsystems may temporarily assign different and/or smaller frequency ranges to conflicting subsystems while the cellular communication is in an active state (eg, WLAN subsystem) 108) to solve. In one embodiment, controller 101 sends a message to the conflicting subsystem, instructing the subsystem to change its internal circuitry (eg, by adjusting its internal oscillator such that it operates with a smaller frequency range). Alternatively, controller 101 may determine that conflicts between subsystems may be by assigning different (eg, non-simultaneous) time slots to a conflicting non-homed system (eg, to WLAN subsystem 108) This is resolved when the hive subsystem 104 is in an active state while it is active. In one embodiment, the controller 101 The time slots can be assigned to the conflicting non-homed subsystem such that it is active only when the cellular subsystem 104 encounters the DRX/DTX gap. In step 404, controller 101 begins reconfiguring the non-homed subsystem. For example, controller 101 may instruct a conflicting subsystem (eg, WLAN subsystem 108) to use a different and/or smaller frequency range, or may assign a time slot to a conflicting subsystem to resolve the conflict.

3.3 Minimize the impact of GPS sensitivity requirements

Although the channel assignments of some non-homed subsystems (eg, WLAN subsystem 108 or Bluetooth subsystem 110) can be dynamically changed, due to GPS/GNSS sensitivity requirements (eg, due to GPS/GNSS input signals from satellites relative to other The input signal to the subsystem is very low), so the channel assignment of the GPS/GNSS subsystem 106 cannot be easily changed. In some geographic locations, an assisted global positioning system (AGPS) can be used. AGPS uses a cellular network for triangulation and improves GPS functionality. For example, AGPS can improve GPS performance and get a faster time to first fix (TTFF). Since AGPS uses terrestrial cellular network equipment, the signal from AGPS is much stronger than the GPS signal from the satellite.

In one embodiment, the GPS/GNSS subsystem 106 uses AGPS for position detection functionality when AGPS is available. Controller 101 can begin to switch to AGPS. Since the AGPS signal is stronger, switching to AGPS enables the communication system 100 to have more freedom to configure other subsystems without interrupting GPS lock or generating interference to the GPS receiver. In addition, AGPS can operate in a different frequency band than GPS, which provides greater flexibility to controller 101 to configure subsystems 104-116.

The use of assisted GPS (AGPS) will now be described with reference to FIGS. 5 and 1. A function to configure a method of sharing multiple subsystems of a reference oscillator. In step 500, a determination is made whether AGPS support is available. For example, the GPS/GNSS subsystem 106 can periodically perform a scan for an AGPS enabled service provider and can forward this information to the controller 101. If no AGPS support is available, then the reconfiguration of the GPS subsystem does not begin in step 501. If AGPS support is available, then in step 502, switching to AGPS for the location detection function begins. For example, controller 101 can instruct GPS/GNSS subsystem 106 (and/or honeycomb subsystem 104) to switch to AGPS. As described above, switching to AGPS provides greater flexibility to the communication system 100 since the AGPS function provides greater freedom to the communication system to configure other subsystems, and since AGPS can operate in a frequency band different from GPS, switching to AGPS provides greater flexibility to the communication system 100. To configure other subsystems.

In step 504, the subsystems of communication system 100 are reconfigured based on the additional flexibility provided by AGPS support. For example, if the AGPS uses a frequency band other than GPS, the controller 101 can re-tune the circuitry of the other subsystems to include the frequency range previously used by the GPS. Furthermore, since the reduced sensitivity requirements caused by switching to AGPS enable the subsystem to use a larger frequency band without interference with GPS calculations, the controller 101 can instruct the subsystem of the communication system 100 to tune the internal circuitry to use a larger Frequency band.

4. Example computer system implementation

It will be apparent to those skilled in the relevant art that the various elements and features of the present invention described herein can be implemented by one or more general purpose or special purpose processors using hardware and software using analog and/or digital circuits. Or as a combination of hardware and software.

In view of the integrity, the following describes a general purpose computer system. Implementation of the invention The method can be implemented by a combination of hardware or hardware and software. Thus, embodiments of the invention may be implemented in the context of a computer system or other processing system. An example of such a computer system 600 is shown in FIG. Some or all of the modules described in FIG. 1 (eg, controller 101, subsystems 104-116, etc.) may be implemented using one or more different computer systems 600. Moreover, each step of the flowcharts depicted in Figures 2 through 5 can be performed on one or more different computer systems 600.

Computer system 600 includes one or more processors, such as processor 604. Processor 604 can be a dedicated or general purpose digital signal processor. The processor 604 is coupled to a communication infrastructure 602 (e.g., a bus or network). Various software implementations are described with respect to the computer system of this embodiment. After reading this specification, it will be apparent to those skilled in the relevant art how to implement the present invention using other computer systems and/or computer structures.

Computer system 600 also includes main memory 606, preferably including random access memory (RAM), and also includes auxiliary memory 608. The auxiliary memory 608 can include, for example, a hard disk drive 610 and/or a removable storage drive 612, representing a floppy disk drive, a tape drive, a compact disk drive, and the like. Removable storage drive 612 reads and/or writes removable storage unit 616 in a well known manner. The removable storage unit 616 represents a floppy disk, a magnetic tape, a compact disc, etc., which is read and written by the removable storage drive 612. Those skilled in the relevant art will appreciate that the removable storage unit 616 includes a computer usable storage medium having stored therein computer software and/or material.

In alternative embodiments, the auxiliary memory 608 can include other similar devices that allow computer programs or other instructions to be loaded into the computer system 600. Such a device may include, for example, a removable storage unit 618 and interface 614. Examples of such devices may include a cartridge and a box interface (eg, visible within a video game device), a removable memory chip (eg, EPROM or PROM), and associated sockets, thumb drives (thumb drive) And USB ports, and other removable storage units 618 and interfaces 614 that allow software and material to be transferred from the removable storage unit 618 to the computer system 600.

Computer system 600 can also include a communication interface 620. Communication interface 620 allows for the transfer of software and data between computer system 600 and external devices. Examples of communication interface 620 may include a data machine, a network interface (e.g., an Ethernet network card), a communication port, a PCMCIA slot and card, and the like. The software and material transmitted via communication interface 620 is in the form of a signal that is an electrical, electromagnetic, optical, or other signal that can be received by communication interface 620. These signals are provided to communication interface 620 via communication path 622. Communication path 622 carries signals and can be implemented using wires or cables, fiber optics, telephone lines, cellular telephone links, radio frequency links, and other communication channels.

As used herein, the terms "computer program medium" and "computer readable medium" are used to refer to a tangible storage medium, such as removable storage units 616 and 618 or a hard disk mounted within hard disk drive 610. These computer program products are devices that provide software to the computer system 600.

Computer programs (also referred to as computer control logic) are stored in main memory 606 and/or auxiliary memory 608. The computer program can also be received via the communication interface 620. When executing such a computer program, these programs enable computer system 600 to perform the invention described herein. In particular, when executing such a computer program, these programs can cause processor 604 to perform the processes of the present invention, such as any of the methods described herein. Therefore, such a computer program represents a controller of the computer system 600. Using software to implement the present invention The software can be stored in a computer program product and loaded into computer system 600 using removable storage drive 612, interface 614, or communication interface 620.

In another embodiment, features of the invention are performed primarily in a hard body using, for example, hardware components (e.g., dedicated integrated circuit (ASIC) and gate arrays). It is also apparent to those skilled in the relevant art to implement a hardware state machine to perform the functions described herein.

5 Conclusion

It is to be understood that the specific embodiments, rather than the The Abstract may describe one or more but not all of the embodiments of the present invention as contemplated by the inventors, and thus, in no way, is intended to limit the scope of the invention and the appended claims.

The invention has been described above with the aid of a functional building block that shows embodiments of its particular functions and relationships. The boundaries of these functional building blocks have been arbitrarily defined herein for ease of description. Optional boundaries can be defined as long as their specific functions and relationships are properly performed.

The above description of the specific embodiments fully discloses the generality of the invention, so that one can easily modify and/or adjust, for example, a specific embodiment, without departing from the general inventive concept. The application, without undue experimentation, does not depart from the main concepts of the invention. Therefore, such adaptations and modifications are intended to be within the meaning and range of the embodiments of the invention. It should be understood that the phraseology or terminology herein is for the purpose of description and description

Typical signal processing functions (e.g., channel and source decoders, etc.) described herein may be implemented in hardware, software, or some combination thereof. As will be appreciated by those skilled in the art based on the discussion presented herein, computer processing functions can be implemented using computer processors, computer logic, application specific circuits (ASICs), digital signal processors, and the like. Accordingly, any processor that performs the signal processing functions described herein is within the scope and spirit of the invention.

The above systems and methods can be implemented as a computer program, computer program product, or tangible and/or non-transitory computer readable medium having stored instructions. For example, the functions described herein may be implemented by computer program instructions executed by a computer processor or any of the hardware devices described above. Computer program instructions cause the processor to perform the signal processing functions described herein. Computer program instructions (eg, software) can be stored in tangible, permanently usable media, computer program media, or any storage medium that can be accessed by a computer or processor. Such media include memory devices such as RAM or ROM, or other types of computer storage media such as computer magnetic disks or CD ROMs. Accordingly, any tangible, permanent computer storage media having computer program code that causes the processor to perform the signal processing functions described herein is within the scope and spirit of the present invention.

While the various embodiments of the invention have been described, the embodiments It will be apparent to those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of the invention. Therefore, the scope and breadth of the invention should not be construed as being limited

100‧‧‧Communication system

101‧‧‧ Controller

102‧‧‧Reference oscillator

104‧‧‧Hive (RF) subsystem

106‧‧‧Global Positioning System (GPS)/Global Navigation Satellite System (GNSS) subsystem

108‧‧‧Wireless Local Area Network (WLAN) Subsystem

110‧‧‧Bluetooth (BT) Subsystem

112‧‧‧FM (FM) subsystem

114‧‧‧Communication (NFC) subsystem

116‧‧‧Other subsystems

118‧‧‧Control order

120a‧‧‧ Order

120b‧‧‧ Order

Order 120c‧‧‧

Order 122a‧‧‧

122b‧‧‧ Order

Order 122c‧‧‧

122d‧‧‧ Order

Order 122e‧‧‧

Order of 122f‧‧

200‧‧‧ Multiple requests to receive the frequency of the reference oscillator from multiple subsystems

202‧‧‧Determining the priority of the request

204‧‧‧Start processing the highest priority request

206‧‧‧Notice that the subsystem reference oscillator is about to change

208‧‧‧ Start configuring the reference oscillator to meet the highest priority request requirements

300‧‧‧Detecting changes in the geographical location of the communication system

302‧‧‧New configuration for determining one or more properties of the reference oscillator based on the new geographic location

304‧‧‧Notice that the subsystem reference oscillator is about to change

306‧‧‧Reconfigure the reference oscillator

400‧‧ Is the frequency of communication for non-honeycomb systems conflicting with the requirements of the hive subsystem?

401‧‧‧Do not start reconfiguring subsystems

402‧‧‧If new configurations are detected for non-honeycomb systems if a conflict with the requirements of the hive subsystem is detected

404‧‧‧ Beginning to reconfigure conflicting non-homed subsystems

500‧‧‧AGPS support available?

501‧‧‧Do not start reconfiguring the GPS subsystem

502‧‧‧Start switching to AGPS for position detection

504‧‧Reconfigure subsystem based on additional flexibility provided by AGPS support

600‧‧‧ computer system

602‧‧‧Communication infrastructure

604‧‧‧ processor

606‧‧‧ main memory

608‧‧‧Auxiliary memory

610‧‧‧ hard disk drive

612‧‧‧Removable storage drive

614‧‧ interface

616‧‧‧Removable storage unit

618‧‧‧Removable storage unit

620‧‧‧Communication interface

622‧‧‧Communication path

1 is a block diagram of a system for use of a reference oscillator shared in an arbitration subsystem; FIG. 2 is a flow diagram of a method of arbitrating a request to change the frequency of a reference oscillator shared among a plurality of subsystems; A flowchart of a method for configuring a plurality of subsystems sharing a reference oscillator based on geographic awareness; FIG. 4 is a flowchart of a method for configuring a plurality of subsystems of a shared reference oscillator based on spectrum occupancy awareness; FIG. 5 is for assisting A flowchart of a method of configuring a plurality of subsystems sharing a reference oscillator with the availability of a GPS (AGPS) function; Figure 6 shows an embodiment computer system that can be used to implement aspects of the present invention.

100‧‧‧Communication system

101‧‧‧ Controller

102‧‧‧Reference oscillator

104‧‧‧Hive (RF) subsystem

106‧‧‧Global Positioning System (GPS)/Global Navigation Satellite System (GNSS) subsystem

108‧‧‧Wireless Local Area Network (WLAN) Subsystem

110‧‧‧Bluetooth (BT) Subsystem

112‧‧‧FM (FM) subsystem

114‧‧‧Communication (NFC) subsystem

116‧‧‧Other subsystems

118‧‧‧Control order

120a‧‧‧ Order

120b‧‧‧ Order

Order 120c‧‧‧

Order 122a‧‧‧

122b‧‧‧ Order

Order 122c‧‧‧

122d‧‧‧ Order

Order 122e‧‧‧

Order of 122f‧‧

Claims (8)

A communication system comprising: a plurality of subsystems; a reference oscillator coupled to the subsystem, wherein the reference oscillator is configured to provide a reference signal to the subsystem; and a controller coupled to the a reference oscillator and the subsystem, wherein the controller is configured to receive a request to change a characteristic of the reference oscillator from a first one of the plurality of subsystems; based on a priority order of the request Determining whether to process the request; in response to determining that the request should be processed, reconfiguring the reference oscillator to satisfy a request of the first subsystem; detecting a change in a geographic location of the communication system; Determining a new configuration for the reference oscillator based on a current geographic location of the communication system; notifying the subsystem that the configuration of the reference oscillator is about to change; and beginning to reconfigure the reference oscillator to be new Configuration. The communication system of claim 1, wherein the controller is further configured to transmit to the subsystem the characteristics of the reference oscillator are about to occur before starting the reconfiguration of the reference oscillator Notification of change. The communication system of claim 1, wherein the request includes information regarding preferred characteristics of the reference oscillator. The communication system of claim 1, wherein the controller is further configured to: Determining whether a frequency of communication for the second subsystem conflicts with a frequency requirement of the first subsystem; and if a frequency of communication for the second subsystem is related to a frequency requirement of the first subsystem In case of conflict, the second subsystem is reconfigured. A communication method for changing a reference oscillator configuration, comprising: receiving a request to change a characteristic of a reference oscillator from a first one of a plurality of subsystems of a communication system; determining whether to process the request based on a priority order of the request Requesting; and in response to determining that the request should be processed: transmitting to the subsystem a notification that the characteristics of the reference oscillator are about to change, beginning to reconfigure the reference oscillator to satisfy the preferences of the first subsystem Requesting; determining whether a frequency of communication for the second subsystem conflicts with a frequency requirement of the first subsystem; and if a frequency of communication for the second subsystem is related to a frequency of the first subsystem If the requirements conflict, a smaller frequency range is assigned to the second subsystem. The method of claim 5, further comprising: detecting a change in a geographic location of the communication system; determining a new configuration for the reference oscillator based on a current geographic location of the communication system; The configuration of the reference oscillator is about to change; and the reconfiguration of the reference oscillator to a new configuration begins. The method of claim 5, further comprising: determining whether a frequency of communication for the second subsystem is related to the first subsystem Frequency requirements conflict; and if the frequency of communication for the second subsystem conflicts with the frequency requirement of the first subsystem, it will be inconsistent with the first time slot assigned to the first subsystem The second time slot is assigned to the second subsystem. A communication device comprising: a plurality of wireless subsystems; a reference oscillator coupled to the wireless subsystem, wherein the reference oscillator is configured to provide a reference signal to the wireless subsystem; and a controller, Coupled to the reference oscillator and the subsystem, wherein the controller is configured to receive, from the subsystem, a plurality of requests to change a frequency of the reference oscillator; prioritizing the requests Arranging; based on a priority order of the request, selecting a first request; determining whether to process the first request based on a frequency of the reference oscillator; responding to determining that the first request should be processed: sending to the subsystem Notifying that the characteristics of the oscillator are about to change; and initiating a first reconfiguration of the reference oscillator to satisfy the request of the first subsystem; detecting a change in the geographic location of the communication system; a current geographic location, determining a new configuration for the reference oscillator; notifying the subsystem that the configuration of the reference oscillator is about to change; Response to determining that all of said plurality of requests have been processed in A second reconfiguration of the reference oscillator is initiated to adjust the frequency of the reference oscillator to a nominal value.