Develop > Service Infrastructure > DDR Server
DDR Server
DDR(Device Description Repository)
In the mobile web service market, exchanging terminal information through standardized information is an important issue and a task to diverse users, service providers and contents providers. In particular, contents providers are provided of characteristics information on diverse handsets through handset information DB and based on the provided information, providers offer optimized contents by tailoring to various characteristics by handsets. As the above image, contents providers provide contents irrelevant with handset characteristics in case they are unaware of handset information, therefore, it is difficult for them to provide an optimized service. Handset information storage is an infrastructure designed to save and provide handset information to resolve these problems.
System Composition
[Mobile Device & Browser]
User handset device using mobile web service, mobile handsets (mobile phone, smart phone, PDA, PMP, Navigation, Wibro handsets) supporting mobile web (including full browsing) services
[Mobile Network]
Wireless network access environment used to access mobile web from various mobile handsets and is a wireless network environment that is accessed through mobile communication provider such as CDMA, WCDMA, Wibro, WIFI, WLAN or ISP Gateway.
[Contents Server]
A mobile web server established by contents provider as a mobile web contents providing server. When there is a request for mobile web contents at the contents providing server, request for mobile handset information at DDR(Device Description Repository) server by using various protocols based on access information and then acquire and analyze handset information and provide an optimized contents to user mobile handset.
[DDR(Device Description Repository) server]
Has handset information fitting mobile web 2.0 forum standard [MW2.SD-0007 handset information language requirements] and [MW2.SD-0008 handset information language statement], and provides handset information by using URI or handset information API. The standard for handset information API follows mobile web 2.0 forum standard [MW2.SD-0014 handset repository information API], [MW2.SD-0015 handset information repository requirements], [MW2.SD-0016 handset information key words] standards.
Scenario
i. Request for mobile web contents
The mobile web user requests for contents through mobile web contents providing server. (access browser)
ii. handset access information analysis
In the mobile web contents providing service, use mobile handset access HTTP Request Header information and check mobile handset’s handset information repository location.
Handset access information example)
[case.1] mobile OK expansion browser installed handset (LG-LH2300)
| Server Variable | Value |
|---|---|
| HTTP_ACCEPT | image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* |
| HTTP_ACCEPT_LANGUAGE | ko |
| HTTP_USER_AGENT | Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;800*480;POLARIS 6.0;em1.0;lgtelecom;EB10-20081201-706240714;LG-LH2300W;0) |
| HTTP_PROFILE | http://ddr.mobileok.kr/profile/DeviceProfile.do?mn=LG-LH2300 |
[case.2] mobile OK expansion browser non-installed handset (LG-LH2300)
| Server Variable | Value |
|---|---|
| HTTP_ACCEPT | image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* |
| HTTP_ACCEPT_LANGUAGE | ko |
| HTTP_USER_AGENT | Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;800*480;POLARIS 6.0;em1.0;lgtelecom;EB10-20081201-706240714;LG-LH2300W;0) |
iii. handset information request
Request for handset information using handset information URI or DDR API according to HTTP Request Header information.
In case of [case.1] at the handset access information analysis phase, HTTP_PROFILE header exists.
As the URI stipulated at HTTP_PROFILE is a handset information repository URI that includes corresponding handset information, if there is header value in HTTP_PROFILE, request handset information to corresponding URI.
예) HTTP_PROFILE : http://ddr.mobileok.kr/profile/DeviceProfile.do?mn=LG-LH2300
[case.2] Where there isn’t HTTP_PROFILE header
In case of [case.2] at the handset access information analysis phase, HTTP_PROFILE header does not exist.
In case of the PROFILE(HTTP_PROFILE) header of HTTP Request Header does not exist, use USER-AGENT(HTTP_USER_AGENT) Header information to request handset information to handset information repository.
ex) deliver via parameter USER-AGENT information to handset information repository location and request handset information
http://ddr.mobileok.kr/profile/DeviceProfile.do?ua=Mozilla/4.0%20(compatible;%20MSIE%206.0;%20Windows%20NT%205.0;800*480;POLARIS%206.0;em1.0;lgtelecom;EB10-20081201-706240714;LG-LH2300W;0)
iv. Handset information analysis
When providing handset information of URI providing type, the response to RDF type XML file. Therefore, set value to optimize mobile web contenst by extracting desired handset information by parsing the corresponding XML file.
Handset information composition element and attributes
| Large category | Description |
|---|---|
| HardwarePlatform |
Hardware characteristics information (BluetoothProfile, BitsPerPixel, ColorCapable etc) |
| SoftwarePlatform |
s/w characteristics information (CcppAccept, CcppAccept-Charset etc) |
| BrowserUA |
Browser related characteristics information (BrowserName, BrowserVersion, CcppAccept etc) |
| NetworkCharacteristics |
Network related characteristics information (CurrentBearerService, SecuritySupport etc) |
The definition of detail attributes, refer to [MW2.SD-0008 handset information language statement] standard
v. Contents Optimization
Optimized contents based on extracted handset information by analyzing provided handset information. For example, process to optimize the contents such as by differentiating image size according to LCD horizontal and vertical size of mobile handset, controlling font size, and processing UI according to whether the script is going to be used.
vi. Contents provision
Provide optimized contents to mobile web users.
