throbber
a2) United States Patent
`US 6,590,568 B1
`(10) Patent No.:
`
` Astala et al. (45) Date of Patent: Jul. 8, 2003
`
`
`US006590568B1
`
`8/2002 Jones et al. 370/313
`8/2002 Moonet al. cece 345/777
`
`6,430,164 B1 *
`6,433,801 B1 *
`cited by examiner
`Primary Examiner—Steven Saras
`Assistant Examiner—Michael J Moyer
`(74) Alttorney, Agent, or Firm—Antonelli, Terry, Stout &
`Kraus, LLP
`(57)
`
`ABSTRACT
`
`Amethod of and apparatus for dragging and dropping items
`displayed on a touch screen. In one embodiment, the item on
`the touch screen is touched with a pressure greater than a
`first predetermined pressure for a first predetermined period
`em"draggedwiththeredhcedpressieeto4 second
`location at which the touch screen is touched with a pressure
`greater than a second predetermined pressure for a time
`duration greater than a second predetermined time period. In
`another embodiment, the item on the touch screen is touched
`with a pressure greater than a predetermined pressure for a
`first predetermined period of time, and then the touch screen
`is touched at a second location with a pressure greater than
`the predetermined pressure for a second predetermined
`period of time, less than the first predetermined period of
`time
`:
`
`24 Claims, 7 Drawing Sheets
`
`(75)
`
`(54) TOUCH SCREEN DRAG AND DROP INPUT
`TECHNIQUE
`Inventors: Arto Astala, Vantaa (FI); Tapio
`Mansikkaniemi, Espoo(FT)
`:
`:
`:
`.
`(73) Assignee: Nokia Corporation, Espoo (FI)
`(*) Notice:
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`US.C. 154(b) by 200 days.
`
`(21) Appl. No.: 09/714,939
`;
`Filed:
`Noy. 20, 2000
`(22)
`Inte C1? neers GO9G 5/00; GO9G 5/08
`(51)
`(52) US. Che oerreeereerrees 345/173; 345/6RRO'
`:
`,
`(58) Field of Search 0.0.0.0...ecco 345/156-179,
`345/799, 856-857
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`Logan et al... 345/173
`Boie et al.
`.....
`. 345/174
`Toda et al.
`....
`... 345/173
`Bisset et al. we. 345/173
`Gillespie et al.
`......... 178/18.01
`
`
`
`7/1994
`10/1995
`9/1997
`10/1998
`3/1999
`
`*t***
`
`5,327,161 A
`5,463,388 A
`5,673,066 A
`5,825,352 A
`5,880,411 A
`
`
`BA
`732
`
`
`
`
`
`
`
`
`a,
`
`FLED
`
`728
`
`730a DIRT
`DIR2
`
`DIR 3
`DIR 4
`FILES
`ALES
`
`DIR3
`
`
`2136
`
`
`
`
`730
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(Ot
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`<- ~“DIR2|FETPIRT FILE2
`
`
`
`DIRS
`DIR 4
`FILES
`FILE 4
`728
`
`DIR3
`
`
`ra
`
`
`FILES
`FILE 4
`728
`
`DIR 3
`
`
`
`
`
`
`Valve Exhibit 1005
`Valve Exhibit 1005
`Valve v. Immersion
`Valve v. Immersion
`
`

`

`U.S. Patent
`
`Jul. 8, 2003
`
`Sheet 1 of 7
`
`US6,590,568 B1
`
`42
`
`40ay
`D|_}*
`
`AP
`
`34
`
`
`
`BUS.OWNER
`
`36
`
`38
`
`22
`
`|F+_|Co
`
`2
`3
`
`MDASERVER
`30b a
`bo}LH/30c
`FIG.1
`
`30a
`
`20a
`
`20b
`
`4
`
`28
`
`

`

`U.S. Patent
`
`Jul. 8, 2003
`
`Sheet 2 of 7
`
`US6,590,568 B1
`
`
`
`

`

`U.S. Patent
`
`Jul. 8, 2003
`
`Sheet 3 of 7
`
`US 6,590,568 B1
`
`
`
`

`

`U.S. Patent
`
`Jul. 8, 2003
`
`Sheet 4 of 7
`
`US 6,590,568 B1
`
`FIG. 4
`
`400
`
`ts
`
`402
`
` TEMINAL
`
`POWER
`ON?
`
`
`
`
`NO COMMUNIC.
`
`NO
`
`LINK ESTAB.
`
`YES
`
`ESTABLISH A COMM.
`LINK WITH ACCESS
`POINT
`
`406
`
`426
`
`END
`
`GLOBAL ADDRESS SERVER NO
`
`GET INTERNET
`ADDRESS OF MDA
`SERVER FROM THE
`
`
`
`
`
`TERMINALANGESTAB
`TERMINAL
`
`
`
`POWER STILL
`FAMILY SESSION WITH
`ONS
`
`
`
`
`
`
`
`#10
`
`TERMINATE]
`PRIVATE
`SESSION
`
`422
`
`414
`
`USER
`
`REQUESTS A
`ACTIVE AND USER
`CAN CONTINUE TO
`RETRIEVE FAMILY
`LEVEL INFO.
`
`MDA SERVER
`FAMILY SESSION
`
`
`
`AUTHORIZED USER LOGS|416
`INTO START PRIVATE
`
`
`USER
`SESSION
`
`REQUESTS
`
`NO
`
`TERMINATION
`
`OF PRIVATE
`
`
`SESSION
`
`
`
`
`RETRIEVE PRIVATE
`INFO. & SERVICES
`
`418
`
`

`

`U.S. Patent
`
`Jul. 8, 2003
`
`Sheet 5 of 7
`
`US 6,590,568 B1
`
`FIG.S
`
`500
`
`ESTABLISH COMMUNICATION LINK
`WITH ACCESS POINT
`
`OBTAIN RELATED INTERNET
`ADDRESS FOR THE TERMINAL
`BASED ON CONNECTION W/ ACCESSPT.
`
`ESTABLISH COMMUNICATION LINK
`WITH ISP
`
`RETRIEVE INTERNET ADDRESS
`OF GLOBAL ADD. SERVER
`
`SEND REQUEST TO GLOBAL ADD.
`SERVER
`
`OBTAIN ADDRESS OF THE MDA
`SERVER FROM GLOB. ADD. SERV.
`
`TERMINAL SENDSITS ID
`TO THE MDA SERVER FOR
`AUTHENTICATION
`
`MDA SERVER AUTHENTICATES
`TERMINAL FOR FAMILY LEVEL
`
`FAMILY SESSION STARTS
`
`902
`
`504
`
`906
`
`508
`
`910
`
`o12
`
`514
`
`516
`
`518
`
`

`

`U.S. Patent
`
`Jul. 8, 2003
`
`Sheet 6 of 7
`
`US 6,590,568 B1
`
`FIG. 6a
`
`INPUT
`
`DETECT
`TOUCH
`
`START
`TIMER
`
`702
`
`704
`
` READ
`
`
`
`XYZ
`coorpINATes|/°
`708
`
`Zi > ZA
`Z2-Z1>Az
`DESTINATION
`INPUT
`
`READ
`X, Y,Z
`COORDINATES
`
`718
`
`DETERMINE
`OBJECT
`
`720
`
`MOVEOBJECT
`
`722
`
`724
`
`DETERMINE
`OBJECT
`
`DETECT
`ty >tA
`
`DETECT
`ty-ty>At
`
`772
`
`FOLLOW
`DRAG
`z>7ZB
`
`DETECT
`TOUCH
`
`716
`
`

`

`U.S. Patent
`
`Jul. 8, 2003
`
`Sheet 7 of 7
`
`US 6,590,568 B1
`
`FIG. 6b
`
`
`
` FILE4
`FILE3
`DIR 3
`
`DIR1
`
`DIR2
`
`FILE 2
`
`DIR3
`
`DIR4
`
`FILE1
`
`FILE2
`
`DIR3
`
`DIR4
`
`FILE4
`FILES.
`DIR 3
`
`FIG. 6d
`
`DIR 1
`
`DIR 2
`
`
`
`DIR 3
`
`DIR 4
`
` FILE4
`FILE3
`DIR 3
`
`

