`
`EXHIBIT 1013 - PAGE 0201
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0202
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0203
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0204
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0205
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0206
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0207
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0208
`
`APPLE
`
`

`

` ”
`
`a“
`
`M”
`
`cca
`
`n”
`
`a“
`
`mn
`
`a“
`
`my
`
`“a
`
`a“
`
`n”
`
`a“
`
`”
`
`i
`
`EXHIBIT 1013 - PAGE 0209
`
`APPLE
`
`

`

`
`
`—*
`
`“a
`
`EXHIBIT 1013 - PAGE 0210
`
`APPLE
`
`

`

`
`
`a“
`
`mW
`
`a“
`
`HT
`
`”
`
`a“
`
`“
`
`a“
`
`u“
`
`a“
`
`ye,7
`
`ym
`
`yw
`
`.
`7
`
`:
`
`.
`7
`
`A ee
`
`:
`
`.7
`
`sn)
`
`.7
`
` ,
`
`ais
`
`EXHIBIT 1013 - PAGE 0211
`
`APPLE
`
`

`

`
`
`
`
`EXHIBIT 1013 - PAGE 0212
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0213
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0214
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0215
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0216
`
`APPLE
`
`

`

`
`
`aw
`
`EXHIBIT 1013 - PAGE 0217
`
`APPLE
`
`,
`
`a“
`
`n”
`
`;
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0218
`
`APPLE
`
`
`

`

`ice
`
`”
`
`a“
`
`al
`
`a“
`
`”
`
`”
`
`“a
`
`a”
`
`EXHIBIT 1013 - PAGE 0219
`
`APPLE
`
`
`
`
`

`

`
`
`a“
`
`n”
`
`a“
`
`wt
`
`. Fee
`
`EXHIBIT 1013 - PAGE 0220
`
`APPLE
`
`
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0221
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0222
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0223
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0224
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0225
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0226
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0227
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0228
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0229
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0230
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0231
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0232
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0233
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0234
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0235
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0236
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0237
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0238
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0239
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0240
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0241
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0242
`
`APPLE
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`any}CHARTERS2D0ist-10002.[fblock10092determinesthatEFR9855informationwas0092. ffromthe ck 10092 termines that EFR 9855 information w
`
`
`
`
`
`
`EFRs may be configured for a plurality of different applications.
`
`selected for being managed by the user, block 10094 interfaces with the userfor creating,
`deleting, modifying and maintaining EFRs 9855. The user may choose to save changesorexit
`han
`before
`continuing
`to block 10036 for terminating block
`9928
`pro
`ing, EFR
`tend to be application specific forfiltering events for MADR processing, howeverthe same
`
`EXHIBIT 1013 - PAGE 0243
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0244
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0245
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0246
`
`APPLE
`
`

`

`
`
`History field 9855 e is to be appropriately updated to reflect user configurations made at
`block 10094. While not explicitly shown, field 9855 e is used at block 10094 to enforce
`ermissions
`(privileges) between the user using FIG. 19 processing and the user who originated
`or last updated the EFR for what EFR alterations and managementis permitted to be
`erformed. Block 10094 provides
`errors
`to the user of FIG. 19 processing when a neede
`privilege has not been granted.
`
`If
`
`block 1
`
`2 determines the user
`
`did not select to manage EFRs,
`
`then processing continues
`
`lication was
`particular
`checking which
`4 starts the series of
`4. Block 1
`block 1
`to
`selected for management from block 9906options. If block 10004 determines the application to
`@ managed is the advertising
`application,
`block 1
`erforms advertising application
`configuration, for example data which may be found in section 8004 f_ and processing continues
`to block 10008. The userinterfaces at block 10008 to set how the advertising application will
`present AD MADR information. A preferred embodiment of block 10008 configure a user's
`presentation preferences for all MADR presentations, in particular since many of the MADRsfor
`any application may contain advertisement information,
`perhaps shared from another MS or
`
`system. Having
`
`block 1
`
`configure all MADR presentation reminds the user that advertisin
`
`is involved
`
`despite there being useful MADR configurations that
`
`do not involve
`
`advertising.
`
`can be set
`supports configuration outside of MADR data of a visual mode setting
`Block 10008
`here for the observer's preference of: full screen, dedicated user interface visual area, newly
`spawned window,
`pop-up
`(e.g. window) with “stolen” focus,
`title-bar area of currently focused
`window,useroriginator's intent, or other visual method for presenting MADR information. An
`audio modeSetting can also be setfor the observer's preference of: mix, preempt, or use
`
`th MADRwithth
`rver's
`preference
`for reconciling a
`t fit presentation of the MADR.
`i
`Permissions
`govern
`authoritative
`reconciliation when there
`onflict
`between the originator
`intent and the observer's preference. Block 10008 continues to block 10012.
`
`Block 10012 preferably accesses the most recent settings of Boolean variables for enablin
`
`preferabl
`is
`FIG. 19
`t
`whole. Each Boolean variabl
`in
`MADR pr
`maintained to an application term, referred to as AppTerm. An AppTerm waswell defined in the
`parent applications and was well described in context of the BNE grammar of FIGS. 8A through
`E
`FIG.
`8D). At
`blocks 10012, 10020,
`10026,
`10032 and 10034, Boolean variables
`ar
`
`EXHIBIT 1013 - PAGE 0247
`
`APPLE
`
`

`

`provided for enable/disable of all MADR processing (e.g. MADR_srch), enable/disable certain
`application MADR processing
`(e.g. MADR AD), or enable/disable certain subsets of application
`
`calendar).
`for
`(e.g. MADR COM-R-cal
`MADR processing
`Blocks 10012, 10020, 10026, 10032 and 10034 preferably use permissions to enforce what
`subsets of processing can be enabled or disabled.
`
`For example, the user can enable or disable all processing involving functionality provided by
`the messagerepository for any of: ADs, OGMs, OCMs, and COMs for inbound and/or outbound
`distributions in context of particular applications (advertisin
`hone, email, address book
`calendar,
`profile, emergency,
`rfid, statistics. appliance, etc). This
`provides a user with the abilit
`to enable or
`disable all of a category
`of message repository
`functionality as desired outside of
`activating/deactivating specific MADR fields 9850 j. Current setting(s) are accessed at
`block 10012 and preferably
`presented to the user. The user may
`change (e.g. toggle)
`the settin
`
`context
`
`of the
`
`particular
`
`lication of FIG. 19 processin
`
`r leave the current settings
`
`as
`
`within
`they are.
`
`Block 10012 provides the user with ability to enable/disable all MADR processing or any subset
`f AD and advertise application MADR processing. Processin
`ntinues to
`block 1
`where
`block 9928 processing terminates.If block 10004 determines the user did not select to manage
`the advertising application,
`processin
`ntinues to
`block 10014.
`
`lication
`phon
`the
`is
`man
`lication t
`th
`determines
`block 10014
`If
`block 10016 performs phone application configuration, for example data which maybe found in
`section 8002 fas described in the parent application. For example, a user interfaces at
`block 10016 to set how the phone application will behave. Block 10016 preferably accesses the
`most recent settings, and the user confirms or changes as desired. Thereafter,
`
`
`
`
`
`lock 10018 requestadesiredenables the user to specify how to OCM, an itionally saves
`
`
`
`
`ny
`
`key,
`
`changes before
`
`continuing
`
`to block 10020. The user
`
`can specify which user
`
`action
`
`(e.g. hot-
`
`touch screen action, etc) will request a default OCM, which user action will request the best
`
`specific referenced OCM (preferably usin
`select a
`fit OCM, and which user action will
`field 9850 a). The user action specified may also indicate whetheror not to wait for a recording
`delimiter prior to leaving the message, for any of the requests. For example, in a hot-key user
`
`action embodiment, a <ctrl-d> selects the default OCM. a <ctrl-b> selects the best fit OCM, and
`an <Alt> key
`pressed while followed by character(s) or number(s) maintained in an embodiment
`of fiel
`50 a selects the particular
`OCM. However, when the capital lock key
`is on,
`this
`
`touch
`Unique
`the m
`leaving
`prior to automatically
`limiter
`to wait for
`indicates
`motions may also be used. There are many different user actions which can be configured
`
`
`
`
`
`depending foradelimiter mayon the MS user interface. Waiting be implemented regardless
`
`e.g. no specific user action required), or may not be implemented at all
`(e.g. user waits for
`OGM). Depending on embodiments, block 10018 enables the user to select desirable user
`interface actions for making an OCM request. Block 10020 interfaces with the userfor
`managing Boolean variables for enable/disable of all MADR processing (e.g. MADR_srch),
`nable/disable OGM MADR opr
`in
`nable/disable OCM MADR pr
`in
`c
`
`nable/di
`
`|
`
`rtain subsets of
`
`phon
`
`lication MADR pro
`
`in
`
`.g. MADR COM-L-
`
`hone). Thereafter, block
`h
`rdidn
`|
`
`9928
`man
`
`pro
`
`he
`
`ing
`phon
`
`terminat
`lication,
`
`t block 10036. If block 10014 determin
`pr
`in
`ntin
`lock 10022.
`
`If block 10022 determines the application to be managed is the email application,
`block 10024 performs configuration of the email application, for example data which may be
`
`EXHIBIT 1013 - PAGE 0248
`
`APPLE
`
`

