Single-soft-multiple-hard implementation method and device of radio frequency front-end system

Abstract

The invention relates to the technical field of electronics, and particularly provides a single-soft-multiple-hard implementation method and device of a radio frequency front-end system. The method comprises the following steps: when mainboard hardware is started, identifying a plurality of candidate radio frequency front-end units connected to the same bus; wherein each candidate radio frequency front-end unit comprises a plurality of radio frequency devices; reading a plurality of pieces of identification information of each radio frequency device in the plurality of radio frequency devices; wherein the identification information comprises a device identifier and a configuration identifier; determining a target radio frequency front-end unit from the plurality of candidate radio frequency front-end units based on a target device identifier and a target configuration identifier of a target radio frequency device in the plurality of radio frequency devices; and configuring the plurality of radio frequency devices to be configured based on the radio frequency configuration information corresponding to the target radio frequency front-end unit. According to the invention, the single-soft multi-hard function of mainboard hardware can be realized, diversified device type selection is supported, the convenience of product design, production and maintenance is improved, and the product competitiveness is effectively improved.

Description

Technical Field

[0001] This disclosure relates to the field of electronic technology, and in particular to a method and apparatus for implementing a single-software and multi-hardware radio frequency front-end system. Background Technology

[0002] Currently, there are many types of smart terminals or module products, and the software and hardware designs are becoming increasingly diversified. Considering factors such as product supply chain stability and cost, and given that the baseband chip cannot be changed, the diversified selection and design of radio frequency front-end devices has become the most important aspect.

[0003] In related technologies, smart terminals and module products support communication standards covering 2G / 3G / 4G, and even higher-end products covering 5G. This typically requires complex and varied radio frequency (RF) front-end systems to support them. However, the current RF front-end market has a large number of users, and the diverse product definitions bring a series of problems to product design, production, and maintenance. Summary of the Invention

[0004] This disclosure is made in view of the above-mentioned problems. This disclosure provides a method and apparatus for implementing a single-software, multi-hardware RF front-end system.

[0005] According to one aspect of this disclosure, a method for implementing a single-software, multi-hardware RF front-end system is provided, applied to an RF front-end system, the method comprising: When the motherboard hardware starts up, based on the multiple radio frequency devices to be configured on the motherboard hardware, multiple candidate radio frequency front-end units connected to the same bus are identified; wherein, each of the candidate radio frequency front-end units includes the multiple radio frequency devices. Read multiple identification information for each of the plurality of radio frequency devices; wherein, the identification information includes a device identifier and a configuration identifier; Based on the target device identifier and target configuration identifier of the target RF device among the plurality of RF devices, the target RF front-end unit is determined from the plurality of candidate RF front-end units; Based on the RF configuration information corresponding to the target RF front-end unit, the multiple RF devices to be configured are configured to realize the single-software and multi-hardware functions of the motherboard hardware.

[0006] According to another aspect of this disclosure, a single-software-multiple-hardware implementation device for an RF front-end system is provided, applied to an RF front-end system, the device comprising: An identification module is used to identify multiple candidate radio frequency front-end units connected to the same bus based on multiple radio frequency devices to be configured on the motherboard hardware when the motherboard hardware starts up; wherein each candidate radio frequency front-end unit includes the multiple radio frequency devices. A reading module is used to read multiple identification information of each of the plurality of radio frequency devices; wherein, the identification information includes a device identifier and a configuration identifier; The processing module is used to determine the target RF front-end unit from the plurality of candidate RF front-end units based on the target device identifier and target configuration identifier of the target RF device among the plurality of RF devices; The configuration unit is used to configure the multiple radio frequency devices to be configured based on the radio frequency configuration information corresponding to the target radio frequency front-end unit, so as to realize the single-software and multi-hardware functions of the motherboard hardware.

[0007] In another aspect of exemplary embodiments of this disclosure, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory, the processor executing the computer program to implement the methods described in exemplary embodiments of this disclosure.

[0008] In another aspect of exemplary embodiments of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the methods described in exemplary embodiments of the present disclosure.

[0009] In another aspect of the exemplary embodiments of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the methods described in the exemplary embodiments of this disclosure.

[0010] As will be described in detail below, the single-software-multiple-hardware implementation method of the RF front-end system according to the embodiments of this disclosure identifies multiple candidate RF front-end units connected to the same bus based on multiple RF devices to be configured on the motherboard hardware during the motherboard hardware startup; wherein each candidate RF front-end unit includes multiple RF devices; reads multiple identification information of each RF device among the multiple RF devices; wherein the identification information includes device identifier and configuration identifier; determines the target RF front-end unit from the multiple candidate RF front-end units based on the target device identifier and target configuration identifier of the target RF device among the multiple RF devices; and configures the multiple RF devices to be configured based on the RF configuration information corresponding to the target RF front-end unit. This solves the problem of USID conflict of RF devices on the same bus, allows the use of RF devices from multiple manufacturers, and can automatically identify and configure multiple RF devices to be configured on the motherboard hardware without changing the motherboard hardware design or increasing the motherboard hardware cost. While reducing thermal intervention, it realizes the single-software-multiple-hardware function of the motherboard hardware, that is, one software adapts to multiple hardware configurations, thereby supporting diversified device selection, improving the convenience of product design, production and maintenance, and effectively enhancing product competitiveness.

[0011] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0012] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0013] Figure 1 A flowchart illustrating a single-software, multi-hardware implementation method for a radio frequency front-end system provided in an exemplary embodiment of this disclosure is shown. Figure 2 A schematic diagram of the framework of the radio frequency front-end system provided in an embodiment of this disclosure is shown; Figure 3 A schematic diagram of the radio frequency front-end interface and bus structure provided in the embodiments of this disclosure is shown; Figure 4 A communication flowchart of a register read operation defined by the mobile industry processor interface protocol provided in an exemplary embodiment of this disclosure is shown. Figure 5 A schematic diagram of the structure of a single-software-multiple-hardware implementation device for a radio frequency front-end system provided in an exemplary embodiment of this disclosure is shown. Figure 6 A schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this disclosure is shown; Figure 7 A schematic diagram of the structure of a computer system provided in an exemplary embodiment of this disclosure is shown. Detailed Implementation

[0014] To make the objectives, technical solutions, and advantages of this disclosure more apparent, exemplary embodiments according to this disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this disclosure, and not all embodiments of this disclosure. It should be understood that this disclosure is not limited to the exemplary embodiments described herein.

[0015] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0016] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below. It should be noted that the concepts of "first", "second", etc., used in this disclosure are only used to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0017] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0018] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0019] In related technologies, the mainstream implementation methods of single-software and multi-hardware approaches can be divided into two types. The first is to use the board IDADC method, which can use a fixed current source and different voltages collected by different precision resistors to identify these key RF devices, and then call the corresponding RF parameters; however, this method requires hardware support, which increases product costs. The second method is to use software to read the unique slave identifier (USID) of the RF device for identification. However, if different RF devices with the same USID appear on the same mobile industry processor interface bus (MIPI bus), the current readback process architecture will fail to read the device due to addressing conflicts, and cannot identify scenarios where RF devices have the same USID, which has certain limitations.

[0020] Therefore, in order to solve the above problems, this disclosure provides a single-software-multiple-hardware implementation method for a radio frequency front-end system. This method can solve the compatibility design of different products from different manufacturers without changing the hardware design or increasing the cost of the motherboard hardware. It can effectively save hardware costs, bring convenience to production and maintenance, and thus effectively enhance product competitiveness.

[0021] The single-software-multiple-hardware implementation method for an RF front-end system provided in this disclosure is applied to an RF front-end system. It can be executed by a terminal with an RF front-end system deployed, or by a chip applied to a terminal with an RF front-end system deployed.

[0022] For example, the terminal may include one or more of the following: mobile phone, tablet computer, wearable device, in-vehicle device, laptop computer, ultra-mobile personal computer (UMPC), netbook, PDA, and wearable device based on augmented reality (AR) and / or virtual reality (VR) technology. The exemplary embodiments disclosed herein do not impose specific limitations on these.

[0023] Figure 1 A flowchart illustrating a single-software, multi-hardware implementation method for a radio frequency front-end system provided in an exemplary embodiment of this disclosure is shown. Figure 1 As shown, the single-software multi-hardware implementation method of this RF front-end system includes: S101, when the motherboard hardware starts up, identifies multiple candidate RF front-end units connected to the same bus based on the multiple RF devices to be configured on the motherboard hardware; wherein, each candidate RF front-end unit includes multiple RF devices. S102, read multiple identification information for each of the multiple radio frequency devices; wherein, the identification information includes device identifier and configuration identifier; S103, Based on the target device identifier and target configuration identifier of the target RF device among multiple RF devices, determine the target RF front-end unit from multiple candidate RF front-end units; S104 configures multiple RF devices to be configured based on the RF configuration information corresponding to the target RF front-end unit, so as to realize the single-software and multi-hardware functions of the motherboard hardware.

[0024] Specifically, in the aforementioned motherboard hardware, the multiple radio frequency devices to be configured (also known as slave devices) may include, but are not limited to, at least two of the following: a transmitter module (2G TX MODULE, TXM), a multi-mode multi-band power amplifier (MMMBPA), an antenna switch module (ASM), a low-noise amplifier (LNA), and a tuner.

[0025] From a control perspective, these RF devices are collectively referred to as slave identifiers. The Mobile Industry Processor Interface (MIPI) Alliance provides flexible and varied identifiers for these different categories of RF front-end devices. However, precisely because these flexible and varied identifiers, to a certain extent, assign these slave devices the same unique slave identifier (USID) (the USID being the device identifier mentioned above), it leads to difficulties in control or invocation during the use of RF front-end systems, causing numerous inconveniences for product selection, design, production, and maintenance.

[0026] Figure 2 A schematic diagram of the framework of the radio frequency front-end system provided in this disclosure embodiment is shown, such as... Figure 2 As shown, node 200 is the motherboard hardware, namely the radio frequency integrated circuit (RFIC) chip, node 201 is the multimode multi-frequency power amplifier (MMMB PA), and node 202 is the transmitter module (TXM). The transmission link direction is that the transmitted TX signal passes through nodes 200, 201, and 202 in sequence, and then is radiated by the antenna.

