UPLOADING A FORM ATTACHMENT

• US 20150237163A1
• Filed: 02/17/2015
• Published: 08/20/2015
• Est. Priority Date: 02/20/2014
• Status: Active Grant

• Current Assignee: Alibaba Group Holding Ltd.
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: Ou, Xingnan
• Granted Patent: US 9,692,852 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

Embodiments of the present application relate to a method, apparatus, and system for uploading a form attachment file. The method includes receiving, from a second terminal, a request for an attachment upload address. In response to receiving the request for the attachment upload address, sending a form attachment upload address to the second terminal, receiving, from a first terminal, an attachment upload page access request, and receiving a form attachment from the first terminal.

Claims

1. A method comprising:

receiving, from a second terminal, a request for an attachment upload address;

in response to receiving the request for the attachment upload address, sending a form attachment upload address to the second terminal;

receiving, from a first terminal, an attachment upload page access request for requesting access to a page associated with the attachment upload address; and

receiving a form attachment from the first terminal, the form attachment being an attachment related to the request for the attachment upload address made by the second terminal.

2. The method of claim 1, wherein the first terminal is a mobile terminal.

3. The method of claim 1, wherein the form attachment is received from the first terminal via a submission to the page associated with the attachment upload address.

4. The method of claim 1, wherein the sending of the form attachment upload address to the second terminal comprises:

in response to receiving a form page access request from the second terminal, sending a form page and the form attachment upload address to the second terminal.

5. The method of claim 1, wherein the sending of the form attachment upload address to the second terminal comprises:

in response to receiving the request for the attachment upload address from the second terminal after the second terminal accesses a form page, sending the form attachment upload address to the second terminal.

6. The method of claim 1, wherein:

the sending of the form attachment upload address to the second terminal comprises generating an information code based at least in part on the form attachment upload address, and sending the information code to the second terminal.

7. The method of claim 6, wherein the sending of the form attachment upload address further comprises:

providing, by the second terminal, the information code to the first terminal;

acquiring, by the first terminal, the information code; and

extracting, by the first terminal, the form attachment from the information code.

8. The method of claim 1, wherein:

the request for the attachment upload address includes form-related information;

the form-related information is sent with an attachment upload page to the first terminal; and

the form attachment includes the form-related information.

9. The method of claim 8, further comprising:

storing an association between the form-related information and the form attachment.

10. The method claim 8, further comprising:

acquiring a security code that is associated with the form-related information after receiving the request for the attachment upload address sent by the second terminal and before sending the form attachment upload address to the second terminal;

acquiring a result of a validation of the security code in the event that the attachment upload page access request is received; and

in the event that the security code is validated, sending the form-related information mapped to the security code with the attachment upload page to the first terminal.

11. The method of claim 10, wherein the acquiring of the security code associated with the form-related information comprises:

sending the form-related information to an application server;

generating, by the application server, the security code;

associating, by the application server, the security code with the form-related information; and

receiving the security code from the application server.

12. The method of claim 11, wherein the acquiring the result of the validation of the security code comprises:

sending the security code included with the attachment upload page access request to the application server; and

receiving an indication of whether the security code is valid in response to the application server validating the security code included with the attachment upload page access request in comparison to the generated security code.

13. The method of claim 12, wherein validation of the security code comprises:

assessing whether the security code corresponds to an already created security code;

in the event that the security code corresponds to the already created security code, deeming the security code included with the attachment upload page access request to be valid; and

in the event that the security code does not correspond to the already created security code, deeming the security code included with the attachment upload page access request to be invalid.

14. The method of claim 12, wherein validation of the security code comprises:

assessing whether the security code corresponds to an already created security code and whether the security code is unused;

in the event that the security code corresponds to the already created security code and that the security code is unused, deeming the security code included with the attachment upload page access request to be valid; and

in the event that the security code does not correspond to the already created security code or that the security code is not unused, deeming the security code included with the attachment upload page access request to be invalid,

wherein the security code is recorded as used in the event that the security code is validated so as to be deemed valid.

15. The method of claim 1, further comprising:

in response to receiving the form attachment submitted by the first terminal, sending the form attachment to a file storage server.

16. The method of claim 8, further comprising:

receiving a file information regeneration request from the second terminal;

acquiring stored form attachment file information corresponding to form-related information included with the file information regeneration request; and

sending the file information to the second terminal so that the second terminal can use the file information to populate a current form.

17. The method of claim 16, wherein the second terminal sends the file information regeneration request using a polling method that includes:

polling and sending the file information regeneration request via JavaScript included in a form page;

or

polling and sending the file information regeneration request via a plugin embedded in the form page;

or

polling and sending the file information regeneration request by establishing a persistent connection with a web server.

18. A web server comprising:

an interface module configured to exchange data with a second terminal and a first terminal;

a form page returning module configured to send a form attachment upload address to the second terminal via the interface module in response to the interface module receiving a request for an attachment upload address from the second terminal;

an upload page returning module configured to send an attachment upload page to the first terminal via the interface module in response to the interface module receiving an is attachment upload page access request for requesting access to a page associated with the attachment upload address sent from the first terminal; and

a form processing module configured to store a form attachment in response to the interface module receiving the form attachment from the first terminal.

19. The web server of claim 18, wherein the form page returning module is further configured to send a form page and the form attachment upload address to the second terminal.

20. The web server of claim 18, wherein the form page returning module is further configured to send the form attachment upload address to the second terminal in response to the interface module receiving the request for the attachment upload address from the second terminal after the second terminal access a form page.

21. The web server of claim 18, wherein the form page returning module is further configured to generate an information code based at least in part on the form attachment upload address, and to send the information code to the second terminal.

22. The web server of claim 21, wherein the information code is provided to the first terminal, which acquires the information code, and extracts the attachment upload address from the information code.

23. The web server of claim 18, wherein:

the request for the attachment upload address includes form-related information; and

the upload page returning module is further configured to send the form-related information with the attachment upload page to the first terminal.

24. The web server of claim 23, wherein the form processing module is further configured to store an association between the form-related information and the form attachment.

25. The web server of claim 23, wherein:

the form page returning module is further configured to acquire a security code that is associated with the form-related information; and

the upload page returning module is further configured to acquire a result of a validation of the security code in the event that the interface module receives the attachment upload page access request, and in the event that the security code is validated, to send the form-related information mapped to the security code with the attachment upload page to the first terminal.

26. The web server of claim 25, wherein the form page returning module is further is configured to in the event that the security code associated with the form-related information is acquired, send the form-related information to an application server and to receive, from the application server, the security code, which is generated and associated with the form-related information by the application server

27. The web server of claim 26, wherein the upload page returning module is further configured to send the security code included with the attachment upload page access request to the application server, and to receive an indication of whether the security code is valid in response to the application server validating the security code included with the attachment upload page access request in comparison to the generated security code.

28. The web server of claim 18, wherein the form processing module is further configured to send the form attachment to a file storage server for storage in response to receiving the form attachment submitted by the first terminal.

29. The web server of claim 23, further comprising:

a file information acquiring module configured to acquire, in the event that the interface module receives a file information regeneration request from the second terminal, stored form attachment file information corresponding to the form-related information included with the file information regeneration request, and to send the file information via the interface module to the second terminal so that the second terminal can use the file information to populate a current form.

30. A computer program product embodied in a tangible non-transitory computer-readable storage medium and comprising computer instructions for:

receiving a request for an attachment upload address from a second terminal;

sending a form attachment upload address to the second terminal in response to receiving the request for the attachment upload address from the second terminal;

receiving an attachment upload page access request for requesting access to a page associated with the attachment upload address sent from a first terminal;

sending page associated with attachment upload address to the first terminal in response to receiving the attachment upload page access request; and

receiving a form attachment from the first terminal, the form attachment being an attachment related to the request for the attachment upload address made by the second terminal.

31. The computer program product of claim 30, wherein the computer instructions are further configured to:

acquire a security code that is associated with form-related information; and

acquire a result of a validation of the security code in the event that the attachment upload page access request is received, and in the event that the security code is validated, send the form-related information mapped to the security code with the attachment upload page to the first terminal.

32. The computer program product of claim 30, wherein the computer instructions are further configured to:

send the form attachment to a file storage server for storage in response to receiving the form attachment submitted by the first terminal.

33. The computer program product of claim 30, wherein the computer instructions are further configured to:

in response to receiving a file information regeneration request from the second terminal, acquire stored form attachment file information corresponding to form-related information included with the file information regeneration request; and

send the file information to the second terminal so that the second terminal can use the file information to populate a current form.