CN114423024B - WLAN driver framework, componentization method of WLAN driver framework and related equipment - Google Patents

Abstract

The embodiment of the application provides a WLAN driving framework, a componentization method of the WLAN driving framework and related equipment. The method comprises the following steps: dividing a WLAN driving framework into a configuration part, a core driving part and a chip driving part, wherein the core driving part comprises a basic component and a service component; configuring the core driving part and the chip driving part by using a configuration part to generate configuration information; initializing basic components and business components in a chip driving part and a core driving part according to configuration information; and binding the service component and the chip driving part. In the embodiment, the WLAN driving framework is modularized, so that the WLAN driving framework is standardized, and the coupling degree among the components in the WLAN driving framework is reduced.

Description

WLAN driver framework, componentization method of WLAN driver framework and related equipment

technical field

Embodiments of the present application relate to the field of wireless communication, and in particular, to a componentization method of a WLAN driver framework and related devices.

Background technique

Usually, the wireless communication technology is mainly based on the wireless local area network (Wireless Local Area Network, WLAN) technology, and when using the WLAN, the WLAN chip and the corresponding chip driver need to work together. After several generations of development and standard evolution of WLAN technology, business logic and application scenarios have become more and more complex, resulting in a gradual increase in the complexity of chip drivers.

When WLAN chips are applied to products, due to the great differences in the development frameworks provided by the operating systems, the business logic and implementation of the chip drivers on different operating systems cannot be unified, and different chip manufacturers use the development frameworks in different degrees, resulting in Chip drivers under the same operating system vary greatly. At the same time, due to the problems of high coupling between modules, high framework complexity, and unreasonable abstraction in the open framework, the development threshold of chip drivers is currently high and the development is very difficult.

Contents of the invention

The embodiment of the present application discloses a WLAN driver framework, a componentization method of the WLAN driver framework and related equipment, which can componentize the WLAN driver framework, standardize the WLAN driver framework, and reduce the coupling degree between components in the WLAN driver framework.

The first aspect of the present application discloses a componentization method of the WLAN driver framework. The componentization method of the WLAN driver framework includes: dividing the WLAN driver framework into a configuration part, a core driver part, and a chip driver part. The core driver part includes basic components and Business components; use the configuration part to configure the core driver part and the chip driver part to generate configuration information; initialize the chip driver part and the basic components and business components in the core driver part according to the configuration information; bind the business component and the chip driver part.

The embodiments of the present application can componentize the WLAN driver framework, avoid huge differences in WLAN driver frameworks in different operating systems, standardize the WLAN driver framework, and reduce the coupling degree between components in the WLAN driver framework. In addition, it can also improve the efficiency of WLAN driver development and lower the development threshold.

In some optional implementation manners, the configuration information of the core driver part includes business component support information and basic component support information.

By adopting the technical solution, the configuration of the service components supported by the WLAN driver framework can be realized.

In some optional implementation manners, the componentization method of the WLAN driver framework further includes: using the configuration part to modify the service component support information according to the configuration information of the chip driver part.

By adopting the technical solution, it is possible to configure the support information of the service component according to the function or user's needs.

In some optional embodiments, initializing the basic components and service components in the core driver part according to the configuration information includes: analyzing the configuration information of the core driver part to obtain the configuration information of the core driver part after analysis; creating a WLAN component framework; The WLAN component framework initializes the basic components and service components in the core driver part according to the parsed configuration information of the core driver part.

By adopting this technical solution, the initialization of the basic components and business components in the core driver part can be realized, and the initialization of unnecessary business components in the configuration information can be avoided, which can not only improve the initialization efficiency, but also avoid running unnecessary business components .

In some optional implementation manners, creating the WLAN component framework includes: creating a frame structure; creating a frame structure processing method; hooking an implementation function of the frame structure processing method; registering the frame structure processing method and configuration for the frame structure information.

By adopting the technical solution, the creation of the WLAN component framework can be realized.

In some optional implementation manners, based on the WLAN component framework, initializing the basic components and service components in the core driver part according to the configuration information of the core driver part after parsing includes: determining the supported Components and supported service subcomponents; the supported components and supported service subcomponents are initialized based on the WLAN component framework.

By adopting the technical solution, the initialization of the basic components and business components in the core driver part can be realized. Initializing the service components according to the configuration information can realize tailoring some components in the WLAN component framework according to functional requirements.

In some optional implementation manners, binding the service component and the chip driver part includes: statically binding the service component and the chip driver part; or dynamically binding the service component and the chip driver part.

By adopting this technical solution, different binding forms can be used to realize the binding between service components and chip drivers, and improve the scene adaptability of the WLAN driver framework.

In some optional implementation manners, the static binding of the service component and the chip driver part includes: determining the associated service subcomponent and the chip driver according to the static binding configuration information; storing the associated service subcomponent and the chip driver through static configuration ; Start the associated business subcomponent and chip driver in the same process.

By adopting this technical solution, the static binding of the business component and the chip driver part can be realized for function hooking.

In some optional implementation manners, dynamically binding the service component and the chip driver includes: starting the service component; determining the chip based on chip detection; and starting the chip driver from the chip driver according to the determined chip.

By adopting this technical solution, the dynamic binding of business components and chip driver parts can be realized, and the dynamic binding of business components and chip driver parts can be performed according to functions or user needs, and the scene adaptability of the WLAN driver framework can be improved.

In some optional implementation manners, after dynamically binding the service component and the chip driver part, the componentization method of the WLAN driver framework further includes: the service component includes one or more service sub-components, and the bound service sub-component occupies The chip resource and the bound chip resource adjust the dynamic binding relationship between the bound business sub-component and the chip driver part.

By adopting this technical solution, the deployment flexibility of the WLAN driver framework can be further improved, and the binding relationship can be dynamically adjusted according to user needs or functions.

The second aspect of the present application discloses a WLAN driver framework. The WLAN driver framework includes a configuration part, a core driver part and a chip driver part, wherein the core driver part includes basic components and service components; Configure and generate configuration information; the core driver part initializes the basic components and business components in the core driver part according to the configuration information; the chip driver part initializes the chip driver in the chip driver part according to the configuration information.

By adopting the technical solution, it is possible to avoid huge differences in WLAN driver frameworks in different operating systems, standardize the WLAN driver framework, and reduce the coupling degree between components in the WLAN driver framework. And improve the efficiency of WLAN driver development and lower the development threshold.

In some optional implementation manners, the configuration information of the core driver part includes business component support information and basic component support information.

By adopting the technical solution, the configuration of the service components supported by the WLAN driver framework can be realized.

In some optional implementation manners, if the configuration information of the chip driver part is received, the configuration part modifies the service component support information according to the configuration information of the chip driver part.

By adopting the technical solution, it is possible to configure the supporting information of the service component according to the function or user's needs.

In some optional implementation manners, the core driver part parses the configuration information of the core driver part from the configuration part, and obtains the configuration information of the core driver part after analysis; creates a WLAN component framework; based on the WLAN component framework, according to the resolved core driver Part of the configuration information initializes the basic components and business components in the core driver part.

By adopting the technical solution, the initialization of the basic components and business components in the core driver part can be realized. Avoid initializing unnecessary business components in configuration information, improve initialization efficiency, and avoid running unnecessary business components.

In some optional implementation manners, the creation of the WLAN component framework by the core driver part includes: creating a frame structure; creating a frame structure processing method; hooking the implementation function of the frame structure processing method; registering the frame structure processing for the frame structure method and configuration information.

By adopting the technical solution, the creation of the WLAN component framework can be realized.

In some optional implementation manners, the core driver part determines the supported components and supported service subcomponents according to the parsed configuration information of the core driver part; and initializes the supported components and supported service subcomponents based on the WLAN component framework.

By adopting the technical solution, the initialization of the basic components and business components in the core driver part can be realized. Initializing the service components according to the configuration information can realize tailoring some components in the WLAN component framework according to functional requirements.

In some optional implementation manners, the core driver part binds the service component and the chip driver part.

By adopting this technical solution, the binding of the business component and the driver part of the chip can be realized, and the functions can be linked.

In some optional implementation manners, the core driver part is statically or dynamically bound to the service component and the chip driver part.

By adopting this technical solution, different binding forms of service components and chip drivers can be realized, and the scene adaptability of the WLAN driver framework can be improved.

The third aspect of the present application discloses an electronic device, including a processor and a memory; the memory is used to store instructions; the processor is used to call the instructions in the memory, so that the electronic device executes a WLAN driver framework componentization method.

The fourth aspect of the present application discloses a computer-readable storage medium, the computer-readable storage medium stores at least one instruction, and the componentization method of the WLAN driver framework is implemented when the at least one instruction is executed by a processor.

For the technical effects brought about by the second aspect to the fourth aspect, please refer to the descriptions related to the methods involved in the above methods, and details will not be repeated here.

Description of drawings

FIG. 1A is a schematic diagram of a WLAN driver framework of a LINUX operating system.

FIG. 1B is a schematic diagram of a network driver framework of the WINDOWS operating system.

Fig. 2 is a schematic diagram of a WLAN driver framework provided by an embodiment of the present application.

Fig. 3 is a schematic diagram of components of a WLAN driver framework provided by an embodiment of the present application.

FIG. 4 is a schematic diagram of component classification of a WLAN driver framework provided by an embodiment of the present application.

Fig. 5 is a schematic diagram of binding between a service component and a chip driver provided by an embodiment of the present application.

Fig. 6 is a flow chart of a componentization method of a WLAN driver framework provided by an embodiment of the present application.

FIG. 7 is an initialized WLAN driver framework provided by the embodiment of the present application.

FIG. 8 is a schematic structural diagram of an electronic device 100 provided by an embodiment of the present application.

FIG. 9 is a block diagram of the software structure of the electronic device 100 provided by the embodiment of the present application.

Detailed ways

It should be noted that in the embodiments of the present application, "at least one" refers to one or more, and "multiple" refers to two or more than two. "And/or" describes the association relationship of associated objects, indicating that there can be three types of relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B Can be singular or plural. The terms "first", "second", "third", "fourth", etc. (if any) in the description and claims of this application and the drawings are used to distinguish similar objects, not to Describe a specific order or sequence.

In the operating system of the electronic device, the componentization of the wireless local area network (WLAN, Wireless Local Area Network) driver framework includes division, loading, operation of the WLAN driver framework and processing logic inside the WLAN driver framework. The processing logic inside the WLAN driver framework may include processing logic for control services and data services.

In order to better understand the componentization method and related devices of the WLAN driver framework provided by the embodiments of the present application, the WLAN driver frameworks of the LINUX operating system and the WINDOWS operating system are firstly described below.

FIG. 1A is a schematic diagram of a WLAN driver framework of a LINUX operating system. As shown in FIG. 1A , the WLAN driver framework of the LINUX operating system in the electronic device includes components nl80211, cfg80211, mac80211, chip driver and so on. Among them, nl80211 is used to interact with user mode applications in electronic devices; cfg80211 is a management interface related to WLAN functions, used for system applications in electronic devices to control WLAN chips; mac80211 is a WLAN 802.11 protocol layer component, Provide the function of the Media Access Control Address (MAC, Media Access Control Address) layer of the 802.11 protocol standard; the WLAN chip driver (chip driver) part can be provided by the manufacturer of the network equipment in the electronic equipment, and is used for the management of the network equipment. For example, initialization, control, parameter configuration, monitoring, data interaction, etc. cfg80211 and mac80211 interact with the chip driver through the interface cfg80211_ops.