`

`US 6,590,568 B1
`
`1
`TOUCH SCREEN DRAG AND DROP INPUT
`TECHNIQUE
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`The present application is related to U.S. application Ser.
`No. 09/609,581, filed in the U.S. Patent and Trademark
`Office on Jun. 20, 2000; U.S. application Ser. Nos. 09/607,
`637 and 09/607,638, both filed in the U.S. Patent and
`Trademark Office on Jun. 30, 2000; and U.S. application Ser.
`No. 09/659,416, filed in the U.S. Patent and Trademark
`Office on Sep. 11, 2000, the content of these applications
`being incorporated by reference herein in their entirety.
`Furthermore, priority is claimed under 35 U.S.C. ’120 for
`the aforecited U.S. application Ser. No. 09/607,638.
`BACKGROUND OF THE INVENTION
`
`The present invention relates to electronic devices and
`more particularly to a touch screen input
`technique for
`allowing a user input to an electronic device having a touch
`screen.
`
`Advances in technology have resulted in smaller and
`more sophisticated electronic devices becoming available.
`These devices, such as portable communication devices,
`allow a user wireless access to communication networks,
`thereby enabling both Internet access and two-way e-mail
`communication.
`As the size of these communication devices decreases and
`as the numberof functions increases, it has become increas-
`ingly important for a user to be able to enter commands and
`information into the communication device in an efficient
`manner. With a reduction in size of the device, a keypad
`input device mustalso be reduced in size, thereby decreasing
`the efficiency with which information can be inputted by
`reducing the numberandsize of the keys. Furthermore, with
`a reduction in size of the device, the display size must also
`be reduced. Still furthermore, the use of a mouse with such
`devicesis usually not possible since a mouse requiresa flat
`clean surface to be properly used.
`The use of a touch screen input device that serves both as
`a display and as an input device for the communication
`device allows a larger display in that a large keypad is no
`longer required since manyof the functions have been taken
`over by the use of the display screen as an input device. A
`user enters information and data by touching the display
`screen at specific points.
`US. Pat. No. 4,700,022 to Salvadoretal. is directed to a
`method an apparatus for determining the coordinates of a
`contact point on a resistive type semi-analog sensitive
`surface. The coordinates are of a zone of contact of a
`
`conductive object, such as a finger, on a sensitive surface
`consisting of an insulating support having a grate formed by
`two terminals between which a certain number of emitting
`resistant strips arc connected in parallel and having detecting
`conductive strips placed between the resistant strips. This
`patent merely discloses one of many techniques for deter-
`mining the location of the zone of contact on a touch
`sensitive screen.
`
`is directed to a
`US. Pat. No. 5,119,079 to Hube et al.
`touch screen user interface with expanding touch locations
`for a reprographic machine. The interface allows the expan-
`sion of the area for selection on the touch screen so as to
`
`improve the accuracy of sclection thercof.
`US. Pat. No. 5,545,857 to Lee et al. is directed to a
`remote control device having a touch screen allowing user
`input via the touch screen.
`
`10
`
`15
`
`30
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`While eachof the three above-noted patents discloses the
`use of a touch screen for inputting purposes, none of these
`patents teaches or suggests a touch screen arrangement in
`which both the location and the time duration and/or pres-
`sure and/or velocity of a finger or other object contacting the
`touch screen are detected, the detected values being quan-
`tized so as to allow the dragging and dropping of an item
`displayed on the touch screen,
`SUMMARYOF THE INVENTION
`
`An object of the present invention is to provide a touch
`screen technique for an electronic device, for example,
`which allows such electronic device to have a reasonably
`large display screen in a compact configuration. The keypad
`of the device or substantial portions of the keypad of the
`device are deleted and their functions implemented by the
`touch screen displayscreen, thereby allowing more space to
`be utilized for the display screen.
`Another object of the present invention is to provide a
`touch screen technique for an electronic device in which the
`location and the time duration of an object, such as a finger
`or stylus or other pointed object, contacting or pressing a
`detection point on the touch screen, are detected. In addition,
`the pressure of the object on the touch screen may be
`detected as well as the velocity of the object as it is moved
`across the face of the touch screen. The detected time
`
`duration may be quantized into one of two or more values,
`each value corresponding to a specific input state. The
`interpretation of the contact detection may be dependent on
`the application and/or program phaseactive in the electronic
`device. For example, pressing a selection point for a first
`predetermined time period may correspond to single click-
`ing the left button on a mouse. On the other hand, pressing
`a selection point for a second predetermined period of ume
`whichis longer than the first predetermined period of time
`may correspond to double-clicking the left button on a
`mouse. Thus, when a touch input is effected by pressing a
`selected first
`item displayed on the touch screen for a
`predetermined period of time and then dragging the object or
`finger along the face of the touch screen to a second item
`displayed on the touch screen while pressing the screen with
`a lighter pressure than the initial pressing onthe selected first
`item and then pressing on the second item displayed on the
`touch screen for a third predetermined period of time may
`result in moving the selected item to the location of the
`second item,that is, dragging and droppingthe selected first
`item on the second item.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The foregoing and a better understanding of the present
`invention will become apparent from the following detailed
`description of example embodiments and the claims when
`read in connection with the accompanying drawings, all
`forming a part of the disclosure of this invention. While the
`foregoing and following written and illustrated disclosure
`focuses on disclosing example embodiments of the
`invention, it should be understood that the same is by way
`of illustration and example only and the invention is not
`limited thereto. The spirit and scope of the present invention
`are limited only by the terms of the appended claims.
`The following represents brief descriptions of the
`drawings, wherein:
`FIG. 1 is a block diagram of an example communication
`network having mobile terminals that are capable of com-
`municating with a mobile display appliance (MDA) system
`having an MDAserver with related services;
`
`

`

`US 6,590,568 B1
`
`3
`FIG. 2 is a block diagram of the MDA server of the MDA
`system of the network of FIG. 1;
`FIG. 3 is a block diagram of an example of a mobile
`terminal that may opcrate with the MDAsystem ofFIG. 1;
`FIG. 4 is a flowchart of a process for establishing a family
`session and a private session between the mobile terminal of
`FIG. 3 and the MDAserver of FIG. 1;
`FIG. 5 is a flowchart of a process for establishing a
`communication link between the mobile terminal of FIG. 3
`and the MDAserver; and
`FIGS. 6a—-6d are illustrations of a technique utilizing
`touch screen inputs for dragging and dropping objects
`displayed on the touch screen according to an embodiment
`of the present invention.
`DETAILED DESCRIPTION
`
`Before beginning a detailed description of the subject
`invention, mention of the following is in order. When
`appropriate, like reference numerals and characters may be
`used to designate identical, corresponding, or similar com-
`ponents in differing drawing figures. Furthermore, in the
`detailed description to follow, example sizes/models/values/
`ranges maybe given, although the present invention is not
`limited thereto. Still furthermore, any clock signals and
`timing signals that are set forth are exemplary, andcritical
`time values are mentioned whenappropriate. As a final note,
`well-known components have not been shown within the
`drawing figures for simplicity of illustration and discussion
`and so as not to obscure the present invention.
`FIG. 1 is a block diagram of an example communication
`network having mobile terminals that are capable of com-
`municating with a mobile display appliance (MDA) system
`having an MDAserver with related services. Network 10
`includes terminals 20a—20c, each coupled over a wireless
`interface to an access point 22, for communicating with the
`network and transmitting and retrieving information for a
`user. More specifically, the access point 22 is coupled to an
`Internet Service Provider (ISP) 24, which is coupled to the
`Internet 26. Accordingly, the access point 22 has an Internet
`address relative to the Internet address of the ISP 24.
`Additionally, the ISP 24 is coupled to a Mobile Display
`Appliance (MDA)server28 that provides the users, through
`terminals 20a—20c, with specific services and features,
`which will be discussed herein.
`
`Terminals 20a—20c each includes a user input and output
`device for allowing a user to access services of the MDA
`server 28. The MDAserver 28 provides services, such as
`e-mail, calendar, notes, ability to shop on line, and necessary
`authentication, as well as third-party services and informa-
`tion.
`
`Terminals 20a, 20b, and 20c are coupled to the access
`point 22 via wireless connections 30a, 30b, and 30c, respec-
`tively; hence, the user has portable or mobile access to the
`Internet 26 and the services provided by the MDA server28.
`Morespecifically, terminals 20a—20c may be coupled to the
`access point 22 using a Wireless Local-Area-Network Gate-
`way (WLAN GW)that is installed at a specific location,
`such as the user’s premises or location. Although terminals
`20a—20c are shown as being coupled to the MDAserver 28
`through the ISP 24, the present invention, as set forth in the
`claims, is not limited thereby. ['urthermore, in the illustrated
`network of FIG. 1, the ISP 24 is not acting as the MDA
`server 28 and vice versa, even though this is possible. For
`cxample, terminals 20a—20c may be coupled directly to the
`MDAserver 28 through the access point 22.
`Additionally, even though the access point 22 is shown as
`being coupled to the ISP 24 through a landline 32,
`the
`
`10
`
`15
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`present invention as set forth in the claims is not limited
`thereby. For example, the access point 22 can be wirelessly
`coupled to the ISP 24. Thus, the terminal 20 accesses the ISP
`24 through the access point 22, and thus the user can access,
`navigate through, and retrieve information fromthe Internet
`26 using the terminal 20.
`In order for a terminal, such as terminals 20a—20c, to have
`access to the services of the MDA server 28, the MDAscrver
`28 must authenticate and authorize each terminal’s access.
`
`Although only the authentication and authorization steps
`relating to each terminal 20a—20care discussedin detail, the
`teachings set forth herein are also applicable to otherter-
`minals. Upon proper authentication of each terminal
`20a—20c, the user can accessthe services of the MDA server
`28 at the authorized level of authentication.
`
`There are two levels of authentication that provide access
`to the services and information of the MDA server:
`the
`
`family level and the private level. The family level is a level
`of authentication that occurs based on the identity of each of
`the terminals 20a—20c in order to initiate a family session.
`In order to create a family, at least one terminal is needed,
`but typically there are several terminals that make up a
`family, and each terminal has a unique identity that allows
`the terminal access to a [amily session at the family level.
`Thus, for example, anyone having access to terminal 20a
`could have access to the family level
`information. The
`family level authentication may be based on the identity of
`the hardware of the terminal 20a, and the authentication may
`automatically occur when the unit is powered on. Even
`though the authentication at the family level may automati-
`cally occur, the present invention, as set forth in the claims,
`is not limited thereby. For example, the terminal 20a could
`request input from the uscr in order to initiate the family
`level authentication process. Once the terminal 20a is autho-
`rized to access the services, then each user is able to access
`information and services that are available to all other users
`
`in the family as well asto initiate a private session to access
`private information and services available only to that user.
`Unlike the family session at the family level, the level of
`authentication for a private session at
`the private level
`requires input from the user ta allow the user of a terminal,
`such as, for example, terminal 20a, acccss to information
`intended only for that user. For example, the user could use
`anyterminal that is within the user’s family and then initiate
`a private session to access information and services specific
`to that user. The authentication can be done using anything
`that
`is unique and only known bythat user, such as a
`password. Thus, the user can have a private session with a
`secured level of privacy of information and/or services
`unique to that user, regardless of which terminal is being
`used. However,as indicated above, anyone having access to
`the terminal 20a would have access to the family level
`information and services, because it is assumed for exem-
`plary purposes that authentication is based on the hardware
`of the terminal 20@ and occurs automatically, and a family
`session is always active whenthe terminalis on. This allows
`anyone, even an unauthorized user, to access the family level
`services and to perform tasks, and access the Internet
`through the ISP 24 coupled to the access point 22.
`In addition to the ISP 24, the access point 22 is also
`coupled to a business owner 34. The business owner 34
`includes a global address server 36 and a global upgrade
`server 38. The Internet address of the global address server
`36 may be permanently contained in the memories of the
`terminals 20. The global address server 36 is a place from
`whichall the terminals, such as terminals 20a, 20b, and 20c,
`can fetch the Internet address of their respective MDA
`
`

`

`US 6,590,568 B1
`
`5
`server. The advantage of having each terminal 20a—20cstore
`the Internet address of the global address server 36 is thatif
`terminals 20a—20c were relocated near another access point,
`then terminals 20a—20c canstill obtain the Internet address
`location of the MDA server 28 simply by knowing the
`Internet address of the global address server 36. However,
`the invention as set forth in the claimsis not limited thereby.
`For example, the Internet address of the MDA server 28
`could be stored on terminals 20a—20c, and the memories of
`terminals 20a—20c could be updated as needed.
`The user profile and terminal-specific user interface con-
`figuration settings, as well as possible software component
`or program updates to server 28, are controlled and effected
`by a configuration tool manager 39 (in FIG. 1) of a man-
`agementserver 37. Configuration changes mayaffect server
`28 and/or terminals 20a—20c, and 40.
`An advantage to storing the Internet address of the global
`address server 36 on each terminal 20a—20c is that
`the
`association between terminal and MDAserver as well as
`changes in the Internet address of MDA servers can beeasily
`and cfficiently appreciated without having to update the
`memory of each terminal. The global update server 38
`updates the global address sever 36 each time there is a
`changein the association between the terminal and the MDA
`server, when there are new terminals to associate with an
`MDAserver, or when the Internet address of a particular
`MDAserveris changed.
`With the Internet address of the global address server 36
`stored in the memory of the terminal 20, the terminal 20 is
`able to request and retrieve the Internet address of the MDA
`server 28 from the global address sever 36. The global
`address server 36 stores information about the location of
`the MDA server 28 and all other MDAservers in the
`network and the corresponding relation between each ter-
`minal and its MDAserver, Thus, the terminal 20 is always
`able to obtain the address of the MDA server 28, which is the
`MDAserver designedto serve the terminal 20. For example,
`the terminal 40 coupled through an access point 42 to an ISP
`44 can retrieve the Internet address of the MDAserver 28
`
`from the global address server 36, provided that the MDA
`server 28 is the MDAserverdesignated to serve the terminal
`40 and that the terminal 40 is authenticated by the MDA
`server 28 as an authorized user of the services.
`
`FIG. 2 is a block diagram of the MDA server of the MDA
`system of the network of FIG. 1. The MDA server 38 may
`include an application server 46, a support server 48, a
`network application server 50, and a directory server 52. It
`will be apparent to those skilled inthe art that the referenced
`connections do not depict the physical connections between
`the logical elements; the emphasis is merely on the logical
`connections. The support server 48 provides services ori-
`ented toward enabling and supporting the services provided
`to the terminal 20. The support server 48 may include an
`upgrade services unit 54, a login services unit 56, a profile
`services unit 58, an advertisement services unit 60, an
`administrative services unit 62, and a defined services unit
`64.
`
`The upgrade services unit 54 is a specific means for
`controlled software upgrade of the software for the support
`server 48. The login services unit 56 provides the meansfor
`authentication of the user and the terminal 20 that is being
`used to access the services. Additionally, the login services
`unit 56 is also responsible for log-off activities, such as
`private session termination. The profile services unit 58
`provides a meansfor modifying a user’s profile information,
`e.g., family and private information and preferences. The
`
`10
`
`15
`
`30
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`administration services unit 62 provides a means for admin-
`istration of the support server 48 and the application server
`46. The advertisement services unit 60 provides a meansfor
`the MDAserver 28 to tailor advertisements to the user and
`the terminal 20 according to the user’s profile information.
`The defined services unit 64 is a classification of other
`services containing items like bookmark management
`services, help services,
`log services, name management
`services, and general managementservices.
`The administration services unit 62 provides for admin-
`istration of the support server 46 and the application server
`48. The software product updates are transmitted from the
`global upgrade server 38 (as shown in FIG. 1)
`and its
`configuration tool manager 39 to the upgrade service unit 54
`in FIG. 2 andits configuration tool client. The configuration
`tool client is a functional unit that acts when any configu-
`ration tool manager 39 (as shown in FIG. 1) of the man-
`agement server 37 (as shown in FIG. 1) upgrades any
`software component, fully executable software program, or
`reconfigures configuration parameters; application and sys-
`tem parameters, as well as user interface-specific parameters
`of the terminal.
`
`FIG. 3 is a block diagram of a mobile terminal 20a that
`operates within the MDA system of FIG. 1. Terminals 20b
`and 20c maybe similar in design. Terminal 20a mayinclude
`a touch screen 70 for providing a display, a keyboard 72, a
`browser 74, a driver 76, and hardware 78. The hardware 78
`may include a memoryfor storing data, such as the Internet
`address of the global address server 36, and the software for
`operating the terminal 20, such as the browser 74. Hardware
`78 may include a touch screen controller for controlling the
`input process for touch screen 70. As the terminal 20a is
`turned on, the driver 76 retrieves data relating to the Internet
`address of the global address server 36. Once the terminal
`20a is turned on,it is coupled to the access point 22 and the
`ISP 24. Thus,
`the terminal 20a is able to obtain its own
`Internet address. Using the Internet address of its global
`address server, the terminal 20a is coupled to the global
`address server 36 and sends a request in order to obtain the
`Internet address of its MDAserver. Once the terminal 20a
`
`has the Internet address of its MDAserver,it is then coupled
`to the MDAserver 28. The MDAscrver 28 authenticates,
`using the unique identity of the hardware 78 of the terminal
`20a, that the terminal 20a has family level access privileges.
`Accordingly, the terminal 20a is authenticated and logged
`onto the MDA server 28 to begin a family session at a family
`level. Thus,
`the user can now access services or retrieve
`information from the MDAserver 28 or access the Internet
`
`26. In order for the user to initiate a private session and
`retrieve private information, the user must use the terminal
`20a and provide further authentication to the MDAserver 28
`to gain accessat the private level. It will be apparent to those
`skilled in the art that at either the family level or the private
`level, the user is able to retrieve information related to the
`family of users as well as browse the Internet 26 to retrieve
`information.
`
`The browser 74is a typical browser and may include such
`features as HyperText Transfer Protocol (HTTP), JAVA
`script, and cascade style sheet capability. As with typical
`Personal Computers (PCs), the browser 74 helps the user
`navigate through and retrieve information from the Internet
`oncethe user is connected to the ISP 24 through the terminal
`20. The user utilizes the terminal 20a to connect to both the
`
`ISP 24 and the MDA server 28 using authentication protocol
`as discussed in detail herein. The terminal 20a is the primary
`meansof access by the user to the MDA server 28 and the
`related services and applications. However, the user can also
`
`

`

`US 6,590,568 B1
`
`7
`access the ISP 24 and the MDA server 28 using a PC 20d or
`non-mobile terminal using appropriate family level authen-
`tication initiated manually.
`In orderto retrieve informationor to request services from
`the MDA server28 orthe Internet 26, the user might utilize
`the input touch screen 70. The user can provide input using
`a virtual keyboard displayed on the display 70, using key-
`board 72, or through the touch screen input on the touch
`screen 70 utilizing various processes and functions accord-
`ing to the embodiments of the invention. Even though the
`virtual keyboard may be used as the user retrieves informa-
`tion from the Internet 26, such as a web page, the user can
`receive the information at the display 70 of the terminal 20
`in a full screen format. Full screen format is available
`because the virtual keyboard disappears whenthe user types
`a Universal Resource Locator (URL)or followsa hyperlink
`while navigating the Internet 26. In order to return to the
`virtual keyboard,the user presses a button 80, andthe virtual
`keyboard as well as the header and footer related to the
`services are presented again. Additionally, once the user
`presses the button 80, the web page, which wasa full screen
`display prior to pressing the button 80,
`is reduced to a
`thumbnail view and positioned in the display 70, such as in
`the bottom left corner of the footer. Consequently, the user
`has a shortcut to quickly access the web page that was
`previously visited or to save that web page as a bookmark.
`FIG. 4 illustrates an example of the process of authenti-
`cating a terminal at the family level to initiate a family
`session and authenticating the user at the private level to
`initiate a private session. The process of FIG. 4 beginsat step
`400. At step 402, it is determined whether the terminal is
`turned on. At step 404,if it is determined that the terminal
`is not
`turned on,
`then a communication link cannot be
`established through an access point to the MDA server;
`hence, the process returns to step 402 until the terminal is
`turned on. On the other hand, if the terminal is turned on,
`then the terminal establishes a connection to the access
`point, and hence to an ISP and a global address server. At
`step 408,
`the terminal obtains the Internet address of its
`MDAserver from the global address server.
`At step 410, the terminal communicates with the MDA
`server and is authenticated as an authorized terminal with
`
`access to information and services at the family level, and
`the family session begins and continues until the terminal is
`turned off, Once the MDAserver recognizes the terminal,
`establishing the family session is an automatic background
`activity carried out by the terminal and transparent to the
`user, which is discussed with respect to FIG. 5. In order for
`the user to establish a private session and access private
`information and services, the user has to log in as a private
`user at the private level.
`At step 412,
`it is determined whether the user is an
`authorized private user. At step 414,
`if the user is not
`authenticated as a private uscr, then the user will only be
`given access to a family session with the family level
`information and services. On the other hand, at step 416, if
`the user is an authorized private user, then a private session
`is established and the user is allowed access to the private
`information and services. Although the private level infor-
`mation and services may be the same for all users,
`the
`content will vary from user to user.
`At step 418,
`in the private session the user retrieves
`information and uses the private level services provided by
`the MDAserver. At step 420, it is determined whether the
`user wants to terminate the private session and return to the
`family level. If it is determined that the user does not want
`
`10
`
`15
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`to terminate the private session, then the user continues the
`private session at the private level and the processreturns to
`step 418. On the other hand,if it is determined that the user
`wants to terminate the private session, then at step 422, the
`private session is terminated and the user goes from the
`private level to the family level. At step 424,it is determined
`whether the terminal is still turned on. If the terminal is
`turned on, then the process returns to step 412, with the user
`at the family level in a family session. Otherwise, if the
`terminal
`is turned off,
`then the family session is also
`terminated, and the terminal is logged off the MDA server,
`and the process ends at step 426.
`‘Thus, once the MDA server authenticates the terminal,
`then a family session begins at the family level; once the
`user is recognized as a private user, then a private session is
`initiated. Consequently, a private session remains in effect
`until
`the user explicitly terminates the private session,
`whereas a family session remainsin effect until the terminal
`is turned off. Other features can be included, such as
`termination ofthe private session if no inputis received from
`the user after a predetermined period of time.
`FIG. 5 illustrates an example of the process of establish-
`ing a communication link to an access point, step 406 of
`L1G. 4, and obtaining the Internet address of an MDA server
`for that terminal, step 408 of FIG. 4. Initiating a family
`session at the family level begins at step 500. At stop 502,
`the terminal establishes a communication link with the
`
`access point. At step 504, the terminal obtains its Internet
`address from the access point based on the Internet address
`of the access point with which the terminal has established
`the communication link. At step 506,
`the terminal estab-
`lishes a communication link with the ISP coupled to the
`access point. At step 508, the terminal retrieves the Internet
`address of the global address server from its memory. At step
`510, the terminal sends a request to the global address server
`for the Internet address of the MDAserverthat is associated
`
`the global address server
`with the terminal. At step 512,
`returns the Internet address of the appropriate MDAserver
`to the terminal.

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