# US 10,313,253 B2 · Non-blocking request processing method and device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,313,253 B2 - Document ID: US10313253B2 - Status: Granted - Kind: B2 - Application number: 15/535,647 - Filed: 2016-06-15 - Published: 2018-03-01 - Granted: 2019-06-04 - Earliest claimed: 2016-03-07 - Assignees: Boe Technology Group Co., Ltd. - Applicants: Boe Technology Group Co., Ltd. - Inventors: Junjie Zhao; Zhenpeng Guo - Web page: https://patentgrep.com/patent/US10313253B2 ## CPC - H04L 47/2466: using signalling traffic - H04L 43/106: using time related information in packets, e.g. by adding timestamps - H04L 67/62: Establishing a time schedule for servicing the requests - H04L 69/28: Timers or timing mechanisms used in protocols - H04W 28/02: Traffic management, e.g. flow control or congestion control - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A non-blocking request processing method and a device. The non-blocking request processing method includes: receiving a non-blocking request from a requestor; determining an execution completion estimated timestamp of the non-blocking request; and sending the execution completion estimated timestamp to the requestor. ## Claims ### Claim 1 A non-blocking request processing method, comprising: receiving a non-blocking request from a requestor; determining an execution completion estimated timestamp indicating the normal completion time of the non-blocking request according to a determination strategy of the execution completion estimated timestamp; and sending the execution completion estimated timestamp to the requestor, wherein determining of the execution completion estimated timestamp indicating the normal completion time of the non-blocking request according to a determination strategy of the execution completion estimated timestamp, includes: determining the execution completion estimated timestamp of the non-blocking request received according to the execution completion estimated timestamp of various categories of non-blocking requests. ### Claim 2 (depends on 1) The non-blocking request processing method according to claim 1, wherein the determination strategy of the execution completion estimated timestamp is determined according to at least one of: an indication of the requestor; a current state of the receiver; and an execution parameter of the non-blocking request. ### Claim 3 (depends on 1) The non-blocking request processing method according to claim 1, wherein determining of the execution completion estimated timestamp of the non-blocking request according to a determination strategy of the execution completion estimated timestamp, includes: calculating the execution completion estimated timestamp of the non-blocking request according to a predetermined calculation strategy of the execution completion estimated timestamp, the predetermined calculation strategy of the execution completion estimated timestamp being used for calculating the execution completion estimated timestamp according to at least one of a request ideal execution timestamp of the non-blocking request, task priority of the non-blocking request, and receiver load capacity. ### Claim 4 (depends on 3) The non-blocking request processing method according to claim 3, wherein the receiver load capacity includes at least one of: a processor occupancy rate, a memory occupancy rate, and a network occupancy rate. ### Claim 5 (depends on 4) The non-blocking request processing method according to claim 4, wherein calculating of the execution completion estimated timestamp includes: calculating the execution completion estimated timestamp of the non-blocking request according to the ideal execution timestamp of the non-blocking request, a delay timestamp of the task priority corresponding to the non-blocking request, and a delay timestamp corresponding to the receiver load capacity. ### Claim 6 (depends on 1) The non-blocking request processing method according to claim 1, wherein determining of the execution completion estimated timestamp of the non-blocking request according to a determination strategy of the execution completion estimated timestamp, includes: determining the execution completion estimated timestamp of the non-blocking request according to an execution completion timestamp of various categories of historical requests recorded. ### Claim 7 (depends on 6) The non-blocking request processing method according to claim 6, wherein determining of the execution completion estimated timestamp of the non-blocking request according to an execution completion timestamp of various categories of historical requests recorded, includes: selecting at least one historical request that matches with the non-blocking request; retrieving a historical execution completion timestamp of the at least one historical request; and determining the execution completion estimated timestamp of the non-blocking request, according to the historical execution completion timestamp of the at least one historical request. ### Claim 8 (depends on 7) The non-blocking request processing method according to claim 7, wherein the at least one historical request that matches with the non-blocking request is selected according to a request type of the non-blocking request, or according to the request type and a request operation object of the non-blocking request. ### Claim 9 (depends on 7) The non-blocking request processing method according to claim 7 wherein determining of the execution completion estimated timestamp of the non-blocking request, according to the historical execution completion timestamp of the at least one historical request includes: determining a maximum value of the historical execution completion timestamp of the plurality of historical requests as the execution completion estimated timestamp of the non-blocking request. ### Claim 10 (depends on 1) The non-blocking request processing method according to claim 1, wherein determining of the execution completion estimated timestamp of the non-blocking request received according to the execution completion estimated timestamp of various categories of non-blocking requests, includes: categorizing the non-blocking request received, according to the request type of the non-blocking request, or according to the request type and the request operation object of the non-blocking request, to determine the request category of the non-blocking request received, and taking the preset execution completion estimated timestamp corresponding to the request category as the execution completion estimated timestamp of the non-blocking request received. ### Claim 11 (depends on 1) The non-blocking request processing method according to claim 1, wherein, sending of the execution completion estimated timestamp to the requestor, includes: including the execution completion estimated timestamp in a response primitive, and sending the execution completion estimated timestamp to the requestor through the response primitive. ### Claim 12 (depends on 1) The non-blocking request processing method according to claim 1, further comprising: creating a request resource and a resource index after receiving the non-blocking request from the requestor; and sending the resource index to the requestor. ### Claim 13 (depends on 12) The non-blocking request processing method according to claim 12, wherein the resource index and the execution completion estimated timestamp are included in a response primitive, and the resource index and the execution completion estimated timestamp are sent to the requestor through the response primitive. ### Claim 14 (depends on 1) The non-blocking request processing method according to claim 1, further comprising: sending the execution result of the non-blocking request to the requestor, after the execution completion estimated timestamp, and after the execution result retrieving request of the non-blocking request from the requestor is received. ### Claim 15 A non-blocking request processing method, comprising: sending a non-blocking request to a receiver; and receiving an execution completion estimated timestamp indicating the normal completion time of the non-blocking request determined according to a determination strategy of the execution completion estimated timestamp from the receiver, wherein the execution completion estimated timestamp of the non-blocking request received is determined according to the execution completion estimated timestamp of various categories of non-blocking requests. ### Claim 16 (depends on 15) The non-blocking request processing method according to claim 15, further comprising: timing the execution completion estimated timestamp, and after completion of the timing of the execution completion estimated timestamp, sending an execution result retrieving request to the receiver. ### Claim 17 (depends on 15) The non-blocking request processing method according to claim 15, wherein, the receiving an execution completion estimated timestamp of the non-blocking request from the receiver is implemented through a response primitive. ### Claim 18 (depends on 15) The non-blocking request processing method according to claim 15, further comprising: receiving, from the receiver, a resource index of a request resource created for the non-blocking request, the receiving an execution completion estimated timestamp of the non-blocking request from the receiver and the receiving, from the receiver, a resource index of a request resource created for the non-blocking request being both implemented through the response primitive.