The WLAN driver framework of the LINUX operating system also includes skb (data model for network transmission), which is used to store transmitted network data and control information, and provide related operations on network data for calling by the WLAN driver framework. The LINUX operating system also includes wpa_supplicant (the transfer station between the Wi-Fi driver and the user) in the user state, which is used to support protocols and encryption authentication.

The components of the WLAN driver framework of the LINUX operating system are simply divided, the interface functions are not classified, and the object-oriented abstraction is relatively low-level. The LINUX operating system can define cfg80211, but does not regulate and restrict the chip driver, resulting in large differences in driver business logic and functional differences among chip manufacturers.

FIG. 1B is a schematic diagram of a network driver framework of the WINDOWS operating system, and the network driver framework of the WINDOWS operating system may include a WLAN driver framework. As shown in FIG. 1B, the WLAN driver framework of the WINDOWS operating system in the electronic device includes a Network Driver Interface Specification (NDIS), a miniport driver (Miniport driver), an intermediate driver (Intermediate Driver) and the like. Among them, NDIS provides network driver management through the ndis.sys library, for example, it may include driver registration/uninstallation, network device addition/deletion, network protocol binding and other functions. The "Native 802.11IM driver" module inside NDIS provides general functions of WLAN. Miniportdriver is a network device driver provided by the manufacturer of the network device in the electronic device, which is used for the management of the network device, such as performing initialization, control, parameter configuration, monitoring, data interaction, etc. The network device driver can register the driver with the WINDOWS operating system. Intermediate Driver is an intermediate driver, used for data monitoring, load sharing, etc. The WLAN driver framework of the WINDOWS operating system can isolate the WLAN chip driver through a WLAN Device Driver Interface (WLAN Device Driver Interface, WDI). The WINDOWS operating system provides functions such as network management, protocol layer binding, and driver management.

As shown in Figure 1B, TCP/IP (Transmission Control Protocol/Internet Protocol, Transmission Control Protocol/Internet Protocol) is a protocol stack for network transmission, which is used to process network protocols; network interface card (network interface card, NIC), NIC device is Network equipment. WDI is the interactive interface between NDIS and Miniport driver. The management objects are adapters and interfaces, which are used for WLAN network device management, such as initialization, control, parameter setting, and event reporting.

The WLAN driver framework of the WINDOWS operating system adopts a standardized network driver interface to realize network driver management. The network driver interface specification can be the NDIS specification; at the same time, it provides a series of API interfaces for network device driver management, including network device driver Functions such as registration/uninstallation, addition/deletion of network devices, network protocol binding, etc.

The WLAN driver framework scheme of the WINDOWS operating system is relatively complex, relying on NDIS and WDI, the coupling between functional modules in WLAN technology is strong, and it is difficult to tailor; it cannot adapt to miniaturized and embedded devices, and the component logic is not clear enough.

Fig. 2 is a schematic diagram of a WLAN driver framework provided by an embodiment of the present application.

In the embodiment provided by this application, according to the idea of separation of configuration and business, the WLAN driver framework can be designed as shown in Figure 2. Specifically, the WLAN driver framework can be divided into configuration parts (for example, configuration parts) and The driver part, and the driver part is further divided into two parts according to different services and service providers, for example, a core driver part (Core driver) and a chip driver part (chip driver). Among them, the chip driver of the chip driver part is adapted to the chip manufacturer.

The configuration part can describe and configure the core driver part and the chip driver part based on the Huawei configuration language HCS (HDF Configuration Source), and generate configuration information. The Huawei configuration language-based configuration part (HCS-CFG) may include the Huawei configuration language-based WLAN configuration part (WLAN HCS-CFG). HCS-CFG can perform development version configuration, driver configuration, and component configuration on the WLAN driver framework.

The core driver part initializes the basic components and business components in the core driver part according to the configuration information. The core driver part is the entity of the driver part in the WLAN driver framework, and is a public part of the WLAN driver framework. Based on the splitting of WLAN business logic and the abstraction of functions, the core driver part is divided into basic components and business components. A component is a functional unit after the WLAN driver function is split, and each component and each sub-component has a standardized implementation. Among them, the basic components can include configuration management components, communication components, protocol components, data components, bus (Bus) components and other necessary components; business components can include access point (Access Point, AP) subcomponents, station (Station, STA) subcomponents, Neighbor Awareness Networking (Neighbor Awareness Networking, NAN) subcomponents and other service subcomponents that implement actual services. For the description of each component, reference may be made to the description of FIG. 3 below.

The chip driver part initializes the chip driver in the chip driver part according to the configuration information. The chip driver implements chip adaptation, mainly the 802.11 MAC layer interface, chip communication, data flow control, and WLAN chip control implemented by each chip manufacturer.

The business components of the core driver part can be statically or dynamically bound to the chip driver part. The core driver part can parse the configuration information of the core driver part from the configuration part, and obtain the parsed configuration information of the core driver part. The core driver part can create WLAN component framework. Based on the WLAN component framework, the core driver part can initialize basic components and service components in the core driver part according to the parsed configuration information of the core driver part.

Specifically, the core driver part can determine the supported components and supported service subcomponents according to the parsed configuration information of the core driver part; and initialize the supported components and supported service subcomponents based on the WLAN component framework.

In the embodiment of the present application, static or dynamic binding of the service component and the chip driver part can be realized. For example, the configuration information includes static binding configuration information, and the core driver determines the associated business subcomponent and chip driver according to the static binding configuration information; stores the associated business subcomponent and chip driver through static configuration. The chip driver part starts the associated business subcomponent and chip driver in the same process. As another example, the dynamic binding of the service component and the chip driver includes: starting the service component; determining the chip based on chip detection; and starting the chip driver from the chip driver according to the determined chip. Wherein, for the binding manner of the business component and the chip driver, refer to the detailed description in FIG. 5 and FIG. 6 below.

