CN111367868A - Method and device for processing file acquisition request - Google Patents

Method and device for processing file acquisition request Download PDF

Info

Publication number
CN111367868A
CN111367868A CN201811601136.2A CN201811601136A CN111367868A CN 111367868 A CN111367868 A CN 111367868A CN 201811601136 A CN201811601136 A CN 201811601136A CN 111367868 A CN111367868 A CN 111367868A
Authority
CN
China
Prior art keywords
request
target object
returned
request queue
content
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
CN201811601136.2A
Other languages
Chinese (zh)
Other versions
CN111367868B (en
Inventor
温源
黄莹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
3600 Technology Group Co ltd
Original Assignee
Beijing Qihoo Technology Co Ltd
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 Beijing Qihoo Technology Co Ltd filed Critical Beijing Qihoo Technology Co Ltd
Priority to CN201811601136.2A priority Critical patent/CN111367868B/en
Publication of CN111367868A publication Critical patent/CN111367868A/en
Application granted granted Critical
Publication of CN111367868B publication Critical patent/CN111367868B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention discloses a processing method and device of a file acquisition request, electronic equipment and a computer readable storage medium. The method comprises the following steps: receiving an acquisition request for a target object; when the target object is not stored locally, judging whether a request queue meeting the conditions exists or not; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, requesting the target object from the source server, and creating a corresponding request queue according to the content to be returned so as to be put into the request queue when receiving the same acquisition request again; and processing each acquisition request in the request queue according to the content returned by the source server. In the technical scheme, the existence of the request queue meeting the conditions can avoid obtaining the same target object from the source server for multiple times, and prevent the waste of transmission resources between the storage server and the source server; and each acquisition request in the request queue is processed respectively, so that the response efficiency of the acquisition request is ensured.

Description

Method and device for processing file acquisition request
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for processing a file acquisition request, electronic equipment and a computer-readable storage medium.
Background
When the storage server receives an acquisition request for a certain file sent by a user, if the file is not locally stored, the file needs to be acquired from the source server, that is, the source server occupies transmission resources between the source server and returns the file to the storage server. If the storage server receives the acquisition request for the same file again while the source server is returning the file, the file still needs to be acquired from the source server because the file is not stored locally. Thus, the same file is acquired from the source server for multiple times, which causes waste of transmission resources between the storage server and the source server.
Disclosure of Invention
In view of the above, the present invention has been made to provide a file acquisition request processing method, apparatus, electronic device, and computer-readable storage medium that overcome or at least partially solve the above-mentioned problems.
According to one aspect of the present invention, a method for processing a file acquisition request is provided, wherein the method comprises:
receiving an acquisition request for a target object;
when the target object is not stored locally, judging whether a request queue meeting the conditions exists or not;
if so, putting the acquisition request into a request queue meeting the conditions;
otherwise, requesting the target object from a source server, and creating a corresponding request queue according to the content to be returned;
and processing each acquisition request in the request queue according to the content returned by the source server.
Optionally, when the target object is a specified field of a specified file, the locally unsaved target object includes:
the appointed file corresponding to the target object is not stored locally;
or the designated file stored locally does not contain the target object.
Optionally, the determining whether there is a qualified request queue includes:
and judging whether the content to be returned corresponding to the existing request queue contains the target object.
Optionally, when the target object is a specified field of a specified file, the creating a corresponding request queue according to the content to be returned includes:
judging whether the source server supports the request of the target object;
if so, determining that the content to be returned corresponding to the created request queue is the target object;
if not, determining that the corresponding content to be returned of the created request queue is the specified file containing the target object.
Optionally, the processing, according to the content returned by the source server, each acquisition request in the request queue includes:
and synchronously processing each acquisition request in the request queue according to the content returned by the source server.
Optionally, the synchronizing, according to the content returned by the source server, each acquisition request in the request queue includes:
and when the source server returns the part of the content, synchronously responding to each acquisition request in the request queue, and returning the returned part to the request end until the source server returns all the content.
Optionally, the synchronizing, when the source server returns a part of the content, each acquisition request in the response request queue, and returning the returned part of the content to the request end includes:
and determining one or more acquisition requests corresponding to the returned partial contents of the source server in the request queue, and synchronously responding to the determined one or more acquisition requests and returning the returned partial contents to the corresponding request terminal.
Optionally, the method further comprises:
when the target object is locally stored but the stored target object is incomplete, responding to the acquisition request, and returning part of the existing target object to the request end;
and when all the existing part of target objects return, putting the acquisition request into a corresponding request queue.
According to another aspect of the present invention, there is provided a file acquisition request processing apparatus, wherein the apparatus includes:
a receiving unit adapted to receive an acquisition request for a target object;
the judging unit is suitable for judging whether a request queue meeting the conditions exists or not when the target object is not stored locally; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, requesting the target object from a source server, and creating a corresponding request queue according to the content to be returned;
and the processing unit is suitable for processing each acquisition request in the request queue according to the content returned by the source server.
Optionally, when the target object is a designated field of a designated file, the determining unit is adapted to not store the designated file corresponding to the target object locally; or, when the target object is not contained in the locally stored specified file, the judgment is performed.
Alternatively,
the judging unit is suitable for judging whether the content to be returned corresponding to the existing request queue contains the target object.
Optionally, when the target object is a specified field of a specified file, the determining unit is adapted to determine whether the source server supports the request for the target object; if so, determining that the content to be returned corresponding to the created request queue is the target object; if not, determining that the corresponding content to be returned of the created request queue is the specified file containing the target object.
Alternatively,
and the processing unit is suitable for synchronously processing each acquisition request in the request queue according to the content returned by the source server.
Alternatively,
and the processing unit is suitable for synchronously responding each acquisition request in the request queue and returning the returned part to the request end when the source server returns the part of the content each time until the source server returns all the content.
Alternatively,
the processing unit is suitable for determining one or more acquisition requests corresponding to the partial content returned by the source server in the request queue, and synchronously responding to the one or more acquisition requests determined and returning the returned partial content to the corresponding request terminal.
Alternatively,
the processing unit is suitable for responding to the acquisition request and returning part of the existing target objects to the request end when the target objects are locally stored but the stored target objects are incomplete;
and when all the existing part of target objects return, putting the acquisition request into a corresponding request queue.
According to still another aspect of the present invention, there is provided an electronic apparatus, wherein the electronic apparatus includes:
a processor; and the number of the first and second groups,
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform a method according to the foregoing.
According to yet another aspect of the present invention, there is provided a computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement the aforementioned method.
According to the technical scheme of the invention, an acquisition request for a target object is received; when the target object is not stored locally, judging whether a request queue meeting the conditions exists or not; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, requesting the target object from the source server, and creating a corresponding request queue according to the content to be returned so as to be put into the request queue when receiving the same acquisition request again; and processing each acquisition request in the request queue according to the content returned by the source server. In the technical scheme, the existence of the request queue meeting the conditions can avoid obtaining the same target object from the source server for multiple times, and prevent the waste of transmission resources between the storage server and the source server; and each acquisition request in the request queue is processed respectively, so that the response efficiency of the acquisition request is ensured.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flowchart illustrating a method for processing a file retrieval request according to an embodiment of the invention;
FIG. 2 is a schematic diagram illustrating an architecture of a device for processing a file retrieval request according to an embodiment of the present invention;
FIG. 3 shows a schematic structural diagram of an electronic device according to one embodiment of the invention;
fig. 4 shows a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 is a flowchart illustrating a method for processing a file acquisition request according to an embodiment of the present invention. As shown in fig. 1, the method includes:
in step S110, an acquisition request for a target object is received.
The target object can be a complete file or a specified field of a file.
Step S120, when the target object is not stored locally, judging whether a request queue meeting the condition exists; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, the target object is requested from the source server, and a corresponding request queue is created according to the content to be returned.
For the acquisition request which needs to request the target object from the source server, a corresponding request queue is created, so that the acquisition requests for the same target object which are received at the same time or the acquisition requests for the same target object which are received later are put into the request queue, and then the processing is carried out according to the content returned by the source server.
Before the acquisition request of the target object is received, if the target object is not stored locally and a qualified request queue is created, the target object is requested from the source server. Then, the obtaining request may not need to request the target object from the source server, but may be directly put into the request queue, and when each obtaining request in the request queue is processed according to the content returned by the source server, the obtaining request is also processed. If there is no eligible request queue, the target object needs to be requested from the source server and a request queue is created.
Step S130, processing each acquisition request in the request queue according to the content returned by the source server.
The corresponding request queue only needs to request the source server once, and the acquisition requests in the request queue can obtain corresponding target objects, so that the same target object can be prevented from being acquired from the source server for multiple times, and the waste of transmission resources between the storage server and the source server is prevented; and each acquisition request in the request queue is processed respectively, so that the response efficiency of the acquisition request is ensured.
In one embodiment of the present invention, when the target object is a specified field of a specified file, the locally unsaved target object includes: the appointed file corresponding to the target object is not stored locally; alternatively, the target object is not contained in the locally stored specified file.
In practical applications, the acquisition request for the target object may be an acquisition request for a complete file, or an acquisition request for a specified field of a file.
For the acquisition request of the specified field of a file, when determining whether the file is locally saved, two situations exist, wherein one situation is that any field of the file is not locally saved, namely the file is not locally saved; in another case, the file is stored locally, but the stored file is incomplete and there is no specified field to be obtained by the acquisition request. For example, the acquisition request acquires field 2 of file 1, one is that file 1 is not saved locally, and the other is that only field 1 of file 1 is saved locally and field 2 is not saved.
In one embodiment of the present invention, the determining whether there is a qualified request queue in step S120 of the method shown in fig. 1 includes: and judging whether the content to be returned corresponding to the existing request queue contains a target object.
It is contemplated that the existing request queue may be created upon receiving a get request for a complete file, or may be created upon receiving a get request for a specified field of a file. If the request is created when the request for acquiring the complete file is received, and the request is for the complete file when the request is made to the source server, the content to be returned by the request queue is the complete file, and at this time, the content returned by the source server contains the target object regardless of whether the request for acquiring the complete file or the request for acquiring the specified field of the file is the request for acquiring the target object received in step S110, that is, the content to be returned corresponding to the request queue contains the target object.
However, if the request queue is created when a get request for a specified field of a file is received. Then it is considered whether the content returned by the origin server is the specified field corresponding to the request for acquisition or the complete file. If the returned content is the specified field corresponding to the get request, and the specified field corresponding to the get request is different from the specified field obtained by the get request received in step S110, even if the get request received in step S110 is put into the request queue, the corresponding specified field cannot be obtained. Therefore, in this embodiment, it is necessary to determine whether the content to be returned corresponding to the existing request queue includes the target object.
In an embodiment of the present invention, when the target object in the method shown in fig. 1 is a specified field of a specified file, the creating a corresponding request queue according to the content to be returned in step S120 includes:
judging whether the source server supports the request of the target object; if so, determining that the content to be returned corresponding to the created request queue is a target object; if not, determining that the corresponding content to be returned of the created request queue is the specified file containing the target object.
Consider whether the origin server supports requests for random files or requests for only full files. For example, some origin servers can only return a complete file even if they receive a request for a specified field of a file, and some origin servers return the specified field of a file when they receive a request for the specified field of the file. It can be seen that the content to be returned by the origin server is different after receiving the request.
If the source server supports the request for the target object and the content to be returned corresponding to the created request queue is the target object, only the acquisition request for the same specified field can be put into the request queue in the later time.
If the source server does not support the request for the target object, and the content to be returned corresponding to the created request queue is the specified file containing the target object, then in the later time, as long as the request for obtaining the same file can be put into the request queue.
In an embodiment of the present invention, the processing, in step S130 of the method shown in fig. 1, each obtaining request in the request queue according to the content returned by the origin server includes: and synchronously processing each acquisition request in the request queue according to the content returned by the source server.
In this embodiment, after the source server returns the content, the source server synchronously processes each acquisition request in the request queue according to the content returned by the source server, so as to prevent the request of the acquisition request from being overtime.
Further, the aforementioned synchronization processing of each acquisition request in the request queue according to the content returned by the source server includes: and when the source server returns the part of the content, synchronously responding to each acquisition request in the request queue, and returning the returned part to the request end until the source server returns all the content.
In this embodiment, the effect of sending while receiving can be achieved, that is, the source server returns a part of the content when returning the content, and does not return the content once, so that when the source server returns a part of the content, the returned part is returned to the request end first, and when the source server returns another part of the content, the other part of the content is returned to the request end again until the source server returns all the content, and all the content is returned to the request end. Here, the requesting side is a device that sends the acquisition request.
Further, the above-mentioned, when the source server returns a part of the content, synchronizing the acquisition requests in the response request queue, and returning the returned part of the content to the request end includes: and determining one or more acquisition requests corresponding to the returned partial contents of the source server in the request queue, and synchronously responding to the determined one or more acquisition requests and returning the returned partial contents to the corresponding request terminal.
The obtaining requests in the request queue are not all obtaining requests for the complete file, and may also include obtaining requests for specified fields of the file, for example, if the content to be returned corresponding to the request queue is the complete file, the obtaining requests included in the request queue may be obtaining requests for the complete file, or obtaining requests for specified fields of the file. Thus, when the origin server returns a portion of the content, there are acquisition requests to acquire that portion and there are requests to acquire that portion. Therefore, in the present embodiment, one or more acquisition requests in the request queue corresponding to the partial content that has been returned by the origin server are first determined. And synchronously responding to the determined one or more acquisition requests, and returning the returned partial contents to the corresponding request end.
For example, the request queue includes an acquire request 1 to acquire a complete file, an acquire request 2 to acquire a specified field 1 of the file, and an acquire request 3 to acquire a specified field 2 of the file. When the source server returns the designated field 1 of the file, determining that the corresponding acquisition requests are an acquisition request 1 and an acquisition request 2, then synchronously responding to the acquisition request 1 and the acquisition request 2, and respectively returning the designated field 1 of the file to the request ends corresponding to the acquisition request 1 and the acquisition request 2; when the source server returns the specified field 2 of the national enterprise file, the corresponding acquisition requests are determined to be the acquisition request 1 and the acquisition request 3, then the acquisition request 1 and the acquisition request 3 are synchronously responded, and the specified field 2 of the file is respectively returned to the request ends corresponding to the acquisition request 1 and the acquisition request 3.
That is, with the present embodiment, for an acquisition request for a specified field of a file in a request queue, only when the origin server starts to return the specified field of the file, the response to the acquisition request for the specified field is restarted.
In one embodiment of the present invention, the method shown in fig. 1 further comprises: when the target object is locally stored but the stored target object is incomplete, responding to the acquisition request, and returning part of the existing target object to the request end; and when all the existing part of target objects return, putting the acquisition request into a corresponding request queue.
When the target object is locally stored, the two situations are also divided into two situations, wherein one situation is that the target object obtained by the acquisition request is completely stored, and then the stored target object can be directly returned to the corresponding request end; the other situation is that the target object acquired by the acquisition request is stored in a part of the storage, and the storage is incomplete, which indicates that the target object is requesting from the source server, but the source server has not returned all the target objects, then the part of the target object to be stored is returned to the corresponding request terminal, and after the part of the target object to be stored is returned, the corresponding request queue is determined, and the acquisition request is placed in the request queue.
The corresponding request queue determined here is also a qualified request queue, for example, the content to be returned corresponding to the request queue includes the target object. Alternatively, the content to be returned corresponding to the request queue includes the target object that is not returned, for example, the first part and the second part of the target object, where the first part is already returned, and then the content to be returned corresponding to the request queue includes the second part of the target object.
In one embodiment of the present invention, the method shown in fig. 1 further comprises: when a plurality of acquisition requests for the same file are received at the same time, if no request queue meeting the conditions exists, determining one acquisition request from the plurality of acquisition requests, requesting the file from the source server according to the acquisition request, creating a request queue, and putting the rest acquisition requests into the request queue.
In a specific example, the received get request is a get request of a complete file. First, whether the complete file is stored locally is judged. (1) And if the file is completely stored, directly responding to the acquisition request and returning the complete file. If the file is not completely stored, the stored part of the file is returned, and then the acquisition request is placed into the corresponding request queue. (2) If the file is not stored, judging whether a request queue for acquiring the complete file exists, and if so, putting the acquisition request into the request queue. And if not, requesting the file from the source server, and creating a request queue, wherein the content to be returned corresponding to the request queue is the complete file. Then, according to the content returned by the source server, the acquisition requests in the request queue are synchronously processed.
In another specific example, the received get request is a get request of a specified field of a file. First, it is determined whether the specified field is stored locally. (1) If the specified field exists, the acquisition request is directly responded, and the specified field is returned. (2) If the file is locally stored, or the file is stored but the specified field is not stored, judging whether a request queue with the content to be returned containing the specified field exists, if so, putting the acquisition request into the request queue, if not, requesting the specified field from the source server, and creating a request queue according to the content to be returned of the source server. Then, according to the content returned by the source server, the acquisition requests in the request queue are synchronously processed.
For example, when a plurality of acquisition requests for the same file are received at the same time, if there is no request queue meeting the conditions, one acquisition request is determined from the plurality of acquisition requests, the file is requested from the source server according to the acquisition request, a request queue is created, and the rest acquisition requests are placed in the request queue. When a get request for the same file is received again, the get request is also placed in the request queue. Then, when the source server returns the file, the acquisition request in the request queue is responded to synchronously. Or, when the acquisition request for the specified field of the same file is received again, the acquisition request is put into the request queue, and when the source server returns the specified field, the source server starts to respond to the acquisition request in the request queue.
For another example, when a plurality of acquisition requests for the first field of the same file are received at the same time, if there is no request queue meeting the condition, one acquisition request is determined from the plurality of acquisition requests, the file is requested from the source server according to the acquisition request, and a request queue is created, and the rest acquisition requests are placed in the request queue. When a get request for the first field of the same file is received again, the get request is also placed in the request queue. Then, when the source server returns the first field of the file, the acquisition requests in the corresponding request queue are synchronized. Or, when receiving an acquisition request for a complete file of the same file again, determining whether the complete file to be returned corresponding to the created request queue is the first field, if the complete file is the first field, placing the acquisition request in the request queue, and when the source server returns the file, starting the acquisition request in the corresponding request queue. If the field is the first field, a request queue is created again, and the content to be returned corresponding to the request queue is the complete file. Or, when receiving an acquisition request for a second field of the same file again, determining whether a complete file to be returned corresponding to the created request queue is the first field, if the complete file is the first field, placing the acquisition request in the request queue, and when the source server returns the second field of the file, starting the acquisition request in the corresponding request queue. And if the first field exists, creating a request queue again, wherein the content to be returned corresponding to the request queue is the second field of the file.
Fig. 2 is a schematic structural diagram of a file acquisition request processing apparatus according to an embodiment of the present invention. As shown in fig. 2, the file acquisition request processing apparatus 200 includes:
the receiving unit 210 is adapted to receive an acquisition request for a target object.
The target object can be a complete file or a specified field of a file.
A judging unit 220, adapted to judge whether there is a request queue meeting the condition when the target object is not locally stored; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, the target object is requested from the source server, and a corresponding request queue is created according to the content to be returned.
For the acquisition request which needs to request the target object from the source server, a corresponding request queue is created, so that the acquisition requests for the same target object which are received at the same time or the acquisition requests for the same target object which are received later are put into the request queue, and then the processing is carried out according to the content returned by the source server.
Before the acquisition request of the target object is received, if the target object is not stored locally and a qualified request queue is created, the target object is requested from the source server. Then, the obtaining request may not need to request the target object from the source server, but may be directly put into the request queue, and when each obtaining request in the request queue is processed according to the content returned by the source server, the obtaining request is also processed. If there is no eligible request queue, the target object needs to be requested from the source server and a request queue is created.
The processing unit 230 is adapted to process each obtaining request in the request queue according to the content returned by the source server.
The corresponding request queue only needs to request the source server once, and the acquisition requests in the request queue can obtain corresponding target objects, so that the same target object can be prevented from being acquired from the source server for multiple times, and the waste of transmission resources between the storage server and the source server is prevented; and each acquisition request in the request queue is processed respectively, so that the response efficiency of the acquisition request is ensured.
In an embodiment of the present invention, when the target object is a specified field of a specified file, the determining unit 220 shown in fig. 2 is adapted to not save the specified file corresponding to the target object locally; alternatively, the determination is made when the target object is not contained in the designated file stored locally.
In practical applications, the acquisition request for the target object may be an acquisition request for a complete file, or an acquisition request for a specified field of a file.
For the acquisition request of the specified field of a file, when determining whether the file is locally saved, two situations exist, wherein one situation is that any field of the file is not locally saved, namely the file is not locally saved; in another case, the file is stored locally, but the stored file is incomplete and there is no specified field to be obtained by the acquisition request. For example, the acquisition request acquires field 2 of file 1, one is that file 1 is not saved locally, and the other is that only field 1 of file 1 is saved locally and field 2 is not saved.
In an embodiment of the present invention, the determining unit 220 shown in fig. 2 is adapted to determine whether the content to be returned corresponding to the existing request queue includes the target object.
It is contemplated that the existing request queue may be created upon receiving a get request for a complete file, or may be created upon receiving a get request for a specified field of a file. If the request is created when the acquisition request for the complete file is received, and the request is for the complete file when the request is made to the source server, the content to be returned by the request queue is the complete file, at this time, the content returned by the source server contains the target object regardless of whether the acquisition request for the target object received by the receiving unit is the acquisition request for the complete file or the acquisition request for the specified field of the file, that is, the content to be returned corresponding to the request queue contains the target object.
However, if the request queue is created when a get request for a specified field of a file is received. Then it is considered whether the content returned by the origin server is the specified field corresponding to the request for acquisition or the complete file. If the returned content is the specified field corresponding to the acquisition request, and the specified field corresponding to the acquisition request is different from the specified field obtained by the acquisition request received by the receiving unit, even if the acquisition request received by the receiving unit is put into the request queue, the corresponding specified field cannot be obtained. Therefore, in this embodiment, it is necessary to determine whether the content to be returned corresponding to the existing request queue includes the target object.
In one embodiment of the present invention, when the target object is a specified field of a specified file, the determining unit 220 shown in fig. 2 is adapted to determine whether the source server supports the request for the target object; if so, determining that the content to be returned corresponding to the created request queue is a target object; if not, determining that the corresponding content to be returned of the created request queue is the specified file containing the target object.
Consider whether the origin server supports requests for random files or requests for only full files. For example, some origin servers can only return a complete file even if they receive a request for a specified field of a file, and some origin servers return the specified field of a file when they receive a request for the specified field of the file. It can be seen that the content to be returned by the origin server is different after receiving the request.
If the source server supports the request for the target object and the content to be returned corresponding to the created request queue is the target object, only the acquisition request for the same specified field can be put into the request queue in the later time.
If the source server does not support the request for the target object, and the content to be returned corresponding to the created request queue is the specified file containing the target object, then in the later time, as long as the request for obtaining the same file can be put into the request queue.
In an embodiment of the present invention, the processing unit 230 shown in fig. 2 is adapted to synchronously process each acquisition request in the request queue according to the content returned by the origin server.
In this embodiment, after the source server returns the content, the source server synchronously processes each acquisition request in the request queue according to the content returned by the source server, so as to prevent the request of the acquisition request from being overtime.
Further, the processing unit 230 is adapted to, each time the source server returns a part of the content, synchronously respond to each acquisition request in the request queue, and return the returned part to the requesting end until the source server returns all the content.
In this embodiment, the effect of sending while receiving can be achieved, that is, the source server returns a part of the content when returning the content, and does not return the content once, so that when the source server returns a part of the content, the returned part is returned to the request end first, and when the source server returns another part of the content, the other part of the content is returned to the request end again until the source server returns all the content, and all the content is returned to the request end. Here, the requesting side is a device that sends the acquisition request.
Further, the processing unit 230 is adapted to determine one or more obtaining requests in the request queue corresponding to the partial content that has been returned by the source server, and synchronously respond to the one or more obtaining requests that are determined, and return the partial content that has been returned to the corresponding requesting end.
The obtaining requests in the request queue are not all obtaining requests for the complete file, and may also include obtaining requests for specified fields of the file, for example, if the content to be returned corresponding to the request queue is the complete file, the obtaining requests included in the request queue may be obtaining requests for the complete file, or obtaining requests for specified fields of the file. Thus, when the origin server returns a portion of the content, there are acquisition requests to acquire that portion and there are requests to acquire that portion. Therefore, in the present embodiment, one or more acquisition requests in the request queue corresponding to the partial content that has been returned by the origin server are first determined. And synchronously responding to the determined one or more acquisition requests, and returning the returned partial contents to the corresponding request end.
For example, the request queue includes an acquire request 1 to acquire a complete file, an acquire request 2 to acquire a specified field 1 of the file, and an acquire request 3 to acquire a specified field 2 of the file. When the source server returns the designated field 1 of the file, determining that the corresponding acquisition requests are an acquisition request 1 and an acquisition request 2, then synchronously responding to the acquisition request 1 and the acquisition request 2, and respectively returning the designated field 1 of the file to the request ends corresponding to the acquisition request 1 and the acquisition request 2; when the source server returns the specified field 2 of the national enterprise file, the corresponding acquisition requests are determined to be the acquisition request 1 and the acquisition request 3, then the acquisition request 1 and the acquisition request 3 are synchronously responded, and the specified field 2 of the file is respectively returned to the request ends corresponding to the acquisition request 1 and the acquisition request 3.
That is, with the present embodiment, for an acquisition request for a specified field of a file in a request queue, only when the origin server starts to return the specified field of the file, the response to the acquisition request for the specified field is restarted.
In an embodiment of the present invention, the processing unit 230 shown in fig. 2 is adapted to, when the target object is locally stored, but the stored target object is not complete, return the existing part of the target object to the requesting end in response to the obtaining request; and when all the existing part of target objects return, putting the acquisition request into a corresponding request queue.
When the target object is locally stored, the two situations are also divided into two situations, wherein one situation is that the target object obtained by the acquisition request is completely stored, and then the stored target object can be directly returned to the corresponding request end; the other situation is that the target object acquired by the acquisition request is stored in a part of the storage, and the storage is incomplete, which indicates that the target object is requesting from the source server, but the source server has not returned all the target objects, then the part of the target object to be stored is returned to the corresponding request terminal, and after the part of the target object to be stored is returned, the corresponding request queue is determined, and the acquisition request is placed in the request queue.
The corresponding request queue determined here is also a qualified request queue, for example, the content to be returned corresponding to the request queue includes the target object. Alternatively, the content to be returned corresponding to the request queue includes the target object that is not returned, for example, the first part and the second part of the target object, where the first part is already returned, and then the content to be returned corresponding to the request queue includes the second part of the target object.
In one embodiment of the present invention, the apparatus shown in fig. 2 further comprises: the creating unit is suitable for determining an obtaining request from a plurality of obtaining requests when a plurality of obtaining requests for the same file are received at the same time and if no request queue meeting the conditions exists, requesting the file from the source server according to the obtaining request, creating a request queue, and placing the rest obtaining requests into the request queue.
In summary, according to the technical solution of the present invention, an acquisition request for a target object is received; when the target object is not stored locally, judging whether a request queue meeting the conditions exists or not; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, requesting the target object from the source server, and creating a corresponding request queue according to the content to be returned so as to be put into the request queue when receiving the same acquisition request again; and processing each acquisition request in the request queue according to the content returned by the source server. In the technical scheme, the existence of the request queue meeting the conditions can avoid obtaining the same target object from the source server for multiple times, and prevent the waste of transmission resources between the storage server and the source server; and each acquisition request in the request queue is processed respectively, so that the response efficiency of the acquisition request is ensured.
It should be noted that:
the algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose devices may be used with the teachings herein. The required structure for constructing such a device will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the processing means, electronics and computer readable storage medium of file retrieval requests according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
For example, fig. 3 shows a schematic structural diagram of an electronic device according to an embodiment of the invention. The electronic device 300 conventionally comprises a processor 310 and a memory 320 arranged to store computer-executable instructions (program code). The memory 320 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Memory 320 has storage space 330 for storing program code 340 for performing the method steps shown in fig. 1 and in any of the embodiments. For example, the storage space 330 for the program code may comprise respective program codes 340 for implementing respective steps in the above method. The program code can be read from or written to one or more computer program products. These computer program products comprise a program code carrier such as a hard disk, a Compact Disc (CD), a memory card or a floppy disk. Such a computer program product is generally a computer-readable storage medium 400 such as described in fig. 4. The computer-readable storage medium 400 may have memory segments, memory spaces, etc. arranged similarly to the memory 320 in the electronic device of fig. 3. The program code may be compressed, for example, in a suitable form. In general, the memory unit stores a program code 410 for performing the steps of the method according to the invention, i.e. a program code readable by a processor such as 310, which program code, when executed by an electronic device, causes the electronic device to perform the individual steps of the method described above.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, third, etc. does not indicate any ordering. These words may be interpreted as names.
The invention discloses A1 and a processing method of a file acquisition request, wherein the method comprises the following steps:
receiving an acquisition request for a target object;
when the target object is not stored locally, judging whether a request queue meeting the conditions exists or not;
if so, putting the acquisition request into a request queue meeting the conditions;
otherwise, requesting the target object from a source server, and creating a corresponding request queue according to the content to be returned;
and processing each acquisition request in the request queue according to the content returned by the source server.
A2, the method of A1, wherein when the target object is a specified field of a specified file, the locally unsaved target object comprises:
the appointed file corresponding to the target object is not stored locally;
or the designated file stored locally does not contain the target object.
A3, the method of A1, wherein the determining whether there is a eligible request queue includes:
and judging whether the content to be returned corresponding to the existing request queue contains the target object.
A4, the method as in A1, wherein when the target object is a specified field of a specified file, the creating a corresponding request queue according to content to be returned comprises:
judging whether the source server supports the request of the target object;
if so, determining that the content to be returned corresponding to the created request queue is the target object;
if not, determining that the corresponding content to be returned of the created request queue is the specified file containing the target object.
A5, the method as in a1, wherein the processing each get request in the request queue according to the content returned by the source server includes:
and synchronously processing each acquisition request in the request queue according to the content returned by the source server.
A6, the method as in A5, wherein the synchronizing the obtaining requests in the request queue according to the content returned by the source server comprises:
and when the source server returns the part of the content, synchronously responding to each acquisition request in the request queue, and returning the returned part to the request end until the source server returns all the content.
A7, the method as in a5, wherein the synchronizing the respective get requests in the request queue each time the source server returns a portion of content, and the returning the returned portion of content to the requesting end comprises:
and determining one or more acquisition requests corresponding to the returned partial contents of the source server in the request queue, and synchronously responding to the determined one or more acquisition requests and returning the returned partial contents to the corresponding request terminal.
A8, the method of a1, wherein the method further comprises:
when the target object is locally stored but the stored target object is incomplete, responding to the acquisition request, and returning part of the existing target object to the request end;
and when all the existing part of target objects return, putting the acquisition request into a corresponding request queue.
The invention also discloses B9, a processing device of the file acquisition request, wherein, the device comprises:
a receiving unit adapted to receive an acquisition request for a target object;
the judging unit is suitable for judging whether a request queue meeting the conditions exists or not when the target object is not stored locally; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, requesting the target object from a source server, and creating a corresponding request queue according to the content to be returned;
and the processing unit is suitable for processing each acquisition request in the request queue according to the content returned by the source server.
The device as B10 stated in B9, wherein when the target object is a designated field of a designated file, the judging unit is adapted to not save the designated file corresponding to the target object locally; or, when the target object is not contained in the locally stored specified file, the judgment is performed.
B11, the device of B9, wherein,
the judging unit is suitable for judging whether the content to be returned corresponding to the existing request queue contains the target object.
B12 the apparatus according to B9, wherein when the target object is a designated field of a designated file, the judging unit is adapted to judge whether the source server supports the request for the target object; if so, determining that the content to be returned corresponding to the created request queue is the target object; if not, determining that the corresponding content to be returned of the created request queue is the specified file containing the target object.
B13, the device of B9, wherein,
and the processing unit is suitable for synchronously processing each acquisition request in the request queue according to the content returned by the source server.
B14, the device of B13, wherein,
and the processing unit is suitable for synchronously responding each acquisition request in the request queue and returning the returned part to the request end when the source server returns the part of the content each time until the source server returns all the content.
B15, the device of B13, wherein,
the processing unit is suitable for determining one or more acquisition requests corresponding to the partial content returned by the source server in the request queue, and synchronously responding to the one or more acquisition requests determined and returning the returned partial content to the corresponding request terminal.
B16, the device of B9, wherein,
the processing unit is suitable for responding to the acquisition request and returning part of the existing target objects to the request end when the target objects are locally stored but the stored target objects are incomplete;
and when all the existing part of target objects return, putting the acquisition request into a corresponding request queue.
The invention also discloses C17 and an electronic device, wherein the electronic device comprises:
a processor; and the number of the first and second groups,
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform a method according to any one of a 1-A8.
The invention also discloses D18, a computer readable storage medium, wherein the computer readable storage medium stores one or more programs that when executed by a processor implement the method of any one of a 1-a 8.

Claims (10)

1. A processing method of a file acquisition request is provided, wherein the method comprises the following steps:
receiving an acquisition request for a target object;
when the target object is not stored locally, judging whether a request queue meeting the conditions exists or not;
if so, putting the acquisition request into a request queue meeting the conditions;
otherwise, requesting the target object from a source server, and creating a corresponding request queue according to the content to be returned;
and processing each acquisition request in the request queue according to the content returned by the source server.
2. The method of claim 1, wherein when the target object is a specified field of a specified file, the locally unsaved target object comprises:
the appointed file corresponding to the target object is not stored locally;
or the designated file stored locally does not contain the target object.
3. The method of claim 1, wherein said determining whether a eligible request queue exists comprises:
and judging whether the content to be returned corresponding to the existing request queue contains the target object.
4. The method of claim 1, wherein, when the target object is a specified field of a specified file, the creating a corresponding request queue according to the content to be returned comprises:
judging whether the source server supports the request of the target object;
if so, determining that the content to be returned corresponding to the created request queue is the target object;
if not, determining that the corresponding content to be returned of the created request queue is the specified file containing the target object.
5. The method of claim 1, wherein the processing each get request in the request queue according to the content returned by the source server comprises:
and synchronously processing each acquisition request in the request queue according to the content returned by the source server.
6. The method as claimed in claim 5, wherein said synchronizing the acquisition requests in the request queue according to the content returned by the source server comprises:
and when the source server returns the part of the content, synchronously responding to each acquisition request in the request queue, and returning the returned part to the request end until the source server returns all the content.
7. The method of claim 5, wherein synchronizing each fetch request in the response request queue each time the origin server returns a portion of the content, returning the returned portion of the content to the requesting end comprises:
and determining one or more acquisition requests corresponding to the returned partial contents of the source server in the request queue, and synchronously responding to the determined one or more acquisition requests and returning the returned partial contents to the corresponding request terminal.
8. A file acquisition request processing apparatus, wherein the apparatus comprises:
a receiving unit adapted to receive an acquisition request for a target object;
the judging unit is suitable for judging whether a request queue meeting the conditions exists or not when the target object is not stored locally; if so, putting the acquisition request into a request queue meeting the conditions; otherwise, requesting the target object from a source server, and creating a corresponding request queue according to the content to be returned;
and the processing unit is suitable for processing each acquisition request in the request queue according to the content returned by the source server.
9. An electronic device, wherein the electronic device comprises:
a processor; and the number of the first and second groups,
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the method of any one of claims 1 to 7.
10. A computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement the method of any of claims 1-7.
CN201811601136.2A 2018-12-26 2018-12-26 File acquisition request processing method and device Active CN111367868B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811601136.2A CN111367868B (en) 2018-12-26 2018-12-26 File acquisition request processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811601136.2A CN111367868B (en) 2018-12-26 2018-12-26 File acquisition request processing method and device

Publications (2)

Publication Number Publication Date
CN111367868A true CN111367868A (en) 2020-07-03
CN111367868B CN111367868B (en) 2023-12-29

Family

ID=71206038

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811601136.2A Active CN111367868B (en) 2018-12-26 2018-12-26 File acquisition request processing method and device

Country Status (1)

Country Link
CN (1) CN111367868B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006946A (en) * 2021-10-29 2022-02-01 中国平安人寿保险股份有限公司 Method, device and equipment for processing homogeneous resource request and storage medium

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102761617A (en) * 2012-07-02 2012-10-31 北京京北方信息技术有限公司 Workflow queue server and workflow scheduling system and method
CN103077243A (en) * 2013-01-16 2013-05-01 北京数码视讯科技股份有限公司 Processing method and system for file system access
CN103139258A (en) * 2011-11-30 2013-06-05 百度在线网络技术(北京)有限公司 Method and device and system for processing page access requests of mobile terminal
US20130173796A1 (en) * 2011-12-30 2013-07-04 United Video Properties, Inc. Systems and methods for managing a media content queue
CN103345486A (en) * 2013-06-24 2013-10-09 积成电子股份有限公司 Method for obtaining and showing picture file by client side under remote browsing environment
CN104219283A (en) * 2014-08-06 2014-12-17 上海爱数软件有限公司 Method for file downloading on demand and automatic synchronizing on basis of cloud storage and device thereof
CN105353987A (en) * 2015-11-13 2016-02-24 曙光信息产业股份有限公司 File processing method and device
WO2016052665A1 (en) * 2014-09-30 2016-04-07 株式会社日立製作所 Distributed storage system
CN106375472A (en) * 2016-09-29 2017-02-01 北京三快在线科技有限公司 Access request processing method and apparatus, and server
CN107302549A (en) * 2016-04-14 2017-10-27 宾盛科技(武汉)有限公司 A kind of remote data transmission and storage system and method
CN107404480A (en) * 2017-07-24 2017-11-28 平安科技(深圳)有限公司 A kind of transmission method of stream medium data, storage medium and streaming media server
CN108628688A (en) * 2018-03-30 2018-10-09 阿里巴巴集团控股有限公司 A kind of message treatment method, device and equipment
CN108965450A (en) * 2018-07-27 2018-12-07 江西贪玩信息技术有限公司 Service request response method, device, computer equipment and storage medium

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139258A (en) * 2011-11-30 2013-06-05 百度在线网络技术(北京)有限公司 Method and device and system for processing page access requests of mobile terminal
US20130173796A1 (en) * 2011-12-30 2013-07-04 United Video Properties, Inc. Systems and methods for managing a media content queue
CN102761617A (en) * 2012-07-02 2012-10-31 北京京北方信息技术有限公司 Workflow queue server and workflow scheduling system and method
CN103077243A (en) * 2013-01-16 2013-05-01 北京数码视讯科技股份有限公司 Processing method and system for file system access
CN103345486A (en) * 2013-06-24 2013-10-09 积成电子股份有限公司 Method for obtaining and showing picture file by client side under remote browsing environment
CN104219283A (en) * 2014-08-06 2014-12-17 上海爱数软件有限公司 Method for file downloading on demand and automatic synchronizing on basis of cloud storage and device thereof
WO2016052665A1 (en) * 2014-09-30 2016-04-07 株式会社日立製作所 Distributed storage system
CN105353987A (en) * 2015-11-13 2016-02-24 曙光信息产业股份有限公司 File processing method and device
CN107302549A (en) * 2016-04-14 2017-10-27 宾盛科技(武汉)有限公司 A kind of remote data transmission and storage system and method
CN106375472A (en) * 2016-09-29 2017-02-01 北京三快在线科技有限公司 Access request processing method and apparatus, and server
CN107404480A (en) * 2017-07-24 2017-11-28 平安科技(深圳)有限公司 A kind of transmission method of stream medium data, storage medium and streaming media server
CN108628688A (en) * 2018-03-30 2018-10-09 阿里巴巴集团控股有限公司 A kind of message treatment method, device and equipment
CN108965450A (en) * 2018-07-27 2018-12-07 江西贪玩信息技术有限公司 Service request response method, device, computer equipment and storage medium

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
张天魁;单思洋;许晓耕;刘银龙;: "信息中心网络缓存技术研究综述", 北京邮电大学学报, vol. 39, no. 03, pages 1 - 15 *
李剑宇;唐荣峰;熊劲;孟丹;: "基于对象存储的机群文件系统数据通路", 计算机工程, no. 10, pages 49 - 51 *
雷博: "基于OpenStack的云文件共享系统构建研究", 信息系统工程, no. 11, pages 58 - 60 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006946A (en) * 2021-10-29 2022-02-01 中国平安人寿保险股份有限公司 Method, device and equipment for processing homogeneous resource request and storage medium
CN114006946B (en) * 2021-10-29 2023-08-29 中国平安人寿保险股份有限公司 Method, device, equipment and storage medium for processing homogeneous resource request

Also Published As

Publication number Publication date
CN111367868B (en) 2023-12-29

Similar Documents

Publication Publication Date Title
CN110096660B (en) Method and device for loading page pictures and electronic equipment
CN111240653B (en) Interface document generation method, device and readable storage medium
CN107239701B (en) Method and device for identifying malicious website
CN108228799B (en) Object index information storage method and device
CN108009147B (en) Electronic book cover generation method, electronic device and computer storage medium
CN104348919A (en) Method and device for downloading file and browser
CN112711372B (en) Page response method in visual impairment mode, computing device and computer storage medium
CN108769157B (en) Message popup display method and device, computing equipment and computer storage medium
CN109343862B (en) Scheduling method and device of resource data of application
CN110515631B (en) Method for generating application installation data packet, server and computer storage medium
CN106649588B (en) Method, device and system for acquiring installed application program list
CN111431952B (en) Message pushing method, device and system, computer storage medium and electronic equipment
CN111367868B (en) File acquisition request processing method and device
CN111383038A (en) Advertisement display method and device of mobile terminal, mobile terminal and storage medium
CN110889073B (en) Page request response method, server and computer storage medium
CN111580881B (en) File loading method and device and electronic equipment
CN105630889B (en) Universal caching method and device
CN108595262B (en) Data processing method and device
CN103336671A (en) Method and equipment for acquiring data from network
CN110765392A (en) Data loading method and device, storage medium and terminal
CN111367921A (en) Data object refreshing method and device
CN106708516B (en) Method and device for calling external function by SO file
CN106446080B (en) Data query method, query service equipment, client equipment and data system
CN111143293B (en) Metadata acquisition method, device, equipment and computer readable storage medium
CN113434344A (en) File storage method and device, computing equipment and computer storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20231206

Address after: 300450 No. 9-3-401, No. 39, Gaoxin 6th Road, Binhai Science Park, Binhai New Area, Tianjin

Applicant after: 3600 Technology Group Co.,Ltd.

Address before: 100088 room 112, block D, 28 new street, new street, Xicheng District, Beijing (Desheng Park)

Applicant before: BEIJING QIHOO TECHNOLOGY Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant