US20040006593A1 - Multidimensional approach to context-awareness - Google Patents
Multidimensional approach to context-awareness Download PDFInfo
- Publication number
- US20040006593A1 US20040006593A1 US10/457,010 US45701003A US2004006593A1 US 20040006593 A1 US20040006593 A1 US 20040006593A1 US 45701003 A US45701003 A US 45701003A US 2004006593 A1 US2004006593 A1 US 2004006593A1
- Authority
- US
- United States
- Prior art keywords
- user
- information
- client
- context information
- context
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000013459 approach Methods 0.000 title description 2
- 230000006978 adaptation Effects 0.000 claims abstract description 56
- 230000000694 effects Effects 0.000 claims abstract description 9
- 238000004891 communication Methods 0.000 claims description 43
- 238000000034 method Methods 0.000 claims description 35
- 230000001953 sensory effect Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 11
- 230000003993 interaction Effects 0.000 claims description 10
- 238000012384 transportation and delivery Methods 0.000 description 23
- 230000008569 process Effects 0.000 description 10
- 238000004519 manufacturing process Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 206010048865 Hypoacusis Diseases 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 238000013528 artificial neural network Methods 0.000 description 2
- 230000008094 contradictory effect Effects 0.000 description 2
- 238000007418 data mining Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 230000009897 systematic effect Effects 0.000 description 2
- 206010011878 Deafness Diseases 0.000 description 1
- 206010020675 Hypermetropia Diseases 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 208000001491 myopia Diseases 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 230000001681 protective effect Effects 0.000 description 1
- 230000029058 respiratory gaseous exchange Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 230000001755 vocal effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Definitions
- This invention relates to the use of context information by computing applications.
- adapting the user interface of the selected client may include selecting a sensory communication path for the interaction of the user with the enterprise service that is suited to a context described by the context information.
- the sensory communication path selected may include, for example, a voice communication path, a text communication path, or a graphical communication path.
- the context determination service may include a rule engine or an inference engine.
- the inference engine 320 may employ Bayesian reasoning, the Dempster-Shafer theory, a knowledge base, an expert system, plan recognition, collaborative filtering, statistical analysis, a neural network, data mining, keyword analysis, fuzzy logic, an overlay model, a bug library, or a combination of one or more of these methods or systems.
- the decision engine may, for example, update the user profile 370 with the newly determined context information 330 .
- This decision is based, for example, on David Dudley's role as a long haul delivery truck driver in the middle of a current delivery, and upon the limited interface capabilities of the client PDA.
- the interface adaptation service may presume that David Dudley will most likely inquire about either his present delivery task, or about a delivery task scheduled for the near future.
- the interface adaptation service may determine to simplify the interface by limiting the information presented to David Dudley accordingly. Contrary to expectation, however, David Dudley may desire to access employee benefit services, or to view shipping tasks further in the future in order to plan for a vacation.
- the interface adaptation may allow David Dudley to override its preliminary determination 655 based on his actual rather than expected needs.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- User Interface Of Digital Computer (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A context aware enterprise system includes a network, an enterprise service coupled to the network, and a plurality of information sources that include enterprise information related to one or more activities of the enterprise system. The enterprise system also includes a plurality of clients with user interfaces by which a user may access the enterprise service over the network. A context determination service determines context information describing a multi-dimensional context based on the enterprise information. The context information determined by the context determination service includes a user identification, an identification of a client selected by the user, a user role, a user expertise related to the enterprise service, and a user expertise related to the selected client. Based on the context information, an interface adaptation service adapts the user interface of the client.
Description
- This application claims priority from U.S. Provisional Application Nos. 60/388,289, filed Jun. 14, 2002, and 60/422,112, filed Oct. 30, 2002, each titled MULTIDIMENSIONAL APPROACH TO CONTEXT-AWARENESS.
- This invention relates to the use of context information by computing applications.
- An enterprise resource planning (ERP) system includes various business-related enterprise services. The ERP system provides an organization-wide information handling infrastructure to control the business processes of a company. The ERP system and the enterprise services that it includes may be extremely complex and the company may depend on their correct operation.
- Many employees of the company may use the enterprise services of the ERP system through a variety of client devices. For example, an accountant may access the ERP system on a desktop computer to update financial records of the company. The chief executive officer (CEO), on the other hand, may use a laptop computer to obtain a strategic overview of company performance from the ERP system. In turn, a delivery driver may access the ERP system using a personal digital assistant (PDA) to determine a delivery schedule. Each also might use the ERP system to inquire about the status of their employee benefits from home, for example, using a phone. In sum many employees may access the ERP system, and each may do so in a variety of contexts.
- Employees of the company may have difficulty using the ERP system because of the system's complexity and the many contexts in which it may be used. Even when employees develop expertise in the ERP system, they may find that the system is ill-adapted to the particular context of their use.
- In one general aspect, an enterprise system with multi-dimensional context awareness includes a network, an enterprise service coupled to the network, and a plurality of information sources that include enterprise information related to one or more activities of the enterprise system. The enterprise system also includes a plurality of differing clients with user interfaces by which a user may access the enterprise service over the network. The clients may or may not be wireless. A context determination service determines context information describing a multi-dimensional context based on the enterprise information. The context information determined by the context determination service includes a user identification, an identification of the client selected by the user, a user role, a user expertise related to the enterprise service, and a user expertise related to the client selected by the user. Based on the context information, an interface adaptation service adapts the user interface of the selected client.
- Implementations may include one or more of the following features. For example, adapting the user interface of the selected client may include selecting a sensory communication path for the interaction of the user with the enterprise service that is suited to a context described by the context information. The sensory communication path selected may include, for example, a voice communication path, a text communication path, or a graphical communication path.
- The interface also may be adapted to adjust a level of help automatically provided to the user regarding operation of the selected client or the enterprise service. The level of help may be adjusted based on the context information describing the user expertise related to the selected client or the enterprise service, respectively. Adaptation also may include adapting the user interface to present only information to the user relevant to the role or identification of the user described by the context information.
- To determine context information, the context determination service may include a rule engine or an inference engine.
- The sources of the enterprise information accessed by the context determination service include databases, enterprise security devices, and location determining devices. Nevertheless, in a further implementation, the information sources include no information source configured only to provide context information.
- The context information that the context determination service determines may further include a measure of time, or information regarding a physical environment of the user. The physical environment information may include information related to a location of the user, an activity of the user, a measure of background noise, or a measure of lightness or darkness.
- To adapt the user interface based on the context information, the interface adaptation service also may include a rule engine, and/or an inference engine.
- The inference engines of the context determination service and the interface adaptation service may employ, for example, Bayesian reasoning, the Dempster-Shafer theory, a knowledge base, an expert system, plan recognition, collaborative filtering, statistical analysis, a neural network, data mining, keyword analysis, fuzzy logic, an overlay model, a bug library, or a combination of one or more of these methods or systems.
- These general and specific aspects may be implemented using a method, a system, or a computer program, or any combination of systems, methods, and computer programs.
- Other features will be apparent from the following description, including the drawings, and from the claims.
- FIG. 1 is a is a schematic diagram of an enterprise system that configures a client interface using a context adaptation service.
- FIG. 2 is a schematic diagram of an enterprise system, as in FIG. 1, that illustrates several multi-dimensional contexts.
- FIGS.3-4 are schematic diagrams illustrating systems that may be used to implement the context adaptation service of FIGS. 1 and 2.
- FIG. 5 is a flow diagram illustrating a systematic process implementable by the context adaptation service of FIGS.1-2.
- FIG. 6A describes an exemplary multi-dimensional context related to an enterprise system.
- FIG. 6B illustrates an interface adaptation corresponding to the multi-dimensional context information of FIG. 6A.
- FIGS.7A-C are exemplary displays illustrating a user interaction with a user interface adapted by the context adaptation service.
- Like reference symbols in the various drawings indicate like elements.
- Referring to FIG. 1, a
generalized enterprise system 100 may be used to configure a user interface of a client to facilitate a user's access to an enterprise service based upon a multi-dimensional context (i.e., a context described by more than one parameter) of the user's use. The multi-dimensional context includes, for example, an identification of the user and of the client, a role of the user, expertise of the user relative to the enterprise service and relative to the client. Exemplary components of theenterprise system 100 are described in greater detail below. - The
enterprise system 100 of FIG. 1 generally includes one ormore clients 110, anetwork 130, anenterprise service 150, and acontext adaptation service 170. Theclients 110 generally may include any device, system, and/or piece of code that relies on another service to perform an operation. For example, theclients 110 may include a workstation, a notebook computer, a pen based computer, a personal digital assistant (PDA) or cellular telephone. Theclients 110 also may include a web browser, an email client, a synchronization client (e.g., a calendar synchronization client, a task list synchronization client), an instant messaging (IM) client, a business productivity application (e.g., a word processor, a spreadsheet), and/or an operating system or operating system kernel. Theclients 110 may access data or services provided by theenterprise service 150 by communicating with theenterprise service 150 using voice and/or non-voice data. - The
enterprise service 150 generally may include, for example, any device, system, and/or piece of code configured to perform an operation requested by a client 110 (e.g., a cellular telephone, a web browser, or other service). For example, theenterprise service 150 may include an ERP service, an email service, an accounting service, a resource management service, a synchronization service (e.g., a calendar synchronization service, a task list synchronization service), a print service, a file access service, an IM service, an operating system, an operating system kernel, an authentication service, an authorization service, and/or any combination of these or other services. - The
context adaptation service 170 generally may include, for example, any device, system, and/or piece of code configured to determine a users multi-dimensional context and adapt an interaction of the enterprise system with the user based on that context. For example, thecontext adaptation service 170 may include acontext determination service 175, and aninterface adaptation service 180. Theservices context adaptation service 170 may include a database access service, a sensor data access service, a rule engine, an inference engine (e.g., a Bayesian reasoning engine, a Dempster-Shafer engine, a probabilistic reasoning engine), a file access service, an operating system, an operating system kernel, and/or any combination of these services. Thecontext adaptation service 170 may or may not be included in theenterprise service 150. - Communication between the
clients 110 and theenterprise service 150 as well as other communications within the enterprise system services generally occur over acommunications network 130. Thecommunication network 130 typically allows direct or indirect communication between the system services (e.g., between theclient 110, theenterprise service 150, and the context adaptation service 170), irrespective of physical or logical separation. Thecommunication network 130 may include a secured communication network (e.g., a communication network protected by a firewall and/or other security mechanisms). - The
communication network 130 may further include various mechanisms for delivering voice and/or non-voice data, such as, for example, the transport connection protocol (TCP), the Internet protocol (IP), the World Wide Web, one or more local area networks (LANs) and/or one or more wide area networks (WANs). Thecommunication network 130 also may include analog or digital wired and wireless telephone networks, e.g., public switched telephone networks (PSTN), integrated services digital networks (ISDN), various types of digital subscriber lines (xDSL), advance mobile telephone service (AMPS), global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), radio, cable, satellite, and/or other delivery mechanisms for carrying voice or non-voice data. - One or more other services may be included in the components of
enterprise system 100 and/or these components (hereinafter the system services) may be included as part of one or more other services. For example, the system services may include or be included in a general-purpose or a special-purpose computer (e.g., a personal computer, a personal digital assistant (PDAs), or a device specifically programmed to perform certain tasks), at least one Local Area Network (LAN), and/or at least one Wide Area Network (WAN). Either way, the response to and execution of instructions received by any or all of the system services may be controlled by, for example, a program, a piece of code, an instruction, a device, a computer system, or a combination thereof, for independently or collectively instructing the services to interact and operate as described herein. - FIG. 2 shows an enterprise system200, generally similar to
enterprise system 100 of FIG. 1, illustrating severalmulti-dimensional contexts enterprise service 150 using aclient 110. For example, company employees may include a delivery truck driver (context 205), a corporate executive (context 210), and a manufacturing manager (context 215). The responsibilities of each employee differ greatly as well as the information and services that their jobs require theenterprise service 150 to provide them. As with their responsibilities, the training and experience of the employees may differ dramatically. Moreover, the physical environments under which each employee accesses the enterprise service may differ greatly, both from access to access and from employee to employee. - More specifically, the delivery driver uses a mobile client (e.g., a pen computer, a PDA, a cellular telephone) to access, for example, delivery lists, addresses, and schedules maintained by the
enterprise service 150. The delivery driver may use the mobile client to access theenterprise service 150, for example, from the delivery truck, or at a pick-up or delivery site. Moreover, the delivery driver may wish to verify delivery information while driving the delivery truck. Depending on time, season, and delivery point, ambient conditions such as lighting, temperature, and noise may vary greatly and may further complicate the task of accessing theenterprise service 150 using the client. - The corporate executive may access the
enterprise service 150, for example, to obtain data showing corporate performance, or reflecting strategic relationships with other companies. The corporate executive may use a laptop computer orother client 110 to access theenterprise service 150 from an office in a corporate headquarters, from a corporate boardroom during a meeting, or while traveling (e.g., in an airplane or at a hotel). The privacy and security with which the corporate executive may access theenterprise service 150 may substantially influence the corporate executive's ability to use theenterprise service 150 in certain situations (e.g., while at an on-site meeting with a customer or competitor, or while traveling on a plane). - The manufacturing manager may access the
enterprise service 150 to determine order status, manufacturing schedules, or work schedules. The manufacturing manager may use a workstation or other client device to access theenterprise service 150 from the manufacturing floor. Conditions on the manufacturing floor may be loud or may require silence, lighting conditions may vary, and there may be many spurious audible and visual distractions. Certain clothing or protective gear may be required (e.g., a cleansuit, a respirator, ear protection, eye protection), and may or may not interfere with using theclient 110 to access theenterprise service 150. - FIGS. 3 and 4 describe systems that may be used to implement the
context determination service 175 and theinterface adaptation service 180, respectively, of FIGS. 1 and 2. - Referring to FIG. 3, some implementations of the
context determination service 175 include adecision engine 310 used to determinecontext information 330 fromenterprise information 350. In this implementation, theenterprise information 350 includes a user identification and aclient device identification 352. - The enterprise information also may include an
activity history 354 of the enterprise service users. Theactivity history 354 may include, for example, anapplication use history 356 that shows details of user's past use of the enterprise service. For each enterprise user, theapplication use history 356 might show, for example, a frequency of access to the enterprise service, a frequency of access to help procedures of the enterprise services and a nature or timing of the help requested, and/or a frequency of functions performed using the enterprise service. Theuser activity history 354 also may include aclient use history 358 showing, for each enterprise user, clients used to access the enterprise service and a frequency that those clients have been used. In addition, theuser activity history 354 may include security andauthentication data 360 related to the current and past security status and privileges of enterprise service users. The security andauthentication data 360 also may include information regarding when and where secure resources were accessed. For example, the security andauthentication data 360 may record that a user entered a building through a secured door at 7:30 am on a Monday morning. - The
enterprise information 350 also may includeinformation 362 that indicates current and past characteristics and features of the enterprise service and clients. The application andclient feature data 362 may include, for example, information that a new capability has been added to a newly released version of the enterprise service, or that a PDA client may be voice enabled while a pen based computer client may not. - Also included in the
enterprise information 350 aregeneral employee data 364 andcustomer date 366. For each employee, theemployee data 364 may include information such as the role, job title, job description, or job location of the employee. This information may describe the workplace, permissions, restrictions and tasks associated with each employee. Information regarding home contact information, education, physical characteristics, health record, or employee benefits also may be included. For each customer, thecustomer data 366 may include information identifying services or goods generally provided to the customer, delivery or payment preferences, customer contacts, and associated customer locations (e.g., addresses, approximate latitude and longitude). - The enterprise information also may include
data 368 from specialized context sensors. For example, the context sensors might include a global positioning system (GPS) which might detect a client device and provide location data (e.g., latitude and longitude) related to the client device. Location data also may be obtained using a beacon emitting signals, such as, radio frequency signals or infrared signals. These signals may be received, for example, by a client. The beacon may broadcast location identifying information, such as, a geographical identifier (e.g., latitude and longitude of the beacon) or an abstract representation of a location (e.g., the street address of the beacon, the name of a store, a numerical identifier). Thecontext sensor data 368 also might include data provided by other context sensors related to temperature, loudness, lighting, a pulse or respiration rate of the user, or a skin conductivity of the user. - The enterprise information also may include for each user a
user profile 370. Theuser profile 370 may include previously determined context information, such as, for example, context information based on the users' most recent accesses to the enterprise service. The user profile may include information stored, for example, in a data repository based on the X.500 directory access standard (e.g., a lightweight directory access protocol (LDAP)). Among other benefits, LDAP allows different kinds of context information to be stored, such as, for example, client and service profiles. - The
decision engine 310 includes, for example, arule engine 315, and/or aninference engine 320. Therule engine 315 may be configured to enable thedecision engine 310 to determine thecontext information 330 by applying one or more rules to theenterprise information 350 accessed by thedecision engine 310. Each rule of therule engine 310 may include a condition and an associated action that is performed or a conclusion that is drawn if the condition is satisfied. Theinference engine 320 may be configured to infer thecontext information 330 from information input to thedecision engine 310. Theinference engine 320 may employ one or more methods or systems to infer thecontext information 330 from information accessed by thedecision engine 310 that is uncertain, contradictory, or ambiguous. For example, theinference engine 320 may employ Bayesian reasoning, the Dempster-Shafer theory, a knowledge base, an expert system, plan recognition, collaborative filtering, statistical analysis, a neural network, data mining, keyword analysis, fuzzy logic, an overlay model, a bug library, or a combination of one or more of these methods or systems. After determining thecontext information 330, the decision engine may, for example, update theuser profile 370 with the newlydetermined context information 330. - The
context information 330 determined by thedecision engine 310 includes at least auser identification 332 of the user accessing the enterprise service, aclient identification 334 of the client device used by the user to access the enterprise service, auser role 336 associated with the user, anapplication expertise 338 of the user related to the enterprise service, and aclient expertise 340 of the user related to the client. Nevertheless, thecontext data 330 may include many additional items of information. For example, thecontext data 330 may includephysical environment information 342 related to a physical environment of the user, such as, for example, time, temperature, lighting, or loudness. Thecontext data 330 also may includephysical status information 344 related to a physical status of the user, such as, for example, whether the user is hard of hearing, near-sighted or far-sighted, or whether the user is distracted or nervous. - Referring to FIG. 4, the
interface adaptation service 180 may include anadaptation engine 410 configured to access the context information 330 (e.g., directly from the decision engine, or from the user profile 370) and to adapt an interface of aclient 430 according to thecontext information 330. Similarly to thedecision engine 310 of the system of FIG. 3, theadaptation engine 410 may include arule engine 415 or aninference engine 420 that may determine adaptation of the client interface based on thecontext information 330 accessed by theadaptation engine 410. Theinference engine 420 may adapt the user interface even when thecontext information 330 accessed by theadaptation engine 410 is uncertain, ambiguous or contradictory. Theinference engine 420 may employ Bayesian reasoning and/or any of the methods or systems described with respect to theinference engine 320 of FIG. 3, either alone or in combination. - FIG. 5, illustrates a
systematic process 500 implementable by the systems of FIGS. 1-4 to adapt a user interface of aclient 510 accessing an enterprise service 515 based upon multi-dimensional context information. Initially, a user 505 may use theclient 510 to access the enterprise service 515. Theprocess 500 may respond by identifying multi-dimensional context information (steps 520), and adapting a user interface based on the multi-dimensional context information (steps 540). - Determining the multi-dimensional context information (steps520) may include, for example, obtaining first information regarding the access or login (e.g. a user identification, a client identification) from the enterprise service (step 525). Based on the first information, second information may be determined, for example, from information sources of the enterprise service (step 530). Based on the first and second information, multi-dimensional context information then may be determined (step 535).
- Adapting the interface based on the multi-dimensional context information (steps540) includes using the multi-dimensional context information to determine an interface adaptation suited to the context information (step 545). The interface configuration also may be based on direct user input, received, for example, by making a query to the user based on an initially determined interface configuration.
- More specifically, the interface adaptation may be based, among other things, on an expertise of the user related to the enterprise service515, or related to the
client 510 or interaction scheme. Specifically, a user not familiar with a specific aspect of the enterprise service 515 may need to be instructed regarding what information to enter in information fields associated with that aspect of the enterprise service 515. At the same time, when accessing the enterprise service 515 from a familiar client such as a desk-top computer, the user may require no help to use the screen, keyboard and mouse. On the other hand, the user may access the enterprise service 515 using a client with a fully VoiceXML (voice extensible markup language) enabled interface. In that case, although familiar with the enterprise service 515, the user may need more support with an unfamiliar interaction scheme of the interface (e.g. the interface may advise the user “you can say the number or type into the keyboard”). The interface might also be adapted to hide items expected to be irrelevant to a current task of the user while offering shortcuts to probably needed functions. - After the interface configuration is determined, the
context adaptation process 500 may communicate the interface configuration to theclient 510 and/or to the enterprise service 515 causing the interface to be adapted (step 550). The user then may interact with the enterprise service 515 through theclient 510 using the adapted interface. Thecontext adaptation process 500 may continually determine context and may readapt the user interface based on a changed context. For example, after communicating the interface configuration to the enterprise service and/or the client (step 550), theprocess 500 may continue to monitor the information sources of the enterprise service (step 530) and determine context information (step 535) to determine if a changed context exists. When a changed context is determined, theprocess 500 may re-determine the interface configuration (step 545) and communicate the re-determined interface configuration to the enterprise service and/or the client (step 550). - FIG. 6A illustrates
multi-dimensional context information 600 such as may be determined using theprocess 500 of FIG. 5. Themulti-dimensional context information 600 includes an identification of theuser 605 as David Dudley,age 52, with anemployee number 14999. Themulti-dimensional context information 600 also includesinformation 610 that identifies the client device used by David Dudley to access the enterprise as a BrainFlex model 32xi voice-capable PDA.User role information 615 identifies David Dudley's role as a company employee, and, more specifically, as a driver of a long haul delivery truck. Theuser role information 615 further identifies that David Dudley currently is making a delivery to Alyeska Pipeline Service Co. of Fairbanks, Ak. - The
multi-dimensional context information 600 also includesinformation 620 regarding aspects of David Dudley's physical environment. Specifically, it includesinformation 622 that identifies David Dudley as being intruck Information information 630 to be substantial while his expertise with the client is identified byinformation 635 as modest.Context information 640 indicates that David Dudley historically has preferred to take a passive role with respect to accessing help. In other words, he has preferred that he not be required to request the help, but that appropriate help be offered to him. In addition,information 645 identifies no physical constraints associated with David Dudley, such as, for example, hardness of hearing. - FIG. 6B illustrates an
interface adaptation 650 determined based on themulti-dimensional context information 600 of FIG. 6A. Theinterface adaptation 650 includes adescription 655 of the enterprise service content that the interface will present to David Dudley. In this example, the interface adaptation service has determined from the context information to present to David Dudley information relating to his shipping tasks for a three day period extending from his time of access to the enterprise service. - This decision is based, for example, on David Dudley's role as a long haul delivery truck driver in the middle of a current delivery, and upon the limited interface capabilities of the client PDA. The interface adaptation service may presume that David Dudley will most likely inquire about either his present delivery task, or about a delivery task scheduled for the near future. The interface adaptation service may determine to simplify the interface by limiting the information presented to David Dudley accordingly. Contrary to expectation, however, David Dudley may desire to access employee benefit services, or to view shipping tasks further in the future in order to plan for a vacation. The interface adaptation may allow David Dudley to override its
preliminary determination 655 based on his actual rather than expected needs. - Because the context information indicates that David Dudley is driving and that lighting likely is poor (e.g., it is still night in Alaska during the winter at 2:30 p.m.), the
interface adaptation 650 may provide 660 that the primary interface path should be voice (e.g., using VoiceXML), thus allowing David Dudley to maintain eye contact with the road. Nevertheless, another primary interface path might be chosen were the context information to indicate that the noise level were high, or that David Dudley were hard of hearing or deaf. For example, another suitable interface path might be available where the delivery truck includes a heads-up display with integrated steering-wheel controls configured to operate with the client PDA. In that case, the heads up display might be selected as the primary interface path in the interface adaptation. - Based on the indication of the context information that David Dudley has substantial expertise with the enterprise service, the
interface adaptation 650 may indicate anenterprise help level 665 of “low” that may cause the interface to be streamlined by minimizing the level of help offered regarding use of the enterprise service. On the other hand, the interface adaptation may indicate a clientdevice help level 670 that is “moderate to high,” (e.g., the company recently may have replaced a notebook computer on which David Dudley was proficient with the PDA). In that circumstance, the clientdevice help level 670 may cause the user interface to provide a moderate to high level of help with respect to the client PDA. - Finally, the interface adaptation may indicate675 that help should be offered to David Dudley in a proactive style (e.g., offered when a pause indicates possible user confusion). This determination may be based on the context information showing that David Dudley historically has preferred a passive role in receiving help. The interface adaptation might provide that the help style should be passive (e.g., activated only upon user request) if the context information indicated that David Dudley preferred to refer to help only after having failed himself to determine a solution.
- The
interface adaptation 650 may be implemented based on an interface or protocol associated with the interface adaptation service, and/or as a data structure. For example, the interface adaptation service may “push” the information of theinterface adaptation 650 to the enterprise service or the client device using a suitable protocol. The interface adaptation service also may be configured to populate the information of theinterface adaptation 650 into an appropriate data structure. The enterprise service or the client device may then access the information of theinterface adaptation 650 by accessing the data structure. - FIGS.7A-C illustrate an interaction of David Dudley with the client PDA using the adapted interface.
- Referring to FIG. 7A, the client PDA initially may await for David Dudley to provide login information or to demonstrate an intent to login. For example, David Dudley might provide login information using a handwriting recognition system of the PDA, through an attached keyboard, or might indicate an intent to login vocally by saying “Login.” Upon receiving the verbal command “login,” the client PDA might respond: “To login, state your username and password.” Alternatively, the client PDA might employ biometrics such as through finger-printing or a voice scan to provide the needed identification and authentication.
- Referring to FIG. 7B, once David Dudley has logged onto the system, the context adaptation service may determine context and adapt the client PDA interface as described above. Based on the interface adaptation, the client PDA may display a main menu offering selections related to David Dudley's immediate and near future tasks as a truck driver. These might include his short term transport schedule, as well as any maintenance scheduled for his truck for the same period. Based on the interface adaptation determination of voice as the primary interface, the client PDA may present the menu information vocally without further prompting by David Dudley. For example, the interface may instruct: “To select from the Main menu, state ‘one’ or ‘transport schedule’ to select the first item, or state ‘two’ or truck maintenance’ to select the second item.” David Dudley might determine to access the transport schedule and might do so by stating “one.”
- Referring to FIG. 7C, the client PDA may respond to David Dudley's instruction by indicating through speech that “Your current delivery time is delayed by 3-hours at the customer's request; pick-up for you next delivery is deferred for 3-hours.” Similar information also may be provided textually by the client PDA. The textual information displayed by the client PDA may be more limited in view of a more limited display capacity of the PDA. The client PDA may provide an associated on screen text description as shown in FIG. 7C, but may require a user to make an additional selection to provide the more detailed information readily provided using voice.
- The context information may be updated to match changing context continuously, periodically, or by any other suitable method. As context information changes in response to changing context, the interface adaptation also may be updated. For example, David Dudley may determine to stop at a diner to eat before reaching Fairbanks, but to continue interacting with the enterprise service while at the diner. The context information may be updated to reflect that David Dudley no is outside of his truck which no longer is moving. Moreover, the noise level in the diner may be high. In view of the changed context, the interface adaptation may indicate that that the primary interface path should be text rather than voice based on the noise level and in order to protect privacy while David Dudley is outside of his truck.
- Other implementations are within the scope of the following claims. For example, enterprise process workflows also may be adapted to recognize and respond automatically to complex situations based on multi-dimensional context information. Multi-dimensional context information also may improve user identification and authentication schemes by combining existing enterprise information with, for example, biometric identification of a user.
Claims (47)
1. An enterprise system with multi-dimensional context awareness, the system comprising:
a network;
an enterprise service coupled to the network;
a plurality of clients configured to communicate with the network to access the enterprise service, wherein each client includes a user interface by which a user may interact with the enterprise service;
a plurality of information sources that include enterprise information related to one or more activities of the enterprise system;
a context determination service configured to determine context information describing a multi-dimensional context based on the enterprise information, wherein the context information comprises a user identification, an identification of the client selected by the user, a user role, a user expertise related to the enterprise service, and a user expertise related to the selected client; and
an interface adaptation service operable to adapt the user interface of the selected client based on the context information.
2. The system of claim 1 wherein the plurality of clients comprise one or more wireless handheld devices.
3. The system of claim 1 , wherein adapting the user interface of the selected client based on the context information comprises selecting a sensory communication path for the interaction of the user with the enterprise service that is suited to a context described by the context information.
4. The system of claim 3 wherein the sensory communication path selected comprises a voice communication path.
5. The system of claim 3 wherein the sensory communication path selected comprises a text communication path.
6. The system of claim 3 wherein the sensory communication path selected comprises a graphical communication path.
7. The system of claim 1 , wherein adapting the user interface of the selected client based on the context information comprises adapting the user interface to adjust a level of help automatically provided to the user regarding operation of the selected client based on the context information describing the user expertise related to the selected client.
8. The system of claim 1 , wherein adapting the user interface of the selected client based on the context information comprises adapting the user interface to adjust a level of help automatically provided to the user regarding operation of the enterprise service based on the context information describing the user expertise related to the enterprise service.
9. The system of claim 1 , wherein adapting the user interface of the selected client based on the context information comprises adapting the user interface to present only information to the user relevant to the user role described by the context information.
10. The system of claim 1 , wherein adapting the user interface of the selected client based on the context information comprises adapting the user interface to present only information to the user relevant to the user identification described by the context information.
11. The system of claim 1 wherein the context determination service comprises a rule engine.
12. The system of claim 1 wherein the context determination service comprises an inference engine.
13. The system of claim 12 wherein the inference engine comprises a Bayesian reasoning engine.
14. The system of claim 1 wherein the interface adaptation service comprises a rule engine.
15. The system of claim 1 wherein the interface adaptation service comprises an inference engine.
16. The system of claim 15 wherein the inference engine comprises a Bayesian reasoning engine.
17. The system of claim 1 wherein the context information further comprises a measure of time.
18. The system of claim 1 wherein the context information further includes information regarding a physical environment of the user.
19. The system of claim 18 wherein the physical environment information includes information related to a location of the user, an activity of the user, a measure of background noise, and a measure of lightness or darkness.
20. The system of claim 1 wherein the plurality of information sources includes one or more databases.
21. The system of claim 1 wherein the plurality of information sources includes a security device.
22. The system of claim 1 wherein the plurality of information sources includes a global positioning system.
23. The system of claim 1 wherein the plurality of information sources does not include an information source configured only to provide context information.
24. The system of claim 23 wherein the plurality of information sources does not include a GPS configured to provide a location of a client device.
25. A method of adapting a user interface of a client in an enterprise system based on multi-dimensional context information, the method comprising:
receiving a request of a user to login to an enterprise service of the enterprise system using a client;
determining first information based on the request to login to the enterprise service using the client;
determining second information from a plurality of information sources of the enterprise system based on the first information;
determining context information describing a multi-dimensional context based on the first information and the second information, wherein the context information comprises a user identification, a client identification, a user role, a user expertise related to the enterprise service, and a user expertise related to the client; and
adapting the user interface of the client based on the context information.
26. The method of claim 25 , wherein adapting the user interface of the client based on the context information comprises selecting a sensory communication path for the interaction of the user with the enterprise service that is suited to a context described by the context information.
27. The method of claim 26 wherein the sensory communication path selected comprises a voice communication path.
28. The method of claim 26 wherein the sensory communication path selected comprises a text communication path.
29. The method of claim 26 wherein the sensory communication path selected comprises a graphical communication path.
30. The method of claim 25 , wherein adapting the user interface of the client based on the context information comprises adapting the user interface to adjust a level of help automatically provided to the user regarding operation of the client based on the context information describing the user expertise related to the client.
31. The method of claim 25 , wherein adapting the user interface of the client based on the context information comprises adapting the user interface to adjust a level of help automatically provided to the user regarding operation of the enterprise service based on the context information describing the user expertise related to the enterprise service.
32. The method of claim 25 , wherein adapting the user interface of the client based on the context information comprises adapting the user interface to present only information to the user relevant to the user role described by the context information.
33. A computer program for adapting a user interface of a client in an enterprise system based on multi-dimensional context information, the computer program comprising:
a login code segment to cause a computer to receive a request of a user to login to an enterprise service of the enterprise system using a client;
a first information determination code segment to cause the computer to determine first information based on the request to login to the enterprise service using the client;
a second information determination code segment to cause the computer to determine second information from a plurality of information sources of the enterprise system based on the first information;
a context information determination code segment to cause the computer to determine context information describing a multi-dimensional context based on the first information and the second information, wherein the context information comprises a user identification, a client identification, a user role, a user expertise related to the enterprise service, and a user expertise related to the client; and
an adaptation code segment to cause the computer to adapt the user interface of the client based on the context information.
34. The computer program of claim 33 , wherein adapting the user interface of the client based on the context information comprises selecting a sensory communication path for the interaction of the user with the enterprise service that is suited to a context described by the context information.
35. The computer program of claim 34 wherein the sensory communication path selected comprises a voice communication path.
36. The computer program of claim 34 wherein the sensory communication path selected comprises a text communication path.
37. The computer program of claim 34 wherein the sensory communication path selected comprises a graphical communication path.
38. The computer program of claim 33 , wherein adapting the user interface of the client based on the context information comprises adapting the user interface to adjust a level of help automatically provided to the user regarding operation of the client based on the context information describing the user expertise related to the client.
39. The computer program of claim 33 , wherein adapting the user interface of the client based on the context information comprises adapting the user interface to adjust a level of help automatically provided to the user regarding operation of the enterprise service based on the context information describing the user expertise related to the enterprise service.
40. The computer program of claim 33 , wherein adapting the user interface of the client based on the context information comprises adapting the user interface to present only information to the user relevant to the user role described by the context information.
41. A method of adapting a user interface of a client in an enterprise system based on multi-dimensional context information, the method comprising:
receiving a request of a user to login to an enterprise service of the enterprise system using a client;
determining first information based on the request to login to the enterprise service using the client;
determining second information from a plurality of information sources of the enterprise system based on the first information;
determining context information describing a multi-dimensional context based on the first information and the second information; and
adapting the user interface of the client based on the context information.
42. The method of claim 41 , wherein adapting the user interface of the client based on the multi-dimensional context information comprises selecting a sensory communication path for the interaction of the user with the enterprise service that is suited to a context described by the multi-dimensional context information.
43. The method of claim 42 wherein the sensory communication path selected comprises a voice communication path.
44. The method of claim 42 wherein the sensory communication path selected comprises a text communication path.
45. The method of claim 42 wherein the sensory communication path selected comprises a graphical communication path.
46. The method of claim 41 , wherein adapting the user interface of the client based on the multi-dimensional context information comprises adapting the user interface to adjust a level of help automatically provided to the user based on the multi-dimensional context information.
47. The method of claim 41 , wherein adapting the user interface of the client based on the multi-dimensional context information comprises adapting the user interface to present only information to the user relevant to a context described by the multi-dimensional context information.
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/457,010 US20040006593A1 (en) | 2002-06-14 | 2003-06-09 | Multidimensional approach to context-awareness |
EP03759957A EP1514178B1 (en) | 2002-06-14 | 2003-06-13 | Multidimensional approach to context-awareness |
PCT/EP2003/006269 WO2003107179A1 (en) | 2002-06-01 | 2003-06-13 | Multidimensional approach to context-awareness |
AU2003257417A AU2003257417A1 (en) | 2002-06-14 | 2003-06-13 | Multidimensional approach to context-awareness |
DE60313457T DE60313457T2 (en) | 2002-06-14 | 2003-06-13 | MULTIDIMENSIONAL APPROACH TO CONTEXT CONSCIOUSNESS |
US12/210,493 US8126984B2 (en) | 2002-06-14 | 2008-09-15 | Multidimensional approach to context-awareness |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US38828902P | 2002-06-14 | 2002-06-14 | |
US42211202P | 2002-10-30 | 2002-10-30 | |
US10/457,010 US20040006593A1 (en) | 2002-06-14 | 2003-06-09 | Multidimensional approach to context-awareness |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/210,493 Continuation US8126984B2 (en) | 2002-06-14 | 2008-09-15 | Multidimensional approach to context-awareness |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040006593A1 true US20040006593A1 (en) | 2004-01-08 |
Family
ID=29740836
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/457,010 Abandoned US20040006593A1 (en) | 2002-06-01 | 2003-06-09 | Multidimensional approach to context-awareness |
US12/210,493 Expired - Fee Related US8126984B2 (en) | 2002-06-14 | 2008-09-15 | Multidimensional approach to context-awareness |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/210,493 Expired - Fee Related US8126984B2 (en) | 2002-06-14 | 2008-09-15 | Multidimensional approach to context-awareness |
Country Status (5)
Country | Link |
---|---|
US (2) | US20040006593A1 (en) |
EP (1) | EP1514178B1 (en) |
AU (1) | AU2003257417A1 (en) |
DE (1) | DE60313457T2 (en) |
WO (1) | WO2003107179A1 (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004114190A1 (en) * | 2003-06-16 | 2004-12-29 | Uru Technology Incorporated | Method and system for creating and operating biometrically enabled multi-purpose credential management devices |
US20050086264A1 (en) * | 2003-10-16 | 2005-04-21 | Fuji Xerox Co., Ltd. | Application program execution system, sensor, first server, second server, and object thereof and application program execution method |
US20060087474A1 (en) * | 2004-10-27 | 2006-04-27 | Do Phuc K | Method and system for monitoring location based service emitter instructure |
KR100587563B1 (en) | 2004-07-26 | 2006-06-08 | 삼성전자주식회사 | Apparatus and method for providing context-aware service |
US20070160564A1 (en) * | 2001-02-28 | 2007-07-12 | Jue-Chen Liu | Compositions Containing Legume Products |
US20080005679A1 (en) * | 2006-06-28 | 2008-01-03 | Microsoft Corporation | Context specific user interface |
US20080016580A1 (en) * | 2006-07-11 | 2008-01-17 | Royyuru Dixit | Role-based access in a multi-customer computing environment |
KR100844293B1 (en) | 2007-01-04 | 2008-07-07 | 성균관대학교산학협력단 | Management System of Situational Awareness Security Service and Management Method |
US20080250316A1 (en) * | 2007-04-04 | 2008-10-09 | Honeywell International Inc. | Mechanism to improve a user's interaction with a computer system |
US20080270913A1 (en) * | 2007-04-26 | 2008-10-30 | Howard Singer | Methods, Media, and Devices for Providing a Package of Assets |
US20100138759A1 (en) * | 2006-11-03 | 2010-06-03 | Conceptual Speech, Llc | Layered contextual configuration management system and method and minimized input speech recognition user interface interactions experience |
US20100250530A1 (en) * | 2009-03-31 | 2010-09-30 | Oracle International Corporation | Multi-dimensional algorithm for contextual search |
KR101027667B1 (en) | 2008-02-27 | 2011-04-12 | 성균관대학교산학협력단 | Context-aware access control management system, its management method and recording medium |
US20130031619A1 (en) * | 2011-07-25 | 2013-01-31 | Lenovo (Singapore) Pte. Ltd. | Remote authentication screen locker for a mobile device |
US20130073634A1 (en) * | 2011-09-16 | 2013-03-21 | Oracle International Corporation | Email client with erp task integration |
US20130239048A1 (en) * | 2005-11-30 | 2013-09-12 | Microsoft Corporation | Centralized User Interface for Displaying Contextually Driven Business Content and Business Related Functionality |
US20160035006A1 (en) * | 2014-05-13 | 2016-02-04 | Paypal, Inc. | Streamlined online checkout |
US9565528B2 (en) * | 2015-04-08 | 2017-02-07 | Verizon Patent And Licensing Inc. | Providing a message based on translating a beacon identifier to a virtual beacon identifier |
US10026058B2 (en) | 2010-10-29 | 2018-07-17 | Microsoft Technology Licensing, Llc | Enterprise resource planning oriented context-aware environment |
Families Citing this family (72)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050278640A1 (en) * | 2004-06-09 | 2005-12-15 | Jones Edwin R | System and method of dynamic entitlement |
US7614049B2 (en) | 2004-08-24 | 2009-11-03 | International Business Machines Corporation | Autonomic installation and configuration of an enterprise business process on-demand |
US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US7433741B2 (en) | 2005-09-30 | 2008-10-07 | Rockwell Automation Technologies, Inc. | Hybrid user interface having base presentation information with variably prominent supplemental information |
US20070078535A1 (en) * | 2005-09-30 | 2007-04-05 | Rockwell Automation Technologies, Inc. | System and method for identifying particularized equipment information of interest to varied users in an industrial automation environment |
US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
US8996376B2 (en) | 2008-04-05 | 2015-03-31 | Apple Inc. | Intelligent text-to-speech conversion |
US8209638B2 (en) * | 2008-12-31 | 2012-06-26 | Sap Ag | Customization abstraction |
US10241752B2 (en) | 2011-09-30 | 2019-03-26 | Apple Inc. | Interface for a virtual digital assistant |
US9858925B2 (en) | 2009-06-05 | 2018-01-02 | Apple Inc. | Using context information to facilitate processing of commands in a virtual assistant |
US10241644B2 (en) | 2011-06-03 | 2019-03-26 | Apple Inc. | Actionable reminder entries |
US9431006B2 (en) | 2009-07-02 | 2016-08-30 | Apple Inc. | Methods and apparatuses for automatic speech recognition |
US8682667B2 (en) | 2010-02-25 | 2014-03-25 | Apple Inc. | User profiling for selecting user specific voice input processing information |
US10511609B2 (en) | 2010-09-15 | 2019-12-17 | Core Mobile Networks, Inc. | Context-based analytics and intelligence |
US8606923B2 (en) * | 2010-09-15 | 2013-12-10 | Core Mobile Networks, Inc. | System and method for real time delivery of context based content from the cloud to mobile devices |
CN102023894A (en) * | 2010-11-18 | 2011-04-20 | 华为终端有限公司 | User operation interface transformation method and terminal |
US8555249B2 (en) * | 2010-12-13 | 2013-10-08 | Sap Ag | Lifecycle stable user interface adaptations |
US8214904B1 (en) * | 2011-12-21 | 2012-07-03 | Kaspersky Lab Zao | System and method for detecting computer security threats based on verdicts of computer users |
US8209758B1 (en) * | 2011-12-21 | 2012-06-26 | Kaspersky Lab Zao | System and method for classifying users of antivirus software based on their level of expertise in the field of computer security |
US8214905B1 (en) * | 2011-12-21 | 2012-07-03 | Kaspersky Lab Zao | System and method for dynamically allocating computing resources for processing security information |
US9280610B2 (en) | 2012-05-14 | 2016-03-08 | Apple Inc. | Crowd sourcing information to fulfill user requests |
US9721563B2 (en) | 2012-06-08 | 2017-08-01 | Apple Inc. | Name recognition system |
US20140068445A1 (en) * | 2012-09-06 | 2014-03-06 | Sap Ag | Systems and Methods for Mobile Access to Enterprise Work Area Information |
US9058583B2 (en) | 2012-09-06 | 2015-06-16 | Sap Se | Systems and methods for mobile access to item information |
US9547647B2 (en) | 2012-09-19 | 2017-01-17 | Apple Inc. | Voice-based media searching |
US20140181652A1 (en) * | 2012-12-21 | 2014-06-26 | Timothy A. Stanke | Contextual and Personalized Help |
US9807145B2 (en) | 2013-05-10 | 2017-10-31 | Successfactors, Inc. | Adaptive tile framework |
WO2014197334A2 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
US9350625B2 (en) | 2013-06-25 | 2016-05-24 | Sap Se | Service consumption based on gamification level classification |
US20150025927A1 (en) * | 2013-07-16 | 2015-01-22 | Raytheon Company | Mission component evaluation and response architecture |
US9747463B2 (en) | 2013-11-30 | 2017-08-29 | Sap Se | Securing access to business information |
US9430463B2 (en) | 2014-05-30 | 2016-08-30 | Apple Inc. | Exemplar-based natural language processing |
US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US9668121B2 (en) | 2014-09-30 | 2017-05-30 | Apple Inc. | Social reminders |
US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
US9578173B2 (en) | 2015-06-05 | 2017-02-21 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
CN105023101A (en) * | 2015-07-17 | 2015-11-04 | 浙江云景信息科技有限公司 | Intelligent and integrated management cloud platform for primary and secondary school students |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US10366158B2 (en) | 2015-09-29 | 2019-07-30 | Apple Inc. | Efficient word encoding for recurrent neural network language models |
US11010550B2 (en) | 2015-09-29 | 2021-05-18 | Apple Inc. | Unified language modeling framework for word prediction, auto-completion and auto-correction |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US10446143B2 (en) | 2016-03-14 | 2019-10-15 | Apple Inc. | Identification of voice inputs providing credentials |
US9934775B2 (en) | 2016-05-26 | 2018-04-03 | Apple Inc. | Unit-selection text-to-speech synthesis based on predicted concatenation parameters |
US9972304B2 (en) | 2016-06-03 | 2018-05-15 | Apple Inc. | Privacy preserving distributed evaluation framework for embedded personalized systems |
US10249300B2 (en) | 2016-06-06 | 2019-04-02 | Apple Inc. | Intelligent list reading |
US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
DK179309B1 (en) | 2016-06-09 | 2018-04-23 | Apple Inc | Intelligent automated assistant in a home environment |
US10509862B2 (en) | 2016-06-10 | 2019-12-17 | Apple Inc. | Dynamic phrase expansion of language input |
US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US10192552B2 (en) | 2016-06-10 | 2019-01-29 | Apple Inc. | Digital assistant providing whispered speech |
US10490187B2 (en) | 2016-06-10 | 2019-11-26 | Apple Inc. | Digital assistant providing automated status report |
DK179049B1 (en) | 2016-06-11 | 2017-09-18 | Apple Inc | Data driven natural language event detection and classification |
DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
DK179343B1 (en) | 2016-06-11 | 2018-05-14 | Apple Inc | Intelligent task discovery |
DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
US11361266B2 (en) | 2017-03-20 | 2022-06-14 | Microsoft Technology Licensing, Llc | User objective assistance technologies |
DK201770439A1 (en) | 2017-05-11 | 2018-12-13 | Apple Inc. | Offline personal assistant |
DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
DK201770432A1 (en) | 2017-05-15 | 2018-12-21 | Apple Inc. | Hierarchical belief states for digital assistants |
DK201770431A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
DK179560B1 (en) | 2017-05-16 | 2019-02-18 | Apple Inc. | Far-field extension for digital assistant services |
EP3605326B1 (en) | 2018-07-31 | 2021-09-08 | Hewlett Packard Enterprise Development LP | Combining computer applications |
US11438452B1 (en) | 2019-08-09 | 2022-09-06 | Apple Inc. | Propagating context information in a privacy preserving manner |
US11157679B2 (en) * | 2020-01-27 | 2021-10-26 | Capital One Services, Llc | Semantic navigation of content documents |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5799292A (en) * | 1994-04-29 | 1998-08-25 | International Business Machines Corporation | Adaptive hypermedia presentation method and system |
US5930699A (en) * | 1996-11-12 | 1999-07-27 | Ericsson Inc. | Address retrieval system |
US5948040A (en) * | 1994-06-24 | 1999-09-07 | Delorme Publishing Co. | Travel reservation information and planning system |
US6026375A (en) * | 1997-12-05 | 2000-02-15 | Nortel Networks Corporation | Method and apparatus for processing orders from customers in a mobile environment |
US6049711A (en) * | 1995-08-23 | 2000-04-11 | Teletrac, Inc. | Method and apparatus for providing location-based information services |
US6088594A (en) * | 1997-11-26 | 2000-07-11 | Ericsson Inc. | System and method for positioning a mobile terminal using a terminal based browser |
US6199099B1 (en) * | 1999-03-05 | 2001-03-06 | Ac Properties B.V. | System, method and article of manufacture for a mobile communication network utilizing a distributed communication network |
US6236978B1 (en) * | 1997-11-14 | 2001-05-22 | New York University | System and method for dynamic profiling of users in one-to-one applications |
US6260035B1 (en) * | 1996-07-19 | 2001-07-10 | Microsoft Corporation | Intelligent user assistance facility for a software program |
US20010018349A1 (en) * | 2000-02-29 | 2001-08-30 | Jair Kinnunen | Location dependent services |
US20030090515A1 (en) * | 2001-11-13 | 2003-05-15 | Sony Corporation And Sony Electronics Inc. | Simplified user interface by adaptation based on usage history |
US20030144846A1 (en) * | 2002-01-31 | 2003-07-31 | Denenberg Lawrence A. | Method and system for modifying the behavior of an application based upon the application's grammar |
US20030182394A1 (en) * | 2001-06-07 | 2003-09-25 | Oren Ryngler | Method and system for providing context awareness |
US20030208459A1 (en) * | 2002-05-06 | 2003-11-06 | Shea Gabriel O. | Collaborative context information management system |
US20060200260A1 (en) * | 1991-12-23 | 2006-09-07 | Steven Hoffberg | System and method for intermachine markup language communications |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4964077A (en) * | 1987-10-06 | 1990-10-16 | International Business Machines Corporation | Method for automatically adjusting help information displayed in an online interactive system |
US5115501A (en) * | 1988-11-04 | 1992-05-19 | International Business Machines Corporation | Procedure for automatically customizing the user interface of application programs |
TW426175U (en) * | 1999-03-16 | 2001-03-11 | Hon Hai Prec Ind Co Ltd | Carrying apparatus for electric circuit board |
AU2001249261A1 (en) * | 2000-03-16 | 2001-09-24 | Microsoft Corporation | Notification platform architecture |
ATE377330T1 (en) * | 2000-04-11 | 2007-11-15 | American Calcar Inc | GPS PUBLICATION APPLICATION SERVER |
GB2386724A (en) * | 2000-10-16 | 2003-09-24 | Tangis Corp | Dynamically determining appropriate computer interfaces |
US20020101448A1 (en) * | 2000-11-29 | 2002-08-01 | Sanderson Richard A. | Generating a declarative user interface |
-
2003
- 2003-06-09 US US10/457,010 patent/US20040006593A1/en not_active Abandoned
- 2003-06-13 AU AU2003257417A patent/AU2003257417A1/en not_active Abandoned
- 2003-06-13 WO PCT/EP2003/006269 patent/WO2003107179A1/en active IP Right Grant
- 2003-06-13 DE DE60313457T patent/DE60313457T2/en not_active Expired - Lifetime
- 2003-06-13 EP EP03759957A patent/EP1514178B1/en not_active Expired - Lifetime
-
2008
- 2008-09-15 US US12/210,493 patent/US8126984B2/en not_active Expired - Fee Related
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060200260A1 (en) * | 1991-12-23 | 2006-09-07 | Steven Hoffberg | System and method for intermachine markup language communications |
US5799292A (en) * | 1994-04-29 | 1998-08-25 | International Business Machines Corporation | Adaptive hypermedia presentation method and system |
US5948040A (en) * | 1994-06-24 | 1999-09-07 | Delorme Publishing Co. | Travel reservation information and planning system |
US6049711A (en) * | 1995-08-23 | 2000-04-11 | Teletrac, Inc. | Method and apparatus for providing location-based information services |
US6260035B1 (en) * | 1996-07-19 | 2001-07-10 | Microsoft Corporation | Intelligent user assistance facility for a software program |
US5930699A (en) * | 1996-11-12 | 1999-07-27 | Ericsson Inc. | Address retrieval system |
US6236978B1 (en) * | 1997-11-14 | 2001-05-22 | New York University | System and method for dynamic profiling of users in one-to-one applications |
US6088594A (en) * | 1997-11-26 | 2000-07-11 | Ericsson Inc. | System and method for positioning a mobile terminal using a terminal based browser |
US6026375A (en) * | 1997-12-05 | 2000-02-15 | Nortel Networks Corporation | Method and apparatus for processing orders from customers in a mobile environment |
US6199099B1 (en) * | 1999-03-05 | 2001-03-06 | Ac Properties B.V. | System, method and article of manufacture for a mobile communication network utilizing a distributed communication network |
US20010018349A1 (en) * | 2000-02-29 | 2001-08-30 | Jair Kinnunen | Location dependent services |
US20030182394A1 (en) * | 2001-06-07 | 2003-09-25 | Oren Ryngler | Method and system for providing context awareness |
US20030090515A1 (en) * | 2001-11-13 | 2003-05-15 | Sony Corporation And Sony Electronics Inc. | Simplified user interface by adaptation based on usage history |
US20030144846A1 (en) * | 2002-01-31 | 2003-07-31 | Denenberg Lawrence A. | Method and system for modifying the behavior of an application based upon the application's grammar |
US20030208459A1 (en) * | 2002-05-06 | 2003-11-06 | Shea Gabriel O. | Collaborative context information management system |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070160564A1 (en) * | 2001-02-28 | 2007-07-12 | Jue-Chen Liu | Compositions Containing Legume Products |
US7715593B1 (en) | 2003-06-16 | 2010-05-11 | Uru Technology Incorporated | Method and system for creating and operating biometrically enabled multi-purpose credential management devices |
US8144941B2 (en) | 2003-06-16 | 2012-03-27 | Uru Technology Incorporated | Method and system for creating and operating biometrically enabled multi-purpose credential management devices |
US20100275259A1 (en) * | 2003-06-16 | 2010-10-28 | Uru Technology Incorporated | Method and system for creating and operating biometrically enabled multi-purpose credential management devices |
WO2004114190A1 (en) * | 2003-06-16 | 2004-12-29 | Uru Technology Incorporated | Method and system for creating and operating biometrically enabled multi-purpose credential management devices |
US20100117794A1 (en) * | 2003-06-16 | 2010-05-13 | William Mark Adams | Method and system for creating and operating biometrically enabled multi-purpose credential management devices |
US20050086264A1 (en) * | 2003-10-16 | 2005-04-21 | Fuji Xerox Co., Ltd. | Application program execution system, sensor, first server, second server, and object thereof and application program execution method |
US8150952B2 (en) * | 2003-10-16 | 2012-04-03 | Fuji Xerox Co., Ltd. | Application program execution system, sensor, first server, second server, and object thereof and application program execution method |
KR100587563B1 (en) | 2004-07-26 | 2006-06-08 | 삼성전자주식회사 | Apparatus and method for providing context-aware service |
US7283093B2 (en) | 2004-10-27 | 2007-10-16 | International Business Machines Corporation | Method and system for monitoring location based service emitter infrastructure |
US20060087474A1 (en) * | 2004-10-27 | 2006-04-27 | Do Phuc K | Method and system for monitoring location based service emitter instructure |
US20130239048A1 (en) * | 2005-11-30 | 2013-09-12 | Microsoft Corporation | Centralized User Interface for Displaying Contextually Driven Business Content and Business Related Functionality |
US20080005679A1 (en) * | 2006-06-28 | 2008-01-03 | Microsoft Corporation | Context specific user interface |
US20080016580A1 (en) * | 2006-07-11 | 2008-01-17 | Royyuru Dixit | Role-based access in a multi-customer computing environment |
US8336078B2 (en) | 2006-07-11 | 2012-12-18 | Fmr Corp. | Role-based access in a multi-customer computing environment |
US20100138759A1 (en) * | 2006-11-03 | 2010-06-03 | Conceptual Speech, Llc | Layered contextual configuration management system and method and minimized input speech recognition user interface interactions experience |
US9471333B2 (en) * | 2006-11-03 | 2016-10-18 | Conceptual Speech, Llc | Contextual speech-recognition user-interface driven system and method |
KR100844293B1 (en) | 2007-01-04 | 2008-07-07 | 성균관대학교산학협력단 | Management System of Situational Awareness Security Service and Management Method |
US20080250316A1 (en) * | 2007-04-04 | 2008-10-09 | Honeywell International Inc. | Mechanism to improve a user's interaction with a computer system |
US20080270913A1 (en) * | 2007-04-26 | 2008-10-30 | Howard Singer | Methods, Media, and Devices for Providing a Package of Assets |
KR101027667B1 (en) | 2008-02-27 | 2011-04-12 | 성균관대학교산학협력단 | Context-aware access control management system, its management method and recording medium |
US20100250530A1 (en) * | 2009-03-31 | 2010-09-30 | Oracle International Corporation | Multi-dimensional algorithm for contextual search |
US8229909B2 (en) * | 2009-03-31 | 2012-07-24 | Oracle International Corporation | Multi-dimensional algorithm for contextual search |
US10026058B2 (en) | 2010-10-29 | 2018-07-17 | Microsoft Technology Licensing, Llc | Enterprise resource planning oriented context-aware environment |
US20130031619A1 (en) * | 2011-07-25 | 2013-01-31 | Lenovo (Singapore) Pte. Ltd. | Remote authentication screen locker for a mobile device |
US20130073634A1 (en) * | 2011-09-16 | 2013-03-21 | Oracle International Corporation | Email client with erp task integration |
US9911089B2 (en) * | 2011-09-16 | 2018-03-06 | Oracle International Corporation | Email client with ERP task integration |
US20160035006A1 (en) * | 2014-05-13 | 2016-02-04 | Paypal, Inc. | Streamlined online checkout |
US9565528B2 (en) * | 2015-04-08 | 2017-02-07 | Verizon Patent And Licensing Inc. | Providing a message based on translating a beacon identifier to a virtual beacon identifier |
Also Published As
Publication number | Publication date |
---|---|
DE60313457D1 (en) | 2007-06-06 |
US8126984B2 (en) | 2012-02-28 |
DE60313457T2 (en) | 2008-01-03 |
EP1514178B1 (en) | 2007-04-25 |
WO2003107179A1 (en) | 2003-12-24 |
EP1514178A1 (en) | 2005-03-16 |
AU2003257417A1 (en) | 2003-12-31 |
US20090013038A1 (en) | 2009-01-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1514178B1 (en) | Multidimensional approach to context-awareness | |
US11544675B2 (en) | Contextually aware schedule services | |
US10796247B2 (en) | System for managing risk in employee travel | |
EP1363221B1 (en) | Increasing the level of automation when scheduling and managing meetings | |
US9323849B2 (en) | Personalising content provided to a user | |
US20030182394A1 (en) | Method and system for providing context awareness | |
CA2695194C (en) | Method and system for presenting a mash-up, or personalized mixture, and associated contextual suggestions to mobile users | |
US20170289305A1 (en) | Extensibility for context-aware digital personal assistant | |
WO2007024704A2 (en) | Virtual assistant | |
US20070239506A1 (en) | Priority based scheduling system | |
US20020103865A1 (en) | Logbook database system | |
JPH1055259A (en) | User interface environment setting method and data processing system | |
CN110337660B (en) | Context application organizer framework for user life events | |
US20130165153A1 (en) | System for Managing Risk in Employee Travel | |
US9898555B2 (en) | Systems and methods to automatically suggest elements for a content aggregation system | |
US8667602B2 (en) | System for managing risk in employee travel | |
WO2002091128A2 (en) | System and method for seminar reservations | |
US12034602B2 (en) | Management of computing devices via reference to linked employee records | |
Hong et al. | Ubiquitous enterprise service adaptations based on contextual user behavior | |
US20150120587A1 (en) | Use of a social network to enhance hiring team collaboration | |
AU2018299827A1 (en) | System and method for dynamically delivering content | |
US9665834B2 (en) | System for managing risk in employee travel | |
CN116261752A (en) | User-oriented actions based on audio conversations | |
US20080178075A1 (en) | Configuration Data Store for Overriding a Web Application Configuration Involving Multiple Customers | |
Hertzog et al. | Context-aware mobile assistants for optimal interaction: a prototype for supporting the business traveler |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAP AKTIENGESELLSCHAFT, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VOGLER, HARTMUT K.;GOSLAR, KEVIN;REEL/FRAME:013995/0412;SIGNING DATES FROM 20030902 TO 20030904 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |