Shape of My Heart

The DG eCall recommends that the following essential requirements for transmitting both voice and data through the mobile networks should be adopted:
1.Pan-European solution:
o Roaming capability
o Belonging to GSM Standards (ETSI, 3GPP) that must be available for long enough to support vehicle life cycle
o Commonly implemented by all European Telcos & within preferably all GSM modules
2.Real time transport mechanism
3.Quasi simultaneous voice call and data transfer
4.Secure transport and routing mechanism (E112)
5.Automatic Acknowledgement

The DG eCall recommends that the architecture for eCall, as illustrated in following figure, is adopted by all stakeholders when implementing eCall. The process is described below:
1) The eCall Generator initiate the eCall by sensors triggered and/or manually, send the in-vehicle
triggered eCall to a PSAP. The eCall consists of two elements: a pure voice (audio) telephone call
based on 112 and the minimum set of data (MSD)
2) The eCall (data + voice) carried through the mobile network, is recognized by the mobile network
operator (MNO) as a 112 emergency call, and is first handled by the MNO. Based on the 112
handling the MNO enrich the call with the CLI (caller line identification), and at the same time,
according to the USD and the E112 recommendation, add the best location available (based on the
best effort principle11). After the 112 handling, the telecom operator delivers the 112-voice together
with the CLI, mobile location and the eCall MSD to the appropriate PSAP.
3) The PSAP transmits an acknowledgement to the eCall Generator specifying that the MSD have been
properly received.

//========================================================================
//TITLE:
// 预编译指令与相关宏小结
//AUTHOR:
// norains
//DATE:
// Saturday 10-December-2007
//Environment:
// EVC4.0 + Windows CE 5.0 Standard SDK
//========================================================================

1.预编译指令

01) #
空指令，无任何效果

02) #include
包含一个源代码文件

03) #define
定义宏

04) #undef
取消已定义的宏

05) #if
如果给定条件为真，则编译下面代码

06) #else
作为其他预处理的剩余选项进行编译

07) #ifdef
如果宏已经定义，则编译下面代码

08) #ifndef
如果宏没有定义，则编译下面代码

09) #elif
如果前面的#if给定条件不为真，当前条件为真，则编译下面代码

10) #endif
结束一个#if……#else条件编译块

11) #line
改变当前的行数和文件名称

12) #pragma
为编译程序提供非常规的控制流信息

13) #error
停止编译并显示错误信息

2.与编译器相关的宏

文中只列出部分相关宏,如果想查看完整的宏列表,可参考MSDN的"Predefined Macros"一节

01) _MSC_VER
Microsoft 编译器的版本宏.
各版本编译器相应的数值如下表所示:

Compiler _MSC_VER value
-------------------- -----------------------
C Compiler version 6.0 600
C/C++ compiler version 7.0 700
Visual C++, Windows, version 1.0 800
Visual C++, 32-bit, version 1.0 800
Visual C++, Windows, version 2.0 900
Visual C++, 32-bit, version 2.x 900
Visual C++, 32-bit, version 4.0 1000
Visual C++, 32-bit, version 5.0 1100
Visual C++, 32-bit, version 6.0 1200
Visual C++, 32-bit, version 2002 1300
Visual C++, 32-bit, version 2003 1310
Visual C++, 32-bit, version 2005 1400
Embedded Visual C++, 32-bit,version 4.0 Cross 1200 - 1202


02) _MFC_VER
MFC版本宏.

Version _MFC_VER value
-------------- -----------------
4.21 0x0421
6.0 0x0600
7.0 0x0700


03) __TIME__
编译当前源文件的时间,格式为 "hh:mm:ss" 样式的字符串.


04) __DATE__
编译当前源文件的日期,格式为 "Mmm dd yyyy" 样式的字符串.


05) __FILE__
编译的当前源文件名.

3.实例解说

01) 根据_MFC_VER值判断当前的编译环境.
#if _MSC_VER >= 1400
// this is Visual C++ 2005
#elif _MSC_VER >= 1310
// this is Visual c++ .NET 2003
#elif _MSC_VER > 1300
// this is Visual C++ .NET 2002
#endif


02) #else if 和 #elif 的细微差别
#if _MSC_VER < 1202
//EVC 4.0 complier is cross 1200 - 1202
#else if _MSC_VER >= 1400
//Visual C++ 2005 complier is 1400
#else
//Visual C++ 2005 complier is 1400
#endif

这段预编译代码在Evc4.0和visual studio 2005中编译会出错,提示错误为"unexpected #else".此时只要将"#else if"置换成"#elif"即可:

#if _MSC_VER < 1202
//EVC 4.0 complier is cross 1200 - 1202
#elif _MSC_VER >= 1400
//Visual C++ 2005 complier is 1400
#else
//Visual C++ 2005 complier is 1400
#endif

上面代码可以顺利编译通过.


03) 包含上级目录的某个头文件
如果当前文件需要包含上级目录的某个头文件,可采用"..\\"形式,比如:
#include "..\\Configure.h"

甚至还可以层层递推,定位于上上级目录:
#include "..\\..\\Configure.h"


04) 包含当前目录的某个文件夹下的头文件
如果当前文件需要包含当前目录下的某个文件夹中的某个头文件,可采用".\\"形式,比如:
#include ".\\Include\\Configure.h"


05) 判断当前CPU类型
#ifdef _X86_
//x86
#endif

#ifdef _MIPS_
//Mips
#endif

#ifdef _ARM_
//Arm
#endif


06)代码中手动添加lib库
#pragma comment (lib,"..\\Engine\\Engine.lib")

LTE and WiMax may be two peas in an OFDM pod, but they are not twins. Here are three significant differences:

1. Both use orthogonal frequency division multiple access (OFDMA) in the downlink. But WiMax optimizes for maximum channel usage by processing all the information in a wide channel. LTE, on the other hand, organizes the available spectrum into smaller chunks. This translates into higher power consumption, for WiMAX. An architecture that exploits the principles of SDR, however, could reconfigure its FFT function for better power efficiency.

2. LTE uses single-carrier frequency division multiple access (SC-FDMA) for uplink signaling, while WiMax sticks with OFDMA. LTE opted for the SC-FDMA specifically to boost power efficiency. Programmable solutions may be flexible enough to reuse gates and keep power low in LTE mode.

3. WiMax implementations are predominantly Time-Division Duplex (TDD). LTE seems to be heading in the Frequency-Division Duplex (FDD) direction with separate up and downstream channels. A WiMax TDD radio is simpler and makes techniques like beamforming easier.

调用DLL有两种方法：静态调用和动态调用.
(一).静态调用其步骤如下:
1.把你的youApp.DLL拷到你目标工程(需调用youApp.DLL的工程)的Debug目录下;
2.把你的youApp.lib拷到你目标工程(需调用youApp.DLL的工程)目录下;
3.把你的youApp.h(包含输出函数的定义)拷到你目标工程(需调用youApp.DLL的工程)目
录下;
4.打开你的目标工程选中工程,选择Visual C++的Project主菜单的Settings菜单;
5.执行第4步后，VC将会弹出一个对话框，在对话框的多页显示控件中选择Link页。然
后在Object/library modules输入框中输入:youApp.lib
6.选择你的目标工程Head Files加入：youApp.h文件;
7.最后在你目标工程(*.cpp,需要调用DLL中的函数)中包含你的:#include "youApp.h"
注：youApp是你DLL的工程名。

2.动态调用其程序如下:
动态调用时只需做静态调用步骤1.
{
HINSTANCE hDllInst = LoadLibrary("youApp.DLL");
if(hDllInst)
{
typedef DWORD (WINAPI *MYFUNC)(DWORD,DWORD);
MYFUNC youFuntionNameAlias = NULL; // youFuntionNameAlias 函数别名
youFuntionNameAlias = (MYFUNC)GetProcAddress
(hDllInst,"youFuntionName");
// youFuntionName 在DLL中声明的函数名
if(youFuntionNameAlias)
{
youFuntionNameAlias(param1,param2);
}
FreeLibrary(hDllInst);
}
}

显式（静态）调用：
LIB + DLL + .H，注意.H中dllexport改为dllimport

隐式（动态）调用：
DLL + 函数原型声明，先LoadLibrary，再GetProcAddress（即找到DLL中函数的地址），不用后FreeLibrary

Timer under Windows/WinCE

Read more...