WO2021057351A1 - 在glibc环境下控制安卓蓝牙的装置、方法及终端设备 - Google Patents

在glibc环境下控制安卓蓝牙的装置、方法及终端设备 Download PDF

Info

Publication number
WO2021057351A1
WO2021057351A1 PCT/CN2020/110493 CN2020110493W WO2021057351A1 WO 2021057351 A1 WO2021057351 A1 WO 2021057351A1 CN 2020110493 W CN2020110493 W CN 2020110493W WO 2021057351 A1 WO2021057351 A1 WO 2021057351A1
Authority
WO
WIPO (PCT)
Prior art keywords
module
bluetooth
message
environment
glibc
Prior art date
Application number
PCT/CN2020/110493
Other languages
English (en)
French (fr)
Inventor
李鹏
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021057351A1 publication Critical patent/WO2021057351A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/545—Interprogram communication where tasks reside in different layers, e.g. user- and kernel-space
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces

Definitions

  • the embodiments of the present application relate to the field of smart devices, and in particular, to a device, method, and terminal device for controlling Android Bluetooth in a glibc environment.
  • Bionic C library is the basic C/C++ library of the Android operating system (Android), and the GNU C library (Gnulibc, referred to as glibc) is the standard C library of the Linux operating system. There are many differences in the implementation of the two, so in Programs linked through the Boinic library during compilation cannot be loaded and run directly in the glibc environment.
  • Some hardware-related driver libraries in the Android environment are usually provided by the hardware manufacturer. If you want to control Android Bluetooth in the glibc environment, you need to develop a matching system for the Linux operating system. Bluetooth hardware, this will undoubtedly increase the cost.
  • the purpose of the embodiments of the present application is to provide an apparatus, method, terminal device, and computer-readable storage medium for controlling Android Bluetooth in a glibc environment.
  • the implementation mode of this application provides a device for controlling Android Bluetooth in a glibc environment, including: a functional interface converter, an application message processing module, a command issuing module, and a message monitoring module; a functional interface converter for integrating the bionic environment
  • the functional interface of Android Bluetooth is converted to the functional interface that can be called by the glibc environment;
  • the communication module is used to communicate with the Bluetooth application, the command issuing module and the message monitoring module;
  • the command issuing module is used to generate messages from the communication module Operation command, and send the operation command to the Bluetooth hardware through the functional interface that can be called by the converted glibc environment;
  • the message monitoring module is used to monitor the message from the Bluetooth hardware, and send the processed message from the Bluetooth hardware to the communication module .
  • the embodiment of the present application also provides a method for controlling Android Bluetooth in a glibc environment, including: a functional interface converter converts the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment; the communication module receives and processes Information from the Bluetooth application; the command issuing module generates operation commands based on the messages from the communication module, and sends the operation commands to the Bluetooth hardware through the functional interface that can be called by the converted glibc environment; the message monitoring module listens to the messages from the Bluetooth hardware, Process the message from the Bluetooth hardware and send it to the communication module; the communication module process the message from the message monitoring module and send it to the Bluetooth application.
  • a functional interface converter converts the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment
  • the communication module receives and processes Information from the Bluetooth application
  • the command issuing module generates operation commands based on the messages from the communication module, and sends the operation commands to the Bluetooth hardware through the functional interface that
  • the embodiment of the present application also provides a terminal device, including the aforementioned device for controlling Android Bluetooth in the glibc environment, a Bluetooth application, and Bluetooth hardware; the Bluetooth application controls the operation of the Bluetooth hardware through the device for controlling Android Bluetooth in the glibc environment, And through the device that controls the Android Bluetooth in the glibc environment to receive the information from the Bluetooth hardware; the Bluetooth hardware receives and executes the operating commands from the device that controls the Android Bluetooth in the glibc environment, and through the device that controls the Android Bluetooth in the glibc environment The information of the Bluetooth hardware is returned to the Bluetooth application.
  • the embodiment of the present application also provides a computer-readable storage medium that stores a computer program, where the computer program is executed by a processor to realize the above-mentioned method for controlling Android Bluetooth in a glibc environment.
  • FIG. 1 is a schematic diagram of a device for controlling Android Bluetooth in a glibc environment in the first embodiment of the present application
  • Fig. 2 is a schematic structural diagram of a functional interface converter in the first embodiment of the present application
  • FIG. 3 is a schematic diagram of the structure of the command issuing module in the first embodiment of the present application.
  • FIG. 4 is a schematic diagram of a device for controlling Android Bluetooth in a glibc environment in the second embodiment of the present application
  • FIG. 5 is a schematic structural diagram of a message processing module in the second embodiment of the present application.
  • FIG. 6 is a schematic diagram of the structure of a protocol management module in the second embodiment of the present application.
  • FIG. 7 is a flowchart of a method for controlling Android Bluetooth in a glibc environment in the third embodiment of the present application.
  • Fig. 8 is a working flow chart of the functional interface converter in the third embodiment of the present application.
  • FIG. 9 is a working flowchart of the command issuing module in the third embodiment of the present application.
  • FIG. 10 is a working flowchart of the message monitoring module in the third embodiment of the present application.
  • FIG. 11 is a flowchart of the initialization of the Bluetooth service framework in the third embodiment of the present application.
  • FIG. 12 is a flowchart of a method for controlling Android Bluetooth in a glibc environment in the fourth embodiment of the present application.
  • FIG. 13 is a working flowchart when the message processing module in the fourth embodiment of the present application delivers a Bluetooth application message
  • FIG. 14 is a working flowchart when the protocol management module sends out the message processing module message in the fourth embodiment of the present application.
  • FIG. 15 is a working flow chart of the protocol management module uploading the message of the message monitoring module in the fourth embodiment of the present application.
  • FIG. 16 is a flowchart when the message processing module uploads the protocol management module message in the fourth embodiment of the present application.
  • FIG. 17 is a schematic diagram of specific implementation of a mobile terminal in the fifth embodiment of the present application.
  • the first embodiment of the present application relates to a device for controlling Android Bluetooth in a glibc environment.
  • the implementation details of the device for controlling Android Bluetooth in the glibc environment of this embodiment will be described in detail below. The following content is provided for ease of understanding and is not necessary for implementing this solution.
  • the device involves a set of Bluetooth service framework, which includes a function interface converter 101, a communication module 102, a command issuing module 103, and a message monitoring module 104.
  • the functional interface converter 101 includes a loading module 1011 and a replacement module 1012.
  • the command issuing module 103 includes a creation module 1031, an operation command generation module 1032, and an operation command sending module 1033.
  • the modules in the Bluetooth service framework and the functional interface converter (Android shared library loader) are located in the glibc environment, and the Android Bluetooth library is located in the bionic environment.
  • the specific structure is shown in Figure 1, including:
  • the functional interface converter 101 is used to convert the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment.
  • the functional interface converter 101 may also be referred to as an Android shared library loader. As shown in FIG. 2, the functional interface converter 101 includes: a loading module 1011 and a replacement module 1012.
  • the loading module 1011 is used to load the shared library of the bionic environment in the glibc environment; the replacement module 1012 is used to replace the interface function provided by the shared library of the bionic environment with the interface function provided by the glibc environment.
  • the functional interface converter 101 supports platforms such as ARM and MIPS, which is not limited here.
  • the hardware abstraction layer of the Android Bluetooth driver is in the form of a dynamic link library in the executable and linkable format (ELF).
  • the Android shared library (Android Bluetooth library) provides basic Bluetooth chip operation interfaces, including basic interfaces such as Bluetooth module enable, Bluetooth module shutdown, and Bluetooth module initialization, which are not limited here.
  • the loading module 1011 first adds the Android shared library file in the glibc environment, then parses the symbol table in the dynamic library according to the ELF standard, then traverses the symbol table, and replaces the module 1012 with the functions provided by the bionic library (such as pthread, localtime, etc.) Replace with the functions provided by the glibc library, so that the running environment can be switched to the glibc environment for the Bluetooth service to use, and finally the function interface function symbols related to the hardware abstraction layer are imported into the Bluetooth service for the command issuing module to call.
  • the bionic library such as pthread, localtime, etc.
  • the communication module 102 is used to communicate with the Bluetooth application, the command issuing module, and the message monitoring module.
  • the communication module 102 receives a message from a Bluetooth application, processes the message from the Bluetooth application, and sends it to the command issuing module 103.
  • the communication module 102 can also receive a message from the message monitoring module 104, and process the message from the message monitoring module 104 and send it to a Bluetooth application.
  • the function of the Bluetooth application can be one or more, including listening to music, transferring files, scanning the bike, etc., which are not limited here.
  • the command issuing module 103 is configured to generate an operation command according to the message from the communication module, and send the operation command to the Bluetooth hardware through a functional interface that can be called by the converted glibc environment.
  • the command issuing module 103 includes a creation module 1031, an operation command generation module 1032, and an operation command sending module 1033.
  • the creation module 1031 is used to create a message processing strategy
  • the operation command generation module 1032 is used to use the message processing strategy to generate an operation command corresponding to the message from the communication module 102
  • the operation command sending module 1033 is used to call through the converted glibc environment
  • the functional interface sends operation commands to the Bluetooth hardware.
  • the command issuing module 103 adopts a message-driven model to operate, and establishes an independent thread operating environment during initialization. Then establish a message processing function table, that is, a message processing strategy. Each item in the table is a sequence pair, the first element is the message type, and the second element is the specific logic code, such as ⁇ SCAN, start_inquiry>.
  • the command issuing module 103 can look up the logic code corresponding to the message in the message processing function table according to the type of the message, that is, the processing function.
  • the command issuing process is an asynchronous process.
  • the command issuing module 103 processes the next message immediately after sending the received message, and does not pay attention to the execution result of the sent message.
  • the message monitoring module 104 is configured to monitor messages from the Bluetooth hardware through a functional interface that can be called by the converted glibc environment, and send the processed messages from the Bluetooth hardware to the communication module.
  • the message monitoring module 104 adopts a message-driven model to operate, and initializes an independent thread running environment.
  • the communication module 102 registers the underlying event processing functions with the message monitoring module at startup, including enabling failure and enabling success, pairing success and pairing failure, connection success and connection failure, etc., which are not limited here.
  • a message from the hardware abstraction layer is received, it is distributed to the corresponding registration callback function for processing according to the message type.
  • the received message from the hardware abstraction layer includes the execution result of the last issued command, the remote device requesting pairing, the remote device requesting connection and other messages, which are not limited here.
  • the message from the hardware abstraction layer is parsed, it is distributed to the communication module 102 for processing according to different business scenarios.
  • modules involved in this embodiment are all logical modules.
  • a logical unit can be a physical unit, a part of a physical unit, or multiple physical units. The combination of units is realized.
  • this embodiment does not introduce units that are not closely related to solving the technical problems proposed by this application, but this does not mean that there are no other units in this embodiment.
  • the Bluetooth service framework communicates with the Bluetooth application, and can use the functional interface converter 101 to interact with the Bluetooth hardware, complete the message loop, and realize the control of Bluetooth in the glibc environment of the Linux operating system, so that the Bluetooth manufacturers can also use the Bluetooth function in the Linux operating system under the condition that the Bluetooth manufacturer only provides the Android driver without repeated development. At the same time, it is compatible with the upper-level Bluetooth applications.
  • the existing applications can work normally without any modification.
  • the second embodiment of the present application relates to a device for controlling Android Bluetooth in a glibc environment.
  • the communication module 102 in the first embodiment includes a message processing module 201 and a protocol management module 202. Therefore, the Bluetooth service framework in this embodiment includes a function interface converter 101, a message processing module 201, a protocol management module 202, a command issuing module 103, and a message monitoring module 104.
  • the implementation details of the device for controlling Android Bluetooth in the glibc environment in this embodiment will be described in detail below. The following content is only provided for ease of understanding and is not necessary for implementing this solution.
  • the specific structure is shown in Figure 4, including:
  • the functional interface converter 101 is similar to the first embodiment, and will not be repeated here.
  • the message processing module 201 is used to process messages from the Bluetooth application and send to the protocol management module 202, and process messages from the protocol management module 202 and send to the Bluetooth application.
  • the protocol management module 202 communicates with the command issuing module and the message monitoring module 104 according to a preset protocol.
  • the message processing module 201 may also be referred to as an application communication module.
  • the message processing module 201 is used to communicate with a Bluetooth application, and analyze the service type according to the message from the Bluetooth application.
  • the service type includes enabling Bluetooth, scanning, pairing with remote devices, etc., which are not limited here. .
  • the message processing module 201 sends the parsed service type to the protocol management module 202.
  • the message processing module 201 is also used to parse the execution result of the service type according to the message from the protocol management module 202, and send the execution result to the Bluetooth application in the form of a message for processing.
  • the execution result includes enable success, failure, and scan result.
  • the list of devices, the Bluetooth protocol supported by the remote device, etc. are not limited here.
  • the message processing module 201 includes: a first analysis module 2011, a second analysis module 2012, a service type sending module 2013, and an execution result sending module 2014.
  • the protocol management module 202 includes: a first conversion module 2021, a first sending module 2022, a second conversion module 2023, and a second sending module 2024.
  • the first parsing module 2011 is used to parse out the service type according to the message from the Bluetooth application.
  • the service type includes pairing, connection, etc., which are not limited here.
  • the service type sending module 2013 is used to send the service type to the first conversion module 2021; the first conversion module 2021 is used to convert the service type to generate a first message instruction; the first sending module 2022 is used to send the first message instruction to The command issuing module 103; the second conversion module 2023 is used to convert the message from the message monitoring module 104 to generate a second message instruction; the second sending module 2024 is used to send the second message instruction to the message processing module 201;
  • the second parsing module 2012 is used to analyze the execution result of the service type according to the second message instruction; the execution result sending module 2014 is used to send the execution result of the service type to the Bluetooth application.
  • the first conversion module 2021 includes: a first registration module and a first generation module, the preset protocol includes a first callback function; the first registration module is used to register the first callback function; the first generation module is used to use The first callback function converts the service type to generate the first message instruction.
  • the second conversion module 2023 includes: a second registration module and a second generation module, the preset protocol also includes a second callback function; the second registration module is used to register the second callback function; the second generation module is used to use the second callback function The function converts the message from the message monitoring module 104 to generate a second message instruction.
  • the protocol management module 202 in the Bluetooth service adopts a message-driven model to establish an independent thread operating environment during initialization, and is responsible for the specific business logic in the Bluetooth application scenario, including protocol initialization, remote device matching, Connection and disconnection are not limited here.
  • the protocol management module 202 exchanges information with the message processing module 201, the command issuing module 103, and the message monitoring module 104 in the form of messages.
  • the protocol management module 202 receives application request information, processes it through the registered first callback function, and converts it into a command message that can be issued. At the same time, the information of the message monitoring module 104 is also received, processed through the registered second callback function, and converted into a message sent to the message processing module 201.
  • the message processing module 201 implements an inter-process communication (Inter-Process Communication, referred to as IPC) server, that is, implements some technologies or methods for transmitting data or signals between at least two processes or threads.
  • IPC Inter-Process Communication
  • the method adopted in this application Including the desktop bus protocol (Desktopbus, D-Bus for short), which is not limited here.
  • the command issuing module 103 is similar to the first embodiment and will not be repeated here.
  • the message monitoring module 104 is similar to the first embodiment, and will not be repeated here.
  • the message processing module 201 in the Bluetooth service framework communicates with the Bluetooth application, the protocol management module 202 completes message processing and sending according to a preset protocol, and the Bluetooth service framework can use the function interface converter 101 and the Bluetooth hardware Information interaction is completed, the message loop is completed, and Android Bluetooth is controlled in the glibc environment of the Linux operating system.
  • the Bluetooth function can also be used in the Linux operating system without repeated development. At the same time, it is compatible with the upper Bluetooth application.
  • the existing application can work normally without any modification. .
  • the third embodiment of the present application relates to a method for controlling Android Bluetooth in a glibc environment, which is applied to a terminal device.
  • a terminal device Such as: mobile phones, computers, etc., which are not limited here.
  • the functional interface converter 101 converts the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment, and then the communication module 102 in the Bluetooth service framework interacts with the Bluetooth application to interact with the command
  • the sending module 103 and the message monitoring module 104 exchange information with the Bluetooth hardware, and finally form a message loop between the Bluetooth service framework and the Bluetooth application and the Bluetooth hardware, which can realize the control of the Android Bluetooth in the glibc environment.
  • the implementation details of the method for controlling Android Bluetooth in the glibc environment of this embodiment will be specifically described below. The following content is provided for ease of understanding and is not necessary for implementing this solution.
  • the specific flow chart is shown in Figure 7, including:
  • Step 301 The functional interface converter 101 converts the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment.
  • the functional interface converter 101 includes a loading module 1011 and a replacement module 1012.
  • the loading module 1011 loads the shared library of the bionic environment in the glibc environment
  • the replacement module 1012 replaces the interface function provided by the shared library of the bionic environment with the interface function provided by the glibc environment, so that the running environment can be switched to glibc.
  • the functional interface function symbols related to the hardware abstraction layer are imported into the Bluetooth service for use by the command issuing module 103.
  • the working flow chart of the functional interface converter 101 is shown in Fig. 8, including:
  • Step 3011 Load the shared library of the bionic environment in the glibc environment.
  • Step 3012 Replace the interface function provided by the shared library of the bionic environment with the interface function provided by the glibc environment.
  • step 302 the communication module 102 receives and processes the message from the Bluetooth application.
  • the communication module 102 receives a message from a Bluetooth application, processes the message from the Bluetooth application, and sends it to the command issuing module 103.
  • the function of the Bluetooth application can be one or more, including listening to music, transferring files, scanning the bike, etc., which are not limited here.
  • step 303 the command issuing module 103 generates an operation command according to the message from the communication module 102, and sends the operation command to the Bluetooth hardware through a functional interface that can be called by the converted glibc environment.
  • the command issuing module 103 first creates a message processing strategy, and then uses the message processing strategy to generate an operation command corresponding to the message from the message processing module 201, and finally uses the function interface that can be called by the converted glibc environment The operation command is issued to the Bluetooth hardware.
  • the working flow chart of the command issuing module 103 is shown in Fig. 9 and includes:
  • Step 3031 create a message processing strategy
  • Step 3032 Use the message processing strategy to generate an operation command corresponding to the message from the message processing module 201;
  • Step 3033 Send the operation command to the Bluetooth hardware through a functional interface that can be called by the converted glibc environment.
  • the message monitoring module 104 adopts a message-driven model to operate, initializes and establishes an independent thread operating environment, and the communication module 102 registers the underlying event processing functions with the message monitoring module 104 at startup, including enable failure and enable success , Pairing success and pairing failure, connection success and connection failure, etc., are not limited here.
  • the message monitoring module 104 receives a message from the Bluetooth hardware abstraction layer, it is distributed to the corresponding registration callback function for processing according to the message type.
  • the received message from the hardware abstraction layer includes the execution result of the last issued command. ,
  • the remote device requests pairing, the remote device requests connection and other messages, which are not limited here.
  • the working flow chart of the message monitoring module 104 is shown in FIG. 10, including:
  • Step 3041 Receive a message from the Bluetooth hardware abstraction layer.
  • Step 3042 Process the message from the Bluetooth hardware abstraction layer and send it to the communication module 102.
  • step 305 the communication module 102 processes the message from the message monitoring module 104 and sends it to the Bluetooth application.
  • Step 401 Initialize the functional interface.
  • the functional interface converter 101 converts the functional interface in the Android Bluetooth service in the bionic environment into a functional interface that can be called by the glibc environment, that is, loads the Android Bluetooth library into the glibc environment through the functional interface converter.
  • the functional interface converter 101 here may also be referred to as an Android shared library loader.
  • step 402 the command issuing module 103 and the message monitoring module 104 are initialized.
  • a message loop from the command issuing module 103 to the message listening module 104 is established.
  • This message loop can realize the process from the command issuing module 103 to the Bluetooth hardware. Message delivery to the message monitoring module 104.
  • step 403 the initialized functional interface is called through the command issuing module 103, and an instruction is sent to the Bluetooth chip.
  • step 404 the message monitoring module 104 receives the feedback message from the Bluetooth chip.
  • Step 405 Initialize the communication module 102.
  • an event loop of the communication module 102 is established, that is, information interaction between the communication module 102 and the Bluetooth application, and the command issuing module 103 and the message monitoring module 104 can be realized.
  • the functional interface converter 101 converts the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment, and then the communication module 102 receives and processes the information from the Bluetooth application, and then the command issuance module 103
  • the operation command is generated according to the message from the communication module 102, and the operation command is sent to the Bluetooth hardware through the functional interface that can be called by the converted glibc environment, so as to realize the message delivery from the Bluetooth application to the Bluetooth hardware.
  • the message monitoring module 104 listens to the message from the Bluetooth hardware, processes the message from the Bluetooth hardware and sends it to the communication module 102, and then the communication module 102 processes the message from the message monitoring module 104 and sends it to the Bluetooth application.
  • Bluetooth service framework and Bluetooth hardware are used for message interaction, and the various modules cooperate with each other to realize the control of Bluetooth in the glibc environment of the Linux operating system, so that under the condition that Bluetooth manufacturers only provide Android drivers,
  • the Bluetooth function can also be used in the Linux operating system without repeated development. At the same time, it is compatible with upper-layer Bluetooth applications.
  • the existing applications can work normally without any modification.
  • the fourth embodiment of the present application relates to a method for controlling Android Bluetooth in a glibc environment, which is applied to a terminal device.
  • a terminal device Such as: mobile phones, computers, etc., which are not limited here.
  • the Bluetooth service framework includes a message processing module 201, a protocol management module 202, a command issuing module 103, and a message monitoring module 104.
  • the functional interface converter 101 converts the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment.
  • the Bluetooth service framework performs message interaction with Bluetooth applications and Bluetooth hardware, and can control Android Bluetooth in the glibc environment. The specific process is shown in Figure 12, including:
  • step 501 the functional interface converter 101 converts the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment. It is similar to step 301 and will not be repeated here.
  • step 502 the message processing module 201 processes the message from the Bluetooth application and sends it to the protocol management module 202.
  • Fig. 13 the working flow chart of the message processing module 201 when sending a Bluetooth application message is shown in Fig. 13, including:
  • Step 5021 Receive and process a message from a Bluetooth application
  • Step 5022 Send the processed message from the Bluetooth application to the protocol management module 202.
  • the message processing module 201 parses out the service type according to the message from the Bluetooth application.
  • the service type includes pairing, connection, etc., which are not limited here. Then the message processing module 201 sends the parsed service type to the protocol management module 202.
  • Step 503 The protocol management module 202 processes the message from the message processing module 201 according to a preset protocol, and sends it to the command issuing module 103.
  • Fig. 14 the working flow chart of the protocol management module 202 when the message processing module 201 sends a message is shown in Fig. 14, including:
  • Step 5031 Process the message from the message processing module 201 according to a preset protocol
  • Step 5032 Send the processed message from the message processing module 201 to the command issuing module 103.
  • the protocol management module 202 parses out the service type according to the message from the Bluetooth application, then converts the service type according to the preset protocol to generate the first message instruction, and then sends the first message instruction to the command issuance Module 103.
  • the protocol management module 202 registers the first callback function, uses the first callback function to convert the service type to generate the first message instruction, and then sends the first message instruction to the command issuing module 103.
  • step 504 the command issuing module 103 generates an operation command according to the message from the message processing module 201, and sends the operation command to the Bluetooth hardware through a functional interface that can be called by the converted glibc environment. It is similar to step 303 and will not be repeated here.
  • step 505 the message monitoring module 104 monitors the message from the Bluetooth hardware, processes the message from the Bluetooth hardware, and sends it to the protocol management module 202.
  • Step 506 The protocol management module 202 processes the message from the message monitoring module 104 according to the preset protocol, and sends it to the message processing module 104.
  • the workflow when the protocol management module 202 uploads the message of the message monitoring module 104 is shown in FIG. 15 and includes:
  • Step 5061 Process the message from the message monitoring module 104 according to a preset protocol
  • Step 5062 Send the processed message from the message monitoring module 104 to the message processing module 201.
  • the protocol management module 202 converts the message from the message monitoring module 104 according to a preset protocol to generate a second message instruction, analyzes the execution result of the service type according to the second message instruction, and sends it to the message processing module 201.
  • the protocol management module 202 registers the second callback function, and uses the second callback function to convert the message from the message monitoring module 104 to generate a second message instruction, and then sends the second message execution to the message processing module 201.
  • Step 507 The message processing module 201 processes the message from the protocol management module 202 and sends it to the Bluetooth application.
  • the flowchart when the message processing module 201 uploads a message from the protocol management module 202 is shown in FIG. 16, and includes:
  • Step 5071 Receive and process the message from the protocol management module 202;
  • Step 5072 Send the processed message from the protocol management module 202 to the Bluetooth application.
  • the Bluetooth service framework performs message interaction with Bluetooth applications and Bluetooth hardware
  • the functional interface converter 101 can convert the functional interface of Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment.
  • the Bluetooth service framework and the function interface converter 101 cooperate with each other to realize the control of Bluetooth in the glibc environment of the Linux operating system, so that the Bluetooth function can also be used in the Linux operating system under the condition that the Bluetooth manufacturer only provides the Android driver. Repetitive development is required and compatible with upper-level Bluetooth applications. Existing applications can work normally without any modification.
  • the fifth embodiment of the present application relates to a terminal device, including: a device that controls Android Bluetooth in a glibc environment, a Bluetooth application, and Bluetooth hardware; a Bluetooth application that controls the operation of Bluetooth hardware through a device that controls Android Bluetooth in a glibc environment, and Receive the information from the Bluetooth hardware through the device that controls the Android Bluetooth in the glibc environment; the Bluetooth hardware receives and executes the operation commands from the device that controls the Android Bluetooth in the glibc environment, and connects the Bluetooth through the device that controls the Android Bluetooth in the glibc environment The hardware information is returned to the Bluetooth application.
  • FIG. 17 is a schematic diagram of a specific implementation of a mobile terminal in this embodiment. As shown in Figure 17:
  • the terminal device has a processor 601, including a computing unit, a modem, etc., which is not limited herein.
  • the processor 601 is responsible for managing the bus and general processing, and can also provide various functions, including calculation, timing, peripheral interfaces, voltage regulation, power management, modulation and demodulation, and other control functions.
  • the processor 601 has an associated memory 602, which includes but is not limited to RAM memory, ROM memory, EEPROM memory, flash memory, or a combination thereof. Can be used to store data used by the processor when performing operations.
  • the memory 602 and the processor 601 are connected in a bus manner.
  • the bus may include any number of interconnected buses and bridges.
  • the bus connects one or more various circuits of the processor 601 and the memory 602 together.
  • the bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein.
  • the bus interface provides an interface between the bus and the transceiver.
  • the transceiver may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on the transmission medium.
  • the data processed by the processor 601 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 601.
  • the terminal device also has a display 603, which can be used to display the collected data, which is not limited here.
  • the terminal device also has an input unit 604 for the user to input operation instructions or select corresponding functions, which is not limited here.
  • the terminal device also has an operating system 605, a communication interface 606, a human-computer interaction interface 607, and an application program 608.
  • the operating system 605 is used to handle basic tasks such as managing and configuring memory, determining the priority of supply and demand of system resources, controlling input devices and output devices, operating networks, and managing file systems.
  • the operating system also provides an operation interface that allows users to interact with the system.
  • the device for controlling Android Bluetooth in the glibc environment in this embodiment may be located in the operating system 605.
  • the communication interface 606 includes, but is not limited to, various modules, protocol stacks, drivers, and other logic related to communication.
  • the communication interface 606 can be used to provide communication services such as transmission, network, and connectivity for a radio frequency interface, a Bluetooth interface, and an infrared interface, so as to implement communication between terminals.
  • the radio frequency interface includes but is not limited to a wifi interface.
  • the radio frequency interface includes the internal fire-box antenna and the appropriate circuit for establishing and maintaining the wireless link to the base station.
  • the human-computer interaction interface 907 includes but is not limited to a keyboard interface, a mouse interface, a stylus interface, etc., which are not limited herein.
  • the application program 908 includes but is not limited to a dial-up service application, a call service application, a short message service application, etc., which are not limited here.
  • the Android Bluetooth hardware abstraction layer does not involve the encapsulation of the Android Bluetooth hardware abstraction layer, but only converts the Android Bluetooth service function interface above the hardware abstraction layer, and controls the Android Bluetooth device and the Bluetooth application and the Bluetooth hardware in the glibc environment.
  • Conduct information exchange The functional interface converter in the device that controls the Android Bluetooth in the glibc environment converts the functional interface of the Android Bluetooth in the bionic environment into a functional interface that can be called by the glibc environment.
  • the communication module in the Bluetooth service framework performs information interaction with the Bluetooth application.
  • the command issuing module sends the message to the hardware abstraction layer through the functional interface that can be called by the converted glibc environment, and the message monitoring module receives the message from the hardware abstraction layer to complete the message interaction between the Bluetooth service framework and the Bluetooth hardware.
  • the terminal device in this embodiment can realize the use of the Bluetooth function in the Linux operating system under the condition that the Bluetooth manufacturer only provides the Android driver.
  • Linux application developers do not need to care about the underlying details when using the Bluetooth function, they can directly use the API provided by the Bluetooth service framework.
  • the fourth embodiment of the present application relates to a computer-readable storage medium storing a computer program.
  • the computer program is executed by the processor, the above method embodiment is realized.
  • the program is stored in a storage medium and includes several instructions to make a device (It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) executes all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .
  • the implementation of this application realizes the control of Android Bluetooth under the glibc environment and is compatible with all Linux applications.
  • the Android Bluetooth hardware can also be controlled in the Linux operating system to realize the Bluetooth function, without the need for the manufacturer to specifically develop matching Bluetooth hardware for the Linux operating system.
  • Linux application developers do not need to care about the underlying details when using Bluetooth applications, and can directly use the Application Programming Interface (API for short) provided in the device.
  • API Application Programming Interface

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

