DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This office action is in responsive to communication(s): original application filed on 05/21/2024, said application claims a priority filing date of 08/26/2022. Claims 1-20 are pending. Claims 1, 9, and 15 are independent.
Claim Objections
Claims 2, 15, and 18 are objected to because of the following informalities:
in Claim 2, line 5, "… the graphical object selectable by a user to display the drawer page" appears to be "… the graphical object selectable by the user to display the drawer page";
in Claim 15, line 13, "… wherein the historical wherein the historical data associated with the drawer bar comprises …" appears to be "… wherein the historical data associated with the drawer bar comprises …";
in Claim 18, line 1, "The non-transitory computer-readable medium of claim of claim 16 …" appears to be "The non-transitory computer-readable medium of claim 16 …".
Appropriate correction is required.
Double Patenting
The non-statutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A non-statutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on non-statutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a non-statutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based e-Terminal Disclaimer may be filled out completely online using web-screens. An e-Terminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about e-Terminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are rejected on the ground of non-statutory double patenting as being unpatentable over Claims 1, 1-16, 18, 17, and 19 of U.S. Patent No. 12,019,851 B2. Although the claims at issue are not identical, they are not patentably distinct from each other because claim limitations of U.S. Patent No. 12,019,851 B2 falls entirely within the scope of the claimed limitations of present application as shown below.
Present Application 18/670,069
U.S. Patent No. 12,019,851 B2
1. A system comprising: a processor; and a memory comprising program code that is executable by the processor for causing the processor to:
9. A computer-implemented method comprising:
15. A non-transitory computer-readable medium comprising program code that is executable by a processor for causing the processor to:
1. A system comprising: a processor; and a memory comprising program code that is executable by the processor for causing the processor to:
8. A computer-implemented method comprising:
14. A non-transitory computer-readable medium comprising program code that is executable by a processor for causing the processor to:
generate/generating a static page of a graphical user interface;
generate/generating a static page of a graphical user interface,
2. The system of claim 1, wherein the static page comprises a first set of interactive elements comprising: a plurality of resource shortcuts; a plurality of account boxes; and
the static page comprising a first set of interactive elements comprising: a plurality of resource shortcuts; a plurality of account boxes; and
the graphical object selectable by a user to display the drawer page.
receive/receiving a selection of a graphical object by a user at the graphical user interface to display a drawer page;
the drawer page overlaid on at least a portion of the static page and
a graphical object selectable by a user to display a drawer page that overlays at least a portion of the static page;
receive/receiving a selection of the graphical object;
the drawer page overlaid on at least the portion of the static page and
generate/generating the drawer page of the graphical user interface,
generate/generating the drawer page of the graphical user interface,
the drawer page … comprising a drawer bar that is interactable by the user to adjust a drawer page size of the drawer page and a static page size of the static page based on a position of the drawer bar; and
the drawer page … comprising: a drawer bar that is interactable by the user to adjust a drawer page size of the drawer page and a static page size of the static page based on a position of the drawer bar; and
display/displaying the static page and the drawer page of the graphical user interface, the drawer bar positioned at a default position based on historical data associated with the drawer bar, wherein the historical data associated with the drawer bar comprises data associated with user adjustments made by a plurality of users to a plurality of drawer bar positions using devices that are a device type that matches the device type associated with the user.
display/displaying the static page and the drawer page of the graphical user interface, the drawer bar positioned at a default position based on historical data associated with the drawer bar, wherein the historical data associated with the drawer bar comprises data associated with user adjustments made by a plurality of users to a plurality of drawer bar positions using devices that are a device type that matches the device type associated with the user.
As shown in the comparison table above, although slightly different claim languages are used, Claim 2 of present application has similar scopes as in Claim 1 of prior U.S. Patent No. 12,019,851 B2, and independent Claims 1, 8, and 14 of U.S. Patent No. 12,019,851 B2 includes additional limitations "the static page comprising a first set of interactive elements comprising: a plurality of resource shortcuts; a plurality of account boxes" compared to independent Claims 1, 9, and 15 of the present application respectively.
Also, as shown in the comparison table below, dependent Claims 3-8 of the present application use the same claim language as recited in Claims 2-7 of U.S. Patent No. 12,019,851 B2 respectively, dependent Claims 10-14 of the present application use the same claim language as recited in Claims 9-13 of U.S. Patent No. 12,019,851 B2 respectively, and dependent Claims 16-20 of the present application use the same claim language as recited in Claims 15-16, 18, 17, and 19 of U.S. Patent No. 12,019,851 B2 respectively.
Present Application 18/670,069
U.S. Patent No. 12,019,851 B2
3. The system of claim 1, further comprising program code that is executable by the processor for causing the processor to:
20. The non-transitory computer-readable medium of claim 15, further comprising program code that is executable by the processor for causing the processor to:
detect metadata corresponding to hardware that is associated with a user device; and based on the metadata, adjust the default position of the drawer bar.
2. The system of claim 1, further comprising program code that is executable by the processor for causing the processor to:
19. The non-transitory computer-readable medium of claim 14, further comprising program code that is executable by the processor for causing the processor to:
detect metadata corresponding to hardware that is associated with a user device; and based on the metadata, adjust the default position of the drawer bar.
4. The system of claim 1,
10. The computer-implemented method of claim 9,
16. The non-transitory computer-readable medium of claim 15,
wherein the drawer page comprises a second set of interactive elements comprising a message box configured to receive user input, and at least one message bubble configured to display an output to the user.
3. The system of claim 1,
9. The computer-implemented method of claim 8,
15. The non-transitory computer-readable medium of claim 14,
wherein the drawer page comprises a second set of interactive elements comprising a message box configured to receive user input, and at least one message bubble configured to display an output to the user.
5. The system of claim 4,
11. The computer-implemented method of claim 10,
17. The non-transitory computer-readable medium of claim 16,
wherein the second set of interactive elements is configured to provide the user input to a virtual assistant that is configured to generate the output based on the user input to engage in correspondence with the user.
4. The system of claim 3,
10. The computer-implemented method of claim 9,
16. The non-transitory computer-readable medium of claim 15,
wherein the second set of interactive elements is configured to provide the user input to a virtual assistant that is configured to generate the output based on the user input to engage in correspondence with the user.
6. The system of claim 5,
12. The computer-implemented method of claim 11,
18. The non-transitory computer-readable medium of claim 16,
wherein the user input comprises an audio input.
5. The system of claim 4,
11. The computer-implemented method of claim 10,
18. The non-transitory computer-readable medium of claim 15,
wherein the user input comprises an audio input.
7. The system of claim 5,
13. The computer-implemented method of claim 11,
19. The non-transitory computer-readable medium of claim 17,
wherein the virtual assistant is configured to, in response to a certain user input, connect the user with a live agent.
6. The system of claim 4,
12. The computer-implemented method of claim 10,
17. The non-transitory computer-readable medium of claim 16,
wherein the virtual assistant is configured to, in response to a certain user input, connect the user with a live agent.
8. The system of claim 1,
14. The computer-implemented method of claim 9,
wherein a portion of the drawer bar is selectable by the user to hide the drawer page.
7. The system of claim 1,
13. The computer-implemented method of claim 8,
wherein a portion of the drawer bar is selectable by the user to hide the drawer page.
Allowable Subject Matter
Claims 1-20 allowable after filing e-Terminal Disclaimer that meets all requirements.
The following is a statement of reasons for the indication of allowable subject matter:
In regard to independent Claims 1, 9, and 15, prior arts of records, either singularly or in combination, do not teach or suggest the combination of claimed elements including "a system comprising: a processor; and a memory comprising program code that is executable by the processor for causing the processor to: generate a static page of a graphical user interface; receive a selection of a graphical object by a user at the graphical user interface to display a drawer page; generate the drawer page of the graphical user interface, the drawer page overlaid on at least a portion of the static page and comprising a drawer bar that is interactable by the user to adjust a drawer page size of the drawer page and a static page size of the static page based on a position of the drawer bar; and display the static page and the drawer page of the graphical user interface, the drawer bar positioned at a default position based on historical data associated with the drawer bar, wherein the historical data associated with the drawer bar comprises data associated with user adjustments made by a plurality of users to a plurality of drawer bar positions using devices that are a device type that matches the device type associated with the user", "a computer-implemented method comprising: generating a static page of a graphical user interface; receiving a selection of a graphical object by a user at the graphical user interface to display a drawer page; generating a drawer page of the graphical user interface, the drawer page overlaid on at least a portion of the static page and comprising: a drawer bar that is interactable by the user to adjust a drawer page size of the drawer page and a static page size of the static page based on a position of the drawer bar; and displaying the static page and the drawer page of the graphical user interface, the drawer bar positioned at a default position based on historical data associated with the drawer bar, wherein the historical data associated with the drawer bar comprises data associated with user adjustments made by a plurality of users to a plurality of drawer bar positions using devices that are a device type that matches the device type associated with the user", or "a non-transitory computer-readable medium comprising program code that is executable by a processor for causing the processor to: generate a static page of a graphical user interface; receive a selection of a graphical object by a user at the graphical user interface to display a drawer page; generate the drawer page of the graphical user interface, the drawer page overlaid on at least a portion of the static page and comprising: a drawer bar that is interactable by the user to adjust a drawer page size of the drawer page and a static page size of the static page based on a position of the drawer bar; and display the static page and the drawer page of the graphical user interface, the drawer bar positioned at a default position based on historical data associated with the drawer bar, wherein the historical wherein the historical data associated with the drawer bar comprises data associated with user adjustments made by a plurality of users to a plurality of drawer bar positions using devices that are a device type that matches the device type associated with the user" when interpreted as a whole.
Bhumkar et al. (US 2008/0022229 A1, published on 01/24/2008) discloses a results page 10 with a list of search results displayed in a browser running on a user device, wherein the list of search results (i.e., resources of interest) provided by search engine is displayed as links 12a-12e to target web sites on the left side of results page 10, and "sponsored links" 14a-14f and 16a-16b to commercial sites are displayed on the top and ride side of the search results page 1 (Bhumkar, FIG. 1; ¶¶ [0003] and [0005]-[0007]). Bhumkar further discloses that the searcher has now positioned his/her cursor 18 near the hyperlink associated with the first, non-sponsored link result 12a; in response, a quick view 20 of the associated web site has been displayed superimposed over the search result page 10; and previewed links may change color to indicate those already viewed and/or the one currently being viewed; e.g., the preview page 50 being displayed when the user positions cursor 18 over sponsored link 52 (Bhumkar, FIG. 2; ¶¶ [0039] and [0051]). Bhumkar also discloses that (1) a preview window 54 displayed in response to a mouseover or other event is illustrated super positioned over a search result page which includes several links returned in response to a search query; (2) the preview window 54 includes a toolbar 56 with back icon 58, full-screen icon 60, share icon 62, close icon 64, and lock icon 66; (3) a stack tab 92 is arranged and shown on the right side of the page 90, which indicates that a stack of pages/URLS has been created; (4) when not being accessed, the drawer is hidden, and a tab denotes its location on the screen; (5) the drawer may be located on the right of the screen (by default), but may also be movable/adjustable at the user's control; and (6) a cursor control event associated with the tab (such as a mouse over, single click, double click or other event) may cause the drawer to open by sliding out (Bhumkar, FIGS. 5 and 10B; ¶¶ [0061]-[0066] and [0069]). Bhumkar further teaches that (1) the stack drawer 96 with several thumbnails 80, 100, etc., is shown on the right side of page 94, which includes a stack toolbar 102 providing several convenient ways for users to initiate several operations; and (2) the drawer itself may be revealed on screen (e.g., by sliding out from the edge of a browser window) along with its content(s) whenever a new page/URL is added to the stack and/or when the user positions a mouse cursor over the drawer tab, gesturing for the stack to slide out; the stack toolbar 102 is located at left side of the drawer 96 (Bhumkar, FIG. 10C; ¶ [0070]). Bhumkar also teaches that (1) share icon 62 initiates a communication interface (e.g., a message box) through which users can share contextual information with themselves or others (Bhumkar, FIG. 7; ¶ [0064]); (2) FIG. 9 displays the definition of the highlighted term "consist" in preview window 78 and displays thesaurus of the highlighted term "consist" in a message box/bubble (Bhumkar, FIG. 9; ¶ [0088]: FIG. 9); and (3) the stack toolbar 102 of the stack drawer 96 provides several convenient ways for users to initiate several operations; e.g., the function to close the current stack drawer 96 (Bhumkar, ¶¶ [0070]-[0071] and [0073])
Doyle et al. (US 2015/0088740 A1, published on 03/26/2015) discloses a system and a method relating to a user interface (Doyle, ¶ [0085]), wherein (1) web interface 200 display representative of three bank accounts 208,210, 212 200, wherein two of the accounts have one or more checks in various stages of processing (Doyle, FIG. 3D; ¶ [0086]); and (2) selection of the Deposit icon 366 can open a bank account selection window 511, which can be a separate window navigated to from the incoming payments window 356, or a pop-up window overlaying the incoming payments window 356, as illustrated in FIG. 28A (Doyle, FIGS. 19 and 28A; ¶ [0143]).
Reeves (US 2012/0084697 A1, published on 04/05/2012) discloses methods and apparatus for controlling the display of one or more drawers of a user interface (Reeves, ABSTARCT), wherein (1) the drawer may be opened by a user by manipulation of a graphical portion 502; e.g., a handle 506 or other graphical portion 502 may be provided to access the drawer; (2) a drawer may be operative to be opened into view on a display from the periphery of the display such that the rendered display resembles a drawer being opened from off display to reveal the contents of the drawer; (3) a user may access a drawer by dragging open the drawer by selecting the handle 506 or other graphical portion 502 that allows the drawer to open (that is, slide into view); (4) as such, a drawer may be opened to occupy a majority of a display or may be partially opened to only a partial extent that covers a portion of the display; (5) the first drawer portion 500 may be partially opened to only cover a portion of the first display 102; a first handle 506 may also be provided at the bottom of the first drawer portion 500; and the first status portion 502 may remain displayed at the top of the screen; i.e., a first drawer handle 506 that is interactable by the user to adjust a drawer page size of the drawer page 500 and a static page size of the static page 102 that is not covered by the drawer page 500 (Reeves, FIGS. 5A-B; ¶¶ [0066] and [0070]).
Everette et al. (US 11,099,731 B1, filed on 08/02/2016) discloses a system and a method relating to a graphical user interface (Everette, ABSTRACT), wherein (1) a user can tap and drag 406 "gesture sensitive element" 408 a second distance, a control panel 410 can be displayed; and (2) the user can cause control panel 410 to be hidden with a close gesture which may include a tap and drag down, or other close gesture (Everette, FIGS. 4A-B; Col. 4, line 58 – Col. 5, line 16). Everette further discloses that (1) changing the position of the gesture sensitive element by a user; (2) a gesture sensitive element 902 can be manually placed at one or more locations on the screen 904; and (3) a guide of snap points 906 and/or lines 908 may be displayed indicating locations where the gesture sensitive element 902 can be relocated so that when the user opens an app that includes gesture sensitive element 902, the element can be positioned based on one or more new locations chosen by the user (Everette, FIG. 9; Col. 7, line 46 – Col. 8, line 10). Everette also discloses that (1) adjusting the position of the "gesture sensitive element" based on usage; (2) based on the selection history, an average selection location can be determined; (3) if the average selection location is greater than the threshold distance from a center point of the display element, then an adjustment distance can be determined based on the distance between the average selection location and the display element center location; and (4) using the adjustment distance, subsequent renderings of the GUI can cause the display element to be displayed offset based on the adjustment distance (Everette, FIGS. 8A-C; FIG. 12; Col. 6, line 54 – Col. 7, line 45; Col. 11, lines 1-43). Everette further teaches that (1) depending on the size of screen 808, and the size of the user's hands, this default position may not be comfortable for all users; e.g., larger devices may typically be held with two hands, making the center of the screen more difficult to reach than the edges; (2) similarly, users with smaller hands may not comfortably reach the center of the screen; depending on the size of the device, different users may hold the device differently, meaning the default position may not be the most useful position for all users; and (3) "gesture sensitive element" can be automatically repositioned based on historical usage and screen size of the device (Everette, FIGS. 8A-C and 9; Col. 6, line54 – Col. 8, line 10)
Brown et al. (US 2013/0283168 A1, published on 10/24/2013) a system and a method relating user interaction with a computing device (Brown, ¶ [0009]), wherein (1) a user inter face (UI) 110 that includes content 112 from the service provider 106 and a conversation graphical user interface (GUI) 114 from a virtual-assistant service 116; (2) the content 112 of the site may include any sort of details or information associated with the service provider 106, while the conversation GUI 114 is provided to assist the user 102 in navigating the content 112 or in any other activity; (3) the conversation GUI 114 conveys a visual representation of a conversation between the user 102 and the virtual assistant 118; (4) the conversation GUI 114 presents a series of dialog representations 120 and 122, such as graphical content bubbles, which are designated to the user or the virtual assistant; and (5) the user-originated dialog representations 122 contain input from a user (verbal or otherwise) and the assistant originated dialog representations 120 contain responses from the virtual assistant; conversation GUI 114 also includes an interface area 124 that captures input from the user 102, including via typed input, audio or speech input, touch input and gesture input (Brown, FIGS. 1-2; ¶¶ [0071]-[0073] and [0081]-[0085]). Brown further discloses that (1) the user-originated dialog representations 122 contain input from a user (verbal or otherwise; (2) an interface area 124 that captures input from the user 102, including via typed input, audio or speech input, touch input and gesture input; and (3) in the case of verbal input, the computing device 104 may include a speech recognition engine 208 that receives the vocal audio data captured by a microphone (Brown, FIGS. 1-2; ¶¶ [0073] and [0084]-[0085]). Brown also discloses (1) virtual assistant embodies a human representative of the service provider that is displayed on a website; (2) virtual assistants thus act as an effective interface that allows users to seek information they desire while still allowing service providers to realize cost savings associated with providing information online rather than via a human representative; and (3) increasing the ability of these virtual assistants to emulate human representatives remains a priority (Brown, ¶¶ [0003]-[0004]).
ZUVERINK et al. (US 2016/0275582 A1, published on 09/22/2016) a system and a method relating to a user interface for customer interactions (ZUVERINK, ¶¶ [0010] and [0002]), wherein (1) the customer 104 may be presented with a clickable widget, such as widget 118, on the enterprise website; the widget 118 may be configured to initiate a chat interaction of the customer 104 with a live agent, such as a live agent 120 (ZUVERINK, FIG. 1; ¶¶ [0030]); (2) the customer may instead choose to chat with the virtual assistant by entering another question in the text entry section 308 (e.g., requesting assistance for choosing a best printer in free-form textual input 404) and submit the question by selecting the send option 310; the system 200, either directly or by causing a virtual agent to interact with the customer, by means of the interactive form, receive information regarding the customer's requirement (e.g., display a question 410 along with multiple answer options 412; display a next question 420 along with multiple answer options 422), till a live agent is available; and (3) in such a scenario, the reply provided to the customer may include a text entry 406 informing the customer of a subsequent involvement of a live agent (e.g., an indication 408 including text Agent John will join you in about two minute) in assisting the customer with the desired assistance (ZUVERINK, FIGS. 3F and 4A-C; ¶¶ [0078]-[0086]).
UCHIUMI (US 2021/0072884 A1, published on 03/11/2021) discloses that (1) determine whether an instruction to display the toolbox 30 is input from a user at step S10; (2) when it is determined that a display instruction is input at step S10, determine whether a predetermined number or more of movement (adjustment) data are accumulated for the corresponding user ID at step S12; (3) when it is determined that the movement (adjustment) data accumulated for the corresponding user ID in the movement (adjustment) history DB 22 are less than the predetermined number at step S12, displays the toolbox 30 at the basic display position 40 at step S14; and (4) when it is determined that the movement (adjustment) data accumulated for the corresponding user ID in the movement (adjustment) history DB 22 are equal to or more than the predetermined number at step S12, specify the changed display position based on the movement (adjustment) history DB 22 at step S16, and at step S20display the toolbox 30 at the changed display position 42 specified at step S16 (UCHIUMI, FIGS. 2-4 and 9; ¶¶ [0082]-[0088]).
Steinberg et al. (US 2013/0097498 A1, published on 04/18/2018) discloses as a system and a method for displaying an expanding (e.g. showable/hideable, or minimizable/maximizable) discovery drawer without obscuring the application work area (Steinberg, ¶ [0005]), and further discloses the specific states of the drawer's states can be used to render the drawer screen devices based on the user's last interaction (Steinberg, ¶ [0071]).
Bellare et al. (US 2015/0324068 A1, published on 11/12/2015) discloses a Geographic Information System (GIS) application comprising of a plurality of collapsible drawers, wherein (1) the drawers comprise of the tools, options and information related to the map being currently displayed; (2) the drawers may be collapsed/expanded by the user by clicking on a handle associated with each of the drawers so that the collapsed drawers enable the user access to maximum screen space to view more information on large maps; (3) FIG. 3a depicts the GIS application, with the north, west, south and east drawers 302a, 303a,304a and 305a in the expanded mode; (4) FIG. 3b depicts the GIS application with all the drawers collapsed, and the respective handles remain visible, with the user being able to expand the drawers by clicking on the respective handle; (5) FIG. 3c depicts the GIS application with only the south drawer 304a in expanded form, while the other; (6) FIG. 3d depicts the GIS application with two drawers, the north drawer 302a and the east drawer 305a in expanded form, while the west drawer 303a and the south drawer 304a are collapsed drawers are collapsed; and (7) FIG. 3e depicts GIS application when the north drawer is expanded (Bellare, ABSTARCT; FIGS. 3A-E; ¶¶ [0025]-[0026]).
Conrad et al. (US 2007/0106955A1, published on 05/10/2007) discloses a window management mechanism allows a user to open a window as a drawer or, perhaps more appropriately named, a pop-up window, wherein the drawer is an opened window that a user has dragged down to a drawer region at the bottom of the screen such that only the title bar or some drawer handle illustration is left showing (Conrad, ABSTRACT).
PERRY (US 2013/0061151 A1, published on 03/07/2013) discloses a system and a method for adapting displayed text or images and other user interface elements, to best suit the numerous sizes of display screens and types of input mechanisms associated with various devices (PERRY, ¶ [0002]), wherein (1) the mapping-repository in the server 16 maintains mapping of specific mobile device models to preferred UI variants best suited for each individual mobile device; (2) the mapping-repository is queried over the network 18 by means of querying application of the invention, to select the default UI-variant for that specific mobile device model (PERRY, FIG. 2; ¶ [0047]); (3) the preferences analysis engine analyzes cumulative data received from multiple mobile devices of the same type, and identifies the UI-variant that is preferred by most users for that type of mobile device; (4) the preferences analysis engine stores the identified preferences for specific mobile device models in the mapping repository; and (5) the UI variant that is identified as preferred by users of a specific mobile device model becomes the default UI-variant for other people using the same type of mobile device (PERRY, FIG. 3; ¶ [0048]). PERRY further discloses that (1) when a user manually selects a different UI variant, the mobile application of the invention, then forwards information about the user's new UI-variant preferences, along with device type identifier 36, to the preferences analysis engine 34, located in the remote server 16; (2) the preferences analysis engine 34 collects statistics about the preferences of users on different mobile device models, and identifies over time, for each mobile device model, a UI-variant that is preferred by the majority of users of that type of mobile device; (3) the preferences analysis engine 34 stores the identified preferences for specific mobile device models in the mapping repository 33 on the remote server 16, thereby making that information available to future queries by instances of the mobile application 30 of the invention running on mobile devices 31; and (4) as a result, the UI variant that is identified as preferred by most users of a specific mobile device model, will be used as the default UI variant 32 for other people using the same type of mobile device (PERRY, ¶¶ [0058]-[0060]).
Edecker et al. (US 2014/0280180 A1, published on 09/18/2014) discloses that (1) the initial state of the application disclosed herein is defined by initial states of all tools and the drawer; (2) more specifically, in this embodiment, the state of the drawer at any point in time is defined by its current content, that is, specific tools, which currently sit in the drawer; (3) the initial state tracked by the disclosed system is defined by the predefined set of tools that will be displayed in the drawer upon first application start up; (4) the more commonly-used tools are taken out of the drawer and made available to a user; (5) as a result of the default inclusion of common tools in the drawer, a first time user will be able to see the drawer inaction and become aware of its existence; (6) in particular, when the application starts with clean map, the system displays the drawer as automatically opening and further moves certain commonly-used tools out of and moved to their default locations on the map screen; (7) the disclosed system defines the initial states of specific tools by a set of predefined values stored in the disclosed system; (8) these predetermined or initial values can be updated depending upon a user's interaction with the system, and are some of the persistent properties described above; e.g., a particular tool may have a persistent property called "XY” that indicates the coordinates of the tool on the screen; (9) the persistent property has a default value that is used the first time the tool is taken out of the drawer; and (10) as the user moves the tool around the screen, the coordinates stored as the "XY value are updated to match the position on the screen, such that in a subsequent session, the tool is displayed in a new default position when it is taken out of the drawer (Edecker, ¶ [0128]). Edecker further discloses that (1) standard or default tool positions are computed at run time based on the current map window dimensions and tool size (diameter); and (2) tool size, in turn, depends on computer display horizontal resolution (provided that the display has landscape orientation, that is, horizontal resolution represents the bigger side of the display) (Edecker, ¶[0132]).
Van Hecke et al. (US 2019/0104216 A1, published on 04/04/2019) discloses that (1) FIG. 4 illustrates graphical user interface 200 shortly after receiving an input from the user to open a drawer 240; (2) as shown in FIG. 4, drawer 240 may be partly visible (e.g., because drawer 240 is partly opened); (3) the user may have selected icon 212 in FIG. 2 to open drawer 240; (4) the user may have swiped down on dock 230 to open drawer 240; (5) as can be seen in FIG. 4, drawer 240 may be connected to dock 230, and thus, as dock 230 moves down across the screen, drawer 240 may appear, trailing drawer 240; (6) FIG. 5 illustrates graphical user interface 200 with drawer 240 fully visible; (7) as shown in FIG. 5, drawer 240 may include an "EVERYTHING" section (which may include all available activities); (8) drawer 240 may also include a "RECENT' section (showing the four most recently selected activities); (9) as drawer 240 is showing, icon 212 from FIG. 2 may be replaced with an icon 410 (e.g., for closing drawer 240); (10) additionally or alternatively, the user may close drawer 240 by swiping upward on dock 230; (11) even though drawer 240 consumes the majority of the display area, some icons within drawer 240 may not be visible; (12) FIG. 6 illustrates graphical user interface 200 with drawer 240 partially scrolled; and (13) as shown in FIG. 6, dock 230 may remain visible at the bottom of the display area even as the contents of drawer 240 continue to scroll (e.g., allowing the user to scroll through drawer 240 without dock 230 disappearing) (Van Hecke, ¶¶ [0061]-[0067] with FIGS. 2-6)
However, closest arts of records, as discussed above, singly or in combination do not teach or suggest at least following features "generate a static page of a graphical user interface; receive a selection of a graphical object by a user at the graphical user interface to display a drawer page; generate the drawer page of the graphical user interface, the drawer page overlaid on at least a portion of the static page and comprising a drawer bar that is interactable by the user to adjust a drawer page size of the drawer page and a static page size of the static page based on a position of the drawer bar; and display the static page and the drawer page of the graphical user interface, the drawer bar positioned at a default position based on historical data associated with the drawer bar, wherein the historical data associated with the drawer bar comprises data associated with user adjustments made by a plurality of users to a plurality of drawer bar positions using devices that are a device type that matches the device type associated with the user" when combining with all other limitations of these claims as a whole
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HWEI-MIN LU whose telephone number is (313)446-4913. The examiner can normally be reached Mon - Fri: 9:00 AM - 6:00 PM EST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Mariela D. Reyes can be reached at (571) 270-1006. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/HWEI-MIN LU/Primary Examiner, Art Unit 2142