`
`EXHIBIT 1013 - PAGE 0151
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0152
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0153
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0154
`
`APPLE
`
`

`

`
`
`FIGS-35Athrough37Gand$16-53, iHustratePresentdisclosure data records-ferexample (FIG. 1
`
`
`through 17 or any other disclosed data records), may be maintained in an SQL database, or
`maintained in record form by a data processing system. Appropriate indexes and/or constraints
`are defined ina SQL embodiment. Depending on the embodiment, some data record fields
`disclosed may be multi-part fields (i.e. have sub-fields), fixed length records, varying length
`records, or a combination with field(s) in one form or another. Some data record field
`embodiments will use anticipated fixed length record positions for subfields that can contain
`useful data, or a null value (e.g. -1). Other embodiments mayuse varying lengthfields
`depending on the numberof sub-fields to be populated, or may use varying length fields and/or
`
`sub-fields which havetags iadicatingindicate their presence. Other embodiments will define
`additional data record fields to prevent putting more than one accessible data item in onefield.
`Other embodiments may
`implementpointers in fields to memory
`(e.g. memory
`pointer) or
`storage locations(e.g. file pointer and perhapsfile offset therein) which may or may not have
`been dynamically allocated. In any case, processing will have means for knowing whether a
`value is presentor not, and for whichfield (or sub-field) it is present. Absence in data may be
`indicated with a null indicator (-1), or indicated with its lack of being there (e.g. varying length
`record embodiments). Fields described may be converted: a) prior to storing; or b) after
`accessing; or c) by storage interface processing; (e.g. for standardized processing). Fields
`described may not be converted(i.e. used as is)._Any field may contain a join value (e.g. SQL)
`to
`one
`or more other
`data entities (e.g. tables) which
`contain a matching value (e.g. in at least
`
`to associate additional data (e.g. one or more other columns of data)
`one column)
`record 9850field.
`
`to an
`
`
`
`
`
`
`
`Handle ntainsauniquefield 9850 handle t rticular MADR. Various embodiment
`
`
`
`
`
`
`
`
`
`a SQL Database
`a unique integer (e.g. generate
`include a user assigned name (e.g. string),
`(DB) unique sequence numbergenerator), or other unique data instance for accessing a
`particular MADR 9850. Field 9850 a is to contain a unique value across all MADRsregardless
`of embodiment, for example when created or altered. Type field 9850 b contains the type of
`messagefield 9850 c of the MADR 9850, for example categorized in audio recording types,
`video recording types, text types, executable types, and application information types. There are
`many different message types depending on what formats will or can be supported in
`field 9850 c. Some examples:
`
`audio recording types: WAV (WaveForm), WMA (Windows Media Audio), ALE (Apple Lossless),
`MP3, bit sample rate information, or any combination of information describing an audio
`recording type for processing;
`
`video recording types: MPEG-1, MPEG-2, WMV, MOV, AVI, pixel and/or scanline information,
`frame sampling rate information, or any combination of information describing a video recording
`type for processing:
`
`text types: single byte characters, double byte characters, character set information, font, size,
`appearance, or any combination of information describing a text string for processing;
`
`EXHIBIT 1013 - PAGE 0155
`
`APPLE
`
`

`

