METHOD, DEVICE, TERMINAL, SERVER AND STORAGE MEDIUM OF PROCESSING NETWORK REQUEST AND RESPONSE

• US 20180309842A1
• Filed: 04/07/2017
• Published: 10/25/2018
• Est. Priority Date: 07/20/2016
• Status: Active Grant

• Current Assignee: Ping An Technology Company Limited (Ping An Insurance (Group) Company of China, Ltd.)
• Original Assignee: Ping An Technology Company Limited (Ping An Insurance (Group) Company of China, Ltd.)
• Inventors: XIANG, Yangjun
• Granted Patent: US 10,574,773 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1074 for supporting data block transmission mechanisms file transfer H04L67/06
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing

Abstract

A method of processing a network request and response includes: merging a plurality of requests to obtain a merged request; transmitting the merged request to a server side; detecting a current status identification of the merged request; when the status indicated by the current status identification shows that data is transferring, receiving resource data corresponding to each request in the merged request and returned by the server side, and detecting the received resource data and obtaining a boundary identification contained in the received resource data; extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification; and when the status indicated by the current status identification shows that the data transferring is completed, stopping receiving the resource data.

Claims

1. A method of processing a network request and response, comprising:

merging a plurality of requests to obtain a merged request;

transmitting the merged request to a server side;

detecting a current status identification of the merged request;

when the status indicated by the current status identification shows that data is transferring, receiving resource data corresponding to each request in the merged request and returned by the server side, detecting the received resource data, and obtaining a boundary identification contained in the received resource data;

extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification; and

stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed.

2. The method of claim 1, wherein the extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification comprises:

extracting and processing the resource data received before the first boundary identification, when the obtained boundary identification is a first boundary identification in the received resource data, and

extracting and processing the resource data received between the current obtained boundary identification and the previous obtained boundary identification, when the obtained boundary identification is not the first boundary identification in the received resource data.

3. The method of claim 1, wherein after stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed, the method further comprises:

extracting and processing the resource data received after the last obtained boundary identification.

21. The method of claim 1, wherein the merging the plurality of requests to obtain the merged request comprises:

merging requests which request for resource data with the same type in a preset manner to obtain the merged request, wherein the preset manner can be that predefining a separator to separate resources data requested by different requests.

22. The method of claim 1, wherein the boundary identification is configured to identify the resource data uniquely, and the boundary identification can comprises a time stamp and a separator line.

23. The method of claim 1, wherein the stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed comprises:

receiving a message segment with an end mark, wherein the status indicated by the current status identification of the merged request shows that the data transferring is completed, and closing a connection with the server side.

4-10. -10. (canceled)

11. A terminal comprising a processor, and a memory storing computer executable instructions, which, when executed by the processor cause the processor to perform steps comprising:

merging a plurality of requests to obtain a merged request;

transmitting the merged request to a server;

detecting a current status identification of the merged request;

when the status indicated by the current status identification shows that data is transferring, receiving resource data returned by the server and corresponding to each request in the merged request, detecting the received resource data and obtaining a boundary identification contained in the received resource data;

extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification; and

stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed.

12. The terminal of claim 11, wherein the extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification comprises:

extracting and processing the resource data received before the first boundary identification, when the obtained boundary identification is a first boundary identification in the received resource data, and

extracting and processing the resource data received between the current obtained boundary identification and the last obtained boundary identification, when the obtained boundary identification is not the first boundary identification in the received resource data.

13. The terminal of claim 11, wherein the computer executable instructions, which, when executed by the processor, cause the processor to perform steps comprising:

after step of stopping receiving the resource when the status indicated by the current status identification shows that the data transferring is completed, extracting and processing the resource data received after the last obtained boundary identification.

24. The terminal of claim 11, wherein the merging the plurality of requests to obtain the merged request comprises:

merging requests which request for resource data with the same type in a preset manner to obtain the merged request, wherein the preset manner can be that predefining a separator to separate resources data requested by different requests.

25. The terminal of claim 11, wherein the boundary identification is configured to identify the resource data uniquely, and the boundary identification can comprises a time stamp and a separator line.

26. The terminal of claim 11, wherein the stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed comprises:

receiving a message segment with an end mark, wherein the status indicated by the current status identification of the merged request shows that the data transferring is completed, and closing a connection with the server side.

14. (canceled)

15. (canceled)

16. At least one non-transitory computer-readable medium comprising computer executable instructions, which, when executed by at least one processor cause the at least one processor to perform steps comprising:

merging a plurality of requests to obtain a merged request;

transmitting the merged request to a server;

detecting a current status identification of the merged request;

when the status indicated by the current status identification shows that data is transferring, receiving resource data returned by the server and corresponding to each request in the merged request, detecting the received resource data and obtaining a boundary identification contained in the received resource data;

extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification; and

stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed.

17. The non-transitory computer-readable medium of claim 16, wherein the extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification comprises:

extracting and processing the resource data received before the first boundary identification, when the obtained boundary identification is a first boundary identification in the received resource data, and

extracting and processing the resource data received between the current obtained boundary identification and the last obtained boundary identification, when the obtained boundary identification is not the first boundary identification in the received resource data.

18. The non-transitory computer-readable medium of claim 16, wherein the computer executable instructions, which, when executed by the at least one processor, cause the at least one processor to perform steps comprising:

after step of stopping receiving the resource when the status indicated by the current status identification shows that the data transferring is completed, extracting and processing the resource data received after the last obtained boundary identification.

27. The non-transitory computer-readable medium of claim 16, wherein the merging the plurality of requests to obtain the merged request comprises:

merging requests which request for resource data with the same type in a preset manner to obtain the merged request, wherein the preset manner can be that predefining a separator to separate resources data requested by different requests.

28. The non-transitory computer-readable medium of claim 16, wherein the boundary identification is configured to identify the resource data uniquely, and the boundary identification can comprises a time stamp and a separator line.

29. The non-transitory computer-readable medium of claim 16, wherein the stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed comprises:

receiving a message segment with an end mark, wherein the status indicated by the current status identification of the merged request shows that the data transferring is completed, and closing a connection with the server side.

19-20. -20. (canceled)