KR20100003537A - System and method for extracting information from a mobile device by a web page that is being executed on the mobile device and control method thereof - Google Patents

System and method for extracting information from a mobile device by a web page that is being executed on the mobile device and control method thereof Download PDF

Info

Publication number
KR20100003537A
KR20100003537A KR1020080063474A KR20080063474A KR20100003537A KR 20100003537 A KR20100003537 A KR 20100003537A KR 1020080063474 A KR1020080063474 A KR 1020080063474A KR 20080063474 A KR20080063474 A KR 20080063474A KR 20100003537 A KR20100003537 A KR 20100003537A
Authority
KR
South Korea
Prior art keywords
mobile device
web page
information
web
web browser
Prior art date
Application number
KR1020080063474A
Other languages
Korean (ko)
Inventor
심재범
Original Assignee
주식회사 로직플랜트
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 로직플랜트 filed Critical 주식회사 로직플랜트
Priority to KR1020080063474A priority Critical patent/KR20100003537A/en
Priority to PCT/KR2009/003205 priority patent/WO2010002124A2/en
Publication of KR20100003537A publication Critical patent/KR20100003537A/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The present invention relates to a system for providing a method for extracting information of a mobile device from a web page executed on the mobile device and a control method thereof.

The present invention system displays a web page received from a web server on the output device, a mobile device that allows the web page to extract the information of the device, and transmits the web page to the mobile device, the web page on the mobile device It consists of a web server that can receive the extracted information, the mobile device and the web server is connected to each other by a network.

According to the present invention, the web page displayed on the mobile device can extract and use the information of the mobile device and transmit it to the web server, thereby enabling a web service specialized for the mobile device.

Description

System and method for extracting information from a mobile device by a web page that is being executed on the mobile device and control method about}

The present invention relates to a system for providing a method of extracting information of a mobile device from a web page executed on a mobile device, and a method of controlling the same, wherein the information of the mobile device is extracted from a web page and transmitted to the web server. The present invention relates to a system and method for providing a web service specialized for a mobile device.

As mobile devices including mobile phones are widely used and their performance has improved, web browsing on mobile devices has emerged as an important service. In recent years, 'full browsing', which refers to the same level of web browsing as PCs, has attracted attention.

Full-browser mobile devices can process web pages for traditional PCs as they would on a PC and display them on the output device. Thus, a web service provider can build a service for a mobile user using only existing website building technology for a PC without investing in a new technology. In addition, since a web page for an existing PC can be used as it is, basic services that are not specialized for mobile can be provided without any additional effort. Further, if necessary, the web server may detect characteristics of a web browser for a mobile device, and may provide content of some pages to be customized for a user using the mobile device.

Here, one of the ways that the web server can detect the characteristics of the web browser for mobile devices is a method in which the web server checks user agent information, which is one of header information transmitted when the web browser requests a web page from the web server. have. The user agent information specifies the characteristics of the web browser, such as the name of a compatible popular web browser and the name of the operating system currently running, so that the web server determines whether the web browser is for a mobile device based on the information. can do.

As such, a web service provider can use a web technology for a PC due to the full browsing technology, and create a web page specialized for a mobile user when necessary.

However, there are currently limitations to specializing in mobile users. In order to find out its limitations, we first need to categorize services specific to mobile users. Each type of service is:

First, show what mobile users are interested in. For example, it may show advertisements of the latest mobile phones or PMPs.

Second, provide a service to download programs or music files that can be used on mobile devices. For example, there is a service that downloads mobile games or mobile phone ringtones.

Third, using the current information of the mobile device to provide a service that is appropriate to the situation indicated by the information. For example, if you search for a restaurant, you can use a location-based service to show restaurants that are close to your mobile device's current location.

Of these, only the first service type can be provided by the above method of detecting the characteristics of the web browser. In order to provide the second and third types of services, it is not enough to simply detect whether the web browser is for a mobile device in the web server, and the web page needs to access the operating system or system of the mobile device.

In the case of the second service type, in addition to the file download function generally available in a web service, a function of properly storing and registering a downloaded file in a storage that a mobile phone can recognize as a program or a ringtone is required. This feature is currently implemented by calling an external function from the mobile operator's WAP page. For example, a WAP browser can provide special handling of a particular protocol's URL, so that when a user clicks or otherwise activates a link that specifies that protocol's URL, the URL instead of going to that URL's page There is a way to perform the function specified in. An example of this method is as follows.

