`
`EXHIBIT 1013 - PAGE 0321
`
`APPLE
`
`

`

`
`
`
`
`If block 733410638-31 determines the-custemtaunchistouseanApplicationInterfaceProsramming
`
`-
`
`
`
`
`
`appleatienfield 9850 c is exclusively for an application information type, block 10638-
`33 prepares presentation parameters using block 10610 reconciliations andfirst invoking
`the FIG. 26 procedure for resolving the specified application information. LRDR information may
`be used to skip
`presentation processing
`(e.g. no presenting at WS whereabouts described by a
`LRDR),
`therefore a skip
`return is checked for at block 10638-35. After resolving
`the application
`information, block 10638-33 finalizes the message and block 10638-35 presents the message in
`accordance with other MADR fields if no skip was to be processed. Block 10638-33 is capable
`of many format transformations in order to get the target presentation format. Active call line
`play was preferably handled with an API in FIG. 25A, and active call information preferably need
`not be used at block 10638-35, for example to provide information during an active call,
`however block 10638-35 can interface for output using architecture of FIG. 22. Processing
`leaves block 10638-35 for block 10638-39. If block 10638-31 determines field 9850 c is not for
`an_application information type, processing continues to block 10638-37 where other MADR
`
`EXHIBIT 1013 - PAGE 0322
`
`APPLE
`
`

`

`types(if defined) are processed appropriately, and processing continues backto
`
`block 739610638-39.
`
`EXHIBIT 1013 - PAGE 0323
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0324
`
`APPLE
`
`

`

`
`
`
`
`
`
`FIG. 7626 depicts a flowchart for describing a preferred embodiment ofprocessingespecialterm
`
`
`
`
`
`
`
`bleck7622-application information resolution processing, for example as invoked by
`blocks 10628, 10638-15, 10638-21, 10638-27, 10638-33 and 10638-37. Processing begins at
`block 10702, continues to block 10704 for accessing
`parameters passed (e.g. MADR, sender
`recipient, CLOC), and block 10706 for starting the checks for which application information has
`been specified. If block 10706 determines application information is for presenting the current
`MS location information, block 10708 gets the current MS (of FIG. 26 processing) whereabouts
`of a reasonable confidence and processing continues to block 10710. If block 10710 determines
`
`a confident whereabouts of the MS could not be determined,
`then block 10712 uses MADR
`information to form an appropriate “status unavailable” message for presentation and
`processing returns to the invoker at block 10714 for not skipping the presentation. If
`block 10710 determines the MS location (whereabouts) was determined,
`then
`block 10716 checks the application information for being qualified for using LRDR information to
`
`EXHIBIT 1013 - PAGE 0325
`
`APPLE
`
`

`

`enhancethe presentation message (e.g. use user friendly description field 9860d)in which
`case processing continues to block 10720, otherwise block 10718 forms an appropriate
`message containing
`location information in as informative terms as possible (some
`embodimentsjust report latitude and longitude which is not very informative), and processing
`continues to block 10714. Block 10720 accesses LRDRs 9860 for a match to whereabouts from
`block 10708, and processing continues to block 10722. If block 10722 determines the MS
`whereabouts match the location of a LRDR (uses encoding field 9860 c using type field 9860 b),
`then processing continues to block 10726, otherwise processing continues to block 10724.If
`block 10726 determines the application information qualified using LRDR information to make a
`moreinformative message, then block 10728 uses description field 9860 d of the matched
`LRDR to provide a user friendly whereabouts message of where the MS is currently located
`(e.g. use Convenient waymarkinformation description to describe the current MS whereabouts
`to: a caller for OGM processing or callee for OCM processing),
`and processing continues to
`block 10714. Block 10726 will continue to block 10732 if arrived to by way of block 10730. If
`block 10724 determines a LRDR should be used to qualify MS whereabouts (however no LRDR
`match was found), then processing continues to block 10718. Block 10724 will continue to
`block 10714 if arrived to by way of block 10730. Returning back to block 10706, if
`block 10706 determines application information is not for presenting the current MS location
`
`information, then processing continues to block 10730.
`
`EXHIBIT 1013 - PAGE 0326
`
`APPLE
`
`

`

`
`
`If block 10730 determines application information is for using LRDR information to potentially
`skip providing the presentation, then processing continues to block 10708 for processing as
`described abovewith the following exceptions:
`
`lO|lole
`
`lo
`
`1) Block 10716 continues unconditionally to block 10720:
`2) Block 10724 continues to block 10714 when no LRDR match wasfound for
`the current MS whereabouts(i.e. do not skip
`the presentation): and
`3) Block 10726 continues unconditionally to block 10732 for returning to the
`invoker for skipping
`the MADR presentation entirely
`(when a LRDR match was
`found). This
`provides the user with a way
`to use waymark information for definin
`where not to have a presentation.
`
`If block 10730 determines application information is not for checking to skip the presentation,
`then processing continues to block 10734.
`
`EXHIBIT 1013 - PAGE 0327
`
`APPLE
`
`

`

`If block 10734 determines application information is for accessing MS user status from_an
`external application (e.g. Facebook, Twitter),
`then processing continues to block 10736 for
`accessing the status, preferably through an API. Other embodiments can force a userinterface
`refresh from the external application (e.g. load html
`page)
`in order to access data therein for
`obtaining status. Thereafter, if block 10738 determines useful status was found, then
`block 10740 builds an informative message with the status and processing continues to
`block 10714, otherwise processing continues to block 10712. If block 10734 determines
`application information is not for accessing MS user status from an external application, then
`
`processing continues to block 10742.
`
`
`
`
`
`
`enablinganyapplicationsubsetsofdatainfield1100lf block 10742 determines application
`information is for accessing information about MS usersin the vicinity and “in common”with the
`MS of FIG. 26 processing, then processing continues to block 10744 for accessing locally
`maintained whereabouts information for the specified numberof users in the vicinity of the MS
`of FIG. 26 processing. Application information specifications for nearby “in common” person(s
`include a number of nearby MS users (1 or more), and a distance measurement in convenient
`units for how nearby(e.g. 25 feet). Thereafter, block 10746 accesses permissions granted to
`both the sender passed to FIG. 26 processing (if not null) and each userfoundin the vicinity of
`the MS (user) of FIG. 26 processing. Granted permissions are one embodimentfor determining
`the “in common”condition. Other embodiments will access contactlists, call history, email
`history, SMS history, the like, or combination thereof, to determine the “in common” condition.
`Thereafter,
`if block 10748 determines that the sought number (e.g. 1) of “in common” MSsin the
`
`then block 10750 builds an informative message
`(within specified distance) are found,
`vicinity
`with useridentifier information, for example to inform to call someone else nearby.
`Block 10750 preferably uses source section 8002 a to build a messagewith the bestidentifier
`information depending on the messagetype field 9850 _b. Processing leaves block 10750 for
`block 10714. If block 10748 determines the sought number of nearby
`person(s) “in common”
`have not yet been found, then processing continues back to block 10744 for checking for
`additional MSsin the vicinity. Blocks 10744, 10746 and 10748 stay in a loop until MSs are
`identified, or there are not enough of them in the vicinity meeting specifications.
`Block 10750 also builds a messageindicating there is no status available and no people “in
`common” nearby that may help. If block 10742 determines application information is not for
`accessing MS user information for nearby
`person(s)
`in common,
`then processing continues to
`block 10752.
`
`EXHIBIT 1013 - PAGE 0328
`
`APPLE
`
`

`

`
`toblock10760.
`
`If block 10752 determines application information is for accessing the current MS date/time
`information, block 10754 accessesthe current MS time and processing continues to
`block 10758 through block 10756 for building a message containing date/time information.
`Thereafter, processing continues to block 10714.If block 10752 determines application
`information is not for accessing the current MS date/time information, then processing continues
`
`EXHIBIT 1013 - PAGE 0329
`
`APPLE
`
`

`

`
`
`block 10760 determines application information is for accessing MS user calendar information,
`block 10754 accesses the current MS time and processing continues to block 10762 through
`block 10756 for accessing a calendar information scheduled for the current time. Thereafter,if
`block 10764 determines a calendar entry matches the current time, then block 10766 builds a
`message containing the informative scheduled calendar information and processing continues
`to block 10714, otherwise processing continues to block 10712. If block 10760 determines
`application information is not for accessing the calendar information, then processing continues
`to block 10768. An alternate embodiment supports
`qualifying
`the application information for
`calendar accesswith identifier information identifying the ownerof the calendarinformation to
`
`be accessed.
`
`netselectte-enable ore i
`id-
`If block 772610768 determines they
`
`
`te-field1100kapplication informationis foraccessing the current‘applicationinin usee at the Ms,
`
`block 10770 accesses the currently focused application information (e.g. title-bar information
`application name, description field information 5300 b, or other informative data),
`block 10772 builds an informative message using the information found, and processing
`
`continues to block 10714. If no focused information could be determined,
`then default a
`message is built at block 10772 (e.g. message as to user is busy using MS). If
`block 10768 determines application information is not for accessing the current application in
`
`
`
`
`use,then processingcontinues to block 7430-1block7730determinestheuserselectedteexit AG.
`
`
`
`EXHIBIT 1013 - PAGE 0330
`
`APPLE
`
`

`

`If block 10774 determines application information is for overriding a message with CLOC
`information, block 10776 accesses a confident MS (of FIG. 26 processing) whereabouts.
`
`Thereafter,
`if block 10778 determines a confident whereabouts could not be determined,
`then
`processing continues to block 10714 for normal processing of the field 9850 c, otherwise
`block 10780 overrides (replaces)
`any message in field 9850 ¢ with an informative message that
`the sender/caller is nearby if the MS of FIG. 26 processing is nearby the CLOC associated with
`the sender/caller. A preferred embodiment allows qualifying with a specification for a distance in
`convenient units for how close to denote being nearby. Block 10780 will not override message
`field 9850 c if CLOC is null, orif the nearby condition is not true. If the CLOC is nearby the
`whereabouts determined at block 10776, then an informative messageis built that the senderis
`nearby, perhaps with how nearby using the qualifier specification in the message. Thereafter,
`processing continues to block 10714. If block 10774 determines application information is not
`for overriding a message with CLOC information, then processing continues to
`block 10782 where other application information types (if defined) are resolved, and processin
`continues to block 10714. In one example, a CLOC override is useful for letting a remote caller
`know they are within shouting range.
`
`MS whereabouts (e.g. at blocks 10708, 10776, etc) are determined using the MS GPSinterface,
`a WDR queuedisclosed in the parent applications, a location retrieval interface, or any other
`MS resource for determining the location of the MS.
`
`An alternate embodiment defines a new use field 9860 f containing what application information
`the LRDR is to be used for (e.g. bit field mask like use field 9850 d for: presentation skippin
`and/or location reporting and/or specific map application use, etc).
`
`The sender orcaller, and recipient or callee, can take on a variety of identifier embodiments.
`Whenprovided in a form which should be transformed to another form for proper comparison or
`processing, source section 8002 a information can be used for cross application addressing to
`translate from oneidentifier form to another identifier form when necessary.
`
`are maintained for user configurations with FIG. 18 (e.g. each variety of
`Statistics and history
`MADR objects (and associated EFRs) created, deleted and modified for distinct settings in any
`record fields), varieties of MADR objects sent with FIG. 10A and received with FIG. 10B (e.g.
`eachvariety of MADRs (and associated EFRs) based ondistinct settings in any recordfields),
`observerand originator configurations through FIG. 24 (e.g. each variety of events configured),
`varieties of MADR objects sent with FIG. 13A and received with FIG. 13B (e.g. each variety of
`MADRs(and associated EFRs) based on distinct settings in any MADR fields), varieties of
`events which occur for searching MADRs and which varieties of MADRs and EFRs are matched
`along with event date/time information, observer and originator configurations for reconciliation
`and how reconciled, MADR varieties which are presented along with date/time information,
`varieties of AD event configurations received by FIG. 10B, errors which are encountered or
`unanticipated, or criteria of any other processing block or data. An LBS service informant may
`also be used to inform a service of how MADR objects were used, maintained, presented, or
`processed ata MS.
`
`
`
`EXHIBIT 1013 - PAGE 0331
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0332
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0333
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0334
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0335
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0336
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0337
`
`APPLE
`
`

`

`
`
`
`
`populatinguseAtFDOA,AGA,MPTand/erwhereabeuts, MADRs do not contain an expression
`field 9850 g. Permissions
`(privileges)
`in
`place between the sender/caller and recipient/callee are
`completely relied upon for governing what conditional processing is to take place. In another
`embodiment, both the expression and privileges are used to determine what conditional
`processing is to take place, preferably with privileges having precedence over expression
`evaluation. Wherever permissions are used herein, they are enforced through the LBX modelof
`identifiers or groups of identifiers (e.g. field 9850 i may carry group information-+e-field 1100).
`
`
`
`
`Company name and/or product name trademarks used herein belong to their respective
`companies.
`
`EXHIBIT 1013 - PAGE 0338
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0339
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0340
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0341
`
`APPLE
`
`

`

`
`
`While various embodimentsof the present disclosure have been described above, it should be
`understood that they have been presented by way of example only, and notlimitation. Thus, the
`breadth and scopeof the present disclosure should notbe limited by any of the above-
`described exemplary embodiments, but should be defined only in accordancewith the following
`claims and their equivalents.
`
`EXHIBIT 1013 - PAGE 0342
`
`APPLE
`
`

`

`Summary report:
`Litera® Change-Pro for Word 10.8.2.11 Document comparison done on
`10/28/2021 11:54:29 AM
`
`IMoveTo—s—“‘“‘“‘“‘“‘(S:;S*™S™SCCCOCC*d
`Move To
`Table Insert
`FableDelete
`
`lO
`
`Style name: DLAPiper
`Intelligent Table Comparison: Active
`Original filename: C:\Users\jh33717\OneDrive - DLA Piper LLP (US)\Matter-
`BillJCo\Patents\word version of specification - 267 patent.docx
`Modified filename: C:\Users\jh33717\OneDrive - DLA Piper LLP (US)\Matter-
`BillJCo\Patents\8566839 specification.docx
`
`3969
`
`Table movesto
`Tablemovesfrom:
`
`Tablemovesfrom
`
`Embedded Graphics (Visio, ChemDraw, Imagesetc Ott(iti‘*”
`Embedded Excel
`:
`
`oO
`
`Total Changes:
`
`EXHIBIT 1013 - PAGE 0343
`
`APPLE
`
`