H04L61/45

SYSTEMS AND METHODS FOR IDENTIFYING A SEQUENCE OF EVENTS AND PARTICIPANTS FOR RECORD OBJECTS
20220038548 · 2022-02-03 · ·

Methods, systems, and storage media for identifying a sequence of events and participants for record objects are disclosed. Exemplary implementations may: access record objects of a system of record; identify a subset of record objects associated with a group entity and having a first record object status; identify one or more electronic activities linked to the record objects; determine an event-participant pattern based on the electronic activities linked to the record object; identify electronic activities linked with a second record object; determine that a first event is performed by the a participant type and a second event is not yet performed by a second participant type; generate a content item identifying an action to trigger a performance of the second event; and transmit the content item to a device of a participant of at least one electronic activity linked with the second record object.

Method and apparatus for discovery of location context identifiers based on approximate location

As part of a localized positioning solution, a mobile device may transmit a request message to a server to obtain information about location contexts near the mobile device. In response, the server may, in some implementations, transmit a response message back to the mobile device that identifies a list of nearby LCIs and an area that encompasses these LCIs. The mobile device may store the returned LCI information and the returned area information in corresponding databases for later use. In some implementations, time limits may be placed on the returned area information after which the information is deemed stale.

System and method for permitting use of content using transfer rights

Apparatus, method, and media for permitting use of content. An exemplary method comprises associating a transfer right with content, the transfer right specifying that the content is permitted to be transferred from a first computing device to a second computing device, transferring the content from the first computing device to the second computing device in accordance with the transfer right, updating information associated with the transfer right based on the transfer of the content from the first computing device to the second computing device, and associating a usage right with the content, the usage right corresponding to a utilization of the content, wherein the first computing device includes at least a server mode of operation, and wherein the second computing device includes both a requester mode of operation and a server mode of operation.

Unified geograhic database and methods of creating, maintaining and using the same

A Universal Geographic Database (“UGD”) is provided that includes a real-time, automated registry/clearinghouse for the publication and retrieval of real-world locations and location-related information for businesses and other entities. By this registry, entities may publish their location and location-related information in a single place, and information services and their users can refer to this single place, via telecommunications devices, to obtain static, real-time location and location-based information about the registered locations. Each UGD record is keyed by a proprietary location address (PLA) based on the World Geographic Referencing System (WGRS). PLAs may be used as key reference and addressing terms, e.g., imbedded in digital documents, websites, GPS devices, or other information services to provide links to maps, directions, and information in the registry related to such locations. PLAs may also provide a concise, user-friendly notation for location naming and designating real-world locations and on all types of location-sensitive electronic devices.

Cloud provider, service, and tenant classification in cloud computing

A cloud provider supports cloud-based services accessible to tenants of the cloud provider over a network. In the cloud provider, classification information including a cloud-identifier to identify the cloud provider, service-identifiers each to identify a respective one of the services, and tenant-identifiers each to identify a respective one of the tenants is maintained. The classification information is distributed within the cloud provider, including to the services, and may also be distributed outside of the cloud provider, to enable a respective tenant to exchange IP packets with, and thereby access, a respective service based on the classification information, wherein each IP packet includes the cloud-identifier, the service-identifier of the respective service, and the tenant-identifier of the respective tenant.

Enabling resource semantics

Disclosed are methods and systems for Semantics Node functions which provide semantics support in machine-to-machine systems. In an example, a Semantic node may manage semantics resources capable of being discovered, retrieved, or validated by other devices. In another example, the Semantics Node may be discovered by other nodes, and semantics resources may be discovered with subscription mechanisms.

Private domain name registration

A service for protecting the privacy of domain name registrants while preserving the registrant's ability to directly change the registration information or transfer the registration. A whois record is created that reflects the registrant's actual identity but contains contact information that is entirely associated with a privacy service.

Phone alert for unauthorized email

The disclosed techniques enable selective forwarding and blocking of emails directed to an alias email address based on a whitelist, as well as text message alerts triggered by emails from unauthorized senders. More generally, the disclosed techniques enable an enterprise system to store contact emails for users (i.e., alias email addresses) while avoiding storing and managing personal email addresses for the user. For example, the enterprise system may forward personal email addresses to an aliasing server configured to generate alias email addresses based on the personal email addresses. The aliasing server may operate as a “middle man” that receives emails directed to the alias email addresses and that forwards the emails to the personal email addresses (when appropriate). The enterprise system may store and maintain the alias email addresses in lieu of the personal email addresses.

Methods, systems, and computer readable media for facilitating the resolving of endpoint hostnames in test environments with firewalls, network address translators (NATs), or clouds

Methods, systems, and computer readable media for facilitating the resolving of endpoint hostnames in test environments with firewalls, network address translators (NATs), or clouds is disclosed. According to one exemplary method, the method occurs at a registration server configured to operate in a public network. The method includes receiving, from a first endpoint, a packet including a payload containing a first address and a hostname associated with the first endpoint. The method also includes identifying a second address from a header of the packet. The method also includes initiating, using the second address, a connection to the first endpoint. The method also includes determining whether the connection is successful. The method further includes associating the hostname of the first endpoint with one of the first address and the second address based on results of the determination.

Address generation

Various example embodiments for supporting generation of addresses for network entities in communication systems are presented. Various example embodiments for supporting generation of addresses for network entities may be configured to support generation of a new address for a network entity based on an existing address of the network entity. Various example embodiments for supporting generation of addresses for network entities may be configured to support generation of a new address for a network entity based on manipulation of at least a portion of an existing address of the network entity. Various example embodiments for supporting generation of addresses for network entities may be configured to support generation of a transport layer address (e.g., an Internet Protocol (IP) address or the like) for a network entity based on a data link layer address (e.g., a Media Access Control (MAC) address or the like) of the network entity.