a2 United States Patent
`
`Czajka, II et al.
`
`US011025573B1
`
`US 11,025,573 B1
`Jun. 1, 2021
`
`(10) Patent No.:
`45) Date of Patent:
`
`(54)
`
`(71)
`(72)
`
`(73)
`
`)
`
`@1
`(22)
`
`(63)
`
`(60)
`
`(1)
`
`(52)
`
`(58)
`
`METHOD AND APPARATUS FOR DATA
`SHARING
`
`Applicant: Ginko LLC, West Bloomfield, M1 (US)
`
`Inventors: Reonald J. Czajka, II, Brighton, MI
`(US); Sam B. Attisha, West
`Bloomfield, MI (US)
`
`Assignee: Ginko LLC, West Bloomfield, MI (US)
`
`Notice: Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`
`U.S.C. 154(b) by 193 days.
`Appl. No.: 16/212,902
`
`Filed: Dec. 7, 2018
`
`Related U.S. Application Data
`
`Continuation-in-part of application No. 15/217,424,
`filed on Jul. 22, 2016, now Pat. No. 10,171,985.
`
`Provisional application No. 62/195,534, filed on Jul.
`22, 2015, provisional application No. 62/234,246,
`filed on Sep. 29, 2015.
`
`Int. CL.
`
`GO6F 3/048 (2013.01)
`
`HO4L 12/58 (2006.01)
`
`HO4L 29/12 (2006.01)
`
`HO4W 8/00 (2009.01)
`
`HO4L 29/08 (2006.01)
`
`HO4W 4/021 (2018.01)
`
`U.S. Cl
`
`CPC ............. HO04L 51/12 (2013.01); HO4L 5120
`
`(2013.01); HO4L 61/1547 (2013.01); HO4L
`67/06 (2013.01); HO4L 67/306 (2013.01);
`HO4W 4/022 (2013.01); HO4W 8/005
`(2013.01)
`Field of Classification Search
`CPC ... GOGF 3/0484; GOGF 3/0488; GOGF 3/0482
`See application file for complete search history.
`
`402
`
`406 -
`N
`
`(56) References Cited
`
`U.S. PATENT DOCUMENTS
`
`5,960,411 A 9/1999 Hartman et al.
`
`6,694,353 B2 2/2004 Sommerer
`
`6,748,402 Bl 6/2004 Reeves et al.
`
`6,785,367 B2 8/2004 Horvath et al.
`
`6,873,841 Bl 3/2005 Sagar
`
`6,909,910 B2 6/2005 Pappalardo et al.
`
`7,194,419 B2 3/2007 Robertson et al.
`
`7,466,810 B1* 12/2008 Quon ............... HO04M 3/42229
`
`379/201.01
`
`(Continued)
`
`OTHER PUBLICATIONS
`
`“SQL Profiles: Technical Overview” (Oracle, May 2010), 5 pgs.
`
`Primary Examiner — Hua Lu
`(74) Attorney, Agent, or Firm — Young Basile Hanlon &
`MacFarlane, P.C.
`
`(57) ABSTRACT
`
`A method for data sharing includes receiving, from a poten-
`tial contact, a first location. The method also includes, in a
`case that a second location of a user device of a user
`matching the first location, identifying, for the user, the
`potential contact; receiving, from the user device, a request
`for the user to become a contact with the potential contact,
`the request includes a permission setting, the permission
`indicates whether a subset of user data of the user can be
`viewed by the potential contact; sending, based on the
`request, a communication to the potential contact to initiate
`a data exchange; and, in response to receiving an acceptance
`of the communication: setting the user as a contact of the
`potential contact, the subset of the user data is viewable to
`the potential contact in accordance with the permission; and
`setting the potential contact as a contact of the user.
`
`31 Claims, 14 Drawing Sheets
`
`a7 -
`
`418
`
`APPLE
`
`EXHIBIT 1001 - 0001
`
`
`
`
`
`
`
`
`US 11,025,573 B1
`Page 2
`
`(56)
`
`7,606,725
`7,634,509
`7,680,513
`8,588,386
`9,037,645
`10,217,085
`10,356,035
`2005/0032527
`2005/0091316
`2007/0061567
`2008/0082332
`2008/0189387
`
`2009/0307281
`2010/0057481
`
`2010/0088246
`2010/0217614
`
`2010/0306185
`2011/0153553
`2011/0202956
`2012/0272287
`
`2012/0316962
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`B2 *
`B2
`B2
`B2
`B2 *
`B2
`BL*
`Al
`Al
`Al*
`Al*
`Al*
`
`Al
`Al*
`
`Al
`Al*
`
`Al*
`
`Al*
`
`Al*
`
`Al*
`
`Al*
`
`10/2009
`12/2009
`3/2010
`11/2013
`5/2015
`2/2019
`7/2019
`2/2005
`4/2005
`3/2007
`4/2008
`8/2008
`
`12/2009
`3/2010
`
`4/2010
`8/2010
`
`12/2010
`
`6/2011
`
`8/2011
`
`10/2012
`
`12/2012
`
`Robertson .............. G06Q 10/02
`705/7.11
`
`Onyon et al.
`
`Haitani et al.
`
`Isaacson et al.
`
`Czajka ..ococcovvvencnne HO4L 67/42
`709/203
`Castro et al.
`Gravino ................. HO04L 51/14
`Sheha et al.
`Ponce et al.
`Day ...coooveiecenens HO4L 9/3234
`713/159
`Mallett ......c.oovevenene G10L 17/00
`704/250
`Lee v HO4L 51/28
`709/217
`McCarthy et al.
`Fein .ooocoovvvnreninn G06Q 30/02
`705/1.1
`Lim
`Brown ................ HO4L 67/1095
`705/1.1
`Smith ... GO6F 16/24578
`707/709
`Klotz .oocoeveieninnn. G06Q 50/01
`707/607
`Connelly ........... HO4AN 21/4755
`725/38
`Kuhlke ......ccoovevnee HO04W 4/023
`726/1
`Rathod ................ G06Q 10/107
`705/14.54
`
`2013/0185368 Al* 7/2013
`
`2013/0219516 Al* 82013
`2013/0298030 Al* 11/2013
`2014/0075075 Al* 3/2014
`2014/0101255 Al* 42014
`2014/0122220 Al* 5/2014
`2014/0122605 Al* 5/2014
`2014/0164129 Al* 6/2014
`2014/0230030 Al* 82014
`
`2014/0244744 Al
`2015/0120406 Al*
`
`82014
`4/2015
`
`2015/0205842 Al* 7/2015
`2015/0302098 Al* 10/2015
`2015/0319157 Al* 11/2015
`2015/0319203 Al* 11/2015
`2016/0088139 Al* 3/2016
`2016/0110467 Al* 4/2016
`
`2016/0308685 Al* 10/2016
`2019/0347426 Al* 11/2019
`
`* cited by examiner
`
`............ HO04W 4/023
`
`709/206
`
`.............. HO4L 63/08
`
`726/28
`
`I i HO04W 4/21
`
`715/733
`
`................. GOG6F 1/1632
`
`710/303
`
`......................... GO06Q 50/01
`
`709/204
`
`............. G06Q 30/0267
`
`705/14.42
`
`.................. G06Q 10/10
`
`709/204
`
`Lo G06Q 30/0261
`
`705/14.58
`
`......... GO6F 16/9537
`
`726/6
`
`............... G06Q 30/0641
`
`705/14.5
`
`....................... GO6F 16/215
`
`707/732
`
`....................... GO6F 21/41
`
`707/708
`
`............. GO6F 16/1844
`
`726/7
`
`............ G06Q 30/0641
`
`715/753
`
`............... HO04M 1/27453
`
`715/763
`
`....................... HO4L 67/22
`
`235/375
`
`................... HO4L 12/1818
`“““““““““ HO04L 63/104
`
`APPLE
`EXHIBIT 1001 - 0002
`
`
`
`
`
`
`
`
`U.S. Patent
`
`o~
`
`ON
`
`LOCATI
`
`Jun. 1, 2021
`
`Sheet 1 of 14
`
`US 11,025,573 B1
`
`&
`
`¥
`
`=
`Yy &8
`- C
`e
`w
`- &
`st
`]
`&
`k
`o~ =t
`mn] wedy
`B . =
`] ]
`[
`y
`®
`®
`
`COMMUNICATION
`
`FiG. 1
`
`APPLE
`EXHIBIT 1001 - 0003
`
`
`
`
`
`
`
`
`U.S. Patent Jun. 1, 2021 Sheet 2 of 14 US 11,025,573 Bl
`
`=~ j/”‘<~\\
`N / N
`w 5 l\
`| <
`)
`. ™
`AU
`<
`o3
`N
`\N ——
`[a? \.._,j ®
`.
`. ////// :
`
`Ve 202
`'\\\
`S
`K
`S
`J
`
`>
`o
`
`APPLE
`EXHIBIT 1001 - 0004
`
`
`
`
`
`
`
`
`U.S. Patent Jun. 1, 2021 Sheet 3 of 14 US 11,025,573 Bl
`
`300
`302 -
`IDENTIFY USER DATA
`
`304 -
`
`\ y
`
`DETERMINE LOCATION OF USER
`DEVICES
`
`306
`
`2
`
`IDENTIFY POTENTIAL CONTACT
`WITHIN A PROXIMITY
`
`308 N ¥
`SEND COMMUNICATIONS TO INITIATE
`DATA SHARING
`310~ !
`
`EXCHANGE DATA
`
`FiIG. 3
`
`APPLE
`EXHIBIT 1001 - 0005
`
`
`
`
`
`
`
`
`U.S. Patent Jun. 1, 2021 Sheet 4 of 14 US 11,025,573 Bl
`
`412
`418
`
`FIG. 4
`
`—
`“
`
`402
`
`APPLE
`EXHIBIT 1001 - 0006
`
`
`
`
`
`
`
`
`U.S. Patent Jun. 1, 2021 Sheet 5 of 14 US 11,025,573 Bl
`
`FIG. 5
`
`APPLE
`EXHIBIT 1001 - 0007
`
`
`
`
`
`
`
`
`US 11,025,573 B1
`
`Sheet 6 of 14
`
`Jun. 1, 2021
`
`U.S. Patent
`
`9 DIA
`
`i
`
`YA ‘GLikYy e ‘woribug
`
`FGTY BLLRY uRiug
`
`709
`
`APPLE
`
`EXHIBIT 1001 - 0008
`
`
`
`
`
`
`
`
`U.S. Patent Jun. 1, 2021 Sheet 7 of 14 US 11,025,573 Bl
`
`bl :
`b &
`- :
`e oo
`o oo
`¥ o
`S $a
`
`: 1389 P8
`ge2ot1d
`
`Brobis,
`
`Work
`
`FiG. 7
`
`APPLE
`EXHIBIT 1001 - 0009
`
`
`
`
`
`
`
`
`US 11,025,573 B1
`
`Sheet 8 of 14
`
`Jun. 1, 2021
`
`U.S. Patent
`
`TERYY
`
`Ty
`IS
`
`pEo Ry
`
`WEOT BT i ussuliiy
`
`soetoy
`
`WeEREL B tones
`
`APPLE
`
`EXHIBIT 1001 - 0010
`
`
`
`
`
`
`
`
`US 11,025,573 B1
`
`Sheet 9 of 14
`
`Jun. 1, 2021
`
`U.S. Patent
`
`W B
`
`6 DIA
`
`/
`Dy IBHS O
`
`i
`
`stsonhoy
`i/
`
`e Lopndacy g
`
`s165nhaL;
`
`>
`
`e
`
`\
`Y
`\
`
`AN
`
`~..
`
`APPLE
`
`EXHIBIT 1001 - 0011
`
`
`
`
`
`
`
`
`U.S. Patent Jun. 1, 2021 Sheet 10 of 14 US 11,025,573 Bl
`
`1012
`
`FIG. 10
`
`1004
`
`1002
`
`APPLE
`EXHIBIT 1001 - 0012
`
`
`
`
`
`
`
`
`US 11,025,573 B1
`
`Sheet 11 of 14
`
`Jun. 1, 2021
`
`U.S. Patent
`
`(03 3200750y
`YT TLT-CLT
`ctii-fii-ttt
`
`182404 T 1
`
`A
`
`[ OIA
`
`WO 0330l
`LLTTTLTTLL
`PPEI-TEI-TRY
`
`U €11
`rapuuef
`
`W00 003)3¢
`LT LTLTLL
`PEEE-TEE-TTE
`
`UIBIA 11
`Apeig
`
`APPLE
`
`EXHIBIT 1001 - 0013
`
`
`
`
`
`
`
`
`US 11,025,573 B1
`
`Sheet 12 of 14
`
`Jun. 1, 2021
`
`U.S. Patent
`
`COTO-TCI-1 11 =Hqo
`. S L
`
`STI8Y [N JOiy uuy
`QAY U 7T
`WD 00 JUOY
`
`AT YA R R RIS A
`e e SUTOF
`
`UORBULIOIU] 109T0)) APy
`
`¢l Did
`
`W0 32310y
`PCCTTTTIlL
`cUHI-THE-TE
`
`182104 €71
`Ae™p
`
`APPLE
`
`EXHIBIT 1001 - 0014
`
`
`
`
`
`
`
`
`US 11,025,573 B1
`
`Sheet 13 of 14
`
`Jun. 1, 2021
`
`U.S. Patent
`
`WO 330 @SO
`STTC-TTT-TTL
`Stel-tel-igl
`
`1706 VO V1
`
`IS YREN 71
`
`SISNN]
`
`£ 'DIA
`
`O oueD
`
`LANIIS SIY) MOJIO)
`01 jem 1ok o
`
`WO IDDISHIA
`SCEL-CTTTLL
`
`stei-iei-iet !
`
`E1T06 VO 'V
`
`18 UIN £71 W
`
`APPLE
`
`EXHIBIT 1001 - 0015
`
`
`
`
`
`
`
`
`U.S. Patent Jun. 1, 2021 Sheet 14 of 14 US 11,025,573 B1
`
`1414
`
`FIG. 14
`
`1404
`
`APPLE
`EXHIBIT 1001 - 0016
`
`
`
`
`
`
`
`
`US 11,025,573 Bl
`
`1
`METHOD AND APPARATUS FOR DATA
`SHARING
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`This application is a continuation-in-part of U.S. appli-
`cation Ser. No. 15/217,424, filed Jul. 22, 2016, which claims
`the benefit of U.S. Provisional Application Nos. 62/195,534,
`filed Jul. 22, 2015, and 62/234,246, filed Sep. 29, 2015, each
`of which is incorporated herein by reference in its entirety.
`
`TECHNICAL FIELD
`
`The present disclosure relates to data sharing, including
`sharing contact information, and determining potential can-
`didates for data sharing between devices based on relative
`proximity of the devices.
`
`BACKGROUND
`
`Exchange of personal and professional contact informa-
`tion with another via business cards is on the decline, while
`digital contact information exchange is now trending. Social
`media tools are focused around an online forum rather than
`live meetings. There is a need for exchanging digital contact
`information immediately or upon request, such as in an
`impromptu situation or event, and for controlling future
`access to the exchanged information.
`
`SUMMARY
`
`Afirst aspect is a method for data sharing between devices
`in a network. The method includes identifying, for a user
`associated with a user device, a potential contact; receiving,
`from the user device of the user, a request for the user to
`become a contact with the potential contact; and sending,
`based on the request, a communication to the potential
`contact to initiate a data exchange. The user is associated
`with user data, and the potential contact is associated with
`contact data. The request includes a first permission setting,
`the first permission setting is at least a first value or a second
`value; the first value indicates that a subset of user data of
`a permitting user is to be shared with a permitted user; and
`the second value indicates that only chats are allowed from
`the permitted user to the permitting user. The method also
`includes, in response to receiving, from the potential con-
`tact, an acceptance of the communication, setting the user as
`a contact of the potential contact such that the subset of the
`user data is viewable to the potential contact in a case that
`the first permission setting being the first value; and setting
`the potential contact as a contact of the user.
`
`A second aspect is a system for data sharing between
`devices in a network. The system includes a processor and
`a memory. The memory includes computer-executable
`instructions that, when executed by the processor, perform
`operations including identifying, for a user associated with
`a user device, a potential contact, the user is associated with
`user data, and the potential contact is associated with contact
`data; receiving, from the user device of the user, a request for
`the user to become a contact with the potential contact, the
`request includes a first permission setting, and the first
`permission setting is at least a first value that indicates that
`a subset of user data of a permitting user is to be shared with
`a permitted user; and sending, based on the request, a
`communication to the potential contact to initiate a data
`exchange. The operations also include, in response to receiv-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`
`ing an acceptance of the communication, setting the user as
`a contact of the potential contact, the subset of the user data
`is viewable to the potential contact in a case that the first
`permission setting is the first value; and setting the potential
`contact as a contact of the user.
`
`A third aspect is another method for data sharing between
`devices in a network. The method includes receiving, from
`a potential contact, a first location. The method also
`includes, in a case that a second location of a user device of
`a user matching the first location, identifying, for the user,
`the potential contact; receiving, from the user device, a
`request for the user to become a contact with the potential
`contact, the request includes a permission setting, the per-
`mission indicates whether a subset of user data of the user
`can be viewed by the potential contact; sending, based on the
`request, a communication to the potential contact to initiate
`a data exchange; and, in response to receiving an acceptance
`of the communication: setting the user as a contact of the
`potential contact, the subset of the user data is viewable to
`the potential contact in accordance with the permission; and
`setting the potential contact as a contact of the user.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The invention is best understood from the following
`detailed description when read in conjunction with the
`accompanying drawings. It is emphasized that, according to
`common practice, the various features of the drawings are
`not to-scale. On the contrary, the dimensions of the various
`features are arbitrarily expanded or reduced for clarity.
`
`FIG. 1 is a diagram of an example of an apparatus for data
`sharing in accordance with implementations of this disclo-
`sure;
`
`FIG. 2 is a diagram of an example of a system for data
`sharing between devices based on relative proximity in
`accordance with implementations of this disclosure;
`
`FIG. 3 is a flowchart diagram of an example of a method
`for data sharing between devices of FIG. 2 based on relative
`proximity in accordance with the implementations of this
`disclosure; and
`
`FIG. 4 is a diagram of an example of a user interface for
`in accordance with implementations of this disclosure.
`
`FIG. 5 is a diagram of an example of a user interface
`display for detecting contacts automatically in accordance
`with implementations of this disclosure.
`
`FIG. 6 is a diagram of an example of a user interface
`display for selecting user data for data sharing in accordance
`with implementations of this disclosure.
`
`FIG. 7 is a diagram of an example of a user interface
`display for identifying a potential contact based on location
`in accordance with implementations of this disclosure.
`
`FIG. 8 is a diagram of an example of a user interface
`display for identifying a potential contact by scan code in
`accordance with implementations of this disclosure.
`
`FIG. 9 is a diagram of an example of a user interface
`display for sharing user data by scan code in accordance
`with implementations of this disclosure.
`
`FIG. 10 is a diagram of an example of a user interface
`display for selecting location data for data sharing in accor-
`dance with implementations of this disclosure.
`
`FIG. 11 is a diagram of an example of a user interface
`display of user data of listed registered contacts in accor-
`dance with implementations of this disclosure.
`
`FIG. 12 is a diagram of an example of a user interface
`display for changing data sharing in accordance with imple-
`mentations of this disclosure.
`
`APPLE
`
`EXHIBIT 1001 - 0017
`
`
`
`
`
`
`
`
`US 11,025,573 Bl
`
`3
`
`FIG. 13 is a diagram of an example of a user interface
`display for following registered users in accordance with
`implementations of this disclosure.
`
`FIG. 14 is a diagram of an example of a user interface
`display for following registered contacts in accordance with
`implementations of this disclosure.
`
`DETAILED DESCRIPTION
`
`Various aspects of this disclosure are now described with
`reference to the drawings. In the following description,
`numerous specific details are set forth in order to provide a
`thorough understanding of one or more aspects. It should be
`understood, however, that certain aspects of this disclosure
`may be practiced without these specific details, or with other
`methods, components, materials, etc. In other instances,
`well-known structures and devices are shown in block
`diagram form to facilitate describing one or more aspects.
`
`The present disclosure presents methods and apparatuses
`for detecting the proximity of contacts relative to a user and
`sharing contact information between the user and one or
`more detected contacts. A user of the disclosed method and
`apparatus, including without limitation computer readable
`instructions executable by the processing unit of the elec-
`tronic device present disclosure (collectively, the “applica-
`tion”; noting, however, that said term may also include
`further embodiments as may hereinafter be described or
`referenced), may receive contact and other information and
`data (collectively, “user data”) from detected contacts (i.e.,
`other users) and send their own user data thereto based in
`part on the types of information each user elects to share, the
`nature of the relationship between the users, and the condi-
`tions under which any user data may be shared. Generally,
`each user may receive user data from and transmit user data
`to other users, for example, by way of a server in commu-
`nication with each user device, thereby resulting in a real-
`time exchange of user data, subject to any limitations as may
`be imposed by each user.
`
`As used herein, the term “user” includes individuals and
`entities using the application, for example, at least based on
`the existence of an account profile belonging thereto. As
`used in the singular form, “user” may refer to a human user
`by example. As used in the plural form, “users” may refer to
`one or more potential contacts and/or registered contacts.
`Notwithstanding the foregoing, it will be apparent that
`“user” may include various other embodiments as may
`hereinafter be described or referenced.
`
`FIG. 1 is a diagram of an example of an apparatus for
`detecting contact proximity and sharing contact information
`in accordance with implementations of the present disclo-
`sure.
`
`A user device 100 for detecting contact proximity and
`sharing contact information may include a processing unit
`110, a memory unit 120, a location component 130, a
`communication component 140, a user interface unit 150, or
`a combination thereof. The user device 100 may be an
`electronic device, which may be, without limitation, a smart-
`phone, personal digital assistant, tablet computer, laptop
`computer, desktop computer or other Internet-connectable
`device.
`
`The processor 110 may be one or more various computer
`processors used to process data and perform computing
`tasks including without limitation a central processing unit
`(CPU) 112, and/or a graphical processing unit (GPU) 114 as
`shown in FIG. 1. In some embodiments, the CPU 112 or
`GPU 114 may be implemented as a microcontroller, micro-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`
`processor, or an application specific integrated circuit
`(ASIC), or a combination thereof.
`
`The storage memory 120 may be one or more various
`volatile and nonvolatile memory types including without
`limitation random access memory, read only memory, flash
`memory or other removable/non-removable storage media.
`The storage memory 120 may include a system memory
`module that may store executable computer instructions
`that, when executed by the processor 110, perform various
`user device functionalities including those described herein.
`The storage memory 120 may store data, including user
`account information or contact information, entered by the
`user via user interface unit 150 or received from the com-
`munication component 140.
`
`The location component 130 may include, for example, a
`global positioning system module or geolocation module,
`which, based on its configuration, may be in communication
`with satellite or other external systems for tracking the
`location of an electronic device. In some embodiments, the
`positioning data received by the location component 130
`may be one or more of a set of coordinates and a common
`address (e.g., a street address along with corresponding city,
`state/province/country information). The location compo-
`nent 130 may identify a location of the user device 100 using
`positioning data. The communication component 140 may
`send and receive electronic data including, for example, user
`data. The user interface unit 150 may maintain the user’s
`account profile and user data and the user data of other users,
`as well as receiving user commands to be processed.
`
`The communication component 140 may include, for
`example, a modem or other hardware module or adapter for
`connecting the electronic device to a network, such as an
`intranet, local network, or the Internet, either through a
`physical connection (e.g., Ethernet) or wireless connection
`(e.g., Wi-Fi). In some embodiments, the communication
`component may connect the user device to, and thereafter
`communicate with, a server and/or one or more other user
`devices.
`
`The user interface unit 150 may include one or more units
`that may register or receive input from a user or present
`outputs to the user, such as a display, touch interface, a
`proximity sensitive interface, a light receiving/emitting unit,
`sound receiving/emitting unit, a wired/wireless unit, or other
`units. In some embodiments, the user interface unit 150 may
`include a display, one or more tactile elements (e.g., buttons
`or virtual touch screen buttons), lights (e.g., LED), speakers,
`or other user interface elements. The user interface unit 150
`may receive user input and provide information to a user
`related to operation of the user device 100. The interface unit
`150 may include, for example, part of a software application
`installed on and executed by the processor 110 and config-
`ured to receive and store user data, contact data and other
`information stored in the memory 120.
`
`In some embodiments, the user interface unit 150 may
`include a display screen, such as a touch screen, for dis-
`playing content and receiving user commands to be pro-
`cessed. The user interface unit 150 may be supported by one
`or more input configurations including without limitation a
`keyboard and/or mouse configuration, a touchscreen con-
`figuration, and a microphone and speaker configuration. In
`some embodiments, the user interface unit 150 g may
`include user-selected customization features for creating and
`maintaining user data in an account profile. For example, the
`user interface unit 150 may include graphical features to
`enable the user to establish settings data, which may include
`various settings for modifying or limiting certain aspects of
`the software application.
`
`APPLE
`
`EXHIBIT 1001 - 0018
`
`
`
`
`
`
`
`
`US 11,025,573 Bl
`
`5
`
`The user data, the contact data, the settings data, or a
`combination thereof, may be stored within the storage
`memory 120 of the user device 100, within non-transient
`memory contained within the server, or a combination of
`both. For example, data associated with the user account
`profile may be input using the user interface unit 150, which
`may be immediately stored in storage memory 120 of the
`user device 100, and may be transmitted via the communi-
`cation component 140 to a network server for storage in the
`network database within the server memory. The user data,
`contact data, and settings data may be communicated to the
`server periodically or in response to data changes, for
`example, to update contact data registered with various users
`or record select user preferences.
`
`The account profile of the user may include user data of
`the user, which is viewable at least in part by certain other
`users. For example, “registered contacts” referred herein as
`network users with whom user data is being shared with the
`user, may view user data of the user. In some embodiments,
`the account profile may comprise various graphical features.
`For example, a picture (which may include without limita-
`tion a photograph, a computer generated image, a solid
`color, or a patterned image) may be uploaded to use as the
`background for the user account profile, or a picture may be
`retrieved from a library provided by the application or
`server. In some embodiments, the various media files, such
`as video, audio and picture files, may be uploaded to the
`account profile and made available for viewing by other
`users. For example, an entity user may upload commercials
`or other marketing materials to the account profile to pro-
`mote goods and services to potential customers.
`
`The user data may include information relative to an
`account profile of a user and may comprise name, title,
`company, availability status, account picture, phone and
`mobile numbers, mailing addresses, email addresses, fac-
`simile numbers, social media links, websites, birthday, anni-
`versary, and/or other information associated with the user.
`The user data may be received from a user interface. In some
`embodiments, user data may further include present and past
`location data for the user. The user data may be organized
`into one or more profiles (e.g., a work profile comprising the
`user’s business contact information and a home profile
`comprising personal contact information), to permit the user
`to conveniently elect for only certain profiles to be publicly
`viewable, and/or to distinguish professional and personal
`user data for presentation to other users.
`
`The contact data may include user data relative to regis-
`tered contacts, which may be viewable by the user, for
`example, as a contact list accessible within the application.
`In some embodiments, the registration of further contact
`data or modification of existing contact data for a registered
`contact may be automatic according to user-based configu-
`ration by the user. In some embodiments, the registration of
`further contact data or modification of existing contact data
`for a registered contact may be received from a user inter-
`face in response to user entry. As an example of automatic
`modification, a registered contact of the user may elect to no
`longer share certain contact data with the user, permissions
`for the contact data relative to the user may be changed by
`the registered contact, thereby causing that contact data to no
`longer be viewable by the user. The contact data may be
`organized into one or more profiles as set by the correspond-
`ing user.
`
`The settings data may include settings configured by the
`user device in accordance with selections by the user. In
`some embodiments, the settings data may be input to the
`user device via a user interface, such as the user interface
`
`20
`
`25
`
`40
`
`45
`
`60
`
`65
`
`6
`
`unit 150 of FIG. 1. For example, an application may be
`executed to graphically display various configurable settings
`on a touch screen, and in response to user input, record and
`save the settings data to a memory of the user device, such
`as the memory 120. The settings data may be sent to a
`network server and stored in a memory unit of the network
`server as parameters when executing data sharing and detec-
`tion of potential contacts in accordance with this disclosure.
`In some embodiments, the settings data may include a
`proximity range setting, a detection preferences setting, a
`user data setting, or a combination thereof.
`
`The proximity range setting may indicate a particular
`proximity range relative to the user device location, within
`which searching and detecting of other users may be
`executed, such as searching and detecting potential contacts
`for the user within a two mile radius of the user’s present
`location. In some embodiments, a network server may
`receive the proximity range setting from the user device, and
`may identify other users concurrently located within prox-
`imity of the user corresponding to the proximity range
`setting. In some embodiments, the user device may include
`a location detection function that uses peer-to-peer signals
`with a user device of another user located within a proximity
`of the user as defined by the proximity range setting. The
`proximity range setting may be fixed and unchangeable, or
`may be adjustable by the user.
`
`The detection preferences setting may be defined by the
`user and may identify other users individually or a classi-
`fication of users as potential contacts to be detected within
`the proximity range. For example, the detection preferences
`setting may be set to allow all users to be detected, or it may
`instead allow only certain selected users (e.g., entities that
`are restaurants, users identified by a first name, age, or
`gender, or other criteria) to be detected.
`
`The user data setting may indicate the degree to which the
`user data (or specific portions thereof) is viewable by other
`users. In some embodiments, the user may define all or
`select portions of the user data as being public user data (i.e.,
`automatically viewable by other users) or private user data
`(i.e., only viewable by other users upon the user granting
`permission therefor). The user may modify the user data
`setting from an initial setting. For example, the user data
`setting for a portion of the user data may be changed from
`public user data to private user data, and vice versa.
`
`Based on the settings data, the server may detect other
`users located within the defined proximity range. Users who
`have not previously shared user data with the user, as well
`as users who have, but who no longer are sharing user data
`with the user, may be defined as “potential contacts.” Users
`who are currently sharing user data with the user may be
`defined as “registered contacts.” In some embodiments,
`upon detecting a potential contact, the user may send an
`exchange request to the potential contact by electing to share
`all user data, some user data, or no user data with the
`potential contact, provided that user data defined as public
`may automatically be shared upon initiating the exchange
`request. Upon the potential contact and the user each agree-
`ing to share user data with one another, the user and the
`potential contact each become registered contacts to one
`another, and user data of the potential contact may be shared
`with the user as contact data and vice versa. In some
`embodiments, the user and a potential contact or registered
`contact may elect to enter into a private chat wherein they
`may communicate messages to each other.
`
`FIG. 2 is a diagram of an example of a system for data
`sharing between devices based on relative proximity in
`accordance with implementations of the present disclosure.
`
`APPLE
`
`EXHIBIT 1001 - 0019
`
`
`
`
`
`
`
`
`US 11,025,573 Bl
`
`7
`
`In some embodiments, a system 200 may include a user
`device 202, which may be configured as shown and
`described herein with reference to user device 100 in FIG.
`1. The system 200 may also include one or more other user
`devices 212, a network access point 222, and a network
`server 232. The system 200 may also include communica-
`tion links 204/214/224 and network 234.
`
`The user device 202 may communicate with the network
`entities via communication link 204, and may access the
`network server 232 via a network or internet connection 234.
`The one or more other user devices 212 may be located
`within the proximity range as defined by the proximity range
`setting. In some embodiments, the user device 202 may
`communicate with the network server 232 to set up the
`account profile of the user and to upload the settings data
`onto the network server 232. The network server may detect
`the one or more user devices 212 as being associated with
`potential contacts for the user of user device 202 in response
`to an action by the user. For example, the user may open or
`start an application on the user device 202, which may
`automatically send a signal on communication link 204 to
`the access point 222 and forwarded to the network server
`232 over the internet or network 234. The signal may include
`the location data and/or the settings data of the user device
`202. Meanwhile, one or more other users registered with the
`network on associated user devices 212 may have commu-
`nicated respective location data to the network server on
`communication link 214 via the access point 222 and the
`network 234. Based on the location data and/or settings data
`received from the user devices 202/212, the network server
`232 may identify one or more user devices 212 as being
`located within the proximity range as set by the user device
`202, and as such, are identified as potential contacts for the
`user of user device 202. In some embodiments, the user
`devices 202/212 may exchange location data directly, such
`as through a peer-to-peer communication link 224, which
`may then be transmitted to the network server 232.
`
`In some embodiments, the user device 202 may receive an
`indication from the network server 232 of user devices 212
`associated with potential contacts, as identified by the net-
`work server 232. The user device 202 may display the
`potential contacts on a user interface, from which a potential
`contact may be selected for exchanging user data such as
`contact information. The user device 202 may send the
`potential contact selection to the network server via the
`communication link 204. In response to the potential contact
`selection, the network server 232 may send a request to the
`user device 212 of the potential contact for exchanging
`contact information with the user of user device 202. If the
`potential contact agrees to exchange data with the user of
`user device 202, the data sharing may be transmitted via the
`networ