Communication method, apparatus and electronic device

Abstract

This application provides a communication method, apparatus, and electronic device. The method includes: acquiring operation information of a first operating system running on the System-on-a-Chip (SOC), the operation information being associated with a Bluetooth module, the Bluetooth module being configured in the controller MCU of the smart wearable device; generating a first request corresponding to the operation information, and sending the first request to the MCU based on a first communication module; receiving first information corresponding to the first request sent by the MCU based on the first communication module, and converting the first information into second information recognizable by the first operating system; and processing the second information based on the first operating system. This method can effectively solve the problems of low Bluetooth communication efficiency and unreasonable resource allocation in dual-system terminals, and achieve stable operation of functions such as connection, call, and data transmission.

Description

Technical Field

[0001] This application relates to the field of Bluetooth communication technology, and in particular to a communication method, device and electronic device. Background Technology

[0002] As the core communication module of the terminal, Bluetooth's communication efficiency and resource scheduling capabilities under the dual-system architecture directly affect the device's standby time and user experience.

[0003] Currently, integrating dual systems and two independent Bluetooth chips into a single terminal product, with the ability to quickly switch between systems, is a mainstream solution. However, dual Bluetooth chips significantly increase the cost of the terminal. Summary of the Invention

[0004] This application provides a communication method, apparatus, and electronic device to solve the technical problem of high cost in dual-system architecture.

[0005] In a first aspect, embodiments of this application provide a communication method, the communication method comprising:

[0006] Obtain the operation information of the first operating system running on the SOC. The operation information is associated with the Bluetooth module, which is set in the controller MCU of the smart wearable device.

[0007] Generate a first request corresponding to the operation information, and send the first request to the MCU based on the first communication module;

[0008] Based on the first communication module, the first information corresponding to the first request sent by the MCU is received, and the first information is converted into second information that can be recognized by the first operating system.

[0009] The second information is processed based on the first operating system.

[0010] In one possible implementation, the first request corresponding to the operation information includes:

[0011] Based on the first interface, the operation information is processed to obtain the third information. The first interface is used to convert the operation information into information that the Bluetooth module can recognize.

[0012] Based on the communication protocol corresponding to the first communication module, the third information is encapsulated to obtain the first request.

[0013] In one possible implementation, a first request is sent to the MCU based on the first communication module, including:

[0014] Based on the first communication module, the first request is processed to obtain a first request that meets the transmission format of the first bus. The SOC and MCU are connected based on the first bus.

[0015] Based on the first communication module and the first bus, a first request that meets the transmission format of the first bus is sent to the first communication module of the MCU.

[0016] In one possible implementation, converting the first information into second information recognizable by the first operating system includes:

[0017] Based on the communication protocol corresponding to the first communication module, the first information is parsed to obtain the parsed first information;

[0018] Based on the first interface, the parsed first information is converted into second information that can be recognized by the first operating system.

[0019] In one possible implementation, the MCU is used to run a second operating system;

[0020] When the first operating system of the SOC is running, the Bluetooth module in the MCU is in the first Bluetooth mode;

[0021] When the MCU's second operating system is running, the Bluetooth module in the MCU is in the second Bluetooth mode, and the power consumption of the first Bluetooth mode is lower than that of the second Bluetooth mode.

[0022] The power consumption of the smart wearable device running the first operating system and starting the first Bluetooth mode is greater than the power consumption of the smart wearable device running the second operating system and starting the second Bluetooth mode.

[0023] In one possible implementation, the method also includes:

[0024] Obtain the second interface of the SOC, which is the Bluetooth Low Energy underlying interface;

[0025] The second interface is converted into a remote procedure call to obtain the first interface.

[0026] In one possible implementation, the method also includes:

[0027] Based on the first communication module, the fourth information sent by the MCU is received. The fourth information includes sensor data that is transmitted to other devices via the Bluetooth module.

[0028] Based on the first interface, the fourth information is parsed to obtain the fifth information that the first operating system can recognize;

[0029] The fifth piece of information is processed based on the first operating system.

[0030] Secondly, embodiments of this application provide a communication device, which includes an acquisition module, a generation module, a transmission module, a receiving module, a conversion module, and a processing module, wherein:

[0031] The acquisition module is used to acquire the operation information of the first operating system running on the SOC. The operation information is associated with the Bluetooth module, which is set in the controller MCU of the smart wearable device.

[0032] The generation module is used to generate the first request corresponding to the operation information;

[0033] The sending module is used to send a first request to the MCU based on the first communication module;

[0034] The receiving module is used to receive first information corresponding to the first request sent by the MCU, based on the first communication module;

[0035] The conversion module is used to convert the first information into second information that can be recognized by the first operating system;

[0036] The processing module is used to process the second information based on the first operating system.

[0037] Thirdly, embodiments of this application provide an electronic device, including:

[0038] At least one processor and memory;

[0039] The memory stores instructions that the computer executes;

[0040] At least one processor executes computer execution instructions stored in memory, causing at least one processor to perform the communication method described in the first aspect above and various possible designs of the first aspect.

[0041] Fourthly, embodiments of this application provide a chip that stores a computer program, which, when executed by the chip, causes the method provided by either party to be executed.

[0042] Fifthly, embodiments of this application provide a chip module on which a computer program is stored, such that when the computer program is executed by the chip module, the method provided by either party is executed.

[0043] In a sixth aspect, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the communication method described in the first aspect and various possible designs of the first aspect.

[0044] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the communication method described in the first aspect and various possible designs of the first aspect.

[0045] This application provides a communication method, apparatus, and electronic device. The electronic device can obtain operation information of a first operating system running on a System-on-a-Chip (SoC). This operation information is associated with a Bluetooth module, which is located in the controller MCU of a smart wearable device. The electronic device can generate a first request corresponding to the operation information and send the first request to the MCU based on a first communication module. The electronic device can also receive first information corresponding to the first request sent by the MCU based on the first communication module and convert the first information into second information recognizable by the first operating system. The electronic device can then process the second information based on the first operating system. In this method, because the Bluetooth module is deployed on the MCU, shared scheduling of a single Bluetooth hardware resource between the two systems is achieved, eliminating the need for dual Bluetooth chips. Therefore, the hardware resource utilization rate under the dual-system architecture can be improved, and hardware design and deployment costs can be reduced. Furthermore, since cross-system data interaction and format adaptation between the SoC and MCU are completed based on a unified first communication module and standardized interfaces, the request, transmission, and feedback processing flow of Bluetooth-related information is standardized. Therefore, the transmission efficiency of Bluetooth communication between the two systems can be improved, ensuring the stable operation of Bluetooth connection, call, and data transmission functions. Attached Figure Description

[0046] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0047] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0048] Figure 2 This is a schematic diagram illustrating a communication method provided in an embodiment of this application;

[0049] Figure 3 A timing diagram for cross-system interaction in dual-system Bluetooth communication provided in an embodiment of this application;

[0050] Figure 4 A schematic diagram illustrating the process of generating and adapting a first interface as provided in an embodiment of this application;

[0051] Figure 5 This application provides a schematic diagram of a sensor data Bluetooth transmission and processing flow according to an embodiment of the present application.

[0052] Figure 6 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0053] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0054] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0055] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0056] It should be noted that the communication method, device and electronic device provided in this application embodiment can be used in the field of Bluetooth communication technology, or in any field other than the field of Bluetooth communication technology. The application field of the communication method, device and electronic device in this application is not limited.

[0057] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0058] In related technologies, two independent Bluetooth chips (e.g., a main Bluetooth chip and an auxiliary Bluetooth chip) are integrated into the terminal, each connecting to a different operating system. However, dual Bluetooth chips significantly increase the terminal's cost and size, hindering the design of miniaturized wearable devices. Furthermore, they require maintaining separate protocol stacks and drivers, leading to high system resource consumption. The two systems communicate via interfaces such as Serial Peripheral Interface (SPI) and Universal Asynchronous Receiver / Transmitter (UART), with data exchange between the Bluetooth chips achieved through a protocol layer. However, cross-chip communication relies on underlying protocols, resulting in low data transmission efficiency and difficulty in meeting real-time requirements.

[0059] To address the technical problems in related technologies, embodiments of this application provide a communication method. An electronic device can obtain operation information from a first operating system running on a System on Chip (SOC). This operation information is associated with a Bluetooth module, which is located in the microcontroller unit (MCU) of a smart wearable device. The electronic device can process the operation information based on a first interface to obtain third information. The first interface is used to convert the operation information into information recognizable by the Bluetooth module. Based on the communication protocol corresponding to the first communication module, the third information is encapsulated to obtain a first request. The electronic device can receive first information corresponding to the first request sent by the MCU based on the first communication module, and convert the first information into second information recognizable by the first operating system. The electronic device can then process the second information based on the first operating system. In this way, by deploying the Bluetooth module on the MCU, the first interface and standardized communication protocol enable the dual systems to share and schedule a single Bluetooth hardware resource, eliminating the need for dual Bluetooth chips. Therefore, the hardware configuration is simplified, reducing the hardware material and design costs associated with dual Bluetooth chips. Furthermore, since electronic devices can adapt their operation information to the format of the Bluetooth module through the standardized first interface, the efficiency of cross-system Bluetooth communication can be improved when processing Bluetooth-related operation information between the two systems.

[0060] Below, in conjunction with Figure 1 The application scenarios of the embodiments of this application will be described.

[0061] Figure 1 Please refer to the schematic diagram of an application scenario provided in this application embodiment. Figure 1 This includes a smart wearable device and an external Bluetooth interaction device. The smart wearable device employs a dual-system hardware architecture of SOC and MCU, serving as the core execution carrier for the dual-system dual-Bluetooth communication method of this application. The external Bluetooth interaction device is the Bluetooth data interaction object for the smart wearable device, and can specifically be a mobile phone, Bluetooth headset, smart home device, or other device with Bluetooth communication capabilities. The SOC of the smart wearable device runs a first operating system, acting as the initiator and processor of Bluetooth-related operation information. The MCU runs a second operating system, and the Bluetooth module is deployed on the MCU, undertaking all Bluetooth underlying communication functions of the smart wearable device. A bidirectional data interaction link is established between the SOC and the MCU via SPI and the first communication module. Data transmission is achieved between the Bluetooth module on the MCU and the external Bluetooth interaction device via Bluetooth wireless communication.

[0062] In this way, by deploying the Bluetooth module exclusively on the MCU and building a standardized cross-system communication link between the SOC and the MCU based on the first communication module, the first operating system on the SOC side can remotely call the Bluetooth module function on the MCU side through a request-response method, realizing unified scheduling and collaborative use of Bluetooth resources by the SOC and MCU dual systems. This effectively solves the problems of low Bluetooth communication efficiency and unreasonable resource allocation between dual system terminals. At the same time, it optimizes the overall power consumption performance of smart wearable devices by relying on the low power consumption characteristics of the MCU side, ensuring the stable operation of Bluetooth connection, voice call, data transmission and other functions.

[0063] It should be noted that, Figure 1 These are merely examples of application scenarios for the embodiments of this application, and are not intended to limit the application scenarios of the embodiments of this application. The following detailed description uses specific embodiments to illustrate the technical solutions of this application and how these solutions solve the aforementioned technical problems. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0064] Figure 2 For a flowchart illustrating a communication method provided in this application, please refer to [link / reference]. Figure 2 The method may include:

[0065] S201. Obtain the operation information of the first operating system running on the SOC.

[0066] The execution subject of this application embodiment can be an electronic device or a communication device within an electronic device. The communication device can be implemented based on software, or it can be implemented based on a combination of software and hardware; this application embodiment does not limit this.

[0067] In this context, the SOC can be a quad-core / octa-core low-power processing chip integrated into a smart wearable device. For example, the SOC can be the SOC chip for wearable smart terminal devices such as smartwatches and smart bracelets. These chips integrate core components such as processors, memory, and various communication interfaces, with computing power adapted to the application operation requirements of smart wearable devices while also taking power consumption control into account. This application does not limit this aspect.

[0068] In some embodiments, the first operating system can be a system that interacts with the user. For example, the first operating system can run on a System-on-a-Chip (SoC) and respond to user commands such as Bluetooth connection, voice calls, and data transmission.

[0069] In some embodiments, the operation information may include Bluetooth operation commands triggered by the user through interactive methods such as tapping, swiping, or pressing physical buttons. For example, the operation information may be Bluetooth pairing / connection commands, Bluetooth disconnection commands, Bluetooth voice call start / stop commands, Bluetooth data transmission commands triggered by the user clicking on Bluetooth-related controls on the device, and Bluetooth-related shortcut operation commands triggered by pressing physical buttons on the device.

[0070] It should be noted that electronic devices can obtain the operation information of the first operating system running on the SOC according to any feasible implementation method, and the embodiments of this application do not limit this.

[0071] S202, Generate the first request corresponding to the operation information.

[0072] The first request can be used to request the execution of instructions or functions corresponding to the operation information. For example, the first request can be a pairing connection request for a Bluetooth device or a data transmission request for a Bluetooth device; however, this embodiment does not limit this.

[0073] In some embodiments, the electronic device can generate a first request corresponding to the operation information based on the following feasible implementation: processing the operation information through a first interface to obtain third information; the first interface is used to convert the operation information into information recognizable by the Bluetooth module, and encapsulating the third information based on the communication protocol corresponding to the first communication module to obtain the first request. This can improve the efficiency of information conversion and encapsulation, and enhance the compatibility and stability of cross-system data transmission.

[0074] The third information can be used as intermediate information after the operation information has been formatted and converted. For example, the third information can be used to convert the Bluetooth pairing command of the first operating system on the SOC side into pairing operation data that is common to the Bluetooth module, or to convert the Bluetooth data transmission command into transmission information that the Bluetooth module can recognize.

[0075] In some embodiments, the Bluetooth module can be used for Bluetooth wireless communication. For example, a smart wearable device can send Bluetooth data to a mobile phone via the Bluetooth module. For example, a smart wearable device can receive Bluetooth data sent by a mobile phone via the Bluetooth module. For example, a smart wearable device can collect a user's real-time heart rate and send the real-time heart rate to a mobile phone via the Bluetooth module.

[0076] For ease of understanding, the following examples are provided, but are not intended to limit the embodiments of this application. For example, the Bluetooth module can be a low-power Bluetooth chip integrated into the MCU, capable of performing operations such as pairing and connecting a mobile phone / Bluetooth headset, wireless transmission of sensor data via Bluetooth, and audio data transmission and reception for Bluetooth voice calls.

[0077] In some embodiments, the first interface can enable conversion and adaptation between different information formats. For example, the first interface can be a low-power Bluetooth underlying adapter interface converted by Remote Procedure Call (RPC), which can convert high-level Bluetooth operation instructions of the first operating system into low-level hardware instructions that the Bluetooth module can recognize, and can also convert the execution results of the Bluetooth module into an information format that the operating system can recognize.

[0078] RPC can be used to implement cross-system function calls and instruction interactions between different processing units and different operating systems. For example, the first operating system on the SOC side can operate and control the Bluetooth module on the MCU side, and this application embodiment does not limit this.

[0079] S203. Based on the first communication module, send a first request to the MCU. The first communication module can be used to realize cross-system data interaction between the SOC and the MCU. For example, the first communication module can be responsible for encapsulating and adapting the request from the SOC side, or it can be responsible for receiving and parsing the request from the MCU side.

[0080] In some embodiments, the communication protocol can be used to standardize the format, timing, verification, and interaction rules for data transmission between the first communication module and the SOC and MCU. For example, the communication protocol can be a proprietary communication protocol based on SPI, containing fixed formats such as data frame header, instruction type, data length, valid data, check bits, and frame trailer; or it can be a universal serial communication protocol corresponding to a Universal Asynchronous Receiver / Transmitter (UART), adapting to the bus transmission requirements of the SOC and MCU. This ensures the accuracy, integrity, and orderliness of data transmission, effectively avoiding problems such as data loss, out-of-order delivery, and parsing failures.

[0081] In some embodiments, SPI can be the underlying transmission carrier of the communication module, and this application does not limit this. For example, SPI can be the core hardware communication bus between the SOC and the MCU.

[0082] In some embodiments, UART can be an asynchronous serial communication bus commonly used in smart devices, with a data transmission rate lower than SPI, which is a conventional method for communication between hardware units in existing dual-system terminals.

[0083] In some embodiments, the electronic device can send a first request to the MCU based on the first communication module in the following feasible implementation: The first request is processed by the first communication module to obtain a first request that conforms to the transmission format of the first bus. The SOC and MCU are connected via the first bus, and the electronic device can send the first request conforming to the transmission format of the first bus to the first communication module of the MCU based on the first communication module and the first bus. This enables format adaptation and standardized transmission of the first request, improving the reliability and transmission efficiency of data interaction between the SOC and the MCU.

[0084] The first bus can be a hardware communication link between the SOC and the MCU. For example, the first bus can be an SPI serial peripheral interface, or a short-range serial communication bus such as UART suitable for smart wearable devices. In this way, due to its high-speed transmission and simple wiring characteristics, it can meet the requirements of hardware miniaturization and high-efficiency data transmission in smart wearable devices.

[0085] In some embodiments, the electronic device can use the MCU to run a second operating system based on the following feasible implementation: When the electronic device is running the first operating system of the SOC, the Bluetooth module in the MCU is in a first Bluetooth mode; when the second operating system of the MCU is running, the Bluetooth module in the MCU is in a second Bluetooth mode. The power consumption of the first Bluetooth mode is lower than that of the second Bluetooth mode, and the power consumption of the smart wearable device running the first operating system and activating the first Bluetooth mode is greater than that of the smart wearable device running the second operating system and activating the second Bluetooth mode. In this way, by matching the appropriate Bluetooth power consumption mode for different system operation, ineffective high-power operation is avoided, and combined with the low hardware power consumption characteristics of the MCU itself, the working stability of Bluetooth communication of the smart wearable device is improved under different operating scenarios.

