Patent Description:
A finite number of connections may be executed concurrently from a mobile application. When the number of connections that are needed exceed the number of available connections, call requests, sometimes important call requests, are blocked while other less important call requests finished. For example, in a mobile application where thumbnail images are displayed, thirty or more thumbnails may need to be fetched from a server. However, other more important tasks must also be performed, such as maintaining updated content on the mobile application. If there are for example, ten connections available for the mobile application, the more important content update will be blocked until the thumbnail images are finished downloading. The downloading images may no longer be relevant to the mobile application, yet the low priority download takes precedent over the higher priority content update due to the first-come-first-serve nature of requests. This creates an unresponsive mobile application and a poor user experience.

Therefore, there is a need for a method for maximizing a number of connections that can be executed from a mobile application. D1 (<CIT>) proposes a browser download task management method. D2 (<CIT>) discloses an advertiser-supported interactive Web accelerator. D3 (<CIT>) relates to a method for context-aware portal connection allocation, in which a finite number of connections between a portal server and one or more backend systems are allocated.

Aspects of the present invention provide a method, an apparatus and a non-transitory computer readable medium, as set out by the appended set of claims.

While the method and apparatus for maximizing a number of connections that can be executed from a mobile application is described herein by way of example for several embodiments and illustrative drawings, those skilled in the art will recognize that the method and apparatus for maximizing a number of connections that can be executed from a mobile application is not limited to the embodiments or drawings described. It should be understood, that the drawings and detailed description thereto are not intended to limit embodiments to the particular form disclosed. As used herein, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words "include", "including", and "includes" mean including, but not limited to.

Techniques are disclosed for an apparatus and method for maximizing a number of connections that can be executed from a mobile application, according to embodiments of the invention. The disclosed method for maximizing a number of connections that can be executed from a mobile application, includes setting a priority for each call request that is possible from a mobile application. The priorities may be as simple as high and low and within each priority level, there may be secondary priorities rankings. For example, within the high priority category, there may be three or more secondary categories HP1, HP2, HP3, and the like, where HP1 is a higher priority call than HP2, and HP2 is a higher priority than HP3, and so on. Similarly, the low priority level may also include secondary low priority categories, such as LP1, LP2, LP3, and the like. The secondary priorities order calls that are waiting. If a first call request has a priority of HP3 and a second call request with a priority of HP2 is received after the HP3 call request is already in queue, the HP2 call request will be serviced ahead of the HP3 call request when a slot becomes available.

A number of allowable concurrent connections is determined for the mobile application. Each call request or response uses a connection. As used herein, the connection used by a call request or response is referred to as a "slot". A number of slots that may be run concurrently is allocated such that one slot for each priority level is reserved and remains available for authentication requests, re-authentication requests, and renewing token requests, referred to herein as a "reserved slot". When a low priority call request is received, if a slot is available, the slot is given to the call request. However, if no slot is available, then the call request is placed in a queue until a slot becomes available. When a high priority call request is received, it is given an available slot. However, if no slot is available, a low priority request that is currently executing is cancelled and placed in the queue and the high priority request is given the slot that was used by the low priority call. The reserved slots remain available for authentication requests, re-authentication requests, and renewing token requests.

Various embodiments of a method and apparatus for maximizing a number of connections that can be executed from a mobile application are described. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of claimed subject matter. However, it will be understood by those skilled in the art that claimed subject matter may be practiced without these specific details. In other instances, methods, apparatuses or systems that would be known by one of ordinary skill have not been described in detail so as not to obscure claimed subject matter.

Some portions of the detailed description that follow are presented in terms of algorithms or symbolic representations of operations on binary digital signals stored within a memory of a specific apparatus or special purpose computing device or platform. In the context of this particular specification, the term specific apparatus or the like includes a general-purpose computer once it is programmed to perform particular functions pursuant to instructions from program software. Algorithmic descriptions or symbolic representations are examples of techniques used by those of ordinary skill in the signal processing or related arts to convey the substance of their work to others skilled in the art. An algorithm is here, and is generally, considered to be a self-consistent sequence of operations or similar signal processing leading to a desired result. In this context, operations or processing involve physical manipulation of physical quantities. Typically, although not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared or otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as "processing," "computing," "calculating," "determining" or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic computing device. In the context of this specification, therefore, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.

<FIG> depicts a block diagram of an system <NUM> for maximizing a number of connections that can be executed from a mobile application, according to one or more embodiments of the invention. The system <NUM> includes a mobile device <NUM>, a server <NUM>, communicatively connected via network <NUM>.

The mobile device <NUM> is a computing device, such as a desktop computer, laptop, tablet computer, smartphone, smartwatch or other wearable, smart speaker with a screen, and the like. The mobile device <NUM> includes a Central Processing Unit (CPU) <NUM>, support circuits <NUM>, a display <NUM>, and a memory <NUM>. The CPU <NUM> may include one or more commercially available microprocessors or microcontrollers that facilitate data processing and storage. The various support circuits <NUM> facilitate the operation of the CPU <NUM> and include one or more clock circuits, power supplies, cache, input/output circuits, and the like. The memory <NUM> includes at least one of Read Only Memory (ROM), Random Access Memory (RAM), disk drive storage, optical storage, removable storage and/or the like. The memory <NUM> includes an operating system <NUM>, application <NUM>, a call manager <NUM>, a call classification manager <NUM>, stored call priorities <NUM>, and a queue <NUM>. The operating system <NUM> may include various commercially known operating systems. The server <NUM> may be in the cloud and may be the backend server for the application <NUM>. In some embodiments, there may be a plurality of servers <NUM>. Call requests from the application <NUM> may use network <NUM> to communication with server <NUM>.

The call classification manager <NUM> sets a priority for each type of network call request that may be made from the application <NUM>. For example, an authentication request or a call that affects the experience of a user, such as a synchronization (e.g., favoriting or deleting content) call may be classified as high priority calls. Displaying thumbnail images may be classified as high priority but may be considered secondary to an authentication call. As such, synchronization calls may be given an HP1 classification, while thumbnail display calls may be given an HP2 classification. Calls that may be temporarily delayed without noticeable impact on the user experience may be classified as low priority (LP1). The call classifications are stored as call priorities <NUM>.

The call manager <NUM> determines a number of allowable concurrent network connections for the application <NUM>. Each call request or response uses a connection (i.e., takes up one slot). The call manager <NUM> allocates a number of slots such that for each priority level, the call manager <NUM> allocates one slot , referred to as a "reserved slot". In some embodiments, the call manager <NUM> allocates reserved slots based on the needs of the application <NUM>. For example, the application <NUM> may only require one type of authentication. In such case, the call manager <NUM> would allocate one reserved slot. If the application <NUM> requires authentication and re-authentications, the call manager <NUM> may reserve two slots. When a call request is received, the call manager <NUM> processes the call request. If a slot is available, the slot is given to the call request and the call associated with the call request is executed. However, if no slot is available, then the call manager <NUM> determines the priority level of the call request using the call priorities <NUM>. If the call request is a low priority call, the call manager <NUM> places the low-priority call request in the queue <NUM>. However, if the call request is a high priority call request then the call manager <NUM> determines whether there is a low priority call among the calls that are in progress. If there are low-priority calls in progress, a low priority call is cancelled and placed in the queue <NUM> until a slot becomes available for its execution. In some embodiments, the call manager <NUM> selects the low priority call with the lowest secondary priority and cancels and queues said low-priority call. If the call request is a high priority call request and no slots are available, and the call manager <NUM> determines that all slots are being utilized for high priority call execution, then high priority call request is placed in queue <NUM>. If a high priority call request is received that requires a re-authentication and all slots are filled with high and low priority calls, the call manager <NUM> executes the re-authentication request in a reserved slot and executes the high priority in a slot according to the above description.

When a call completes, the call manager <NUM> gives the newly available slot to the call request in the queue <NUM> with the highest priority.

<FIG> depicts a flow diagram of a method <NUM> for maximizing a number of connections that can be executed from a mobile application, according to one or more embodiments of the invention. The method <NUM> starts at step <NUM> and proceeds to step <NUM>.

At step <NUM>, a plurality of connection slots is allocated for network calls. As an example, a mobile application allows ten concurrent network connections. The number of concurrent network connections allowed may be defined by the mobile device. In the present example, where there are ten slots allowed, two slots may be reserved, one for each priority level. In some embodiments, the number of reserved and non-reserved slots is configurable based on the needs of the mobile application. For example, if the mobile application simply requires authentication, one reserve slot may be allocated. However, if the mobile application requires authentication and re-authentication, two reserve slots may be allocated.