`

`found
`
`in section
`
`2
`
`cas
`
`described
`
`in the parent application. For example, a user interfaces at
`
`behave. Block 10024 preferably accesses the
`lock 10024 to set how the email application will
`most recent settings, and the user confirms or changesas desired. Thereafter,
`block 10026 interfaces with the user for managing Boolean variables for enable/disable of all
`MADR processing
`(e.g. MADR _srch), enable/disable all email application MADR processing or
`enable/disable certain subsets of email application MADR processing
`(e.g. MADR CONM-R-
`email). Thereafter, block 9928 processing terminates at block 10036. If block 10022 determines
`the user did not select to manage the email application, processing continues to block 10028.
`
`If block 10028 determines the application to be managedis the calendar application,
`be
`lock 1
`erforms configuration of the calendar application, for example data which may
`found in section 8002 d as described in the parent application. For example, a userinterfaces at
`block 10030 to set how the calendar application will behave. Block 10030 preferably accesses
`the most recent settings,
`and
`the user
`confirms
`or changes
`as desired. Thereafter
`block 10032 interfaces with the user for managing Boolean variables for enable/disable of all
`MADR processing
`(e.g. MADR_srch), enable/disable all calendar application MADR processin
`or enable/disable certain subsets of calendar application MADR processing. Thereafter,
`block 9928 processing terminates at block 10036. If block 10028 determines the user did not
`select to manage the calendar application, processing continues to block 10034.
`
`Block 10034 interfaces with the user to manage an other application analogously to applications
`above (e.g. email, calendar). Thereafter,
`processing continues to block 10036 where
`lock 9928
`processing
`terminates. Block 1
`4 handles other applications,
`such as
`those
`
`hown in FIG. 14,
`
`including COM configurations
`
`for analogous
`
`pr
`
`ing. COM-L-app MADR:
`
`via field
`
`9850 a) are utiliz
`
`n inbound
`
`and
`
`outbound
`
`distributions at the
`
`local MS,
`
`and COM-
`
`processed
`being
`distributions for
`re utilized on outbound
`9850
`MADRs(via field
`R-
`remote (receiving) MS, for example as specified by
`the sending
`user(i.e. for all applications
`“app’=SMS/texting, advertise, profile, ab, emergency,rfid, statistics, appliance, etc).
`
`at the
`
`preferred MADR
`FIG. 20 depicts a flowchart for a preferred embodiment of a procedure for
`processing of an event for generic applications described by rows 9894 for a particular
`application, such as email, calendar, advertise, phone, profile, ab, emergency,rfid, statistics,
`appliance, etc. Special application rows 9892 are described below. Processing begins at
`block 10102 upon an inbound or outbound event
`(e.g. at a MS) for a particular application, and
`ontinues to block 10104 where parameters are determined. Depending on implementation, an
`
`inbound
`
`event may
`
`occur when
`
`istribution is
`
`received,
`
`when
`
`istribution is
`
`acted
`
`upon
`
`(e.g.
`
`seen)
`
`by a user, or as is appropriate in designating an inbound event,
`
`preferably
`
`consistent
`
`ur when
`outbound event m
`an
`on implementation,
`nding
`lications. D
`ross M
`distribution is sent from the application, when a distribution is transmitted from the MS,or asis
`appropriate in designating an outbound event, preferably consistent across MS applications. An
`alternate embodiment maintains separate bits to field 9850 d for different varieties of COM types
`for distinguishing between a plurality of inbound or outbound event types for the same
`application. While FIG. 20
`demonstrates MADR pr
`ing
`of interest to
`this
`disclosure,
`
`it
`
`ociat
`email transport) for th
`.g.
`transport u
`understood that the
`houl
`distribution may also be used for carrying a MADR object to prevent two separate
`transmissions, for example in the case of COM-R processing. For example, a MADR object can
`h
`ial
`hmen
`n
`email which is
`then
`sent with an
`email
`delivery
`API.
`There are other embodiments for sending the COM-R MADR to a receiving system.
`
`EXHIBIT 1013 - PAGE 0249
`
`APPLE
`
`

`

