WO2015172106A1 - Displaying information in association with communication - Google Patents

Displaying information in association with communication Download PDF

Info

Publication number
WO2015172106A1
WO2015172106A1 PCT/US2015/030025 US2015030025W WO2015172106A1 WO 2015172106 A1 WO2015172106 A1 WO 2015172106A1 US 2015030025 W US2015030025 W US 2015030025W WO 2015172106 A1 WO2015172106 A1 WO 2015172106A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
specific content
voice communication
time voice
real
Prior art date
Application number
PCT/US2015/030025
Other languages
French (fr)
Other versions
WO2015172106A8 (en
Inventor
Raymond P. Kasbarian
Original Assignee
Zypline Services, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to US201461990559P priority Critical
Priority to US61/990,559 priority
Application filed by Zypline Services, Inc. filed Critical Zypline Services, Inc.
Publication of WO2015172106A1 publication Critical patent/WO2015172106A1/en
Publication of WO2015172106A8 publication Critical patent/WO2015172106A8/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42034Calling party identification service
    • H04M3/42042Notifying the called party of information on the calling party
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42034Calling party identification service
    • H04M3/42059Making use of the calling party identifier
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42085Called party identification service
    • H04M3/42093Notifying the calling party of information on the called or connected party
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42085Called party identification service
    • H04M3/42102Making use of the called party identifier

Abstract

A technique for displaying information in association with communication involves a mobile device engaging in communication with an entity. The mobile device (and/or one or more other computing systems) can determine that a phone number of the entity identifies entity-specific content associated with the entity. For example, the entity-specific content is associated with the entity and is identifiable based on the phone number of the entity. The mobile device can detect at least one of an incoming real-time voice communication associated with the phone number or an outgoing real-time voice communication associated with the phone number. The mobile device can acquire from an entity-specific content source the entity-specific content identified based on the phone number. The mobile device can further display (or otherwise present) at least a portion of the entity-specific content during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication.

Description

DISPLAYING INFORMATION IN ASSOCIATION WITH MOBILE

COMMUNICATION

BACKGROUND

[0001] An area of ongoing research and development is in mobile computing devices or systems. Many people use mobile computing devices or systems (also known as mobile devices) for a wide variety of purposes. In some cases, users of mobile devices can make phone calls and receive phone calls. In some instances, users can use their mobile devices to access content made available through one or more networks, such as when browsing the Internet. Moreover, users can use their mobile devices to create, develop, and/or provide content. Furthermore, in some cases, users can run applications (apps) or other software on their mobile devices.

[0002] A specific area of interest is communications for mobile devices. In some implementations, conventional approaches to mobile device communications can involve a mobile device engaging in telephonic communications with another device or system capable of telephonic communications. In one example, a mobile device can make a phone call to or receive a phone call from a dedicated telephone device or system (e.g., land-line, voice over IP, etc.). In another example, two or more mobile devices can communicate with one another through telephonic communications. Further, in some implementations, conventional approaches to mobile device communications can involve a mobile device communicating with a networked device or system through one or more network connections. For example, the mobile device can transmit data to and receive data from an online service or server via the Internet. In another example, multiple mobile devices can share data among themselves. However, conventional approaches to mobile device communications can sometimes be inconvenient, inefficient, and/or impractical. [0003] The foregoing discussion of related art is intended to be illustrative and not exclusive. The problems or concerns associated with conventional approaches can create challenges for and reduce the overall experience associated with using mobile devices. Other limitations of the relevant art will become apparent to those of skill in the art upon a reading of the specification and a study of the drawings.

SUMMARY

[0004] The following embodiments and aspects thereof are described and illustrated in conjunction with systems, tools, and methods that are meant to be exemplary and illustrative, not necessarily limiting in scope. In various embodiments, one or more of the above-described problems have been addressed, while other embodiments are directed to other improvements.

[0005] A technique for displaying information in association with communication involves a mobile device engaging in communication with an entity. The mobile device can determine that a phone number of the entity identifies entity- specific content associated with the entity. For example, the entity- specific content is associated with the entity and is identifiable based on the phone number of the entity. The mobile device can detect at least one of an incoming real-time voice communication associated with the phone number or an outgoing real-time voice communication associated with the phone number. The mobile device can acquire from an entity- specific content source the entity- specific content identified based on the phone number. The mobile device can further display (or otherwise present) at least a portion of the entity- specific content during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication.

[0006] In some implementations, the entity- specific content can be acquired via a data communication with an entity- specific content source (e.g., an entity- specific content datastore) concurrent to or during the real-time voice communication with a real-time voice communication device used by the entity. In some instances, the entity- specific content can be acquired from the entity- specific content source by the mobile device prior to and/or after the real-time voice communication as well. For example, if the entity- specific content is acquired after the real-time voice communication, then the entity- specific content is to be displayed after the real-time voice communication.

[0007] In some implementations, the entity- specific content can be acquired by the mobile device by pulling or fetching the entity- specific content from the entity- specific content source. In some implementations, the entity- specific content can be acquired by the mobile device when the entity- specific content is pushed from the entity- specific content source.

[0008] These and other advantages will become apparent to those skilled in the relevant art upon a reading of the following descriptions and a study of the several examples of the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. 1 depicts a diagram of an example of a system in which information can be displayed in association with communication.

[0010] FIG. 2 depicts a diagram of an example of a system configured to facilitate displaying information in association with communication.

[0011] FIG. 3A depicts a diagram of an example of a mobile device configured to facilitate displaying information in association with communication.

[0012] FIG. 3B depicts a diagram of an example of a mobile device configured to facilitate displaying information in association with communication.

[0013] FIG. 4 depicts a flowchart of an example of a method for facilitating a display of information in association with communication.

[0014] FIG. 5 depicts a diagram of an example of a mobile device configured to facilitate displaying information in association with communication.

DETAILED DESCRIPTION

[0015] FIG. 1 depicts a diagram 100 of an example of a system in which information can be displayed in association with communication. The diagram 100 can include a computer- readable medium 102, an entity- specific content datastore 104, a mobile device 106, an entity- specific concurrent communications management engine 108, and an entity- associated communications device 110. The mobile device 106 can include an entity- specific content display 112 and a communications interface 114.

[0016] In the example of FIG. 1, the computer-readable medium 102 can include communications hardware and/or software within a single computer, a device locally attached to a computer, and/or a networked system that includes several computer systems coupled together, such as a local area network (LAN), wireless local area network (WLAN), campus area network (CAN), municipal or metropolitan area network (MAN), wide area network (WAN), telephone network, cellular network, any other applicable type of network(s), or any combination thereof. The computer-readable medium 102 can at least theoretically be of any size and/or characterized in some other fashion (e.g., personal area network (PAN) or home area network (HAN), to name a couple of alternatives).

[0017] Networks can include enterprise private networks and virtual private networks (collectively, private networks). As the name suggests, private networks are under the control of an entity rather than being open to the public. Where context dictates a single entity would control a network, it should be understood that reference to a network is a reference to the private portion subset of that network. For example, a LAN can be on a WAN, but only the LAN under the control of an entity; so if an engine controls policy on the network, it may be that the engine only controls policy on the LAN (or some other subset of the WAN). Private networks can include a head office and optional regional offices (collectively, offices). Many offices enable remote users to connect to the private network offices via some other network, such as the Internet. In specific implementations, networks can be implemented as a WAN, a LAN, a WLAN, a telephone network such as a public switched telephone network (PSTN), a cellular network, or some other network or combination of similar or different networks capable of coupling multiple networks.

[0018] As discussed, the computer-readable medium 102 can include practically any applicable type of network, such as the Internet, an intranet, or an infrastructure network. The term "Internet" as used herein refers to a network of networks that uses certain protocols, such as the TCP/IP protocol, and possibly other protocols such as the hypertext transfer protocol (HTTP) for hypertext markup language (HTML) documents that make up the World Wide Web (the web). Content is often provided by content servers, which are referred to as being "on" the Internet or "online." A web server, which is one type of content server, is typically at least one computer system which operates as a server computer system and is configured to operate with the protocols of the World Wide Web and is coupled to the Internet. The physical connections of the Internet and the protocols and communication procedures of the Internet and the web are well known to those of skill in the relevant art.

[0019] For illustrative purposes, it is assumed the computer-readable medium 102 broadly includes, as understood from relevant context, anything from a minimalist coupling of the components, or a subset of the components, illustrated in the example of FIG. 1, to every component of the Internet and networks coupled to the Internet. In the example of FIG. 1, the computer-readable medium 102 can include a data path, such as a bus, in a computer. In such an implementation, one or more of the components illustrated in the example of FIG. 1 can be implemented on the same machine. [0020] In the example of FIG. 1, the diagram 100 includes an entity- specific content source or datastore 104. In some implementations, the entity- specific content datastore 104 can be implemented within or can operate in conjunction with an entity- specific content manager (not shown in FIG. 1). In one example, the entity-specific content source (or datastore) 104 and the entity- specific content manager can be implemented within or reside at one or more content servers, such as web servers. The entity- specific content datastore 104 can be configured to store, search for, create, read, access, update, modify, and delete, etc., entity- specific content (or other entity- specific data).

[0021] Entity- specific content can refer to data, information, or other content associated with a specific or particular entity. In one example, the entity can correspond to a person, a business, a company, a corporation, an organization, or any combination thereof. In some implementations, the entity can be associated with a phone number (or other contact information).

[0022] In some implementations, the entity- specific content datastore 104 can be configured to access, retrieve, and provide a particular entity- specific content, or a portion thereof, based on a unique identifier for the particular entity- specific content. In some cases, the unique identifier can be associated with the entity as well as with the particular entity- specific content (of the entity). In some cases, the unique identifier can be unique to the entity with respect to a given scope of identification, such as a specified location or region (e.g., a country, the world, etc.). For example, the unique identifier can be a phone number of the entity.

[0023] In one example, an entity can provide or upload a particular entity- specific content (or a portion thereof) to the entity- specific content datastore 104 to be stored. The entity- specific content is specific to, particular to, or associated with the entity who provided or uploaded the content. In this example, the entity possesses a particular phone number, which can be utilized as a unique identifier for identifying the particular entity- specific content stored at the entity- specific content datastore 104. Accordingly, given the particular phone number, the entity- specific content datastore 104 can locate, access, and/or retrieve the entity's particular entity- specific content identified based on the entity's phone number. The unique identifier can enable the entity- specific content datastore 104 to distinguish the particular entity- specific content from other entity- specific content associated with other entities.

[0024] Moreover, a datastore, as used in this paper, can be implemented, for example, as software embodied in a physical computer-readable medium on a general- or specific -purpose machine, in firmware, in hardware, in a combination thereof, or in an applicable known or convenient device or system. Datastores in this paper are intended to include any organization of data, including tables, comma-separated values (CSV) files, traditional databases (e.g., SQL), or other applicable known or convenient organizational formats. Datastore-associated components, such as database interfaces, can be considered "part of a datastore, part of some other system component, or a combination thereof, though the physical location and other characteristics of datastore-associated components is not critical for an understanding of the techniques described in this paper.

[0025] Datastores can include data structures. As used in this paper, a data structure is associated with a particular way of storing and organizing data in a computer so that it can be used efficiently within a given context. Data structures are generally based on the ability of a computer to fetch and store data at any place in its memory, specified by an address, a bit string that can be itself stored in memory and manipulated by the program. Thus some data structures are based on computing the addresses of data items with arithmetic operations, while other data structures are based on storing addresses of data items within the structure itself. Many data structures use both principles, sometimes combined in non-trivial ways. The implementation of a data structure usually entails writing a set of procedures that create and manipulate instances of that structure.

[0026] In an example of a system where a datastore is implemented as a database, a database management system (DBMS) can be used to manage the datastore. In such a case, the DBMS may be thought of as part of the datastore or as part of another applicable depicted component, or as a separate functional unit (not shown). A DBMS is typically implemented as an engine that controls organization, storage, management, and retrieval of data in a database. DBMSs frequently provide the ability to query, backup and replicate, enforce rules, provide security, do computation, perform change and access logging, and automate optimization. Examples of DBMSs include Alpha Five, DataEase, Oracle database, IBM DB2, Adaptive Server Enterprise, FileMaker, Firebird, Ingres, Informix, Mark Logic, Microsoft Access, InterSystems Cache, Microsoft SQL Server, Microsoft Visual FoxPro, MonetDB, MySQL, PostgreSQL, Progress, SQLite, Teradata, CSQL, OpenLink Virtuoso, Daffodil DB, and OpenOffice.org Base, to name several.

[0027] Database servers can store databases, as well as the DBMS and related engines. Any of the datastores described in this paper can presumably be implemented as database servers. It should be noted that there are two logical views of data in a database, the logical (external) view and the physical (internal) view. In this paper, the logical view is generally assumed to be data found in a report, while the physical view is the data stored in a physical storage medium and available to a specifically programmed processor. With most DBMS implementations, there is one physical view and an almost unlimited number of logical views for the same data.

[0028] A DBMS typically includes a modeling language, data structure, database query language, and transaction mechanism. The modeling language is used to define the schema of each database in the DBMS, according to the database model, which may include a hierarchical model, network model, relational model, object model, or some other applicable known or convenient organization. An optimal structure may vary depending upon application requirements (e.g., speed, reliability, maintainability, scalability, and cost). One of the more common models in use today is the ad hoc model embedded in SQL. Data structures can include fields, records, files, objects, and any other applicable known or convenient structures for storing data. A database query language can enable users to query databases, and can include report writers and security mechanisms to prevent unauthorized access. A database transaction mechanism ideally ensures data integrity, even during concurrent user accesses, with fault tolerance. DBMSs can also include a metadata repository; metadata is data that describes other data.

[0029] Furthermore, in the example of FIG. 1, at least a portion of the entity- specific content datastore 104 or at least one instance of the entity- specific content datastore 104 can be implemented or locally exist at the mobile device 106, in some implementations. For example, one or more datastores of the mobile device 106 can locally store the at least the portion or instance of the entity- specific content datastore 104.

[0030] In general, the mobile device 106 can be a computing device or system that is mobile or portable. An example of the mobile device 106 can include, but is not limited to, a smartphone, a tablet computer, or a wearable device (e.g., smart watch, smart glasses, etc.).

[0031] A computer system (i.e., computer device, computing system, computing device, computer, etc.), as used in this paper, is intended to be construed broadly. In general, a computer system will include a processor, memory, non-volatile storage, and an interface. A typical computer system will usually include at least a processor, memory, and a device (e.g., a bus) coupling the memory to the processor. The processor can be, for example, a general- purpose central processing unit (CPU), such as a microprocessor, or a special-purpose processor, such as a microcontroller.

[0032] The memory can include, by way of example but not limitation, random access memory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). The memory can be local, remote, or distributed. As used in this paper, the term "computer-readable storage medium" is intended to include only physical media, such as memory. As used in this paper, a computer-readable medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are nonstatutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.

