Implementing asynchronous processes on a mobile client

Abstract

Systems and methods are provided perform an asynchronous process in a mobile client when not connected to an enterprise server. An application on a mobile client receives a request from a user to perform a task that is ordinarily performed by the enterprise server, such as decompressing a large data file. The mobile client determines, however, that it is not connected to the enterprise server. Instead, the application spawns a thread to complete the task asynchronously. Accordingly, the task need not be performed synchronously, thus making the user wait, when the mobile client is disconnected from the enterprise server.

Description

FIELD OF THE INVENTION

One embodiment is directed to customer relationship management (“CRM”), and more particularly directed to a mobile client operating a CRM application.

BACKGROUND INFORMATION

In recent years, the annual rate of increase among physicians has remained relatively flat while the number of pharmaceutical sales representatives has grown considerably overall, even accounting for recent reductions in field force sizes. As a result, sales call effectiveness has waned in the face of a changing market and physicians' increasingly busy schedules, forcing life sciences organizations to transform their sales and marketing capabilities. Pharmaceutical companies face stiff challenges in terms of completion, cost escalation and reduction in margins, while promoting their products by sending out sales representatives to doctors, hospitals and other medical organizations. Typically the sales representatives, in the few minutes that they get with the audience/doctors, orally explain the complicated details of the medical product and then give handouts, such as presentation material on the product in paper form. A very likely result of such an approach is that after the session the audience would have already forgotten much, depending on the oral presentation skills of the representative, and the handouts will most likely be thrown away. A more effective approach would be to provide the sales representative with an animated presentation that would be more engaging for the little time allotted to the presentation. The sales representative could give the presentation on a mobile client such as a tablet personal computer (“PC”).

However, the mobile thin client may need to perform computationally intense tasks such a decompressing large data files. Such tasks should be carried out asynchronously, allowing the user to continue with other tasks, while the background process performs the required decompression. Typically the server is required to start the asynchronous process, and since a mobile client does not have the server running, the creation of an asynchronous process is not possible. In this case, the decompression must take place synchronously, and the user must wait until the process is complete to use the mobile client again.

SUMMARY OF THE INVENTION

One embodiment is a system for performing an asynchronous process in a mobile client when not connected to an enterprise server. The system receives a request to perform a task ordinarily performed by the enterprise server. The system determines, however, that the mobile client is not connected to the enterprise server. The system instead spawns a thread from a base application to complete the task asynchronously. The base application receives a notification that the task was completed by the thread.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system that can implement a personalized content delivery (“PCD”) system in accordance with an embodiment;

FIG. 2 illustrates a method of providing personalized content delivery and analytics in accordance with an embodiment;

FIG. 3 illustrates example call details user interface (“UI”) of the PCD system in accordance with an embodiment;

FIG. 4A illustrates a typical enterprise network;

FIG. 4B illustrates a mobile client disconnected from an enterprise network in accordance with an embodiment; and

FIG. 5 illustrates a method performing a task asynchronously on a mobile client when not connected to an enterprise server in accordance with an embodiment.

DETAILED DESCRIPTION

Systems and methods are provided that generate an asynchronous process locally using a thread spawned on a mobile client. Typically, to perform an asynchronous process as part of an enterprise application system (“EAS”) such as a customer relationship management (“CRM”) system, application code creates and invokes a job on an enterprise server in the EAS to create a new thread to perform the asynchronous process. However, to do this the server needs to be connected and running. Instead, a mobile client (e.g., a personalized content delivery (“PCD”) system as described below) creates a new thread itself in a manner that does not require the server to be connected or running. The mobile client utilizes a core Operating System Dependent (“OSD”) class function OSDCreateThread that would create a separate thread to execute the asynchronous task. As a parameter it takes the function name from which the thread would start its execution.

FIG. 1 is a block diagram of a system 10 that can implement an embodiment of a PCD system. System 10 includes a bus 12 or other communication mechanism for communicating information, and a processor 22 coupled to bus 12 for processing information. Processor 22 may be any type of general or specific purpose processor. System 10 further includes a memory 14 for storing information and instructions to be executed by processor 22. Memory 14 can be comprised of any combination of random access memory (“RAM”), read only memory (“ROM”), static storage such as a magnetic or optical disk, or any other type of computer readable media. System 10 further includes a communication device 20, such as a network interface card, to provide access to a network. Therefore, a user may interface with system 10 directly, or remotely through a network or any other method.

Computer readable media may be any available media that can be accessed by processor 22 and includes both volatile and nonvolatile media, removable and non-removable media, and communication media. Communication media may include computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.

Processor 22 is further coupled via bus 12 to a display 24, such as a Liquid Crystal Display (“LCD”), for displaying information to a user. A cursor control device 28, such as a touch screen, is further coupled to bus 12 to enable a user to interface with system 10. In one embodiment, system 10 is a tablet PC.

In one embodiment, memory 14 stores software modules that provide functionality when executed by processor 22. The modules include an operating system 15 that provides operating system functionality for system 10. The modules further include a PCD module 100. This module is described in greater detail below. System 10 may further coupled to a database 17 for storing additional data.

FIG. 2 illustrates a flow diagram of the functionality of PCD module 100 in accordance with an embodiment. In one embodiment, the functionality of the flow diagram of FIG. 2, and FIG. 5 below, is implemented by software stored in memory and executed by a processor. In other embodiments, the functionality may be performed by hardware (e.g., through the use of an application specific integrated circuit (“ASIC”), a programmable gate array (“PGA”), a field programmable gate array (“FPGA”), etc.), or any combination of hardware and software. Initially, digital presentation content is loaded on PCD system 10 (200). Digital presentation content may be used by brand managers, marketing managers and sales operation managers as a sales communication tool for more effective communication in order to acquire, retain and develop profitable customer relationships and improve marketing and sales effectiveness. Examples of digital presentation content includes presentations in the form of Flash files, PowerPoint files, word documents, movie files, Portable Document files, etc. A “message” refers to a slide, page or segment of a presentation conveying a specific message that managers wish to track.

After loading the digital presentation content on PCD system 10, an administrator or manager may then create a “messaging plan” for the sales representative to use (210). The messaging plan is a sequence of digital presentation content used to deliver the tracked message regarding the product. When a sales representative makes a sales call, a messaging plan is selected on the PCD system 10 and details about the call are entered into the system (220). During the sales call, the PCD system 10 dynamically and automatically collects analytical data such as time spent by the sales representative on each presentation message and the sequence of the messages (230). For example, PCD system 10 may include a timer (not shown) for recording the time spent on each message or segment of the presentation.

Once the sales presentation is over, the analytical data collected during the session is written back to database 17 (240). After the call, the sales representative may also enter additional details about the sales call such a samples and promotional items left with the doctor or audience, issues about the call, or questionnaires dropped during the call. FIG. 3 illustrates an example screenshot of a user interface (“UI”) 310 for PCD system 10 where the sales representative can enter call details in promotional items section 320, samples dropped section 330, issues section 340, and questionnaires section 350. The screenshot UI 310 displays in presentation details section 360 the messages that were presented to the contact in the detailing session, the sequence of presented messages and their parent messaging plans (i.e., the message plan to which the messages belong), and duration of presentation of each message. Ultimately, information about the sales call and other sales calls regarding the same product may be used to develop marketing strategies for that product based on the success of the sales calls.

The materials for giving a presentation, such as the messages or presentations themselves, may be stored in a compressed format on PCD system 10. To decompress the material asynchronously so that the sales representative may continue using PCD system 10, the decompression is typically spawned by an enterprise server, such as a CRM server (e.g., server running Oracle® Life Sciences). FIG. 4A illustrates a typical scenario where PCD system 10 and presentation application 410 are connected to enterprise server 420 via network 430 (e.g., the Internet). In this scenario, enterprise server 420 performs a decompression task 440. This scenario occurs in an architecture where the client natively does all actions synchronously and submits all asynchronous jobs to the server. The server adds each request to a queue and processes it as first-in, first-out (“FIFO”).

However, there may be a scenario where PCD system 10 cannot connect to enterprise server 420, such as when a sales representative is on a sales call in a customer's office. FIG. 4B illustrates a scenario where PCD system 10 has determined it is not connected to enterprise server 420. Instead of making the sales representative wait for decompression task 440 to be performed synchronously by the presentation application 410, an embodiment spawns a thread 450 off of presentation application 410 to complete decompression task 440. Alternatively to decompression task 440, the asynchronous task may be any time consuming task that does not require user interaction, such as processing business flow logic or preparing reports.

FIG. 5 illustrates a method for performing an asynchronous task on a mobile client (e.g., PCD system 10) when not connected to an enterprise server, in accordance with an embodiment. The mobile client first receives a request to perform an asynchronous task, such as decompressing a data file (510). This request may be in response to a sales representative launching a presentation. The mobile client then determines that is not connected to an enterprise server to perform the task asynchronously (520). Instead, the mobile client spawns a thread to perform the task asynchronously (530). An application, such as presentation application 410, later receives a notification when the thread has finished performing the task (540).

Example code for implementing an embodiment is presented below:

#include <utlosd.h>
#include “physmod.h”
scfErrCode errCode = OSDCreateThread(PrepareForDecompression,
this, 0, OSD_THRD_NO_CTX, &threadId);
ccfErrCode PrepareForDecompression(void* p)
{
CSSLSPCDSvc* var = (CSSLSPCDSvc*)p;
CSSModelPhysDef::SetThreadModel(var->m_pModel);
BOOL         bDone = true;
while(bDone)
{
// Do the actual tasks here( in this case: Decompress files)
bDone = false;
}
return 0;
}

The thread model should be set explicitly, as below:

• DOCHILD (m_pModel, GetBusObj (SStext(“Admin Sales Tool”), pBOLitAdmin));

Since different threads may be accessing the same file, there may be synchronization conflicts. To avoid these conflicts, the files should be locked while in use, and unlocked after use, as shown in the code below:

#include <osdsync.h>
#include <ccfsync.h>
CCFLock m_oLock;
m_oLock.Lock( );
//Do the processing of file here
m_oLock.Unlock( );

The mobile client may try to create two threads simultaneously, thus synchronization is needed to create only one thread at a time. Synchronization may be ensured by creating a static variable (e.g., static BOOL m_isSyncInProgress), which would be set to TRUE as soon as the new thread is started. Since this variable is static, any further attempt to create a thread would fail by implementing the following code:

BOOL CSSLSPCDSvc::DoCanInvokeMethod (const SSchar*
pMethodName)
{
.......................................
.......................................
else if (SSstrcmp(pMethodName,
METHOD_CREATETHREADTODECOMPRESS)== 0)
{
if(m_isSyncInProgress)
return FALSE;
else
return TRUE;
}
}

When the thread ends after decompressing the data, the static variable is set to FALSE, allowing other users can create the thread.

Thus, a mechanism is implemented to enable a mobile client to spawn a thread to perform a task asynchronously. Accordingly, a user does not have to wait for the task to be performed synchronously when the mobile client is not connected to an enterprise server that ordinarily performs that same task.

Some embodiments of the invention have been described as computer-implemented processes. It is important to note, however, that those skilled in the art will appreciate that the mechanisms of the invention are capable of being distributed as a program product in a variety of forms. The foregoing description of example embodiments is provided for the purpose of illustrating the principles of the invention, and not in limitation thereof, since the scope of the invention is defined solely by the appended claims.

Claims

1. A method for performing an asynchronous process in a mobile client when not connected to an enterprise server, comprising: launching a presentation that comprises a data file stored in a compressed format, one or more messages, and a sequence of the one or more messages;receiving a request to perform decompression of the data file ordinarily performed by the enterprise server, in response to the launching of the presentation;determining the mobile client is not connected to the enterprise server;creating a thread from a base application to complete the decompression of the data file asynchronously utilizing a class function, wherein the class function takes a function name from which the thread starts its execution as a parameter;collecting analytical data on the one or more messages and the sequence of the one or more messages while the thread completes the decompression of the data file asynchronously; andreceiving a notification that the decompression of the data file was completed by the thread.

2. The method of claim 1, wherein the enterprise server is a customer relationship management (“CRM”) server.

3. The method of claim 1, wherein the mobile client is a personalized content delivery (“PCD”) system.

4. The method of claim 1, wherein the base application is an applet.

5. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to perform an asynchronous process in a mobile client when not connected to an enterprise server by: launching a presentation that comprises a data file stored in a compressed format, one or more messages, and a sequence of the one or more messages;receiving a request to perform decompression of the data file ordinarily performed by the enterprise server, in response to the launching of the presentation;determining the mobile client is not connected to the enterprise server;creating a thread from a base application to complete the decompression of the data file asynchronously utilizing a class function, wherein the class function takes a function name from which the thread starts its execution as a parameter;collecting analytical data on the one or more messages and the sequence of the one or more messages while the thread completes the decompression of the data file asynchronously; andreceiving a notification that the decompression of the data file was completed by the thread.

6. The non-transitory computer-readable medium of claim 5, wherein the enterprise server is a customer relationship management (“CRM”) server.

7. The non-transitory computer-readable medium of claim 5, wherein the mobile client is a personalized content delivery (“PCD”) system.

8. The non-transitory computer-readable medium of claim 5, wherein the base application is an applet.

9. A system for performing an asynchronous process in a mobile client when not connected to a customer relationship management (“CRM”) server, comprising: a processor;an application running on the mobile client; anda thread for performing data decompression of a data file asynchronously of the application, wherein the application creates the thread in response to a launching of a presentation that comprises the data file, one or more messages, and a sequence of the one or more messages after determining that the mobile client is not connected to the CRM server utilizing a class function, wherein the class function takes a function name from which the thread starts its execution as a parameter;wherein the application is also configured to collect analytical data on the one or more messages and the sequence of the one or more messages while the thread performs the decompression of the data file asynchronously.

10. A system for performing an asynchronous process in a mobile client when not connected to an enterprise server, comprising: means for launching a presentation that comprises a data file stored in a compressed format, one or more messages, and a sequence of the one or more messages;means for receiving a request to perform decompression of the data file ordinarily performed by the enterprise server, in response to the launching of the presentation;means for determining the mobile client is not connected to the enterprise server;means for creating a thread from a base application to complete the decompression of the data file asynchronously utilizing a class function, wherein the class function takes a function name from which the thread starts its execution as a parameter;means for collecting analytical data on the one or more messages and the sequence of the one or more messages while the thread completes the decompression of the data file asynchronously; andmeans for receiving a notification that the decompression of the data file was completed by the thread.

11. The system of claim 9, wherein the mobile client is a personalized content delivery (“PCD”) system.

12. The system of claim 9, wherein the application is an applet.

13. The system of claim 10, wherein the enterprise server is a customer relationship management (“CRM”) server.

14. The system of claim 10, wherein the mobile client is a personalized content delivery (“PCD”) system.

15. The system of claim 10, wherein the base application is an applet.