`the event
`causing FIG. 20 invocation and
`arameter indicates which application is
`The a
`parameterindicates which event occurred that is associated to the application. The invoking
`application is assumedto take care of the inbound/outbounddistribution on its own so that FIG.
`20 is for MADR processing. Other embodiments will support handling of the distribution (e.g. to
`send it) and the MADR in the sameinvoked interface and/or transmission. The sender
`arameter is the sender of the application event
`(e.g.
`phone call caller, text message sender
`etc) and the recipient parameter is the recipient of the application event
`(e.g. callee, text
`message
`recipient,
`etc). In a preferred
`embodiment, criteria is a
`pointer to a text
`stream (email
`
`lendar item
`
`text message, text stream derived
`
`from _an
`
`active
`
`call,
`
`etc) which
`
`can
`
`data) for when the application eventis t
`mpare
`r
`.g. ki
`55
`to a fiel
`mpared
`be associated with matching EFR(s) to distribution information associated to the event.
`However, criteria can be any form which may be matched to EFR information. The CLOC
`parameter is CLOC information received with a distribution. Parameters may take on a variety of
`embodiments for passing the same information. The parameters sender, recipient, criteria and
`CLOC may or may not be null when FIG. 20 is invoked. In one embodiment,
`MADRs9850include additional fields for sender and recipient comparison information which
`can be used to access specific MADRsat block 10106.
`
`Thereafter,
`
`block 10106 accessesall active and un-expired MADRswith use field 9850 d for the
`
`lication and event. For example, each COM-L variety includes: COM-L-email
`rticular
`CON-L-
`CON-L-calendar, COM-L-phone, COM-L-advertise, COM-L-profile, COM-L-
`emergency,
`COM-L-rfid, COM-L-statistics, COM-L-appliance, etc:
`and
`an event
`can be either
`inbound or outbound. Block 10106 preferably sorts the MADRsfor ordered processing based on
`a select setof field settings in the MADRs. Block 10106 also uses Boolean variables set in FIG.
`19 to determine if any MADRs should be searched at all. Processing continues to block 10108.
`In one embodiment, block 10106first accesses all expired MADRs (checking data in
`
`field 9850f)and expires them (i.e. preferably inactivates, or discards).
`
`
`Block 10108 gets the next MADR for processing and block 10110 checksto seeif all MADRs
`from block 10108 have been processed, in which case processing continues to block 10118,
`otherwise processing continues to block 10112. One MADR is preferably found if any are found
`_a default), but none may
`be
`found. When a MADR is marked a default with default
`
`fiel
`
`50 e,
`
`expression fiel
`
`50
`
`robably null for this case)
`
`is assumed
`
`t
`
`True
`
`(i.e.n
`
`
`
`
`
`
`field 9850gcheck necessary) and processing will proceed to block 10192 via block 10114.
`
`
`Otherwise, block 10112 determines the Boolean result for expression field 9850 g preferablyin
`real-time by evaluating conditions of the expression using stack processing and accessto
`applicable terms. Thereafter, if block 10114 determines expression field 9850 g evaluated to
`True, then block 10192 accesses any joined EFRs to the MADR in process.
`
`
`Block 10192 determines:a)no EFRsare joined:b)one or more EFR(s) joined do not match
`criteria and/or CLOC information passed as parameters; or c) all EFR(s) joined match the
`criteria and CLOC information passed as parameters. Block 10192 compareslocation type
`EFRs
`to
`the CLOC parameter if not null,
`compares
`the ke
`rd(s)
`type EFRs
`to
`the criteria
`parameter, and comparesthe scheduling information type EFRsto the criteria parameter,if not
`
`null. The criteria parameter mayinclude a typefield for facilitating a match so multiple EFR
`th
`n
`join
`field
`i
`for interpre
`ion of
`h fiel
`nd
`
` Location e EFRsclari event handlin for a certain locationmatch, Ke s ord s es EFRs
`
`
`event handling for certain associated keywords, for example as contained in the
`
`clarify
`
`EXHIBIT 1013 - PAGE 0250
`
`APPLE
`
`