[0033] The bus can also couple the processor to the non-volatile storage. The nonvolatile storage is often a magnetic floppy or hard disk, a magnetic-optical disk, an optical disk, a readonly memory (ROM), such as a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory during execution of software on the computer system. The non-volatile storage can be local, remote, or distributed. The non-volatile storage is optional because systems can be created with all applicable data available in memory.

[0034] Software is typically stored in the non-volatile storage. Indeed, for large programs, it may not even be possible to store the entire program in the memory. Nevertheless, it should be understood that for software to run, if necessary, it is moved to a computer-readable location appropriate for processing, and for illustrative purposes, that location is referred to as the memory in this paper. Even when software is moved to the memory for execution, the processor will typically make use of hardware registers to store values associated with the software, and local cache that, ideally, serves to speed up execution. As used herein, a software program is assumed to be stored at any known or convenient location (from non-volatile storage to hardware registers) when the software program is referred to as "implemented in a computer-readable storage medium." A processor is considered to be "configured to execute a program" when at least one value associated with the program is stored in a register readable by the processor.

[0035] In one example of operation, the computer system can be controlled by operating system software, which is a software program that includes a file management system, such as a disk operating system. One example of operating system software with associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Washington, and their associated file management systems. Another example of operating system software with its associated file management system software is the Linux operating system and its associated file management system. The file management system is typically stored in the non-volatile storage and causes the processor to execute the various acts required by the operating system to input and output data and to store data in the memory, including storing files on the non- volatile storage.