[0086] The second operating system can provide a runtime environment for the MCU, controlling the MCU and Bluetooth module to operate according to preset logic. For example, the second operating system can be a real-time operating system for low-power peripheral management. Thus, due to its low power consumption and high real-time performance, the second operating system can enable lightweight control scenarios for smart wearable devices.

[0087] In some embodiments, the first Bluetooth mode can be used to enable the Bluetooth module to operate with low power consumption while the SOC's first operating system is running. For example, the first Bluetooth mode can be a low-power standby mode, a low-data-rate connection mode, or a periodic broadcast mode, maintaining only basic Bluetooth communication with low power consumption.

[0088] In some embodiments, the second Bluetooth mode can be used to enable the Bluetooth module to meet more complex or higher-intensity communication needs when running a second operating system on the MCU. For example, the second Bluetooth mode can be a normal operating mode, a full-function communication mode, or a continuous data transmission mode, supporting full Bluetooth services and providing stronger communication capabilities.

[0089] S204. Based on the first communication module, receive the first information corresponding to the first request of the MCU, and convert the first information into second information that can be recognized by the first operating system.

[0090] The first information can be used to characterize the response result or feedback data after the Bluetooth module on the MCU executes the first request. For example, the first information can be raw communication data returned by the MCU, such as Bluetooth scan results, Bluetooth connection status, data transmission and reception response, and Bluetooth module status information. This application embodiment does not limit this.

[0091] The second information can be used to be recognized, parsed, and processed by the first operating system on the SOC. For example, the second information can be a list of Bluetooth devices that the first operating system can directly display, a connection success message, a data reception completion status, etc. This application embodiment does not limit this.

[0092] In some embodiments, the electronic device can convert the first information into second information recognizable by the first operating system based on the following feasible implementation: parsing the first information according to the communication protocol corresponding to the first communication module to obtain parsed first information; and converting the parsed first information into second information recognizable by the first operating system based on the first interface. In this way, since the electronic device can perform standardized parsing of the first information through a unified communication protocol, the recognition efficiency and processing speed of cross-system information can be improved when parsing and converting Bluetooth information returned by the MCU. Furthermore, since the parsing process follows a unified protocol and the conversion process is completed through a dedicated interface, the reliability and stability of Bluetooth communication between the SOC and the MCU can be improved.

[0093] S205. Based on the first operating system, process the second information.

[0094] Processing the second information may include: reporting the second information to the application layer of the first operating system, or updating the Bluetooth status of the electronic device based on the second information; this embodiment of the application does not limit this. For example, when the second information is Bluetooth device connection status information, the electronic device may display on the user interface whether Bluetooth is connected or disconnected based on the second information; when the second information is a list of devices scanned by Bluetooth, the electronic device may display the device list to the user.

[0095] Below, in conjunction with Figure 3This embodiment provides a detailed explanation of the cross-system interaction via dual-system Bluetooth communication.

[0096] Figure 3 This is a timing diagram for cross-system interaction in dual-system Bluetooth communication, provided as an embodiment of this application.

[0097] in, Figure 3 Using dual-system Bluetooth connectivity and data interaction as a typical scenario, the full-process cross-system interaction logic between the SOC and MCU ends, from operation initiation, command transmission, Bluetooth execution to result feedback, is clearly demonstrated. The participating entities and core interaction steps are as follows:

[0098] T2: Connection Request Initiation: The first communication module on the SOC side sends a "connection request" to the first communication module on the MCU side. This request is a standardized Bluetooth connection command after being converted by the first interface and encapsulated by the communication protocol, which corresponds to the step of generating and sending the first request in S202 of this application.

[0099] For ease of understanding, the following examples are provided, but they are not intended to limit the embodiments of this application. For example, the connection request may carry information such as the MAC address and connection parameters of the target Bluetooth device, which is used to trigger the Bluetooth module on the MCU to perform a connection operation.

[0100] T3: The operation information triggers the first operating system on the SOC to send Bluetooth operation information (such as a Bluetooth connection command triggered by the user) to the first communication module on the SOC, providing an initial command source for the generation of the connection request, corresponding to the step of obtaining operation information in S201 of this application.

[0101] T5: Connection confirmation feedback. The first communication module on the MCU side returns a "connection confirmation" to the first communication module on the SOC side. This confirmation information is the response result of the Bluetooth module on the MCU side after performing the connection operation. After being encapsulated by the communication protocol, it is fed back to the SOC side through the first bus, which corresponds to the step of receiving and converting the first information in S203 of this application.

[0102] For ease of understanding, the following examples are provided, but are not intended to limit the embodiments of this application. For example, connection confirmation may include information such as connection success status and device handle, used to inform the SOC side that a Bluetooth connection has been established.

[0103] T6-T7: Data transmission and interaction: The first computer common channel and the first communication module on the MCU side sequentially perform "data transmission" to realize business data interaction after the Bluetooth connection is established. Among them, the data on the SOC side is encapsulated by the first communication module and transmitted to the MCU side through the first bus. After the Bluetooth module on the MCU side performs data transmission and reception operations, it feeds back the results to the SOC side through the first bus, which corresponds to the core process of cross-system data transmission and processing in this application.

[0104] For ease of understanding, the following examples are provided, but are not intended to limit the embodiments of this application. For example, data transmission may include Bluetooth audio data, sensor-collected data, etc., to ensure the normal operation of Bluetooth services between the two systems.

[0105] T8-T9: Disconnection Notification and Execution: The first communication module on the MCU side sends a "disconnection notification" to the Bluetooth module on the MCU side, triggering the Bluetooth module to perform a connection disconnection operation; after the Bluetooth module completes the disconnection, it feeds back the disconnection status to the first communication module on the MCU side, and then feeds back to the SOC side via the first bus, completing the closed loop of the entire Bluetooth communication process.

[0106] For ease of understanding, the following examples are provided, but are not intended to limit the embodiments of this application. For example, a disconnection notification can be used to actively terminate a Bluetooth connection, or to trigger a connection disconnection under abnormal circumstances, ensuring the security and stability of device communication.

[0107] exist Figure 2 Based on the embodiments shown, the following, in conjunction with Figure 4 The generation and adaptation process of the first interface in the above communication is explained in detail.

[0108] Figure 4 This is a schematic diagram illustrating the process of generating and adapting a first interface according to an embodiment of this application. Please refer to... Figure 4 Specifically, it includes the following steps:

[0109] S401, Obtain the second interface of the SOC.

[0110] The second interface can be used to provide a Bluetooth low-level operation interface for the SOC. For example, the second interface can be the native low-power Bluetooth low-level interface of the first operating system on the SOC side, used to interact with the Bluetooth protocol stack.

[0111] S402. Perform a remote procedure call conversion on the second interface to obtain the first interface.

[0112] RPC can be used to implement cross-system interface calls and data interaction between the SOC and MCU. For example, Remote Procedure Call can encapsulate the second interface on the SOC side into a standardized interface that can be called across hardware and systems. In this way, since the first operating system can control and transmit data to the Bluetooth module on the MCU side through the converted first interface, and can also receive information from the MCU side, bidirectional cross-system interaction between the SOC and MCU can be achieved.

[0113] It should be noted that the above RPC conversion process can be executed by the communication device of the terminal device or the dedicated processing module of the SOC. The converted first interface has bidirectional adaptation capability, which can convert the operation information on the SOC side into information that the Bluetooth module can recognize, and can also convert the information fed back by the Bluetooth module on the MCU side into information that the first operating system can recognize. No additional hardware components are required throughout the process. Cross-system information compatibility transmission can be achieved through software-level interface conversion, which can meet the design requirements of miniaturization and low power consumption of smart wearable devices.

[0114] In this way, since electronic devices can obtain the native second interface of the SOC as a basis, and combine the cross-system conversion capability of RPC, the compatibility and standardization of interface adaptation can be improved when generating and adapting the first interface, ensuring that the first interface can accurately connect the Bluetooth module on the SOC side and the MCU side.

[0115] Based on any of the above embodiments, the following, in conjunction with Figure 5 The paper provides a detailed explanation of the data reception, parsing, and processing processes of electronic devices in the aforementioned communication.

[0116] Figure 5 This is a schematic diagram illustrating a sensor data Bluetooth transmission and processing flow provided in an embodiment of this application. Please refer to... Figure 5 Specifically, it includes the following steps:

[0117] S501. Based on the first communication module, receive the fourth information sent by the MCU. The fourth information includes sensor data transmitted to other devices via the Bluetooth module.

[0118] The fourth piece of information can be used to characterize sensor-related data collected or transmitted by the MCU via the Bluetooth module. For example, the fourth piece of information can be raw sensor data or packaged data such as accelerometer data, heart rate sensor data, gyroscope data, and position information. This application embodiment does not limit this.

[0119] S502. Based on the first interface, the fourth information is parsed to obtain the fifth information that the first operating system can recognize.

[0120] The fifth piece of information can be directly recognized, displayed, or further processed by the first operating system on the SOC. For example, the fifth piece of information can be formatted data such as heart rate, step count, exercise status, and device status that can be directly displayed by the first operating system; however, this embodiment does not limit this.

[0121] S503, based on the first operating system, processes the fifth piece of information.

[0122] The processing of the fifth piece of information can include reporting it to the application layer, displaying it to the user, or storing or uploading it to a server. For example, an electronic device can display parsed heart rate, step count, and other data on the interface or save it to a local log through the first operating system. In this way, since the electronic device can reliably receive sensor data uploaded by the MCU through the first communication module and perform unified parsing and conversion of the data using the first interface, the efficiency and compatibility of receiving and parsing Bluetooth sensor data can be improved.

[0123] Figure 6 A schematic diagram of the communication device provided in this application. Please refer to [link / reference]. Figure 6 The communication device 600 includes an acquisition module 601, a generation module 602, a transmission module 603, a receiving module 604, a conversion module 605, and a processing module 606, wherein:

[0124] The acquisition module 601 is used to acquire the operation information of the first operating system running on the on-chip system SOC. The operation information is associated with the Bluetooth module, which is set in the controller MCU of the smart wearable device.

[0125] Generation module 602 is used to generate the first request corresponding to the operation information;

[0126] The sending module 603 is used to receive first information corresponding to the first request sent by the MCU based on the first communication module;

[0127] The receiving module 604 is used to receive first information corresponding to the first request sent by the MCU based on the first communication module;

[0128] Conversion module 605 is used to convert the first information into second information that can be recognized by the first operating system;

[0129] The processing module 606 is used to process the second information based on the first operating system.

[0130] In one possible implementation, the generation module 602 is specifically used for:

[0131] Based on the first interface, the operation information is processed to obtain the third information. The first interface is used to convert the operation information into information that the Bluetooth module can recognize.

[0132] Based on the communication protocol corresponding to the first communication module, the third information is encapsulated to obtain the first request.

[0133] In one possible implementation, the sending module 603 is specifically used for:

[0134] Based on the first communication module, the first request is processed to obtain a first request that meets the transmission format of the first bus. The SOC and MCU are connected based on the first bus.

[0135] Based on the first communication module and the first bus, a first request that meets the transmission format of the first bus is sent to the first communication module of the MCU.

[0136] In one possible implementation, the receiving module 604 is specifically used for:

[0137] Based on the first communication module, the first information corresponding to the first request sent by the MCU is received;

[0138] In one possible implementation, the conversion module 605 is specifically used for:

[0139] Based on the communication protocol corresponding to the first communication module, the first information is parsed to obtain the parsed first information;

[0140] Based on the first interface, the parsed first information is converted into second information that can be recognized by the first operating system.

[0141] In one possible implementation, processing module 606 is specifically used for:

[0142] The second information is processed based on the first operating system.

[0143] In one possible implementation, the MCU is used to run a second operating system;

[0144] When the first operating system of the SOC is running, the Bluetooth module in the MCU is in the first Bluetooth mode;

[0145] When the MCU's second operating system is running, the Bluetooth module in the MCU is in the second Bluetooth mode, and the power consumption of the first Bluetooth mode is lower than that of the second Bluetooth mode.

[0146] The power consumption of the smart wearable device running the first operating system and starting the first Bluetooth mode is greater than the power consumption of the smart wearable device running the second operating system and starting the second Bluetooth mode.

[0147] In one possible implementation, the device further includes an interface conversion module, which is used for:

[0148] Obtain the second interface of the SOC, which is the Bluetooth Low Energy underlying interface;

[0149] The second interface is converted into a remote procedure call to obtain the first interface.

[0150] In one possible implementation, the device further includes a sensor data processing module, which is used for:

[0151] Based on the first communication module, the fourth information sent by the MCU is received. The fourth information includes sensor data that is transmitted to other devices via the Bluetooth module.

[0152] Based on the first interface, the fourth information is parsed to obtain the fifth information that the first operating system can recognize;

[0153] The fifth piece of information is processed based on the first operating system.

[0154] The communication device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0155] The communication device shown in the embodiments of this application can be a chip, hardware module, processor, etc. Of course, the communication device can be in other forms, and the embodiments of this application do not specifically limit it.

[0156] Figure 7 This is a schematic diagram of the structure of an electronic device provided in this embodiment. Please refer to [link / reference]. Figure 7 The diagram illustrates a structural schematic of an electronic device 700 suitable for implementing this embodiment. The electronic device may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, personal digital assistants (PDAs), portable Android devices (PADs), portable media players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 7 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0157] like Figure 7As shown, the electronic device 700 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the electronic device 700. The processing 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.

[0158] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 An electronic device 700 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0159] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 709, or installed from storage device 708, or installed from ROM 702. When the computer program is executed by processing device 701, it performs the functions defined in the methods of embodiments of this application.

[0160] It should be noted that the computer-readable medium described above in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having 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 device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0161] 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.

[0162] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

[0163] This application provides a computer-readable storage medium storing computer-executable instructions. When a processor executes the computer-executable instructions, it implements various methods that may be involved in the above embodiments.

[0164] This application provides a computer program product, including a computer program that, when executed by a processor, implements various methods that may be involved in the above embodiments.

[0165] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" 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 can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0166] 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 application. 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.

[0167] The units described in the embodiments of this application can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0168] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, 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.

[0169] In the context of this application, a machine-readable medium 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. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0170] It should be noted that the terms "a" and "a plurality of" used in this application 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".

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

[0172] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and provisions. The data may include information, parameters and messages, such as flow switching indication information.

[0173] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application 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 with similar functions disclosed in this application.

[0174] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Multitasking and parallel processing may be advantageous in certain contexts. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this application. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely exemplary forms of implementing the claims.

Claims

1. A communication method, characterized in that, Applied to a system-on-a-chip (SoC), the method includes: Obtain the operation information of the first operating system running on the SOC, the operation information being associated with the Bluetooth module, the Bluetooth module being configured in the controller MCU of the smart wearable device; Generate a first request corresponding to the operation information, and send the first request to the MCU based on the first communication module; Based on the first communication module, the system receives first information corresponding to the first request sent by the MCU, and converts the first information into second information recognizable by the first operating system. The second information is processed based on the first operating system.

2. The method according to claim 1, characterized in that, Generating the first request corresponding to the operation information includes: Based on the first interface, the operation information is processed to obtain the third information. The first interface is used to convert the operation information into information that the Bluetooth module can recognize. Based on the communication protocol corresponding to the first communication module, the third information is encapsulated to obtain the first request.

3. The method according to claim 1, characterized in that, Based on the first communication module, the first request is sent to the MCU, including: Based on the first communication module, the first request is processed to obtain a first request that meets the transmission format of the first bus, and the SOC and the MCU are connected based on the first bus; Based on the first communication module and the first bus, a first request that satisfies the transmission format of the first bus is sent to the first communication module of the MCU.

4. The method according to claim 2, characterized in that, Converting the first information into second information recognizable by the first operating system includes: Based on the communication protocol corresponding to the first communication module, the first information is parsed to obtain the parsed first information. Based on the first interface, the parsed first information is converted into second information that can be recognized by the first operating system.

5. The method according to any one of claims 1-4, characterized in that, The MCU is used to run a second operating system; When the first operating system of the SOC is running, the Bluetooth module in the MCU is in the first Bluetooth mode; When the second operating system of the MCU is running, the Bluetooth module in the MCU is in a second Bluetooth mode, and the power consumption of the first Bluetooth mode is lower than that of the second Bluetooth mode. The power consumption of the smart wearable device when running the first operating system and activating the first Bluetooth mode is greater than the power consumption of the smart wearable device when running the second operating system and activating the second Bluetooth mode.

6. The method according to any one of claims 2-4, characterized in that, The method further includes: Obtain the second interface of the SOC, where the second interface is a low-power Bluetooth underlying interface; The second interface is converted into a remote procedure call to obtain the first interface.

7. The method according to any one of claims 1-4, characterized in that, The method further includes: Based on the first communication module, the fourth information sent by the MCU is received, which includes sensor data transmitted to other devices via the Bluetooth module. Based on the first interface, the fourth information is parsed to obtain the fifth information that the first operating system can recognize; The fifth piece of information is processed based on the first operating system.

8. A communication device, characterized in that, It includes an acquisition module, a generation module, a sending module, a receiving module, a conversion module, and a processing module, among which: The acquisition module is used to acquire the operation information of the first operating system running on the SOC. The operation information is associated with the Bluetooth module, which is set in the controller MCU of the smart wearable device. The generation module is used to generate a first request corresponding to the operation information; The sending module is used to send the first request to the MCU based on the first communication module; The receiving module is used to receive first information corresponding to the first request sent by the MCU, based on the first communication module; The conversion module is used to convert the first information into second information that can be recognized by the first operating system; The processing module is used to process the second information based on the first operating system.

9. An electronic device, characterized in that, include: Processor and memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

Images