Fig. 3 is a schematic diagram of components of a WLAN driver framework provided by an embodiment of the present application.

As mentioned above, the WLAN driver framework includes a core driver part, a chip driver part, and a configuration part, wherein the core driver part can initialize basic components and service components in the core driver part according to configuration information. Specifically, the basic components may include communication components ①, configuration management components ②, protocol components ⑥, data components, bus components ⑩ and other necessary components. Service components may include AP sub-components ③, STA sub-components ④, NAN sub-components ⑤ and other service sub-components to realize actual services. The data component may include a NetDevice object ⑦, a NetBuf data structure ⑧, and a FlowCtl parameter ⑨, wherein the FlowCtl parameter ⑨ represents a parameter for flow control.

The above description of the components and/or sub-components is only an example, and is not limited thereto in practical applications. For example, the service component may also include more service sub-components, such as the AN sub-component.

Business components are component objects abstracted according to WLAN functions. Among them, AP subcomponent ③ provides wireless workstations with access to wired LANs, and wired LANs to wireless workstations. STA subcomponent ④ implements station (infrastructure) functions. NAN Subcomponent ⑤ implements the WLAN sensing function. The core driver part can combine multiple components in the manner of "communication component-business component-protocol component-data component-bus component". Among them, business components can be assembled according to actual functional requirements. For example, for unnecessary functions, corresponding components can be deleted; for newly added functions, corresponding components can be created.

The configuration management component ② can configure the core driver part, can analyze and manage configuration information, and can be used to tailor components.

The communication component ① can use multiple communication methods to solve the communication differences between different platforms. At the same time, the communication component ① can be deployed in the business sub-components to support the independent operation of the business sub-components. The communication component ① can communicate with the wireless computer network security system (Wi-Fi Protected Access, WPA).

The protocol component ⑥ can be the API adaptation interface layer of the MAC layer of the 802.11 protocol, which is used to adapt the MAC APIs of different chip drivers, so as to shield the differences of the protocols of different chip drivers and shield the differences in services. Optionally, the protocol component can include more protocol types.

The WLAN driver framework provided in the embodiment of the present application can standardize the APIs to the upper layer, so as to unify the APIs to the upper layer from the WLAN driver frameworks of different operating systems.

The data component is an abstract component of the data service, which is used to realize the processing, forwarding and flow control of data packets. Among them, the NetDevice object ⑦ corresponds to the business sub-component. For example, the NetDevice object ⑦ corresponds to the AP subcomponent ③.

The bus component ⑩ can normalize the hardware bus used by the WLAN chip, standardize the read-write interface, and make the core driver part and the chip driver part access the bus interface in a unified way, so as to shield the core driver part and the chip driver part from differences.

The core driver part also includes chip detector (Chip detector), control read and write interface (Ctrl R/W), data read and write interface (Data R/W), etc.

FIG. 4 is a schematic diagram of component classification of a WLAN driver framework provided by an embodiment of the present application. Optionally, the WLAN driver framework may include communication components, service components, protocol components, data components, and bus components. Wherein, the communication component can include the Message component, the business component can include the AP subcomponent, the STA subcomponent, the NAN subcomponent, the protocol component can include the Mac80211 protocol layer component, and the data component can include the NetDevice object, the NetBuf data structure, the FlowCtl parameter, the bus component Can include Bus components. Business components and protocol components are extensible components, and subcomponents can be added according to functions or user needs.

Fig. 5 is a schematic diagram of binding between a business component and a chip driver provided by an embodiment of the present application, wherein the left figure shows a static binding of a business component and a chip driver, and the right figure shows a dynamic binding of a business component and a chip driver .

As shown in the left figure of Figure 5, component A1 is an AP subcomponent, component A2 is an STA subcomponent, and component AN is a NAN subcomponent. Components A1 and A2 are statically bound to the chip driver B1 of the chip driver. The chip driver BN of the driver part is statically bound.

As shown in the right figure of Figure 5, component A1 is an AP subcomponent, component A2 is a STA subcomponent, and component AN is a NAN subcomponent. Components A2 and AN are dynamically bound to the chip driver B1 of the chip driver part. Component A1 and the chip The chip of the driver part drives BN dynamic binding. Figure 5 shows an example of binding between business components and chip drivers. The actual application is not limited to the example shown in the figure. The specific binding implementation can refer to the WLAN driver framework shown in Figure 6 A detailed description of the binding part in the componentized method flow chart of .

As shown in FIG. 6, it is a flowchart of a componentization method of a WLAN driver framework provided by an embodiment of the present application. The componentization method of the WLAN driver framework is applied to an electronic device. Specifically, the componentization method of the WLAN driver framework includes:

S601. Divide the WLAN driver framework into a configuration part, a core driver part, and a chip driver part, where the core driver part includes basic components and service components.

S602. Using the configuration part to configure the core driver part and the chip driver part to generate configuration information.

The configuration part is used to display the configuration template to the development user, and the configuration of the core driver part and the chip driver part input by the development user based on the configuration template is received to generate configuration information.

The configuration information may include configuration information of the WLAN driver framework, configuration information of the core driver part, and configuration information of the chip driver part.

The configuration information of the core driver part may include: business component support information, basic component support information, and the like.

The configuration information of the chip driver part may include: chip quantity, chip operation efficiency, chip type, and the like.

The configuration information of the core driver part may also include: a WLAN driver framework function support table. The configuration information of the chip driver part may also include: a WLAN driver framework function support table.

The configuration information of the WLAN driver framework is a description of the configuration of the CPU and bus connected to the WLAN driver framework.

In an embodiment of the present application, the electronic device can use the configuration part to modify the service component support information according to the configuration information of the chip driver part. Specifically, if the number of chips is greater than the preset number of chips, and/or the computing efficiency of the chip is greater than the preset computing efficiency of the chip, add the supported business sub-components in the business component support information; if the number of chips is less than or equal to the preset chip number; and/or Or the chip computing efficiency is less than or equal to the preset chip computing efficiency, and the supported business sub-components are reduced in the business component support information. Optionally, the electronic device can determine whether the chip resource occupied by the supported service subcomponent is greater than or equal to the available chip resource; if the chip resource occupied by the supported service subcomponent is greater than or equal to the available chip resource, the service component supports Reduce the supported business sub-components in the information; if the supported business sub-components need to occupy less chip resources than the available chip resources, add the supported business sub-components in the business component support information.

S603. Initialize the basic components and service components in the chip driver part and the core driver part according to the configuration information.

In one embodiment of the present application, the electronic device can analyze the configuration information of the core driver part, obtain the configuration information of the core driver part after analysis; create a WLAN component framework; based on the WLAN component framework, according to the configuration of the core driver part after analysis The information initializes the basic components and business components in the core driver part.

Specifically, the creation of the WLAN component framework by the electronic device may include: creating a frame structure by the electronic device; creating a processing method for the frame structure; attaching an implementation function of the processing method for the frame structure; registering the processing method and configuration information for the frame structure .

For example, during specific implementation, the WLAN component framework can be created according to the WifiModuleCreate method. A frame structure can be created according to "struct WifiModule*module=OsalMemAlloc(sizeof(*module))", where "struct" is a structure, "*module" is a pointer, "OsalMemAlloc" is a function to allocate memory of a specified size, " sizeof" is the memory size. The frame structure processing method iface can be created according to "iface=OsalMemAlloc(sizeof(*iface))". According to "iface->updateModule=UpdateWiFiModule", you can modify the implementation function for iface connection; you can add implementation functions for iface connection according to "iface->addFeature=AddFeature"; you can use "iface->delFeature=DelFeature" to connect iface Remove implementation function. According to "module->iface=iface; module->moduleConfig.hslConfig=config", the framework structure processing method and configuration information can be registered with the framework structure.

Specifically, based on the WLAN component framework, the framework initializes the basic components and service components in the core driver part according to the configuration information of the parsed core driver part, including:

Determine supported components and supported service subcomponents according to the parsed configuration information of the core driver; and initialize supported components and supported service subcomponents based on the WLAN component framework.

For example, the configuration information parsed by the core driver part includes "Station{name="sta"; mode=true; }HostAp{name="ap"; mode=false;}P2P{name="p2p"; mode=false; }Mac80211{mode=true;}NetFlow{mode=false;}NetDevice{mode=true;}Netbuf{mode=true;}", according to the analyzed configuration information of the core driver part, it is determined that the supported component is the protocol component "Mac80211 ", "NetDevice", "Netbuf", the supported service subcomponent is the STA subcomponent "sta"; traverse each component based on the WLAN component framework, and initialize the supported components and supported service subcomponents. For example, a component or business sub-component whose mode value is equal to true may be determined as a supported component or business sub-component; a component or business sub-component whose mode value is equal to false may be determined as an unsupportable component or business sub-component.

Optionally, before the supported components and supported service subcomponents are initialized based on the WLAN component framework, it may also be determined whether there is a function matching the supported components and supported service subcomponents in the WLAN driver framework function support table. If there is a function matching the supported components and supported service subcomponents in the WLAN driver framework function support table, the supported components and supported service subcomponents are initialized based on the WLAN component framework.

In the embodiment provided by the present application, the electronic device can determine the supported components according to the parsed configuration information of the core driver part; and initialize the supported components based on the WLAN component framework. The electronic device can determine the supported service subcomponents according to the parsed configuration information of the core driver part; and initialize the supported service subcomponents based on the WLAN component framework.

The electronic device can analyze the configuration information of the chip driver part to obtain the analyzed configuration information of the chip driver part; initialize the chip driver part according to the analyzed configuration information of the chip driver part.

It will be described with reference to FIG. 7 , as shown in FIG. 7 , it is the initialized WLAN driver framework provided by the embodiment of the present application. The initialized components include configuration part, core driver part (configuration management component, communication component, business component, protocol component, data component, bus component), chip driver part. Among them, the business component includes a business sub-component (STA sub-component ④), and the data component includes NetDevice object and NetBuf data structure. The chip driver of the chip driver part can drive the chip. For example, the chip driver of the chip driver part can drive the Hi3881 chip.

The electronic device can parse the configuration information through the configuration component.

S604, binding the service component and the chip driver part.

In an embodiment of the present application, the electronic device may perform static binding or dynamic binding on the service component and the chip driver part.

Specifically, the configuration information also includes static binding configuration information, and the static binding of the service component and the chip driver of the electronic device includes: determining the associated service sub-component and the chip driver according to the static binding configuration information; storing the associated Business subcomponents and chip drivers; start the associated business subcomponents and chip drivers in the same process.

Specifically, the dynamic binding of the service component and the chip driver of the electronic device includes: starting the service component; determining the chip based on chip detection; and starting the chip driver from the chip driver according to the determined chip.

Further, the determined chip may include one chip, multiple chips of the same type, or multiple chips of different types. After the chip driver is started, the chip driver may drive one chip, multiple chips of the same type, or multiple chips of different types. chips to support business components. For example, combined with the left figure in Figure 5, the chip driver can drive two different types of chips, namely chip B1 and chip BN, chip B1 provides support for the STA sub-component and AP sub-component in the business component, and chip BN is The NAN subassembly provides support. Combined with the right figure in Figure 5, the chip driver can drive two different types of chips, namely chip B1 and chip BN. Chip B1 provides support for the STA sub-component and NAN sub-component in the business component, and chip BN is the AP in the business component. Subcomponents provide support.

In one embodiment of the present application, after the electronic device dynamically binds the service component and the chip driver part, the componentization method of the WLAN driver framework further includes: according to the chip resource occupied by the bound service sub-component and the bound chip resource Adjust the dynamic binding relationship between the bound business sub-component and the chip driver part. Specifically, the electronic device can determine whether the chip resource occupied by the bound service sub-component is greater than or equal to the bound chip resource; if the chip resource occupied by the bound service sub-component is greater than or equal to the bound chip resource, the bound Rebind the business subcomponents to the available chip drivers in the chip driver section. The chip resources may be determined by the number of chips and the computing efficiency of the chips. For example, the chip resources may be equal to the product of the number of chips and the computing efficiency of the chips.

After the electronic device dynamically binds the service component and the chip driver, the componentization method of the WLAN driver framework further includes: dynamically adjusting the dynamic binding relationship between the service sub-component and the chip driver according to the configuration information. Specifically, the electronic device can determine the binding relationship or non-binding relationship between the service sub-component and the chip driver according to the configuration information; and bind the service sub-component and the chip driver according to the determined binding relationship; Release the binding between the business subcomponent and the chip driver. Binding or non-binding can be configured through preset values, such as 0 and 1.

An implementation manner of the embodiment of the present application is described below through some exemplary codes.

For example, a kernel driver configuration file can include the following configuration information:

For example, create a WLAN component framework; based on the WLAN component framework, initialize the basic components and business components in the core driver part according to the parsed configuration information of the core driver part:

For example, creating a WLAN component framework specifically includes:

FIG. 8 is a schematic structural diagram of an electronic device 100 provided by an embodiment of the present application. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and A subscriber identification module (subscriber identification module, SIM) card interface 195 and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, bone conduction sensor 180M, etc.

It can be understood that, the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor ( image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. . Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

Wherein, the controller may be the nerve center and command center of the electronic device 100 . The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver (universal asynchronous receiver) /transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input and output (general-purpose input/output, GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and/or A universal serial bus (universal serial bus, USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (serial data line, SDA) and a serial clock line (derail clock line, SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 can be respectively coupled to the touch sensor 180K, the charger, the flashlight, the camera 193 and the like through different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to realize the touch function of the electronic device 100 .

The I2S interface can be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170 . In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface, so as to realize the function of answering calls through the Bluetooth headset.

The PCM interface can also be used for audio communication, sampling, quantizing and encoding the analog signal. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to realize the function of answering calls through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 and the wireless communication module 160 . For example: the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to realize the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface, so as to realize the function of playing music through the Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . The MIPI interface includes a camera serial interface (camera serial interface, CSI), a display serial interface (displayserial interface, DSI), and the like. In some embodiments, the processor 110 communicates with the camera 193 through the CSI interface to realize the shooting function of the electronic device 100 . The processor 110 communicates with the display screen 194 through the DSI interface to realize the display function of the electronic device 100 .

The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193 , the display screen 194 , the wireless communication module 160 , the audio module 170 , the sensor module 180 and so on. The GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface conforming to the USB standard specification, specifically, it may be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100 , and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones and play audio through them. This interface can also be used to connect other electronic devices, such as AR devices.

It can be understood that the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The charging management module 140 is configured to receive a charging input from a charger. Wherein, the charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100 . While the charging management module 140 is charging the battery 142 , it can also provide power for electronic devices through the power management module 141 .

The power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 . The power management module 141 receives the input from the battery 142 and/or the charging management module 140 to provide power for the processor 110 , the internal memory 121 , the external memory, the display screen 194 , the camera 193 , and the wireless communication module 160 . The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be disposed in the processor 110 . In some other embodiments, the power management module 141 and the charging management module 140 may also be set in the same device.

The wireless communication function of the electronic device 100 can be realized by the antenna 1 , the antenna 2 , the mobile communication module 150 , the wireless communication module 160 , a modem processor, a baseband processor, and the like.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor, and convert them into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.

A modem processor may include a modulator and a demodulator. Wherein, the modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal is passed to the application processor after being processed by the baseband processor. The application processor outputs sound signals through audio equipment (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194 . In some embodiments, the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent from the processor 110, and be set in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (wireless fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (codedivision multiple access, CDMA), wideband code Wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), fifth generation wireless communication system (5G, the 5thGeneration of wireless communication system), BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc. The GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou satellite navigation system (beidounavigation satellite system, BDS), a quasi-zenith satellite system (quasi- zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).

The electronic device 100 realizes the display function through the GPU, the display screen 194 , and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos and the like. The display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light emitting diode). AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diodes (quantum dot light emitting diodes, QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194 , where N is a positive integer greater than 1.

The electronic device 100 can realize the shooting function through the ISP, the camera 193 , the video codec, the GPU, the display screen 194 and the application processor.

The ISP is used for processing the data fed back by the camera 193 . For example, when taking a picture, open the shutter, the light is transmitted to the photosensitive element of the camera through the lens, and the light signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be located in the camera 193 .

Camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects it to the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a complementary metal-oxide-semiconductor (complementary metal-oxide-semiconductor, CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other image signals. In some embodiments, the electronic device 100 may include 1 or N cameras 193 , where N is a positive integer greater than 1.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 can play or record videos in various encoding formats, for example: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor. By referring to the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process input information and continuously learn by itself. Applications such as intelligent cognition of the electronic device 100 can be realized through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. Such as saving music, video and other files in the external memory card.

The internal memory 121 may be used to store computer-executable program codes including instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 . The internal memory 121 may include an area for storing programs and an area for storing data. Wherein, the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like. The storage data area can store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.) and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.

The electronic device 100 can implement audio functions through the audio module 170 , the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be set in the processor 110 , or some functional modules of the audio module 170 may be set in the processor 110 .

Speaker 170A, also referred to as a "horn", is used to convert audio electrical signals into sound signals. Electronic device 100 can listen to music through speaker 170A, or listen to hands-free calls.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the receiver 170B can be placed close to the human ear to receive the voice.

The microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can put his mouth close to the microphone 170C to make a sound, and input the sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 may be provided with two microphones 170C, which may also implement a noise reduction function in addition to collecting sound signals. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and realize directional recording functions, etc.

The earphone interface 170D is used for connecting wired earphones. The earphone interface 170D may be the USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.

The pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may be comprised of at least two parallel plates with conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 may also calculate the touched position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view short messages is executed. When a touch operation whose intensity is greater than or equal to the first pressure threshold acts on the icon of the short message application, the instruction of creating a new short message is executed.

The gyro sensor 180B can be used to determine the motion posture of the electronic device 100 . In some embodiments, the angular velocity of the electronic device 100 around three axes (ie, x, y and z axes) may be determined by the gyro sensor 180B. The gyro sensor 180B can be used for image stabilization. Exemplarily, when the shutter is pressed, the gyro sensor 180B detects the shaking angle of the electronic device 100, calculates the distance that the lens module needs to compensate according to the angle, and allows the lens to counteract the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude based on the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

The magnetic sensor 180D includes a Hall sensor. The electronic device 100 may use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a clamshell machine, the electronic device 100 can detect opening and closing of the clamshell according to the magnetic sensor 180D. Furthermore, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, features such as automatic unlocking of the flip cover are set.

The acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of electronic devices, and can be used in applications such as horizontal and vertical screen switching, pedometers, etc.

The distance sensor 180F is used to measure the distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 may use the distance sensor 180F for distance measurement to achieve fast focusing.

Proximity light sensor 180G may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes. The light emitting diodes may be infrared light emitting diodes. The electronic device 100 emits infrared light through the light emitting diode. Electronic device 100 uses photodiodes to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it may be determined that there is an object near the electronic device 100 . When insufficient reflected light is detected, the electronic device 100 may determine that there is no object near the electronic device 100 . The electronic device 100 can use the proximity light sensor 180G to detect that the user is holding the electronic device 100 close to the ear to make a call, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode, automatic unlock and lock screen in pocket mode.

The ambient light sensor 180L is used for sensing ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket, so as to prevent accidental touch.

The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access to application locks, take pictures with fingerprints, answer incoming calls with fingerprints, and the like.

The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to implement a temperature treatment strategy. For example, when the temperature reported by the temperature sensor 180J exceeds the threshold, the electronic device 100 may reduce the performance of the processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to prevent the electronic device 100 from being shut down abnormally due to the low temperature. In some other embodiments, when the temperature is lower than another threshold, the electronic device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

Touch sensor 180K, also known as "touch panel". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a “touch screen”. The touch sensor 180K is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 , which is different from the position of the display screen 194 .

The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor 180M can also contact the human pulse and receive the blood pressure beating signal. In some embodiments, the bone conduction sensor 180M can also be disposed in the earphone, combined into a bone conduction earphone. The audio module 170 can analyze the voice signal based on the vibration signal of the vibrating bone mass of the vocal part acquired by the bone conduction sensor 180M, so as to realize the voice function. The application processor can analyze the heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M, so as to realize the heart rate detection function.

The keys 190 include a power key, a volume key and the like. The key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 can receive key input and generate key signal input related to user settings and function control of the electronic device 100 .

The motor 191 can generate a vibrating reminder. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations applied to different applications (such as taking pictures, playing audio, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects for touch operations acting on different areas of the display screen 194 . Different application scenarios (for example: time reminder, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

The indicator 192 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.

The SIM card interface 195 is used for connecting a SIM card. The SIM card can be connected and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . The electronic device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card and so on. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards may be the same or different. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calling and data communication. In some embodiments, the electronic device 100 adopts an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100 .

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .

FIG. 9 is a block diagram of the software structure of the electronic device 100 provided by the embodiment of the present application. The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, the application program layer, the application program framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer. The application layer can consist of a series of application packages.

As shown in FIG. 9, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 9, the application framework layer can include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. Said data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebook, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, the management of call status (including connected, hung up, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify the download completion, message reminder, etc. The notification manager can also be a notification that appears on the top status bar of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, issuing a prompt sound, vibrating the electronic device, and flashing the indicator light, etc.

Android Runtime includes core library and virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application program layer and the application program framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

A system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of various commonly used audio and video formats, as well as still image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing, etc.

2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

If the integrated modules of the electronic device 100 are implemented in the form of software function modules and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above-mentioned embodiments in the present application can also be completed by instructing related hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium In this example, when the computer readable instructions are executed by the processor, the steps of the above-mentioned various method embodiments can be realized. Wherein, the computer-readable instructions include computer-readable instruction codes, and the computer-readable instruction codes may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer-readable instruction code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random memory access memory (RAM), etc.

This embodiment also provides a computer storage medium, where computer instructions are stored in the computer storage medium, and when the computer instructions are run on the electronic device, the electronic device is made to perform the steps of the above-mentioned related methods to implement the WLAN driver framework in the above-mentioned embodiment. Component approach.

This embodiment also provides a computer program product, which, when running on the electronic device, causes the electronic device to execute the above related steps, so as to realize the componentization method of the WLAN driver framework in the above embodiment.

In addition, an embodiment of the present application also provides a device, which may specifically be a chip, a component or a module, and the device may include a connected processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device is running, The processor can execute the computer-executable instructions stored in the memory, so that the chip executes the componentization method of the WLAN driver framework in the above method embodiments.

Wherein, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is all used to execute the corresponding method provided above, therefore, the beneficial effects it can achieve can refer to the corresponding method provided above The beneficial effects in the method will not be repeated here.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated according to needs It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined Or it can be integrated into another device, or some features can be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separated, and a component displayed as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or may be distributed to multiple different places. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium Among them, several instructions are included to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other various media that can store program codes. .

The above is only a specific implementation of the application, but the protection scope of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the application should be covered within the protection scope of the application . Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims (20)

1. A componentization method for a Wireless Local Area Network (WLAN) driven framework, the method comprising:

dividing a WLAN driving framework into a configuration part, a core driving part and a chip driving part, wherein the core driving part comprises a basic component and a service component;

configuring the core driving part and the chip driving part by using the configuration part to generate configuration information;

initializing the basic components and the business components in the chip driving part and the core driving part according to the configuration information;

and binding the service component and the chip driving part.

2. The componentization method of the WLAN driven framework of claim 1, wherein the configuration information of the core driven part comprises service component support information and infrastructure component support information.

3. The componentization method of the WLAN driven framework of claim 2, wherein the componentization method of the WLAN driven framework further comprises:

and modifying the service component support information by using the configuration part according to the configuration information of the chip driving part.

4. The componentization method of the WLAN driven framework of claim 1, wherein the initializing the base components and the service components in the core driven portion according to the configuration information comprises:

analyzing the configuration information of the core driving part to obtain the analyzed configuration information of the core driving part;

creating a WLAN component framework;

based on the WLAN component framework, initializing the basic components and the service components in the core driving part according to the analyzed configuration information of the core driving part.

5. The componentized method of the WLAN driven framework of claim 4, wherein the creating the WLAN component framework comprises:

creating a frame structure;

creating a frame structure processing method;

hooking an implementation function of the frame structure body processing method;

registering the framework structure processing method and the configuration information for the framework structure.

6. The componentization method of the WLAN driven framework according to claim 4, wherein the initializing the base component and the service component in the core driven part according to the parsed configuration information of the core driven part based on the WLAN component framework comprises:

determining supported components and supported service subcomponents according to the analyzed configuration information of the core driving part;

initializing the supported components and the supported traffic subcomponents based on the WLAN component framework.

7. The componentized method of the WLAN driven framework of claim 1, wherein said binding the traffic component with the chip driven portion comprises:

statically binding the service component and the chip driving part; or

And dynamically binding the service component and the chip driving part.

8. The componentized method of the WLAN driven framework of claim 7, wherein the statically binding the traffic component with the chip driven portion comprises:

determining the associated service sub-components and chip drivers according to the static binding configuration information;

storing the associated service sub-components and the chip driver in a static configuration mode;

and starting the associated service sub-component and the chip driver in the same process.

9. The componentized method of the WLAN driven framework of claim 7, wherein said dynamically binding the traffic component with the chip driven portion comprises:

starting the business component;

determining a chip based on chip detection;

starting chip driving from the chip driving part according to the determined chip.

10. The componentized method of the WLAN driven framework of claim 9, wherein after the dynamically binding the traffic component with the chip driven portion, the componentized method of the WLAN driven framework further comprises:

the service component comprises one or more service sub-components, and the dynamic binding relationship between the bound service sub-components and the chip driving part is adjusted according to the chip resources occupied by the bound service sub-components and the bound chip resources.

11. A wireless local area network, WLAN, driven framework, the WLAN driven framework comprising:

the system comprises a configuration part, a core driving part and a chip driving part, wherein the core driving part comprises a basic component and a business component;

the configuration part configures the core driving part and the chip driving part to generate configuration information;

the core driving part initializes the basic components and the service components in the core driving part according to the configuration information;

the chip driving part initializes the chip driving in the chip driving part according to the configuration information.

12. The WLAN driven framework of claim 11, wherein the configuration information of the core driven portion includes service component support information and infrastructure component support information.

13. The WLAN driven framework of claim 12, wherein if the configuration information of the chip driving part is received, the configuration part modifies the service component support information according to the configuration information of the chip driving part.

14. The WLAN driven framework of claim 11, wherein the core driving part parses the configuration information of the core driving part from the configuration part to obtain the parsed configuration information of the core driving part;

creating a WLAN component framework;

based on the WLAN component framework, initializing the basic components and the service components in the core driving part according to the analyzed configuration information of the core driving part.

15. The WLAN driven framework of claim 14, wherein the core driver portion creating the WLAN component framework comprises:

creating a frame structure;

creating a frame structure processing method;

hooking an implementation function of the frame structure body processing method;

registering the framework structure processing method and the configuration information for the framework structure.

16. The WLAN driven framework of claim 14, wherein the core driver portion determines supported components and supported service subcomponents based on the parsed configuration information of the core driver portion;

initializing the supported components and the supported traffic subcomponents based on the WLAN component framework.

17. The WLAN driven framework of claim 11, wherein the core driver portion binds the service component with the chip driver portion.

18. The WLAN driven framework of claim 17, wherein the core driver portion statically or dynamically binds the traffic component with the chip driver portion.

19. A computer device comprising a processor and a memory; the memory to store instructions; the processor to invoke the instructions in the memory to cause the computer device to perform the componentized method of the wireless local area network WLAN driver framework of any of claims 1 to 10.

20. A computer-readable storage medium storing at least one instruction which, when executed by a processor, implements a modular method of a wireless local area network, WLAN, driver framework as claimed in any one of claims 1 to 10.

Images