At step <NUM>, a call request is received. The call request is from the mobile application and requires a network connection.

At step <NUM>, it is determined whether there are any non-reserved slots available for the call request. If there are available slots, then at step <NUM>, the call is executed using one of the available slots. However, if there are no non-reserved slots available, then the method <NUM> proceeds to step <NUM>.

At step <NUM>, it is determined whether the call request is a high priority call request or a low priority call request. If the call request is a low priority call request, then the method proceeds to step <NUM>, where the call request is placed in a queue until a connection slot becomes available for the call request. However, if the call request is a high priority call request, then the method <NUM> proceeds to step <NUM>.

At step <NUM>, it is determined whether there are any low priority calls in progress (i.e., executing in one of the connection slots). If there is a low priority call in progress, then at step <NUM>, the low priority call is canceled and placed in the queue until a connection slot becomes available for the call request. At step <NUM>, the high priority call is initiated in the slot that was just made available by canceling the low priority call and the method <NUM> proceeds to step <NUM>.

However, if at step <NUM>, it is determined that no low priority calls are in progress (i.e., all calls in progress are high priority calls), then the method <NUM> proceeds to step <NUM>, where the call request is placed in a queue until a connection slot becomes available for the call request.

<FIG> depict connections slots <NUM> during processing of incoming calls, according to one or more embodiments of the invention. In <FIG>, there are ten (<NUM>) connection slots available. Slots <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are allocated as non-reserved slots. Slots <NUM> and <NUM> are reserved, for special call requests, such as authentication call requests, re-authentication call requests, renewing token requests, and the like, when needed and to avoid blocking high priority calls. Although the slots are numbered for ease of description, in practice, there is no order to the connection slots.

<FIG> depicts the connection slots <NUM> while a number of network calls are being executed. Slots <NUM>, <NUM>, <NUM>, and <NUM> are high priority calls in execution. Slots <NUM>, <NUM>, <NUM>, and <NUM> are low priority calls in execution. Slots <NUM> and <NUM> are free in the event an authentication/re-authentication/token call request is received.

<FIG> depicts the transition from connection slots <NUM> in <FIG> to connection slots <NUM> when new high priority calls are received. In <FIG>, two new high priority calls are initiated. Slots <NUM>, <NUM>, <NUM>, and <NUM> are already being used for high priority calls in execution. Slots <NUM> and <NUM> are taken for execution of the two new high priority calls. The low priority calls that had been executing in slots <NUM> and <NUM> are canceled and put into a queue for execution when slots are freed up Slots <NUM> and <NUM> remain in use for the low priority calls in execution. Slots <NUM> and <NUM> remain free in the event an authentication/re-authentication/token call request is received.

<FIG> depicts the transition from the connection slots in <FIG> to connection slots <NUM> where a number of high priority calls complete and low priority calls from in queue are placed in the newly available slots. Three high priority calls complete. As such slots <NUM>, <NUM>, and <NUM> remain in use for high priority calls in execution. Slots <NUM> and <NUM> are able to be used for low priority calls with the additional slots <NUM>, <NUM>, and <NUM> available for low priority calls. Slots <NUM> and <NUM> are free in case a new high priority call request is received. With five slots available for low priority calls, the two low priority calls from <FIG> continue to execute while three low priority calls may be pulled off the queue. In the present example, there are five low priority calls in the queue, with priorities of LP1, LP3, LP2, LP2, and LP1, respectively. As such, the low priority calls with higher secondary priorities (LP1 and LP2) are executed first. As such, LP1, LP1, and LP2 are executed in slots <NUM>, <NUM>, and <NUM>. Now, three high priority calls are executing, five low priority calls are executing, two slots (slot <NUM> and <NUM>) remain free in the event an authentication/re-authentication/token call request is received, and two low priority calls still in the queue.

<FIG> depicts the transition from the connection slots in <FIG> to connection slots <NUM> where one high priority call completes. Slots <NUM> and <NUM> are being used for high priority calls in execution. Slot <NUM> is freed when the high priority call completes. As such a low priority call that is still in the queue may use slot <NUM>. The low priority call with the highest secondary priority (L2) is selected to be executed in slot <NUM>. Slots <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are being used for low priority calls in execution. Slots <NUM> and <NUM> are free in the event an authentication/re-authentication/token call request is received.