一种在glibc环境下控制安卓蓝牙的装置，涉及智能设备领域。该装置包括：功能接口转换器（101），用于将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口；通信模块（102），用于与蓝牙应用、命令下发模块（103）和消息监听模块（104）进行通信；命令下发模块（103），用于根据来自通信模块（102）的消息生成操作命令，并通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件；消息监听模块（104），用于监听来自蓝牙硬件的消息，并将处理后的来自蓝牙硬件的消息发送给通信模块（102）。

Description

在glibc环境下控制安卓蓝牙的装置、方法及终端设备 技术领域
本申请实施例涉及智能设备领域，特别涉及一种在glibc环境下控制安卓蓝牙的装置、方法及终端设备。
背景技术
仿生C库(Bionic)是安卓操作系统(Android)基础的C/C++库，GNU C库(Gnulibc，简称glibc)是Linux操作系统的标准C库，二者的实现上有着许多的不同，所以在编译时通过Boinic库链接的程序无法直接在glibc环境中加载运行。
发明人发现在一些情形下至少存在以下问题：安卓环境中的一些硬件相关的驱动库通常由硬件厂商提供，要想实现在glibc环境中控制安卓蓝牙，就需要厂商针对Linux操作系统专门开发匹配的蓝牙硬件，这样无疑会增加成本。
发明内容
本申请实施方式的目的在于提供一种在glibc环境下控制安卓蓝牙的装置、方法、终端设备以及计算机可读存储介质。
本申请的实施方式提供了一种在glibc环境下控制安卓蓝牙的装置，包括：功能接口转换器、应用消息处理模块、命令下发模块和消息监听模块；功能接口转换器，用于将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口；通信模块，用于与蓝牙应用、命令下发模块和消息监听模块进行通信；命令下发模块，用于根据来自通信模块的消息生成操作命令，并通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件；消息监听模块，用于监听来自蓝牙硬件的消息，并将处理后的来自蓝牙硬件的消息发送给通信模块。
本申请的实施方式还提供了一种在glibc环境下控制安卓蓝牙的方法，包括：功能接口转换器将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口；通信模块接收并处理来自蓝牙应用的信息；命令下发模块根据来自通信模块的消息生成操作命令，并通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件；消息监听模块监听来自蓝牙硬件的消息，将来自蓝牙硬件的消息进行处理并发送给通信模块；通信模块将来自消息监 听模块的消息进行处理并发送给蓝牙应用。
本申请的实施方式还提供了一种终端设备，包括上述在glibc环境下控制安卓蓝牙的装置、蓝牙应用和蓝牙硬件；蓝牙应用，通过在glibc环境下控制安卓蓝牙的装置控制蓝牙硬件的操作，并通过在glibc环境下控制安卓蓝牙的装置接收来自蓝牙硬件的信息；蓝牙硬件，接收并执行来自在glibc环境下控制安卓蓝牙的装置的操作命令，并通过在glibc环境下控制安卓蓝牙的装置将蓝牙硬件的信息返回给蓝牙应用。
本申请的实施方式还提供了一种计算机可读存储介质，存储有计算机程序，其中，计算机程序被处理器执行时实现上述在glibc环境下控制安卓蓝牙的方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1是本申请第一实施方式中在glibc环境下控制安卓蓝牙的装置示意图；
图2是本申请第一实施方式中功能接口转换器的结构示意图；
图3是本申请第一实施方式中命令下发模块的结构示意图；
图4是本申请第二实施方式中在glibc环境下控制安卓蓝牙的装置示意图；
图5是本申请第二实施方式中消息处理模块的结构示意图；
图6是本申请第二实施方式中协议管理模块的结构示意图；
图7是本申请第三实施方式中在glibc环境下控制安卓蓝牙的方法流程图；
图8是本申请第三实施方式中功能接口转换器的工作流程图；
图9是本申请第三实施方式中命令下发模块的工作流程图；
图10是本申请第三实施方式中消息监听模块的工作流程图；
图11是本申请第三实施方式中蓝牙服务框架初始化流程图；
图12是本申请第四实施方式中在glibc环境下控制安卓蓝牙的方法流程图；
图13是本申请第四实施方式中消息处理模块下发蓝牙应用消息时的工作流程图；
图14是本申请第四实施方式中协议管理模块下发消息处理模块消息时的工作流程图；
图15是本申请第四实施方式中协议管理模块上传消息监听模块消息时的工作流程图；
图16是本申请第四实施方式中消息处理模块上传协议管理模块消息时的流程图；
图17是本申请第五实施方式中移动终端的具体实现示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施方式进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施方式中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
安卓的快速发展同时也带动了蓝牙芯片厂家对硬件抽象层接口进行了适配，使得蓝牙的接口统一且稳定，这也为Linux系统下更方便的使用蓝牙技术提供了契机，使得蓝牙功能更加易用和稳定。为了实现在glibc环境下控制安卓蓝牙，发明人提供了以下几种实施方式。
本申请的第一实施方式涉及一种在glibc环境下控制安卓蓝牙的装置。下面对本实施方式的在glibc环境下控制安卓蓝牙的装置的实现细节进行具体说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。该装置涉及一套蓝牙服务框架，该蓝牙服务框架包括功能接口转换器101、通信模块102、命令下发模块103和消息监听模块104。其中，功能接口转换器101包括加载模块1011、替换模块1012。其中，命令下发模块103包括创建模块1031、操作命令生成模块1032和操作命令发送模块1033。蓝牙服务框架中的模块以及功能接口转换器(安卓共享库加载器)位于glibc环境，安卓蓝牙库位于bionic环境中。具体结构如图1所示，包括：
功能接口转换器101，用于将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口。
具体地说，功能接口转换器101也可称为安卓共享库加载器。如图2所示，功能接口转换器101包括：加载模块1011、替换模块1012。加载模块1011用于在glibc环境加载bionic环境的共享库；替换模块1012用于将bionic环境的共享库提供的接口函数替换为glibc环境提供的接口函数。
在一个具体的例子中，功能接口转换器101支持ARM、MIPS等平台，在此不做限定。安卓蓝牙驱动的硬件抽象层是以可执行与可链接格式(Executableand Linkable Format，简称ELF)的动态链接库形式存在的。安卓共享库(安卓蓝牙库)提供基本的蓝牙芯片操作接口，包括蓝牙模块使能、蓝牙模块关闭、蓝牙模块初始化等基础接口，在此不做限定。加载模块1011首先在glibc环境加Android共享库文件，然后依照ELF标准解析出动态库中的符号表， 接着遍历符号表，替换模块1012将其中由bionic库所提供的函数(比如pthread、localtime等)替换为glibc库提供的函数，这样便可以将运行环境切换到glibc环境中供蓝牙服务使用，最后将硬件抽象层相关的功能接口函数符号导入到蓝牙服务中供命令下发模块调用。
通信模块102，用于与蓝牙应用、命令下发模块和消息监听模块进行通信。
在一个具体的例子中，通信模块102接收来自蓝牙应用的消息，并将来自蓝牙应用的消息进行处理后发送给命令下发模块103。通信模块102还能够接收来自消息监听模块104的消息，并将来自消息监听模块104的消息进行处理后发送给蓝牙应用。其中，蓝牙应用的功能可以是一种或是多种，包括听音乐、传文件、扫码单车等，在此不做限定。
命令下发模块103，用于根据来自通信模块的消息生成操作命令，并通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件。
具体地说，如图3所示，命令下发模块103包括创建模块1031、操作命令生成模块1032和操作命令发送模块1033。创建模块1031用于创建消息处理策略，操作命令生成模块1032用于利用消息处理策略生成与来自通信模块102的消息对应的操作命令，操作命令发送模块1033用于通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件。
在一个具体的例子中，命令下发模块103采用消息驱动模型运作，初始化时建立独立的线程运行环境。然后建立消息的处理函数表，即消息处理策略，该表中的每一项为一个序列对，第一个元素为消息类型，第二个元素为具体的逻辑代码，比如<SCAN,start_inquiry>。当通信模块102将消息发送给命令下发模块103后，命令下发模块103可以根据该消息的类型在消息处理函数表中查找该消息对应的逻辑代码，即处理函数。接着调用转换后的glibc环境能调用的功能接口，并将消息发送给硬件抽象层，然后再将发送给硬件抽象层的消息进行处理后发送给蓝牙驱动。命令下发的过程为异步过程，命令下发模块103在下发完接收到的消息之后立即处理下一个消息，而且不关注发送出的消息的执行结果。
消息监听模块104，用于通过转换后的glibc环境能调用的功能接口监听来自蓝牙硬件的消息，并将处理后的来自蓝牙硬件的消息发送给通信模块。
在一个具体的例子中，消息监听模块104采用消息驱动模型运作，初始化建立独立的线程运行环境。通信模块102在启动时向消息监听模块注册底层事件处理函数，包括使能失败和使能成功，配对成功和配对失败，连接成功和连接失败等，在此不做限定。当接收到来自硬件抽象层的消息后，根据消息类型分发到对应的注册回调函数中进行处理。其中，接收到的来自硬件抽象层的消息包括上一次下发命令的执行结果、远端设备请求配对、远端设备请求连接等消息，在此不做限定。对来自硬件抽象层的消息进行解析后，根据不同的业务场景分发给通信模块102进行处理。
值得一提的是，本实施方式中所涉及到的各模块均为逻辑模块，在实际应用中，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现。此外，为了突出本申请的创新部分，本实施方式中并没有将与解决本申请所提出的技术问题关系不太密切的单元引入，但这并不表明本实施方式中不存在其它的单元。
在本实施方式中，蓝牙服务框架和蓝牙应用进行通信，且能够借助功能接口转换器101和蓝牙硬件进行信息交互，完成了消息循环，实现了在Linux操作系统的glibc环境中控制蓝牙，使得在蓝牙厂商只提供安卓驱动的条件下，也可以在Linux操作系统中使用蓝牙功能，而不需要进行重复开发，同时兼容上层的蓝牙应用，现有的应用不做任何修改即可正常工作。
本申请的第二实施方式涉及一种在glibc环境下控制安卓蓝牙的装置。本实施方式与第一实施方式的区别是：第一实施方式中的通信模块102包括消息处理模块201、协议管理模块202。所以本实施方式中的蓝牙服务框架包括功能接口转换器101、消息处理模块201、协议管理模块202、命令下发模块103和消息监听模块104。下面对本实施方式中的在glibc环境下控制安卓蓝牙的装置的实现细节进行具体说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。具体结构如图4所示，包括：
功能接口转换器101，与第一实施方式类似，在此不再赘述。
消息处理模块201，用于将来自蓝牙应用的消息进行处理，并发送给协议管理模块202，以及将来自协议管理模块202的消息进行处理，并发送给蓝牙应用。
协议管理模块202，根据预设的协议与命令下发模块和消息监听模块104进行通信。
需要说明的是，消息处理模块201也可称为应用通信模块。在一个具体的例子中，消息处理模块201用于和蓝牙应用进行通信，根据来自蓝牙应用的消息解析出业务类型，业务类型包括使能蓝牙、扫描、配对远端设备等，在此不做限定。然后消息处理模块201将解析出的业务类型发送给协议管理模块202。消息处理模块201还用于根据来自协议管理模块202的消息解析出业务类型的执行结果，并将执行结果同样以消息的形式发送到蓝牙应用中处理，执行结果包括使能成功、失败、扫描到的设备列表、远端设备所支持的蓝牙协议等，在此不做限定。
具体地说，如图5所示，消息处理模块201包括：第一解析模块2011、第二解析模块2012、业务类型发送模块2013和执行结果发送模块2014。如图6所示，协议管理模块202包括：第一转换模块2021、第一发送模块2022、第二转换模块2023、第二发送模块2024。第一解析模块2011用于根据来自蓝牙应用的消息解析出业务类型，业务类型包括配对、连接等，在此不做限定。业务类型发送模块2013用于将业务类型发送给第一转换模块2021；第一转换模块2021用于将业务类型进行转换生成第一消息指令；第一发送模块2022用于将第一消息 指令发送给命令下发模块103；第二转换模块2023用于将来自消息监听模块104的消息进行转换，生成第二消息指令；第二发送模块2024用于将第二消息指令发送给消息处理模块201；第二解析模块2012用于根据第二消息指令解析出业务类型的执行结果；执行结果发送模块2014用于将业务类型的执行结果发送给蓝牙应用。
具体地说，第一转换模块2021包括：第一注册模块和第一生成模块，预设的协议包括第一回调函数；第一注册模块用于注册第一回调函数；第一生成模块用于利用第一回调函数将业务类型进行转换生成第一消息指令。第二转换模块2023包括：第二注册模块和第二生成模块，预设的协议还包括第二回调函数；第二注册模块用于注册第二回调函数；第二生成模块用于利用第二回调函数将来自消息监听模块104的消息进行转换，生成第二消息指令。
在一个具体的例子中，蓝牙服务中的协议管理模块202采用消息驱动模型，初始化时建立独立的线程运行环境，负责蓝牙应用场景中的具体业务逻辑，包括协议的初始化、远端设备的匹配、连接和断开等，在此不做限定。协议管理模块202通过消息的形式与消息处理模块201、命令下发模块103、消息监听模块104进行信息交互。协议管理模块202接收应用请求信息，通过注册的第一回调函数进行处理，转换为可下发的命令消息。同时也接收消息监听模块104的信息，通过注册的第二回调函数进行处理并转换为发送给消息处理模块201的消息。消息处理模块201实现了一个进程间通信(Inter-Process Communication，简称IPC)的服务端，即实现了至少两个进程或线程间传送数据或信号的一些技术或方法，在本申请中采用的方式包括桌面总线协议(Desktopbus，简称D-Bus)，在此不做限定。
命令下发模块103，与第一实施方式类似，在此不再赘述。
消息监听模块104，与第一实施方式类似，在此不再赘述。
本实施方式中，蓝牙服务框架中的消息处理模块201与蓝牙应用进行通信，协议管理模块202根据预设的协议完成消息的处理和发送，且蓝牙服务框架能够借助功能接口转换器101和蓝牙硬件进行信息交互，完成了消息循环，实现了在Linux操作系统的glibc环境中控制安卓蓝牙。使得在蓝牙厂商只提供安卓驱动的条件下，也可以在Linux操作系统中使用蓝牙功能，而不需要进行重复开发，同时兼容上层的蓝牙应用，现有的应用程序不做任何修改即可正常工作。
本申请的第三实施方式涉及一种在glibc环境下控制安卓蓝牙的方法，应用于终端设备。如：手机、电脑等，在此不做限定。在第三实施方式中，功能接口转换器101将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口，然后蓝牙服务框架中的通信模块102和蓝牙应用进行信息交互，与命令下发模块103和消息监听模块104和蓝牙硬件之间进行信息交互，最后形成蓝牙服务框架和蓝牙应用以及蓝牙硬件之间的消息循环，能够实现在 glibc环境下控制安卓蓝牙。下面对本实施方式的在glibc环境下控制安卓蓝牙的方法的实现细节进行具体的说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。具体流程图如图7所示，包括：
步骤301，功能接口转换器101将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口。
在一个具体的例子中，功能接口转换器101包括加载模块1011和替换模块1012。首先，加载模块1011在glibc环境中加载bionic环境的共享库，然后替换模块1012将bionic环境的共享库提供的接口函数替换为glibc环境提供的接口函数，这样就可以将运行环境切换到glibc中。最后将硬件抽象层相关的功能接口函数符号导入到蓝牙服务中供命令下发模块103使用。功能接口转换器101的工作流程图如图8所示，包括：
步骤3011，在glibc环境中加载bionic环境的共享库。
步骤3012，将bionic环境的共享库提供的接口函数替换为glibc环境提供的接口函数。
步骤302，通信模块102接收并处理来自蓝牙应用的消息。
在一个具体的例子中，通信模块102接收来自蓝牙应用的消息，并将来自蓝牙应用的消息进行处理后发送给命令下发模块103。其中，蓝牙应用的功能可以是一种或是多种，包括听音乐、传文件、扫码单车等，在此不做限定。
步骤303，命令下发模块103根据来自通信模块102的消息生成操作命令，并通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件。
在一个具体的例子中，命令下发模块103首先创建消息处理策略，然后利用消息处理策略生成与来自消息处理模块201的消息对应的操作命令，最后通过转换后的glibc环境能调用的功能接口将操作命令下发给蓝牙硬件。命令下发模块103的工作流程图如图9所示，包括：
步骤3031，创建消息处理策略；
步骤3032，利用消息处理策略生成与来自消息处理模块201的消息对应的操作命令；
步骤3033，通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件。
步骤304，消息监听模块104监听来自蓝牙硬件的消息，将来自蓝牙硬件的消息进行处理并发送给通信模块102。
在一个具体的例子中，消息监听模块104采用消息驱动模型运作，初始化建立独立的线程运行环境，通信模块102在启动时向消息监听模块104注册底层事件处理函数，包括使能失败和使能成功，配对成功和配对失败，连接成功和连接失败等，在此不做限定。当消息监听模块104接收到来自蓝牙硬件抽象层的消息后，根据消息类型分发到对应的注册回调函数中进行处理，其中，接收到的来自硬件抽象层的消息包括上一次下发命令的执行结果、远端 设备请求配对、远端设备请求连接等消息，在此不做限定。对来自硬件抽象层的消息进行解析后，根据不同的业务场景分发给通信模块102进行处理。消息监听模块104的工作流程图如图10所示，包括：
步骤3041，接收来自蓝牙硬件抽象层的消息。
步骤3042，将来自蓝牙硬件抽象层的消息进行处理并发送给通信模块102。
步骤305，通信模块102将来自消息监听模块104的消息进行处理并发送给蓝牙应用。
需要说明的是，在进行步骤301-305之前，需要将蓝牙服务框架初始化，具体如图11所示，包括：
步骤401，初始化功能接口。
具体地说，功能接口转换器101将bionic环境下安卓蓝牙服务中的功能接口转换为glibc环境能调用的功能接口，即通过功能接口转换器将安卓蓝牙库装载到glibc环境中。这里的功能接口转换器101也可称为安卓共享库加载器。
步骤402，初始化命令下发模块103和消息监听模块104。
具体地说，在初始化命令下发模块103和消息监听模块104的过程中，建立命令下发模块103到消息监听模块104的消息循环，此消息循环可以实现从命令下发模块103到蓝牙硬件再到消息监听模块104的消息传送。
步骤403，通过命令下发模块103调用初始化后的功能接口，并向蓝牙芯片发送指令。
步骤404，消息监听模块104接收来自蓝牙芯片的反馈消息。
步骤405，初始化通信模块102。
具体地说，初始化通信模块102的过程中，建立通信模块102的事件循环，即能够实现通信模块102和蓝牙应用以及命令下发模块103和消息监听模块104之间的信息交互。
在本实施方式中，首先功能接口转换器101将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口，接着通信模块102接收并处理来自蓝牙应用的信息，然后命令下发模块103根据来自通信模块102的消息生成操作命令，并通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件，实现从蓝牙应用到蓝牙硬件的消息下发。相应的，消息监听模块104监听来自蓝牙硬件的消息，将来自蓝牙硬件的消息进行处理并发送给通信模块102，接着通信模块102将来自消息监听模块104的消息进行处理并发送给蓝牙应用，实现从蓝牙硬件到蓝牙应用的消息结果反馈。借助功能接口转换器101实现蓝牙服务框架和蓝牙硬件进行消息交互，各个模块之间相互配合，从而实现了在Linux操作系统的glibc环境中控制蓝牙，使得在蓝牙厂商只提供安卓驱动的条件下，也可以在Linux操作系统中使用蓝牙功能，而不需要进行重复开发，同时兼容上层蓝牙应用，现有的应用不做任何修改即可正 常工作。
不难发现，本实施方式可与第一实施方式互相配合实施。第一实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第一实施方式中。
本申请的第四实施方式涉及一种在glibc环境下控制安卓蓝牙的方法，应用于终端设备。如：手机、电脑等，在此不做限定。在本实施方式中，蓝牙服务框架中包括消息处理模块201、协议管理模块202、命令下发模块103和消息监听模块104。首先，功能接口转换器101将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口，蓝牙服务框架与蓝牙应用以及蓝牙硬件进行消息交互，能够实现在glibc环境下控制安卓蓝牙。具体流程如图12所示，包括：
步骤501，功能接口转换器101将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口。与步骤301类似，在此不再赘述。
步骤502，消息处理模块201将来自蓝牙应用的消息进行处理并发送给协议管理模块202。
在一个具体的例子中，消息处理模块201下发蓝牙应用消息时的工作流程图如图13所示，包括：
步骤5021，接收并处理来自蓝牙应用的消息；
步骤5022，将处理后的来自蓝牙应用的消息发送给协议管理模块202。
在一个具体的例子中，消息处理模块201根据来自蓝牙应用的消息解析出业务类型，业务类型包括配对、连接等，在此不做限定。然后消息处理模块201将解析出的业务类型发送给协议管理模块202。
步骤503，协议管理模块202根据预设的协议将来自消息处理模块201的消息进行处理，并发送给命令下发模块103。
在一个具体的例子中，协议管理模块202下发消息处理模块201消息时的工作流程图如图14所示，包括：
步骤5031，根据预设的协议将来自消息处理模块201的消息进行处理；
步骤5032，将处理后的来自消息处理模块201的消息发送给命令下发模块103。
在一个具体的例子中，协议管理模块202根据来自蓝牙应用的消息解析出业务类型，接着根据预设的协议将业务类型进行转换生成第一消息指令，然后将第一消息指令发送给命令下发模块103。
在一个具体的例子中，协议管理模块202注册第一回调函数，并利用第一回调函数将业务类型进行转换生成第一消息指令，然后将第一消息指令发送给命令下发模块103。
步骤504，命令下发模块103根据来自消息处理模块201的消息生成操作命令，并通过转换后的glibc环境能调用的功能接口将操作命令发送给蓝牙硬件。与步骤303类似，在此不再赘述。
步骤505，消息监听模块104监听来自蓝牙硬件的消息，将来自蓝牙硬件的消息进行处理并发送给协议管理模块202。
步骤506，协议管理模块202根据预设的协议将来自消息监听模块104的消息进行处理，并发送给消息处理模块104。
在一个具体的例子中，协议管理模块202上传消息监听模块104消息时的工作流程图如图15所示，包括：
步骤5061，根据预设的协议将来自消息监听模块104的消息进行处理；
步骤5062，将处理后的来自消息监听模块104的消息发送给消息处理模块201。
在一个具体的例子中，协议管理模块202根据预设的协议将来自消息监听模块104的消息进行转换生成第二消息指令，根据第二消息指令解析出业务类型的执行结果并发送给消息处理模块201。
在一个具体的例子中，协议管理模块202注册第二回调函数，并利用第二回调函数将来自消息监听模块104的消息进行转换生成第二消息指令，然后将第二消息执行发送给消息处理模块201。
步骤507，消息处理模块201将来自协议管理模块202的消息进行处理并发送给蓝牙应用。
在一个具体的例子中，消息处理模块201上传协议管理模块202消息时的流程图如图16所示，包括：
步骤5071，接收并处理来自协议管理模块202的消息；
步骤5072，将处理后的来自协议管理模块202的消息发送给蓝牙应用。
在本实施方式中，蓝牙服务框架和蓝牙应用以及蓝牙硬件进行消息交互，功能接口转换器101可以将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口。蓝牙服务框架和功能接口转换器101相互配合，实现了在Linux操作系统的glibc环境中控制蓝牙，使得在蓝牙厂商只提供安卓驱动的条件下，也可以在Linux操作系统中使用蓝牙功能，而不需要进行重复开发，同时兼容上层蓝牙应用，现有的应用不做任何修改即可正常工作。
不难发现，本实施方式可与第二实施方式互相配合实施。第二实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第二实施方式中。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请第五实施方式涉及一种终端设备，包括：在glibc环境下控制安卓蓝牙的装置、蓝牙应用和蓝牙硬件；蓝牙应用，通过在glibc环境下控制安卓蓝牙的装置控制蓝牙硬件的操作，并通过在glibc环境下控制安卓蓝牙的装置接收来自蓝牙硬件的信息；蓝牙硬件，接收并执行来自在glibc环境下控制安卓蓝牙的装置的操作命令，并通过在glibc环境下控制安卓蓝牙的装置将蓝牙硬件的信息返回给蓝牙应用。
图17为本实施方式移动终端的一种具体实现示意图。如图17所示：
该终端设备具有处理器601，包括计算单元、调制解调器等，在此不做限定。处理器601负责管理总线和通常的处理，还可以提供各种功能，包括计算、定时、外围接口、电压调节、电源管理、调制解调以及其他控制功能。处理器601具有关联的存储器602，该存储器602包括但不限于RAM存储器、ROM存储器、EEPROM存储器、闪存或其组合。可以被用于存储处理器在执行操作时所使用的数据。存储器602和处理器601采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器601和存储器602的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器601处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器601。
该终端设备还具有显示器603，可以用来显示采集到的数据，在此不做限定。
该终端设备还具有输入单元604，可以供用户输入操作指令或选择相应的功能，在此不做限定。
该终端设备还具有操作系统605、通信接口606、人机交互接口607、应用程序608。其中，操作系统605用来处理如管理与配置内存、决定系统资源供需的优先次序、控制输入设备与输出设备、操作网络与管理文件系统等基本事务。操作系统也提供一个让用户与系统交互的操作界面。本实施例中的在glibc环境下控制安卓蓝牙的装置可以位于操作系统605中。其中，通信接口606包括但不限于各种模块、协议栈、驱动器等与通信相关的逻辑。通信接口606可用于为无线射频接口、蓝牙接口、红外接口提供通信服务，例如传输、网络和联通性，以实现终端之间的通信。其中，无线射频接口包括但不限于wifi接口。无线射频接口包 括内部火娃不天线以及用于建立和维护通往基站的无线链路的适当的电路。其中，人机交互接口907包括但不限于键盘接口、鼠标接口和手写笔接口等，在此不做限定。其中，应用程序908包括但不限于拨号服务应用、呼叫服务应用、短信服务应用等，在此不做限定。
在本实施方式中，不涉及对安卓蓝牙硬件抽象层的封装，而只是对硬件抽象层以上的安卓蓝牙服务功能接口进行转换，在glibc环境下控制安卓蓝牙的装置和蓝牙应用和蓝牙硬件之间进行信息交互。在glibc环境下控制安卓蓝牙的装置中的功能接口转换器将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口，蓝牙服务框架中通信模块与蓝牙应用进行信息交互。命令下发模块通过转换后的glibc环境能调用的功能接口将消息发送给硬件抽象层，消息监听模块接收来自硬件抽象层的消息，完成蓝牙服务框架和蓝牙硬件之间的消息交互。本实施方式中的终端设备能够在蓝牙厂商只提供安卓驱动的条件下，实现在Linux操作系统中使用蓝牙功能。Linux应用程序开发者在使用蓝牙功能时无需关心底层细节，直接使用蓝牙服务框架提供的API即可。
本申请第四实施方式涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述实施例的方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请的实施方式，实现了在glibc环境下控制安卓蓝牙，并兼容所有的Linux应用程序。在蓝牙厂商只提供安卓蓝牙硬件的条件下，也可以在Linux操作系统中控制安卓蓝牙硬件以实现蓝牙功能，而不需要厂商针对Linux操作系统专门开发匹配的蓝牙硬件。除此之外，Linux应用程序开发者在使用蓝牙应用时不需要关心底层细节，直接使用装置中提供的应用编程接口(Application Program Interface，简称API)即可。
本领域的普通技术人员可以理解，上述各实施方式是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (11)

  1. 一种在glibc环境下控制安卓蓝牙的装置，包括：功能接口转换器、应用消息处理模块、命令下发模块和消息监听模块；
    所述功能接口转换器，用于将bionic环境下安卓蓝牙的功能接口转换为glibc环境能调用的功能接口；
    所述通信模块，用于与蓝牙应用、所述命令下发模块和所述消息监听模块进行通信；
    所述命令下发模块，用于根据来自所述通信模块的消息生成操作命令，并通过转换后的所述glibc环境能调用的功能接口将所述操作命令发送给蓝牙硬件；
    所述消息监听模块，用于监听来自所述蓝牙硬件的消息，并将处理后的所述来自所述蓝牙硬件的消息发送给所述通信模块。
  2. 根据权利要求1所述的在glibc环境下控制安卓蓝牙的装置，其中，所述通信模块包括：消息处理模块和协议管理模块；
    所述消息处理模块，用于将所述来自所述蓝牙应用的消息进行处理，并发送给所述协议管理模块，以及将所述来自所述协议管理模块的消息进行处理，并发送给所述蓝牙应用；
    所述协议管理模块，用于根据预设的协议与所述命令下发模块和所述消息监听模块进行通信。
  3. 根据权利要求1所述的在glibc环境下控制安卓蓝牙的装置，其中，所述功能接口转换器包括：加载模块、替换模块；
    所述加载模块，用于在所述glibc环境加载所述bionic环境的共享库；
    所述替换模块，用于将所述bionic环境的共享库提供的接口函数替换为所述glibc环境提供的接口函数。
  4. 根据权利要求2所述的在glibc环境下控制安卓蓝牙的装置，其中，所述消息处理模块包括:第一解析模块、第二解析模块、业务类型发送模块和执行结果发送模块；所述协议管理模块，包括：第一转换模块、第一发送模块、第二转换模块、第二发送模块；
    所述第一解析模块，用于根据所述来自所述蓝牙应用的消息解析出业务类型；
    所述业务类型发送模块，用于将所述业务类型发送给所述第一转换模块；
    所述第一转换模块，用于根据所述预设的协议将所述业务类型进行转换生成第一消息指令；
    所述第一发送模块，用于将所述第一消息指令发送给所述命令下发模块；
    所述第二转换模块，用于根据所述预设的协议将所述来自所述消息监听模块的消息进行转换生成第二消息指令；
    所述第二发送模块，用于将所述第二消息指令发送给所述消息处理模块；
    所述第二解析模块，用于根据所述第二消息指令解析出所述业务类型的执行结果；
    所述执行结果发送模块，用于将所述业务类型的执行结果发送给所述蓝牙应用。
  5. 根据权利要求4所述的在glibc环境下控制安卓蓝牙的装置，其中，所述第一转换模块包括：第一注册模块和第一生成模块，所述预设的协议包括第一回调函数；
    所述第一注册模块，用于注册所述第一回调函数；
    所述第一生成模块，用于利用所述第一回调函数将所述业务类型进行转换生成所述第一消息指令。
  6. 根据权利要求4所述的在glibc环境下控制安卓蓝牙的装置，其中，所述第二转换模块包括：第二注册模块和第二生成模块，所述预设的协议还包括第二回调函数；
    所述第二注册模块，用于注册所述第二回调函数；
    所述第二生成模块，用于利用所述第二回调函数将所述来自所述消息监听模块的消息进行转换，生成所述第二消息指令。
  7. 根据权利要求1中任一项所述的在glibc环境下控制安卓蓝牙的装置，其中，所述命令下发模块包括：创建模块、操作命令生成模块和操作命令发送模块；
    所述创建模块，用于创建消息处理策略；
    所述操作命令生成模块，用于利用所述消息处理策略生成与所述来自所述消息处理模块的消息对应的所述操作命令；
    所述操作命令发送模块，用于通过所述转换后的所述glibc环境能调用的功能接口将所述操作命令发送给所述蓝牙硬件。
  8. 一种在glibc环境下控制安卓蓝牙的方法，包括：
    所述功能接口转换器将所述bionic环境下安卓蓝牙的功能接口转换为所述glibc环境能调用的功能接口；
    所述通信模块接收并处理来自所述蓝牙应用的信息；
    所述命令下发模块根据所述来自所述通信模块的消息生成所述操作命令，并通过转换后的所述glibc环境能调用的功能接口将所述操作命令发送给蓝牙硬件；
    所述消息监听模块监听来自所述蓝牙硬件的消息，将所述来自所述蓝牙硬件的消息进行处理并发送给所述通信模块；
    所述通信模块将来自所述消息监听模块的消息进行处理并发送给所述蓝牙应用。
  9. 根据权利要求8所述的在glibc环境下控制安卓蓝牙的方法，其中，
    所述通信模块接收并处理来自所述蓝牙应用的信息，包括：所述通信模块包括所述消息处理模块和所述协议管理模块；
    所述消息处理模块将所述来自所述蓝牙应用的消息进行处理并发送给所述协议管理模块；
    所述协议管理模块根据所述预设的协议将来自所述消息处理模块的消息进行处理，并发送给所述命令下发模块；
    所述通信模块将来自所述消息监听模块的消息进行处理并发送给所述蓝牙应用，包括：
    所述协议管理模块根据所述预设的协议将来自所述消息监听模块的消息进行处理，并发送给所述消息处理模块；
    所述消息处理模块将来自所述协议管理模块的消息进行处理并发送给所述蓝牙应用。
  10. 一种终端设备，包括：权利要求1-7中任一项权利要求所述的在glibc环境下控制安卓蓝牙的装置、蓝牙应用和蓝牙硬件；
    所述蓝牙应用，通过所述在glibc环境下控制安卓蓝牙的装置控制所述蓝牙硬件的操作，并通过所述在glibc环境下控制安卓蓝牙的装置接收来自所述蓝牙硬件的信息；
    所述蓝牙硬件，接收并执行来自所述在glibc环境下控制安卓蓝牙的装置的操作命令，并通过所述在glibc环境下控制安卓蓝牙的装置将所述蓝牙硬件的信息返回给所述蓝牙应用。
  11. 一种计算机可读存储介质，存储有计算机程序，其中，所述计算机程序被处理器执行时实现权利要求8至9中任一项所述的在glibc环境下控制安卓蓝牙的方法。
PCT/CN2020/110493 2019-09-24 2020-08-21 在glibc环境下控制安卓蓝牙的装置、方法及终端设备 WO2021057351A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910903590.1A CN112559199A (zh) 2019-09-24 2019-09-24 在glibc环境下控制安卓蓝牙的装置、方法及终端设备
CN201910903590.1 2019-09-24

Publications (1)

Publication Number Publication Date
WO2021057351A1 true WO2021057351A1 (zh) 2021-04-01

Family

ID=75028964

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/110493 WO2021057351A1 (zh) 2019-09-24 2020-08-21 在glibc环境下控制安卓蓝牙的装置、方法及终端设备

Country Status (2)

Country Link
CN (1) CN112559199A (zh)
WO (1) WO2021057351A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113950034B (zh) * 2021-10-14 2024-04-26 北京字节跳动网络技术有限公司 蓝牙行为的模拟方法、装置和设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120174021A1 (en) * 2011-01-04 2012-07-05 Motorola, Inc. Systems and methods for displaying android applications launchers in webtop application tray
CN104484181A (zh) * 2014-12-23 2015-04-01 北京元心科技有限公司 在glibc环境下控制安卓相机的方法、装置及移动设备
CN106933529A (zh) * 2017-01-24 2017-07-07 北京元心科技有限公司 提供音频服务的方法及系统
CN108037924A (zh) * 2017-12-11 2018-05-15 中国电子科技集团公司第三十二研究所 glibc和bionic的驱动自适配系统及方法
CN109669782A (zh) * 2017-10-13 2019-04-23 阿里巴巴集团控股有限公司 硬件抽象层复用方法、装置、操作系统和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120174021A1 (en) * 2011-01-04 2012-07-05 Motorola, Inc. Systems and methods for displaying android applications launchers in webtop application tray
CN104484181A (zh) * 2014-12-23 2015-04-01 北京元心科技有限公司 在glibc环境下控制安卓相机的方法、装置及移动设备
CN106933529A (zh) * 2017-01-24 2017-07-07 北京元心科技有限公司 提供音频服务的方法及系统
CN109669782A (zh) * 2017-10-13 2019-04-23 阿里巴巴集团控股有限公司 硬件抽象层复用方法、装置、操作系统和设备
CN108037924A (zh) * 2017-12-11 2018-05-15 中国电子科技集团公司第三十二研究所 glibc和bionic的驱动自适配系统及方法

