WO2014040489A1

WO2014040489A1 - Method and apparatus for uploading a file

Info

Publication number: WO2014040489A1
Application number: PCT/CN2013/082266
Authority: WO
Inventors: Tao CAO; Jie Hou; Ningjun DOU; Ming He; Xuhui LV
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2012-09-12
Filing date: 2013-08-26
Publication date: 2014-03-20
Anticipated expiration: 2015-03-12
Also published as: SG11201501077QA; CN103685379B; CN103685379A; MY175280A

Description

METHOD AND APPARATUS FOR UPLOADING A FILE

CROS S-REFERENCES TO RELATED APPLICATIONS

[0001] This application claims priority to Chinese Patent Application No.

CN201210335644.7, filed on September 12, 2012, the entire contents of which are incorporated herein by reference.

FIELD OF THE DISCLOSURE

[0002] The present disclosure relates to the field of Internet technology and, more particularly, relates to methods and apparatus for uploading a file based on a webkit kernel browser.

BACKGROUND

[0003] An iOS operating apparatus is an apparatus operated by handheld devices and developed by Apple Inc. The iOS and Mac OS X operating apparatus are based on Darwin, which is an open-source operating system published by Apple Inc. in year 2000. The iOS and Mac OS X operating systems are commercial operating systems that are Unix-like. Webkit is an open source browser kernel. Webkit is used as the browser kernel of iOS apparatus. The Webkit kernel has a clear source code structure and a rapid rendering speed.

[0004] Currently, the iOS operating apparatus covers a great share in the global smart phone market and in the U.S. smart phone market. As a mobile terminal browser, the user may access mailbox, microblogs, and websites at any time, and file-uploading has become a desired feature. However, the webkit kernel browser of the iOS operating apparatus does not have a file-uploading function. The iOS operating apparatus restricts application programs to access local file systems. In webkit-based browsers (i.e., webkit kernel browsers) for an input tab having the type of "file" on the webpage, the user cannot click on the image of the local file system to upload the file.

BRIEF SUMMARY OF THE DISCLOSURE

[0005] According to various embodiments, the present disclosure provides a method for uploading a file based on a webkit kernel browser by using a UlWebView control in the webkit kernel browser to monitor a url request. The url request can be linked with a triggering button related to a file for uploading on a webpage. It is then determined whether the url request monitored by the UlWebView control contains an agreed protocol header. When it is determined that the url request contains the agreed protocol header, the file for uploading is received and uploaded. When it is determined that the url request does not contain the agreed protocol header, the file for uploading is not uploaded.

[0006] According to various embodiments, there is also provided an apparatus for uploading a file based on a webkit kernel browser. The apparatus can include a monitoring module, and a determination executing module. The monitoring module can be configured to use a UlWebView control in the webkit kernel browser to monitor a url request. The url request can be linked with a triggering button related to a file for uploading on a webpage. The determination executing module can be configured to determine whether the url request monitored by the UlWebView control contains an agreed protocol header. When the url request is determined that contains the agreed protocol header, the file for uploading is received and uploaded. When it is determined that the url request does not contain the agreed protocol header, the file for uploading is not uploaded.

[0007] Other aspects or embodiments of the present disclosure can be understood by those skilled in the art in light of the description, the claims, and the drawings of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The following drawings are merely examples for illustrative purposes according to various disclosed embodiments and are not intended to limit the scope of the present disclosure.

[0009] FIG. 1 depicts an exemplary method for uploading a file in accordance with various embodiments;

[0010] FIG. 2 depicts another exemplary method for uploading a file in accordance with various embodiments;

[0011] FIG. 3 depicts exemplary upload code in accordance with various embodiments;

[0012] FIG. 4 depicts an exemplary apparatus for uploading a file in accordance with various embodiments;

[0013] FIG. 5 depicts another exemplary apparatus for uploading a file in accordance with various embodiments;

[0014] FIG. 6 depicts an exemplary environment incorporating certain disclosed

embodiments; and

[0015] FIG. 7 depicts an exemplary server consistent with the disclosed embodiments.

DETAILED DES CRIPTION

[0016] Reference will now be made in detail to exemplary embodiments of the disclosure, which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

[0017] FIGS. 1-5 depict exemplary methods and apparatus for uploading a file based on a webkit kernel browser in accordance with various disclosed embodiments. The exemplary methods and apparatus can be implemented, for example, in an exemplary environment 600 as shown in FIG. 6.

[0018] As shown in FIG. 6, the environment 600 can include a server 604, a terminal/client

(hereinafter referred as "terminal") 606, and a communication network 602. The server 604 and the terminal 606 may be coupled through the communication network 602 for information exchange, for example, Internet searching, webpage browsing, etc. Although only one terminal 606 and one server 604 are shown in the environment 600, any number of terminals 606 or servers 604 may be included, and other devices may also be included.

[0019] The communication network 602 may include any appropriate type of communication network for providing network connections to the server 604 and terminal 606 or among multiple servers 604 or terminals 606. For example, the communication network 602 may include the Internet or other types of computer networks or telecommunication networks, either wired or wireless.

[0020] A terminal, as used herein, may refer to any appropriate user terminal device with certain computing capabilities, for example, a personal computer (PC), a work station computer, a notebook computer, a car computer (e.g., carrying in a car or other vehicles), a server computer, a hand-held computing device (e.g., a tablet computer), a mobile terminal (e.g., a mobile phone, a smart phone, an iPad, and/or an aPad), a POS (i.e., point of sale) device, or any other user-side computing device. In various embodiments, the terms "terminal" and "terminal device" can be used interchangeably. In various embodiments, the terminal 606 can include a browser such as a webkit kernel browser.

[0021] A server, as used herein, may refer one or more server computers configured to provide certain server functionalities, for example, search engines and database management. A server may also include one or more processors to execute computer programs in parallel. [0022] The server 604 and the terminal 606 may be implemented on any appropriate computing platform. FIG. 7 shows a block diagram of an exemplary computing system 700 capable of implementing the server 604 and/or the terminal 606. As shown in FIG. 7,

[0023] the exemplary computer system 700 may include a processor 702, a storage medium

704, a monitor 706, a communication module 708, a database 710, peripherals 712, and one or more bus 714 to couple the devices together. Certain devices may be omitted and other devices may be included.

[0024] The processor 702 can include any appropriate processor or processors. Further, the processor 702 can include multiple cores for multi-thread or parallel processing. The storage medium 704 may include memory modules, for example, ROM, RAM, and flash memory modules, and mass storages, for example, CD-ROM, U-disk, removable hard disk, etc. The storage medium 704 may store computer programs for implementing various processes, when executed by the processor 702.

[0025] Further, the peripherals 712 may include I/O devices, for example, keyboard and mouse, and the communication module 708 may include network devices for establishing connections through the communication network 602. The database 710 may include one or more databases for storing certain data and for performing certain operations on the stored data, for example, webpage browsing, database searching, etc.

[0026] In operation, the terminal 606 may cause the server 604 to perform certain actions, for example, an Internet search or other database operations. The server 604 may be configured to provide structures and functions for such actions and operations. More particularly, the server 604 may include a data searching system for real-time database searching. In various embodiments, a terminal, for example, a mobile terminal involved in the disclosed methods and systems can include the terminal 606. [0027] FIG. 1 depicts an exemplary method for uploading a file in accordance with various embodiments. The exemplary method for uploading the file can be based on a webkit kernel browser.

[0028] In Step S 11 , a UlWebView control in a webkit kernel browser is used to monitor a url request. The url request is linked with a triggering button related to a file for uploading on a webpage.

[0029] In Step S 12, it is determined whether the url request, monitored by the UlWebView control, contains an agreed protocol header. When the url request is determined that contains the agreed protocol header, the file for uploading can be received and uploaded.

[0030] When a user needs to upload a file, the user can first click on the triggering button related to the file for uploading on the webpage, for example, by clicking on buttons of "upload", "browse", etc. In various embodiments, the triggering button related to the file for uploading can be linked with the url request. When the url request monitored by the UlWebView control in the webkit kernel browser contains the agreed protocol header, it is determined that the user triggers a file uploading request. Note that the agreed protocol header can be pre-set as needed. For example, the agreed protocol header can be pre-set to be http://wbupload or any other suitable protocol headers, without limitation.

[0031] The disclosed methods for uploading a file based on the webkit kernel browser uses a form of a link to replace conventional input tabs. When the triggering button is clicked by the user, the UlWebView control in the webkit kernel browser is triggered to monitor a url request and to determine whether the url request contains the agreed protocol header. When it is determined that the url request contains the agreed protocol header, the file for uploading is received and uploaded. Otherwise, when it is determined that the url request does not contain the agreed protocol header, the file for uploading cannot be uploaded. This may solve the problems that the webkit kernel browser for conventional iOS apparatus cannot upload files.

[0032] FIG. 2 depicts another exemplary method for uploading a file in accordance with various embodiments. The exemplary method for uploading the file can be based on a webkit kernel browser.

[0033] In Step S21, a UlWebView control in a webkit kernel browser is used to monitor a url request. The url request is linked with a triggering button related to a file for uploading on a webpage