<FIG> depicts the transition from the connection slots in <FIG> to connection slots <NUM> where one more high priority call completes. Slot <NUM> is still being used for a high priority call in execution. Slot <NUM> is freed when the high priority call in slot <NUM> completes. As such a low priority call that is still in the queue may use slot <NUM>. Slots <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are being used for low priority calls in execution. Slots <NUM> and <NUM> remain free in the event an authentication/re-authentication/token call request is received.

<FIG> depicts the transition from the connection slots in <FIG> to connection slots <NUM> where a reserved slot must be utilized. Slot <NUM> is being used for a high priority call in execution. Slots <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are being used for low priority calls in execution. Slots <NUM> and <NUM> are free in the event a new high priority call request is received. The high priority call request in slot <NUM> requires a re-authentication. All of the slots are in use. As such, the authentication call uses the reserved slot <NUM>. The slot <NUM> may be used immediately to avoid delay in waiting for a slot to become available. When the re-authentication call is complete, the high priority call may proceed and the reserved slot <NUM> if free and waiting for a next authentication/re-authentication/token call request.

<FIG> depicts a computer system that can be used to implement the method of <FIG> in various embodiments of the present invention. Various embodiments of a method and apparatus for maximizing a number of connections that can be executed from a mobile application, as described herein, may be executed on one or more computer systems, which may interact with various other devices. One such computer system is computer system <NUM> illustrated by <FIG>, which may in various embodiments implement any of the elements or functionality illustrated in <FIG>. In various embodiments, computer system <NUM> may be configured to implement methods described above. The computer system <NUM> may be used to implement any other system, device, element, functionality or method of the above-described embodiments. In the illustrated embodiments, computer system <NUM> may be configured to implement method <NUM>, as processor-executable executable program instructions <NUM> (e.g., program instructions executable by processor(s) <NUM>) in various embodiments.

In the illustrated embodiment, computer system <NUM> includes one or more processors <NUM> coupled to a system memory <NUM> via an input/output (I/O) interface <NUM>. Computer system <NUM> further includes a network interface <NUM> coupled to I/O interface <NUM>, and one or more input/output devices <NUM>, such as cursor control device <NUM>, keyboard <NUM>, and display(s) <NUM>. In various embodiments, any of components may be utilized by the system to receive user input described above. In various embodiments, a user interface (e.g., user interface <NUM>) may be generated and displayed on display <NUM>. In some cases, it is contemplated that embodiments may be implemented using a single instance of computer system <NUM>, while in other embodiments multiple such systems, or multiple nodes making up computer system <NUM>, may be configured to host different portions or instances of various embodiments. For example, in one embodiment some elements may be implemented via one or more nodes of computer system <NUM> that are distinct from those nodes implementing other elements. In another example, multiple nodes may implement computer system <NUM> in a distributed manner.

In different embodiments, computer system <NUM> may be any of various types of devices, including, but not limited to, a personal computer system, desktop computer, laptop, notebook, or netbook computer, mainframe computer system, handheld computer, workstation, network computer, a camera, a set top box, a mobile device, a consumer device, video game console, handheld video game device, application server, storage device, a peripheral device such as a switch, modem, router, or in general any type of computing or electronic device.

In various embodiments, computer system <NUM> may be a uniprocessor system including one processor <NUM>, or a multiprocessor system including several processors <NUM> (e.g., two, four, eight, or another suitable number). Processors <NUM> may be any suitable processor capable of executing instructions. For example, in various embodiments processors <NUM> may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs), such as the x96, PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. In multiprocessor systems, each of processors <NUM> may commonly, but not necessarily, implement the same ISA.

System memory <NUM> may be configured to store program instructions <NUM> and/or data <NUM> accessible by processor <NUM>. In various embodiments, system memory <NUM> may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/flash-type memory, persistent storage (magnetic or solid state), or any other type of memory. In the illustrated embodiment, program instructions and data implementing any of the elements of the embodiments described above may be stored within system memory <NUM>. In other embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media or on similar media separate from system memory <NUM> or computer system <NUM>.

In one embodiment, I/O interface <NUM> may be configured to coordinate I/O traffic between processor <NUM>, system memory <NUM>, and any peripheral devices in the system, including network interface <NUM> or other peripheral interfaces, such as input/output devices <NUM>, In some embodiments, I/O interface <NUM> may perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory <NUM>) into a format suitable for use by another component (e.g., processor <NUM>). In some embodiments, I/O interface <NUM> may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface <NUM> may be split into two or more separate components, such as a north bridge and a south bridge, for example. Also, in some embodiments some or all of the functionality of I/O interface <NUM>, such as an interface to system memory <NUM>, may be incorporated directly into processor <NUM>.

Network interface <NUM> may be configured to allow data to be exchanged between computer system <NUM> and other devices attached to a network (e.g., network <NUM>), such as one or more external systems or between nodes of computer system <NUM>. In various embodiments, network <NUM> may include one or more networks including but not limited to Local Area Networks (LANs) (e.g., an Ethernet or corporate network), Wide Area Networks (WANs) (e.g., the Internet), wireless data networks, some other electronic data network, or some combination thereof. In various embodiments, network interface <NUM> may support communication via wired or wireless general data networks, such as any suitable type of Ethernet network, for example; via telecommunications/telephony networks such as analog voice networks or digital fiber communications networks; via storage area networks such as Fibre Channel SANs, or via any other suitable type of network and/or protocol.

Input/output devices <NUM> may, in some embodiments, include one or more display terminals, keyboards, keypads, touch pads, scanning devices, voice or optical recognition devices, or any other devices suitable for entering or accessing data by one or more computer systems <NUM>. Multiple input/output devices <NUM> may be present in computer system <NUM> or may be distributed on various nodes of computer system <NUM>. In some embodiments, similar input/output devices may be separate from computer system <NUM> and may interact with one or more nodes of computer system <NUM> through a wired or wireless connection, such as over network interface <NUM>.

In some embodiments, the illustrated computer system may implement any of the methods described above, such as the method illustrated by the flowchart of <FIG>. In other embodiments, different elements and data may be included.

Those skilled in the art will appreciate that computer system <NUM> is merely illustrative. In particular, the computer system and devices may include any combination of hardware or software that can perform the indicated functions of various embodiments, including computers, network devices, Internet appliances, PDAs, wireless phones, pagers, etc. Computer system <NUM> may also be connected to other devices that are not illustrated, or instead may operate as a stand-alone system. In addition, the functionality provided by the illustrated components may in some embodiments be combined in fewer components or distributed in additional components. Similarly, in some embodiments, the functionality of some of the illustrated components may not be provided and/or other additional functionality may be available.

Those skilled in the art will also appreciate that, while various items are illustrated as being stored in memory or on storage while being used, these items or portions of them may be transferred between memory and other storage devices for purposes of memory management and data integrity. Alternatively, in other embodiments some or all of the software components may execute in memory on another device and communicate with the illustrated computer system via inter-computer communication. Some or all of the system components or data structures may also be stored (e.g., as instructions or structured data) on a computer-accessible medium or a portable article to be read by an appropriate drive, various examples of which are described above. In some embodiments, instructions stored on a computer-accessible medium separate from computer system <NUM> may be transmitted to computer system <NUM> via transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as a network and/or a wireless link. Various embodiments may further include receiving, sending or storing instructions and/or data implemented in accordance with the foregoing description upon a computer-accessible medium or via a communication medium. In general, a computer-accessible medium may include a storage medium or memory medium such as magnetic or optical media, e.g., disk or DVD/CD-ROM, volatile or non-volatile media such as RAM (e.g., SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc..

Claim 1:
A computer implemented method (<NUM>) for prioritising call requests executed by a mobile application, comprising:
allocating (<NUM>) for the mobile application a plurality of connection slots for a plurality of types of network calls, wherein allocating the connection slots comprises reserving one or more connection slots;
receiving (<NUM>) a call request;
determining (<NUM>) whether a connection slot of the plurality of connection slots is available for the call request;
executing (<NUM>) a call based on the call request when a connection slot is available;
processing the call request when a connection slot is not available, where processing the request comprises:
determining (<NUM>) a priority level for the call request;
when the determined priority level is a low priority, putting (<NUM>) the call request in a queue for later processing; and
when the determined priority level is a high priority:
when a low priority call is in progress, performing the steps of:
canceling (<NUM>) the in-progress low priority call;
placing (<NUM>) the cancelled low priority call in a queue for later processing; and
executing (<NUM>) the high priority call; and
when no low priority call is in progress, placing (<NUM>) the high
priority call request in the queue;
wherein the method further comprises:
when a high priority call requires an authentication, a re-authentication, or a renewal of a token, and no connections slots are available, executing the authentication, the re-authentication or the renewal of a token in a reserved connection slot.