Bidirectional communication for front-end modules (FEMs)
By realizing the bidirectional communication bus between FEM and BBP in a mobile communication device, using tunneling technology for information exchange, the problem of one-way communication limitation is solved, dynamic optimization and performance improvement of FEM are achieved, and adapting to higher frequency and complexity is achieved. Wireless standard requirements.
Patent Information
- Application Number
- CN202380035746.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-10-14
- Filing Date
- 2023-05-19
- Publication Date
- 2024-12-06
AI Technical Summary
The communication between the front-end module (FEM) and the baseband processor (BBP) in existing mobile communication devices is mainly one-way, limiting the dynamic optimization and performance adjustment of FEM, and cannot effectively cope with the pressure and improvement caused by higher frequencies. Complex wireless standard requirements.
By implementing a bidirectional communication bus between FEM and BBP, using tunneling technology and drivers to exchange information with control circuits, FEM and BBP are allowed to dynamically adjust operating parameters based on real-time information to optimize performance.
It realizes more dynamic control of FEM, improves the performance of mobile communication devices, can more effectively adapt to higher frequency and complex wireless standards, and improves processing capabilities and user experience.
Smart Images

Figure CN119096470A_ABST
Abstract
Description
[0001] Priority application
[0002] This application is related to U.S. Provisional Patent Application No. 63 / 379,514, filed on October 14, 2022, entitled “BIDIRECTIONAL COMMUNICATION FOR FRONT END MODULE (FEM)”, the contents of which are incorporated herein by reference in their entirety.
[0003] This application is related to U.S. Provisional Patent Application No. 63 / 347,639, filed on June 1, 2022, entitled “SMARTPATH WITH SMART FEM FOR DYNAMIC AND ADAPTIVEOPTIMIZATION OF TX AND RX PATH IN MOBILE FRONT ENDS,” the contents of which are incorporated herein by reference in their entirety. Technical Field
[0004] The technology of the present disclosure generally relates to a front end module (FEM) in a mobile device, and particularly to communication between a baseband module and the FEM in a mobile device. Background Art
[0005] In modern society, computing devices are ubiquitous, and more specifically, mobile communication devices are becoming more and more common. The popularity of these mobile communication devices is driven in part by the many features currently enabled on such devices. The increase in processing power in such devices has meant that mobile communication devices have evolved from pure communication tools to complex mobile entertainment centers, thereby enhancing the user experience. With the emergence of the countless functions available to such devices, the pressure to provide more bandwidth to handle the increased data load used by the countless functions has increased. This pressure has led to the evolution of wireless standards. A typical way to handle more bandwidth is by using higher frequencies. With each frequency evolution, more pressure is exerted on the front-end module within the mobile communication device to comply with the new wireless standard. This pressure provides room for innovation. Summary of the invention
[0006] Various aspects disclosed in the specific embodiments include systems and methods for bidirectional communication of a front-end module (FEM). Specifically, exemplary aspects of the present disclosure contemplate a bidirectional communication path that tunnels through an existing communication bus between the FEM and a baseband processor (BBP). In certain aspects, a driver that may be locally hosted or may be hosted by an external processor communicates with a circuit system within the BBP to achieve the desired tunneling communication through a bus between the BBP and the FEM. The bidirectional communication may allow the FEM to adjust settings based on information provided by the BBP to optimize performance. Likewise, information from the FEM may be used to adjust the operation of the BBP.
[0007] In this regard, in one aspect, a BBP is disclosed. The BBP includes a bus interface. The bus interface is configured to couple to a FEM via a bus. The bus interface is also configured to communicate with the FEM using a first protocol. The BBP also includes a control circuit configured to interoperate with a driver, the driver bidirectionally communicating with the FEM via the first protocol through tunneling.
[0008] In another aspect, a method of controlling a FEM in a mobile device is disclosed. The method includes reading information from a register in the FEM using a package command. The method also includes passing the information from the register to a driver. The method also includes sending a command to the FEM based on the information using a second package command.
[0009] In another aspect, a mobile device is disclosed. The mobile device includes a FEM. The mobile device also includes a communication bus coupled to the FEM. The mobile device also includes a BBP coupled to the communication bus and configured to bidirectionally communicate with the FEM using encapsulated read and write commands. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a block diagram of an exemplary mobile device having a baseband processor (BBP) and a front end module (FEM) with bidirectional communication between the BBP and the FEM;
[0011] Figure 2 is a block diagram of an exemplary mobile device having a BBP and a FEM, with tunneled bidirectional communication between the BBP and the FEM being implemented by a driver in an external processor;
[0012] Figure 3 is a block diagram of an exemplary mobile device having a BBP and a FEM, with tunneled bidirectional communication between the BBP and the FEM being implemented by a driver in an external processor;
[0013] Figure 4Ais a block diagram of an exemplary mobile device having a driver that enables bidirectional communication not only with a BBP and a FEM, but also with other elements within a transceiver architecture;
[0014] Figure 4B is a block diagram of an exemplary mobile device having a driver in an external processor that enables bidirectional communication not only with a BBP and a FEM, but also with other elements within a transceiver architecture;
[0015] Figure 5 yes Figure 1 a block diagram of a mobile device of the invention with additional details relating to information provided to a driver from a BBP and adjustments that may be made in a FEM by the driver using exemplary aspects of bidirectional communication of the present disclosure;
[0016] Figure 6 yes Figure 1 a block diagram of a mobile device with additional details about the drive and the drive's host;
[0017] Figure 7 yes Figure 1 A block diagram of a mobile device having additional detectors in the FEM to assist the driver in determining operating conditions;
[0018] Figure 8 yes Figure 1 a block diagram of a mobile device of FIG. 1 with additional details regarding how key performance indicators (KPIs) may be used to assist a driver in determining operating conditions; and
[0019] Fig. 9 yes Figure 1 A block diagram of a mobile device with additional details regarding how a machine learning module may be used to assist in determining dynamic control of a BBP and FEM based on operating conditions. DETAILED DESCRIPTION
[0020] The embodiments set forth below represent information necessary to enable those skilled in the art to practice the embodiments and to illustrate the best mode for practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize the applications of these concepts not specifically described herein. It should be understood that these concepts and applications fall within the scope of the present disclosure and the appended claims.
[0021] It should be understood that although the terms first, second, etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the present disclosure, the first element can be referred to as the second element, and similarly, the second element can be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more items in the associated listed items.
[0022] It should be understood that when an element such as a layer, region or substrate is referred to as "on another element" or "extending to" another element, it can be directly on another element or directly extend to another element, or there can also be an intermediate element. On the contrary, when an element is referred to as "directly on another element" or "directly extending to another element", there is no intermediate element. Similarly, it should be understood that when an element such as a layer, region or substrate is referred to as "above another element" or "extending above another element", it can be directly above another element or directly extend above another element, or there can also be an intermediate element. On the contrary, when an element is referred to as "directly above another element" or "directly above another element" extends, there is no intermediate element. It will also be understood that when an element is referred to as "connected" or "coupled" to another element, it can be directly connected or coupled to another element, or there can be an intermediate element. On the contrary, when an element is referred to as "directly connected" or "directly coupled" to another element, there is no intermediate element.
[0023] Relative terms such as "below" or "above" or "up" or "lower" or "horizontal" or "vertical" may be used herein to describe one element, layer or region's relationship to another element, layer or region as illustrated in the figures. It will be understood that these terms and those discussed above are intended to encompass different orientations of the device in addition to the orientation depicted in the figures.
[0024] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the present disclosure. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are also intended to include the plural forms. It should also be understood that when used herein, the terms "comprises", "comprising", "includes", and / or "including" specify the presence of the features, integers, steps, operations, elements, and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts, and / or groups thereof.
[0025] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs. It will be further understood that, unless expressly defined herein, the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art, and will not be interpreted in an idealized or overly formal sense.
[0026] Various aspects disclosed in the specific embodiments include systems and methods for bidirectional communication of a front-end module (FEM). Specifically, exemplary aspects of the present disclosure contemplate a bidirectional communication path that tunnels through an existing communication bus between the FEM and a baseband processor (BBP). In certain aspects, a driver that may be locally hosted or may be hosted by an external processor communicates with a circuit system within the BBP to achieve the desired tunneling communication through a bus between the BBP and the FEM. The bidirectional communication may allow the FEM to adjust settings based on information provided by the BBP to optimize performance. Likewise, information from the FEM may be used to adjust the operation of the BBP.
[0027] In the past, the amount of information passed between the BBP and the FEM was typically limited to a one-way communication bus, such as the Radio Frequency Front End (RFFE) bus published by MIPI (Release 3, released in April 2020 and available to MIPI members). Furthermore, the type of information sent from the BBP to the FEM was often limited, and the FEM operated in a generally static mode without dynamic changes based on conditions known to the FEM and / or with limited changes in operating mode based on instructions from the BBP.
[0028] Exemplary aspects of the present disclosure allow a driver to write operating parameters to registers in a FEM and read operating status information from the registers through an existing communication bus through a tunneling process. As used herein, "tunneling" is a technique for securely transferring data from one device to another. More specifically, tunneling contemplates "encapsulating" data and commands outside the scope of the protocol within a packet formatted according to a specific communication protocol. Buses and bus interfaces for devices only "see" correctly formatted packets or signals. At the destination, the packets are unpacked and the encapsulated data or commands are then read and used. In this way, the packets appear to be general packets accepted within the protocol, allowing them to pass through without being noticed until the device can unpack the packets when it can take action on the commands or data within them. In one particularly contemplated aspect, tunneling is accomplished using an RFFE-compatible bus, and commands and / or data are encapsulated within RFFE packets. Although RFFE is specifically contemplated, buses that conform to other protocols may also benefit from the present disclosure.
[0029] Information about operating conditions at the FEM can be shared with the BBP so that the BBP can adjust operation (of the BBP or FEM) to compensate as needed. This capability allows for more dynamic control of the FEM, which in turn provides better (e.g., more efficient or easier to comply with wireless standards) performance for the mobile device. Exemplary information provided by the FEM can include, but is not limited to, frequency blockers, temperature, sensed Vcc level, voltage-standing wave ratio (VSWR), power level protection status, etc.
[0030] To provide context for exemplary aspects of the present disclosure, Figure 1 1 is a block diagram of a mobile device 100 having a BBP 102 that communicates bidirectionally with a FEM 104 via a communication bus 106, such as an RFFE bus. Additionally, signals for transmission may be passed from the BBP 102 to the FEM 104 via a signal bus 108 for wireless transmission via an antenna 110. Likewise, signals received at the antenna 110 may be passed to the BBP 102 via the signal bus 108. These transmitted and received signals are not of interest to the present disclosure, and typically such signals are not carried on an RFFE bus (e.g., bus 106). The BBP 102 may include control circuitry 112 and a digital input / output (I / O) physical interface 114 (also sometimes referred to as a bus interface or PHY).
[0031] The FEM 104 may include a digital I / O physical interface 116 (also sometimes referred to as a bus interface or PHY) and a control circuit 118 with associated registers 120. The FEM 104 may include a transmit path 122 with an associated power amplifier 124 and a receive path 126 with an associated low noise amplifier (LNA) 128. The FEM 104 may switch between using the transmit path 122 and the receive path 126 using a switch circuit 130 that couples one or more paths 122, 126 to the antenna 110. It should be noted that multiple antennas 110 may be used to support diversity reception / transmission and / or multiple input / multiple output (MIMO) techniques including beam steering, etc. The control circuit 118 may control various aspects of the operation of the transmit path 122, the receive path 126, and the switch circuit 130 based on information stored in the registers 120 (better explained in more detail below). BBP 102 may include IF processing circuitry (not shown), or there may be I / F circuitry 132 positioned between BBP 102 and FEM 104, which upconverts / downconverts the signal passing through antenna 110 as is well known. I / F circuitry 132 may also communicate with other circuitry using bus 106.
[0032] Exemplary aspects of the present disclosure contemplate a driver 202 that may be hosted in the BBP 102 (not shown), in some other portion of the modem circuitry including the BBP 102 (also not shown), or hosted in a processor such as the processor 200 ( Figure 2 104). The processor 200 may also include a memory including a register map 204 that provides a mapping of registers 120 and registers 206 within the BBP 102. The driver 202 is responsible for instructing the BBP 102 to package signals (e.g., instructions, commands (read and / or write), and / or data) for transmission across the bus 106 to the FEM 104 via tunneling. Likewise, the driver 202 is responsible for reading information sent from the FEM 104 and evaluating operating parameters provided to the driver 202 by the BBP 102. Based on the information received at the driver 202, the driver 202 may cause the operation of the BBP 102 and / or the FEM 104 to change in order to provide dynamic optimization of the operation.
[0033] Exemplary aspects of the present disclosure also contemplate that the driver 202 (regardless of location) may operate with multiple BBPs and FEMs, such as Figure 3 2. The processor 200 is better shown in FIG. 2. Specifically, the driver 202 in the processor 200 can operate with the BBPs 102A, 102B (and more not shown). The BBP 102A can have an associated FEM 104A, and the BBP 102B can have an associated FEM 104B. In all other respects, the BBPs 102A, 102B can be the same as the previously described BBP 102. Likewise, the FEMs 104A, 104B can be the same as the previously described FEM 104. There can be additional lookup tables (LUTs) 300 in the processor 200 to assist in mapping signals to and from the appropriate BBPs 102A, 102B and FEMs 104A, 104B.
[0034] Although it is contemplated that most communications between the driver 202 and the BBP 102 may be accomplished using the connection between the BBP 102 and the FEM 104, exemplary aspects of the present disclosure are not limited in this regard. Figure 4AAs better shown in , the driver 202 may be able to communicate directly with other elements of the transceiver architecture (e.g., the power management integrated circuit (PMIC) 400 and / or the antenna tuner circuit 402) via the alternative bus 106A, 106B. The protocol used on the alternative bus 106A, 106B may still be, for example, that of the RFFE, and tunneling may be used as desired. Note that direct communication without tunneling is also contemplated, and for example, there may be a non-RFFE direct bus 106C between the driver 202 and the FEM 104. It should also be noted that the bus 106A, 106B, 106C may also be a single RFFE bus that the driver 202 can access directly (i.e., without going through the BBP 102).
[0035] Figure 4A The aspects shown in contemplate driver 202 in a modem containing BBP 102 or within another processor 200 such as an application processor. However, Figure 4B Another option shown in is a dedicated integrated circuit (IC) or bridge 420, which can act as a master on a bus, such as an RFFE bus, and use tunneling or have a direct bus that does not require tunneling. For example, the bridge 420 can be coupled to the BBP 102, the FEM 104, and the LNA and power amplifier with integrated duplexer (LPAMID) 422, the PMIC 400, one or more couplers 424, the antenna tuner circuit 402, the antenna impedance tuner 426, and / or the envelope tracking integrated circuit (ETIC) 428 (or average power tracking circuit (APT) (not shown)). Registers (not shown) can be used to provide access to information about operating conditions and / or instructions to modify the performance of any of these elements. Other elements can be added to this direct communication if needed or desired. It should also be noted that the bridge 420 can include a driver such as the driver 202, or all functions can be implemented in hardware without any software overlay.
[0036] exist Figure 1-4B With various possible hardware layouts shown in FIG. 1 , the present discussion turns to the types of information that can be exchanged. It should be appreciated that in most cases, the information from the remote element (e.g., FEM 104) will be "pulled" or read from registers in the remote element, rather than the remote element actively sending information to the driver 202. However, exemplary aspects of the present disclosure include both formats.
[0037] Figure 5 Provided Figure 1 200 (or other location, Figure 5104) and adjustments that the driver 202 may make in the FEM 104 using exemplary aspects of bidirectional communication of the present disclosure. Specifically, the BBP 102 may store information such as RF channel information, sub-band information, bandwidth information, carrier aggregation or other carrier information, resource block information, peak to average ratio (PA), maximum power reduction (MPR), ENDC mode, etc. This information may be provided to the driver 202. The driver 202 may use a calculation engine 500 assisted by a global LUT 502 (which may include the LUT 300 and the register map 204) to determine the information to be sent to the FEM 104. Likewise, the driver 202 may include an information exchange module 504 to handle the transmission and reception of information with the FEM 104 (e.g., register control signals 506). Within the FEM 104, the information in the register 120 may be accessed by the control circuit 118 and / or a separate control calculation unit 508 to change settings in the transmit path 122, the receive path 126, and / or the switch circuit 130. Additionally, control circuitry 118 and / or control computation unit 508 may work with a local LUT 510 that provides indices for registers 120 .
[0038] Note that the driver 202 may include an encoding block 600 and a decoding block 602, as shown in Figure 6 106. The encoding block 600 may assist in packaging information from the computing engine 500 so that the information may be tunneled across the bus 106. Likewise, the decoding block 602 may extract the packaged information that has been tunneled across the bus 106 for consideration by the computing engine 500. Similarly, the control computing unit 508 may encode and decode data sent to and from the FEM 104 (respectively).
[0039] To assist in providing information to the actuator 202, the FEM 104 may be equipped with one or more sensors or detectors configured to determine operating conditions and report to the control circuit 118 or control computing unit 508 for encoding and transmission to the actuator 202, such as Figure 7 . By way of example, but not necessarily limitation, detector 700 may be associated with transmit path 122, detector 702 may be associated with receive path 126, and detector 704 may be associated with switch circuit 130. Detectors 700, 702, and 704 may detect temperature, supply voltage, blockers, power protection states, etc. Note that although referenced as a single detector 700, 702, 704, detectors 700, 702, 704 may include multiple detectors at each location designed to detect different operating conditions.
[0040] It should be appreciated that while having information from the FEM 104 to inform operational adjustments provides significant improvements in performance, the present disclosure is not limited thereto. Figure 8 8, the BBP 102 may provide additional information to the driver 202. Specifically, the BBP 102 may have some ability to demodulate information with a demodulator 800 to determine one or more key performance indicators (KPIs) 802 that are provided to the compute engine 500. In an exemplary aspect, information about the KPIs (i.e., KPI information) is provided, which may be an actual KPI or an indication that the KPI is above (or below) a threshold. Exemplary KPIs include bit error rate (BER), signal-to-noise ratio (SNR), error vector magnitude (EVM), signal-to-noise and distortion ratio (SNDR), etc. Based on the KPI (e.g., f(KPI)), the compute engine 500 may select between various preconfigured selections 804(1)-804(N) and provide instructions to the FEM 104 based on the selected selection.
[0041] It should also be noted that the computation engine 500 can benefit from machine learning processes so that optimization is improved through experiential learning. Fig. 9 One such aspect is shown in , where the driver 202 has a machine learning module 900 that works with a case LUT 902 to improve adjustments made to the FEM 104 based on detected operating conditions.
[0042] While the above discussion assumes that there may be a single optimization scheme or set of optimization instructions based on the operating conditions, this assumption may not always be true. For example, one set of adjustments may be optimal for transmission, while another set of adjustments may be optimal for reception. The driver 202 (or bridge 420) may be programmed to select a more desirable set of adjustments or find a compromise set of adjustments that provides the best optimization for both modes while being suboptimal for either mode alone.
[0043] To the extent not expressly stated above, Figure 5-9 Any aspect can be applied to Figure 1-4B Likewise, while the present discussion has presented driver 202 as a monolithic entity hosted in a single location, exemplary aspects of the present disclosure include the possibility that driver 202 may be split between multiple processors (e.g., part in a modem processor and part in an application processor).
[0044] It should also be understood that the system described above also discloses a method for controlling a front-end module by providing information to a driver and a driver to issue a command to the FEM to change the operation by means of the FEM. It should also be noted that the operation steps described in any of the exemplary aspects herein are described to provide examples and discussions. The described operations can be performed in a large number of different orders other than the order shown. In addition, the operations described in a single operation step can actually be performed in many different steps. In addition, one or more operation steps discussed in the exemplary aspects can be combined. It should be understood that it will be readily apparent to those skilled in the art that the operation steps illustrated in the flow chart can be subject to a variety of different modifications. Those skilled in the art will also understand that any of a variety of different technologies and techniques can be used to represent information and signals. For example, voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof can be used to represent data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description.
[0045] The previous description of the disclosure is provided so that any person skilled in the art can make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A baseband processor (BBP), comprising: A bus interface, the bus interface being configured to: coupled to a front end module (FEM) via a bus; and communicating with the FEM using a first protocol; as well as A control circuit is configured to interoperate with a driver that bidirectionally communicates with the FEM via the first protocol through tunneling.
2. The BBP according to claim 1, wherein: The control circuit is also configured to read information from a register in the FEM through tunneling.
3. The BBP according to claim 1, wherein: The control circuit is configured to interoperate with the drive by communicating with a remote application processor.
4. The BBP of claim 1, wherein: The control circuit is configured to interoperate with the driver at a local modem processor.
5. The BBP of claim 1, wherein: The control circuit is also configured to receive packaging instructions for the FEM.
6. The BBP of claim 1, wherein: The control circuit is configured to interoperate with the driver at the bridge.
7. The BBP of claim 2, wherein: The control circuit is also configured to read the detector information in the register.
8. The BBP of claim 2, wherein: The control circuit is further configured to read the operating status information in the register.
9. The BBP of claim 1, wherein: The control circuit is also configured to send information about the BBP to the driver.
10. The BBP of claim 9, wherein: The control circuit is configured to send key performance indicator (KPI) information to the driver.
11. The BBP of claim 9, wherein: The control circuit is configured to send operating condition information to the driver.
12. A method of controlling a front end module (FEM) in a mobile device, the method comprising: Using a package command to read information from a register in the FEM; transferring the information from the register to the driver; as well as Based on the information, a command is sent to the FEM using a second package command.
13. The method according to claim 12, wherein: The commands adjust operating parameters of elements within the FEM.
14. The method of claim 12, further comprising hosting the driver in a modem processor.
15. The method of claim 12, further comprising hosting the driver in an application processor.
16. A mobile device, comprising: Front End Module (FEM); a communication bus coupled to the FEM; as well as A baseband processor (BBP) is coupled to the communication bus and configured to communicate bidirectionally with the FEM using packaged read and write commands.
17. The mobile device of claim 16, further comprising a driver hosted in a modem processor associated with the BBP.
18. The mobile device according to claim 16, wherein: The FEM includes at least one detector associated with an element of the FEM, and a register, wherein information from the at least one detector is stored in the register, and the BBP is configured to read the register using a package read command.
19. The mobile device of claim 16, further comprising a power management integrated circuit (PMIC), and wherein: The BBP is configured to control the PMIC based on information from the FEM.
20. The mobile device according to claim 16, wherein: The BBP is configured to provide information to a driver and receive the packaged read and write commands from the driver.