<option onpick = "device: jam? url = http: //111.222.333.444/mobile/dn.jad"> Download </ option>

This example is part of the WAP page code. Selecting this item in the option field causes the download to run. The name of the special protocol is 'device'.

Another example is to call a function on a special object provided by the WAP browser from a script in a WAP page. An example of this method is as follows.

function runProgram ()

{

External.run ("http://111.222.333.444/download.wml");

}

This example is part of the WAP page code. In this case, when a function called run of an external object is called as a measurement URL as a parameter, the program of the URL is downloaded and executed.

As you can see, the second type of service is implemented in such a way that the web page simply invokes an external function, since the service result has no impact on the web page again and only needs to be performed and terminated. The web page does not need to retrieve information from the mobile device. All tasks related to the information of the mobile device can be performed in an external function.

The third type of service is when a web page interacts with a mobile device. To implement a third type of service, for example, for a nearby restaurant show service, a web page extracts location information from a mobile device and sends it to a web server to generate an appropriate web page, or run a client script to It is necessary to change the web page on the mobile device. Since the location information has a relatively small amount of data, the location information may be transmitted in addition to the user agent information. The same is true for phone numbers. However, since these pieces of information are personally identifiable information of the user, it is not desirable to transmit them without the user's permission to a website that does not require them. Therefore, it would be desirable to have a method for extracting with the permission of the user when the web page explicitly requests it.

This patent relates to the third type of service.

Third, since the service type uses the current information of the mobile device, the service type can be more specialized in the current situation of the mobile user than the other two service types, and thus has great value.

Third, in order to provide a service type in a web page, a method of extracting mobile device information from a web page should be provided. In addition, the method may have a characteristic that can be applied regardless of a model or a specification of a mobile device. In addition, in order to support a web browser of a PC, a web browser of a mobile device that implements the above method, and a web browser of a mobile device that does not implement the above method in one web page, each web browser has a corresponding function, that is, mobile It would be desirable to be able to dynamically check on a web page whether it supports the ability to extract device information.

However, the above method for the third service type is not currently provided. If such a function is devised and provided, the web service provider will be able to provide various services specialized for the customers of the mobile environment.

The present invention is to solve the above problems of the prior art, an object of the present invention is to provide a system and a control method for providing a method for extracting information of a mobile device from a web page displayed on the mobile device. .

A system for providing a method for extracting information of a mobile device from a web page running on a mobile device according to the present invention for achieving the above object, the mobile device receiving a web page from a web server, the mobile device and the network It is connected and possible to communicate with each other, and comprises a web server for transmitting a web page to the mobile device, the web page is characterized in that it includes a function for extracting information of the mobile device.

At this time, the extraction of the information on the mobile device from the web page, the script included in the web page, may be performed using a mobile device information extraction object or API provided by the web browser.

In addition, the extraction of the information about the mobile device from the web page may be performed by the extension module included in the web page using a mobile device information extraction API.

The web server preferably receives information extracted by the web page from the mobile device.

Meanwhile, a method of extracting information of a mobile device from a web page executed in a mobile device having a mobile device and a web server connected to a network according to the present invention for achieving the above object, the mobile device Requesting, by a web browser of the web server, a web page including a script from the web server; A second step of the web server transmitting the web page including the script to the web browser; A third step of analyzing the web page received by the web browser and executing a script in the web page; A fourth step of the executed script requesting information of the mobile device from a web browser; A fifth step of the web browser calling a corresponding mobile device information extraction system API; A sixth step of extracting, by the mobile device information extraction system API information of the mobile device, a web browser; A seventh step of transmitting the received information from the web browser to the script; It is configured to include.

In this case, when the script is not directly included in the web page, the third step may include analyzing the web page to extract a reference to the script in the web page; Requesting a script that exists at the location pointed to by the reference; Receiving and executing the requested script; It is preferable to further include.

The fifth step may include: determining, by the web browser, whether to permit the information request of the mobile device; Calling the mobile device information extraction system API by the web browser when the request for information of the mobile device is permitted as a result of the determination; It may be configured to include more.

In addition, the determination of whether to permit the information request of the mobile device is preferably performed by a method in which the web browser queries a user through a user interface or reads configuration information stored in a storage device of the mobile device.

Meanwhile, another method of extracting information of a mobile device from a web page executed in the mobile device, comprising a mobile device connected to a network according to the present invention and a web server for achieving the above object, and a web server, are described above. Requesting, by a web browser of a mobile device, a web page including an extension module from a web server; Transmitting, by the web server, the web page including the extension module to the web browser; A third step of analyzing a web page received by the web browser and executing an extension module in the web page; A fourth step of executing the extension module calling a mobile device information extraction system API; A fifth step of extracting, by the mobile device information extraction system API, the mobile device information to the expansion module; Characterized in that it comprises a.

In this case, when the extension module is not directly included in the web page, the third step may include analyzing the web page and extracting a reference to the extension module in the web page; Requesting an extension module present at the location indicated by the reference; Receiving and executing the requested extension module; It is preferable to further include.

Meanwhile, the third step may include analyzing a web page transmitted from the web browser and determining whether to permit execution of an extension module in the web page; Executing the extension module in the web page if the execution of the extension module is permitted; It is preferable to further include.

In this case, the determination of whether to execute the extension module in the web page may be performed by the web browser asking a user through a user interface or reading configuration information stored in a storage device of the mobile device.

The method may further include the step of canceling execution of the extension module by the web browser when the request for information of the mobile device is not permitted.

Meanwhile, before the web browser or the extension module calls the mobile device information extraction system API, the web browser or the extension module may be configured to query the mobile device whether it is possible to extract information on the mobile device. have.

According to the present invention, the web page displayed on the mobile device can extract and use the information of the mobile device and transmit it to the web server, thereby enabling a web service specialized for the mobile device.

There are two ways that can be implemented in a mobile device to achieve the object of the present invention.

First, a web browser provides an object or API that can be accessed from a script embedded in a web page.

Second, the web browser supports the execution of extension modules directly and indirectly included in the web page, and the mobile device directly through the API provided by the runtime that governs the execution of the system API provided by the mobile device or the extension module. How to access information Here, the extension module is a function related to execution any more than a web browser starts the module, such as a binary program module in which the CPU of the mobile device directly executes instructions, or an intermediate code program module executable in a runtime such as Java. There is no need to provide an API, it is a module that directly uses the API provided by the system API or runtime.

The control method of the present invention is different for each implementation method described above.

The control method of the first implementation method includes the steps of requesting a web page from a web browser of a mobile device, sending a web page from the web server to the mobile device, analyzing the web page by the web browser of the mobile device, The web browser of the mobile device executing a script embedded in the web page, the script executed by the web browser of the mobile device detecting the presence of the mobile device information access object or API provided by the web browser, the script Using the browser's mobile device information access object or API, and the script using the web browser's mobile device information access object or API to change the content of the web page or sending the result to the web server, to the web server. If a result is sent, the web server receives and processes the result. It includes.

The control method of the second implementation method includes the steps of requesting a web page from a web browser of a mobile device, sending a web page from the web server to the mobile device, analyzing the web page by the web browser of the mobile device, The web browser of the mobile device extracts the extension module from the web page, executes the extracted extension module, and uses the API provided by the runtime that governs the execution of the system API provided by the mobile device or the extension module execution. Performing the steps of changing the web page content or transmitting the result to the web server using the result of using the API, and if the result is sent to the web server, receiving and processing the result. Include.

In the second implementation, the extension module is not directly included in the web page, and in most cases, the web page contains only the reference information of the extension module. It further includes the step of requesting and receiving from the web server.

In addition, in the second implementation method, since an extension module can use all the APIs provided by the system without restriction, an additional step of confirming whether the web browser is executed by the user before executing the extension module is included. Is preferred.

In both implementations, extracting information from a mobile device can lead to the leakage of user personal information, so if an object or API is used to extract information from the mobile device, ask the user if they are allowed to use it immediately before it is used. Preferably, the receiving step is further included. In the first implementation method, since the execution of the object or API is controlled by the web browser, the verification process can be implemented at the web browser level. In the second implementation method, the executable module can directly execute the system API without the intervention of the web browser. However, you can use the runtime APIs, so you must provide the appropriate verification at the system or runtime level.

The first implementation has the following advantages:

First, since the script does not have direct access to the system and the mobile device information access object or API is entirely under the control of the web browser, it is easy to ensure the stability and security of the device.

Second, scripts can be executed on all mobile devices that support the execution of the script grammar, regardless of binary compatibility according to the CPU or system API of the mobile device. Is possible.

Third, script coding is less difficult and costly than extension module development.

On the other hand, since the execution of the script in the web browser to support, there is a disadvantage that the program size of the web browser increases, or require a high-end device.

The second implementation has the advantages and disadvantages of the first older approach. However, extension modules that run on the runtime such as Java have fewer problems with the stability and security of mobile devices, models, and specifications than binary program modules. However, compatibility issues between the Java runtimes still exist.

Hereinafter, with reference to the drawings will be described the present invention in more detail.

1 and 2 are views for explaining the configuration of a system according to an embodiment of the present invention.

First, FIG. 1 is a diagram for explaining a first implementation method, that is, a method using a script, of a system according to an embodiment of the present invention.

Referring to FIG. 1, the system includes a web server 100 and a mobile device 300 connected to the web server 100 and a data communication network 200 to communicate with each other.

The web server 100 is installed with the web server software 110 and transmits the web page 120 to the mobile device 300. The web page 120 may include a script 130 that operates on the mobile device 300 and extracts information of the mobile device 300.

The mobile device 300 is provided with a web browser 310, receives the web page 120 from the web server 100 and outputs it to an output device such as a screen. In addition, the web browser 310 drives the script 130 in the web page 120, and provides a mobile device information extraction object or API 330 to access and use the script 130. The mobile device information extraction object or API 330 delivers the information of the mobile device to the script 130 using the mobile device information extraction system API 320 provided by the mobile device 300 system.

Note that in this diagram, the script 130 does not use the mobile device information extraction system API 320 directly, but rather uses the mobile device information extraction object or API 330 provided by the web browser 310. The execution of the script 130 is controlled by the web browser 320, so that the script 130 cannot directly use the mobile device information extraction system API 320, as well as other system APIs. In this way it is possible to ensure the stability and security of the mobile device (300).

An example of the script 130 included in the web page 120 is as follows.

<script language = "javascript">

<!-

function showLBSInfo ()

{

if (window.mobileInfoGetter == null)

alert ("cannot get LBS info");

else

alert (window.mobileInfoGetter.getLBSInfo ());

}

//->

</ script>

<button onclick = "showLBSInfo ()"> Show LBS info </ button>

In this script, when the button named 'Show LBS info' is pressed, the showLBSInfo () script function is called, and within the function, the window.mobileInfoGetter of the mobile device information extraction object 330 provided by the web browser 310 is called. The API function getLBSInfo () is called to extract LBS information, which is one of the information of the mobile device, and display the result on the screen.

Here, in order to be compatible with a web browser that does not provide the mobile device information extraction object 330, it can be seen whether the window.mobileInfoGetter object exists through comparison with null.

In the above example, the web browser provides mobileInfoGetter as a child object of the window object, a standard Document Object Module (DOM) object that always exists on a web page. The specific way of providing such a DOM object depends on how the web browser is implemented. As some implementations have been published by open source web browser software such as Mozilla or WebKit, they are not described separately.

The implementation of the function of extracting the information of the mobile device in the mobileInfoGetter may vary depending on the mobile device information extraction system API 320 existing for each mobile device, and the operation of different APIs 320 for each mobile device may be consistent with a common object or API ( 330) is the main implementation task. In addition, you can add a function that allows the user to confirm whether the API is allowed when the API is called.

2 is a view for explaining a second implementation method, that is, a method using an extension module, of a system according to an embodiment of the present invention.

FIG. 2 is substantially the same as FIG. 1, except that the extension module 140 exists instead of the script 130, and the extension module 140 directly accesses the mobile device information extraction system API 320 without going through the web browser 310. Use is different. In the case of an intermediate code extension module such as Java, the information extraction system API 320 is present at runtime corresponding to the extension module.

The execution method of the extension module 140 varies depending on a web browser. An example of a typical web browser is an execution of an ActiveX module or a plug-in module. At this time, because of the stability and security risks described above, it is preferable to further include a step of confirming to the user whether to execute before the extension module.

An example of including the extension module 140 in the web page 120 is as follows. Here is an example of including an ActiveX module.

<OBJECT

ID = "MobileServiceObj"

classid = "clsid: A21FE9D5-2FF6-4CE9-8595-4D02BCDE3FF1">

</ OBJECT>

This example includes an extension module 140 called MobileServiceObj. This method is used by Microsoft Internet Explorer, and uses a separate method for other web browsers. The expansion module 140 included as described above is executed at the time of outputting a web page to a screen and other output devices, and then the expansion module 140 operates while using the system API itself.

3 and 4 are message sequence charts provided in the description of the method of operation of the system in one embodiment of the present invention.

First, FIG. 3 is a message sequence chart for explaining an operation process of the first implementation method, that is, a method using a script, of a system according to an embodiment of the present invention.

Referring to FIG. 3, the web browser 310 of the mobile device 300 requests the web server 100 including the script from the web server 100 (S100). The web server 100 transmits the web page 120 including the script to the web browser 310 of the mobile device 300 (S105). The web browser 310 analyzes the web page 120 (S110) and outputs it to the screen or other output device of the mobile device 300 (S115), and executes the script 130 in the web page 120 (S115). S120).

The executed script 130 requests information of the mobile device from the web browser 310 when necessary (S125). The web browser 310 requests the information by calling the corresponding mobile device information extraction system API (320) (S130). The mobile device information extraction system API 320 extracts the corresponding mobile device information (S135) and delivers it to the web browser 310 (S140). The web browser 310 delivers the received information to the script 130 (S145). The script 130 performs a process related to the received mobile device information (S150).

Here, before the web browser 310 calls the mobile device information extraction system API 320, the web browser 310 may request a user for permission to extract the information by using a user interface such as a dialog. In this case, the script will return an error result if the user does not allow it.

4 is a message sequence chart for explaining an operation process of the second implementation method, that is, a method using an extension module, of a system according to an embodiment of the present invention.

Referring to FIG. 4, the web browser 310 of the mobile device 300 requests the web server 100 including the extension module to the web server 100 (S100). The web server 100 transmits the web page 120 including the extension module to the web browser 310 of the mobile device 300 (S105). The web browser 310 analyzes the web page 120 (S110) and outputs the screen or other output device of the mobile device 300 (S115) to execute the expansion module 140 in the web page 120. (S120).

When executed, the expansion module 140 calls for the mobile device information extraction system API 320 to request information (S125). The mobile device information extraction system API 320 extracts the corresponding mobile device information (S130) and delivers it to the expansion module 140 (S1135). The expansion module 140 performs a process related to the received mobile device information (S150).

Here, the extension module 140 is not included directly in the web page 120, unlike the script 130, and the extension module 140 is not included in the web page 120, as in the above example including the extension module 140. Indirectly included by specifying an identifier or reference address. Therefore, in this case, the web browser 310 receives the web page 120 and then receives the expansion module 140 separately.

In addition, before executing the extension module 140, the web browser 310 may request a user to execute the extension module 140 by using a user interface such as a dialog. In this case, unless the user permits, the expansion module 140 is not executed.

Execution of the extension module 140 reads a dynamically loadable extension module file from a storage device received from a server and stores the extension module 140 in a manner defined at the system software level of the mobile device 300. This is done by the web browser 310 finding and calling a function address.

For reference, FIGS. 3 and 4, it can be seen that the main difference between the two implementation methods lies in the mobile device information extraction method of the script 130 and the extension module 140.

Examples of the information of the mobile device that can be extracted by the above method, and an advantage of when the information can be extracted, in addition to the above-described location information (LBS) are the following.

First, phone number. The user is not inconvenient to input directly to the sign-up form, etc., and the web site has the advantage that the user can obtain a real phone number instead of a fake.

Second, the phone book. It's a convenient way to choose a phone number when you're sending text messages or making phone calls.

Third, electronic commerce information such as a certificate. E-commerce can be done through web pages on mobile devices.

Fourth, camera and photography. You can upload a photo stored in the repository, or take a new photo and immediately upload it by the web page command.

Fifth, text message. When providing a text message transmission function, it is possible to provide various text message functions such as selecting, editing, and resending previous texts.

Sixth, the video. You can upload the video you've shot, or upload a new video instantly by ordering it from a web page. If you provide a storage function, you can even download videos.

Seventh, music, ringtones, desktop data. When providing a storage function, the second service type can be implemented.

Eighth, files in other storage. You can upload a file stored on your mobile device to your website. If you provide a storage function, you can even download a random file.

Ninth, cell phone's current signal strength. It is useful for checking the normal operation of a mobile phone.

When the information of various mobile devices can be extracted and controlled from the web page as described above, the user interface of the mobile device can be produced by using the web page. Only the functions provided by the patent system will be able to produce a common.

In addition, if the above method of extracting mobile device information is standardized among the main web browsers, various functions of the mobile device can be provided through a web page regardless of the type of web browser installed in the mobile device. A browser-independent open service framework will be built.

In addition, in the above extraction method, there may be some information that cannot be extracted depending on the mobile device. Therefore, by providing a method of knowing whether or not the information can be extracted for each type, the web page may properly display the screen content according to the information. It can be configured to be adjustable. For example, if a device does not have a camera, the web browser object has a function called 'IsCameraAvailable', and if you call that function, it returns that there is no camera. It can be configured not to appear on the screen.

In addition, it may provide a service for synchronizing the information of the mobile device with information stored in another storage, for example, a website or a personal cup computer, via the Internet.

While the above has been shown and described with respect to preferred embodiments of the present invention, the present invention is not limited to the specific embodiments described above, it is usually in the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

1 is a view for explaining the first implementation method, that is, a method using a script, of the system configuration according to an embodiment of the present invention.

2 is a view for explaining a second implementation method, that is, a method using an extension module, of a system according to an embodiment of the present invention.

3 is a message sequence chart for explaining an operation process of the first implementation method, that is, a method using a script, of a system according to an embodiment of the present invention.

4 is a message sequence chart illustrating an operation process of the second implementation method, that is, the method using an extension module, of the system according to an embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

100: Web Server 120: Web Pages

130: Script 140: Extension Module

300: mobile device 310: web browser

Claims (14)

A mobile device that receives web pages from a web server, A web server connected to the mobile device through a network and communicating with each other, and transmitting a web page to the mobile device, The web page includes a function for extracting the information of the mobile device, the system for providing a method for extracting information of the mobile device from the web page running on the mobile device. The method of claim 1, Extracting information about the mobile device from the web page, The script included in the web page is performed using a mobile device information extraction object or API provided by the web browser, providing a method for extracting information of the mobile device from the web page running on the mobile device System. The method of claim 1, Extracting information about the mobile device from the web page, The extension module included in the web page is performed by using a mobile device information extraction API, the system for providing a method for extracting the information of the mobile device from the web page running on the mobile device. The method of claim 1, The web server is a system for providing a method for extracting information of a mobile device from a web page running on a mobile device, characterized in that the web page receives the information extracted from the mobile device. A method for extracting information of a mobile device from a web page executed on the mobile device, comprising a mobile device and a web server connected to a network and capable of mutual communication, A first step of the web browser of the mobile device requesting a web server including a script from the web server; A second step of the web server transmitting the web page including the script to the web browser; A third step of analyzing the web page received by the web browser and executing a script in the web page; A fourth step of the executed script requesting information of the mobile device from a web browser; A fifth step of the web browser calling a corresponding mobile device information extraction system API; A sixth step of extracting, by the mobile device information extraction system API information of the mobile device, a web browser; A seventh step of transmitting the received information from the web browser to the script; Method for extracting information of the mobile device from a web page running on the mobile device, comprising a. A method for extracting information of a mobile device from a web page executed in a mobile device, comprising a mobile device connected to a network and capable of mutual communication, and a web server, Requesting, by a web browser of the mobile device, a web page including an extension module from a web server; Transmitting, by the web server, the web page including the extension module to the web browser; A third step of analyzing a web page received by the web browser and executing an extension module in the web page; A fourth step of executing the extension module calling a mobile device information extraction system API; A fifth step of extracting, by the mobile device information extraction system API, the mobile device information to the expansion module; Method for extracting information of the mobile device from a web page running on the mobile device, comprising a. The method according to claim 5 or 6, If the script or the extension module is not directly included in the web page, the third step is Analyzing the web page to extract a reference to the script or the extension module in the web page; Requesting a script or extension module that exists at the location pointed to by the reference; Receiving and executing the requested script or extension module; Method for extracting information of the mobile device from a web page running on the mobile device, characterized in that it further comprises. The method of claim 5, The fifth step, Determining, by the web browser, whether to permit the information request of the mobile device; Calling the mobile device information extraction system API by the web browser when the request for information of the mobile device is permitted as a result of the determination; Method for extracting information of the mobile device from a web page running on the mobile device, comprising a. The method of claim 8, The determination of whether to permit the information request of the mobile device, The web browser extracts information of the mobile device from a web page executed in the mobile device, characterized in that the web browser is executed by querying a user through a user interface or reading configuration information stored in a storage device of the mobile device. How to. The method of claim 6, The third step, Analyzing, by the web browser, the received web page and determining whether to permit execution of the extension module in the web page; Executing the extension module in the web page if the execution of the extension module is permitted; Method for extracting information of the mobile device from a web page running on the mobile device, characterized in that it further comprises. The method of claim 10, Determination of permission to run the extension module in the web page, The web browser extracts information of the mobile device from a web page executed in the mobile device, characterized in that the web browser is executed by querying a user through a user interface or reading configuration information stored in a storage device of the mobile device. How to. The method of claim 10, If the request for the information of the mobile device is not permitted, the web browser further comprises the step of canceling the execution of the extension module. How to extract it. The method of claim 5, Before performing step 5, And the web browser queries the mobile device whether it is possible to extract information of the mobile device, from the web page executed in the mobile device. The method of claim 6, Before performing step 4, And the extension module queries the mobile device whether it is possible to extract the information of the mobile device, from the web page executed in the mobile device.
KR1020080063474A 2008-07-01 2008-07-01 System and method for extracting information from a mobile device by a web page that is being executed on the mobile device and control method thereof KR20100003537A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020080063474A KR20100003537A (en) 2008-07-01 2008-07-01 System and method for extracting information from a mobile device by a web page that is being executed on the mobile device and control method thereof
PCT/KR2009/003205 WO2010002124A2 (en) 2008-07-01 2009-06-16 System that provides method for extracting mobile device information from webpage loaded in mobile device and control method thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020080063474A KR20100003537A (en) 2008-07-01 2008-07-01 System and method for extracting information from a mobile device by a web page that is being executed on the mobile device and control method thereof

Publications (1)

Publication Number Publication Date
KR20100003537A true KR20100003537A (en) 2010-01-11

Family

ID=41466420

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020080063474A KR20100003537A (en) 2008-07-01 2008-07-01 System and method for extracting information from a mobile device by a web page that is being executed on the mobile device and control method thereof

Country Status (2)

Country Link
KR (1) KR20100003537A (en)
WO (1) WO2010002124A2 (en)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7249100B2 (en) * 2001-05-15 2007-07-24 Nokia Corporation Service discovery access to user location
KR100461019B1 (en) * 2002-11-01 2004-12-09 한국전자통신연구원 web contents transcoding system and method for small display devices
KR100679033B1 (en) * 2005-01-24 2007-02-06 삼성전자주식회사 Apparatus and method for offering script for mobile terminal
US7814410B2 (en) * 2005-09-12 2010-10-12 Workman Nydegger Initial server-side content rendering for client-script web pages

Also Published As

Publication number Publication date
WO2010002124A3 (en) 2010-03-25
WO2010002124A2 (en) 2010-01-07

Similar Documents

Publication Publication Date Title
US8595186B1 (en) System and method for building and delivering mobile widgets
US8458612B2 (en) Application management framework for web applications
JP6219296B2 (en) Launching an application from a web page
EP2962216B1 (en) Sharing application states
US8620995B2 (en) Method, computer program, transcoding server and computer system for modifying a digital document
US8910115B2 (en) Systems and methods for application development
EP2806357A1 (en) Method and communication device for updating a web application
US9690761B1 (en) Systems and methods for providing mobile browser access to mobile device functionalities
US20100093396A1 (en) Systems and methods for storing or performing functions within removable memory, such as a subscriber identity module of a mobile device
US7987243B2 (en) Method for media discovery
US8271611B2 (en) Method and system of invoking MIDlets from a web browser on a local device
WO2013097592A1 (en) Script loading technology
US20140282032A1 (en) Dynamically configuring user experiences with action uniform resource identifiers
CN104965848A (en) Front-end resource loading method and apparatus
WO2010111147A2 (en) Input content to application via web browser
JP2017504912A (en) Page operation processing method and apparatus, and terminal
WO2011095108A1 (en) Dynamic display method for application program interface and device thereof
KR20110088274A (en) Apparatus for providing terminal web service and method thereof
WO2015027855A1 (en) Two-dimensional code-based website link processing method, apparatus and system
KR100749845B1 (en) Mobile system having features of mobile active page and method for mobile internet service thereof
US9292321B2 (en) System, method and computer-readable recording medium for synchronous script lazy loading
US20220292141A1 (en) Quick Application Startup Method and Related Apparatus
JP2008537202A (en) A device-independent addressing system that accesses web pages via public mobile networks
WO2009020973A1 (en) System and methods for selecting advertisements based on caller identifier information
KR101712138B1 (en) System and method for file control using user server

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E601 Decision to refuse application