`executable types: Motorola (USB to LSB order),
`
`Intel
`
`(reverse
`
`byte order),
`
`16
`
`bit,
`
`32
`
`bit,
`
`64
`
`bit
`
`run time variable settings, or an
`linkable code libraries required,
`stack size required,
`combination of information describing an executable for processing; or
`
`calendar information reference
`date/time,
`current
`current location,
`lication information types:
`term information
`LRDR
`r
`game), waymark or map
`urrent application in u
`.q.
`any combination of information describing application information. Application information also
`includes accessing status from an external application (e.g. Twitter status, Facebook status
`etc), using LRDRsto “skip” handling the presentation (e.g. do not process OGM), and/or
`determining the information to be presented for the nearest person(s) at the time of a
`istripution (e.g. a call). Application information may
`be referenced in user designate
`destinations of a specified recording, text for annunciation, or other presentation data stream, or
`as a single reference for an entire message output.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`me embodimentsoft fiel 5 imply carry a file extension or ial qualifier which i
`
`
`
`
`
`
`
`recognize
`
`an operating
`
`system for handling
`
`the MADR.
`
`Other embodiments
`
`define a
`
`lurality of fields formed
`
`together to determine a particular type. Message fiel
`
`50 c contains
`
`r 50_band maypoints to) the message in the appropriate format as describe fiel be
`
`
`
`
`
`maintained to a file or suitable MS memory. In context of a particular message type, message
`
`field 9850 c may contain the substitution identifiers of U.S. Pat. No. 5,434,910 (“Method and
`system for providing multimedia substitution in messaging systems”, Johnsonetal).
`Field 9850 c may
`involve an executable that does no presentation (e.g. MADR configured to
`
`
`
`erform desired 9850cmayprocessing). Field be advertising content, for example where a
`
`
`ur
`
`hared/communicated
`
`the MADR(s)
`
`to
`
`the
`
`MS
`
`for
`
`conditional presentation at the MS.
`
`Use
`
`field
`
`9850 d
`
`contains
`
`use
`
`information of the messa
`
`f the MADR 9850. A single messa
`
`n have many bits set). Inapreferred embodiment, 9850 d isabituses(e.g. multiple field
`
`
`
`
`mask wherein specific bit positions indicate a particular event use. For example, a bit set to 1 is
`
`enabled and a bit set to 0 is disabled. There maybe bit settings for OGM, OCM, varieties of
`COM-R (e.g. COM for particular application to process at Remote MS), varieties of COM-L (e.g.
`COM for particular application to process at Local MS (e.g. a receiving or sending MS))
`for
`inbound or outbounddistributions, or other uses. Varieties of COM-R and COM-L accommodate
`confirmation of delivery messaging for different applications such as email, calendar, address
`k,
`phone,
`advertising,
`or any
`other application where acknowl
`mentis desired
`for a
`related
`distribution (e.g.
`delivery
`of another message),
`or the inbound/outbound event
`serves a
`a useful trigger for presentation. Various embodiments will granulate COM use settings
`differently. For example, the calendar application can have bit settings for. COM-R-cal (e.g.
`MADRsfor processing at a Remote receiving MS), COM-L-in-cal
`(e.g. MADRs for
`processing at
`the Local MS for inbound calendar items), COM-L-out-cal
`(e.g. MADRsfor processing at the
`
`
`Local MS for outboun lendar items): or forapreferred embodiment of: COM-R-cal (e.g.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`MADRs ataRemote receivingfor processing MS), COM-L-cal (e.g. MADRs for processing at
`
`
`
`
`
`the Local MS
`
`for inbound or outbound calendar items): or for: COM-cal
`
`(e.g. MADRsfor
`
`or the use field 9850 d may be removed from a MADR
`(local/remote) MS):
`rocessing at any
`that the use is completely specified via expression field 9850 g. Any application (like the
`Calendar example) may also have different use field embodiments. In the preferred
`embodiment, use field 9850 d supports manytypes of events which result in MADR processing.
`Default
`fiel
`indi
`whether or not
`the m
`f the MADR
`i
`faul
`message for processing (i.e. True or False). There can be one default MADR for eachof the
`
`uses (e.g. described by field 9850d)so that a default exists when all matching MADRs have
`
`EXHIBIT 1013 - PAGE 0156
`
`APPLE
`
`

`

`expressions that evaluate to False. Originator intentfiel
`
`50
`
`f contains various originator
`
`instructions to be associated with the message which wasnot, or could
`
`not,
`
`be specified or
`
`f includes information for message presentation
`50
`b. Fiel
`50
`ommunicated in type fiel
`that can be applied differently to messages of the same type field 9850 b.
`Field 9850 f information includes specifications for an expiration of the MADR,priority setting
`(e.g. high or normal), appearance or presentation information, volume or volume override
`information, data processing system control operation, ghosting the message image(like a
`watermark)
`over a video
`recordin
`rany
`other originator
`preference
`for affectin
`
`lay/presentation of the particular message toauser. A visual mode settin n be set here for
`
`
`
`
`
`
`
`the
`
`originator's
`
`intent
`
`of: full
`
`screen
`
`icated
`
`user interface
`
`visual area, newl
`
`awn
`
`(e.g. window) with “stolen” focus, title-bar area of currently focused window, use
`pop-up
`window,
`observer's preference, or other visual method for presenting MADR information. An audio mode
`setting can also be set for the originator's intent of: mix, preempt, or use observer's preference.
`Field 9850 f may also include a prescription for which users, groups of users, authority levels of
`users, or which specific privilege(s) configured can maintain, distribute/share, manage, view,
`alter, present, or delete the MADR. Expressionfield 9850 g contains an expression of conditions
`which can be determined at thedata processing system sending and/or receiving the message
`
` m
`
`i
`
`.g. recipient
`t
`liver the m
`t
`nd where
`mail, MS2M
`.g.
`and recipient wildcarding
`is supported for delivering
`to a
`groups (e.g. MS ID group)
`Recipient
`plurality of recipients. A prioritized attempt may also be specified wherein unsuccessful
`deliveries cause further delivery attempts. A null setting in field 9850 h is resolved to the user of
`the MS wherepresentation is to occur. History field 9850 / preferably contains a plurality of
`fields including
`creation
`date/time stamp,
`last change
`te/time stamp,
`creator identit
`information, updateridentity information, system addressinformation where actions took place,
`and_anyother information useful for forming useful history of why MADR datais the wayitis.
`Identity
`information may
`be a
`specific identifier or a group
`identifier, for example used
`in
`enforcing intent field 9850 f for specific MS processing. Active field 9850 / is preferably a
`Boolean (Yes/No) indicating whether or not the MADR is active (i.e. participates in being
`considered for automated processing). Filter join value field 9850 & contains a null, or a join link
`to at least one Event Filter Record (EFR) 9855. Description field 9850 / contains an optional
`user
`documentary
`(e.q. text) for the MADR
`9850. MADRsare operating system independent
`
`objects for
`
`being
`
`processed
`
`locally or remotely,
`
`and
`
`are shared
`
`between systems
`
`based on
`
`ermissions.
`
`
`
`t ype field 9855 b contains the type of data being joined to the MADRS)ad dataevent lhe: Resor tes 855m contain on rmor. So OSare ined
`
`
`
`
`
`
`
`field 9855ccontains data of the t described by field 9855 b. For example, data
`
`field 9855 c is whereabouts information (e.g. location) when type field is WHEREABOUTS, data
`field 9855 c is keyword(s)
`information (e.g. a string or delimiter separated text strings) when
`type field is KEYWORDS, and data field 9855 c is scheduling information (e.g. date/time
`expressions) when type
`field is DATETIME. There may be many supported t
`
`fields 9855bwith corresponding data 9855 c. Description field 9855dcontains an optional user
`documentary
`(e.g. text) for the EFR 9855, History
`field 9855 e preferably contains a plurality of
`fields including creation date/time stamp, last changed date/time stamp, creator identity
`
`EXHIBIT 1013 - PAGE 0157
`
`APPLE
`
`

`

`information, updateridentity information, system addressinformation where actions took place,
`and _anyother information useful for forming useful history of why EFR data is the wayit is.
`
`In one embodiment, EFR data is maintained as part of the MADR object itself in fields of intent
`field 9850 f for originator
`(author)
`intent for the presentation that
`can
`be shared
`between
`
`rmissions. A
`usin
`presented
`and
`rmissions,
`permissions, maintain
`n
`ba
`tems
`preferred embodiment separates out EFR data so that a plurality of MADRs can reference a
`single EFR. There may be MS applications which use EFRsfor other purposes. Although EFRs
`extend MADR processing, the MADR plus EFR together are viewed semantically as a single
`
`MADR object for processing.
`
`EXHIBIT 1013 - PAGE 0158
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0159
`
`APPLE
`
`

`

`
`
`FIG. 3616B depicts a preferred embodimentof a HisteryLocationReference Data Record
`
`
`
`HeaRD®) 36209860 forralscussing operations ofthe presentdisclosure,derived from the grammar
`
`
`
`
`EXHIBIT 1013 - PAGE 0160
`
`APPLE
`
`

`

`
`
`seeCreaterinfe-andsubfields}Medifierlnfe-message processing. Location Reference Data
`
`
`
`Records (LRDRs) 9860 contain reference-able location data which has been saved by a MS
`user, for example from_a map application, navigation application, or other application where a
`user can mark a saved location. Typical industry terminology includes “waymarks”, “waypoints”,
`“pushpins”, “bookmarks”, “geofence”, or any other metaphor whereby a user saves a location
`fr mana
`lication,
`perha S$ with a ra ius
`undary(s
`rmeasurements|indicatin an area or
`
` Ser. No. 11/207,080 temAnd MethodFor‘Anonymous LocationBased Services”, Johnson)
`contained in LRDRs 9860. CRDRs 9860 may or may not be maintained local to a MS. The
`
`coined
`
`terms of “Pin
`
`ots”
`
`“Pingimeters” which are similar location metaphors
`
`and ma
`
`terminology “waymarkinformation” used herein is to include all these embodimentsto facilitate
`explanation brevity. Encoding field 9860 c contains any reasonable whereabouts embodiment
`for such metaphors, for example such as those used in a graphical user interface. LRDRs are
`preferably created using a convenient map navigation interface for marking locations on a map,
`
`
`
`user with asuitableinterface.interface.
`
`Namefield 9860 a contains a name for the LRDR 9860, type field 9860 b contains a type of
`LRDR for
`correct interpretation of field
`9860
`.g. a plurality
`of applications
`sharing a waymark
`
`information repository),
`
`encoding fiel
`
`c contains the whereabouts encoding which can be
`
`b, description field 986
`field 9860
`t
`indicated by
`d as
`d and pro
`defined description for the LRDR (preferably a text description which can be
`annotated/annunciated unambiguously),
`and other fields 9860 e are not of immediate interest
`
`ontains a user
`
`here. In some embodiments, namefield 9860 a contains the desorption and field 9860 diis not
`aieren escription format
`in field 9
`d. Auser may ensure descri ten are unique ifan
`licati ne
`not
`enforce
`uni
`uU
`riptions. Map Term Data Ri
`MTDR
`f th
`
` LRDR 19 rovi he interf: for activiti f lication m rk I ion MADR
`
`
`
`
`
`
`
`
`
`presentation processing can use those locations for useful functionality.
`
`EXHIBIT 1013 - PAGE 0161
`
`APPLE
`
`

`

`With reference now to FIGS.
`
`8A through 8E,
`
`depicted
`
`is the preferred embodiment BNE
`
`rammar from the parent applications,
`
`in particular for memorable reference. An Expression
`
`an Expression or derivative embodiments
`Such
`g.
`50
`e specified for fiel
`8D m
`of FIG.
`thereof may be user configured/specified, preconfigured user selected choices ata data
`processing system, configuration generated, or defaulted/set in accordance with other user
`configurations. Various embodiments will interpret at message accesstime the expression of
`
`field 9850g,or a data processing internalize field 9850gatsystem (e.q. MS 2) may
`
`configuration time
`for
`efficient
`processing at a later tim
`.g. at block
`9936 upon an
`
`reciate the full
`essed. The reader shoul
`nfiguration changes) when the message is
`scope, meaning, processing, and many embodiments possible for an Expression of FIG. 8D.
`
`
`
`With reference now to FIG. 7, depicted is ofaWhereaboutsreferred embodiment
`
`
`
`Wireless) Data Record (WDR) 1100 from the parent applications,
`
`in particular for memorable
`
`preferabl
`of FIG. 14 is
`lications
`mmunicated for the man
`dat
`reference. Recall that
`carried in application sections of applications fields 1100 k. Distinct application sections may be
`referenced with an appfld.X qualifier where X is the application section containing subordinate
`memberdata sections. MADR data may also be carried in application fields 1100 k, preferably
`subordinate to the particular application for which the MADR data is being sent. The COM-R
`varieties of message processing will cause carrying MADR data to receiving systems.
`
`
`
`
`
`Depending on embodiments, useaWDR, MS2MS processindata sent outbound may n
`
`any other
`platform, or
`email transport
`data processing system to another.
`
`ropriate communications means for sending from one
`
`With reference
`
`now to FIG. 14
`
`icted
`
`is a LBX application fields
`
`implementation status
`
`tabl
`
`from the
`
`parent application,
`
`in particular for memorable
`
`reference. While FIG. 17 facilitat
`
`lication involvin
`n
`lication examples of message processin
`few
`iscussin
`sender (or caller, invoker, submitter, etc) and recipient (or callee, invokee, submittee, etc) may
`participate in using the message processing disclosed. MADRswill be processed similarly to the
`descriptions herein for every application with inbound or outbound event. Generic processing is
`involved for any application.
`
`With reference now to FIG. 17, depicted is a table to facilitate explanation of message
`processing for ADs, OGMs, OCMs, and generic application COM processing. Explanation
`table 9875 showsa processing result for a particular scenario including a select exemplary set
`of applications. Special applications are described
`in rows
`2 and
`generic applications are
`
`cri
`
`in row
`
`4. An
`
`lication m
`
`involved
`
`in MADR processing in
`
`imilar
`
`manner to rows 9894.
`
`AD
`
`r
`
`lication: AD specific events
`
`are
`
`configured
`
`for when to
`
`access AD specific MADRsin
`
`it
`
`00 for AD pr
`
`in
`
`FIG, 24), ADs may
`
`be
`
`presented local to
`
`the data
`
`rocessing system hosting
`
`the reposito
`
`or ADs m
`
`e presented
`
`at remote
`
`dat
`
`applicable MADR
`d_and any
`are a
`tems. When an event occurs, MADRs
`in
`ro
`with expression fields 9850 g evaluating to True are presented according to the other MADR
`fields and the observing user's preferences. ACOM may also be associated to inbound or
`outbound advertising information.
`
`OGMapplication.When-ataldoesunansweredatnanswerthereceivingdataprocessingsystem,
`
`in
`M
`
`ifi MADETr resen
`n
`
`lirdin
`
`le MADRs with expressionh her MADRfiel
`fe |
`which eval
`
`
`
`EXHIBIT 1013 - PAGE 0162
`
`APPLE
`
`

`

`to the caller for
`provided
`to the caller and an opportunity is
`presented
`a single OGM is
`Typically,
`
`leaving a recorded message. OGM processingis well knownin the art, however use of the
`message reposito
`rocessing
`provides
`an improved method for customizin
`Ms to
`specific callers. OGMs may be video in nature for video messaging between data processing
`systems (e.g. MSs),
`
`OCMapplication: During an active call, a user can perform an action to invoke OCM processing.
`If the user made the call,
`it is assumed that the user (caller) has selected to automatically leave
`a recorded messageatthe callee's system, for example after the callee's system has presented
`an OGM (to the caller). When the user invokes OCM processing, the active call thread releases
`user interface focus (e.g. at the MS)
`and continues to execute in the background
`for accessin
`
`perform other
`OCM information. The user is free to
`and then presenting
`CM specific MADRs
`application processing (i.e. use other thread(s) for other tasks) at the data processing system
`call.
`MS) while the
`active
`call thre
`utomatically
`processes the OCM and
`then terminates the
`This saves the caller time from having to leave a messageat a callee's system while freeing up
`the MS for other activities concurrently. If OCM processingis invoked during a received call, the
`active call thread maintains user interface focus and the OCMis presented in parallel to the
`active call for both the caller and callee, for example to both hear or see a recording. While the
`most common embodimentis for voice calls, video calls also apply. The OCM will
`be presente
`
`visually
`
`as well
`
`as
`
`audibly
`
`provided
`
`the selected MADR provides visual information and
`
`the
`
`call
`
`involvesavideo session. Typicall single OCM is presented to llee's data processin
`
`
`system.
`
`
`
`
`
`
`
`
`
`
`
` An email COM comesin two forms: COM-L for processing email COM-Lspecific MADRs at the
`
`specified email COM-R MADR(s
`and CON-R for processing
`sender or recipient local system:
`at the remote system(s). COM-L_ MADRsare searched for each email sent or received at the
`local system (e.g. MS). The SMS/texting application is analogous,
`preferably with out-of-band
`data (i.e. not
`part of SMS/text message) to communicate COM-R MADR information. Email
`descriptions are interchangeably applied to text messaging, albeit with more simple text
`
`messagedistributions.
`
`Calendar application (e.g. appfld.calendar.X): A COM can be associated to inbound or outbound
`calendarinformation (e.g. meeting notice). A Calendar COM comesin the identical two forms:
`CON-L (‘L for local)
`for
`processing
`calendar COM-L specific MADRsat the sender or recipient
`
`calendar COM-R MADR
`cified
`for processin
`and COM-R (“R” for Remote)
`tem:
`local
`at the remote system(s). GOM-L_ MADRsare searched for each calendar item sent or received
`at the local system (e.g. MS).
`
`Phone application
`
`(e.g. appfid.phone.X): A COM can be a
`
`jated to
`
`inbound or outbound
`
`hone calls, voice or video,
`
`prior to OCM or OGM processing. A phone
`
`lication COM comes
`
`nder or
`ific MADRs at th
`phone COM-L
`ing
`pro
`identical two forms: CON-L for
`in the
`recipient local system; and COM-Rfor processing specified phone COM-R MADR(s) at the
`remote system(s). COM-L_ MADRsare searched for each call made or received at the local
`system (e.g. MS).
`
`For
`
`fiel
`
`M
`
`c
`
`in
`
`k
`
`|
`
`for MADRs which have
`
`expression
`
`val
`
`True.
`
`M-L
`
`(e.g. indi
`
`in fiel
`
`MADRs which hav
`
`matching
`
`expressions
`
`(fiel
`
`=Tr
`
`re
`
`pr
`
`for in
`
`nd
`
`an
`
`n
`
`nari
`
`EXHIBIT 1013 - PAGE 0163
`
`APPLE
`
`

`

`to distinguish between whether inbound or outboun
`be used
`The expression itself may
`distributions are of consideration, or what type of inbound or outbound eventis of consideration.
`In some em O iments specific C M uses in fiel
`5
`may
`indicate how to se rch MADRs
`
`L-in-email, COM-L-out-email, COM-R-email).
`
`Generic application rows 9894 provide the comprehendible model for other MS applications and
`COM rocessin that a
`lies. The advertise a
`lication e.g. appfid.advertise.X),
`profile
`
`
`
`rticular
`or processed at
`resentedt the user,
`usly. MADRs
`anal
`C M-R rocessing
`system have many different uses and applications. While MADRs support various presentation
`formats,
`any executable
`can
`be
`processed
`there
`erforming
`processing which m
`cm
`not present anything. In some embodiments, the sender's data processing system automatically
`determines the appropriate COM-R MADR(s) without user involvement and appendsthe data to
`the
`distribution without th
`nding user
`being
`burdened
`with user
`interf
`for
`ification.
`
`Inbound and outbound distributions for other applications are involved with receiving or sending
`data within the context of a particular application. For example, the presence of content within
`the WDR application fields section 1100 k which is subordinate to an appfld section of
`fields 1100 & is used to trigger MADR processor. Charters may be user configured to use
`AppTerm conditions
`for
`causing
`the same triggers
`and
`presentation actions
`can
`be
`configure
`
`when the AppTerm expressions
`
`evaluate
`
`to True. However, a MADR is a presentation
`
`object
`
`with a “content-centric” approach, “content-centric” in that an
`
`ratin
`
`tem in
`
`ndent
`
`information for the presentation. Application
`all necess
`defines
`object (i.e. the MADR)
`configuration can be conveniently isolated in field 9850 d. MADRs may be populated by an
`application installation and removed by an application uninstall. Field 9850 d may be set by an
`application installation and unset by an application uninstall. WDRs are not to be the only
`transport of data between systemsin context of the particular application. Other embodiments
`for communicating data between systems may be used. Continuing with some of the other
`examples and regardless of transmission embodiments, an inbound/outbound advertisement,
`inbound/outbound profile, inbound/outbound address book entity, inbound/outbound emergency
`communication, inbound/outbound did transmission, inbound/outboundstatistics data entry,
`inbound/outbound appliance communication transmission, or inbound/outbound distribution of
`data in other applications can have associated objects (i.e. MADRs) for automated
`presentation/messaging.
`
`With reference now to FIG. 18, depicted is a flowchart for a preferred embodiment of MADR
`configuration processing. Methods and systemsfor maintaining data records has been well
`described in the parent applications and similar systems and methods apply here for another
`record type (MADR 9850). Many convenient userinterfaces can be used for equivalent user
`nfiguration functionality. The
`data within the
`record,
`and
`its
`use,
`makes MADR data unique.
`
`There
`
`are obvious
`
`user
`
`interf
`
`ontrol
`
`rror handlin
`
`nd
`
`pro
`
`ing
`
`thereof,
`
`in multi-threaded MS
`example
`incorporated, for
`to be
`is
`semaphore u
`(e.g.
`Synchronization
`processing, to prevent asynchronousthreads from accessing data at inappropriate times.
`Pri
`in
`in
`lock
`2. ntin
`lock
`4 wher
`initializ
`lon for
`
`n
`
`EXHIBIT 1013 - PAGE 0164
`
`APPLE
`
`

`

`where options are presented to the user along with a
`block
`get MADRs),
`embodiment) and
`current scrollable list of MADRs, and on to block 9908 where processing waits for a user action
`in response to options
`presented
`at
`block
`_ Block
`4 preferabl
`essesall expire
`
`MADRs(checking datain field 9850f)and expires them (i.e. preferably inactivates, or discards).
`
`Block 9904 will access the currentlist of MADRs remotely or locally as required by the
`embodiment in an appropriate manner depending on how MADR data is maintained. Various
`embodiments may categorize MADRs, for example on one or more key fields in MADR data,in
`rder to
`organize
`the
`list for
`optimal presentation. AMS may
`come
`preconfigured with useful
`
`MADRs. Upondetecting a monitored user action, processing leaves block 9908 for block 9910.
`
`EXHIBIT 1013 - PAGE 0165
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0166
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0167
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0168
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0169
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0170
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0171
`
`APPLE
`
`

`

`
`
`
`
`
`
`
`
`nraferably with caseade deletein-aSQL2 embodiment) block 298doreate aMADR. 01processing
`
`
`
`continues to block 9912 where the MADR is created by the user. Block 9912 supports the user
`exiting out to block 9906 without having created a MADR,or block 9912 will have saved the
`created MADR sothatit is subsequently
`presented with the list at
`block
`9906. A MADR is
`
`reate
`
`interfacing with the user for validated MADR
`
`9850
`
`field
`
`information and
`
`any
`
`joine
`
`EFR 9855 information described above with FIG. 146A. MADRs may
`
`be validated based on use
`
`9912
`other MADR field(s) specified. Block
`any
`or
`9850 b,
`field
`9850 d, t
`field
`convenientinterfaces for joining to EFR(s) and for creating EFR(s) information.
`Block 9912 continues back to block 9906 for re-presenting the list and options and again
`determining what the user wouldlike to do. If block 9910 determinesthe user did not select to
`
`
`delete-apermission,thencreateaMADR,3952-0fF1G-398-byway-efprocessing continuesto block
`
`eff-page
`
`provides
`
`connecter39509914.
`
`EXHIBIT 1013 - PAGE 0172
`
`APPLE
`
`

`

`ba
`
`Es
`
`7)
`
`
`nn rainy
`
`
`a
`
`pKHracan
`
`Ae
`
`in
`
`
`
`rr
`
`
`
`
`nD
`
`
`
`
`
`
`
`7
`
`
`
`
`
`
`
`useractionthattheuseriscompletereviewingdetails,inwhichcaseprecessingdeleteoneormore
`selected MADRs, processing continues to block 9916 where the selected MADR(s) are
`discarded. The user may interface with the presentedlist for selecting one or more MADRsfor
`deletion. Any
`joined EFR(s) are preferably unaffected by a deletion (except in the embodiment
`where EFR information is contained in the MADR itself). Block 9916 supports the user exiting
`out to block 9906 without having deleted the selected MADR(s) (e.g. after an “Are you Sure?”
`rompt),
`or
`block 9916 will have discarded
`the selected MADR(s) which will subsequently
`be
`
`reflected
`
`in the
`
`list
`
`presented
`
`at
`
`block
`
`. Block
`
`9916
`
`al
`
`iscards
`
`any a
`
`iat
`
`ndin
`
`resentation prompt configurations or
`
`processing
`
`threads (from block 10654) using handle
`
`50 a (e.g. terminates threads, removes calendar entry(s), update history).
`fiel
`Block 9916 continues back to block 39129906 already described. If block 39609914 determines
`the user did not select to getdelete one or more detail,thesnMADRs, processing continues to
`block 39669918.
`
`If block 9918
`
`determines
`
`the user
`
`selected to modify
`
`one or more MADRs,
`
`processing continue
`
`to block 9920 where the selected MADR(s)
`
`are appropriately modifie
`
`the user. A MADR i
`
`V
`ri
`information
`field
`9850
`for validated MADR
`user
`interfacing with the
`Iter
`with FIG. 16A. Processing of block 9920 performs modification processing using the same data
`validation rules used for creating a MADR.If a plurality of MADRs are selected, then the user
`interface at block 9920 supports making a common changeacrossall selected MADRs,
`otherwise the userinterfaces to a single MADR. EFR(s) are preferably unaffected by a
`modification, except perhaps
`eing
`newly
`joined
`to,
`or having
`join(s)
`removed
`(except in the
`embodiment where EFR information is contained in the MADR itself), Block 9920 supports the
`user
`exiting
`out to block
`9906 without having modified selected MADR(s),
`or block
`9920will
`
`have saved the modified MADR data so
`
`it is subsequently
`
`presented with the
`
`list at block
`
`9906.
`
`or processin
`presentation prompt configurations
`nding
`discard associat
`9920 may
`Block
`threads using handle field 9850 a (e.g. terminates threads, removes calendar entry(s), update
`history). In another embodiment, Block 9920 may support modifying associated pendin
`presentation prompt configurations or processing thread instruction using handle field 9850 a.
`Block 9920 continues back to block 9906. If block 9918 determines the user did not select to
`modify one or more MADR(s), processing continues to block 9922.
`
`If block 9922 determines the user selected to clone one or more MADRs, processing continues
`to
`block 9924 where the selected MADR(s)
`are appropriately cloned
`(copied)
`for creating a set
`of new MADRswhich can then be “tweaked” or further modified at block 9920. The newly
`reated MADRs ar
`ied
`in their
`entirety
`from th
`urce MADRs
`except new handl
`
`
`
`fiel tem_generated85 r to ensure uniqueness. The user may modify the handl
`
`
`
`
`at block 9920 provided all MADRs contain unique handles. Block 9924 continues to
`block 9920 for modification processing described above. Cloned and/or modified MADRdata is
`subsequently presented with the list at block 9906. If block 9922 determines the user did not
`select to clone one or more MADR(s),
`processing
`continues to block 9926.
`
`If block 39669926 determines the user selected to internalizepermissionsdatathusfarbeing
`
`,
`
`
`
`
`
`EXHIBIT 1013 - PAGE 0173
`
`APPLE
`
`

`

`
`
`lurality
`
`of
`
`lications
`
`are managed for
`
`bein
`
`erl
`
`tthen processing1 continuestoblock 9928where any ofa
`processed-manage aian appication.
`thereof. Block 9906 preferably displays which avolications can be managedso that processing
`
`nfigured for MADR
`
`data
`
`or changes
`
`at block 9928 can determine which application was selected for being managed. Block 9928is
`described by FIG. 19. Block 9928 continues back to block 9906 upon FIG. 19 processing
`termination. If block 9926 determines the user did not select to manage an application,
`processing continues to block 9930.
`
`
`
`If block 9930 determines the user selected to manage MADR related privileges or charters,
`rocessing continues to block
`9932 where
`the
`user is able
`to
`create,
`delete,
`alter,
`or work with
`privileges and/or charters. Privilege and charter configuration was well described in the parent
`lications.
`Similarly,
`any aspect
`of MADR processing
`discl
`can
`rivil
`for proper
`
`for replacin
`or may not mana
`charters may
`and
`tween M
`interoperabilit
`complementing, or enhancing functionality disclosed herein. Block 9932 continues back to
`block 9906 after configuration processing has been completed. The user may or may not have
`altered privilege or charter data (e.g. viewed privileges or charters). If block 9