throbber
648
`
`t
`
`C}{
`
`pnie"r,rr*
`NUMBER
`
`-".
`
`SUBCLASS
`
`/(l -:z t"s -
`
`EXAMINER
`
`t:
`
`)L.Y
`
`.. , -l
`
`/!!.
`r .i lr.i,.
`
`"##
`i...i.it...:l-,l'ilr:.ir1i, .j. 1..,1 " l. !i.ii:,i.,
`
`SEEIAL NUMBEF
`
`.'.t":
`
`il',"ii'
`
`I
`
`.!il
`
`FILING DATE
`
`l..l l. J' .1. .! .,' :l'i:]
`
`.-i i...i fl 1.'1 i:j r...i lil ,, F: l.-.1..:l ii,l i::. I;l iil i..j t...i l'11 i:r ,
`i:] iYi :i l- i-'i ,, :i i:i i,r I l\l r.i; ,, T' ,)'i ,'
`
`rh...
`-.....
`ii::1iTi
`Flrl rli
`$i'i l;r,:.:l-{i:rii:,.i.... i::,
`
`i
`
`JArs
`
`,f ,t,r:..:i..:ri',i I .1. lill...l
`l.ji::i.i::{:i. i::: I I::: i.::
`
`:+: :+r :+: :+: :+: :+: :+: :+: :+: :+: :+: :l: :+: :+: :+: :r.: :i: :+: :i
`
`j.:,;.:i i-6-1 ''i,
`l"i_l:i. ti i,ll:il::,1 l1.l :t i:j r,_:i t:..:t...ii1,1 i'ti::r
`
`ii ' i .r .t -l::::;
`.,1 :L::j
`.1. i ,,i .: ,.{. j
`'r,.r /
`..i
`
`...r
`
`l..l .1. ./ .1. I_i -/ i i:1.
`
`Y€s*-ss
`
`i::: i i i::;, i::: i i:;i i!.1 ;::r i 1.. i i.l i.:,i I... .i. t.::: H:. l.,i i:i [:. l':i fi f::1 l1.i i li::. ].1 i:.i ::;:: ,,' :;;:: i.j ,/ ':i1 i::,
`
`Forolgn prlorlty clalmed E ,..
`35 USc lls condltlons met E ye"
`
`Verlfled and
`
`STATE OR
`COUNTBY
`
`SHEETS
`DHWGS.
`
`1:l
`
`FILING FEE
`RECEIVED
`
`ATTORNEY'S
`DOCKET NO.
`
`a....lll.i
`
`rlll
`
`I lll'l
`
`--
`
`I
`
`.r
`
`j
`
`i'
`
`*rfi{\
`
`( ^4 22fr*4^-?/t1:*
`
`Aoolications Examiner
`CLAIMS ALLOWED
`Total Claims
`Print Claim
`
`1
`
`DRAWING
`
`Figs. Drwg.
`/Ll
`
`Print Fig.
`
`frq ;
`
`25
`
`Sheets Drwg
`
`tl
`
`ISSUE
`BATCH
`NUMBER
`
`i:1i...i1..:i i
`tyil-1i..-'i .i
`
`t_:ii I .i t::tl..l r:.li:;: i.:ri:i.:l [:l_.: I
`,i. i...:r.-tlii I',lt-l
`-ii:itji.,:.:[ lili:;i i-:r:..iir!ril..i]-l:;ri Iiilt"t; i:ii_tiiii'il[:.l.'il"
`
`uJ
`
`FF
`
`PARTS OF APPLICATION
`FILED SEPARATELY
`
`NOTICE OF ALLOWANCE MAILED
`7/tr 1a-.
`
`Assistant Examiner
`
`f rl
`
`ISSUE FEE
`Amount Due
`
`$l l;fi& & Date Paid
`ln-lk-Clr
`
`Label
`Area
`
`Form PTO-436A
`(Rev. 8i92)
`
`PREPARED FOR ISSUE
`
`WARNING: The information disclosed herein may be restricted. Unauthorized disclosure may be prohibited
`by the United States Code Title 35, Sections 122, 181 and 368. Possession outside the U.S.
`Patent & Trademark Office is restricted to authorized employees and contractors only.
`
`(FACE)
`
`IPR2017-01828
`Ubisoft EX1004 Page 1
`
`

`

`ao(dE
`-ofa
`
`slk,'il a8zl,"lgt;
`
`PATENT DATE
`
`PATENT
`NUMBER
`
`CLASS
`
`SUBCLASS
`
`GROUP ART UNIT
`
`SERIAL NUMBER
`ftE,/ L7B,479
`
`FILING DATE
`{sL / Lr_t /94
`
`6s*
`*;${{f
`,tr-":,:jt (*
`{'
`;:
`tdtr[_LIAf4 J. JfiHI."lSr]H" f'L'ltdgft f,tr:rilFtt], TH; LAHRY lYl" LAiIHI4AN, IHVIFlli, TH; l-. . ,'' ,o v",..
`TJIICHAEL T:." *T,1iTH, IftVII,ILI" TH" .
`
`,e+rll:IF,iTIFJUIIqG ITATFI*;f:1.::*:-t(:l:;l:**:$+*:+:t:I::fi++:**'*:
`. UEFTIFIEIT
`
`FI]ftEIGFI FILIf'IG LIIEN5E fiRAf{TEf,' *2/T}4/94
`
`Foteign priority claimed
`35 USC ll9 conditions met
`
`.; lrlt--tFFfJHLr" FAIL5. Zt]EftL
`, f f 'f HIST SEVE]IITH, 5TE'
`I r[rF;T ]J{rftTH" TX 78,!.1':
`
`.SHEETS
`DRWGS.
`
`TOTAL
`CLAIMS
`
`L1
`
`24
`
`FILING FEE
`RECEIVED
`
`*{:-7'3{} r-r
`
`lJU'lY Ir::$l.l [q$-f IFIl:ATIifFl
`IYIUL-I' I 1'*5H I I{G TtrT'1FUTEft
`
`i.,T r]EJEf,T II{TERFA']E *T[ESE;IFILITY II,I
`EFMEfflilt4ENT
`. t, '
`U.S. DEPT. of COMM.-PaI. & TM Office'PTO'4361Gev. 10-78)
`
`,".. .-,. i
`
`PARTS OE APPLICATION
`FILED SEPARATELY
`
`NOTICE OF ALLOWANCE MAILED
`
`PREPARED FOR ISSUE
`
`WARNING: The information disclosed herein may be restricted. Unauthorized disclosure may be prohibited
`by the United States Code titte 5S, Sections 122, 181 and 368. Possession outside the U.S.
`Patent & Trademark Office is restricted to aulhorized employees and contractors only.
`
`Form PTO-436A
`(Bev. 8/92)
`
`(FACE)
`
`IPR2017-01828
`Ubisoft EX1004 Page 2
`
`

`

`APPROVED FOR LICENSE
`
`INITIALS
`
`.i:'Dai6 :
`Recdived,
`,or
`MaiEd
`..Pl-'r,',I
`
`r.'
`r..
`
`r\(}!
`, ..";
`
`r(")
`
`"trb
`
`t- to-94
`J "8-q5_
`(l/lov ll,rf ?'(
`8- 8- 75-
`/,'/? ,Trrtrr
`{)/-:-4 ,7, t ?Z f
`
`-
`
`lSMVetffil-
`
`ffi/l"is.t?L o
`
`ffiffi ffiffi ffiffim
`
`Date
`Entered
`or
`Counted
`
`CONTENTS
`
`3-4- q4
`
`Application
`
`papers.
`
`.,,) 4
`
`?-{ s.
`
`ta- t5
`
`_1 -At N
`
`o
`
`10.
`
`11.
`
`12.
`
`13.
`
`14.
`
`15.
`
`16.
`
`17.
`
`18.
`
`19.
`
`20.
`
`21.
`
`22.
`
`23.
`
`24.
`
`25.
`
`26.
`
`27.
`
`28.
`
`29.
`
`30.
`
`31.
`
`32.
`
`(FRONT)
`
`IPR2017-01828
`Ubisoft EX1004 Page 3
`
`

`

`'" '566149
`
`.1, i
`
`'''
`':&,
`"'*!fr'r''
`i
`.'a
`
`Date
`Entered
`or
`Counted
`
`33 ->s-f {
`
`'
`
`3-?s- ? y
`6
`/a"*a- f I
`to ^P6^ c N
`/)*rb- f I
`/3//
`
`1''
`
`PATENT APPLICATION
`
`nFpnovro FoR LtcENSE,
`
`INITIALS
`
`I iillil ilfl ltil] iltil illlt illil lltil fltlt ltil ilil
`08586 t4e,
`
`CONTENTS
`
`Date
`Received
`o(
`Mailbd-
`I:i ;r ;; *: i ir' r: ["i
`fri r', ,r
`f*r, rl ." * ,
`tJi-tr#i:i. _l;rji,f;
`-//,f(
`
`iuc r
`{r.'i
`
`u
`
`*
`
`3-'o'? { c
`
`t-6't{
`
`Hi/t''j
`
`t )*tr *, y
`
`(FRONT)
`
`.f,
`,{
`
`IPR2017-01828
`Ubisoft EX1004 Page 4
`
`

`

`SEARCHED
`
`Class
`
`Sub.
`
`Date
`
`Exmr.
`
`3q;
`3qi
`3qf
`36q
`1<t0
`--ed39f
`27)
`7 6Lt
`
`6_;,
`8oo
`ttq
`-fzl
`tt't/Fzt
`
`88
`
`6::o
`tr.
`
`2e:a
`
`Fbtn
`fr)t,l
`altrlv , ?.
`fe ! s, 1",
`ftbyt,
`6/ilq;
`E/L/q;
`Eh q;
`
`14!
`
`i tlfr
`-la
`
`1'/0.
`
`' vt3
`
`eb
`
`SEARCH NOTES I
`
`j DN/ s*
`'f/urfi-,r^
`L/'on
`
`t4/
`/'/6
`
`Lg5
`
`/L{)
`
`INTERFERENCE SEARCHED
`Sub.
`Date
`
`Class
`
`Exmr.
`
`(RTGHT OUTSIDE)
`
`IPR2017-01828
`Ubisoft EX1004 Page 5
`
`

`

`DATE
`/bs/ Eq
`1,fi)/z/
`A*/-4/
`u- q*'q t'
`
`Date
`
`O O s,"p'" rssue Srip nere o
`
`{;*
`
`POSITION
`
`CLASS!FIER
`
`EXAM!NER
`TYPIST
`VERIFIER
`CORPS CORR.
`SPEC. HAND
`FILE MAINT.
`DRAFTING
`
`ID NO.
`dr
`J+
`lr
`\\"rh t
`
`-r'1
`
`./'
`
`INDEX OF CLAIMS
`
`Claim
`(!
`.g
`o)
`
`EciI
`
`o 5
`
`1
`52
`53
`54
`55
`56
`57
`5B
`59
`60
`
`61
`62
`63
`64
`65
`66
`67
`68
`69
`70
`v1
`72
`73
`74
`75
`76
`77
`78
`79
`80
`
`81
`82
`83
`84
`85
`86
`87
`88
`89
`90
`
`91
`92
`93
`94
`95
`96
`97
`98
`99
`'t 00
`
`SYMBOLS
`J .......................'......... Reiected
`= ................................. Allowed
`- (Throuoh numberal) Cancelod
`+ ............,...........,..,..... Reskicted
`N ................................. Non-el0cted
`I .................................
`Interlerenco
`A ................................. Appeal
`0 ................................. 0bjected
`
`(LEFT TNSIDE)
`
`IPR2017-01828
`Ubisoft EX1004 Page 6
`
`

`

`BAR CODE LABEL
`
`r ililil illillilil illllllllllilll llllllllll lill lill
`
`U.S. PATENT APPLICATION
`
`SERIAL NUMBER
`
`o8fL79,479
`
`FILING DATE
`
`CLASS
`
`GROUP ART UNIT
`
`oL/Lo le4
`
`395
`
`2308
`
`Fi
`
`o-
`o-
`
`ryILLIAM J. JOHNSON, FLOWER MOUND, TX; LARRY M. LACHMAN, IRVING, TX;
`
`I MTcHAEL D. sMrrH, rRvrNc, Tx.
`
`* * coNT INU ING DATA* ?t rt * !k rt * * rr r? * * * * * * * * * * *
`VERIFIED
`
`* r, FoRE lGN/nCt eenr,IcAT IoNS * rr rr * * * * * * * * *
`VERIFIED
`
`FORETGN FTLTNG LTCENSE GRANTED O2/O4194
`
`JTATE OR
`]OUNTRY
`
`SHEETS
`DRAWING
`
`TX
`
`11
`
`IU IAL
`]LAIMS
`
`24
`
`NDEPENDENT
`]LAIMS
`
`FILING FEE
`RECEIVED
`
`ATTOBNEY DOCKET NO.
`
`2
`
`$798.00
`
`Dt4l77
`
`GEOFFREY A. MANTOOTH
`WOFFORD, FAILS, ZOBAL & MANTOOTH
`110 WEST SEVENTH, SIE. 500
`FORT WORTH, TX 76102
`
`BUOY ICON NOTITICATION OF OBJECT INTERFACE ACCESSIBILITY IN
`MULTITASKING COMPUTER ENVIRONMENT
`
`aat!
`ccoo
`
`E
`F
`
`This is to certifv that annexed hereto is a true copv from the records of the United States
`Patent and Trademark Office of the application Which is identified above.
`By authority of the
`COMMISSIONER OF PATENTS AND TRADEMABKS
`
`Date
`
`Certifying Officer
`
`IPR2017-01828
`Ubisoft EX1004 Page 7
`
`

`

`PATENT APPLrcArroN
`
`'ERTAL
`
`#'/1?S4?q
`
`U.S. DEPAX.I}IENT OF CO}O{ERCE
`PATENT AND TR.ADEMARK. OFTICE
`FEE RECORD SHEET
`
`D,?0346 ot /25/94 a8fi94?9
`
`09_0453 0t0 10,
`
`7?8.008H Dtt*17?
`
`PTO-1 5 56
`(s187)
`
`IPR2017-01828
`Ubisoft EX1004 Page 8
`
`

`

`L
`
`SPECIFICATION
`
`/
`
`Docket No. DA9-93'O27
`
`TO ALL WHOI{ IT MAY CONCERN:
`
`BE IT KNOWN that w€r Willian J. Johnson, Larry M.
`the United States,
`Lachman and Michael D. Snith of
`residing in the State of Texas, have invented new and
`useful improvements in a
`
`BUOY ICON NOTIFTCATION OT OBITECT INTERFACE ACCESSIBILITY
`IN I'{ULTITASKING COMPUTER ENVIRONI'{ENT
`
`of which the following is a specification:
`
`IPR2017-01828
`Ubisoft EX1004 Page 9
`
`

`

`o r/sr( trP
`
`Docket No. DA9-93-O27
`
`BUOY ICON NOTIFICATION OF
`IN !,IULTITASKING
`
`OB.TECT INTERFACE ACCESSIBILITY
`COMPUTER ENVIRONI,IENT
`
`ABSTRACT
`
`t-0
`
`l-5
`
`20
`
`25
`
`Noti.fication of an execut,ing object becoming idle is
`provided in a nultitasking environment. As the object
`executes, a user can interface with a second object.
`when the executinq object, becomes accessible, a buoy icon
`object is displayed on the computer screen. The buoy
`icon has the name of the accessible object as well as a
`line extending from the buoy icon to
`the
`pointer
`accessible object. The buoy icon provides notification
`that the accessible object executj,on is complete or is
`The user can either
`ready to receive a user input.
`remove the buoy icon from the screen or select the buoy
`icon object to focused the accessible object. The newly
`focused accessible object can then be used' The buoy
`icon notification can be enabled or disabled on an
`obj ect-by-obj ect basis.
`
`,J
`
`IPR2017-01828
`Ubisoft EX1004 Page 10
`
`

`

`{nAlI ;
`,w
`: Nolcx!F93-O27
`Docket
`qf,?li cal-'o'1,i" o. c'a,^li n'*{vn'f
`--flris
`\- \o -qV t rToo) *6*rlrN-ed-'
`BUOY ICON NOTIFTCATION OF OB'ECT INTERFACE ACCESSIBILITY
`rN I{ULTITASKING COMPUTER ENVIRONMENT
`
`fi
`
`5
`
`(
`
`q>q ,[trt
`
`oglDqr
`
`Technical field Of The Invention
`
`The present invention relates to methods and
`apparatusgs for notification of user input situations and
`execution terrninations in asynchronously executing tasks
`in multitasking computer environments.
`
`Background Of The Invention
`
`Multitasking computer environments altow users to
`run or execute plural objects (such as application
`programs) in an apparent sinultaneous manner. For
`example, a user can execute a spread sheet application, a
`graphics application and a phone application at the same
`time.
`
`Each object has a user interface displayed to a user
`on a computer screen. User interfaces for specific
`applications on a computer system present themselves on a
`computer screen as a window, a fuII screen session, an
`icon or plural combinations thereof. When a ful1 screen
`session object is selected, the user interface takes up
`the entire screen and may prornpt the user with a command
`line. When an object is displayed as a window, the
`takes up only a portion of the screen,
`window typically
`so that other objects maY be seen
`A user input is provided to an object through a
`focused window or fu}l. screen session. OnIy one object
`can be focused (or otherwise made accessible to a user)
`
`l-0
`
`L5
`
`20
`
`25
`
`30
`
`35
`
`IPR2017-01828
`Ubisoft EX1004 Page 11
`
`

`

`Docket No. DAg-g3-O27
`
`at any one time. If an object is not focused, it is not
`enabled for receiving a user input. Unfocused objects
`may or may not be obscured from the view of the user by
`the focused object. For example, if the focused object
`fuI1 screen session, then all
`is represented by a
`unfocused object,s are obscured from view. If the focused
`object is represented by a window that takes up only a
`portion of the screen, then some objects (represented as
`either windows or icons) are likely to be visible.
`The liuritation that only one object can be focused
`for receiving a user input at any given time presents a
`problem in multitasking computer environments. A user
`may start an application in one user interface and then
`go to another user interface to work with another
`application. The user must poIl the first application to
`determine when the first application either cornpletes or
`pronpts for a user input. Alternatively, the user can
`sinply sit at
`the screen, waiting for
`the first
`application to complete and prompt for a user input. For
`example, suppose a user begins the formatting of a
`diskette. To continue operations with the diskette, the
`user must wait for the formatting to be completed. While
`formatting, the user begins to use other applications.
`While using these other applications, a convenient nethod
`is needed to indicate the completion of the formatting of
`the diskette.
`rn general, a convenient method is needed to
`that either a specific
`indicate
`to
`the user
`asynchronously executing task is complete or that a
`pronpt for user input has been provided;
`
`Summary of The Invention
`
`to
`
`It is therefore an object of the present invention
`provide a method and apparatus for providing
`nr:*\
`.t\2- -
`
`t-0
`
`t-5
`
`20
`
`25
`
`30
`
`35
`
`IPR2017-01828
`Ubisoft EX1004 Page 12
`
`

`

`Docket No. DA9-93-O27
`
`to a user of an object prompt mode,
`notification
`regardless of the activity that the user is engaging in.
`is another object of the present invention to
`It
`provide a method and apparatus for providing notification
`to a user of termination of an asynchronously executing
`task.
`
`invention provides a method and
`The present
`apparatus for providing notification of availability of
`an object. on a multitasking computer. A first object is
`executed. While the first object is executing, a second
`object is enabled for receiving a user input on a user
`is then deternined when
`interface of the computer. It
`the first object becomes accessible. Becoming accessible
`for entering input to a
`implies either the availability
`task or session or the termination of an asynchronously
`object becomes
`first
`When the
`executing task.
`is provided on the user
`accessible, a notification
`interface.
`provides
`The present
`invention
`automatic
`to a user of when an object becomes
`notification
`accessible. Thus, a user can execute a first object on a
`computer. The user need not wait for the object to
`Instead, the user can turn t,o other
`finish executing.
`tasks, such as interfacing with the second object. While
`interfacing with the second object, the user need not
`return to the first object to check on the progress of
`its execut,ion. with the present invention, a buoy icon
`object is automatically displayed on the screen when the
`object becomes accessible or otherwise ceases
`first
`execution.
`the present
`In accordance with one aspect of
`invention, the determination of when the first object
`becomes accessible further includes the determination of
`when the first object provides a prompt for a user input.
`
`t-0
`
`L5
`
`20
`
`25
`
`30
`
`35
`
`q
`
`IPR2017-01828
`Ubisoft EX1004 Page 13
`
`

`

`Docket No. DA9-93-O27
`
`rn another aspect of the present invention, the
`determination of when the first object becomes accessibre
`further
`includes the determination of when an
`asynchronously executing task terninates.
`rn accordance with sti1l another aspect of the
`present invention, the provision of a notification on the
`user interface when th.e first, object becomes accessible
`further includes displaying a buoy icon on a screen. rn
`addition. to the buoy icon, a name of the first object can
`be disprayed in proxinity to the buoy icon. Arso, a rine
`or other visuar indicator between the buoy icon and the
`first object can be displayed on the screen.
`rn accordance with another aspect of the present
`invention, the computer contains plurar objects which
`incrude first and second objects. The present invention
`allows enabling the notification for serected ones of the
`fn still
`another aspect of the present
`obj ects.
`invention, the notification can be disabred for selected
`ones of said objects.
`'
`rn still another aspect of the present invention,
`the notification can be removed from the user interface
`after the notification has been displayed.
`rn stilI another aspect of the present invent,ion,
`after
`the notification has been disprayed, *!h"
`notification is serect^e-d. Then, the associated object is
`focused on the user interface, wherein user input can be
`provided to the newly focused object.
`rn still another aspect of the present invention,
`the computer includes a
`third bbject, and the
`notification is a first notification. The third object
`is executed. A deterrnination is made when the third
`object becomes accessible. A second notification is
`
`l-o
`
`15
`
`20
`
`25
`
`30
`
`\*-*4 -r/
`
`IPR2017-01828
`Ubisoft EX1004 Page 14
`
`

`

`Docket No. DA9-93-o27
`
`displayed on the user interface when the third object
`is removed
`becomes accessible. The second notification
`from the user interface while rnaintaining the first
`notification on the user interface.
`Alternatively,
`from the user
`instead of removing the second notification
`can be selected,
`the second notification
`interface,
`wherein the third object is focused on a user interface
`while maintaining the first notification on the user
`interface.
`
`Brief Description of The Drawings
`
`Fig. L is a schematic diagrarn of a data processing
`system on which the present invention can be practiced.
`Fig. 2 is a schematic view of a screen showing a
`desktop with a buoy icon of the present invention, in
`accordance with a preferred embodiment, displayed
`thereon.
`Fig. 3 is a schematic view of the screen and desktop
`.
`of Fig. 2r'shown after the buoy icon has been selected,
`wherein the object linked to the buoy icon has been
`focused.
`Fig. 4 is a schenatic view of a screen showing a
`fuIl screen session with a buoy icon displayed thereon.
`rig. 5 is a schematic view of a screen showing a
`desktop with a plurality of buoy icons displayed thereon.
`Figs. 6-LL are flow charts showing various methods.
`Fig. 6 shows the nethod for enabling buoy icon
`for an object. Fig. 7 shows the method for
`notification
`rig. 8 is the
`registering ald tracking active objects.
`method for displaying a buoy icon for an accessibled
`object,. Fig. 9 is the method for removing a buoy icon
`from the screen. Fig. L0 is the method for selecting a
`buoy icon and providing focus to its associated .obj ect.
`
`t0
`
`l-5
`
`20
`
`25
`
`30
`
`35
`
`IIp
`
`IPR2017-01828
`Ubisoft EX1004 Page 15
`
`

`

`Docket No. DA9-93-027
`
`for disabling buoy
`
`Fig. 11" is
`the
`rnethod
`notification
`for an object.
`Figs. L2-L4 are schematic views of tables utilized
`by the present invention. Fig. LZ is a table of those
`objects currently being executed. Fig. 13 is a table of
`those objects for which a buoy icon notification has been
`enabled. Fig. L4 is a table of those objects for which a
`buoy icon has been displayed.
`
`lcon
`
`Description of The Invention
`
`In F'ig. 1, there is shown a schematic diagram of a
`data processing system LL or computer, upon which the
`present invention can be practiced. The computer LL
`includes a user interface, which has a display screen L7
`and a keyboard 19. Other input devices may also be
`provided, such as a mouse 21, a touch screen and a
`microphone for voice input. Each computer 3-L may also be
`coupled to a printer 23 or other output device.
`The
`includes a hard disk drive and
`gomputer LL typically
`floppy disk drive storage devices.
`The computer 11 also has internal memory in the form
`of Random Access Memory (RAU). The RAM memory stores
`resource objects for execution and access by a Central
`Processing Unit (CPU) located within the computer. One
`the present
`the method of
`such resource object
`is
`invention shown by the flow charts.
`Another such
`resource object is an operating system. The computer 11
`utilizes an operating system that provides multitasking
`one such operating system is os/2, which
`capabilities.
`is available from IBM. (Both OS/2 and IBM are trademarks
`of International Business Machines Corporat,ion. )
`rn Fig. 2, there is shown a desktop display 25 on
`the screen L7. The desktop 25 contains plura1 icons
`representing plural objects. For example, there is a
`
`L0
`
`t-5
`
`20
`
`25
`
`30
`
`35
`
`IPR2017-01828
`Ubisoft EX1004 Page 16
`
`

`

`Docket No. DA9-93-027
`
`file cabinet icon 27 , a printer icon 29, a phone icon 3L,
`None of the objects represented by icons can
`etc.
`receive a user inputr dS they are not focused (or enabled
`to receive a user input). A focused object presents
`either a window 33 displayed in the foreground of the
`desktop (as shown in Fig. 2) or a full screen session 34
`displayed in fult on the screen (as shown in Fig. 4).
`In
`Pig. 2, the focused object 33 is named ttos/z windowrr and
`is enabled to receive user inputs. Thus, the user can
`type in data, use a mouse cursor or use some other input
`device to input data or other information to the nos/z
`windowtr object 33.
`the buoy icon notification of
`the
`To illustrate
`present invention, suppose that the user has enabled the
`present invention to provide notification of when the
`phone object 31 is available for user input.
`For
`the user had earlier
`example, suppose that
`been
`interacting with the phone object 31 before interacting
`with the tt}S/z window'r object 33. While interacting with
`the phone object 31 (through a focused window), the user
`reached a step where the phone object executed a task
`such as sending a fax transmission, causing the user to
`Instead of remaining with the phone object while
`wait.
`the user enabled the present invention and
`waiting,
`focused the ttos/z windowrt object 33. Thus, the user is
`able to accomplish some work with the object 33 while
`waiting for the phone object, 31 to execute.
`When the execution of the phone object 3L reaches a
`further
`required for
`is
`step where a user input
`execution, then the present invention causes a buoy icon
`in
`35 to be displayed on the desktop 25. Those skilled
`recognize various algorithms may be used to
`the art
`
`1_O
`
`l_5
`
`20
`
`25
`
`30
`
`IPR2017-01828
`Ubisoft EX1004 Page 17
`
`

`

`Docket No. DA9-93-O27
`
`determine a best placernent of the buoy icon without
`departing from the spirit and scope of the present
`invention. The preferred embodiment, of the buoy icon is
`analogous to a maritime buoy used as an aid to ship
`navigation. Just as a maritime buoy provides information
`that is useful for maritime navigation, the buoy icon 35
`of the present invention provides information that is
`useful for navigation among computer user interfaces.
`Those skilled in the art recognize that alternative buoy
`representations can be utilized without departing from
`the spirit and scope of the present invention. The buoy
`icon 35 indicates when a specified object is available
`for user input. Thus, the user need not, wait for an
`object to execute or switch back and forth between
`focused objects checking on the status of the object in
`interest.
`The preferred buoy icon 35 has a float 37, a mast 39
`and a flag 4L so as to resemble a maritime buoy. The
`buoy icon 35 specifies the associated object by either
`appearing with the object's name (such as rrPHoNEfr), or
`appearing with a line (or other visual indicator) 45
`connect,ing the buoy icon 35 to the object 31 or both (as
`shown in Fig. 2) .
`The user's attention will generally be drawn to the
`buoy icon upon the sudden appearance of the icon 35 on
`the desktop 25. However, other means for attracting the
`attention of the user could be utilized. For example,
`the buoy icon can beep (using a speaker in the computer),
`pulse to alternate between larger and smaller sizes,
`change colors, etc
`once the buoy icon appears, the user can pursue
`several alternatives. First, the user can ignore the
`buoy icon and continue utilizing the focused object 33.
`The appearance of the buoy icon does not change the input
`enabled status of the currently focused object.
`
`.1
`
`10
`
`L5
`
`20
`
`25
`
`30
`
`35
`
`IPR2017-01828
`Ubisoft EX1004 Page 18
`
`

`

`Docket No. DA9-93-027
`
`Second, the user can select the buoy icon, wherein
`the specified object associated with the buoy icon is
`imnediately focused. This is shown in Fig. 3, wherein
`the user has selected the buoy icon, and the window 32
`for the phone object 31 has focused. Thus, the phone
`The ttOS/2
`object is enabled to receive user input.
`windowtt object 33 is relegated to the background and is
`no longer enabled to receive user input. The buoy icon
`has disappeared from the screen in fig. 3.
`The third option available to the user is that' the
`user can dismiss the buoy j.con, causing the icon to
`disappear, while naintaining the status quo among the
`objects. Thus, the currently focused object (for example
`the tt}S/z windowrt object 33) remains focused, and the
`phone object 31 remains as an icon in the background.
`When a buoy icon is displayed, it generally appears
`is
`there
`focused object, unless
`the
`outside of
`insufficient space available. This is to minimize the
`possibility of creating a nuisance witfr the buoy icon
`popping up in the same area as the user is working. For
`example, in Fig. 4, a full screen session 34 is shown.
`The buoy icon 35A is displayed on the fu}I screen session
`34, as there is insufficient space for the buoy icon to
`In this
`be displayed off of the fuII screen session 34.
`situation, the buoy icon 35A is displayed near an edge of
`the screen L7 with prevention of overlaying displayed
`matter or with nininal prevention thereof.
`There may arise a situation where more than one
`In this situation, shown in
`object produces a buoy icon.
`Fig. 5, there are plural. buoy icons 35, 35A, and 35B
`displayed. A buoy icon is displayed for each object that
`is ready for a user input. When one buoy icon is
`selected, the others remain displayed until selected or
`removed
`
`5
`
`L0
`
`t5
`
`20
`
`25
`
`30
`
`35
`
`LO
`
`IPR2017-01828
`Ubisoft EX1004 Page 19
`
`

`

`Docket No. DA9-93-027
`
`Referring now to Figs. G-lL, the flow charts of the
`present invention will be described. In the flow charts,
`following graphical conventions are observed: a
`the
`rectangle is used to
`illustrate
`either a process,
`function or screen display, and a diamond is used to
`illustrate
`a decision.
`These conventions are well
`understood by programmers skilled
`in the art of user
`interfaces, and the flow charts are sufficient
`to enable
`a programmer skilled
`in the art to write code in any
`suitable computer progranming language, such as pASCAL or
`C for a computer such as the IBM personal System / 2
`(PS/2)
`family of computers which supports
`these
`(Personal System / 2 is a trademark of
`languages.
`fnternational Business Machines Corporation. )
`The flow charts will
`first be described generally,
`followed by a more specific discussion of the steps.
`In
`general, for a buoy icon to appear for an object, the
`object is enabled for buoy icon notification, and the
`status of the object changes from active to idle. A user
`6nables the buoy icon notification of
`the present
`invention on an object-by-object basis.
`Examples of
`idled objects include an object that has completed a
`specific asynchronously executing task and an object that
`has provided a prompt for user input. The flow chart of
`Fig. 6 illustrates
`the enablement method. When an object
`is enabled for buoy icon notification, a handle G8 of the
`object is placed into a Buoy Enabled Table, shown in Fig.
`13. When an object executes, the handle 69 of the object
`is placed into an Active Thread Table, shown in fig.
`t2.
`The flow chart of Fig. 7 illustrates
`this. When the
`active object becomes id1e, then the method illustrated
`by the flow chart of Fig. 8 is executed. The rnethod of
`fig. 8 determines if the idled object is in both the Buoy
`Enabled Table of Fig. L3 and the Active Thread Table of
`fig. L2. ff so, then a buoy icon for the idled object is
`
`,T\
`
`IPR2017-01828
`Ubisoft EX1004 Page 20
`
`

`

`Docket No. DA9-93-O27
`
`displayed as shown in Fig. 2. The handle 68 for the
`object is placed into the Buoy Presence Table of Fig. 14.
`the buoy icon has been displayed on the
`After
`screen, the method illustrated by the flow chart of Fig.
`g allows a user to remove the buoy icon from the screen.
`The method illustrated by the flow chart of rig. L0
`allows a user,to focus the object specified by the buoy
`the Buoy Presence
`icon. The method of Fig. 10 utilizes
`Table of Fig. L4.
`The nethod illustrated by the flow chart of Ftig. LL
`for
`allows a user to disable the buoy icon notification
`an object.
`Referring now to Fig. 6, the method for enabling the
`for an object will be discussed.
`buoy icon notification
`The user focuses the object of interest, wherein the
`object is brought into focus. For example, referring to
`rig. 2, the user focuses the phone icon 31 using the
`mouse cursor, keyboard or other input device. The object
`may be focused either as a window or as a ful} screen
`focused, then the user
`Session. Once the object is
`executes the method of rig. 6, starting at step 51. The
`method is executed, for example, with a keyboard
`invocation seqluence, a voice command, a pull down menu on
`After step 51, the method
`the object, window, etc.
`the object in the Buoy
`provides an entry 11 70 for
`Enabled Table of Fig. 13. Each entry F1 7o of the Buoy
`Enabled Table has two parameters or fields, namely a
`handle 68 and an object tyPe 69. The values of the two
`parameters depend on whether the object is a full screen
`session or a window. Therefore, in step 53 of Fig. 6,
`the object is a fuII screen
`the method deternines if
`session. This is deternined from the title bar text and
`If
`class (or some other unique attribute) of the object.
`the result of st,ep 53 is YES, then in step 55, the Buoy
`Enabled Table entry handle 68 is set to the reference of
`
`l_0
`
`15
`
`20
`
`25
`
`30
`
`35
`
`t" )
`t---_
`11- '
`
`IPR2017-01828
`Ubisoft EX1004 Page 21
`
`

`

`Docket No. DA9-93-O27
`
`the screen session group associated with the object. The
`screen session group is a set of resources (such as
`peripherals) attached to a session and is a unigue
`reference for identifying the particular full
`screen
`session. fn step 57, the Buoy Enabled Table object type
`69 is set to fuII screen session. The object type may be
`a constant which is representative of a full screen
`session. After step 57, the method proceeds to step 63.
`If the result of step 53 is NO, then the object has
`a window (or panel) for a user interface, and the method
`proceeds to step 59. In step 59, the Buoy Enabled Table
`entry handle 68 is set to the title bar text and
`classification pain of the window. The title bar text
`and classification as a pair is a unique identifier of
`the particular object window. Various embodiments may
`information as
`utilize
`other unigue identifying
`appropriate to the computer system. In step 6L, the Buoy
`Enabled Table entry object type 69 is set, to panel (or
`window). The object type nay be a constant that is
`ditterent from the fulI screen session constant. After
`step 6L, the method proceeds to step 63.
`In step 63, the method deternines if the entry is
`If the
`already in the Buoy Enabled Table of Fig. 13.
`result of step 63 is No, then in step 65, the entry is
`placed into the Buoy Enabled Table. The method then
`stops, step 67. If the result of step 63 is YES, then
`step 55 is blpassed, and the nethod proceeds directly to
`step 67 to stop. Thus, the presence of an entry in the
`Buoy Enabled Table (Fig. 13) inplies the user reguested
`buoy icon notification.
`Referring now to Fig. 7, the nethod for registering
`an executing object will be discussed. Information on an
`executing object is placed in the Active Thread Tab1e of
`Fig. L2. The Active Thread Table provides a correlation
`between buoy icon notification information and executing
`
`Lo
`
`t_5
`
`20
`
`25
`
`30
`
`35
`
`[},
`L2 | '--'
`
`IPR2017-01828
`Ubisoft EX1004 Page 22
`
`

`

`Docket No. DA9-93-O27
`
`object inforrnation. The method of Fig. 7 is executed
`when an object is executed, step 7L. The object is
`executed when a thread (which is a flow of execution in a
`multitasking computer) of the object executes as a result
`of a user input in the user interface for the object.
`For example, the user could press the ENTER key to cause
`the object to execute. After step 7L, the nethod
`provides an entry E1 72 for the object in the Active
`Thread Table of Fig. L2. Each entry E1 72 of the Active
`Thread Tab}e has the following parameters or fields:
`a
`handle 68, an object type 69, a process identification 87
`(PID) and a thread identification 89 (TID). The values
`for the handle and the object type depend on whether the
`object is a fu1l screen session or a window as heretofore
`described. Therefore, in step 73 of fig. 7, the method
`If
`the object is a fu}I screen session.
`determines if
`the result of step 73 is YES, then the method proceeds to
`In step 75, the Active Thread Table entry
`step 75.
`handle 68 is set to the session screen group associated
`in step 55 of F.ig. 6.
`with the object, much like
`Thereafter, in step 77, the Active Thread Table entry
`object type 69 is set to fuII screen session, much like
`in step 57 of Fig. 6. After step 7'1, the method proceeds
`to step 83.
`the result of step 73 is No, then the object
`If
`being executed has a window for a user interface, and the
`In step 79, the active
`method proceeds to step 79.
`Thread Table entry handle 68 is set to the title bar text
`in step 59 of Fig. 6.
`and classification pair,
`like
`Thereafter, in step 81, the Active Thread Table entry
`object type 69 is set to panel, Iike in step 6L of Fig.
`6. After step 8J., the nethod proceeds to step 83.
`In step 83, the rnethod sets the PID field 87 and TID
`
`L0
`
`l-5
`
`20
`
`25
`
`30
`
`35
`
`,r\q
`
`IPR2017-01828
`Ubisoft EX1004 Page 23
`
`

`

`Docket No. DA9-93-027
`
`field 89 of the Active Thread Entry. The PfD and the TID
`are unigue handles assigned to an object during the
`execution of the object by the computer operating system.
`The PfD and the TID are obtained from the operating
`system. Thereafter, in step 85, the method stops.
`Referring now to Fig. 8, the method of displaying
`I
`the buoy icon will be discussed. The rnethod of rig.
`executes whenever a thread in the computer system becomes
`fn one type of operating
`idle or .blocked, step 9L.
`system (nanely oS/2), a thread is blocked when it
`is no
`longer able t

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket