Communication terminal and method for providing configuration data for a modem

Abstract

Communication terminal (100) comprising the following: a modem (101); a first memory (102) that is configured to store configuration data for the modem; a second memory (103) configured to store firmware for booting the communication terminal; and a processor (104, 301)) configured to execute the firmware for booting the communication terminal and to read the configuration data from the second memory and provide it to the modem controlled by the firmware for booting the communication terminal, where the processor is an application processor of the communication terminal device.

Description

Field of invention

[0001] The embodiments described herein generally relate to communication terminal equipment and methods for providing configuration data for a modem. Background of the invention

[0002] Examples of communication devices are disclosed in US 2003 / 0 031 235 A1 and US 2007 / 0 022 232 A1. The start-up time for a mobile device, such as a mobile phone or tablet computer, should typically be as short as possible to be as convenient as possible for the user. For this reason, approaches to cost-effectively reduce the start-up time of mobile devices are desirable. Summary

[0003] The invention is set out in the attached claims. Brief description of the drawings

[0004] In the drawings, similar reference numerals generally refer to the same parts in all different views. The drawings are not necessarily to scale, as more emphasis is generally placed on illustrating the principles of the invention. Various aspects are explained in the following description with reference to the following drawings, wherein: Fig. 1 shows a communication terminal; Fig. 2 shows a flowchart illustrating a procedure for providing configuration data to a modem; Fig. 3 shows an example of a mobile phone; Fig. 4 shows a flowchart illustrating an example of the process when switching on a mobile phone; Fig. 5 shows a message flow diagram for transferring firmware to a modem; Fig. 6 shows a flowchart for transferring firmware to a modem; Fig. Figure 7 shows an arrangement for storing calibration data on the mobile device; Fig. 8 components of a mobile device for providing the calibration data for the data for the first approach to storing the calibration data are shown; Fig. 9 shows a flowchart illustrating the process of starting up the system for the first approach; Fig. 10 components of a mobile device for providing the calibration data for the data for the second approach to storing the calibration data are shown; Fig. Figure 11 shows a flowchart illustrating the process of starting up the system for the second approach. Description of the embodiments

[0005] The detailed description below refers to the accompanying drawings, which illustrate specific details and aspects of the present disclosure with which the invention can be implemented. Further aspects can also be applied, and structural, logical, and electrical modifications can be made without deviating from the scope of protection of the invention. The different aspects of the present disclosure are not necessarily mutually exclusive, since some aspects of the present disclosure can be combined with one or more other aspects of the present disclosure to form new aspects.

[0006] A modem in a communication terminal may or may not be equipped with memory (e.g., flash memory) for storing modem configuration data, such as the modem's firmware or calibration data. For example, the Android operating system may use a modem without flash memory, which results in a long boot time due to the need to store the configuration data in the modem after the communication terminal starts up. In contrast, the Windows operating system may use a modem with flash memory, for example, because the Microsoft logo needs to appear and due to limitations of the included Windows MBIM (Mobile Broadband Interface Model) driver. However, this results in higher costs (bill of materials) due to the cost of the communication terminal's flash memory.

[0007] In such a case, to support different modem operating modes for Windows and Android, an additional hardware switching circuit may be required due to the different modem designs with regard to flash memory, and a common platform hardware that supports a dual operating system (Android and Windows) may not be possible.

[0008] Regarding calibration data, a communication terminal device that includes a modem (e.g., a mobile phone, tablet, etc.) is typically provided with calibration data during its manufacturing process. However, as mentioned above, a modem with flash memory might be used for a Windows operating system, while a modem without flash memory (i.e., a modem that does not have flash memory) might be used for an Android operating system. Manufacturers (e.g., original equipment manufacturers (OEMs)) of communication terminal devices for Windows and Android, whether installed with one operating system or as dual-boot systems at the operational / production level, typically aim to maintain the same cost (bill of materials).

[0009] For example, different software methods may be used for Android and Windows systems to control the calibration process and write calibration data to the modem's flash memory for a flash-based modem for Windows, and to an eMMC (embedded multimedia card) or UFS (Universal Flash Storage) for an Android modem without flash memory when the communication terminal is provided with calibration data. These software methods are typically incompatible and may involve using modem calibration files in different formats, which delays the manufacturing process. This leads to a significant increase in costs (both in terms of development and bill of materials) for products intended to support a dual-boot operating system, dual operating systems, or multiple operating systems.

[0010] The following approaches, for example, can be used to support both Windows and Android: 1. Independent calibration for each operating system: Store calibration data in the modem's flash memory for Windows and calibration data in an eMMC or UFS partition of the operating system for Android. However, this requires two calibrations to support dual operating systems. Calibration for a typical modem, for example, takes 1.5 minutes when expensive modem calibration equipment is used in the factory. This results in a significant increase in manufacturing costs. 2. (Each time) change the calibration instrument for the modem to be calibrated without flash memory, then move the configuration data to the modem. This may require significant changes to the NVM manager (solid-state storage manager). For example, NVM manager system kernel files may need to be converted to an API format to standardize the formats after calibration. When the modem is reset, the operating system must extract the data and download both NVM data (i.e., calibration data, dynamic and static modem parameters) and modem firmware (FW) to the modem. This requires the development of additional software and validation measures. 3. Using a flash-memory-based modem for both Android and Windows. This allows for a unified data format and storage. However, switching from a modem without flash memory to one with flash memory increases the cost of the communication device. Furthermore, it may be necessary to support both flash-memory-based and non-flash-memory-based solutions for Android if it is not possible or desirable to replace all devices without flash memory with flash-based devices. Resource and time constraints may make this impossible.

[0011] The following describes a communication terminal device that enables a standardization of the calibration process for a variety of operating systems without increasing material costs, but still allows calibration to be handled differently for different operating systems, and also enables a reduction in boot time when using a modem without flash memory.

[0012] Fig. Figure 1 shows a communication terminal 100.

[0013] The communication terminal includes a modem 101, a first memory 102 configured to store configuration data for the modem, a second memory 103 configured to store system boot firmware, and a processor 104 configured to execute the system boot firmware, read the configuration data from memory, and provide it to the modem controlled by the system boot firmware.

