Patent application number | Description | Published |
20080209528 | Network identity management system and method - Users of Internet services (e.g., SKYPE messaging service, GOOGLETALK messaging service, AOL INSTANT MESSENGER messaging service, and MICROSOFT MESSENGER messaging service) that are initially identified using separate identifiers that may be associated with respective service providers (e.g., email addresses) can manage network identities using a single unified set of account information managed by a registry service. The registry authenticates the user's request(s) to bind a service provider identity to his or her personal registry user record by presenting a random challenge to the user which the registry must then receive back from the service provider corresponding to the identity being added. Later, the registry may authenticate itself to service providers using information received from a service provider application as the service provider application authenticates itself to the service provider. | 08-28-2008 |
20080229096 | Network identity management system and method - Users of Internet services (e.g., SKYPE messaging service, GOOGLETALK messaging service, AOL INSTANT MESSENGER messaging service, and MICROSOFT MESSENGER messaging service) that are initially identified using separate identifiers that may be associated with respective service providers (e.g., email addresses) can manage network identities using a single unified set of account information managed by a registry service. The registry authenticates the user's request(s) to bind a service provider identity to his or her personal registry user record. The registry internally associates the service provider identity to an internal unique identifier that is not exposed to subscribers. When a second user wishes to communicate with a first user, the second user provides any service provider identity that is believed to be associated with the first user to determine if the specified service provider identity appears to match the intended subscriber. If so, the second user may specify a nickname (unique to the second subscriber but not necessarily globally unique) to be associated internally within the registry with the internal unique identifier of the first subscriber as part of the second subscriber's user record. Later, even if the first subscriber has relinquished the service provider identity that was originally used to find the first subscriber, the second subscriber can still find the first subscriber by using the associate nickname without either subscriber ever knowing the internal unique identifier of the first subscriber. | 09-18-2008 |
20090006202 | System and method for providing identity-based services - Users of Internet communication services (e.g., SKYPE messaging service, GOOGLETALK messaging service, AOL INSTANT MESSENGER messaging service, and MICROSOFT MESSENGER messaging service, IP PBX systems, etc.) that are initially identified using separate identifiers (e.g., username@serviceprovider) can manage these network identities using a single, personal, unified set of account information managed by a registry service. The registry authenticates the user's request(s) to bind a service provider identity to his or her personal registry identity by presenting a random challenge to the user that the registry must then receive back from the service provider corresponding to the identity being added. Later, the registry may authenticate itself to service providers using information received from a service provider application as the service provider application authenticates itself to the service provider. | 01-01-2009 |
20120233659 | NETWORK IDENTITY MANAGEMENT SYSTEM AND METHOD - Users of Internet services (e.g., SKYPE messaging service, GOOGLETALK messaging service, AOL INSTANT MESSENGER messaging service, and MICROSOFT MESSENGER messaging service) that are initially identified using separate identifiers that may be associated with respective service providers (e.g., email addresses) can manage network identities using a single unified set of account information managed by a registry service. The registry authenticates the user's request(s) to bind a service provider identity to his or her personal registry user record by presenting a random challenge to the user which the registry must then receive back from the service provider corresponding to the identity being added. Later, the registry may authenticate itself to service providers using information received from a service provider application as the service provider application authenticates itself to the service provider. | 09-13-2012 |
20120290698 | NETWORK IDENTITY MANAGEMENT SYSTEM AND METHOD - Users of Internet messaging services that are initially identified using separate identifiers that may be associated with respective service providers (e.g., email addresses) can manage network identities using a single unified set of account information managed by a registry service. When a second user wishes to communicate with a first user, the second user provides any service provider identity that is believed to be associated with the first user to determine if the specified service provider identity appears to match the intended subscriber. If so, the second user may specify a nickname (unique to the second subscriber but not necessarily globally unique) to be associated internally within the registry with the internal unique identifier of the first subscriber as part of the second subscriber's user record. | 11-15-2012 |
20150066669 | NETWORK IDENTIFY MANAGEMENT SYSTEM AND METHOD - Users of Internet services (e.g., SKYPE messaging service, GOOGLETALK messaging service, AOL INSTANT MESSENGER messaging service, and MICROSOFT MESSENGER messaging service) that are initially identified using separate identifiers that may be associated with respective service providers (e.g., email addresses) can manage network identities using a single unified set of account information managed by a registry service. The registry authenticates the user's request(s) to bind a service provider identity to his or her personal registry user record by presenting a random challenge to the user which the registry must then receive back from the service provider corresponding to the identity being added. Later, the registry may authenticate itself to service providers using information received from a service provider application as the service provider application authenticates itself to the service provider. | 03-05-2015 |