[0034] In Step S22, it is determined whether the url request, monitored by the UlWebView control, contains agreed protocol header. When the url request is determined that contains the agreed protocol header, Step S23 (including, e.g., Step 231, Step 232, Step 233, and Step 234) can be performed to receive and upload the file for uploading. Otherwise, when the url request is determined that does not contain the agreed protocol header, the file for uploading cannot be uploaded.

[0035] In Step 231, a file uploading request is received.

[0036] In various embodiments, the url request, linked to the triggering button related to the file for uploading, can be, for example,

http://wbupload://somehost/somepath?som

nc3, where http://wbupload is the agreed protocol header; somehost/somepath?somequery & is a post request url related to file uploading;

http://wbupload://somehost/somepath?som

nc3 is a fixed format with each of fund, func2, and func3 (e.g., js function names with no parentheses) having a specific name delivered depending on a server. [0037] In this case, the UlWebView control can be used to call the fund js function to obtain cookie values used for sending the file uploading request. The obtained cookies can be used to obtain the user's identity and/or other suitable information including, for example, which user is performing the file uploading.

[0038] In Step S232, a file selection box can be generated and popped up for selecting a file.

For example, the UlWebView control can be used to call the func3 js function to obtain a js element object. The client can design own algorithms to calculate a position for the file selection box to point to.

[0039] In Step S233, it is determined whether the file for uploading is selected. When the file for uploading is selected, the selected file for uploading can then be uploaded. After the file is selected and the uploading starts, the client (of the webkit kernel browser) may provide an upload interface. Exemplary upload code is shown in FIG. 3 for illustration purposes. Of course, the present disclosure is not limited thereto.

[0040] In Step S234, after the file uploading, the webpage is displayed.

[0041] In this case, after the file is successfully uploaded, the UlWebView control can be used to call the related func2 js function to display the webpage following the upload of the file. For example, a response body (in a text format) can be used as a parameter of func2 js function. By calculating func2 js function, the webpage can be displayed after the uploading of the file.

[0042] The disclosed methods for uploading a file based on the webkit kernel browser uses a form of a link to replace conventional input tabs. When the triggering button is clicked by the user, the UlWebView control in the webkit kernel browser is triggered to monitor a url request and to determine whether the url request contains the agreed protocol header. When it is determined that the url request contains the agreed protocol header, the file for uploading is received and uploaded. Otherwise, when it is determined that the url request does not contain the agreed protocol header, the file for uploading cannot be uploaded. This may solve the problems that the webkit kernel browser for conventional iOS apparatus cannot upload files.

[0043] FIG. 4 depicts an exemplary apparatus 30 for uploading a file in accordance with various embodiments. The exemplary apparatus for uploading the file can be based on a webkit kernel browser. The exemplary apparatus 30 can include a monitoring module 31 and/or a determination executing module 32.

[0044] The monitoring module 31 can be configured to use a UlWebView control in a webkit kernel browser to monitor a url request linked to a triggering button on a webpage that is related to a file for uploading.

[0045] The determination executing module 32 can be configured to determine whether the url request, monitored by the UlWebView control, contains an agreed protocol header. When the url request is determined that contains the agreed protocol header, the file for uploading can be received and uploaded.

[0046] When a user needs to upload a file, the user can first click on the triggering button related to the file for uploading on the webpage, for example, by clicking on buttons of "upload", "browse", etc. In various embodiments, the triggering button related to the file for uploading can be linked with the url request. When the monitoring module 31 monitors the url request that contains the agreed protocol header, it is determined that the user triggers a file uploading request. Note that the agreed protocol header can be pre-set as needed by a setting module 33. For example, the agreed protocol header can be pre-set to be http://wbupload or any other suitable protocol headers, without limitation.

[0047] The disclosed apparatus for uploading a file based on a webkit kernel browser uses a monitoring module to monitor the url request. The determination executing module is used to determine whether the url request contains the agreed protocol header. When it is determined that the url request contains the agreed protocol header, the file for updating can be received and uploaded. Otherwise, when it is determined that the url request does not contain the agreed protocol header, the file uploading cannot be performed. This solves the problems that the webkit kernel browser for conventional iOS apparatus cannot upload files.

[0048] FIG. 5 depicts an exemplary apparatus 40 for uploading a file in accordance with various embodiments. The exemplary apparatus for uploading the file can be based on a webkit kernel browser. The exemplary apparatus 40 can include a monitoring module 41 and/or a determination executing module 42.

[0049] The monitoring module 41 can be configured to use a UlWebView control in a webkit kernel browser to monitor a url request linked to a triggering button on a webpage that is related to a file for uploading.

[0050] The determination executing module 42 can be configured to determine whether the url request, monitored by the UlWebView control, contains the agreed protocol header. When the url request is determined that contains the agreed protocol header, the file for uploading can be received and uploaded. Otherwise, when the url request is determined that does not contain the agreed protocol header, the file for uploading cannot be uploaded.

[0051] The determination executing module 42 can include a receiving module 421 used to receive a file uploading request. In various embodiments, the url request, linked to the triggering button related to the file for uploading, can be, for example,

http://wbupload://somehost/somepath?someque^

c3, where http://wbupload is the agreed protocol header; somehost/somepath?somequery & is a post request url related to file uploading;

http://wbupload://somehost/somepath?somequei &cookiejs=func1 &successjs=func2&position^ c3 is a fixed format with each of funcl, func2, and func3 (js function name with no parentheses) having a specific name delivered depending on a server. [0052] The receiving module 421 can include a first calling module 4211 configured to use the UlWebView control to call the fund js function to obtain cookie values used for sending the file uploading request.

[0053] The determination executing module 42 can also include a box pop-up module 422 configured to generate and pop up a file selection box.

[0054] Optionally, the box pop-up module 422 can include a second calling module 4221 configured to use the UlWebView control to call related js function to calculate a position for the file selection box to point to.

[0055] The determination executing module 42 can further include a determination executing sub-module 423 configured to determine whether the file for uploading is selected. When the file for uploading is selected, the selected file can then be uploaded.

[0056] The determination executing module 42 can further include a displaying module 424 configured to display the webpage after the uploading of the file.

[0057] The displaying module 424 can include a third calling module 4241 configured to use the UlWebView control to call related js function to display the webpage following the uploading of the file.

[0058] The disclosed apparatus for uploading a file based on a webkit kernel browser uses a monitoring module to monitor the url request. The determination executing module is used to determine whether the url request contains the agreed protocol header. When it is determined that the url request contains the agreed protocol header, the file for updating can be received and uploaded. Otherwise, when it is determined that the url request does not contain the agreed protocol header, the file uploading cannot be performed. This solves the problems that the webkit kernel browser for conventional iOS apparatus cannot upload files. [0059] It should be noted that, in the present disclosure each embodiment is progressively described, i.e., each embodiment is described and focused on difference between embodiments. Similar and/or the same portions between various embodiments can be referred to with each other. In addition, exemplary apparatus is described with respect to corresponding methods.

[0060] Note that, the term "comprising", "including" or any other variants thereof are intended to cover a non-exclusive inclusion, such that the process, method, article, or apparatus containing a number of elements also include not only those elements, but also other elements that are not expressly listed; or further include inherent elements of the process, method, article or apparatus. Without further restrictions, the statement "includes a " does not exclude other elements included in the process, method, article, or apparatus having those elements.

[0061] A person of ordinary skill in the art can understand that the modules included herein are described according to their functional logic, but are not limited to the above descriptions as long as the modules can implement corresponding functions. Further, the specific name of each functional module is used for distinguishing from on another without limiting the protection scope of the present disclosure.

[0062] In various embodiments, the disclosed modules can be configured in one apparatus or configured in multiple apparatus as desired. The modules disclosed herein can be integrated in one module or in multiple modules. Each of the modules disclosed herein can be divided into one or more sub-modules, which can be recombined in any manner.

[0063] One of ordinary skill in the art would appreciate that suitable software and/or hardware (e.g., a universal hardware platform) may be included and used in the disclosed methods and systems. For example, the disclosed embodiments can be implemented by hardware only, which alternatively can be implemented by software products only. The software products can be stored in a computer-readable storage medium including, e.g., ROM/RAM, magnetic disk, optical disk, etc. The software products can include suitable commands to enable a terminal device (e.g., including a mobile phone, a personal computer, a server, or a network device, etc.) to implement the disclosed embodiments.

[0064] The embodiments disclosed herein are exemplary only. Other applications, advantages, alternations, modifications, or equivalents to the disclosed embodiments are obvious to those skilled in the art and are intended to be encompassed within the scope of the present disclosure.

INDUSTRIAL APPLICABILITY AND ADVANTAGEOUS EFFECTS

[0065] Without limiting the scope of any claim and/or the specification, examples of industrial applicability and certain advantageous effects of the disclosed embodiments are listed for illustrative purposes. Various alternations, modifications, or equivalents to the technical solutions of the disclosed embodiments can be obvious to those skilled in the art and can be included in this disclosure.

[0066] The disclosed methods for uploading a file based on the webkit kernel browser uses a form of a link to replace conventional input tabs. When the triggering button is clicked by the user, the UlWebView control in the webkit kernel browser is triggered to monitor a url request and to determine whether the url request contains the agreed protocol header. When it is determined that the url request contains the agreed protocol header, the file for uploading is received and uploaded. Otherwise, when it is determined that the url request does not contain the agreed protocol header, the file for uploading cannot be uploaded. This may solve the problems that the webkit kernel browser for conventional iOS apparatus cannot upload files.

[0067] The disclosed apparatus for uploading a file based on a webkit kernel browser uses a monitoring module to monitor the url request. The determination executing module is used to determine whether the url request contains the agreed protocol header. When it is determined that the url request contains the agreed protocol header, the file for updating can be received and uploaded. Otherwise, when it is determined that the url request does not contain the agreed protocol header, the file uploading cannot be performed. This solves the problems that the webkit kernel browser for conventional iOS apparatus cannot upload files. REFERENCE SIGN LIST

Apparatus 30

Monitoring module 31

Determination executing module 32

Setting module 33

Apparatus 40

Monitoring module 41

Determination executing module 42

Receiving module 421

First calling module 4211

Box pop-up module 422

Second calling module 4221

Determination executing sub-module 423

Displaying module 424

Third calling module 4241

Environment 600

Communication network 602

Server 604

Terminal 606

Processor 702

Storage medium 704

Monitor 706

Communications 708

Database 710

Peripherals 712

Claims

1. A method for uploading a file based on a webkit kernel browser comprising:

using a UlWebView control in the webkit kernel browser to monitor a url request, wherein the url request is linked with a triggering button related to a file for uploading on a webpage;

determining whether the url request monitored by the UlWebView control contains an agreed protocol header; and

receiving and uploading the file for uploading, upon the condition that the url request contains the agreed protocol header, wherein the file for uploading is not uploaded upon the condition that the url request does not contain the agreed protocol header.

2. The method of claim 1, wherein, prior to using the UlWebView control to monitor the url request, the method further comprises:

setting the agreed protocol header.

3. The method of claim 1, wherein the receiving and uploading of the file comprises:

receiving a file uploading request;

generating and popping up a file selection box for selecting a file;

determining whether the file for uploading is selected;

uploading the selected file for uploading, upon the condition that the file for uploading is determined to be selected; and

displaying the webpage after the uploading of the file.

4. The method of claim 3, wherein the receiving of the file uploading request comprises:

using the UlWebView control to call a first js function to obtain a cookie value used for sending the file uploading request.

5. The method of claim 3, wherein the generating and popping up of the file selection box comprises: using the UI Web View control to call a second js function to calculate a position for the file selection box to point to.

6. The method of claim 3, wherein the displaying of the webpage after the uploading of the file comprises:

using the UlWebView control to call a third js function to display the webpage following the uploading of the file.

7. An apparatus for uploading a file based on a webkit kernel browser comprising:

a monitoring module, configured to use a UlWebView control in the webkit kernel browser to monitor a url request, wherein the url request is linked with a triggering button related to a file for uploading on a webpage; and

a determination executing module, configured to determine whether the url request monitored by the UlWebView control contains an agreed protocol header, wherein the file for uploading is received and uploaded, upon the condition that the url request contains the agreed protocol header, or the file for uploading is not uploaded, upon the condition that the url request does not contain the agreed protocol header.

8. The apparatus of claim 7, further comprising:

a setting module, configured to set the agreed protocol header.

9. The apparatus of claim 7, wherein the determination executing module comprises:

a receiving module, configured to receive a file uploading request;

a box pop-up module, configured to generate and pop up a file selection box for selecting a file;

a determination executing sub-module, configured to determine whether the file for uploading is selected, wherein, upon the condition that the file for uploading is determined to be selected, the selected file for uploading is uploaded; and

a displaying module, configured to display the webpage after the uploading of the file.

10. The apparatus of claim 9, wherein the receiving module comprises:

a first calling module, configured to use the UlWebView control to call a first js function to obtain a cookie value used for sending the file uploading request.

11. The apparatus of claim 9, wherein the box pop-up module comprises:

a second calling module, configured to use the UlWebView control to call a second js function to calculate a position for the file selection box to point to.

12. The apparatus of claim 9, wherein the displaying module comprises:

a third calling module, configured to use the UlWebView control to call a third js function to display the webpage following the uploading of the file.

13. A non-transitory computer readable medium used in conjunction with an apparatus for uploading a file based on a webkit kernel browser, the computer readable medium comprising instructions for: