OMA DM UI & Report

6
3/23 Daily Report -- Monky ============================================================ A. Some discussion update ============================================================ 1. I’ve joined the process of FOTA/DM test with Esa. a) The DM setting would be only verified on the server (management website) or device (via registry). Not test upon a specified application, such as MMS. b) FOTA process (1) When booting up, DM client can auto run and self register to server (but we now set it up manually). Device got SMS notification and start to init/authenticate data from server after press “Yes” (2) GPRS connection is activated to exchange from server, press “Yes” (3) Popup info. message that is preset in the DM server by tester, press “Yes” (4) Get message that shows the package size, press “Yes”

Transcript of OMA DM UI & Report

Page 1: OMA DM UI & Report

3/23 Daily Report -- Monky

============================================================

A. Some discussion update

============================================================

1. I’ve joined the process of FOTA/DM test with Esa.

a) The DM setting would be only verified on the server (management website)

or device (via registry). Not test upon a specified application, such as MMS.

b) FOTA process

(1) When booting up, DM client can auto run and self register to server (but we now set it up manually). Device got SMS notification and start to init/authenticate data from server after press “Yes”

(2) GPRS connection is activated to

exchange from server, press “Yes”

(3) Popup info. message that is preset in the DM server by tester, press “Yes”

(4) Get message that shows the package size, press “Yes”

Page 2: OMA DM UI & Report

(5) Begin to download update package (6) After download, popup message to let user confirm package update. (can be deferred), Press “Start”

**** Note that if the download process

is interrupted (out of electricity or…)

The download process will be resumed

from step (4) and data can be resumed

also.

(7) Reboot…. (8) Show MSFT’s update UI

Page 3: OMA DM UI & Report

(9) Reboot again…. (10) Show MSFT’s package update success UI (version from v5.2.0.1401 to v 6.2.0.1401)

** DM Client (bootstrap run up) detect

the update is success now and send data

to DM sever (GPRS connection is

activated)

(c) DM Process

Page 4: OMA DM UI & Report

We can login into HP’s test server to have our own test.

Server URL:

http://219.143.232.148:8001/selfcare/

Account/password is based on the SIM number.

The behavior of DM set(配置) and get(采集) is basically normal now, please

check attached document “DMServerData.doc”. This is the test result recorded

in DM server. The test process is get -> set-> get. Basically, the integration is

okay now but the detailed value needs to be verified item by item.

d) Update package size

Our test update package can be down-sized to decrease test time and cost. (it

may take 30RMB to download 1MB data and we have 700KB now , it takes

around 20 mins to download via GPRS)

2. Some Risk must be concerned.

a) Currently, no full test case support from HP since we don’t have business

agreement to them….

b) CU test schedule is targeted on 4/2 in 深圳, we may only have 1+ week to do

our QA pre-test.

. 3. I bought 200 RMB充值卡 of CU SIM for DM/FOTA test.

============================================================

B. Technical Issue

============================================================

[FOTA]

Except Self Register, the whole process can get it done.

[DM - OEM Library]

1. Per Square’s suggestion, I change to deliver a DLL and a fixed static LIB to HP,

therefore we can debug our own code independently from DM Client (mProDM.exe).

Page 5: OMA DM UI & Report

We only need to change our own DLL once we need debugging.

2. Add more debug messages.

3. We need to study how to suppress system notification since CMCC has this kind of

requirement to suppress backlight/ notification tone when DM SMS notification is

coming.

4. Now, OEMDMlib.lib I deliver to HP is completed up to 16 APIs of 18.

****Please note that the entire integration test is passed but the detailed set/get values

need to be checked later.

//// Device base information

char *Cell_DMLib_getSoftwareVersion(void); // done, pass test

char *Cell_getUpdatePackageName();// done, pass test

//// MMS profiling

char *Cell_devParam_getMMS_MMSC(void); // done, pass test

int Cell_devParam_replaceMMS_MMSC(char* data); // done, pass test

int Cell_MMSProxySettingChange(int flag, char* val); // done, pass test

//// PIM profiling and configuraton

// NOTES:

// REMOVE by CU but would be implemented under CMCC

char *Cell_devParam_getPIM_Addr(void);

int Cell_devParam_replacePIM_Addr(char* data); char

*Cell_devParam_getPIM_AddressBookURI (void); int

Cell_devParam_replacePIM_AddressBookURI (char* data);

char *Cell_devParam_getPIM_CalendarURI (void);

int Cell_devParam_replacePIM_CalendarURI (char* data);

char *Cell_devParam_getPIM_PortNbr (void);

int Cell_devParam_replacePIM_PortNbr (char* data);

char *Cell_devParam_getPIM_UserName (void);

int Cell_devParam_replacePIM_UserName (char* data);

char *Cell_devParam_getPIM_PassWord (void);

int Cell_devParam_replacePIM_PassWord (char* data);

Page 6: OMA DM UI & Report

//// DM GPRS Setting

// Have solution, Taipei can help me to find out solution

// but still need to confirm if we need to implement this!

// we may reserve 32 bytes * 5 space

int Cell_GetDMSettings(int flag, char *buf, int size); // TBD

int Cell_SetDMSettings(int flag, char *data); // TBD

//// Ring tone

BOOL Cell_DMPlayNotifTone(); // done, pass test

BOOL Cell_RemoveGPRSActivationPopup(void); // done, pass test

BOOL Cell_EnableGPRSActivationPopup(void); // done, pass test

////////////////////////////////////////////////////////////////

//// Supplementary API

////////////////////////////////////////////////////////////////

char* Cell_devParam_getSR_number(void); // done, pass test

char* Cell_devParam_getSR_port(void); // done, pass test

char* Cell_devParam_getPushMail_ServerName(void); // done, pass test

char* Cell_devParam_getPushMail_ServerURL(void); // done, pass test

char* Cell_devParam_getBookmark_Name(void);

char* Cell_devParam_getBookmark_URL(void);

char* Cell_devParam_getStreaming_ServerURL(void);

int Cell_devParam_replaceSR_number(char* data); // done, pass test

int Cell_devParam_replaceSR_port(char* data); // done, pass test

int Cell_devParam_replacePushMail_ServerName(char* data); // done, pass test

int Cell_devParam_replacePushMail_ServerURL(char* data); // done, pass test

int Cell_devParam_replaceBookmark_Name(char* data);

int Cell_devParam_replaceBookmark_URL(char* data);

int Cell_devParam_replaceStreaming_ServerURL(char* data);