The present invention includes methods and devices for passively tracking and selectively sharing user experiences with communication devices, including computers, web-enabled telephones, and PDAs. user rating or comments on their experiences can be captured. Particular aspects of the present invention are described in the claims, specification and drawings.
|
0. 36. A non-transitory computer-readable medium storing software for instructing a controller of a user device of a user to:
track automatically with a client-side application at least a portion of the user's internet usage to provide tracking data;
report the tracking data to a server;
enable the user to view a history of the tracking data;
enable the user to select one or more persons on one or more buddy lists of the user to authorize to receive the tracking data; and
enable the user to select one or more entries from the history of the tracking data to be shared such that the one or more entries from the history of the tracking data are capable of being shared with the one or more persons authorized to receive the tracking data.
0. 33. A method of operation of a tracking server to share internet browsing experiences, comprising the following computer-implemented steps:
receiving, by the tracking server, tracking data from a client-side application of a user to automatically track at least a portion of the user's internet usage;
categorizing at least a portion of the tracking data by content category;
receiving data identifying one or more persons on one or more buddy lists of the user authorized by the user to receive the tracking data;
receiving a user request to share one or more entries from a history of the tracking data; and
sending information indicating the one or more entries from the history of the tracking data to the one or more persons authorized to receive the tracking data.
0. 34. A method of operation of a client-side application of a user to share internet browsing experiences, including:
tracking automatically with the client-side application at least a portion of the user's internet usage to provide tracking data;
reporting the tracking data to a server so that at least a portion of the tracking data is categorized by content category;
enabling viewing of a history of the tracking data;
enabling selection of one or more persons on one or more buddy lists of the user to authorize to receive the tracking data; and
enabling selection of one or more entries from the history of the tracking data to be shared such that information indicating the one or more entries from the history of the tracking data are shared with the one or more persons authorized to receive the tracking data.
0. 35. A non-transitory computer-readable medium storing software for instructing a controller of a server to:
receive tracking data from a client-side application operating on a user device of a user, the tracking data comprising information indicating at least a portion of the user's internet usage automatically tracked by the client-side application;
categorize at least a portion of the tracking data by content category;
present to the user a history of the tracking data;
receive data identifying one or more persons and authorizing the one or more persons to receive the tracking data;
receive a user request to share one or more entries from the history of the tracking data; and
send the one or more entries from the history of the tracking data to the one or more persons authorized to receive the tracking data.
0. 1. A method of sharing computer user experiences, including:
communicating with a registration server to register a user, for automatic client-side collection of computer usage experiences for future sharing, wherein the computer usage experiences include one or more of browsing URLs or visiting a location with a location-aware device that records the visited location;
accessing one or more of the user's messaging buddy lists and selecting one or more buddies with whom to share the automatically collected computer usage experiences;
defining categories of computer usage experiences to be shared with particular selected buddies;
tracking automatically on the client-side at least a portion of the user's computer usage experiences and reporting the user's computer usage experiences to a tracking server to be published to the particular buddies in accordance with their defined categories of sharing.
0. 2. The method of
0. 3. The method of
0. 4. The method of
0. 5. The method of
0. 6. The method of
0. 7. The method of
0. 8. The method of
0. 9. The method of
0. 10. The method of
0. 11. The method of
0. 12. The method of
0. 13. The method of
0. 14. The method of
0. 15. The method of
0. 16. The method of
0. 17. The method of
0. 18. The method of
0. 19. The method of
0. 20. The method of
0. 21. The method of
0. 22. The method of
0. 23. The method of
0. 24. The method of
0. 25. The method of
0. 26. The method of
0. 27. The method of
0. 28. The method of
0. 29. The method of
0. 30. The method of
0. 31. A method of sharing internet browsing experiences, including:
tracking automatically with a client-side application at least a portion of a user's internet usage and reporting the tracking data to a server;
categorizing at least a portion of the reported tracking data by content category;
presenting to the user a history of the reported tracking data, with tools for searching and forwarding the tracking data;
receiving from the user data identifying of one or more persons on the user's buddy lists and authorizing the persons to receive tracking data;
responsive to a user request, sending one or more entries from the history of the reported tracking data to the authorized persons.
0. 32. A method of sharing computer user experiences, including:
registering a user with a registration server to collect and share visited location data using a client-side application collected while visiting a location with a location-aware device that records the visited location;
accessing one or more of the user's messaging buddy lists to identify one or more buddies with whom the tracking data may be shared;
defining rights of the buddies to access the visited location data;
posting at least a portion of the user's visited location data for the buddies to access according to their defined rights.
|
12-14 is 12A, 12B, 13, and 14 are flowcharts illustrating the capture of URL related data from a user. The actions illustrated by these flowcharts apply as well to capture of other item or location related data.
The following detailed description is made with reference to the figures. Preferred embodiments are described to illustrate the present invention, not to limit its scope, which is defined by the claims. Those of ordinary skill in the art will recognize a variety of equivalent variations on the description that follows.
A common theme among aspects of the present invention is collecting data regarding a user's computer usage experience and sharing that data. So-called “buddies” identified on buddy lists of instant messaging products can share selected aspects of their computer usage experiences. Administrative tools and processes can be provided to set up selective collection and sharing of data. Collection tools and processes operate on a variety of computer usage activities and user responses to their computer usage experiences. Processing tools and methods filter, integrate and correlate the collected data. Display tools and processes make portions of the data accessible on a pre-defined basis, such as according to defined rights of buddies. Aggregation tools and processes assemble statistics about user experiences across different bases, such as buddy lists, categories of users, and all service participants.
Aspects of the present invention include building and making accessible various databases and combinations of databases. The databases specifically described below are illustrated in one or another of the figures; reference numbers are provided for ease of reference. One database is a visited URL database (“VUD”) 100A. A VUD stores URLs visited by users, or by participants. More generally, a user could visit a web site, listen to or watch content, rate a site or content, assign an emoticon or quick comment to a site or content, send or bookmark a site or content or download data; a VUD entry could result. A rating may be thumbs up or thumbs down or its equivalent, a scaled alpha or numeric rating or its equivalent. An emoticon is an icon conveying a reaction, such as: “:)”, “:(”, “:\”, “=)”, “=(”, etc. Quick comments may be user defined and later accessible through a menue, ush as a pull-down menu. In addition to URLs, the database stores additional information such as page title, address, description, categories applicable to the URL, metadata, names of users accessing the URL, timestamps of visits, ratings of the URL, emoticons evaluating the URL, comments on and bookmarks to the URL, or keywords for retrieval. The page title, address, description and metadata may be ascertained from visiting the URL itself. With assistance of the URL's author, metadata may include suggested categorization. Alternatively, categorization may be provided by an existing content analysis provider, such as Yahoo or the Open Source Directory Project at www.dmoz.org 1506. A further alternative is that content could be categorized by a service provider or other sponsor, either for web content or for intranet, extranet or other network content.
Another database used to practice aspects of the present invention is the visited location database (“VLD”) 100B. A VLD stores similar information for locations visited by users or participants carrying portable devices. For instance, a Bluetooth equipped cell phone or pager could interact with a location that a user entered. Walking in the door of a popular restaurant, nightclub or other location could trigger an interaction between a Bluetooth device and a Bluetooth access point sponsored at the location. The Bluetooth device could learn the location visited and report that location immediately or later when the device returned to the proximity of a home access point or the device docked with a home access point. Alternatively, the Bluetooth device could disclose its identity to a Bluetooth access point at a particular location and the access point could report the visit. The user of the Bluetooth device could have the same options for providing additional information regarding the location, as for URLs. The VLD also could store geographic information regarding the location. such as geo-coded data. Several equivalent methods of associating a portable device with a location are available. Sophisticated networks may fingerprint, triangulate or otherwise locate a wireless device based on radio signal characteristics. Sophisticated devices may include circuits that determine the device's location; these circuits may utilize GPS, DGPS, Loran or any other location fixing protocol. The physics of how the device and the location are associated are relatively unimportant; an independent service may be used to track locations visited by a user based on any of the protocols identified above or any other protocol.
The VUD and VLD databases are readily extended to a visited item database 100, which could include items on a computer, intranet, extranet or any network. These items may be data such as multimedia files, XML documents, database searches or virtually any other material. One distinction between practicing aspects of the present invention and general database processing is storing user-based information, such as the user's pattern of visiting and the user's rating, emoticon or comments regarding an item and making stored, user-based information available to buddies. Collectively, VUDs, VLDs and visited item databases can be referred to as VXDs. Reference to one of the three VXDs is intended to refer to all three, unless the context makes it clear that only one of the three applies.
Access control lists (“ACLs”) 102, 103, 104, 1609 also can be maintained as databases. An ACL identifies buddies and controls their access to VUD, VLD, visited item and other activity-related data. A user could set up his or her own ACL via buddy list and access control list administration functions. An enterprise could set up ACLs for enterprise users. ACL-like data complied for instant messaging products could be accessed and utilized to compile ACLs for users or enterprises.
A URL logo database (“ULD”) 101 can be useful for associating logos with web sites. The logos may be sponsors, advertisers or others who provide support for operation of a service practicing aspects of the present invention.
Item categorization for VUD, VLD or visited items can generate exception databases, such as an item match exceptions database (for instance, a URL match exceptions database (“UMED”) 1505) or a topic match exceptions database (“TMED”) 1507. These exception databases record data which require further attention after initial processing to update the VUD, VLD or a visited item database.
An activity viewer database (“AVD”) 1610 can store information associating particular users with URLs, locations or items. Raw data regarding user activity is filtered and matched with entries front the VUD, VLD or visited item database to create the AVD. The AVD holds users' activity parsed into a format for display via the Activity Viewer. It includes the activity, internal flag settings, the URL, the page title, the logo, the username, the timestamp & category for an entry. If a user filters the display of data on the Activity Viewer, data is pulled from this database.
Batch query results can be stored in a database, a “BQD” 2211. Pre-defined queries can be run against the VUD, VLD or visited item database. For instance, top 10 hits, top 50 hits or top 100 hits in a wide range of categories are most efficiently recalculated periodically on a batch basis, rather than in response to ad hoc inquiries.
Third party location detection data can be stored in a detection network directory 2312. Third party data can be provided as received, on an interrupt-like basis, or in response to periodic requests, on a polling or batch basis. Location categorizations and descriptions 2413, e.g., Yellow Pages.Com, AutoDesk, etc. can be used to provide supplemental information about locations.
Location/topic entries which require further attention, after processing to update the VLD, can be stored in another match exceptions database, a “LTMED” 2414.
One aspect of practicing the present invention can include tying into a user's instant messaging products or, more generally, into the user's messaging facilities. For instant messaging (“IM”), users or participants typically set up so-called buddy lists. Other users or participants agree to participate in instant messaging. One IM user can send an instant message to another IM user, if their IM products are compatible. The two can carry on a dialog or a so-called “chat”. More than two users may be included in a real-time chat, when the instant messaging product allows multiple participants. Examples of instant messaging products include AOL's Instant Messenger software, MSN Messenger software, Yahoo! Messenger software, America Online's ICQ software, Odigo's instant messenger software and Jabber's instant messenger software. Reciprocal inclusion on buddy lists typically involves a closer relationship between participants than inclusion on an e-mail mailing list or directory, but tins is not necessarily the case. Buddy lists sometimes are shorter and more selective than general messaging lists or directories.
The present invention also may be applied to a user's messaging facilities by selectively enabling others listed on a general e-mail or messaging list or directory to participate. Selectively enabling others limits the intrusion on a user's privacy and limits various administrative (e.g., setup and administration) and responsive (e.g., junk mail) burdens. Alternatively, group functions used for other e-mail or messaging purposes can be a basis for defining rights to sharing of activity data.
Data stored regarding an experience may include VUD, VLD or VXD databases 100, a logo database for URLs, locations or items 101 and a variety of ACL databases. The access control lists can be maintained at the service provider level 104, the enterprise level 102 or the individual user level 103.
Data 130 reflecting individual experiences and aggregated experiences can be accessed or reported in a variety of ways. An activity viewer running on a user's system 131, either fixed or portable, can appear in a window. Reports on locations, either the experiences of others visiting the location or the proximity of buddies or buddies of buddies can be reported automatically to Bluetooth enabled wireless devices 132 when such devices reach a location or are in contact with a location-sponsored Bluetooth access point. Wireless devices can be synchronized 133 when reasonable bandwidth is available to retain data that would be too voluminous to access via a low bandwidth connection. The interfaces of instant message tools 134 can serve as an output channel, as licensing arrangements become available. Physical reports 135 can be printed for analysis. These reports can cover analysis of interactions among participants and spreading of information from one user to others.
The sharing status toggle 366 allows a user to turn sharing on and off. When sharing is on, rights defined in the ALL provide access for buddies to the user's activity. When sharing is off, the user's activity will not be shared with buddies. However, the user's activity may still be recorded to a tracking server either for aggregation or to be associated with the user but not reported to buddies. The user's options or access to information may be limited when sharing is off, tending to encourage the user to leave sharing activated. The window maximize control 367 allows direct access to maximizing the window to a pre-selected format.
Other aspects of this interface include space for a banner 368 (either static or moving), an invite button 369, a hot list access 370, a search entry window 371 and a search button 372. The banner could be used to generate advertising revenue. The invite button 369 provides access to an invite interface such as
Several rows of information responsive to the filters 971-976 appear in
The top part of the
The inset to
If the metadata provides a page title 1209, the system stores the page title in a temporary variable. The system next compares the URL to entries in the VUD 1210. If the URL is found in VUD 1211, the system has to determine whether a page title is stored on the VUD 1221. If there is a page title on the VUD 1222, the system action depends on whether the page title variable has been set to null. If not, the system over writes the value on the VUD with the value of the temporary page title variable 1224. If the temporary page title variable is null, the page title stored on the VUD is used 1223. Next, the system determines whether the URL has been categorized on the VUD 1225. If not, the system sets a temporary category variable to uncategorized 1227. This is the same action that the system takes in the URL is not on the VUD 1211. If the URL has been categorized on the VUD, the system sets a temporary category variable based on the contents of the VUD 1226. The system checks to determine if the URL or a portion of the URL is logged in a logo database 1228. The logo or ULD database 101 holds vendor logo images that correspond to the vendor's URLs. If the vendor has not arranged for its logo to be stored on the VLD 1229, the system sets the temporary local variable to null 1231. If there is a corresponding logo, the temporary variable is set to the corresponding logo image 1230. The system sets a temporary activity variable to view 1232, corresponding to viewing a URL. The flow continues in
A variety of activities may be associated with items other than URLs. Depending on the type of item involved, the user may listen to or watch the item 1461, download the item 1463, purchase the item 1465, put the item on a wish list 1467, transfer the item to a mobile device, such as a cell phone or PDA 1469, or select some other process 1471. In some circumstances, an unrecognized activity may occur 1473, which the system may either ignore or treat is an error condition. A listen to or watch activity 1461 causes the system to invoke a player and to record the action and properties of the item listened to or watched 1462. The recorded information is forwarded for addition to the VUD. A download activity invokes a process, which records the download action and properties of the item downloaded 1464. The recorded information is forwarded for addition to the VUD. A purchase activity 1465 invokes a process 1466, which records the purchase action and properties of the item purchased. The recorded information is forwarded for addition to the VUD. A wish list activity 1467 invokes a wish list process 1468 to maintain and add to the user's wish list. The wish list can be maintained as part of the VUD or in a separate database. The information can be maintained redundantly as part of the VUD and as the result of a batch query. When the activity is to transfer the item to a mobile device 1469, the system invokes a process for sending the information to the mobile device, records the action and properties of the items sent to the mobile device, and forwards the recorded information for addition to the VUD 1470. The processing of each of these activities in
In
The interfaces and software described above support many methods and devices for sharing communication device and computer usage experiences. One type of sharing communication device user experiences is sharing computer usage experiences, including Internet browsing experiences. Whichever communication device is used, sharing may depend on registration by a user with a registration server. Registration may involve downloading client software to run on the user's system. For enterprise applications, registration may be handled by a system administrator and integrated or coordinated with registration for network login, e-mail or other messaging. In some embodiments, registration may include contractual terms which limit the use of information collected from the user. In other embodiments, registration may be designed to exclude collection of certain user information, such as the user's e-mail address, actual name or physical address. Some users may feel more comfortable registering with the system if registration excludes collection of any information that identifies the user in a manner adapted to direct marketing. Even if registration excludes initial collection of user identifying information, the user may be given the option of entering additional personal information for general use by the providers of the system or for restricted use, in accordance with contractual terms. The registration process may make the user aware that at least a portion of the user's experiences with a communication device, computer or Internet browser will be collected and shared. It also may make the user aware that information collected from the user will be aggregated with information collected from other users.
Sharing communication device experiences also may include accessing one or more messaging buddy lists associated with the user. Accessing pre-existing buddy lists provides a base for linking the user and buddies with whom tracking data may be shared. Buddy lists may be maintained by AOL's Instant Messenger software, MSN's Messenger software, Yahoo! Messenger software, America Online's ICQ software, Indigo's instant messenger software or Jabber's instant messenger software. More generally, message recipient lists maintained in e-mail systems, such as Microsoft's Outlook products or AOL's Netscape products may maintain the lists that are accessed. Messaging systems such as Lotus Notes also may maintain message recipient lists that the system can access to identify persons with whom tracking data may be shared.
Buddies or groups of buddies are given defined rights to access tracking data collected from the user. Defined rights of buddies to access tracking data may be based on content categories of material accessed. Examples of content categories or topics can be found in
At least a portion of the user's computer usage experiences are tracked and reported to a tracking server. This tracking may be carried out by a module resident on the user's computer or by a device placed between the user's computer and an access point to the Internet. In an enterprise implementation, tracking can be carried out by a server or proxy server. The tracking data can be filtered before it is reported to the tracking server. Data may be filtered based on a sharing on/off option exercised by the user. It also may be filtered based on content categories. In some implementations, only those activities that fit content categories which the user agreed to share would be reported to the tracking server. Alternatively, activity could be reported to the tracking server that was never intended to be posted for access by buddies. The tracking server or a posting server could filter the information before posting it for buddies to access. The computer user experiences tracked could include viewing URLs, downloading files, listening to songs, viewing videos, making purchases, sending items from a user to their buddies, or general messaging between the user and buddies.
In addition to computer user experiences, mobile communication device locations can be tracked, using any of the technologies described above. Activities related to location may include visiting the location, rating, commenting on it, assigning an emoticon, or connecting with another buddy or buddy of a buddy at the location. Proximity to a location may be variation on visiting the location.
It further may be useful to categorize at least a portion of the tracking data by content. The categorized tracking data would be subject to filtering and sorting. Categorized tracking data also could be searchable by content category and date range. For instance, a particular buddy's viewing of stock-related sites containing the name “Cisco” during a one or two-month period could be located.
Tracking data can be posted, after filtering, for buddies to access according to their defined access rights. The interface for viewing activity reflected by the tracking data may include a send button, which allows a user to forward an item to a buddy, either with or without comment. Interface also may include rating an emoticon buttons. It may facilitate free text comments on an item. These functions may apply to selected groups of items, in addition to applying to individual items. The buttons for free text comments and the feature for adding notes to items sent to buddies allow annotation of items.
The tracking process further may include generating a full text index of items viewed. This indexing may be performed in the context to viewing URLs or, in an enterprise implementation, in the context of the viewing internal work product or summaries of internal work product. Automated some regeneration may be combined with indexing, so that summaries are indexed.
Additional functionality of the system, which passively tracks activities of registered users may include tracing the flow of information or data among registered users. Information which is sent from a user to a buddy may be annotated with a history of users who forwarded the information. Alternatively, it may include a first user who forward the information and the immediately previous forwarding user. Or, it could identify a limited number of previous forwarding users. If less than a will history of users who forwarded the information is included with information sent from a user to a buddy, an analysis server may use a combination of timestamps and forwarding information to determine the dissemination or diffusion information and the velocity at which it is disseminated. Social network theory provides a number of metrics for evaluating the dissemination or diffusion of information. The tracking capabilities which are an aspect of the present invention can readily be adapted to quantifying the relative influence of one or another user on their buddies, including the strength, frequency, extent and relative value of their influence. Certain users may be selected for introduction to information or new product releases. Certain users may be selected and rewarded as a result of efficient dissemination of information through their social network.
A system practicing aspects of the present invention can readily collect, collate and present user generated lists of superlatives regarding activities, products and services. List may be generated by time period, utilizing date stamps and activities, number of top items (10 or 50 or 100 top items) or other filtering criteria.
The availability of location information for mobile communication devices allows the system practicing aspects of the present invention to present information regarding buddies and buddies of buddies who may be present at the user's physical location. Based on tracking visits to locations, information can be generated such as a particular user's list of favorite restaurants or favorite boutiques. Patterns of visits to physical locations can be reported. Information can be presented to users based on locations recently visited.
Information associated with particular locations can be offered up to users of mobile communication devices, in a context sensitive mode. Categories of information such as buddies' ratings of nearby restaurants can be provided, utilizing location information generated from the mobile communication device and established buddy lists.
While the preceding example applications are cast in terms of a method, devices and systems employing this method are easily understood. A magnetic memory containing a program capable of practicing the claimed method is one such device. A computer system having memory loaded with a program practicing the claimed method is another such device. A system including a registration server and a tracking server practicing the methods described above is another such device.
While the present invention is disclosed by reference to the embodiments and examples detailed above, it is understood that these examples are intended in an illustrative rather than in a limiting sense. It is contemplated that modifications and combinations will readily occur to those skilled in the art, which modifications and combinations will be within the spirit of the invention and the scope of the following claims.
Briggs, Darren P., Bruce, Brady O., Mitchell, Michael W., Reed, IV, Emile L.
Patent | Priority | Assignee | Title |
RE47704, | Apr 24 2001 | SVENDSEN, HUGH B; SVENDSEN, SARAH S; CURTIS, SCOTT D; FARRELLY, EUGENE; HELPINGSTINE, MICHAEL W ; Ikorongo Texas, LLC | Method and apparatus for selectively sharing and passively tracking communication device experiences |
RE48904, | Apr 24 2001 | SVENDSEN, HUGH B; SVENDSEN, SARAH S; CURTIS, SCOTT D; FARRELLY, EUGENE; HELPINGSTINE, MICHAEL W ; Ikorongo Texas, LLC | Method and apparatus for selectively sharing and passively tracking communication device experiences |
Patent | Priority | Assignee | Title |
5568645, | Aug 21 1991 | Intermec Technologies Corporation | Versatile RF data capture system |
5760917, | Sep 16 1996 | Intellectual Ventures Fund 83 LLC | Image distribution method and system |
5808613, | May 28 1996 | CA, INC | Network navigator with enhanced navigational abilities |
6018619, | May 24 1996 | Microsoft Technology Licensing, LLC | Method, system and apparatus for client-side usage tracking of information server systems |
6195654, | Nov 16 1995 | CHARTOLEAUX KG LIMITED LIABILITY COMPANY | System and method for obtaining improved search results and for decreasing network loading |
6250930, | May 30 1997 | Picante Communications Corporation | Multi-functional communication and aggregation platform |
6480885, | Sep 15 1998 | TUMBLEWEED HOLDINGS LLC | Dynamically matching users for group communications based on a threshold degree of matching of sender and recipient predetermined acceptance criteria |
6549768, | Aug 24 1999 | Nokia Technologies Oy | Mobile communications matching system |
6578072, | Jan 14 1998 | Meta Platforms, Inc | Network photograph service system |
6606657, | Jun 22 1999 | Mavenir LTD | System and method for processing and presenting internet usage information |
6618593, | Sep 08 2000 | WESERVE SYNVEST, LLC | Location dependent user matching system |
6654789, | Jul 20 1999 | ATDATA, LLC | System for storing and retrieving old and new electronic identifiers |
6662231, | Jun 30 2000 | DISTRIBUTED MEDIA SOLUTIONS, LLC | Method and system for subscriber-based audio service over a communication network |
6895084, | Aug 24 1999 | Genesys Telecommunications Laboratories, Inc | System and method for generating voice pages with included audio files for use in a voice page delivery system |
7080139, | Apr 24 2001 | SVENDSEN, HUGH B; SVENDSEN, SARAH S; CURTIS, SCOTT D; FARRELLY, EUGENE; HELPINGSTINE, MICHAEL W ; Ikorongo Texas, LLC | Method and apparatus for selectively sharing and passively tracking communication device experiences |
7366522, | Feb 28 2000 | IpVenture, Inc | Method and system for location tracking |
20010036224, | |||
20020049686, | |||
20020052925, | |||
20020065802, | |||
20020072955, | |||
20020087382, | |||
20020087496, | |||
20020144259, | |||
20030018799, | |||
20030054810, | |||
20030225836, | |||
20040088271, | |||
20040088355, | |||
20050271514, | |||
20090183091, | |||
20090271514, | |||
EP1323318, | |||
EP2312871, | |||
JP2002196778, | |||
KR20020007934, | |||
RE41450, | Apr 24 2001 | SVENDSEN, HUGH B; SVENDSEN, SARAH S; CURTIS, SCOTT D; FARRELLY, EUGENE; HELPINGSTINE, MICHAEL W ; Ikorongo Texas, LLC | Method and apparatus for selectively sharing and passively tracking communication device experiences |
RE44324, | Apr 24 2001 | SVENDSEN, HUGH B; SVENDSEN, SARAH S; CURTIS, SCOTT D; FARRELLY, EUGENE; HELPINGSTINE, MICHAEL W ; Ikorongo Texas, LLC | Method and apparatus for selectively sharing and passively tracking communication device experiences |
WO221864, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 14 2013 | Tena Technology, LLC | (assignment on the face of the patent) | / | |||
May 01 2015 | Tena Technology, LLC | CONCERT DEBT, LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 036501 | /0280 | |
May 01 2015 | Concert Technology Corporation | CONCERT DEBT, LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 036515 | /0471 | |
Aug 01 2015 | Tena Technology, LLC | CONCERT DEBT, LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 036501 | /0123 | |
Aug 01 2015 | Concert Technology Corporation | CONCERT DEBT, LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 036515 | /0495 | |
Aug 02 2018 | Tena Technology, LLC | Ikorongo Technology, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 046728 | /0857 | |
Aug 27 2018 | CONCERT DEBT, LLC | Ikorongo Technology, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 046728 | /0647 | |
Aug 27 2018 | CONCERT DEBT, LLC | Ikorongo Technology, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 046726 | /0749 | |
Mar 20 2020 | FARRELLY, EUGENE | Ikorongo Texas, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0791 | |
Mar 20 2020 | CURTIS, SCOTT D | Ikorongo Texas, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0791 | |
Mar 20 2020 | SVENDSEN, SARAH S | Ikorongo Texas, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0791 | |
Mar 20 2020 | SVENDSEN, HUGH B | Ikorongo Texas, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0791 | |
Mar 20 2020 | Ikorongo Technology, LLC | HELPINGSTINE, MICHAEL W | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0756 | |
Mar 20 2020 | Ikorongo Technology, LLC | FARRELLY, EUGENE | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0756 | |
Mar 20 2020 | Ikorongo Technology, LLC | CURTIS, SCOTT D | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0756 | |
Mar 20 2020 | Ikorongo Technology, LLC | SVENDSEN, SARAH S | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0756 | |
Mar 20 2020 | Ikorongo Technology, LLC | SVENDSEN, HUGH B | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0756 | |
Mar 20 2020 | HELPINGSTINE, MICHAEL W | Ikorongo Texas, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052246 | /0791 |
Date | Maintenance Fee Events |
Feb 26 2018 | REM: Maintenance Fee Reminder Mailed. |
Jul 18 2018 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Jul 18 2018 | M1556: 11.5 yr surcharge- late pmt w/in 6 mo, Large Entity. |
Date | Maintenance Schedule |
Jan 20 2018 | 4 years fee payment window open |
Jul 20 2018 | 6 months grace period start (w surcharge) |
Jan 20 2019 | patent expiry (for year 4) |
Jan 20 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jan 20 2022 | 8 years fee payment window open |
Jul 20 2022 | 6 months grace period start (w surcharge) |
Jan 20 2023 | patent expiry (for year 8) |
Jan 20 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jan 20 2026 | 12 years fee payment window open |
Jul 20 2026 | 6 months grace period start (w surcharge) |
Jan 20 2027 | patent expiry (for year 12) |
Jan 20 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |