|Publication number||US7792795 B1|
|Application number||US 10/463,161|
|Publication date||Sep 7, 2010|
|Filing date||Jun 17, 2003|
|Priority date||Jun 17, 2003|
|Publication number||10463161, 463161, US 7792795 B1, US 7792795B1, US-B1-7792795, US7792795 B1, US7792795B1|
|Inventors||Tanya Swartz, Srikanth R. Avadhanam, Gagan Chopra|
|Original Assignee||Microsoft Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (22), Non-Patent Citations (8), Referenced by (6), Classifications (4), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates to context information. More specifically, the present invention relates to a system which aggregates and abstracts context information from a plurality of different sources and makes it available to requesting applications.
The mobile business space is a business environment in which employees, contractors or other users communicate with one another using mobile devices, such as cellular telephones, palmtop computers, laptop computers, personal digital assistances (PDAs) etc. In such a business environment, contextual information can be critically important in running a business in an efficient manner, and in a manner which is satisfactory to the customers of the business.
However, building business software and computing solutions to satisfy the needs of this business environment is challenging, expensive, and time consuming. The following scenario illustrates some of the challenges associated with this business environment. Assume that a television repair company conducts business by sending technicians to customer sites to fix problems with the customers' televisions. All customer calls are directed through a central call center. A dispatcher receives a call at the call center from a customer whose television has suddenly stopped displaying color. The customer insists that a technician make a call the same day in order to address the problem. In order to assign an appropriate technician to service the customer's call, the dispatcher would desirably know which technician is most qualified, which one has time in his or her schedule to service the customer's call today, which technician is the most affordable, given the previous constraints, and which technician is the closest to the customer. In other words, the dispatcher would desirably know the context associated with the technicians prior to assigning a technician to the customer's call.
However, all of this information currently comes from a wide variety of different sources, which are not easily accessed and obtained. In order to access this wide variety of different sources, a developer must have knowledge of each of the systems which provide different portions of the desired information, know how to interact with those systems, and know how to obtain the relevant information from those systems. This can be quite difficult since the context data sources can vary widely including, by way of example, user personnel files, calendaring or scheduling programs, geographic location devices, cellular networks, mobile devices, etc.
The present system aggregates information from a plurality of different context sources. The present system also makes that aggregated information available to requesting components by abstracting it into a generalized form. Thus, the developer of a context-aware application need only know how to interact with the context service of the present invention, rather than knowing how to interact with each and every one of the context sources.
In one embodiment, the present invention includes a context data store that stores context data aggregated from the plurality of sources. A context service interface is provided which exposes methods that can be called to add context data to the data store and retrieve context data from the data store.
In one embodiment, a find service is provided which receives a request to retrieve context data and invokes the methods on the context service interface to retrieve the desired data. A data provider service can also be provided to receive context data from the plurality of sources and invoke methods on the context service interface to add or update the context data in the data store based on the context data received.
Appendix A illustrates a number of classes in an exemplary class library.
The present invention deals with context information. More specifically, the present invention deals with a system for abstracting and aggregating context information from a variety of sources and making it available to requesting components. However, prior to discussing the present invention in greater deal, one embodiment of an illustrative computing environment for the present invention will be discussed.
The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
With reference to
Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 100. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier WAV or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, FR, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 110 through input devices such as a keyboard 162, a microphone 163, and a pointing device 161, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 190.
The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110. The logical connections depicted in
When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user-input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
It should be noted that the present invention can be carried out on a computer system such as that described with respect to
The discussion of the present invention refers to “context data” or “context information”. For purposes of the present discussion, these terms mean any or all of the following information or similar information:
information that identifies a person (such as user name, user id, address, company, etc. . . . ), business attributes of the person (such as title, billing rate, level of training, expertise, teams the person belongs to, identifying information for those teams, etc. . . . ), the ways to contact the person (such as cellular telephone number#, e-mail address, telephone number, pager number, etc. . . . ), the person's preferences (such as desired hours of availability, preferred devices to use during various hours of the day, etc. . . . ), the devices used by the person and how those devices are set up (such as device id, device description, applications installed on the device, operating system on the device, memory available, etc. . . . ), the person's schedule and contact list, etc. . . . .
System 200 aggregates context information from sources 222-224, as well as from devices and users and abstracts that information into a generalized form which is stored in context data store 202. In one embodiment interface 204 aggregates the information through data provider service 206. A requesting application 220, which will illustratively be a context-aware application that makes use of such context information, can request the aggregated and abstracted context information. In one embodiment, requesting application 220 requests the context information in context data store through find service 208.
The indication as to whether the user is mobile enabled indicates whether the user is a mobile user in the company. For example, this field may be set to true if a user is allowed to submit mobile sales orders. Otherwise the field is set to false. Of course, the User object can include other information or different information. For instance, the user can provide user preferences, such as the times of day that the user wishes to be contacted on different devices that are registered under the user's name. By way of example, the user may wish to be contacted by cellular telephone during the morning hours and by electronic mail on the user's laptop in the afternoon hours.
Once this user registration information is received, it is provided to data provider service 206. Data provider service 206 generates a User object in a standard format. In one embodiment, the user registration information 228 is provided to data provider service 206 as a standard document (such as an XML document). Data provider service 206 then arranges the data into the standard User object form. Generating the User object is illustrated by block 302 in
Once the User object has been created and stored, the device which the user wishes to use is then customized for the user. This is illustrated by block 306 in
Once the device has been customized for the user, the device provides device registration information 226 to data provider 206. This is indicated by block 308 in
Once data provider service 206 receives device registration information 226, it forms a Device object which represents the device registration information 226. This is indicated by block 310 in
Data provider service 206 can also receive information from a variety of other sources. For instance,
Another example of a data source which provides context information to system 200, and which is illustrated in
While a number of context data sources are illustrated in
In addition, a company may provide context information related to the organization of the company. For instance, a Team object may be included which identifies teams, a leader of each team and the name of each team. Similarly, team members may be identified by an object which correlates a team identifier with a user identifier. Many other sources of context data can be provided as well.
It should also be noted that information can be provided from the data sources to interface 204 in a variety of different ways. For instance, where data provider service 206 is implemented as a web service, the data source simply needs to provide a web address for contact service interface 204 along with the location of an XML document which contains the context information being submitted by the data source. In that embodiment, data provider service 206 retrieves the XML document and invokes the proper interface 214 to have context service interface 204 store information represented by an object generated based on the XML document in context data store 202.
In another embodiment, however, the methods of interacting with context data store 202 are implemented in class libraries. The data sources, if they have access to the class libraries, can instantiate objects from the class libraries and call the methods on the instantiated objects themselves. As illustrated in
Not only can data be provided to context data store 202 by data sources, but it can be retrieved from context data store 202 by a requesting application 220.
Requesting application 220 then invokes find service 208 by calling the appropriate web service method. Again, requesting application 220 simply provides the web address of context service interface 204, along with a location in which requesting application 220 desires to receive the XML document containing the context information requested. In that embodiment, find service 208 returns the XML document containing the requested context information to the specified location for access by requesting application 220. Calling the web service method is indicated by block 352 in
Of course, as with providing data to context data store 202, requesting applications 202 can (if they have access to class libraries 234) simply instantiate objects which implement the context service interface 204 and directly invoke the methods on those objects. This is indicated in greater detail in the flow diagram of
In accordance with yet another embodiment, it should be noted that requesting application 220 can access data in context data store 202 directly using database queries. For example, if data store 202 is implemented as a structured query language (SQL) database, then, so long as requesting application 220 is provided with access to data store 202, it can directly retrieve context information from data store 202 using SQL queries. Similarly, if the data sources are given direct access to data store 202, they can add information to data store 202 directly using SQL queries.
The class libraries discussed herein and used to implement interface 204 can take a wide variety of different forms. One illustrative embodiment of a number of the classes in an exemplary class library are set out in appendix A hereto. However, it should be noted that the classes discussed therein are exemplary only and any number of additional or different classes can be used as well.
Illustratively, all accesses to the context information through interface 204 are subjected to a security policy implemented by security layer 212. In one embodiment, security layer 212 is a rules-based security layer. Security layer 212 thus enforces access restriction and any other security measures implemented in the rules. Therefore, users are only allowed to access context information for which they are authorized by layer 212. The rules can implement security in various levels. For example, some users may be provided with complete access to all context information. Other users may be provided with no access to context information. Still other users may be provided with read only access, or read only access to some of the context information and read/write access to other context information. Of course, other or different security measures can be implemented as well.
A number of operations will now be described in order to better illustrate the operation of the system shown in
In another operation, the information is not located in cache 406. In that embodiment, requesting application 220 provides local find service 412 with a request to retrieve the desired context information. Local find service 412 invokes the method on interface 408 to retrieve the desired information, and a null value (or other value) indicating that the information does not exist in cache 406 is returned. In that case, local find service 412 accesses find service 208 in system 200 through network 210. Find service 208 invokes the appropriate method on interface 204 to retrieve the data from data store 202. The data is retrieved and provided from find service 208 back to local find service 412 which returns it to requesting application 220. Local find service 412 then invokes an appropriate method on interface 408 to add the requested context information to cache 406.
In order to add context information, data source 420 first provides the context information to local data provider service 410. Local data provider service 410 then provides the information through network 210 to data provider service 206 in system 200. Data provider service 206, in turn, invokes an appropriate method on interface 204 to add the context information to context data store 202. This is confirmed back to local data provider service 410. Local data provider service 410 then invokes an appropriate method on interface 408 to add the context information to cache 406 and this is also confirmed to local data provider service 410.
It can thus be seen that the present invention helps to reduce information overload to developers and applications by filtering the information according to what is relevant in a current context. It does this by allowing a developer to write applications that are context aware and therefore reduce context information requested to that which is necessary. Similarly, the present invention provides a single place for obtaining all information related to context. The invention functions as an aggregator and abstractor for different providers of context information. Thus, it offers a simple object-oriented programming model to access contextual information so that the developer only needs to learn a single set of semantics instead of one corresponding to each source of context information. By implementing a security layer, the present invention enables custom authorization schemes to address privacy concerns. Similarly, by providing developers with access to the data store directly through SQL queries, developers can customize the service to their needs and performance requirements.
Using the present system, the scenario discussed in the background section can be greatly enhanced. For example, assume that the dispatcher receives a call from a customer that the television is broken (such as fails to display color) and that the customer wishes a technician to attend to the problem today. The dispatcher can simply select an “assign technician” function on a context aware application. This results in a technician being assigned to the job based on several factors considered by the function, such as, current location of the technician, the level of expertise of the technician, and the technician's schedule for the day. All of this information is obtained from the context service component and incorporated into the function of the context-aware application. The dispatcher then assigns the identified technician to the job. The identified technician's schedule is automatically updated with the new job and a message is sent to the technician's mobile telephone informing him of the change in schedule. The technician also receives directions to the new customer site on his mobile device. The technician arrives at the site, completes the job and sends a message back to the call center stating that the job has been completed. This entire scenario is enabled because the application can obtain context information from a central location which has aggregated and abstracted the context information for access by the application.
Of course, a wide variety of other applications can be written using the present context service. For instance, a mobile worker can subscribe to traffic updates on a cellular telephone, to receive those updates everyday from 5-6 PM when traffic is heavy. However, when the worker is out of town for the day, the application realizes this because it is contained in the context information provided by the context service (such as through the Schedule object). Therefore, the application detects that the worker is not in a local area and hence the traffic report is not sent.
Similarly, assume that a worker has identified as a preferred mobile device a personal digital assistant. Assume also that another person attempts to send the worker a message that is quite large, but not very urgent. The context-aware application detects this (again by retrieving context information from the present context service). The message is thus sent to the worker's desk-top computer so that the worker will receive it when he or she returns to the office at the end of the day. This can of course be accomplished by having the worker set up a preference as to which device should receive messages, based on message size.
These are but a few exemplary scenarios that can be addressed by context aware applications using the context service of the present invention. Of course, these are illustrative scenarios only, provided to illustrate some uses and operations of the present invention, and countless others can be supported by the present invention.
Although the present invention has been described with reference to particular embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5033009 *||Mar 3, 1989||Jul 16, 1991||Dubnoff Steven J||System for generating worksheet files for electronic spreadsheets|
|US5713020 *||Sep 2, 1993||Jan 27, 1998||Microsoft Corporation||Method and system for generating database queries containing multiple levels of aggregation|
|US6185598 *||Feb 10, 1998||Feb 6, 2001||Digital Island, Inc.||Optimized network resource location|
|US6347340 *||Feb 18, 2000||Feb 12, 2002||Mobilesys, Inc.||Apparatus and method for converting a network message to a wireless transport message using a modular architecture|
|US6510350 *||Apr 7, 2000||Jan 21, 2003||Steen, Iii Henry B.||Remote data access and system control|
|US6636803 *||Nov 30, 2001||Oct 21, 2003||Corus Home Realty||Real-estate information search and retrieval system|
|US6708186 *||Sep 28, 2000||Mar 16, 2004||Oracle International Corporation||Aggregating and manipulating dictionary metadata in a database system|
|US6842737 *||Jul 19, 2000||Jan 11, 2005||Ijet Travel Intelligence, Inc.||Travel information method and associated system|
|US6847393 *||Apr 19, 2002||Jan 25, 2005||Wren Technology Group||Method and system for monitoring point of sale exceptions|
|US6847892 *||Oct 29, 2001||Jan 25, 2005||Digital Angel Corporation||System for localizing and sensing objects and providing alerts|
|US6934532 *||Feb 8, 2001||Aug 23, 2005||Apriva, Inc.||Communication systems, components, and methods operative with programmable wireless devices|
|US6944662 *||May 4, 2001||Sep 13, 2005||Vinestone Corporation||System and methods providing automatic distributed data retrieval, analysis and reporting services|
|US6947571 *||May 15, 2000||Sep 20, 2005||Digimarc Corporation||Cell phones with optical capabilities, and related applications|
|US6980962 *||Feb 29, 2000||Dec 27, 2005||Quixtar Investments, Inc.||Electronic commerce transactions within a marketing system that may contain a membership buying opportunity|
|US7240027 *||Apr 6, 2001||Jul 3, 2007||The Procter & Gamble Company||Method and apparatus for monitoring the flow of items through a store or warehouse|
|US7299067 *||Oct 11, 2002||Nov 20, 2007||Lee Riggs||Methods and systems for managing the provision of training provided remotely through electronic data networks to users of remote electronic devices|
|US7401131 *||Mar 29, 2002||Jul 15, 2008||Verizon Business Global Llc||Method and system for implementing improved containers in a global ecosystem of interrelated services|
|US7428723 *||Mar 29, 2002||Sep 23, 2008||Verizon Business Global Llc||Aggregrating related events into a single bundle of events with incorporation of bundle into work protocol based on rules|
|US20010037361 *||Apr 10, 2001||Nov 1, 2001||Croy John Charles||Methods and systems for transactional tunneling|
|US20020080771 *||Dec 21, 2000||Jun 27, 2002||802 Systems, Inc.||Methods and systems using PLD-based network communication protocols|
|US20020184170 *||Jun 1, 2001||Dec 5, 2002||John Gilbert||Hosted data aggregation and content management system|
|US20040015783 *||Jun 20, 2003||Jan 22, 2004||Canon Kabushiki Kaisha||Methods for interactively defining transforms and for generating queries by manipulating existing query data|
|1||*||"Core J2EE Patterns: Best Practices and Design Strategies" by Deepak Alur et al. Chapter 9, "Data Access Objects" Jun. 26, 2001.|
|2||*||"Developer's Guide to Building XML-based Web Services with the Java 2 Platform, Enterprise Edition (J2EE)" by James Kao. Jun. 2001. Available online at: http://www.theserverside.com/tt/articles/pdf/J2EE-WebServices-DevGuide.pdf.|
|3||*||"RFC: MetaWeblog API" by Dave Winer. Published Mar. 14, 2002. Accessed Nov. 10, 2007. Available online: http://www.xmlrpc.com/metaWeblogApi.|
|4||*||"The Evolution of RSS" by Andrew King. Published May 3, 2001. Accessed Nov. 10, 2007. Available online: http://www.webreference.com/authoring/languages/xml/rss/1/.|
|5||*||"Web Services Made Easier" by Sun Microsystems, Jun. 2002. Available online at: http://java.sun.com/xml/webservices.pdf.|
|6||*||"What is RSS" by Mark Pilgrim. Published Dec. 18, 2002. Accessed Nov. 10, 2007. Available online: http://www.xml.com/pub/a/2002/12/18/dive-into-xml.html.|
|7||*||"Why getter and setter methods are evil", Allen Holub. Available online at http://www.javaworld.com/javaworld/jw-09-2003/jw-0905-toolbox.html. Published Sep. 5, 2003. Accessed Jun. 9, 2006.|
|8||*||RDF Site Summary (RSS) 1.0 Specification. Published Dec. 9, 2000. Available online at http://web.resource.org/rss/1.0/spec.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8893217||Jun 30, 2011||Nov 18, 2014||International Business Machines Corporation||Method and apparatus for specifying time-varying intelligent service-oriented model|
|US9002778 *||Jun 22, 2004||Apr 7, 2015||International Business Machines Corporation||Designing aggregates based on access patterns in dimensions|
|US20050283375 *||Jun 22, 2004||Dec 22, 2005||International Business Machines Corporation||Designing aggregates based on access patterns in dimensions|
|US20090150206 *||Dec 7, 2007||Jun 11, 2009||Mci Communications Services||Notification system and method|
|US20090327930 *||Sep 10, 2009||Dec 31, 2009||Whirlpool Corporation||Appliance development toolkit with editor for binding data|
|US20130218874 *||Mar 22, 2013||Aug 22, 2013||Salesforce.Com, Inc||System, method and computer program product for applying a public tag to information|
|Jun 17, 2003||AS||Assignment|
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SWARTZ, TANYA;AVADHANAM, SRIKANTH;CHOPRA, GAGAN;REEL/FRAME:014198/0535
Effective date: 20030616
|Feb 25, 2014||FPAY||Fee payment|
Year of fee payment: 4
|Dec 9, 2014||AS||Assignment|
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0477
Effective date: 20141014