IP Library Granted Patent US 10,318,590
Granted Patent B2
US 10,318,590 · App. 14/460,744 · Granted Jun 11, 2019

User interface operation based on token frequency of use in text

Inventors: David Cook (Barrington, IL); Jacek Zwierzchlejski (Naperville, IL); Stacey Kacek (Streamwood, IL); Jason Maeder (New Lenox, IL); Stewart Beck (Bolingbrook, IL)
Assignee: FEEEDOM SOLUTIONS GROUP, LLC
G06F16/93G06F16/334G06F16/338
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,318,590
App. No.
14/460,744
Granted
Jun 11, 2019
Kind
B2
Abstract

Operation of a user interface includes performing token based analysis of a baseline text corpus and a targeted text listing. For a selected token in the targeted text listing, a matching baseline token in identified. From a plurality of contexts corresponding to the matching baseline token, context-matched and non-context matched usage data for the matching baseline token is identified and provided to a user interface. Similar processing may be performed on the basis of a related, but matching, baseline token. In another embodiment, instances of similar spelling errors are identified on the basis of a plurality of tokens identified in the targeted text listing.

Claims (80)

1. A method for providing a user interface of a machine for production of electronic text-based documents and, the machine comprising at least one processor and a display, the method comprising:

identifying, by the at least one processor, at least one baseline token in a baseline text corpus comprising text corresponding to a selected domain;

identifying, by the at least one processor, for each of the at least one baseline token, a plurality of corresponding baseline contexts;

for each of the at least one baseline token, and for each of the plurality of corresponding baseline contexts for the baseline token,

determining, by the at least one processor, frequency of use data;

storing, by the at least one processor, the frequency of use data in association with the baseline token and the corresponding baseline context;

identifying, by the at least one processor, at least one token in a targeted text listing;

identifying, by the at least one processor, for each of the at least one token, a corresponding context based on the targeted text listing;

for a selected token of the at least one token in the targeted text listing, identifying, by the at least one processor, context-matched usage data and non-context-matched usage data for a matching baseline token that matches the selected token, wherein the context-matched usage data comprises frequency of use data for the matching baseline token in a first baseline context that matches the corresponding context of the selected token, wherein the non-context-matched usage data further comprises frequency of use data for the matching baseline token in a second baseline context that does not match the corresponding context of the selected token, and wherein the matching baseline token, the first baseline context and the second baseline context are based on the baseline text corpus; and

providing, by the at least one processor to the user interface on the display, the context-matched usage data and the non-context-matched usage data.

2. The method of claim 1 , further comprising:

receiving, by the at least one processor, identification of an electronic document as the targeted text listing.

3. The method of claim 1 , further comprising:

receiving, by the at least one processor via the user interface, text data as the targeted text listing.

4. The method of claim 1 , wherein determining the frequency of use data further comprises normalizing the frequency of use data relative to a normalizing parameter determined according to the corresponding baseline context.

5. The method of claim 1 , wherein identifying context-matched usage data and non-context-matched usage data further comprises:

comparing, by the at least one processor, the selected token with the at least one baseline token to identify the matching baseline token;

comparing, by the at least one processor, the corresponding context of the selected token with the at least one corresponding baseline context of the matching baseline token to identify a matching context and a non-matching context of the plurality of corresponding baseline contexts;

providing, by the at least one processor as the context-matched usage data, that frequency of use data stored in association with the matching baseline token and the matching context; and

providing, by the at least one processor as the non-context-matched usage data, that frequency of use data stored in association with the matching baseline token and the non-matching context.

6. The method of claim 1 , wherein providing the context-matched usage data and the non-context-matched usage data to the user interface on the display further comprises displaying the context-matched usage data and the non-context-matched usage data in any one or combination of: graphical form, symbolic form and textual form.

7. The method of claim 1 , further comprising:

identifying, by the at least one processor, a related baseline token based on the selected token;

identifying, by the at least one processor, additional context-matched usage data and additional non-context-matched usage data for the related baseline token, wherein the additional context-matched usage data comprises frequency of use data for the related baseline token in a third baseline context matching the corresponding context of the selected token, and wherein the additional non-context-matched usage data further comprises frequency of use data for the baseline token in a fourth baseline context not matching the corresponding context of the selected token; and

providing, by the at least one processor to the user interface on the display, the additional context-matched usage data and the additional non-context-matched usage data.

8. The method of claim 7 , wherein the related baseline token is related to the selected token by any of: a synonym relationship, an antonym relationship, a hypernym relationship, a meronym relationship, a holonym relationship, a homophone relationship, a category relationship, a trend behavior relationship and an overall usage count relationship.

9. An apparatus for production of electronic text-based documents based on a user interface, the apparatus comprising:

at least one processor operatively connected to a display;

a storage device operatively connected to the at least one processor and having stored thereon instructions that, when executed by the at least one processor, cause the at least one processor to:

identify at least one baseline token in a baseline text corpus comprising text corresponding to a selected domain;

identify, for each of the at least one baseline token, a plurality of corresponding baseline contexts;

for each of the at least one baseline token, and for each of the plurality of corresponding baseline contexts for the baseline token,

determine frequency of use data;

store the frequency of use data in association with the baseline token and the corresponding baseline context;

identify at least one token in a targeted text listing;

identify, for each of the at least one token, a corresponding context based on the targeted text listing;

for a selected token of the at least one token in the targeted text listing, identify context-matched usage data and non-context-matched usage data for a matching baseline token that matches the selected token, wherein the context-matched usage data comprises frequency of use data for the matching baseline token in a first baseline context that matches the corresponding context of the selected token, wherein the non-context-matched usage data further comprises frequency of use data for the matching baseline token in a second baseline context that does not match the corresponding context of the selected token, and wherein the matching baseline token, the first baseline context and the second baseline context are based on the baseline text corpus; and

provide, to the user interface on the display, the context-matched usage data and the non-context-matched usage data.

10. The apparatus of claim 9 , wherein the storage device further comprises instructions that, when executed by the at least one processor, cause the at least one processor to:

receive identification of an electronic document as the targeted text listing.

11. The apparatus of claim 9 , wherein the storage device further comprises instructions that, when executed by the at least one processor, cause the at least one processor to:

receive, via the user interface, text data as the targeted text listing.

12. The apparatus of claim 9 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to determine the frequency of use data are further operative to normalize the frequency of use data relative to a normalizing parameter determined according to the corresponding baseline context.

13. The apparatus of claim 9 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to identify context-matched usage data and non-context-matched usage data are further operative to:

compare the selected token with the at least one baseline token to identify the matching baseline token;

compare the corresponding context of the selected token with the at least one corresponding baseline context of the matching baseline token to identify a matching context and a non-matching context of the plurality of corresponding baseline contexts;

provide, as the context-matched usage data, that frequency of use data stored in association with the matching baseline token and the matching context; and

provide, as the non-context-matched usage data, that frequency of use data stored in association with the matching baseline token and the non-matching context.

14. The apparatus of claim 9 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to provide the context-matched usage data and the non-context-matched usage data to the user interface on the display are further operative to display the context-matched usage data and the non-context-matched usage data in any one or combination of: graphical form, symbolic form and textual form.

15. The apparatus of claim 9 , wherein the storage device further comprises instructions that, when executed by the at least one processor, cause the at least one processor to:

identify a related baseline token based on the selected token;

identify additional context-matched usage data and additional non-context-matched usage data for the related baseline token, wherein the additional context-matched usage data comprises frequency of use data for the related baseline token in a third baseline context matching the corresponding context of the selected token, and wherein the additional non-context-matched usage data further comprises frequency of use data for the baseline token in a fourth baseline context not matching the corresponding context of the selected token; and

provide, to the user interface on the display, the additional context-matched usage data and the additional non-context-matched usage data.

16. The apparatus of claim 15 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to identify the related baseline token are further operative to identify, between the related baseline token and the selected token, any of: a synonym relationship, an antonym relationship, a hypernym relationship, a meronym relationship, a holonym relationship, a homophone relationship, a category relationship, a trend behavior relationship and an overall usage count relationship.

17. A non-transitory, machine-readable medium having stored thereon instructions that, when executed by at least one processor, cause the at least one processor to operate as an apparatus for production of electronic text-based documents based on a user interface and to:

identify at least one baseline token in a baseline text corpus comprising text corresponding to a selected domain;

identify, for each of the at least one baseline token, a plurality of corresponding baseline contexts;

for each of the at least one baseline token, and for each of the plurality of corresponding baseline contexts for the baseline token,

determine frequency of use data;

store the frequency of use data in association with the baseline token and the corresponding baseline context;

identify at least one token in a targeted text listing;

identify, for each of the at least one token, a corresponding context based on the targeted text listing;

for a selected token of the at least one token in the targeted text listing, identify context-matched usage data and non-context-matched usage data for a matching baseline token that matches the selected token, wherein the context-matched usage data comprises frequency of use data for the matching baseline token in a first baseline context that matches the corresponding context of the selected token, wherein the non-context-matched usage data further comprises frequency of use data for the matching baseline token in a second baseline context that does not match the corresponding context of the selected token, and wherein the matching baseline token, the first baseline context and the second baseline context are based on the baseline text corpus; and

provide, to the user interface on a display operatively connected to the at least one processing device, the context-matched usage data and the non-context-matched usage data.

18. The machine-readable medium of claim 17 , further comprising instructions that, when executed by the at least one processor, cause the at least one processor to:

receive identification of an electronic document as the targeted text listing.

19. The machine-readable medium of claim 17 , further comprising instructions that, when executed by the at least one processor, cause the at least one processor to:

receive, via the user interface, text data as the targeted text listing.

20. The machine-readable medium of claim 17 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to determine the frequency of use data are further operative to normalize the frequency of use data relative to a normalizing parameter determined according to the corresponding baseline context.

21. The machine-readable medium of claim 17 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to identify context-matched usage data and non-context-matched usage data are further operative to:

compare the selected token with the at least one baseline token to identify the matching baseline token;

compare the corresponding context of the selected token with the at least one corresponding baseline context of the matching baseline token to identify a matching context and a non-matching context of the plurality of corresponding baseline contexts;

provide, as the context-matched usage data, that frequency of use data stored in association with the matching baseline token and the matching context; and

provide, as the non-context-matched usage data, that frequency of use data stored in association with the matching baseline token and the non-matching context.

22. The machine-readable medium of claim 17 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to provide the context-matched usage data and the non-context-matched usage data to the user interface on the display are further operative to display the context-matched usage data and the non-context-matched usage data in any one or combination of: graphical form, symbolic form and textual form.

23. The machine-readable medium of claim 17 , further comprising instructions that, when executed by the at least one processor, cause the at least one processor to:

identify a related baseline token based on the selected token;

identify additional context-matched usage data and additional non-context-matched usage data for the related baseline token, wherein the additional context-matched usage data comprises frequency of use data for the related baseline token in a third baseline context matching the corresponding context of the selected token, and wherein the additional non-context-matched usage data further comprises frequency of use data for the baseline token in a fourth baseline context not matching the corresponding context of the selected token; and

provide, to the user interface on the display, the additional context-matched usage data and the additional non-context-matched usage data.

24. The machine-readable medium of claim 23 , wherein those instructions that, when executed by the at least one processor, cause the at least one processor to identify the related baseline token are further operative to identify, between the related baseline token and the selected token, any of: a synonym relationship, an antonym relationship, a hypernym relationship, a meronym relationship, a holonym relationship, a homophone relationship, a category relationship, a trend behavior relationship and an overall usage count relationship.

Assignments (6)
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT RECORDED AT REEL 039120, FRAME 0168 Recorded Jun 3, 2019
From: PNC BANK, NATIONAL ASSOCIATION
To: FREEDOM SOLUTIONS GROUP, L.L.C.; MICROSYSTEMS HOLDINGS COMPANY, LLC
Reel/Frame 049354/0402 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT REEL 039389, FRAME 0654 AND REEL 046713, FRAME 0243 Recorded Jun 3, 2019
From: SARATOGA INVESTMENT CORP. SBIC LP
To: FREEDOM SOLUTIONS GROUP, L.L.C.; MICROSYSTEMS HOLDINGS COMPANY, LLC
Reel/Frame 049346/0276 →
PATENT SECURITY AGREEMENT Recorded May 31, 2019
From: LITÉRA CORPORATION; FREEDOM SOLUTIONS GROUP, L.L.C.
To: OWL ROCK CAPITAL CORPORATION
Reel/Frame 049337/0220 →
PATENT SECURITY AGREEMENT Recorded Jul 19, 2016
From: FREEDOM SOLUTIONS GROUP, L.L.C.; MICROSYSTEMS HOLDING COMPANY, LLC
To: SARATOGA INVESTMENT CORP. SBIC LP, AS AGENT
Reel/Frame 039389/0654 →
SECURITY INTEREST Recorded Jul 11, 2016
From: FREEDOM SOLUTIONS GROUP, L.L.C.; MICROSYSTEMS HOLDING COMPANY, LLC
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 039120/0168 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2014
From: COOK, DAVID; ZWIERZCHLEJSKI, JACEK; KACEK, STACEY; MAEDER, JASON; BECK, STEWART
To: FREEDOM SOLUTIONS GROUP, LLC D/B/A MICROSYSTEMS
Reel/Frame 033829/0254 →
Continuity (1)
Related Publication 20160048512A1 · Feb 18, 2016