[0027] Multiple radio frequency (RF) devices to be configured on the motherboard hardware, namely nodes 201 and 202, are connected to the same bus. These RF devices can be controlled by a Mobile Industry Processor Interface (MIPI) bus (MIPI bus). During design, the system assigns these RF devices USIDs conforming to the protocol specification, or uses the device's original USID to send MIPI word control words, achieving signal transmission and reception. The MIPI bus can perform write and read operations on these RF devices. The method in this disclosure embodiment is related to implementing single-software multi-hardware, and the execution scope does not include write operations, but focuses on the impact on read operations on RF devices.

[0028] Figure 3 A schematic diagram of the radio frequency front-end interface and bus structure provided in the embodiments of this disclosure is shown, such as... Figure 3The diagram illustrates the Radio Frequency Front-End interface (RFFE interface) and bus structure. In RF subsystem design, front-end devices are typically controlled by General-Purpose Input / Output (GPIO) or MIPI buses. The method described in this disclosure only pertains to the transmit / receive operation of MIPI bus controllers. The protocol specifies that a single MIPI bus can support up to 15 USID RF devices, including TXM (RF device 301) and MMMB PA (RF device 302), among others.

[0029] Figure 4 This illustration shows a communication flowchart of a register read operation defined by the mobile industry processor interface protocol provided in an exemplary embodiment of this disclosure, such as... Figure 4 As shown, the 4 bits following the Sequence Start Condition (SSC) constitute the USID address. After finding the USID, the data in the relevant register address is read according to a fixed format. Therefore, to obtain the data content of the device's destination register, the device's USID must first be known. From a control perspective, the same USID cannot appear on a single MIPI bus.

[0030] The embodiments disclosed herein aim to solve the problem that the occurrence of the same USID on the MIPI bus leads to addressing conflicts, making it impossible to correctly identify these RF devices and thus making it impossible to control the RF configuration information related to calling RF devices.

[0031] Multiple candidate RF front-end units connected on the same bus can be understood as multiple sets of hardware composed of RF devices from multiple different manufacturers, with each set of hardware including multiple RF devices. The multiple RF devices in the same candidate RF front-end unit can come from the same manufacturer or from different manufacturers, depending on actual needs; this disclosure does not specifically limit this.

[0032] Different manufacturers may set the same or different USIDs for the same RF device; the same manufacturer may set the same or different USIDs for different RF devices. This results in multiple RF devices on the same MIPI bus having the same USID, which leads to addressing conflicts and ultimately makes it impossible to correctly identify the device.

[0033] This disclosure embodiment can read multiple identification information for each of a plurality of radio frequency (RF) devices. The identification information may include a device identifier and a configuration identifier. Here, the device identifier is the unique slave device identifier (USID) mentioned above, and the configuration identifier may be an identifier assigned by the manufacturer to the RF device for obtaining the RF parameters of the corresponding RF device.

[0034] Then, from among multiple RF devices, the RF devices that have been surface-mounted on the motherboard hardware are selected as the target RF device, and the target device identifier and target configuration identifier of the target RF device are determined. Based on the target device identifier and target configuration identifier, the target RF front-end unit is determined from among multiple candidate RF front-end units. Here, in this embodiment of the disclosure, the candidate RF front-end unit whose device identifier matches the target device identifier and whose configuration identifier matches the configuration identifier can be determined as the target RF front-end unit.

[0035] After identifying the target RF front-end unit, multiple RF devices to be configured can be configured based on the RF configuration information corresponding to the target RF front-end unit. This solves the problem of USID conflict of RF devices on the same bus, allowing the use of RF devices from multiple manufacturers. It can automatically identify and configure multiple RF devices to be configured on the motherboard hardware without changing the motherboard hardware design or increasing the motherboard hardware cost. While reducing thermal intervention, it realizes the single-software and multi-hardware function of the motherboard hardware, that is, one software adapts to multiple hardware configurations, thereby supporting diversified device selection, improving the convenience of product design, production and maintenance, and effectively enhancing product competitiveness.

[0036] According to the technical solution of the exemplary embodiments of this disclosure, when the motherboard hardware starts up, multiple candidate RF front-end units connected to the same bus are identified based on multiple RF devices to be configured on the motherboard hardware; wherein each candidate RF front-end unit includes multiple RF devices; multiple identification information of each RF device is read; wherein the identification information includes device identifier and configuration identifier; based on the target device identifier and target configuration identifier of the target RF device among the multiple RF devices, a target RF front-end unit is determined from the multiple candidate RF front-end units; based on the RF configuration information corresponding to the target RF front-end unit, the multiple RF devices to be configured are configured, which solves the problem of RF device USID conflict on the same bus, allows the use of RF devices from multiple manufacturers, and can automatically identify and configure multiple RF devices to be configured on the motherboard hardware without changing the motherboard hardware design or increasing the motherboard hardware cost. While reducing thermal intervention, it realizes the single-software multi-hardware function of the motherboard hardware, that is, one software adapts to multiple hardware configurations, thereby supporting diversified device selection, improving the convenience of product design, production and maintenance, and effectively enhancing product competitiveness.

[0037] In some embodiments, a target RF front-end unit is determined from a plurality of candidate RF front-end units based on a target device identifier and a target configuration identifier of a target RF device among a plurality of RF devices, including: Identify the target RF device from multiple RF devices, and obtain the target device identifier and target configuration identifier of the target RF device; If a candidate RF front-end unit meets the first preset judgment condition, then the candidate RF front-end unit is determined to be a pending RF front-end unit; wherein, the first preset judgment condition includes that the device identifier of the target RF device among multiple RF devices matches the target device identifier, and the device identifiers of the other RF devices do not match the target device identifier. If the configuration identifier of the target RF device in the pending RF front-end unit matches the target configuration identifier, then the pending RF front-end unit is determined to be the target RF front-end unit.

[0038] Specifically, the target RF device can be a known RF device among multiple RF devices to be configured on the motherboard hardware. The target RF front-end unit is determined from multiple candidate RF front-end units by using the target device identifier and target configuration identifier of the target RF device.

[0039] First, based on the target device identifier, the candidate RF front-end unit can be determined from multiple candidate RF front-end units. The number of candidate RF front-end units can be one or more.

[0040] The aforementioned first preset determination condition may include the device identifier of the target RF device matching the target device identifier, and the device identifiers of other RF devices not matching the target device identifier. Here, by setting the first preset determination condition, the case where at least two RF devices in the same RF front-end unit have the same USID can be excluded first, thus identifying at least one undetermined RF front-end unit.

[0041] When there is only one pending RF front-end unit, it is determined whether the configuration identifier of the target RF device in the pending RF front-end unit matches the target configuration identifier. If the configuration identifier of the target RF device in the pending RF front-end unit matches the target configuration identifier, then the pending RF front-end unit is determined to be the target RF front-end unit.

[0042] When there are multiple pending RF front-end units, the target RF front-end unit is determined from these pending RF front-end units based on the target configuration identifier. For example, the pending RF front-end unit whose configuration identifier matches the target RF device configuration identifier is determined as the target RF front-end unit.

[0043] In some embodiments, the method may further include: If the configuration identifier of the target RF device in the candidate RF front-end unit does not match the target configuration identifier, then it is determined whether the candidate RF front-end unit meets the second preset judgment condition; wherein, the second preset judgment condition includes the device identifier of the target RF device matching the target device identifier, and there is a device identifier of another RF device matching the target device identifier. If the candidate RF front-end unit meets the second preset judgment condition, then the candidate RF front-end unit is determined to be the target RF front-end unit.

[0044] Specifically, when there is only one candidate RF front-end unit, if the configuration identifier of the target RF device in the candidate RF front-end unit does not match the target configuration identifier, it means that candidate RF front-end units with different USIDs of RF devices need to be excluded. At this time, it can be determined whether the candidate RF front-end unit meets the second preset judgment condition.

[0045] The aforementioned second preset determination condition may include the device identifier of the target RF device matching the target device identifier, and the existence of a device identifier of another RF device matching the target device identifier.

[0046] If a candidate RF front-end unit meets the second preset judgment condition, it means that among the candidate RF front-end units, in addition to the configuration identifier of the target RF device matching the target configuration identifier, there is at least one other RF device whose device identifier matches the target device identifier. At this time, the candidate RF front-end unit can be determined as the target RF front-end unit.

[0047] In some embodiments, the configuration identifier includes a product identifier and a manufacturer identifier, and the RF configuration information includes RF parameters of multiple RF devices. Based on the RF configuration information corresponding to the target RF front-end unit, multiple RF devices to be configured are configured to achieve single-software and multi-hardware functionality of the motherboard hardware, including: Obtain the product identifiers and manufacturer identifiers of multiple RF devices in the target RF front-end unit; Based on product identifiers and manufacturer identifiers, obtain the RF parameters of multiple RF devices in the target RF front-end unit; Based on the RF parameters of multiple RF devices in the target RF front-end unit, the multiple RF devices to be configured are configured to realize the single-software and multi-hardware functions of the motherboard hardware.

[0048] Specifically, when the same RF device manufactured by different manufacturers is used in different products, its RF parameters may differ. Therefore, the configuration identifier set in this embodiment may include a product identifier (PID) and a manufacturer identifier (MID). The product identifier is used to indicate the application product of the RF device, and the manufacturer identifier is used to indicate the manufacturer of the RF device.

[0049] After identifying the target RF front-end unit, the product identifiers and manufacturer identifiers of multiple RF devices within the target RF front-end unit can be obtained. Based on these identifiers, the RF parameters of these devices can be retrieved, ensuring accurate parameter matching. Next, based on the RF parameters of these devices, the multiple RF devices to be configured can be selected. This allows for flexible configuration of RF devices from different manufacturers and products on the motherboard hardware, supporting diverse device selection, improving the convenience of product design, production, and maintenance, and effectively enhancing product competitiveness.

[0050] In some embodiments, before reading multiple identification information of each of the multiple radio frequency devices, the method may further include: Obtain the original device identifiers of multiple RF devices in each candidate RF front-end unit; The original device identifiers are initialized to obtain the device identifiers of multiple RF devices in each candidate RF front-end unit.

[0051] Specifically, before reading the identification information, the original device identifiers of multiple radio frequency devices in each candidate radio frequency front-end unit are initialized to obtain the device identifiers of multiple radio frequency devices in the candidate radio frequency front-end unit.

[0052] This initialization process can reset the USIDs of multiple RF devices in each candidate RF front-end unit, preventing initial conflicts caused by identical factory settings. The USIDs of these RF devices can be changed during initialization, and bias can also be configured, laying the foundation for subsequent identification.

[0053] Meanwhile, after initialization, the device identifier is in a controllable state, making the subsequent reading and matching process smoother.

[0054] The technical solutions provided in the embodiments of this disclosure are given specific examples below: Assuming that the multiple radio frequency devices to be configured on the motherboard hardware include the transmitter module TXM and the multimode multi-frequency power amplifier MMMBPA, and that the selection and design of radio frequency devices may involve situations where the original USIDs are the same (e.g., F and F) or different (e.g., E and F), including but not limited to these three types of candidate radio frequency front-end units, Table 1 shows the identification information of multiple radio frequency devices in the first candidate radio frequency front-end unit provided in the embodiments of this disclosure, Table 2 shows the identification information of multiple radio frequency devices in the second candidate radio frequency front-end unit provided in the embodiments of this disclosure, and Table 3 shows the identification information of multiple radio frequency devices in the third candidate radio frequency front-end unit provided in the embodiments of this disclosure.

[0055] Table 1 Identification information of multiple RF devices in the first candidate RF front-end unit

[0056] Table 2 Identification information of multiple RF devices in the second candidate RF front-end unit

[0057] Table 3 Identification information of multiple RF devices in the third candidate RF front-end unit

[0058] The RF devices TXM and MMMB PA from manufacturers A, B, and C appearing in the first, second, and third candidate RF front-end units are the targets of the single-software-multiple-hardware processing in this disclosure embodiment, requiring a software adaptation solution for the project. However, it can be seen that in the first candidate RF front-end unit, the USIDs of the TXM and MMMB PA provided by manufacturer A are both F; in the second candidate RF front-end unit, the USIDs of the TXM and MMMB PA provided by manufacturer B are E and F respectively; and in the third candidate RF front-end unit, the USIDs of the TXM and MMMB PA provided by manufacturer C are E and F respectively. Of course, in the third candidate RF front-end unit, the TXM and MMMB PA can be provided by different manufacturers; for example, the TXM can be provided by manufacturer A, and the MMMB PA can be provided by manufacturer B; or the TXM can be provided by manufacturer B, and the MMMB PA can be provided by manufacturer A.

[0059] If the motherboard hardware's Bill of Materials (BOM) specifies two RF devices provided by Manufacturer A, with MMMB PA as the target RF device, and the USID, PID, and MID of MMMB PA as the target device identifier (F), target product identifier (0b0000 0001), and target manufacturer identifier (Company A).

[0060] At this point, the startup software of the front-end RF system reads the USID, PID, and MID of the two RF devices on the MIPI bus line. However, since the USID of TXM and MMMB PA in the first candidate RF front-end unit is both F, the two RF devices have the same USID, causing a conflict and preventing the RF device from being identified (the first candidate RF front-end unit meets the second preset judgment condition). Therefore, the first candidate RF front-end unit is excluded because it cannot be identified due to the same USID.

[0061] At this point, the USID of the MMMB PA in the second candidate RF front-end unit can be read. It can be seen that the USID of the MMMB PA in the second candidate RF front-end unit is F, and it is different from the USID of the TXM (the second candidate RF front-end unit meets the first preset judgment condition). Next, it is determined whether the PID of the MMMB PA matches the target product identifier (0b0000 0001), and whether the MID of the MMMB PA matches the target manufacturer identifier (Company A). Referring to Tables 1 and 2, it can be seen that the PID of the MMMB PA in the second candidate RF front-end unit does not match the target product identifier (0b0000 0001), and the MID of the MMMB PA does not match the target manufacturer identifier (Company A). Therefore, the second candidate RF front-end unit is excluded because the PID and MID do not match.

[0062] Reading the USID of the MMMB PA in the third candidate RF front-end unit reveals that its USID is F, which is different from the USID of the TXM (the third candidate RF front-end unit meets the first preset judgment condition). Next, it is determined whether the PID of the MMMB PA matches the target product identifier (0b0000 0001) and whether the MID of the MMMB PA matches the target manufacturer identifier (Company A). Referring to Tables 1 and 3, it can be seen that the PID of the MMMB PA in the third candidate RF front-end unit does not match the target product identifier (0b0000 0001), and the MID of the MMMB PA does not match the target manufacturer identifier (Company A). Therefore, the third candidate RF front-end unit is excluded because the PID and MID do not match.

[0063] At this point, the first candidate RF front-end unit whose "exclusion reason is: unable to identify due to identical USID" can be identified as the target RF front-end unit (E+F combination). Based on this, the RF front-end system can retrieve the RF parameters of the F+F combination, i.e., the two RF devices provided by manufacturer A.

[0064] Similarly, this process is quite flexible and can cover a certain proportion of device combinations, such as [E+F,E+F], [E+F,E+E]; [E+F,F+F], [E+F,E (different MID or PID)+F,F+F], [E+F,E+F (different MID or PID),E+E], etc. These resource pool combinations can be distinguished one by one by the method provided in the embodiments of this disclosure, just like a funnel.

[0065] The simplified software code for the single-software / multi-hardware implementation of the RF front-end system is as follows: uint32_t RFFE_Read(uint32_t usid, uint32_t regaddr) { OSI_LOGI(0x100092fa, "RFFE_Read start usid:%x regaddr:%x", usid,regaddr); OSI_REG32_WRITE(hwp_rffe->cmd_mipi0, regaddr); / / write register addrto cmd_mipi0 OSI_REG32_WRITE(hwp_rffe->cmd_mipi1, 0x70 | (usid<<10)); / / write usidaddr to cmd_mipi1 osiDelayUS(200); return OSI_REG32_READ(hwp_rffe->data_out0); / / read data_out0 } static void prvGetPAType(void) { uint32_t pa_type[3] = {0}; uint32_t val; val = OSI_REG32_READ(hwp_iomux->pad_rfdig_gpio_0_cfg_reg); val&= 0xFFFFFFF0; OSI_REG32_WRITE(hwp_iomux->pad_rfdig_gpio_0_cfg_reg, val|0x1); / / config rf gpio0 iomux val = OSI_REG32_READ(hwp_iomux->pad_rfdig_gpio_1_cfg_reg); val&= 0xFFFFFFF0; OSI_REG32_WRITE(hwp_iomux->pad_rfdig_gpio_1_cfg_reg, val|0x1); / / config rf gpio1 iomux pa_type[0] = RFFE_Read(0,0x1F); / / read PA USID if(pa_type[0] == 0xf) { pa_type[1] = RFFE_Read(0xF, 0x1D) / / read PID pa_type[2] = RFFE_Read(0xF, 0x1E) / / read MID if(pa_type[1] == 0xb)&&pa_type[2] == 0xb); { sprintf((char )fname, "factory / indeltanv_b.bin"); / / load B indeltanv } } else { pa_type[1] = RFFE_Read(0xE, 0x1D) / / read PID pa_type[2] = RFFE_Read(0xE, 0x1E) / / read MID if(pa_type[1] == 0xc)&&pa_type[2] == 0xc); { sprintf((char )fname, "factory / indeltanv_c.bin"); / / load C indeltanv } else { sprintf((char )fname, "factory / indeltanv_a.bin"); / / load A indeltanv } } return; } The foregoing mainly describes the solutions provided by the embodiments of this disclosure. It is understood that, in order to achieve the above functions, the electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0066] This disclosure embodiment can divide the electronic device into functional units according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0067] By dividing each functional module according to its corresponding functions, an exemplary embodiment of this disclosure provides a single-software-multiple-hardware implementation device for an RF front-end system, which can be a terminal or a chip applied to a terminal. Figure 5 A schematic diagram of a single-software, multi-hardware implementation of a radio frequency front-end system provided in an exemplary embodiment of this disclosure is shown. For example... Figure 5 As shown, the device 500 includes: The identification module 501 is used to identify multiple candidate radio frequency front-end units connected to the same bus based on multiple radio frequency devices to be configured on the motherboard hardware when the motherboard hardware starts up; wherein each candidate radio frequency front-end unit includes the multiple radio frequency devices. The reading module 502 is used to read multiple identification information of each of the plurality of radio frequency devices; wherein, the identification information includes a device identifier and a configuration identifier; Processing module 503 is used to determine a target RF front-end unit from the plurality of candidate RF front-end units based on the target device identifier and target configuration identifier of the target RF device among the plurality of RF devices; The configuration unit 504 is used to configure the multiple radio frequency devices to be configured based on the radio frequency configuration information corresponding to the target radio frequency front-end unit, so as to realize the single-software and multi-hardware functions of the motherboard hardware.

[0068] In some embodiments, the processing module 503 is further configured to determine a target radio frequency device from the plurality of radio frequency devices, and obtain a target device identifier and a target configuration identifier of the target radio frequency device; if the candidate radio frequency front-end unit meets a first preset determination condition, then the candidate radio frequency front-end unit is determined to be a pending radio frequency front-end unit; wherein, the first preset determination condition includes the device identifier of the target radio frequency device matching the target device identifier, and the device identifiers of other radio frequency devices not matching the target device identifier; if the configuration identifier of the target radio frequency device in the pending radio frequency front-end unit matches the target configuration identifier, then the pending radio frequency front-end unit is determined to be a target radio frequency front-end unit.

[0069] In some embodiments, the processing module 503 is further configured to determine whether the candidate RF front-end unit meets a second preset determination condition if the configuration identifier of the target RF device in the candidate RF front-end unit does not match the target configuration identifier; wherein, the second preset determination condition includes the device identifier of the target RF device matching the target device identifier, and the existence of a device identifier of another RF device matching the target device identifier; if the candidate RF front-end unit meets the second preset determination condition, then the candidate RF front-end unit is determined to be the target RF front-end unit.

[0070] In some embodiments, the configuration identifier includes a product identifier and a manufacturer identifier, and the radio frequency configuration information includes radio frequency parameters of a plurality of radio frequency devices; The configuration unit 504 is further configured to obtain product identifiers and manufacturer identifiers of multiple radio frequency devices in the target radio frequency front-end unit; obtain radio frequency parameters of multiple radio frequency devices in the target radio frequency front-end unit based on the product identifiers and manufacturer identifiers; and configure the multiple radio frequency devices to be configured based on the radio frequency parameters of multiple radio frequency devices in the target radio frequency front-end unit to realize the single-software and multi-hardware functions of the motherboard hardware.

[0071] In some embodiments, the processing module 503 is further configured to obtain the original device identifiers of multiple radio frequency devices in each candidate radio frequency front-end unit; initialize the original device identifiers to obtain the device identifiers of multiple radio frequency devices in each candidate radio frequency front-end unit.

[0072] In some embodiments, the plurality of radio frequency devices include, but are not limited to, at least two of a transmitter module, a multimode multi-frequency power amplifier, an antenna switch module, a low-noise amplifier, and a tuner.

[0073] This disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the methods disclosed in this disclosure.

[0074] Figure 6 A schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this disclosure is shown. For example... Figure 6 As shown, the electronic device 600 includes at least one processor 601 and a memory 602 coupled to the processor 601. The processor 601 can perform the corresponding steps in the methods disclosed in the embodiments of this disclosure.

[0075] The processor 601 described above can also be referred to as a Central Processing Unit (CPU), which can be an integrated circuit chip with signal processing capabilities. Each step in the method disclosed in this embodiment can be implemented by the integrated logic circuitry in the processor 601 or by software instructions. The processor 601 can be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this embodiment can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can be located in the memory 602, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The processor 601 reads information from the memory 602 and, in conjunction with its hardware, completes the steps of the method described above.

[0076] Furthermore, various operations / processes according to this disclosure, implemented via software and / or firmware, can be transmitted from a storage medium or network to a computer system with a dedicated hardware architecture, for example, Figure 7 The computer system 700 shown is equipped with the programs that constitute the software. When various programs are installed, the computer system is able to perform various functions, including functions such as those described above. Figure 7 A schematic diagram of the structure of a computer system provided in an exemplary embodiment of this disclosure is shown.

[0077] Computer system 700 is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0078] like Figure 7 As shown, the computer system 700 includes a computing unit 701, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 702 or a computer program loaded from a storage unit 708 into a random access memory (RAM) 703. The RAM 703 may also store various programs and data required for the operation of the computer system 700. The computing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0079] Multiple components in the computer system 700 are connected to the I / O interface 705, including: an input unit 706, an output unit 707, a storage unit 708, and a communication unit 709. The input unit 706 can be any type of device capable of inputting information into the computer system 700. The input unit 706 can receive input numerical or character information and generate key signal inputs related to user settings and / or function control of the electronic device. The output unit 707 can be any type of device capable of presenting information and may include, but is not limited to, a monitor, speaker, video / audio output terminal, vibrator, and / or printer. The storage unit 708 may include, but is not limited to, a hard disk and an optical disk. The communication unit 709 allows the computer system 700 to exchange information / data with other devices via a network such as the Internet, and may include, but is not limited to, a modem, network card, infrared communication device, wireless communication transceiver, and / or chipset, such as Bluetooth™ devices, WiFi devices, WiMax devices, cellular communication devices, and / or the like.

[0080] The computing unit 701 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the various methods and processes described above. For example, in some embodiments, the methods disclosed in this disclosure can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program can be loaded and / or installed on an electronic device via ROM 702 and / or communication unit 709. In some embodiments, the computing unit 701 can be configured to perform the methods disclosed in this disclosure by any other suitable means (e.g., by means of firmware).

[0081] This disclosure also provides a computer-readable storage medium, wherein when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform the methods disclosed in this disclosure.

[0082] The computer-readable storage medium in this disclosure can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. The aforementioned computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specifically, the aforementioned computer-readable storage medium may include electrical connections based on one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0083] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0084] This disclosure also provides a computer program product, including a computer program, wherein when the computer program is executed by a processor, it implements the methods disclosed in the embodiments of this disclosure.

[0085] In embodiments of this disclosure, computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include, but are not limited to, object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)), or it can be connected to an external computer.

[0086] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0087] The modules, components, or units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the modules, components, or units do not necessarily constitute a limitation on the module, component, or unit itself.

[0088] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary hardware logic components that can be used include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0089] The above description is merely an illustration of some embodiments of this disclosure and the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0090] While specific embodiments of this disclosure have been described in detail by way of example, those skilled in the art should understand that the examples are for illustrative purposes only and not intended to limit the scope of this disclosure. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the appended claims.

Claims

1. A method for implementing a single-software, multi-hardware RF front-end system, characterized in that, The method is applied to a radio frequency front-end system, and the method comprises: When a mainboard hardware is started, a plurality of candidate radio frequency front-end units connected to a same bus are identified based on a plurality of radio frequency devices to be configured on the mainboard hardware, wherein each of the candidate radio frequency front-end units comprises the plurality of radio frequency devices; A plurality of identification information of each of the radio frequency devices in the plurality of radio frequency devices is read, wherein the identification information comprises a device identifier and a configuration identifier; A target radio frequency front-end unit is determined from the plurality of candidate radio frequency front-end units based on a target device identifier and a target configuration identifier of a target radio frequency device in the plurality of radio frequency devices; The plurality of radio frequency devices to be configured are configured based on radio frequency configuration information corresponding to the target radio frequency front-end unit, so as to realize a single-soft and multi-hard function of the mainboard hardware.

2. The method of claim 1, wherein, The method further comprises: The target radio frequency device is determined from the plurality of radio frequency devices, and the target device identifier and the target configuration identifier of the target radio frequency device are obtained; If the candidate radio frequency front-end unit satisfies a first preset determination condition, the candidate radio frequency front-end unit is determined as a pending radio frequency front-end unit, wherein the first preset determination condition comprises that the device identifier of the target radio frequency device matches the target device identifier, and the device identifiers of other radio frequency devices do not match the target device identifier; If the configuration identifier of the target radio frequency device in the pending radio frequency front-end unit matches the target configuration identifier, the pending radio frequency front-end unit is determined as the target radio frequency front-end unit.

3. The method of claim 2, wherein, The method further comprises: If the configuration identifier of the target radio frequency device in the pending radio frequency front-end unit does not match the target configuration identifier, it is judged whether the candidate radio frequency front-end unit satisfies a second preset determination condition, wherein the second preset determination condition comprises that the device identifier of the target radio frequency device matches the target device identifier, and there is one device identifier of other radio frequency devices matching the target device identifier; If the candidate radio frequency front-end unit satisfies the second preset determination condition, the candidate radio frequency front-end unit is determined as the target radio frequency front-end unit.

4. The method of claim 1, wherein, The configuration identifier comprises a product identifier and a manufacturer identifier, and the radio frequency configuration information comprises radio frequency parameters of the plurality of radio frequency devices; The configuration of the plurality of radio frequency devices to be configured is performed based on the radio frequency parameters of the plurality of radio frequency devices in the target radio frequency front-end unit, so as to realize the single-soft and multi-hard function of the mainboard hardware. The method further comprises: The product identifier and the manufacturer identifier of the plurality of radio frequency devices in the target radio frequency front-end unit are obtained; The radio frequency parameters of the plurality of radio frequency devices in the target radio frequency front-end unit are obtained based on the product identifier and the manufacturer identifier; The configuration of the plurality of radio frequency devices to be configured is performed based on the radio frequency parameters of the plurality of radio frequency devices in the target radio frequency front-end unit, so as to realize the single-soft and multi-hard function of the mainboard hardware.

5. The method of claim 1, wherein, Before the reading of the multiple identification information of each of the multiple radio frequency devices, the method further comprises: obtaining original device identifiers of multiple radio frequency devices in each of the candidate radio frequency front-end units; initializing the original device identifiers to obtain device identifiers of the multiple radio frequency devices in each of the candidate radio frequency front-end units.

6. The method according to any one of claims 1 to 5, wherein, The multiple radio frequency devices include, but are not limited to, at least two of a transmitting module, a multi-mode multi-frequency power amplifier, an antenna switch module, a low-noise amplifier, and a tuner.

7. A single-soft multi-hard implementation apparatus of a radio frequency front-end system, characterized in that, The device is applied to a radio frequency front-end system, and the device comprises: an identification module configured to identify multiple candidate radio frequency front-end units connected to the same bus based on multiple radio frequency devices to be configured on a mainboard hardware when the mainboard hardware is started, wherein each of the candidate radio frequency front-end units comprises the multiple radio frequency devices; a reading module configured to read multiple identification information of each of the multiple radio frequency devices; wherein the identification information comprises a device identifier and a configuration identifier; a processing module configured to determine a target radio frequency front-end unit from the multiple candidate radio frequency front-end units based on a target device identifier and a target configuration identifier of a target radio frequency device in the multiple radio frequency devices; a configuration unit configured to configure the multiple radio frequency devices to be configured based on radio frequency configuration information corresponding to the target radio frequency front-end unit, so as to realize a single-soft multi-hard function of the mainboard hardware.

8. An electronic device comprising a memory, a processor, and a computer program stored on the memory, wherein the computer program, when executed by the processor, is arranged to perform the method of any one of claims 1 to 7. The processor executes the computer program to realize the steps of the method in any one of claims 1-6.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to realize the steps of the method in any one of claims 1-6.

10. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to realize the steps of the method in any one of claims 1-6.

Images