WM platform dual-mode mobile phone development process and framework

Currently
Mobile)/Unix/Linux embedded development has become the mainstream development mode of terminal communication products. Terminal communication products, especially mobile phones, will lead the current trend with the arrival of the 3G era. Dual-mode mobile phone products are the future development trend of mobile phones.

After work, we sorted out Wm
The development process and framework of platform dual-mode mobile phones.

First, be sure to figure out how the windows program runs internally.

The interaction between Windows applications, operating systems, and input/output devices is as follows:

Where:

(1) Windows programming is an event-driven programming model, mainly message-based. When a user needs to complete a function, the user will call a support item of the operating system, and then the operating system will package the user's needs into a message and deliver it to the message queue, finally, the application removes the message from the message queue and responds to the message.

(2) The application notifies the operating system to execute corresponding functions through function calls. In general, each function that the operating system can accomplish has a function corresponding to it. Therefore, an application calls these functions as a system call. The set of these functions is the interface that the Windows operating system provides to applications for programming.
API (Application
Programming Interface ).

(3) the operating system packs every event into a message struct MSG to pass to the application, and then the application processes the event. The process of responding to an event is called message response.

Secondly, find out Wm
The features of each layer in the platform dual-mode mobile phone Development Framework facilitate Bug Locating and debugging.

Generally
The development framework of platform dual-mode mobile phones is as follows:

 

Where:

(1) Wm-based
The active mode of platform. The secondary mode is embedded on the right.

(2) The main functions of each layer in the main module are as follows:

APP: ① display of user information and management of user operations. ② Interact with the API.

API: ① provides the app with a call interface and interacts with rilproxy. ② Realize system compatibility, reusability and security.

Rilproxy: ① call back the process function to the rildriver layer. ② Interact with the API and rildriver.

Rildriver: interacts with rilproxy and module, including active information.

Module: ① implement the network communication function. ② Interact with rildriver.

(3) The main functions of each layer in the sub-module are as follows:

APP: implements the same functions as the app in the main module through the cprog.exe program in the main module.

Tspi: The tspi provided by the API layer in the main module for interaction.

Driver: equivalent to the rilproxy layer and rildriver layer in the main module.
.

Module: ① implement the network communication function. ② Interact with rildriver.

Note the following:

(1) In theory, the process and framework of the secondary mode should be the same as that of the primary mode. However, in actual design, the layer for interaction is often merged. Therefore, the process and framework of the secondary mode can be different.

(2) WM has many different versions. For details, see the latest msdn.

Note: (1) the terms involved in a dual-mode mobile phone may have different names. (2) To adapt to development, Microsoft has changed WM to WP (Windows
Phone.