[0014] In other words, modem configuration data, which includes modem firmware and / or calibration data and / or static and dynamic operating parameters for the modem, is provided to the modem (e.g., in the modem's DRAM) by the system boot firmware (e.g., BIOS). This can occur, for example, before the operating system loads and after the communication terminal is powered on, e.g., while the communication terminal is still being controlled by the system boot firmware. In other words, the system boot firmware includes instructions for the processor, so that the processor is controlled to provide the configuration data to the modem while the system boot firmware is executing.

[0015] Static operating parameters include, for example, modem-specific parameters such as crystal temperature and aging parameters, etc. There are also a number of calibration operating parameters created by the modem calibration process, such as crystal setting, transmitter power setting, receiver gain settings, etc.

[0016] Dynamic operating parameters include, for example, the last stored cell information of the modem, etc.

[0017] Configuration data, such as the modem firmware image, is stored in a reserved (or, in other words, offloaded) eMMC or UFS storage area of ​​the communication terminal. When the communication terminal is powered on, the firmware (i.e., the terminal's main processor controlled by the firmware) uses a firmware module or driver to load the USB stack IPC (interprocessor communication) and flash the modem, thus powering it up. This involves storing the configuration data in the modem and initiating the modem's startup process.

[0018] A communication terminal can include a modem, memory configured to store configuration data for the modem, and a processing circuit (e.g., a processor) configured to read the configuration data from the memory and provide it to the modem in a state between the communication terminal being powered on and the communication terminal's operating system being started (e.g., by storing it in the modem).

[0019] As mentioned above, booting in a modem configuration without flash memory for Android, e.g., based on the modem driver that loads the USB IPC and starts the modem flashing and booting process, can be rather slow because the operating system boot process typically takes a relatively long time, and the modem flashing and booting only occurs then. Firmware used to boot the system, which provides the modem firmware to the modem (i.e., stores it within the modem), thus enables a shorter flashing and boot time for Android. For Windows, where the included MBIM driver does not support the modem-without-flash-memory approach (in ACM (Adaptive Coding and Modulation) mode) and has strict boot time requirements (2 seconds), the following solution is available, referring to... Fig. The approach described in point 1 involves using a modem without flash memory for Windows, since the firmware for booting the system can store firmware in the modem before Windows is started.

[0020] For calibration data, redundant storage space for modem calibration can be avoided by using a shared calibration data storage location for multiple operating systems and a common mechanism for providing the calibration data to the operating system's driver units. For example, the modem calibration data is stored in a reserved (separate) eMMC or UFS storage area shared by the operating systems, and the system boot firmware reads this data after power-on and provides it to the operating system's modem driver via an ACPI (Advanced Configuration and Power Interface). Alternatively, the calibration data can be stored as part of the variable data storage area of ​​the BIOS EFI (Extensible Firmware Interface), and the operating system drivers use the EFI runtime APLS to read or write the calibration data.Both approaches can be used independently of the operating system and for dual-boot scenarios or for a single operating system, with the hardware material costs being the same in each case.

[0021] Compared to approach 1 of the approaches 1 to 3 described above, the number of calibrations for dual operating systems can be reduced from two to one, resulting in significant manufacturing cost savings. Compared to approach 2, the required development work can be reduced, enabling a shorter time to market, for example, for products with dual operating systems. Compared to approach 3, platform material costs and the workload of the development team can be reduced. This also enables a shorter time to market, for example, for products with dual operating systems.

[0022] The communication terminal 100, for example, introduces a Fig. 2 illustrated procedure.

[0023] Fig. Figure 2 shows a flowchart illustrating a procedure for providing configuration data to a modem, e.g., by a communications terminal.

[0024] In step 201, the communication terminal stores configuration data for the modem.

[0025] In step 202, the communication terminal stores firmware for booting up the system.

[0026] In step 203, the communication terminal executes the firmware to boot the system, reads the configuration data from memory, and provides it to the modem controlled by the firmware to boot the system.

[0027] The following examples relate to further embodiments.

[0028] Example 1 is a communication terminal device as defined in reference to Fig. 1 is described.

[0029] In Example 2, the object from Example 1 may optionally include a third memory that stores an operating system of the communication terminal.

[0030] In Example 3, the item from Example 2 may optionally include a processor configured to read the configuration data from memory and provide it to the modem in a state between the communication terminal being switched on and the communication terminal's operating system being started.

[0031] In Example 4, the item from any of Examples 1 to 3 may optionally include a processor configured to read the configuration data and provide it to the modem in response to the power-on of the communication terminal.

[0032] In Example 5, the item from one of Examples 1 to 4 may optionally include a processor configured to store the configuration data in the modem.

[0033] In Example 6, the item from any of Examples 1 to 5 may optionally include a modem driver, with the processor configured to provide the configuration data to the modem driver.

[0034] In Example 7, the item from Example 6 may optionally include a modem driver configured to store the configuration data in the modem.

[0035] In Example 8, the item from one of Examples 6 to 7 may optionally include a modem driver, which is a modem driver of an operating system of the communication terminal device.

[0036] In Example 9, the item from any of Examples 1 to 8 may optionally include a processor configured to store the configuration data in volatile memory.

[0037] In Example 10, the item from Example 9 may optionally include a processor configured to store the configuration data in volatile memory of the modem.

[0038] In Example 11, the item from one of Examples 9 to 10 may optionally include a processor configured to store the configuration data in main memory of the communication terminal.

[0039] In Example 12, the item from one of Examples 1 to 11 may include configuration data that includes the modem's firmware.

[0040] In Example 13, the item from one of Examples 1 to 12 may optionally include configuration data, which includes calibration data for the modem.

[0041] In Example 14, the item from one of Examples 1 to 13 may include configuration data that includes at least static and / or dynamic operating parameters for the modem.

[0042] In Example 15, the object from one of Examples 1 to 14 may, if necessary, include at least one of first storage and one of second storage in the form of a fixed storage device.

[0043] In Example 16, the item from one of Examples 1 to 15 may optionally include the first storage device in the form of a multimedia card.

[0044] In Example 17, the item from one of Examples 1 to 16 may optionally include at least one first memory and one second memory in the form of a ROM.

[0045] In Example 18, the object from one of Examples 1 to 17 may optionally include the processor in the form of an application processor of the communication terminal device.

[0046] In Example 19, the object from one of Examples 1 to 18 may be a mobile communication device.

[0047] In Example 20, the object from one of Examples 1 to 19 may be a mobile phone or a tablet computer.

[0048] Example 21 is a method for providing configuration data for a modem as described in reference to Fig. 2 described.

[0049] In Example 22, the item from Example 21 may include the storage of an operating system.

[0050] In Example 23, the item from Example 22 can include reading the configuration data from memory and making it available to the modem in a state between turning on the communication terminal and starting the operating system.

[0051] In Example 24, the subject matter from one of Examples 21 to 23 may, if applicable, include reading the configuration data and making it available to the modem in response to the switching on of the communication terminal.

[0052] In Example 25, the item from one of Examples 21 to 24 may include storing the configuration data in the modem.

[0053] In Example 26, the item from one of Examples 21 to 25 may, if applicable, include providing the configuration data for a modem driver.

[0054] In Example 27, the subject from Example 26 may include the modem driver storing the configuration data in the modem.

[0055] In Example 28, the subject matter from one of Examples 26 to 27 may include the mode driver being a modem driver of an operating system.

[0056] In Example 29, the item from one of Examples 21 to 28 may include storing the configuration data in volatile memory.

[0057] In Example 30, the item from Example 29 may, if applicable, include storing the configuration data in a volatile memory of the modem.

[0058] In Example 31, the item from one of Examples 29 to 30 may, if applicable, include storing the configuration data in the modem's main memory.

[0059] In Example 32, the item from one of Examples 21 to 31 may include configuration data that includes firmware of the modem.

[0060] In Example 33, the item from one of Examples 21 to 32 may, if applicable, include configuration data, including calibration data for the modem.

[0061] In Example 34, the item from one of Examples 21 to 33 may include configuration data that includes at least static and / or dynamic operating parameters for the modem.

[0062] In Example 35, the item from one of Examples 21 to 34 may include the storage of at least configuration data and / or firmware for booting the system in a fixed memory.

[0063] In Example 36, the item from one of Examples 21 to 35 may include storing the configuration data on a multimedia card.

[0064] In Example 37, the item from one of Examples 21 to 38 may include the storage of at least configuration data and / or firmware for booting the system in a ROM.

[0065] In Example 38, the item from one of Examples 21 to 37 may optionally include an application processor that executes the firmware to start the system and reads the configuration data from memory and provides it to the modem controlled by the firmware to start the system.

[0066] In Example 39, the object from one of Examples 21 to 38 may be carried out by a communication terminal device.

[0067] In Example 40, the item from one of Examples 21 to 39 may, if necessary, be carried out by a mobile phone or a tablet computer.

[0068] Example 41 is a computer-readable medium on which instructions are stored which, when executed by a processor, cause the processor to perform a procedure for carrying out radio communication according to any one of Examples 21 to 40.

[0069] Example 42 is a communication terminal device comprising: a modem; an element for storing configuration data for the modem; an element for storing firmware for booting the system; and an element for executing the firmware for booting the system and for reading the configuration data from memory and making it available to the modem controlled by the firmware for booting the system.

[0070] In Example 43, the item from Example 42 may optionally include an element for storing an operating system of the communication terminal.

[0071] In Example 44, the item from one of Examples 42 to 43 may optionally include an element for executing the firmware to start the system, which serves to read the configuration data from memory and provide it to the modem in a state between the power-on of the communication terminal and the start of the operating system of the communication terminal.

[0072] In Example 45, the item from one of Examples 42 to 44 may optionally include an element for executing the firmware to start the system, which serves to read the configuration data and provide it to the modem in response to the switching on of the communication terminal.

[0073] In Example 46, the item from one of Examples 42 to 45 may optionally include an element for executing the firmware to start the system, which serves to store the configuration data in the modem.

[0074] In Example 47, the item from one of Examples 42 to 46 may optionally include an element for controlling the modem, wherein the element for executing the firmware to start the system serves to provide the configuration data to the means for controlling the modem.

[0075] In Example 48, the item from Example 47 may optionally include an element for controlling the modem, which serves to store the configuration data in the modem.

[0076] In Example 49, the item from one of Examples 47 to 48 may optionally include an element for controlling the modem, which is a modem driver of an operating system of the communication terminal device.

[0077] In Example 50, the item from one of Examples 42 to 49 may optionally include an element for executing the firmware to start the system, which serves to store the configuration data in volatile memory.

[0078] In Example 51, the item from Example 50 may optionally include an element for executing the firmware to start the system, which serves to store the configuration data in a volatile memory of the modem.

[0079] In Example 52, the item from one of Examples 50 to 51 may optionally include an element for executing the firmware to start the system, which serves to store the configuration data in a main memory of the communication terminal.

[0080] In Example 53, the item from one of Examples 42 to 52 may, if applicable, include configuration data that includes firmware of the modem.

[0081] In Example 54, the item from one of Examples 42 to 53 may, if applicable, include configuration data, including calibration data for the modem.

[0082] In Example 55, the item from one of Examples 42 to 54 may include configuration data that includes at least static and / or dynamic operating parameters for the modem.

[0083] In Example 56, the item from one of Examples 42 to 55 may, if necessary, include at least one element selected from the element for storing the configuration data and the element for storing the firmware for booting the system in the form of a fixed storage device.

[0084] In Example 57, the item from one of Examples 42 to 56 may optionally include an element for storing the configuration data in the form of a multimedia card.

[0085] In Example 58, the item from one of Examples 42 to 57 may, if necessary, include at least one element selected from the element for storing the configuration data and the element for storing the firmware for booting the system in the form of a ROM.

[0086] In Example 59, the item from one of Examples 42 to 58 may optionally include an element for executing the firmware for starting the system in the form of an application processor of the communication terminal.

[0087] In Example 60, the object from one of Examples 42 to 59 may be a mobile communication device.

[0088] In Example 61, the object from one of Examples 42 to 60 may be a mobile phone or a tablet computer.

[0089] It should be noted that one or more features of any of the examples listed above can be combined with any of the other examples.

[0090] The examples are described in more detail below with reference to Fig. 3 described. Although Android and / or Windows are used as examples of operating systems in the following examples, any other operating system, such as Linux, iOS, Blackberry, etc., can also be used.

[0091] Fig. 3 shows a mobile phone 300.

[0092] The 300 mobile phone comprises an application processor 301, a BIOS (ROM) memory 302 (as an example of memory for firmware to boot the system), a modem configuration data memory 303, and a modem 304. The mobile phone also includes the typical equipment of a mobile phone, such as one or more antennas, a display, etc.

[0093] Fig. Figure 4 shows a flowchart 400, which illustrates an example of the process of switching on the mobile phone 300.

[0094] The passage of time in Fig. 4 is done from left to right.

[0095] At the first time point 401, the platform (i.e., the mobile phone) is powered on, and the application processor AP (301) begins executing the BIOS. This means the platform's PMIC (power management IC) starts up, BIOS 302 runs, and the modem baseband reset signal is enabled. Power-on is completed, for example, after a period T0 of 10 ms at a second time point 402. The mobile phone (or more generally, the mobile platform) then begins powering on the modem by enabling the modem-ON signal 407 at the second time point 402 and at its conclusion. Processor 301 executes BIOS 302 and enables the MODEM_POWER_ON signal after the second time point. In this example, the signal needs to be enabled for a period Tp of 50 ms to stabilize the modem PMU (power management unit). After the period Tp at a third time point 403, the modem's boot ROM starts, i.e., the modem begins to execute its boot ROM - Tp=50ms.

[0096] Furthermore, at the second time point (402), the BIOS uses an SMI to enter an SMM and loads the USB driver, e.g., onto the SoC (System on Chip). This is completed after Ts ≤ 50ms.

[0097] At a fourth time point after a period T1 ≤ 150ms after the third time point, the timeout occurs when the HSIC (High Speed ​​Inter Chip) is idle (set to “Boot ROM” and determined by the SOC).

[0098] At a fifth time point 405, after a period T2 ≤ 500ms after the fourth time point, the HSIC enumeration time follows (specified by the ACM and determined by the SOC).

[0099] The modem then loads the flash loader and begins receiving the PSI (primary signed image), the EBL (external boot loader), and the FW (firmware) image. This takes approximately 1 second (T4).

[0100] The operating system is started at the end of T4 and the operating system or user can use the modem at a sixth time 406.

[0101] The transfer of the PSI, EBL, and firmware image files is in Fig. 5 illustrates.

[0102] Fig. Figure 5 shows a message flowchart 500.

[0103] The message flow takes place between a Host 501 (i.e., the host of the firmware), which corresponds, for example, to the application processor 301 controlled by the BIOS 302, and a modem, which corresponds to the modem 304, which includes a Boot ROM 402 and ultimately a PSI 503 (which is not present on the modem at the beginning) as well as an Extended Boot Loader 504 (which is not present on the modem at the beginning).

[0104] In port 505, the host sends a "ATAT..." signal stream to the modem, which the modem acknowledges in port 506. This tells the modem that it expects the modem firmware to be downloaded from the host.

[0105] In 507, the host transmits the PSI (primary signed image) to the modem, which the modem acknowledges in 508.

[0106] The modem executes commands 505, 506, 507, and 508 according to the boot ROM; that is, it executes the boot ROM code. This is in Fig. 6 illustrates.

[0107] Fig. Figure 6 shows a flowchart of 600.

[0108] In 601, the modem executes the boot ROM. This corresponds to 505, 506, 507, 508. Fig. 5.

[0109] In port 602, the modem executes the PSI code. This includes, as in Fig. Figure 5 shows that the modem sends a PSI acknowledgment in 509, receives the EBL from the host 501 in 510, and confirms the successful transmission in 511 if the EBL transmission is successful.

[0110] In 603, the modem executes the EBL. This includes, as in Fig. Figure 5 shows that the modem sends an EBL acknowledgment in 512, and in 513, the host (501) and the modem change the transmission bitrate. Then, after successful execution of the EBL, the host and modem request the correct final modem firmware image in 514 and identify it for download to the modem. After this identification process, the final modem firmware is downloaded.

[0111] In port 604, the modem transmits the firmware. This includes, for example, as described in Fig. Figure 5 shows the transfer of files 1 to n in several transfers in Figure 515.

[0112] Adding together the total flash and boot times of the modem yields the following: T0+Tp+T1+T2+T4+T5=10+50+150+500+1000+500≈2.21 s.

[0113] It should be noted that the time T3 omitted in the formula above is the actual connection time. This is already accounted for with 1 s for the duration of the PSI / EBL / FW loading process. The last 500 ms (T5) correspond to the time the modem needs to boot up as an MBIM device.

[0114] Windows and Android require some time to boot up after the platform is switched on. Windows, for example, takes two seconds to boot, and then it takes about one second for the USB MBIM driver to be ready for the modem. Therefore, it takes a total of three seconds from pressing the device's power button until the MBIM USB driver for the modem is ready. At this point (after three seconds), the modem, according to the formula mentioned above, has already been flashed (2.21 seconds) and is ready for the operating system to boot.

[0115] Below is an example of storing calibration data in a communication terminal, e.g., a mobile device, and providing the calibration data to the modem via the BIOS.

[0116] Fig. Figure 7 shows an arrangement 700 for storing the calibration data on the mobile device.

[0117] The arrangement 700 comprises a mobile device 701, which includes an eMMC 702, an application processor (AP) 703, and a modem 704. The arrangement also includes a PC 705 with a calibration instrument 706 and a calibration frame 707.

[0118] During factory calibration, the Modem 704 is controlled by the PC 705, which manages the modem's calibration (via the Modem Calibration Instrument 706) within the environment of the respective operating system, e.g., Android. The modem receives the calibration data and transfers it to the AP 703 via an HSIC interface. The operating system receives the data and moves it to a GPP (general purpose partition) or a UEFI NVM area in the eMMC (or UFS) 702.

[0119] Different approaches can be used to store the calibration data. One approach, for example, is to store the calibration data in a common GPP area of ​​the eMMC (or UFS), and a second approach is to store the calibration data as part of the variable UEFI area.

[0120] The manufacturing phase then ends and the calibration data is stored in the eMMC / UFS / UEFI NVM. After the product is delivered to the end user, the calibration data is provided by the BIOS during boot and made available to the driver.

[0121] Fig. Figure 8 shows components of a mobile device for providing the calibration data for the first approach to storing the calibration data.

[0122] The components include the BIOS 801 (a UEF or UEFI BIOS in this example), a memory control unit 802, the eMMC 803, a DRAM 804 for mobile devices, the operating system's modem driver 805, the USB-HSIC 806, and the modem 807.

[0123] Fig. Figure 9 shows a flowchart illustrating the process of starting up the system.

[0124] It is assumed that in 901, as with reference to Fig. As explained in section 7, the modem calibration data is stored in the GPP area of ​​the eMMC 803.

[0125] In 902, the BIOS is booted and reads the eMMC modem GPP area and copies the calibration data to a specific DRAM address in the system DRAM 804.

[0126] In 903, the BIOS informs the driver 805 of the DRAM address of the modem calibration data via the ACPI table.

[0127] In version 904, driver 805 obtains the modem calibration data DRAM address from the ACPI table.

[0128] In 905, the driver 805 reads the calibration data from the system DRAM 804.

[0129] In 906, the driver 805 moves the calibration data via the USB-HSIC to the modem 807.

[0130] Processes 901 to 906 are in Fig. 8 is also listed under these reference marks.

[0131] Fig. Figure 10 shows components of a mobile device for providing the calibration data for the second approach to storing the calibration data, i.e. the calibration data is stored as part of the variable data storage area of ​​the BIOS-EFI and the operating system modem driver uses EFI runtime APIs to read / write the calibration data.

[0132] The components include the BIOS 1001 (a UEF or UEFI BIOS in this example), a memory control unit 1002, the eMMC 1003, the operating system's modem driver 1004, the USB-HSIC 1005, and the modem 1006.

[0133] Fig. Figure 11 shows a flowchart illustrating the process of starting up the system.

[0134] It is assumed in 1101 that, as with reference to Fig. Section 7 explains that the modem calibration data is stored as part of the variable area of ​​the UEFI.

[0135] In 1102, the modem driver calls the operating system's UEFI runtime service framework.

[0136] In version 1103, the BIOS reads the data from the variable area of ​​the UEFI and writes it to the modem driver in version 1004.

[0137] In version 1104, the modem driver 1104 moves the calibration data to the modem.

[0138] The events 1101 to 1104 are also in Fig. 10 are listed under these reference numbers.

[0139] Although specific aspects have been described, it is clear to those skilled in the art that various modifications regarding form and details can be made without deviating from the essence and scope of the aspects of this disclosure, which are defined by the appended claims. The scope of protection is specified by the appended claims.

Claims

[1] Communication terminal (100) comprising the following: a modem (101); a first memory (102) that is configured to store configuration data for the modem; a second memory (103) configured to store firmware for booting the communication terminal; and a processor (104, 301)) configured to execute the firmware for booting the communication terminal and to read the configuration data from the second memory and provide it to the modem controlled by the firmware for booting the communication terminal, where the processor is an application processor of the communication terminal device. [2] Communication terminal device according to claim 1, comprising a third memory which stores an operating system of the communication terminal device. [3] Communication terminal according to claim 2, wherein the processor is configured to read the configuration data from memory and provide it to the modem in a state between the power-on of the communication terminal and the start-up of the communication terminal's operating system. [4] Communication terminal according to claim 1, wherein the processor is configured to read the configuration data and provide it to the modem in response to the power-on of the communication terminal. [5] Communication terminal device according to claim 1, wherein the processor is configured to store the configuration data in the modem. [6] Communication terminal device according to claim 1, further comprising a modem driver, wherein the processor is configured to provide the configuration data to the modem driver. [7] Communication terminal device according to claim 6, wherein the modem driver is configured to store the configuration data in the modem. [8] Communication terminal device according to claim 6, wherein the modem driver is a modem driver of an operating system of the communication terminal device. [9] Communication terminal device according to claim 1, wherein the processor is configured to store the configuration data in a volatile memory (804). [10] Communication terminal device according to claim 9, wherein the processor is configured to store the configuration data in a volatile memory of the modem. [11] Communication terminal according to claim 9, wherein the processor is configured to store the configuration data in a main memory of the communication terminal. [12] Communication terminal device according to claim 1, wherein the configuration data comprises firmware of the modem. [13] Communication terminal device according to claim 1, wherein the configuration data includes calibration data for the modem. [14] Communication terminal device according to claim 1, wherein the configuration data includes at least static and / or dynamic operating parameters for the modem. [15] Communication terminal device according to claim 1, wherein at least one memory, selected from first memory and second memory, is a fixed memory. [16] Communication terminal device according to claim 1, wherein the first memory is a multimedia card (702, 803). [17] Communication terminal device according to claim 1, wherein at least one memory, selected from first memory and second memory, is a ROM. [18] Communication terminal device according to claim 1, which is a mobile communication terminal device (300, 701). [19] Communication terminal device according to claim 1, which is a mobile phone or a tablet computer. [20] Method for providing configuration data for a modem, the method comprising: Saving (201) configuration data for the modem; Saving (202) firmware to start up a communication terminal and the execution (203) of the firmware for starting the communication terminal by means of an application processor of the communication terminal and the reading of the configuration data from memory and its provision to the modem controlled by the firmware for starting the communication terminal. [21] Method according to claim 20, comprising storing an operating system. [22] Method according to claim 21, comprising reading the configuration data from the memory and making it available to the modem in a state between the switching on of the communication terminal and the starting of the operating system. [23] Method according to claim 20, comprising reading the configuration data and making it available to the modem in response to the switching on of the communication terminal. [24] Computer-readable medium on which instructions are stored which, when executed by a processor, cause the processor to execute a method for carrying out radio communication according to claim 20.

Images