Also Published As

Publication number Publication date
CN112559199A (zh) 2021-03-26

Similar Documents

Publication Publication Date Title
CA2511912A1 (en) System and method for building and execution of platform-neutral generic services&#39; client applications
CN107291456B (zh) 一种多屏显示的控制方法及系统
US20090204725A1 (en) Wimax communication through wi-fi emulation
WO2021190469A1 (zh) 终端设备及其应用程序接口调用控制方法
CN102346669B (zh) 一种基于元数据的移动终端安全中间件系统及方法
US20080222617A1 (en) Server side application integration framework
CN104579792A (zh) 多适配方式实现多种类型虚拟资源集中管理架构及方法
CN111352653B (zh) 基于PaaS云平台服务器的系统开发方法及服务器
CN113032166B (zh) 核间通信的方法、处理器、核间通信系统及计算机可读存储介质
CN104883266A (zh) 网络配置访问方法及装置
CN111142910B (zh) 一种面向多界面的资源调配处理方法及系统
CN112418784B (zh) 一种服务的编排执行系统及方法
WO2021057351A1 (zh) 在glibc环境下控制安卓蓝牙的装置、方法及终端设备
CN113254075B (zh) 指令执行方法、指令执行装置、电子设备及存储介质
CN107896242B (zh) 一种服务共享方法及装置
US8051191B2 (en) Ethernet extensibility
CN113626095A (zh) 配置中心的切换方法、切换系统、电子设备及存储介质
TWI815098B (zh) Web請求處理方法、裝置、電子設備以及內儲程式之電腦可讀取記錄媒體
CN101521592B (zh) 一种建立打印机snmp代理的方法及装置
CN115994014A (zh) 容器引擎和容器引擎的实现方法、电子设备、存储介质
CN113641641A (zh) 文件存储服务的切换方法、切换系统、设备及存储介质
KR100494827B1 (ko) 하드웨어 독립적인 통신 인터페이스를 가지는 분산객체모델 기반의 라디오 서버와 이를 이용한 통신제어방법
CN104010026A (zh) 一种控制家电的方法、装置和家电控制系统
CN114900558B (zh) 一种通用的设备管理协议控制方法及装置
WO2022116191A1 (zh) 连接建立方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20867858

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20867858

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20.02.2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20867858

Country of ref document: EP

Kind code of ref document: A1