(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2007/0030824 A1
`(43) Pub. Date:
`Feb. 8, 2007
`Ribaudo et al.
`
`US 2007003O824A1
`
`(54) SYSTEM AND METHOD FOR PROVIDING
`COMMUNICATION SERVICES TO MOBILE
`DEVICE USERS INCORPORATING
`PROXMITY DETERMINATION
`
`Related U.S. Application Data
`(60) Provisional application No. 60/706.595, filed on Aug.
`8, 2005.
`
`(76) Inventors: Charles S. Ribaudo, Dallas, TX (US);
`James F. Young JR., Dallas, TX (US)
`
`Correspondence Address:
`BAKER BOTTS LLP.
`2OO1 ROSS AVENUE
`SUTE 6OO
`DALLAS, TX 75201-2980 (US)
`
`(21) Appl. No.:
`
`11/463,284
`
`(22) Filed:
`
`Aug. 8, 2006
`
`Publication Classification
`
`(51) Int. Cl.
`(2006.01)
`H04O 700
`(52) U.S. Cl. .............................................................. 370/328
`
`ABSTRACT
`(57)
`In certain embodiments, a method for proximity determina
`tion includes receiving one or more network identifiers, each
`associated with a corresponding network, from a first mobile
`device. The method further includes receiving one or more
`network identifiers, each associated with a corresponding
`network, from a second mobile device. The method further
`includes processing the network identifiers received from
`the first and second mobile devices to determine whether the
`first mobile device and the second mobile device are in
`proximity to one another.
`
`3OO
`
`3O2
`
`
`
`304
`
`RECEIVE USER PROFILE
`FROM FIRST USER
`
`GENERATE PERSONAL
`URL FOR FIRST USER
`
`RECEIVE CONNECTION
`REQUEST FROM SECOND
`USER ORIGINATING FROM URL
`
`306
`
`
`
`SECOND
`USER A REGISTERED
`USERP
`
`NO
`
`
`
`YES
`
`COOKE
`STORED ON MOBILE
`DEVICE OF SECOND
`
`USER
`
`O
`
`NO
`PROMPTSECOND
`USER TOLOGIN
`
`
`
`
`
`316
`
`318
`
`AUTHENTICATE SECONDUSER
`
`YES
`
`
`
`
`
`
`
`31 O
`
`AUTOMATICALLY
`OGN
`SECONDUSER
`
`r
`312
`
`RETRIEVE APPROPRIATE
`MATCH DATA
`
`34
`
`DSPLAY COMMONALITIES
`
`ENO
`
`PROMPTSECOND L-320
`USER TO REGISTER
`
`SECOND
`USER RESPOND
`WITH REGISTRATION
`INFORMATION
`
`
`
`NO
`
`322
`
`YES
`GENERATE
`MATCH DATA FOR -- 324
`SECONDUSER
`
`Petitioners' Ex. 1006, Page 1 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Feb. 8, 2007 Sheet 1 of 4
`
`US 2007/0030824 A1
`
`
`
`12C
`
`12n
`
`22a
`
`22b
`
`22C
`
`Petitioners' Ex. 1006, Page 2 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Feb. 8, 2007 Sheet 2 of 4
`FIG. 2
`
`US 2007/0030824 A1
`
`100
`
`SUBMIT USER PROFILE
`
`102N PROCESS RECEIVED USER PROFILE
`
`104
`
`106
`
`DISTRIBUTE MATCH DATA
`
`LAUNCH APPLICATION
`ON MOBILE DEVICE
`
`
`
`
`
`
`
`
`
`POTENTIAL
`MATCH DETECTED
`2
`
`108
`
`
`
`12
`
`ESTABLISH COMMUNICATION
`
`114
`
`UPLOAD USAGE INFORMATION
`
`
`
`TERMINATION
`EVENT
`
`
`
`110
`
`YES
`
`END
`
`Petitioners' Ex. 1006, Page 3 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Feb. 8, 2007 Sheet 3 of 4
`
`US 2007/0030824 A1
`
`300
`
`302
`
`304
`
`
`
`
`
`
`
`FIG. 3
`
`RECEIVE USER PROFILE
`FROM FIRST USER
`
`GENERATE PERSONAL
`URL FOR FIRST USER
`
`RECEIVE CONNECTION
`REQUEST FROM SECOND
`USER ORIGINATING FROM URL
`
`306
`
`SECOND
`USER A REGISTERED
`USER2
`
`NO
`
`YES
`
`
`
`
`
`
`
`
`
`
`
`
`
`COOKE
`STORED ON MOBILE
`DEVICE OF SECOND
`USERT
`
`
`
`NO
`PROMPTSECOND
`USER TOLOG IN
`
`308
`
`PROMPTSECOND L-320
`USER TO REGISTER
`
`
`
`SECOND
`USER RESPOND
`WITH REGISTRATION
`INFORMATION
`
`
`
`NO
`
`322
`
`YES
`GENERATE
`MATCH DATA FOR N-324
`SECONDUSER
`
`YES
`
`
`
`
`
`
`
`310
`
`AUTOMATICALLY
`LOGN
`SECONDUSER
`
`316
`
`318
`
`312
`
`314
`
`AUTHENCATE SECONDUSER
`
`RETRIEVE APPROPRIATE
`MATCH DATA
`
`DSPLAY COMMONALTES
`
`END
`
`Petitioners' Ex. 1006, Page 4 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`Patent Application Publication Feb. 8, 2007 Sheet 4 of 4
`
`US 2007/0030824 A1
`
`
`
`400
`
`FIG. 4
`CSTART D
`
`SCAN FOR NETWORK
`ADDRESS INFORMATION
`
`402
`
`REPORT NETWORKADDRESS
`NFORMATION TODATA CENTER
`
`404
`
`
`
`406
`
`
`
`408
`
`
`
`RECEIVE NETWORK
`ADDRESS INFORMATION
`
`PROCESS NETWORK
`ADDRESS INFORMATION
`
`REPORTAPPROPRIATE
`INFORMATION
`
`FIG. 5
`502b
`
`p
`
`se
`-
`
`/
`?
`- - - -
`Y.
`
`/
`
`f
`|
`502d-
`\
`1 /
`/ /
`Ys
`/-,
`--- \
`
`1
`
`502b
`
`v,
`
`/
`
`N V
`\
`N
`V
`\
`/
`\
`V
`Y - - - - /
`N-r
`PN
`//
`f 2
`- A d
`508
`\
`- 506
`Yao
`- A - -
`\
`
`V
`N
`
`R
`504 / 502C
`- /
`
`Petitioners' Ex. 1006, Page 5 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2007/003O824 A1
`
`Feb. 8, 2007
`
`SYSTEMAND METHOD FOR PROVIDING
`COMMUNICATION SERVICES TO MOBILE
`DEVICE USERS INCORPORATING PROXMITY
`DETERMINATION
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`0001) This application claims the benefit under 35 U.S.C.
`S119(e) of U.S. Provisional Application No. 60/706.595,
`entitled, “System and Method for Providing Communication
`Services to Mobile Device Users Incorporating Proximity
`Determination, filed on Aug. 8, 2005.
`
`TECHNICAL FIELD OF THE INVENTION
`0002 This invention relates generally to mobile commu
`nications and more particularly to a system and method for
`providing communication services to mobile device users
`incorporating proximity determination.
`
`BACKGROUND
`0003 Personal network building has become increas
`ingly important. A person may desire to network for a
`variety of reasons. For example, a person may desire to
`network for business purposes, Social purposes, or for any
`other Suitable reasons. A person may be in proximity of
`hundred or even thousands of other people every day.
`However, networking with any of these people is often
`difficult without any prior knowledge of them. It is chal
`lenging to identify desirable people with whom to network
`from a random or semi-random selection of the general
`population. Even at a large conference with thousands of
`attendees who necessarily have at least Some common
`interests, it is often difficult for a person to determine the
`most relevant of these people with whom to meet. Tradi
`tionally, people join organizations and attend events to meet
`other people, but such activities are often extremely time
`consuming. Although people who have certain common
`interests, such as belonging to the same organization, attend
`ing the same university, or enjoying the same music, may be
`near each other at a public location, they are frequently
`unaware of these common interests and the opportunity to
`meet each other.
`0004. In recent years, people began exploring the Internet
`for network building, utilizing formats such as chat rooms
`and newsgroups for example. Typically, a chat room enables
`its users to enter and receive messages in real time, while a
`news group enables its users to post and reply to messages.
`However, users of chat rooms and news groups are fre
`quently located in different locations, perhaps thousands of
`miles from each other. As a result, elaborate planning may
`be needed for people sharing common interests to locate and
`meet each other. For example, online sites may still require
`users to complete the elaborate process of visiting the online
`sites to network with other users and then scheduling a time
`and place for a meeting, if desired.
`
`SUMMARY OF THE INVENTION
`0005 According to the present invention, disadvantages
`and problems associated with previous techniques for pro
`viding communication services to mobile device users may
`be reduced or eliminated.
`
`In certain embodiments, the present invention
`0006.
`allows mobile device users with one or more commonalities
`or other reasons for interacting to detect each other when
`they are or have been in physical proximity. In certain
`embodiments, the present invention may compare any num
`ber of user-supplied profiles at a data center or other
`centralized location remote from the mobile device users,
`determine which users are matches for one another in that
`they appear to have one or more commonalities or other
`reasons for interacting, and transmit to each user match data
`containing match identifiers and other information for the
`other users determined to be matches for the user. This
`pre-processed match data for the user is stored locally on the
`user's mobile device. Subsequently, when the user is in
`proximity to another user, the user's mobile device detects
`the presence of the other user's mobile device, receives an
`identifier associated with the detected other user, and com
`pares the received identifier with the pre-processed match
`data stored on the user's mobile device to determine whether
`the other user is one of the user's predetermined matches. In
`certain embodiments, this detection of another user in proX
`imity and determination of whether another detected user is
`a match is performed locally on the user's mobile device,
`without consulting the data center or other centralized
`location remote from the mobile device users. If the other
`user is determined to be one of the user's predetermined
`matches, then the user may arrange to meet or otherwise
`interact with the match to build a new relationship or
`enhance an existing one. The user may connect with the
`match through any of a number of possible mechanisms. The
`user may do so substantially immediately, if the match is still
`in proximity to the user and the user wishes to interact at that
`time, or the user may do so at a later time.
`0007. In certain embodiments, a first user's mobile
`device detects the presence of a second user's mobile device
`in proximity based on network identifiers communicated
`from the mobile devices of the first and second users. In a
`particular embodiment, a method for proximity determina
`tion includes receiving one or more network identifiers, each
`associated with a corresponding network, from a first mobile
`device. The method further includes receiving one or more
`network identifiers, each associated with a corresponding
`network, from a second mobile device. The method further
`includes processing the network identifiers received from
`the first and second mobile devices to determine whether the
`first mobile device and the second mobile device are in
`proximity to one another.
`0008 Facilitating networking according to certain
`embodiments of the present invention may provide a number
`of technical advantages over prior techniques, one or more
`of which may be readily apparent to those skilled in the art
`from the figures, descriptions, and claims included herein.
`Those skilled in the art should appreciate that particular
`embodiments of the present invention may provide all,
`Some, or none of these advantages.
`BRIEF DESCRIPTION OF THE DRAWINGS
`0009 For a more complete understanding of the present
`invention and its advantages, reference is made to the
`following descriptions, taken in conjunction with the accom
`panying drawings, in which:
`0010 FIG. 1 illustrates an example system for providing
`communication services to users of mobile devices;
`
`Petitioners' Ex. 1006, Page 6 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2007/003O824 A1
`
`Feb. 8, 2007
`
`FIG. 2 illustrates an example method for providing
`0011
`communication services to users of mobile devices;
`0012 FIG. 3 illustrates an example method for assigning
`and processing a personal uniform resource locator (URL)
`according to certain embodiments of the present invention;
`0013 FIG. 4 illustrates an example method for proximity
`determination according to certain embodiments of the
`present invention; and
`0014 FIG. 5 illustrates an example set of networks that
`may be used for centralized proximity detection according to
`certain embodiments of the present invention.
`
`DESCRIPTION OF EXAMPLE EMBODIMENTS
`0.015
`FIG. 1 illustrates an example system 10 for pro
`viding communication services to users of mobile devices.
`System 10 includes one or more mobile devices 12, a data
`center 14, and a network 16 that may couple mobile devices
`12 and data center 14 at appropriate times. Although an
`example implementation of system 10 is illustrated and
`primarily described, the present invention contemplates any
`suitable implementation of system 10.
`0016.
`In general, certain embodiments of system 10
`allow users of mobile devices 12 with one or more com
`monalities or other reasons for interacting to detect each
`other when they are or have been in physical proximity. In
`certain embodiments, the present invention may compare
`any number of user-supplied profiles at data center 14 or
`another centralized location remote from the users of mobile
`devices 12, determine which users are matches for one
`another in that they appear to have one or more common
`alities or other reasons for interacting, and transmit to each
`user match data containing match identifiers and other
`information for the other users determined to be matches for
`the user. This pre-processed match data for the user is stored
`locally on the user's mobile device 12. Subsequently, when
`the user is in proximity to another user, the user's mobile
`device 12 detects the presence of the other user's mobile
`device 12, receives an identifier associated with the detected
`other user, and compares the received identifier with the
`pre-processed match data stored on the user's mobile device
`12 to determine whether the other user is one of the user's
`predetermined matches. In certain embodiments, this detec
`tion of another user in proximity and determination of
`whether another detected user is a match is performed
`locally on the user's mobile device 12, without consulting
`data center 14 or another centralized location remote from
`the users of mobile devices 12. If the other user is deter
`mined to be one of the user's predetermined matches, then
`the user may arrange to meet or otherwise interact with the
`match to build a new relationship or enhance an existing
`one. The user may connect with the match through any of a
`number of possible mechanisms. The user may do so Sub
`stantially immediately, if the match is still in proximity to
`the user and the user wishes to interact at that time, or the
`user may do so at a later time.
`0017. In certain embodiments of the present invention,
`data center 14 is operable to gather and store information
`regarding users of mobile devices 12, networks detected by
`users of mobile devices 12 (e.g., including information
`regarding the wireless infrastructure, information regarding
`which users encounter which components of the wireless
`
`infrastructure, and other Suitable information), encounters
`between users of mobile devices 12, and other suitable
`information. For example, data center 14 may gather and
`store information identifying various network access points
`encountered by users of mobile devices 12 and may assign
`data to those network access points. This information may
`be used to match users of mobile devices 12 with other users
`of other mobile devices 12, to match users of mobile devices
`12 with locations associated with particular networks, or for
`other Suitable purposes. These concepts are described in
`more detail throughout this description.
`0018 Mobile devices 12 may include any suitable types
`of devices capable of communicating with other devices.
`Typically, mobile devices 12 are portable at least to some
`degree. Mobile devices 12 may include, for example, “lap
`top' computers, "palmtop' computers, personal digital
`assistants, pagers, cellular telephones, game consoles, cam
`eras, or any other suitable types of portable devices. Each
`mobile device 12 may include one or more suitable devices
`for wireless communication, Such as one or more wireless
`fidelity (Wi-Fi) devices, one or more BLUETOOTH
`devices, one or more Global System for Mobile Communi
`cation (GSM) devices, one or more code division multiple
`access (CDMA) devices, one or more Worldwide Interop
`erability for Microwave Access (WiMax) devices, and/or
`any other Suitable communication devices. Although a par
`ticular number of mobile devices 12 are illustrated, system
`10 may include any suitable number of mobile devices 12.
`For example, the number of mobile devices 12 may vary
`over time depending on the number of users of system 10
`and their mobile device needs. Throughout this description,
`mobile devices 12 and users of mobile devices 12 may be
`referred to interchangeably where appropriate.
`0019 Mobile devices 12 may each include any suitable
`combination of hardware, software, and firmware to provide
`the functionality described herein and any other appropriate
`functionality. In certain embodiments, mobile devices 12
`each include one or more web browsers. Each mobile device
`12 may include an adaptor 18. Each adaptor 18 may include
`or otherwise be associated with one or more applications 20
`that are based on one or more programming languages, such
`as C, C++, C#, Java, or any other suitable language. The
`adaptor 18 of a mobile device 12 (e.g., mobile device 12a)
`may facilitate communication with other mobile devices 12
`(e.g., mobile devices 12b through 12n) and between mobile
`device 12 and data center 14.
`0020. In certain embodiments, adaptor 18 includes a
`protocol driver that is operable to facilitate identifying
`mobile device 12 to a wireless network. For example, the
`protocol driver of mobile device 12 may broadcast a service
`set identifier (SSID). In certain embodiments, the SSID is a
`sequence of characters that is the identifier, or name, of a
`wireless local area network (WLAN) (e.g., a high fidelity
`WLAN, typically referred to as a wireless fidelity or Wi-Fi
`network) or other wireless network. The SSID is a unique
`identifier that wireless access points and wireless nodes use
`to communicate with each other. The SSID may be included
`in the header of packets exchanged within a defined WLAN
`basic service set (BSS). The SSID may be set by a network
`administrator and, for open wireless networks, the SSID
`may be broadcast to one or more, if not all, wireless nodes
`(e.g., one or more other mobile devices 12) within range of
`a network access point.
`
`Petitioners' Ex. 1006, Page 7 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2007/003O824 A1
`
`Feb. 8, 2007
`
`0021. In certain embodiments, one or more mobile
`devices 12 each include a network interface card (NIC) that
`is compliant with IEEE 802.11 and the network driver
`interface specification (NDIS), although mobile devices 12
`may include any suitable type of NIC, according to particu
`lar needs. The adaptor 18 of a mobile device 12 that includes
`an NDIS-compliant and IEEE 802.11-compliant NIC may
`use the 802.11 frame or media access control (MAC) layer
`for detecting other mobile devices 12 in proximity. In certain
`embodiments, even in the absence of an NDIS-compliant
`NIC, the adaptor 18 may still function on the same logical
`network (e.g., the same Internet protocol (IP) subnet), but
`may not be able to take advantage of certain interface
`functionality. Additionally or alternatively, the protocol
`driver of adaptor 18 may be designed so as not to require
`NDIS compliance. In certain embodiments, the protocol
`driver may facilitate multi-hop messaging without requiring
`proprietary WLAN cards or transmission control protocol/
`internet protocol (TCP/IP) drivers. Using the protocol driver
`to pass messages between mobile devices 12 that are out of
`range of one another, other mobile devices 12 may act as
`wireless routers to form mesh networks, such that a mobile
`device 12 is not restricted by the approximately 300-foot
`range of a single-hop Wi-Fi network. This 300-foot range
`may be extended or reduced, as appropriate.
`0022 Application 20 may be operable to implement one
`or more features of the present invention on its associated
`mobile device 12. For example, application 20 may perform
`certain functions to facilitate communication with data cen
`ter 14, completion of user profiles, authentication of users,
`and other suitable functions described below. In certain
`embodiments, application 20 may be installed on mobile
`device 12 using a standard Win32 installer wizard (e.g.,
`InstallerWise, Install Shield, or any other suitable installer
`wizard). During this installation process, an NDIS test may
`be executed to test for the presence of a WLAN card that
`complies with NDIS 5.1 or other suitable NDIS version. For
`example, this test may be performed by executing a WLAN
`object identifier (OID) call and expecting a standard
`response. In certain embodiments, if the WLAN card is
`compliant with NDIS 5.1 or another suitable NDIS, then the
`WLAN card may have full on-board WINDOWS-generic
`WLAN support, and the install wizard may install an appro
`priate NDIS-compliant protocol driver. In certain embodi
`ments, the install wizard may install the NDIS protocol
`driver into c:\windows\System32\drivers\ or another suitable
`path and may use the MICROSOFT TCP stack in addition
`to this protocol driver. In certain embodiments, even if no
`suitable protocol driver is detected, application 20 may still
`function on a standard TCP/IP subnet, but may not be able
`to take full advantage of the WLAN interface to detect other
`mobile devices 12 in proximity.
`0023. Additionally, certain mobile devices 12 may
`include a WINDOWS operating system and may include
`third-party card managers in addition to the MICROSOFT
`WINDOWS Wireless Zero Config (WZC) Service. It may be
`desirable to terminate these managers, so that application 20
`may have control of the WLAN interface. In certain embodi
`ments, application 20 assumes control, possibly automati
`cally, of the WLAN interface by stopping Such managers.
`Application 20 may also include its own network manage
`ment tool, which may allow users to browse and associate
`with available WLANs. Additionally or alternatively, appli
`cation 20 may be operable to integrate with existing man
`
`agers such that those managers can work with application 20
`and any other Suitable components of system 10.
`0024. In certain embodiments, mobile devices 12 may
`each be coupled to data center 14 via network 16. Network
`16 may include any Suitable types of networks, including for
`example one or more LANs, radio access networks (RANs).
`metropolitan area networks (MANs), wide area networks
`(WANs), all or a portion of a global computer network such
`as the Internet, an intranet, or any other wireline, optical,
`wireless, or other links. Network 16 may communicate, for
`example, IP packets, Frame Relay frames, or Asynchronous
`Transfer Mode (ATM) cells to communicate voice, video,
`data, and other suitable information between network
`addresses.
`0025 Mobile devices 12 may connect to network 16,
`when appropriate, through a wired or wireless link. Mobile
`devices 12 may be identified on network 16 by a network
`address or combination of network addresses. Such as a
`MAC address associated with the NIC, an IP address, a cell
`tower ID, and/or any other suitable network addresses
`according to particular needs. Mobile devices 12 may or
`may not be connected to network 16 at any given time.
`0026.
`In general, a mobile device 12 may be operable to
`submit a user profile for its associated user to data center 14
`for comparison with user profiles for users of other mobile
`devices 12. In response to Such comparison, mobile device
`12 may receive and store match data generated at data center
`14. Mobile device 12 may thereafter communicate with
`other mobile devices 12 detected in proximity to determine
`whether their associated users are matches (e.g., have been
`predetermined to be matches as reflected in the match data
`stored in mobile device 12). Mobile device 12 may notify its
`user if such a match is detected in proximity, allowing the
`user to initiate an interaction with the detected match if
`desired.
`0027. In certain embodiments, users of mobile devices 12
`may provide user information to data center 14, via network
`16 for example, so that data center 14 may predetermine
`matches for the users. For example, users of mobile devices
`12 may each Submit one or more user profiles to data center
`14. In certain embodiments, users may interact with mobile
`devices 12 to complete their user profiles and to submit their
`user profiles to data center 14. A user may complete a user
`profile using one or more web pages, by downloading and
`completing a form, or in any other Suitable manner accord
`ing to particular needs. For example, mobile devices 12 may
`include an application that, either alone or in combination
`with a web browser, may provide users with the ability to
`enter information into a user profile. Text entry fields, radio
`buttons, drop-down menus, and/or any other Suitable data
`input mechanism may be used to facilitate completion of
`user profiles. User profile information may include back
`ground information, affiliations, contacts, preferences, or
`any other Suitable information according to particular needs.
`User profiles may be submitted spontaneously by a user, in
`response to an encounter with one or more other users, in
`response to an encounter with one or more locations, in
`response to an encounter with one or more network identi
`fiers (e.g., MAC addresses, cell tower IDs, or other suitable
`identifiers), or in any other suitable manner according to
`particular needs.
`0028. Although users submitting user profiles using
`mobile devices 12 is primarily described, users may submit
`
`Petitioners' Ex. 1006, Page 8 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2007/003O824 A1
`
`Feb. 8, 2007
`
`user profiles in any Suitable manner, according to particular
`needs. For example, a user could submit a user profile using
`a conventional desktop computer. As another example, a
`user could complete a printed copy of a user profile form and
`mail it to the proprietor of system 10 for entry into data
`center 14. In another example, a third party could create and
`enter user profile information for a user.
`0029. Users of mobile devices 12 may submit multiple
`user profiles to data center 14. Each user profile may be
`based on a variety of criteria, including for example inter
`ests, affiliations, associations, events, business networking,
`Social networking, dating, employment, exchanging goods
`and services, connecting friends and acquaintances, geneal
`ogy trees, and any other Suitable categories. In certain
`embodiments, multiple user profiles for a user may have
`similar content but allow the user to match with different
`segments of users. For example, a first user profile may be
`a “University' user profile based on hometown and interests,
`and a second user profile may be a “Business Conference'
`user profile that includes similar content and matches on
`similar criteria but with a different segment of users.
`0030 Throughout this description, users who have com
`pleted one or more user profiles and submitted those user
`profiles to data center 14 may be referred to as “registered
`users. Each user of a mobile device 12 may have a unique
`user ID. The user ID may be used for authentication or any
`other Suitable purposes. For example, prior to a user having
`access to or being able to modify the user's profile, the user
`may be required to provide his userID, as well as a password
`or other suitable information, to data center 14.
`0.031) Subsequent to a user submitting user profile infor
`mation to data center 14, which may include a new user
`profile or updates to an existing user profile, the user may
`receive match data from data center 14 identifying one or
`more predetermined matches. Match data is described in
`greater detail below with respect to data center 14, but
`generally provides a way for a mobile device 12 to deter
`mine whether a user of another mobile device 12 is a match
`when the other mobile device 12 is detected in proximity. In
`certain embodiments, mobile device 12 may request match
`data from data center 14. For example, a user of mobile
`device 12 may log onto the user's account at data center 14
`and request “synchronization,” which may include down
`loading the most current match data for the user to mobile
`device 12. As another example, mobile device 12 may be
`configured to automatically request synchronization at regu
`lar intervals. Match data may be synchronized to mobile
`devices 12 in any suitable manner, according to particular
`needs.
`0032 Mobile devices 12 may each have an associated
`memory module 22. Each memory module 22 may include
`any Suitable memory, database, or other data storage
`arrangement including, without limitation, magnetic media,
`optical media, random access memory (RAM), read-only
`memory (ROM), removable media, or any other suitable
`component. In certain embodiments, each memory module
`22 is operable to store data as one or more compressed
`binary files. In certain embodiments, each memory module
`22 may include one or more structured query language
`(SQL) servers. Although each mobile device 12 is illustrated
`as having a corresponding memory module 22, the present
`invention contemplates one or more mobile devices 12
`
`sharing a memory module 22. Moreover, although a single
`memory module 22 is illustrated for each mobile device 12,
`mobile devices 12 may each include any suitable number of
`memory modules 22 according to particular needs.
`0033 Memory module 22 may store various data asso
`ciated with the user of mobile device 12. For example,
`memory module 22 may store one or more user profiles 24
`for the user of mobile device 12. Additionally, memory
`module 22 may store match data 26 downloaded from data
`center 14 and identifying one or more predetermined
`matches for the user. Memory module 22 may store any
`other Suitable information, according to particular needs.
`0034) Data center 14 may serve as a central processing
`and storage node for system 10. In certain embodiments,
`data center 14 includes a server system 30 and a database32.
`Although database 32 is illustrated as being external to
`server system 30, in embodiments in which data center 14
`includes server system 30, the present invention contem
`plates database 32 being either external or internal to server
`system 30.
`0035) Data center 14 may include one or more computer
`systems at one or more locations that may share data storage,
`communications, or other resources according to particular
`needs. For example, functionality described in connection
`with data center 14 may be provided using a single or
`multiple computer systems, which in a particular embodi
`ment might include a server or pool of servers. Furthermore,
`functionality described in connection with data center 14
`may be provided using any suitable Software components.
`0036) Each computer system associated with data center
`14 may include one or more Suitable input devices, output
`devices, mass storage media, processors, memory, inter
`faces, communication ports, or other appropriate compo
`nents for receiving, processing, storing, and communicating
`information according to the operation of system 10. The
`one or more processors of each computer system may be a
`microprocessor, microcontroller, or any other Suitable com
`puting device or resource.
`0037 Database 32 may include any suitable memory,
`database, or other data storage arrangement including, with
`out limitation, magnetic media, optical media, random
`access memory (RAM), read-only memory (ROM), remov
`able media, or any other Suitable component. In certain
`embodiments, database 32 includes one or more SQL serv
`ers. Moreover, although a single database 32 is illustrated,
`data center 14 may include any suitable number of databases
`32 according to particular needs.
`0038) Data center 14 may include one or more applica
`tions 34 based on one or more programming languages, such
`as C, C++, SQL, Java, and/or any other Suitable language.
`Applications 34 may assist data center 14 in performing one
`or more of the functions described herein.
`0039) Data center 14 is operable to receive information
`from mobile devices 12, as well as any other suitable
`devices, and store the received information in database 32.
`For example, data center 14 is operable to receive user
`profiles 24 from users of mobile devices 12 and store user
`profiles 24 in database 32. User profiles 24 may be stored in
`the format in which they were received or may be processed
`and stored in any other suitable format.
`
`Petitioners' Ex. 1006, Page 9 of 38
`Hewlett Packard Enterprise Co. et al. v. BillJCo, LLC
`IPR2022-00420
`
`

`

`US 2007/003O824 A1
`
`Feb. 8, 2007
`
`0040. In certain embodiments, data center 14 is