(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2004/0252197 A1
`Fraley et al.
`(43) Pub. Date:
`Dec. 16, 2004
`
`US 2004O252197A1
`
`(54) MOBILE DEVICE MANAGEMENT SYSTEM
`(75) Inventors: James J. Fraley, San Diego, CA (US);
`Ning Nicholas Chen, San Diego, CA
`(US)
`Correspondence Address:
`HOGAN & HARTSON L.L.P.
`500 S. GRAND AVENUE
`SUTE 1900
`LOS ANGELES, CA 90071-2611 (US)
`(73) Assignee: NEWS IQ Inc.
`(21) Appl. No.:
`10/430, 197
`(22) Filed:
`May 5, 2003
`
`Publication Classification
`
`(51) Int. Cl. .................................................. H04N 5/225
`
`(52) U.S. Cl. .......................................................... 348/207.1
`
`(57)
`
`ABSTRACT
`
`A mobile device management System including a method for
`monitoring a remote Video camera and event Scheduling,
`Synchronization and modification using location informa
`tion. Video from a remote camera is encoded by a computer
`and Streamed in real time over a network to a mobile device
`for decoding and display. The computer encoder and mobile
`device decoder are Software-based. Event calendar and
`Schedule information is incorporated, shared and automati
`cally updated among multiple mobile devices. Location
`information, Such as from a locator network or a Satellite
`based global positioning System, is used to provide real time
`updates to a mobile device calendar or event Schedule. A
`map or other indicia of the location of other mobile devices
`may be provided.
`
`100 N
`110
`
`MOBE
`DEVICE
`
`140
`
`
`
`
`
`135
`
`
`
`120
`
`130
`
`COMPUTER
`
`I PACKET-SWITCHED
`NETWORK
`
`Petitioners' Ex. 1020, Page 1 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 1 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Dec. 16, 2004 Sheet 1 of 7
`
`US 2004/0252197 A1
`
`
`
`CJEHO LIWAS-LEXOVd
`
`
`
`XHOM LEN
`
`HalmdWOO
`
`99 ||
`
`
`
`? ?un61-I
`
`
`
`0 || ||
`
`~~
`
`ET|8OIN-- — || ||
`BOIAEC]-
`
`Petitioners' Ex. 1020, Page 2 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 2 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Dec. 16, 2004 Sheet 2 of 7
`
`US 2004/0252197 A1
`
`z aun61-I
`
`0/Z-
`
`
`
`EOLAECI ETIEHOW
`
`ÅRHOINE IN
`
`|NOCIN\/>| 06Z
`
`
`SSE OOV/è?ECIO ONE OEC?IA
`
`
`
`
`
`
`
`092MECIO OBCI ORGIA
`
`09Z
`
`
`
`AVTdSICHNOI LOEIS(±)
`
`992
`
`CINVEESW78€.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Glz -- G0z —/
`
`·· --01. Z
`
`Petitioners' Ex. 1020, Page 3 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 3 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Dec. 16, 2004 Sheet 3 of 7
`
`US 2004/0252197 A1
`
`
`
`009~
`
`(S)EOIAEG
`
`Petitioners' Ex. 1020, Page 4 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 4 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Dec. 16, 2004 Sheet 4 of 7
`
`US 2004/0252197 A1
`
`400
`
`CONNECT MOBILE DEVICE
`AND COMPUTER
`
`405
`
`CAPTURE LIVE WIDEO
`IMAGE FROM CAMERA
`
`410
`
`STORE VIDEO IMAGE ON |- 415
`STORAGE DEVICE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`| ENCODE AND STREAM
`IMAGE TO MOBILE DEVICE
`
`420
`
`
`
`
`
`
`
`DECODE AND DISPLAY
`MAGE ON MOBILE
`DEVICE
`
`425
`
`Figure 4
`
`Petitioners' Ex. 1020, Page 5 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 5 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Dec. 16, 2004 Sheet 5 of 7
`
`US 2004/0252197 A1
`
`099
`
`
`
`WELLSÅS (HOLVOOT
`
`(Sd5))
`
`
`
`EITTICIOW K) —>Awano KFF>
`
`NOI.LV/OOT
`
`099
`
`HOIABG=TIGOW
`
`>{V/CINETWO
`
`
`
`OZG|-ETT CIOW
`
`\!VOINETWO
`
`
`
`EKOHAEC ETIEJOW
`
`
`
`
`
`
`
`
`
`
`
`Petitioners' Ex. 1020, Page 6 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 6 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Dec. 16, 2004 Sheet 6 of 7
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ZOZ
`
`Petitioners' Ex. 1020, Page 7 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 7 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Dec. 16, 2004 Sheet 7 of 7
`
`US 2004/0252197 A1
`
`g
`
`g
`
`S.
`
`
`
`
`
`:
`
`:
`
`:
`
`:
`
`Petitioners' Ex. 1020, Page 8 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 8 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2004/0252197 A1
`
`Dec. 16, 2004
`
`MOBILE DEVICE MANAGEMENT SYSTEM
`
`FIELD OF THE INVENTION
`0001. The present invention relates to mobile communi
`cation Systems and, in particular, relates to a mobile device
`management System.
`
`BACKGROUND OF THE INVENTION
`0002 The industrialized world is becoming increasingly
`reliant on mobile technologies, Such as wireleSS Voice and
`data transmission. In addition to voice and data transmis
`Sion, users now demand useful and innovative Video and
`multimedia applications that are Supported by their cell
`phones and personal digital assistants (PDAS). One video
`application that would be of particular utility to a mobile
`device user is the ability to view and monitor feed from a
`remote video camera on their mobile device. The delivery of
`live Video feed generally requires broadband transmission
`media capable of Supporting a very high data rate Signal.
`WireleSS Systems, however, are typically characterized by
`lower device processing power and channels having reduced
`bandwidth and lower reliability. Hence, the receipt and
`display of Video feed from a remote camera on a mobile
`device is difficult to achieve over a wireless link.
`0.003 Mobile device users also demand reliable and
`innovative mechanisms for updating personal data, Such as
`calendar and Scheduling information, that is Stored on their
`mobile devices. The ability to update calendar and schedule
`information with real time location information about other
`mobile device users with whom the user is scheduled to or
`desires to interact would be particularly invaluable. Typi
`cally, however, personal data Stored on a mobile device is
`updated via Synchronization with a larger System Such as a
`Server or personal computer. The mobile device usually must
`be cabled to the System for update of personal data and
`calendar information, and the updates are often user-initi
`ated rather than System-driven or automatic. Real time,
`automatic updating of calendar information incorporating
`location information about other mobile devices is not
`provided by current Systems.
`
`SUMMARY OF THE INVENTION
`0004 One aspect of the invention is a system for moni
`toring a remote camera on a mobile device. Live video
`images from the remote camera are captured and Streamed
`in real time over a network to the mobile device. The images
`may be encoded prior to Streaming with a Software-based
`encoder, and decoded by the mobile device using a Software
`based Video decoder. Control signals may be sent from the
`mobile device to the camera to remotely control the camera.
`Modifications to Standard Video compression and Streaming
`protocols are provided to better Suit a mobile device envi
`rOnment.
`0005 Another aspect of this invention is a system for
`mobile device event management, using location and cal
`endar information. Calendar and location information is
`shared among multiple devices and used to Schedule, re
`Schedule and manage events. The relative proximity of the
`mobile devices may be displayed.
`0006 Additional features, aspects and improvements of
`this invention will be apparent after review of the following
`
`figures and detailed description, and are intended to be
`within the scope of this invention and protected by the
`accompanying claims.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0007 FIG. 1 is a diagram of an inventive mobile device
`Video monitoring System.
`0008 FIG. 2 is a block diagram illustrating the compo
`nents of the mobile device of FIG. 1 in more detail.
`0009 FIG. 3 is a block diagram illustrating the compo
`nents of the computer system of FIG. 1 in more detail.
`0010 FIG. 4 is a flow diagram of an inventive method
`for delivering and displaying video on a mobile device.
`0011 FIG. 5 is a block diagram of an inventive peer-to
`peer mobile device event Scheduling System.
`0012 FIG. 6 is a block diagram of an inventive mobile
`device event Scheduling System.
`0013 FIG. 7 is a flow diagram of an inventive method
`for mobile device event Scheduling.
`0014 FIG. 8 is a diagram of an inventive network of
`fixed location devices for assisting in mobile device event
`Scheduling and location.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`0015 The present invention provides a comprehensive
`System for mobile device management. It includes a System
`for monitoring, receiving and displaying video feed from a
`remote camera on a mobile device, and a System for real
`time mobile device event management using calendar and
`location information. Drawbacks associated with existing
`event Scheduling methodologies are overcome by incorpo
`rating real time location information and Video feed into a
`robust System of mobility management that has application
`in Several practical areas, including Surveillance, Safety and
`Security.
`0016 FIG. 1 illustrates a wireless video monitoring
`system 100. Video monitoring system 100 has broad appli
`cation and may be implemented wherever it is advantageous
`to use a mobile or wireless device (Such as a cellular
`telephone) to monitor images captured by a remote camera.
`With monitoring system 100, for example, a mobile device
`can be employed to monitor one's home while on vacation,
`or to monitor the babysitter or the pets. As will be described
`below, the present invention even allows the mobile device
`user to issue control Signals to the camera to change the
`video feed that is received by the mobile device.
`0017 Referring to FIG. 1, mobile device 105 is coupled
`to cell network 120 over air interface 110. Computer 140
`delivers a live video image from camera 145 to mobile
`device 105 via network connection 135, packet-switched
`network 130 and cell network 120. Cell network 120 can be
`a public or private cellular network providing the necessary
`architecture for mobile call maintenance, including base
`Station Subsystem(s), mobile Switching center(s), location
`registries and other infrastructure components. In one
`embodiment, cell network 120 is a public, wireless wide
`
`Petitioners' Ex. 1020, Page 9 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 9 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2004/0252197 A1
`
`Dec. 16, 2004
`
`area network (W-WAN) supporting one or more multiple
`access schemes (i.e., TDMA, CDMA, etc.) and coupled to
`the Internet.
`0.018
`Packet-switched network 130 is a public or private
`wide area network (WAN) or local area network (LAN)
`Supporting transport Services for delivering Video packets
`between camera 145 and mobile device 105. In one embodi
`ment, network 130 is a private intranet Supporting a propri
`etary packet transport mechanism. In another embodiment,
`network 130 is the Internet and supports the transmission
`control protocol (TCP) and Internet protocol (IP). In this
`embodiment, computer 140 is configured with either a static
`or dynamic IP address. Mobile device 105 can be manually
`configured with the IP address of computer 140, or config
`ured to receive the IP address of computer 140 dynamically,
`using for example, the short message Service (SMS) proto
`col to communicate the IP addressing information.
`0.019 Network connection 135 can use a variety of data
`communication technologies to connect computer 140 to
`packet-switched network 130. If network 130 is the Internet,
`computer 140 can connect to Internet 130 using an Internet
`service provider (ISP) under a variety of connectivity
`options, including cable, digital Subscriber line (DSL), or
`asynchronous dial-up access over the public Switched tele
`phone network (PSTN) using a conventional modem. Net
`work connection 135 can also be a high-speed dedicated
`circuit running between an ISP and computer 140. Network
`connection 135 can itself incorporate a wireleSS data com
`munication link. The test results described were achieved
`using a cable modem to connect between computer 140 and
`packet-switched network (Internet) 130.
`0020 Mobile device 105 may be one of many widely
`available wireleSS communication devices, Such as a cellular
`telephone, a personal digital assistant (PDA), a laptop per
`Sonal computer equipped with a wireleSS modem or even a
`Smart mobile television. Exemplary implementations of
`mobile device 105 include a Sharp(R) code division multiple
`access (CDMA) cellular telephone (used by the inventors as
`a prototype) and a PalmTM handheld device with wireless
`capability. System 100 Supports true device independence
`and is uniquely tailored to run on nearly all third generation
`CDMA phones on the market.
`0021 FIG. 2 illustrates mobile device 105 in more detail.
`Radio frequency (RF) section 205 is coupled to antenna 210
`for receiving and transmitting RF signals. RF section 205
`communicates with baseband section 215 over bus 220.
`Baseband section 215 comprises a processor 225 for voice
`and data Signal processing. Baseband Section 215 Stores and
`retrieves data from random access memory (RAM) 230 over
`memory bus 235. Baseband section 215 also communicates
`with user interface 240 over interface bus 245. User inter
`face 240 typically comprises a display 255 for displaying
`text, graphics or Video, a keypad 270 for entering data and
`dialing, and an audio System 260, Such as a Speaker.
`0022. Mobile device 105 is preferably configured with a
`Software video decoder 250 for decoding video signals.
`Mobile device 105 may also be configured with a software
`video encoder 290 for encoding and transmitting video
`control information. By implementing the encoding and
`decoding processes in Software, System 100 is device and
`processor independent. In other words, Viewing a Video bit
`Stream is possible on any mobile device because the Video
`
`decoder and encoder are implemented in Software rather
`than embedded or hard-coded for operation on a particular
`wireleSS device chipset.
`0023 Use of an application programming interface (API)
`provides the abstraction layer needed to Support device and
`processor independence. Function calls from decoder 250
`can be written to conform to a particular API, Such as Sun
`Microsystems(R Inc.'s Java 2 micro edition (J2ME) or
`Qualcomme Inc.'s binary runtime environment for wireless
`(BREW), instead of to a particular chip (i.e., processor). If
`the encoding and decoding software is written in BREW, for
`example, the Video decoder and encoder can be loaded and
`run on any mobile device that supports BREW. An API such
`as BREW is also useful for providing the necessary IP
`connectivity. Video decoder 250 can be written to pass
`IP-related function calls to the BREW API, which will then
`handle the details of establishing a link between mobile
`device 105 and computer 140.
`0024. The achievable frame rate, video rendering quality
`and performance are functions of the processing power and
`memory at the disposal of mobile device 105. For delay
`Sensitive live Video feed, for example, a relatively fast
`processor is needed to eliminate frame latency. During a
`System test, the inventors achieved six frames per Second
`using an advanced RISC machine (ARM) 7 processor with
`100 kilobytes of RAM embedded in a Qualcomm(R) MSM
`3100 chipset in a prototype Sharp(R) CDMA cell phone.
`0025 Video encoder 290 may send control data over cell
`network 120 and packet-switched network 130 to computer
`140 to control camera 145. Hence, a mobile user can
`remotely control basic camera functions, Such as pan, Zoom,
`and tilt, from device 105. Video encoder 290 is preferably a
`Software-based video encoder loaded into RAM 230. A
`mobile device 105 including both decoder 250 and encoder
`290 supports full duplex operation with live video feed in
`one direction (from camera 145 to mobile device 105) and
`control information in the other direction (from mobile
`device 105 to camera 145).
`0026. The protocol used to stream video can be a stan
`dard packet-based Video compression protocol Such as the
`MPEG4 video compression standard, modified to control
`Special features and limitations of the present invention. The
`Video frame flow control mechanism is modified to accom
`modate the relatively limited amount of mobile device frame
`buffer space that is available. Device 105 waits until assem
`bly of a complete multi-packet video frame is complete
`before signaling computer 140 (typically with a one byte
`header) to send another frame. Computer 140 waits for
`receipt of this header before Sending another Video frame to
`the mobile device. This differs from conventional TCP
`protocol and is advantageous because MPEG4 video decod
`ing is resource and bandwidth intensive while device 105 is
`typically bandwidth limited. The prototype CDMA phone
`used in the inventors’ tests, for example, had a uSeable 14
`kilobits per second of bandwidth.
`0027. Since a typical mobile device will lack the storage
`capacity to permanently Store an incoming video image or
`Stream, another important feature of System 100 is config
`uring the size and resolution of mobile device display 255 to
`best take advantage of the available Storage capacity. Dis
`play 255 may be an LCD panel having a resolution large
`enough to accurately distinguish and render a Video image.
`
`Petitioners' Ex. 1020, Page 10 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 10 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2004/0252197 A1
`
`Dec. 16, 2004
`
`In one embodiment, display 255 is a color display capable
`of supporting an MPEG4 compressed video bit stream.
`Other display technologies and display enhancements com
`monly found on wireleSS devices, Such as windowing and
`backlighting, are supported by system 100. The video dis
`play features of the API that is used, such as BREW, can be
`employed to effect display of the Video image. Satisfactory
`results were achieved in a laboratory prototype developed by
`the inventors that included a cell phone having a 256 color,
`(8-bit) 128x144 pixel display Supporting a Video image
`having a frame size of 128 pixels tall by 96 pixels wide.
`0028. A computer system 300 including computer 140
`and camera 145 is illustrated in more detail in FIG. 3.
`Computer 140 preferably has a software-based video
`encoder 303 and may be configured to operate as a video
`Server. This is a significant departure from Streaming video
`Systems which employ hardware-based Video encoders. A
`Software video encoder provides many advantages, includ
`ing efficient resource utilization and no special hardware
`requirements. So long as it has the minimum components
`needed to load and run a Software video encoder, computer
`140 may be a conventional desktop computer including
`components Such as a processor 302, a dynamic memory
`(RAM) 304 and a static memory (ROM).306 coupled via a
`bus 301 or other communication mechanism. An external
`Storage device 307, Such as a magnetic or optical disk,
`input/output devices 309, such as a keyboard and a monitor,
`and a network adapter 310, Such as a network interface card
`(NIC), may also be coupled to computer 140.
`0029 Video camera 145 may be any camera capable of
`capturing and Streaming a Video image to computer 140 for
`transmission to mobile device 105. Connectivity between
`computer 140 and camera 145 can be a simple universal
`serial bus (USB) or other serial cable connector. The video
`generated by camera 145 may be a still image, Such as an
`image presentable in JPEG format, or a component of a live
`streaming video feed, such as a feed presentable in MPEG4
`format.
`0.030. As mentioned, computer 140 is preferably config
`ured with a Software video encoder 303 stored in the
`dynamic memory or RAM 304. As described with respect to
`mobile device 105, hardware independence is achieved by
`the use of a Software-based decoder. The Video decoding
`Software is written to a particular operating System API, Such
`as Microsoft Windows(E) or Linux(E), rather than embedded
`or hard-coded for operation on a particular processor. The
`prototype computer used by the inventors included an Intel
`Pentium(R III processor running Microsoft Windows(R).
`0.031
`Computer 140 may be deployed in a client/server
`environment having multiple mobile devices, Video cameras
`and servers. Mobile device 105 typically acts as a client
`(video decoder 250) and computer 140 acts as a server
`(video encoder 303). Additionally, as described, mobile
`device 105 may include software-based video encoder 290
`for transmitting camera control Signals to computer 140.
`0032 FIG. 4 depicts a method 400 for delivering video
`from camera 145 to mobile device 105 for display. In step
`405, connectivity is established between mobile device 105
`and computer 140. In step 410, computer 140 captures a live
`video image from camera 145. In step 415, computer 140
`Stores the captured image on a storage device, Such as
`storage device 107. Alternatively, the video can be stored on
`
`a storage device located within or associated with network
`130. In step 420, computer 140 encodes and streams the
`video image to mobile device 105 over packet-switched
`network 130 and cell network 120. In step 425, mobile
`device 105, receives, decodes and displays the Video image
`on display 255. As previously described, device 105 waits
`for receipt of a complete multi-packet Video frame before
`Signaling computer 140 to Send another frame.
`0033 Several modes of operation are envisioned. In a
`“live” mode, the mobile user may simply view live video
`feed in real time. In a “history” mode, computer 140 may
`assemble and deliver to mobile device 105 a Summary file
`containing images of Significant activity only. Timestamps
`may accompany the imageS logged in the Summary file. A
`motion detector, for example, may be coupled to or proxi
`mate camera 145, and only those portions of video feed in
`which motion occurs would be deemed “significant” by
`computer 140 and added to the Summary file. In an “alert”
`mode, a real time alert along with Video feed may be
`provided to the mobile device user upon motion detection.
`The history and alert modes are very useful for security and
`Surveillance applications.
`0034. Another aspect of this invention is a system and
`method for real time mobile device event Scheduling, Syn
`chronization and modification, using location information.
`Intelligent event calendar and Schedule information is incor
`porated and shared among multiple mobile devices. A first
`mobile device updates its calendar/event Schedule by obtain
`ing location and calendar information from a Second mobile
`device. The location information may be obtained with the
`assistance of a global positioning System (GPS) and used to
`graphically represent the location of the Second mobile
`device on the display of the first mobile device. Audible or
`Visible indicia of the proximity of the Second device can also
`be provided, Such as by a beeping Sound or an LED.
`0035 FIG. 5 depicts mobile device event management
`system 500 for managing events between mobile device 105
`and a second mobile device 520. Mobile device 105 com
`prises, in addition to the components discussed with respect
`to FIG. 2, event manager 505, calendar query module 510,
`and location query module 515, which are preferably imple
`mented in software (i.e., executable in RAM 230) using a
`suitable API, such as BREW or Java. Calendar query module
`510 queries a second mobile device 520 over wireless
`channel 525 to obtain information stored in its calendar 530.
`Location query module 515 queries a locator system 550,
`Such as a satellite-based GPS, over wireless channel 560 to
`obtain the location of second mobile device 520. Modules
`510 and 515 communicate with manager 505 via busses 570
`and 580.
`0036) The peer-to-peer implementation of system 500
`depicted in FIG. 5 is effective for managing events, such as
`Schedule creation and Synchronization, between two mobile
`devices 105 and 520. A server could also be added to system
`500 to permit shared calendar and event synchronization,
`update and modification among many users.
`0037 Mobile device 520, like mobile device 105, may be
`any of a wide array of mobile communication products,
`including cellular telephones, personal digital assistants,
`portable personal computers with wireleSS capability, and
`the like. Likewise, channel 525 may be any of a large
`number of wireleSS air interfaces available for establishing a
`
`Petitioners' Ex. 1020, Page 11 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 11 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2004/0252197 A1
`
`Dec. 16, 2004
`
`wireless link. For example, channel 525 can be a public or
`private W-WAN or W-LAN, such as a personal communi
`cation service (PCS) network using CDMA, a global system
`for mobile communication (GSM) network using time divi
`sion multiple access (TDMA), and/or even a local wireless
`personal area network (PAN) incorporating Bluetooth TM
`technology.
`0038 FIG. 6 illustrates a method 600 for mobile device
`event management. In step 605, a first mobile device, such
`as device 105 of FIG. 5, queries and obtains calendar
`information from a Second mobile device, Such as device
`520. The user of device 105, for example, may want to
`schedule a meeting with the user of device 520. Step 605 can
`be performed, for example, by calendar query module 510.
`The calendar information may comprise any of the infor
`mation typically found in modern calendar applications,
`Such as meeting location, date, and time. From this infor
`mation, in step 610, the event manager of the first mobile
`device determines the availability of the second mobile
`device for purposes of creating, rescheduling, or canceling
`an eVent.
`0039. In step 615, the first mobile device obtains the
`location of the second mobile device. Step 615 can be
`performed, for example, by location query module 515. The
`location information may be obtained using a global posi
`tioning system (GPS) and may take the form of latitude or
`longitude data. This information is used to determine the
`relative proximity of the second mobile device to the first
`mobile device. In step 620, the event manager of the first
`mobile device Schedules an event based on the location and
`calendar information obtained from the second mobile
`device.
`0040. Event management may include checking the sta
`tus of and updating an existing event. Method steps 605-620
`can be used by a first mobile device, for example, to
`determine whether the user of a second mobile device will
`be on time to a Scheduled event. By considering the current
`time, the time that the event is scheduled and the relative
`proximity of the two devices, it can be determined whether
`a scheduled event will be late (step 625). If the second user
`will be late but the event can still proceed (step 630), the user
`of the first (querying) mobile device may be alerted that the
`Scheduled event is going to be late or cancelled, and the
`relative proximity of the second mobile device can be
`displayed (step 635). If the event is going to be missed
`completely, in step 640, the two mobile devices can coor
`dinate a re-Scheduling of the event.
`0041) Not all steps of method 600 will are performed in
`each instance. When a mobile device contacts another
`mobile device to Schedule an event in the distant future, for
`example, steps 610 and 615 may be omitted since it is only
`necessary to determine the other devices availability. Its
`current location is not relevant So far in advance of the event.
`Likewise, a device may Sometimes be interested only in the
`current location of another device, and not in its calendar
`information.
`0.042 Method 600 may also be used to track the location/
`proximity of another mobile device. This location/proximity
`information may be displayed in a simple fashion, for
`example, by analyzing the longitude/latitude information of
`each party, Scaling this information to the device display
`size, and then displaying relative proximity through the use
`
`of Spaced dots. More complex displayS may be used if
`device display and capability permits. Location boundaries
`may be established for a first mobile device, and an alert may
`be provided to a second mobile device if the first mobile
`device has left those boundaries. This can be extremely
`useful for monitoring children and pets, for example.
`0043 FIG. 7 demonstrates an example of method 600 in
`action. A first mobile device 702 and a second mobile device
`704 are configured with event managers, location query
`modules and calendar query modules as described with
`reference to mobile device 105. In the example illustrated in
`FIG. 7, first mobile device 702 belongs to a father and
`second mobile device 704 belongs to his son. Before his
`morning commute, father Synchronizes the calendar infor
`mation stored in his mobile device 702 with the information
`stored in his home calendar 706. Home calendar 706 may be
`Stored in, for example, father's home computer. Synchroni
`Zation may be performed in a known matter over a cable or
`wireleSS link. In this example, one event is added to the
`calendar information stored in father's mobile device 702:
`event A, a doctor's appointment at 10:00 a.m.
`0044) On his way to work, father's mobile device 702 is
`queried by Son's mobile device 704 for his availability to
`attend Son's Soccer game that night at 6 p.m. (i.e., Step 605
`in FIG. 6). From father's calendar information, son's mobile
`device determines that father is available (step 610) and the
`event (“B”) is scheduled on father's mobile device (step
`620).
`0045 When father arrives at his office, father again
`Synchronizes the calendar information Stored in his mobile
`device 702, this time with the information stored in his office
`calendar 708. Office calendar 708 may be stored in, for
`example, father's office computer. Synchronization may be
`performed in a known matter over a cable or wireleSS link.
`Two more events are added to the calendar information
`stored in father's mobile device 702: event C: a staff meeting
`at 1:00 p.m.; and event D, a conference call at 4:00 p.m.
`0046 AS the day progresses and Son's Soccer game draws
`near, Son's mobile device 604 automatically queries and
`obtains the location of father's mobile device 602 to deter
`mine whether father will be on time for Son's Soccer game.
`If, for example, father's 4:00 p.m. conference call runs late,
`the location query module of son's mobile device 604 will
`note that father's mobile device 602 is still located at father's
`office, and can provide an alert on Son's mobile device
`display that father will likely be late. Son's mobile device
`604 may also modify its stored calendar information to
`reflect the fact that father will be late.
`0047. When father leaves his conference call, he becomes
`delayed in a traffic jam. The location query module of Son's
`mobile device notes the location of father's mobile device
`and alerts Son's mobile device that father is running even
`later or perhaps will miss the game entirely. Father's mobile
`device 602, conversely, can help father make the game by
`providing a Suggestion for a leSS congested alternate route
`with real time directions and a visual map of the alternate
`route. Such information may be obtained from the Internet,
`for example. Son's mobile device 604 may display the
`relative proximity of father's mobile device 602 and, when
`Son's location query module confirms that father's mobile
`device 602 is within a defined proximity (i.e., within five
`
`Petitioners' Ex. 1020, Page 12 of 14
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`Petitioners' Ex. 1020, Page 12 of 14
`Hewlett Packard Enterpris