[0036] The bus can also couple the processor to the interface. The interface can include one or more input and/or output (I/O) devices. The I/O devices can include, by way of example but not limitation, a keyboard, a mouse or other pointing device, disk drives, printers, a scanner, and other I/O devices, including a display device. The display device can include, by way of example but not limitation, a cathode ray tube (CRT), liquid crystal display (LCD), or some other applicable known or convenient display device. The interface can include one or more of a modem or network interface. It will be appreciated that a modem or network interface can be considered to be part of the computer system. The interface can include an analog modem, isdn modem, cable modem, token ring interface, satellite transmission interface (e.g. "direct PC"), or other interfaces for coupling a computer system to other computer systems. Interfaces enable computer systems and other devices to be coupled together in a network. In some implementations, the network interface can provide for communication between the computer system and any of a wide range of networks, such as an Ethernet (e.g., IEEE 802.3) network, a wireless network (e.g., IEEE 802.11, IEEE 802.16, Wi-Fi, WiMax, Bluetooth, radio-frequency communications, near field communications), and/or a backplane, etc. In some cases, the network interface can be configured to enable the computer system to operate in the capacity of a server machine or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

[0037] In the example of FIG. 1, the mobile device 106 can include the entity- specific content display 112 and the communications interface 114. In some implementations, the entity- specific content display 112 can be a display element, such as a display device, display screen, or touch screen, configured to display various content, including entity- specific content (or related information).

[0038] In some implementations, entity- specific content can be presented in ways other than being displayed. In one example, entity- specific content can be audio content or can be converted into audio content. In this example, the mobile device 106 can comprise an entity- specific content speaker or audio port configured to play or output the entity- specific audio content.

[0039] In some implementations, the communications interface 114 can be configured to process, manage, and/or handle various tasks associated with mobile device 106 communications. The communications interface 114 can enable the mobile device 106 to transmit data to and receive data from the computing-readable medium 102. In one example, the communications interface 114 can facilitate performing one or more real-time voice communications by the mobile device 106, such as by making or receiving phone calls via a telephone network or cellular network. In another example, the communications interface 114 can facilitate sharing data via the Internet by the mobile device 106, such as when the mobile device 106 shares data via a Wi-Fi network or the cellular network.

[0040] In some implementations, the mobile device 106 can also include the entity- specific concurrent communications management engine 108. In some implementations, the entity- specific concurrent communications management engine 108 can be included in one or more computing systems (e.g., one or more servers) that are remote or separate from the mobile device 106, as shown in the example of FIG. 1. The entity- specific concurrent communications management engine 108 can be configured to manage, process, and/or otherwise handle various tasks related to performing entity- specific concurrent communications. In a specific implementation, the entity- specific concurrent communications management engine 108 can enable the mobile device 106 to acquire and display entity- specific content associated with a particular entity with whom a user of the mobile device 106 is concurrently engaging in communication or attempting to engage in communication.

[0041] In one example, the particular entity can be a user of the entity- associated communications device 110, which can be a computing device or system capable of communicating with the mobile device 106 via real-time communications. In this example, the entity- associated communications device 110 can be a land- line telephone or a smartphone used by the particular entity. The mobile device 106 can establish or attempt to establish a communicative connection with the entity- associated communications device 110 via the computer-readable medium 102, thereby enabling a user of the mobile device 106 to engage in or attempt to engage in a real-time voice communication, such as a phone call, with the particular entity who uses the entity- associated communications device 110. The entity- specific concurrent communications management engine 108 can be configured to detect the initiation of (or the attempt to initiate) the real-time voice communication and to determine whether or not the particular entity is associated with any entity- specific content. The entity- specific concurrent communications management engine 108 can communicate with the entity- specific content datastore 104 (e.g., online or local) in attempt to identify, using the particular entity's phone number, any entity- specific content associated with the particular entity. If the entity- specific content datastore 104 finds and provides entity- specific content associated with the particular entity identified using the phone number of the particular entity, then the entity- specific concurrent communications management engine 108 can display (i.e., cause to be displayed, enable to be displayed, etc.), via the entity- specific content display 112, at least a portion of the identified entity- specific content during the real-time communication with the particular entity and/or during the attempt to initiate the real-time communication (e.g., during the perceived ringing phase of the phone call).

[0042] In some implementations, the entity- specific content can be content created by and/or provided by the entity. In one example, the entity- specific content can include, but is not limited to, a document, an image, a video, an audio, or any combination thereof. In another example, the entity- specific content can serve as a web page, an online information source, a flyer, a coupon, an advertisement, etc., associated with the entity. In some implementations, the entity- specific content can be broadly associated with the entity. For example, the entity- specific content can include advertising, marketing, or promotional material indirectly associated with or remotely related to the entity.

[0043] As used in this paper, an engine includes one or more processors or a portion thereof. A portion of one or more processors can include some portion of hardware less than all of the hardware comprising any given one or more processors, such as a subset of registers, the portion of the processor dedicated to one or more threads of a multi-threaded processor, a time slice during which the processor is wholly or partially dedicated to carrying out part of the engine's functionality, or the like. As such, a first engine and a second engine can have one or more dedicated processors or a first engine and a second engine can share one or more processors with one another or other engines. Depending upon implementation- specific or other considerations, an engine can be centralized or its functionality distributed. An engine can include hardware, firmware, or software embodied in a computer-readable medium for execution by the processor. The processor transforms data into new data using implemented data structures and methods, such as is described with reference to the FIGS, in this paper.

[0044] The engines described in this paper, or the engines through which the systems and devices described in this paper can be implemented, can be cloud-based engines. As used in this paper, a cloud-based engine is an engine that can run applications and/or functionalities using a cloud-based computing system. All or portions of the applications and/or functionalities can be distributed across multiple computing devices, and need not be restricted to only one computing device. In some embodiments, the cloud-based engines can execute functionalities and/or modules that end users access through a web browser or container application without having the functionalities and/or modules installed locally on the end- users' computing devices.

[0045] FIG. 2 depicts a diagram 200 of an example of a system configured to facilitate displaying information in association with communication. As shown in the example of FIG. 2, the diagram 200 includes an entity- specific content Search, Create, Read, Update, Delete (SCRUD) engine 202, a communication detection engine 204, an entity- specific content identification engine 206, an entity- specific content acquisition engine 208, an entity- specific content display engine 210, and optionally an entity- specific content relevance engine 212. In some implementations, the components or engines shown in the diagram 200 can be implemented on a mobile device. In some implementations, an entity- specific concurrent communications management engine can include or operate in conjunction with one or more components or engines shown in the diagram 200. In some implementations, at least a portion of the entity- specific concurrent communications management engine can be included in the example of the system depicted in the diagram 200.

[0046] In the example of FIG. 2, the entity- specific content Search, Create, Read, Update, Delete (SCRUD) engine 202 can be configured to store, search for, write, create, read, access, update, modify, delete, remove, process, and/or handle, etc., various entity- specific content. The entity- specific content SCRUD engine 202 can operate in conjunction with various components or engines in order to perform tasks related to processing or handling entity- specific content as needed for displaying information in association with communication. For example, if at least a portion or instance of an entity- specific content source (e.g., datastore) resides within the mobile device, then the entity- specific content SCRUD engine 202 can create, access, retrieve, provide, modify, and/or delete, etc., various entity- specific content on behalf of the mobile device as appropriate.

[0047] In some implementations, the entity- specific content identification engine 204 can be configured to determine that a phone number of an entity identifies entity- specific content associated with the entity. In some cases, the entity- specific content identification engine 204 can communicate with an entity- specific content service, server, source, datastore, and/or system to determine that the entity is associated with entity- specific content and that the entity- specific content is identifiable based on the phone number of the entity. In one example, this determination can be performed when the communication detection engine 206 determines that a real-time voice communication is being attempted, initiated, and/or occurring. In another example, this determination that the entity- specific content is identifiable based on the entity's phone number can be performed when the entity and/or the phone number is added in a contact entry to a contact list or an address book of the mobile device. [0048] In the example of FIG. 2, the communication detection engine 206 can be configured to detect at least one of an incoming real-time voice communication associated with the phone number or an outgoing real-time voice communication associated with the phone number. For example, the communication detection engine 206 can detect an initiation of a real-time voice communication, such as an incoming phone call or (an attempt to make) an outgoing phone call. In a specific implementation, the communication detection engine 206 can further detect when the real-time voice communication has ended, such as when the mobile device hangs up the phone call.

[0049] In some implementations, the entity- specific content acquisition engine 208 can be configured to acquire, from an entity- specific content source such as an entity- specific content datastore, the entity-specific content identified based on the phone number. In some instances, the entity- specific content acquisition engine 208 can pull or fetch the entity- specific content, such as during an initiation or occurrence of the real-time voice communication. In some cases, the entity- specific content acquisition engine 208 can pull or fetch the entity- specific content on a periodic basis, such as checking for updates once every 15 minutes, once every hour, once per day, etc. In some instances, the entity- specific content acquisition engine 208 can acquire the entity- specific content when the entity- specific content source pushes the content or indicates that the content is available, such as when the entity has provided or updated the entity- specific content.

[0050] In some implementations, a user of the mobile device can configure, select, or customize for which entities (e.g., contact entries) respective entity- specific content is to be acquired. In some instances, the user can configure or specify when and/or how often entity- specific content is to be acquired for each entity (if at all). Numerous other configurations, customizations, and/or variations are possible. [0051] In the example of FIG. 2, the entity- specific content display engine 210 can be configured to display (i.e., cause to be displayed, enable to be displayed, etc.) at least a portion of the entity- specific content during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication. In one example, the entity- specific content display engine 210 can display or present the entity- specific content and/or related information (e.g., information included in the entity- specific content) when the communication detection engine 206 determines that an incoming or outgoing real-time voice communication is being attempted, initiated, and/or occurring. In another example, the entity- specific content display engine 210 can cease to display or present the entity- specific content and/or related information when the communication detection engine 206 determines that the real-time voice communication has ended.

[0052] Furthermore, in the example of FIG. 2, there can optionally be an entity- specific content relevance engine 212. In some implementations, the entity- specific content relevance engine 212 can be configured to determine whether or not other content is sufficiently relevant to be displayed or presented in addition to or instead of the entity- specific content.

[0053] FIG. 3A depicts a diagram 300 of an example of a mobile device 302 configured to facilitate displaying information in association with communication. In the example of FIG. 3A, the diagram 300 includes the mobile device 302, which can include a user interface 304 such as a display device or display element.

[0054] In the example of FIG. 3A, the mobile device 302 performs an outgoing real-time communication with an entity "Harry's Diner", who has the phone number (555) 555-5555. The user interface 304 of the mobile device 302 can display information 306 about the outgoing communication with the entity. In some implementations, the user interface 304 can also provide an interactive element 308 for additional options (e.g., to show the keypad, to mute, to use speaker-phone, etc.).

[0055] Moreover, the user interface 304 can be configured to display at least of a portion of entity- specific content (and/or related information) 310 associated with the entity, during the communication with the entity. In the example of FIG. 3A, during or before the initiation of the phone call with the entity Harry's Diner at phone number (555) 555-5555, the mobile device 102 can acquire entity- specific content associated with the entity Harry's Diner, the entity- specific content being identified based on the phone number (555) 555-5555. In some implementations, the entity- specific content can include a document (e.g., text document), an image, an animation, a video, an audio, or any combination thereof. In this example, the entity- specific content for Harry's Diner can include a flyer 310 listing today's specials. The user interface 304 of the mobile device 302 can display the entity- specific content (e.g., the flyer) 310 during the call. It is contemplated that a similar process can occur for an incoming call, as shown in FIG. 3B. In the example of FIG. 3B, if Harry's Diner is calling the mobile device 302, then the mobile device 302 can display the entity- specific content/flyer 310 when the mobile device 302 is ringing and/or during the received call.

[0056] FIG. 4 depicts a flowchart 400 of an example of a method for facilitating a display of information in association with communication. The flowchart 400 starts at module 402 with acquiring a phone number of an entity. In one example, the phone number of the entity can be acquired when the phone number is entered or inputted, into a contact list or an address book, as contact information for the entity. In another example, the phone number of the entity can be acquired when a phone call or other communication is being made to and/or from the entity (i.e., to and/or from a device or system associated with the entity). At module 404, it can be determined, by a mobile device (and/or by one or more other computing systems), that the phone number of the entity identifies entity- specific content associated with the entity. For instance, the mobile device can make this determination by communicating with an entity- specific content source (e.g., datastore), which can be located remotely and/or locally.

[0057] In the example of FIG. 4, if the phone number of the entity identifies entity- specific content associated with the entity, the flowchart 400 continues to module 406 with determining, by the mobile device (and/or by one or more other computing systems), whether or not an incoming real-time voice communication associated with the phone number has been detected. If not, the flowchart 400 continues to module 408 with determining whether or not an outgoing real-time voice communication associated with the phone number has been detected. In some implementations, module 406 and module 408 can be switched or interchanged. In one example, detecting the incoming real-time voice communication and/or the outgoing real-time voice communication can include detecting at least one of an acceptance of an incoming phone call, an attempt to accept the incoming phone call, an initiation of an outgoing phone call, an attempt to initiate the outgoing phone call, or an occurrence or duration of a phone call.

[0058] Continuing with the example of FIG. 4, if at least one of the incoming real-time voice communication or the outgoing real-time voice communication is detected, then the flowchart 400 continues to module 410 with acquiring, by the mobile device (and/or by one or more other computing systems) from an entity- specific content source (e.g., datastore), the entity- specific content identified based on the phone number. As discussed, the acquisition of the entity- specific content source can be performed as a pull/fetch by the mobile device or as a push by the entity- specific content source to the mobile device.

[0059] In the example of FIG. 4, the flowchart 400 continues to module 412 with displaying, by the mobile device (and/or by one or more other computing systems), at least a portion of the entity- specific content during at least one of the incoming real-time voice communication or the outgoing real-time voice communication. Displaying the at least the portion of the entity- specific content can include displaying at least a portion of information included in or related to the entity- specific content. Further, in some implementations, the entity- specific content can be presented in a way other than being displayed, such as by being presented audibly in place of perceived rings during an outgoing call.

[0060] It should be appreciated that there can be additional, fewer, or alternative steps performed in similar or alternative orders, or in parallel, within the scope of the various embodiments unless otherwise stated. For example, in some implementations, acquiring the entity- specific content in module 410 can occur prior to, during, and/or subsequent to detecting the at least one of the incoming communication or the outgoing communication (in module 406 and/or module 408).

[0061] Moreover, it is contemplated that in some implementations the disclosed technology can be implemented (individually, collectively, partially, wholly, or in any combination) as an application or app for the mobile device. In a specification implementation, the disclosed technology can be utilized as a default "Phone" app.

[0062] These and other examples provided in this paper are intended to illustrate but not necessarily to limit the described embodiments and implementations. As used herein, the terms "embodiment" and "implementation" mean an embodiment or implementation that serves to illustrate by way of example but not limitation. The techniques described in the preceding text and figures can be mixed and matched as circumstances demand to produce alternative embodiments or implementations.

[0063] It is contemplated that there can be many variations or other possibilities. In some implementations, a user of the mobile device (and/or one or more other computing systems) can engage in real-time voice communication, such as by completing a dial sequence and activating a "call" option to make an outgoing phone call and/or by accepting an incoming phone call. When the user engages in the real-time voice communication, the mobile device (and/or an application running on the mobile device, etc.) can detect a phone number involved in the real-time voice communication. Using one or more network connections of the mobile device, the mobile device can transmit the phone number to an entity- specific concurrent communications management engine operable with the mobile device. The entity- specific concurrent communications management engine can, for instance, be implemented at the mobile device and/or implemented as an online service/platform via one or more computing systems remote from the mobile device. The entity- specific concurrent communications management engine can acquire, from an entity- specific content source, entity- specific content identified based on the phone number and can return the entity- specific content to the mobile device. As such, the mobile device can acquire the entity- specific content from the entity- specific concurrent communications management engine, which can have acquired the entity- specific content from the entity- specific content source. Subsequently, at least a portion of the entity- specific content can be displayed at the mobile device during the real-time voice communication.

[0064] In some implementations, the real-time voice communication (e.g., at least one of the incoming real-time voice communication or the outgoing real-time voice communication) can utilize a network connection and the entity- specific content can be acquired via the same network connection. For instance, regarding Global System for Mobile Communications (GSM) mobile devices and networks, a GSM mobile device can engage in the real-time voice communication and acquire the entity- specific content via a single network connection (e.g., a GSM cellular network connection).

[0065] Moreover, in some implementations, the real-time voice communication (e.g., at least one of the incoming real-time voice communication or the outgoing real-time voice communication) can utilize a network connection. The entity- specific content can be acquired via the network connection, but not while the network connection is being utilized by the realtime voice communication. Accordingly, the real-time voice communication can be at least temporarily ceased from utilizing the network connection while the entity- specific content is being acquired via the network connection. The real-time voice communication can then be enabled to resume utilizing the network connection when the entity- specific content has been acquired via the network connection. In one example, a non-GSM mobile device without access to a Wi-Fi network connection can utilize a cellular network connection to engage in the real-time voice communication and to acquire the entity- specific content. In this example, the non-GSM mobile device can pause or hold the real-time voice communication via the cellular network connection, acquire (i.e., retrieve, receive, etc.) the entity- specific content via the cellular network connection while the real-time voice communication is paused or held, and resume the real-time voice communication via the cellular network connection when the entity- specific content has been acquired.

[0066] Additionally, in some implementations, the real-time voice communication (e.g., at least one of the incoming real-time voice communication or the outgoing real-time voice communication) can utilize a first network connection and the entity- specific content can be acquired via a second network connection. The entity- specific content can be acquired at least partially within a duration of when the real-time voice communication utilizes the first network connection. For example, a non-GSM mobile device with access to a Wi-Fi network connection can utilize a cellular network connection to engage in the real-time voice communication and can, at the same time, utilize the Wi-Fi network connection to acquire the entity- specific content.

[0067] Furthermore, in some implementations, at least a portion of the entity- specific content can include a link to related data. The real-time voice communication can be at least temporarily ceased when the link to the related data is accessed. The real-time voice communication can be resumed subsequent to the link to the related data being accessed. For instance, at least the portion of the entity- specific content to be displayed can include one or more active links, such as uniform resource locators (URL's), to a web resource, related content, and/or other data. In this example, when the one or more links are selected, activated, or accessed by a user, a connection to the web resource, related content, and/or other data can be established and the real-time voice communication can be at least temporarily ceased. When the user so desires, signals, or instructs, the real-time voice communication can then be resumed.

[0068] FIG. 5 depicts a diagram 500 of an example of a mobile device 502 configured to facilitate displaying information in association with communication. In the example of FIG. 5, the diagram 500 includes the mobile device 502, which can include a user interface 504 such as a display device or display element.

[0069] In some implementations, an absence of a capability for at least the portion of the entity- specific content to be displayed during the real-time voice communication can be detected, such as by a capability detection engine. The capability detection engine can, for example, be implemented with, included in, and/or operable with the entity- specific concurrent communications management engine. In some cases, a link (e.g., element 506 in the example of FIG. 5) can be provided, such as by an option providing engine, for displaying at least the portion of the entity-specific content during the real-time voice communication. In some cases, access to the capability can be provided, such as by the option providing engine via element 508. The option providing engine can, for instance, be implemented with, included in, and/or operable with the entity- specific concurrent communications management engine. In one example, if a user (i.e., the user's device) has not implemented an application and/or service configured to facilitate displaying information in association with communication, then at least the portion of the entity- specific content can be provided for display, during the real-time voice communication, via a link (e.g., element 506). In some cases, the link can be provided via interactive media (e.g., a clickable image/video), an email, and/or a text message (e.g., Short Message Service (SMS)), etc. In another example, if the user has not implemented the application and/or service configured to facilitate displaying information in association with communication, then a link (e.g., element 508) to download and implement the application and/or service can be provided to the user. When the user has implemented the application and/or service, at least the portion of the entity- specific content can be displayed. In a further example, the user can be provided, such as by the option providing engine, with an option (e.g., element 510) to opt-out or unsubscribe to various aspects of the disclosed technology. As discussed above, it should be understood that there can be many variations or other possibilities.

[0070] The detailed description discloses examples and techniques, but it will be appreciated by those skilled in the relevant art that modifications, permutations, and equivalents thereof are within the scope of the teachings. It is therefore intended that the following appended claims include all such modifications, permutations, and equivalents. While certain aspects of the disclosed technology are presented below in certain claim forms, the applicant contemplates the various aspects of the disclosed technology in any number of claim forms. For example, while only one aspect of the disclosed technology is recited as a means-plus-function claim under 35 U.S.C. sec. 212, sixth paragraph, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §212, ¾6 will begin with the words "means for", but use of the term "for" in any other context is not intended to invoke treatment under 35 U.S.C. §212, ¾6.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosed technology.

Claims

CLAIMS We claim:
1. A computer-implemented method comprising:
determining, by a computing system, that a phone number of an entity identifies entity- specific content associated with the entity;
detecting, by the computing system, at least one of an incoming real-time voice communication associated with the phone number or an outgoing real-time voice communication associated with the phone number;
acquiring, by the computing system, from an entity- specific content source the entity- specific content identified based on the phone number; and
enabling, by the computing system, at least a portion of the entity- specific content to be displayed during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication.
2. The computer- implemented method of claim 1, wherein the entity- specific content is acquired during the at least one of the incoming real-time voice communication associated with the phone number or the outgoing real-time voice communication associated with the phone number.
3. The computer- implemented method of claim 1, wherein the entity- specific content is acquired prior to the at least one of the incoming real-time voice communication associated with the phone number or the outgoing real-time voice communication associated with the phone number.
4. The computer- implemented method of claim 1, further comprising:
acquiring from the entity- specific content source additional entity- specific content identified based on the phone number; and
enabling at least a portion of the additional entity- specific content to be displayed after the at least one of the incoming real-time voice communication or the outgoing real-time voice communication.
5. The computer- implemented method of claim 1, wherein the entity- specific content is acquired based on pulling or fetching the entity- specific content from the entity- specific content source.
6. The computer- implemented method of claim 1, wherein the entity- specific content is acquired based on the entity- specific content being pushed from the entity- specific content source.
7. The computer-implemented method of claim 1, wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication utilizes a first network connection, wherein the entity- specific content is acquired via a second network connection, and wherein the entity- specific content is acquired at least partially within a duration of when the at least one of the incoming real-time voice communication or the outgoing real-time voice communication utilizes the first network connection.
8. The computer-implemented method of claim 1, wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication utilizes a network connection, wherein the entity- specific content is acquired via the network connection, wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication is at least temporarily ceased from utilizing the network connection while the entity- specific content is being acquired via the network connection, and wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication is enabled to resume utilizing the network connection when the entity- specific content has been acquired via the network connection.
9. The computer-implemented method of claim 1, wherein the at least the portion of the entity- specific content includes a link to related data, wherein the at least one of the at least one of the incoming real-time voice communication or the outgoing real-time voice communication is at least temporarily ceased when the link to the related data is accessed, and wherein the at least one of the incoming real-time voice communication or the outgoing realtime voice communication is resumed subsequent to the link to the related data being accessed.
10. The computer- implemented method of claim 1, further comprising:
detecting an absence of a capability for at least the portion of the entity- specific content to be displayed during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication; and
providing at least one of: 1) a link for displaying at least the portion of the entity- specific content during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication or 2) access to the capability.
11. A system comprising:
an entity- specific content identification engine configured to determine that a phone number of an entity identifies entity- specific content associated with the entity; a communication detection engine configured to detect at least one of an incoming realtime voice communication associated with the phone number or an outgoing real-time voice communication associated with the phone number;
an entity- specific content acquisition engine configured to acquire from an entity- specific content source the entity- specific content identified based on the phone number; and an entity- specific content display engine configured to enable at least a portion of the entity- specific content to be displayed during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication.
12. The system of claim 1, wherein the entity- specific content is acquired during the at least one of the incoming real-time voice communication associated with the phone number or the outgoing real-time voice communication associated with the phone number.
13. The system of claim 1, wherein the entity- specific content is acquired prior to the at least one of the incoming real-time voice communication associated with the phone number or the outgoing real-time voice communication associated with the phone number.
14. The system of claim 1, wherein the entity- specific content acquisition engine is further configured to acquire from the entity- specific content source additional entity- specific content identified based on the phone number, and wherein the entity- specific content display engine is further configured to enable at least a portion of the additional entity- specific content to be displayed after the at least one of the incoming real-time voice communication or the outgoing real-time voice communication.
15. The system of claim 1, wherein the entity- specific content is acquired based on pulling or fetching the entity- specific content from the entity- specific content source.
16. The system of claim 1, wherein the entity- specific content is acquired based on the entity- specific content being pushed from the entity- specific content source.
17. The system of claim 1, wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication utilizes a first network connection, wherein the entity- specific content is acquired via a second network connection, and wherein the entity- specific content is acquired at least partially within a duration of when the at least one of the incoming real-time voice communication or the outgoing real-time voice communication utilizes the first network connection.
18. The system of claim 1, wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication utilizes a network connection, wherein the entity- specific content is acquired via the network connection, wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication is at least temporarily ceased from utilizing the network connection while the entity- specific content is being acquired via the network connection, and wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication is enabled to resume utilizing the network connection when the entity- specific content has been acquired via the network connection.
19. The system of claim 1, wherein the at least the portion of the entity- specific content includes a link to related data, wherein the at least one of the at least one of the incoming real-time voice communication or the outgoing real-time voice communication is at least temporarily ceased when the link to the related data is accessed, and wherein the at least one of the incoming real-time voice communication or the outgoing real-time voice communication is resumed subsequent to the link to the related data being accessed.
20. The system of claim 1, further comprising:
a capability detection engine configured to detect an absence of a capability for at least the portion of the entity- specific content to be displayed during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication; and
an option providing engine configured to provide at least one of: 1) a link for displaying at least the portion of the entity- specific content during the at least one of the incoming real-time voice communication or the outgoing real-time voice communication or 2) access to the capability.
21. A system comprising:
means for determining that a phone number of an entity identifies entity- specific content associated with the entity;
means for detecting at least one of an incoming real-time voice communication associated with the phone number or an outgoing real-time voice communication associated with the phone number;
means for acquiring from an entity- specific content source the entity- specific content identified based on the phone number; and
means for enabling at least a portion of the entity- specific content to be displayed during the at least one of the incoming real-time voice communication or the outgoing realtime voice communication.
PCT/US2015/030025 2014-05-08 2015-05-08 Displaying information in association with communication WO2015172106A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201461990559P true 2014-05-08 2014-05-08
US61/990,559 2014-05-08

Publications (2)

Publication Number Publication Date
WO2015172106A1 true WO2015172106A1 (en) 2015-11-12
WO2015172106A8 WO2015172106A8 (en) 2016-02-11

Family

ID=54393075

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/030025 WO2015172106A1 (en) 2014-05-08 2015-05-08 Displaying information in association with communication

Country Status (1)

Country Link
WO (1) WO2015172106A1 (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4924496A (en) * 1988-05-12 1990-05-08 Romek Figa D/B/A Abraham & Sons Automatic incoming telephone call originating number and party display system
US20050131935A1 (en) * 2003-11-18 2005-06-16 O'leary Paul J. Sector content mining system using a modular knowledge base
US20060034266A1 (en) * 2004-08-04 2006-02-16 Harris John C System and method for providing content via IP video telephone network
US20080112553A1 (en) * 2006-11-10 2008-05-15 Yen-Fu Chen Method and system for verifying incoming telephone numbers
US20090325560A1 (en) * 2002-12-07 2009-12-31 Pantech&Curitel Communications, Inc. System and mobile terminal for displaying caller information and method thereof
US20120102104A1 (en) * 2010-10-21 2012-04-26 Vinay Kakade Matching items of user-generated content to entities
US20120142323A1 (en) * 2009-08-25 2012-06-07 Nec Corporation Caller information displaying method, cellular phone, and non-transitory computer readable medium storing program
US20130086697A1 (en) * 2011-10-03 2013-04-04 Raymond P. Kasbarian Systems and methods for pairing identification data to a network-based service

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4924496A (en) * 1988-05-12 1990-05-08 Romek Figa D/B/A Abraham & Sons Automatic incoming telephone call originating number and party display system
US20090325560A1 (en) * 2002-12-07 2009-12-31 Pantech&Curitel Communications, Inc. System and mobile terminal for displaying caller information and method thereof
US20050131935A1 (en) * 2003-11-18 2005-06-16 O'leary Paul J. Sector content mining system using a modular knowledge base
US20060034266A1 (en) * 2004-08-04 2006-02-16 Harris John C System and method for providing content via IP video telephone network
US20080112553A1 (en) * 2006-11-10 2008-05-15 Yen-Fu Chen Method and system for verifying incoming telephone numbers
US20120142323A1 (en) * 2009-08-25 2012-06-07 Nec Corporation Caller information displaying method, cellular phone, and non-transitory computer readable medium storing program
US20120102104A1 (en) * 2010-10-21 2012-04-26 Vinay Kakade Matching items of user-generated content to entities
US20130086697A1 (en) * 2011-10-03 2013-04-04 Raymond P. Kasbarian Systems and methods for pairing identification data to a network-based service

Also Published As

Publication number Publication date
WO2015172106A8 (en) 2016-02-11

Similar Documents

Publication Publication Date Title
US9894049B2 (en) Network aggregator
US8756206B2 (en) Updating an inverted index in a real time fashion
US8255494B1 (en) Installable web applications
KR101031929B1 (en) Integration architecture for non-integrated tools
US8073810B2 (en) Shared view of customers across business support systems (BSS) and a service delivery platform (SDP)
US20080032739A1 (en) Management of digital media using portable wireless devices in a client-server network
US9189491B2 (en) Application recommendation using stored files
US9674225B2 (en) System and method for updating downloaded applications using managed container
US7404011B2 (en) System and method for accessing different types of back end data stores
US20170161698A1 (en) Automatic payment and deposit migration
CN101978366B (en) Application management within deployable object hierarchy
JP6188732B2 (en) Computer-implemented method, computer program product, and system for managing tenant-specific data sets in a multi-tenant environment
JP2019194868A (en) Converting tactical queries to continuous queries
US20110288946A1 (en) Method and System of Managing Digital Multimedia Content
US8768881B2 (en) RSS data-processing object
US8244700B2 (en) Rapid update of index metadata
US9298747B2 (en) Deployable, consistent, and extensible computing environment platform
JP6336110B2 (en) Infrastructure for synchronizing mobile devices with mobile cloud services
US8667031B2 (en) Reuse of shared metadata across applications via URL protocol
US20110264692A1 (en) System for searching property listings based on location
JP2014525092A (en) Methods for associating third-party content with online document signatures
US8788617B2 (en) Cookies stored in a cloud computing environment
CA2881804A1 (en) High performance real-time relational database system and methods for using same
WO2008106380A1 (en) Techniques for a web services data access layer
US9772990B2 (en) Personal assistant context building

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15789904

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15789904

Country of ref document: EP

Kind code of ref document: A1