Abstract
`
`Providedis a distributedsystem and method forenablingdependentnewandisefullocation
`
`
`
`
`features-andcentralizing common messaging functionality temebite-dataprocessingsystems-across
`a plurality of heterogeneous Mobile data processing systems+{MSsHnteractwith-each-etheras
`
`
`
`
`MSsSystem (MS)
`
`
`applications, and for synergistically bringing new messaging functionality to those applications.
`New synergistic
`presentation/messagin
`ility
`is
`provided with distributable presentation
`objects in areas of Out-Going Messages (OGMs), Out-going Caller Messages (OCMs),
`Confirmation Of delivery Messages (COMs) and ADvertising messages (ADs). OGMs include
`messageswhich are played to callers in a phone call recording system. OCMsinclude
`m
`that
`can
`left
`automatically t
`hon
`ll recordin
`tem
`ller. COM
`include messages that are automatically sent based on a delivery. ADs include messagesfor
`conveying advertising
`information. Different message
`types are automatically
`presented
`for a
`and
`variety
`of triggering
`events,
`and
`in
`rdance with reconciling
`an
`originator's intent
`an
`observer's preferences. In a preferred embodiment, the Location Based eXchange method and
`system is leveraged.
`
`Description
`
`CROSS-REFERENCES TO RELATED APPLICATIONS
`
`This application is a continuation in part of application Ser. No. 12/590,831 filed Nov. 13, 2009
`and entitled “System and Method for Location Based Exchangesof Data Facilitating Distributed
`
`Locational Applications” which isacontinuation in part of lication Ser. No. 12/287,064 fil
`
`
`
`Oct. 3, 2008 and entitled “System and Method for Location Based Exchanges of Data
`Facilitating Distributed Locational Applications” which is a continuation in part of application Ser.
`No. 12/077,041 filed Mar. 14, 2008 and entitled “System and Method for Location Based
`
`Exchangesof Data Facilitating Distributed Locational Applications’-Specificationfromthe
`a
`joned application is
`included herein.
`OA
`through
`78 and
`eciated, hereinafter
`
`
`
`referred to as the parent applications. Given the size of the parent applications and so as to not
`obfuscate new material,
`it is to be appreciated that
`parent applications are intended an
`assumedto be included herein in their entirety, however drawings and descriptions are
`newprovi
`for
`mpl
`n
`nd-alone
`discl
`re. Thi
`lication is
`fil
`nth
`day as a co-pending application Ser. No. 12/800,395 entitled “System And Method For
`
`m
`
`EXHIBIT 1013 - PAGE 0001
`
`APPLE
`
`

`

`Automatically Leaving An Outgoing Caller Message” which contains an identical specification
`exceptforthe title and abstract.
`
`TECHNICALFIELD-OF+HEINVENFION
`
`The present disclosure relates generally to !ecatienbasedsenicesformobiledataprecessing
`
`systemasmanaging
`information for automatic
`presentation or distribution, and more particularly to
`
`
`
`-managing an information/messaging
`automatically
`being
`presented
`and/or
`ntaining heterogeneous formats for
`reposit
`distributed for certain application events associated with determined data processing system
`conditions.
`
`BACKGROUND-OFFHEINVENHON.
`
`EXHIBIT 1013 - PAGE 0002
`
`APPLE
`
`

`

`
`
`Different users use different types of Mobile data processing Systems (MSs) which are also
`called mobile devices: laptops, tablet computers, Personal Computers (PCs), Personal Digital
`Assistants (PDAs), cell phones, automobile dashboard mounted data processing systems,
`shopping cart mounted data processing systems, mobile vehicle or apparatus mounted data
`
`processing systems, Personal Navigational Devices (PNDs), Android enabled devices, iPhones
`(isheneiPhone is a trademark of Apple, Inc.), iP.
`iPad
`i
`rademark of A
`
`EXHIBIT 1013 - PAGE 0003
`
`APPLE
`
`

`

`
`
`
`
`
`scepeofsuppertfertecatingMSs.[here are many applications which use various message
`formats to carry out a variety of functionality. Many of these applications intersectin
`functionality, message formats, and processing. This causes redundant processing and storing
`of data at a MS whichis usually limited in performance, storage capacity and processing power.
`A method is needed for consolidating, standardizing, or at least organizing overlapping
`messaging functionality to provide optimal MS
`processing,
`storage and
`performance. The term
`“message” or “messaging” as used herein is meant to be interpreted in the broadest sense of
`conveying or communicating information to a recipient user.
`
`
`
`A well organized method is needed for enabling users to manage messages(e.g. information
`for presentation) for any of a variety of reasons that make sense at a MS. Users should be able
`to make use of saved messages for automating Out-Going Messages (OGMs) such as those
`layed
`to callers of a phone (e.g. voice) mail system,
`Out-going Caller Messages
`(OCMs) which
`
`are disclosed
`
`as
`
`those messages
`
`being
`
`left automatically to a phone (e.g. voice) mail
`
`tem
`
`those messages for
`as
`(COMs) which are disclosed
`delivery Messages
`Confirmation Of
`automatically distributing based on a previous distribution, and ADvertising messages (ADs) for
`conveying an advertising
`information to recipient(s). ADs are useful in many applications
`involving OGMs, OCMs and COMs, and AD type messages do not have to be advertisements.
`Providing MS applications with access to a well architected “content-centric” interface gives rise
`to synergistic functionality quickly incorporated into new applications. Incorporating a content-
`ntri
`lution enabl
`roviding
`low
`t_M
`nd M
`lications
`through
`advertisementbill
`paid by companies seeking novel waysto advertise.
`
`EXHIBIT 1013 - PAGE 0004
`
`APPLE
`
`

`

`Different systems for email,
`
`phone mail and
`
`calendaring
`
`provide
`
`different methods for a
`
`confirmation of delivery. For example, one email system will
`
`provide a Confirmation
`
`Of Delive
`
`COD) status to the sender when an email arrives toarecipient's in-basket while another will
`
`
`provide a COD status when a recipient opens the email item. Systems may also implement
`different methods for communicating the status. Some will send a separate COD email (e.g.
`received as new email in in-basket), and some will require a sender to examine (e.g. poll), or
`perform user interface actions, for status associated with the email sent. A consistent method is
`needed across heterogeneous applications and for supporting any application involved in
`
`istribution of information betweenasender and recipient such as phone lications ress
`
`
`
`
`
`
`k applications,
`
`calendar application
`
`rany
`
`other application involved
`
`in inbound
`
`or
`
`be an opportune time to additionally
`data. Providing a COD status also may
`outbound
`an_ advertisement. An advertising framework should provide enough non-advertising
`functionality to entice users to use the framework.
`
`provide
`
`out processin
`to carry
`The multi-threaded Location Based Exchanges (LBX) MS hasthe ability
`which was conventionally carried out by external services. For example, a corporate PBX
`(Private Branch Exchange) would accept phone mail system messages from callers for
`unanswered phones, enable userinterfaces to retrieve phone mail system messages, enable
`all waiting,
`and
`provide many other useful
`phone system features. In another example, a MS
`
`
`
`n incorporate its own caller recordings likeaconventionalcall answering service, and save
`
`
`
`
`
`
`
`
`
`nswering machine. The LBX M
`
`n be self-contained for functionality,
`
`and m
`
`Iso interface
`
`directly to another MS for phone features which were provided byaservice. In particular, as
`
`
`MSsincorporate peer to peer operation, there is no need for services to middle-man
`functionality. The MSs themselves contain adequate processing power and LBX multi-threaded
`capability to provide necessary processing for functionality which was conventionally provided
`by a service. Therefore, a method and system is needed for centralizing common messaging
`interfaces
`acr
`a plurality
`of heterogeneous LBX MS
`applications. Leveraging third
`pa
`advertisement budgets for such functionality is desirable.
`
`
`
`While LBX is a preferred embodiment, telecommunications companies are reluctant to give up
`ntrol
`of
`phone
`user interactions and billin
`nversation enablement. Even two
`MS users
`standing next to each other may be required to go through their phone company network
`rocessing in
`order to
`have a conversation using
`their MSs. In the LBX architecture,
`two users
`
`
`tanding next to each other can make useofa direct wirele eer to peer LBX connection t
`
`accomplish their connectivity. IP datagrams (e.g. WDRs(i.e. Whereabouts Data Records or
`Wireless Data Records)) or a validated-delivery protocol of WORs may be exchanged between
`the MSsfor carrying out data exchanges or conversations, for example one channelfor carrying
`data from the caller to the callee and another channel for carrying data from the callee to the
`ller. Therefore, the disclosed method
`and
`system must handle traditional telephony
`(e.g.
`cellular) environments as well as LBX peer to peer communications environments.
`
`BRIEFSUMMARY-GF--HEINVENFHON
`
`Disclosed
`
`is a
`
`tem_and method
`
`for centralizing common messaging
`
`(e.g. information for
`
`resentation)
`
`interfaces
`
`acr
`
`a plurality
`
`of heterogeneous
`
`MS
`
`applications
`
`including
`
`MSs
`
`ina
`
`environment.
`(Location Based Service(s)) as well as a LBX (Location Based eXchange(s))
`LBS
`many
`differen
`r
`i
`is
`archi
`mm
`many
`differen
`r
`Am
`i
`i
`icati
`icati
`one Application Proar:
`Interface (API) for enabling, or using, desired functionality. The term OGM (Out-Going
`
`EXHIBIT 1013 - PAGE 0005
`
`APPLE
`
`

`

`Message) |is well knowniin the art to automatic answering machines, phone|mail systems. and
`
`for how n
`ropriate
`M is
`determined
`and used. A new term Out-going Caller Message
`OCM)
`is disclosed. MS users are interested in
`getting more out of their time. For example
`when a MS caller reaches an OGM from a callee's system (e.g. busy, or no answerforwards to
`phone mail), the MS caller can opt to leave an OCM rather than wait for the OGM to complete
`and then verbally leave a message. OCM processing enables the MS caller to immediately end
`the
`call and continue
`using
`other MS
`applications
`or
`processing while
`the OCM is automaticall
`
`n
`
`ncurrently
`
`being
`
`left
`
`at the
`
`callee's system. Another new term Confirmation Of
`
`delive
`
`Messa
`
`COM)
`
`is
`
`discl
`
`. MS
`
`users
`
`are
`
`often interested
`
`in
`
`getting a
`
`confirmation that a
`
`revious
`distribution was
`delivered,
`and
`perhaps under what conditions the distribution was
`delivered in, or under what conditions thetecipient ofa distribution experiences. A COMisis
`
`ermissions) between a COM sender and COMrecipient
`referabl
`by
`granting
`permissions in
`the LBX architecture. Permissions (e.g. local at MS) can also be used to govern which callers
`can receiv which OGM or an OGM at all. Permi
`lon can al o be used to den a
`nd c
`
`
`The terminology
`
`“MADR”, “MADR object”,
`
`and “presentation object”
`
`are used
`
`interchangeabl
`
`throughout this disclosure. A MADR is an object because it contains
`methods for processing.
`
`data
`
`along with associate
`
`A primary
`
`advantage
`
`herein is
`
`to
`
`save a novice
`
`user
`
`time from creating
`
`and
`
`testing new LBX
`
`harters
`
`for automated messaging
`
`pr
`
`ing. The
`
`parent applications
`
`discl
`
`tems an
`
`content delivery/presentation feature
`event determination and
`every
`omplishing
`methods for
`disclosed herein through a user's charter configurations, howeverit may be advantageous to
`provide user configurations through a presentation content-centric approach, in particular for
`operating system independent advertisement objects (i.e. MADRs) which can shared between
`systems. While there are convenient user interface embodiments derived from the parent
`applications for accomplishing functionally equivalent charters, a multi-purpose message
`reposit
`may
`replace charter configuration with a simpler user configuration theme. A rich
`
`latform from a presentation
`
`object vanta
`
`int is therefore
`
`provi
`
`. Many useful charters
`
`functionality can be conveniently configured through
`desired
`since
`be configured
`need not
`Message Area Data Records (MADRs). A MS may come prepackaged with MADR objects
`which may or may not be “tweaked”later to minimize a user's time in configuring charters for the
`samefunctionality. MADR objects may be shared between heterogeneous MSsordistributed to
`different types of MSs by services.
`
`
`
`EXHIBIT 1013 - PAGE 0006
`
`APPLE
`
`

`

`
`
`a
`
`It is an advantage herein forenablingusefuldistributedwithoutthenecessityofhavingaapplications
`
`
`
`
`
`5
`a
`nel
`ie
`am agictaring
`ith
`aruica
`NA
`inte
`
`Dp
`Dp
`ary
`p
`Aan_ambhacdiman
`
`
`
`webservice}providing useful non-advertising functionality in the same repository that may
`include advertising entities in order for users to enjoy having the repository regardless of any
`advertisement processing. Presentation and messaging objects which may
`be configured are
`useful to a user even if a single advertisement had never been configured. MADRs have many
`applications outside of advertising, however the architecture is designed with operating system
`independent advertisements in mind. A richer user experience is also provided through
`implementation of Caller Location (CLOC) information automatically appended to outbound
`application distributions including calls (audio or video) made. The receiving systems use the
`CLOC
`information of the caller for various automated
`processing. The CLOC is treated as
`importantly as caller identifier information and is carried in an analogous mannerwith calls.
`
`a
`
`An advantageherein is for advertisements to be maintained in the message repository with
`nough information to:
`ture
`the
`originator’
`.g.
`author)
`intent for being
`“user
`friendly”
`
`ture the originator's (e.g.
`and b
`reconciled with an observer's preferences for presentation:
`author) intent for being “userfriendly” reconciled with an observer's preferences for events
`which causethe presentation. U.S publication 2009/0265214 (“Advertising In Operating
`System”, Jobs et al) describes methods for advertising
`processing
`in an operating
`system.
`Conventional advertising formats are handled with a specialized operating system for how to
`r
`h
`vertisemen
`hat
`th
`rce
`(i.e.
`originator
`or
`author)
`ensur
`r maximizes
`
`i
`
`n
`r
`|
`mewhat
`ntrol
`|
`al
`is
`(e.g. viewer)
`recipient
`the
`ing while
`m
`whenpresentation is desired. The problem is the same advertisement maybetreated differently
`
`EXHIBIT 1013 - PAGE 0007
`
`APPLE
`
`

`

`at a different operating system. The originator (e.g. source, author,
`
`etc)
`
`of the advertisement
`
`loses automatic control over how the advertisement should
`
`be
`
`presented at any operatin
`
`information associated with the
`system. The present disclosure supports encoding
`advertisement for how any receiving operating system is to present it, and there are many
`configurations for when advertisements are best presented in a user-friendly manner, rather
`than forcing a userinto viewing a presentation by crippling or limiting operating system usability
`during a presentation. This disclosure has the advantage of supporting heterogeneous
`operating systems with unique advertisement presentation capabilities based on a recipient's
`referencesrelative to
`an
`originator
`(e.g. source,
`author,
`etc)
`intent, while
`doing s
`rding
`privileges, and in a “user-friendly” manner.
`
`t
`
`An advantageherein is for advertisements to be maintained in the same message repository
`that users find useful for OGM, OCM and COM processing. Advertisements can be presented
`unexpectedly in accordance with inbound or outbound application events and a set of
`associated MS conditions, or advertisements can be presented in an anticipated manner
`according to configurations. A data processing system sharing MADRs may or may not be a
`MS, but rather a privileged identity operating in a peer to peer, or service, mannerfor providing
`advertisements to MSs.
`
`Another advantageis supporting a variety of embodiments, such as having no centralized
`service for containin message information e.g. LBX embodiment or havin a centralized
`
`tem
`
`_“LAN-lin
`
`ing
`
`local
`
`data
`
`or remot
`
`ata, may
`
`incorporat
`
` regardle ofthe parti ulararchitectural emboiment for now injera t. Further, hard wire
`iscl
`fun tionality. In
`some
`embodiments,
`one,
`non
`val
`articipatin
`tems
`involve a
`
`wireless connected MS.
`
`EXHIBIT 1013 - PAGE 0008
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0009
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0010
`
`APPLE
`
`

`

`
`
`Another advantage hereinis to »akesupport information formats and purposesfor a variety of
`current and future application technologies while making useof existing marketplace
`communications hardware, communications methodsand software interfaces, and
`
`communicationsmethodsanclocation methodsavailable during.MS travels where© possible to
`
`accomplishi : } A Whi
`
`
`
`
` istril uting messages and providin resentations. Any wave spectrum and.any
`
`
`protocols for carrying data aspliesmay be used in embodiments described herein.
`
`EXHIBIT 1013 - PAGE 0011
`
`APPLE
`
`

`

`
`
`
`
`
`
`
`besteredatt4S.redundant storing of message information when more than one purposeis to
`be used for a message. Existing messages can be shared by applications and users. User's can
`customize messages and configurations in one place for many different applications. For
`example, a recorded messageleft by a first user (caller) can also be used by a second user
`callee)
`for an OGM or an OCM. Syneray
`is
`provided to different messaging
`platforms b
`providing a single messagerepository with a heterogeneousset of purposes, message formats,
`interoperable configuration, and uses.
`
`
`
`EXHIBIT 1013 - PAGE 0012
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0013
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0014
`
`APPLE
`
`

`

`
`
`
`stis-yetanetherAnother advantage is for automatic call fonwarding,catthandling,; and call
`
`
`
`
`
`
`
`the tanctionalitymprocessing |based onthewhereaboutsofaMS;orwhereaboutsofMS relative other MSs.ved for ified pur
`
`Yet another advantage 4ereis-is for peer to peer content delivery and local MS configuration of
`that content. Users need no connectivity to a service. Users-maketecalconfigurations+eenjey
`
`
`lecationbasedcontentdeliveryto-otherMSs—Contentis delivered undera variety of circumstances
`
`
`
`fora variety ofconfigurable Fereasons.s. Content-maintainedto-an-local ME ie deliversd asynchronously
`
`
`
`
`
`
` infactmadeavailabletothoseLBY. being users-For example,MSto MS‘communications(MS2MS)
`
`
`may be used for carrying out peer to peer processing for carrying out communicating one user's
`content configurations to another user's MS.
`
`
`
`EXHIBIT 1013 - PAGE 0015
`
`APPLE
`
`

`

`
`
`Another
`
`advantage is to
`
`su
`
`rt OGMs,
`
`and
`
`for
`
`configuring expressions which are used
`
`t
`
`vern which OGM plays
`
`to which caller. Expressions
`
`include
`
`a
`
`set
`
`of
`
`conditions which can
`
`
`
`
`etermined suchastime information, caller and identifier information, location information
`
`
`application data information, or other information which may be determined at a data processing
`system in real time.
`
`Another advantageis to support OCMs for enabling moreefficient use of a person's time. A
`person who wants to leave a message for another person can do so in a minimal amount of
`time by immediately ending the call upon determining the sought callee is not available, and that
`a messaae (i.e. OCM) should be left. Expressions (like OGM expressions) and user controls
`can be configured for automatic determination of the best OCM to leave at the callee's phone
`
`mailsystem.
`
`Another advantage 4
`
`
`
`
`5
`evar
`©
`:
`.
`2
`2
`avaitat
`4S-is integration
`
`
`of a MS user's defined waymarkinformation for automatic reference and annotation for
`informative purposes. For example, a user can make a call and automatically leave his
`whereabouts to a callee'
`tem in terms
`of
`personal waymark or map
`term information (Parent
`
`applications
`
`contain map
`
`term (Map Term Data Record
`
`(MTDR))
`
`information). Likewise, a user
`
`llee in terms of their personal waymark/pushpin
`of
`uts
`automatically know the where
`n
`or map term information when encountering message processing.
`
`
`
`EXHIBIT 1013 - PAGE 0016
`
`APPLE
`
`

`

`netwerkofMSs.COMs for automated
`
`presentation or indication when
`
`llee or distribution
`
`
`
`
`
`
`
`
`
`
`messaging of package status based on an evaluated expression.
`
`
`
`
`
`
`
`
`
`mail, been deliveredapreviouSMS/text m lendar item, etc) recipient has ll or
`
`istripution. An informative message can be automatically sent for a variety of conditions as
`described in an expression elaborated at the receiving system for receiving system conditions
`etermined in real time upon delivery. COMs
`provide informative messages for confirmation an
`circumstances about the receiving system during confirmation. Physical delivery or post office
`embodiments also apply, for example when a packageincluding a RFID or MS receives an
`inbound distribution containing an expression determined at the package for automated
`
`EXHIBIT 1013 - PAGE 0017
`
`APPLE
`
`

`

`Another advantage is automatically including
`
`location information with a message such as a
`
`request, or other distribution sent from one data
`data
`processing
`SMS/text message, email,
`ther information om lementing the lox ation
`to another.
`pro essin s stem e.C ._ MS)
`
`processing system can usethe included location and other information to provide directed and
`intelligent processing that would otherwise not be possible had the distribution been received
`without such information. Also, automatically including the information with the distribution
`prevents a user from having to perform user actions in explicitly providing the information.
`
`Another advantage is maintaining of statistical data for why, how, when, and where Message
`Area Data Record
`(MADR)
`data is used,
`and who is involved with related MADR processing.
`This provides meansfor reporting, for example how manytimes an advertisement was
`presented and under what circumstances it was presented.
`
`Yet another advantage
`
`is usin
`
`rmissions
`
`t
`
`vern every
`
`a
`
`t
`
`of MADR object
`
`pr
`
`in
`
`governing what
`for example reconciling an originator's intent with an observer's preferences,
`MADR post-creation maintenance/managementcan be performed by other users, deciding what
`an _be shared
`between systems, an
`verning each
`point
`of processing where more than one
`user (e.g. originator, maintainer, observer) may conflict in preferences for what MADR
`processing occurs. Permissions (privileges) can also be configured between users for an
`authority hierarchy for who can do what. This enables the distribution of MADR objects for
`prescribed processing that can be performed.
`
`Further features and advantagesof the disclosure, as well as the structure and operation of
`various embodiments of the disclosure, are described in detail below with reference to the
`accompanying drawings. In the drawings,like reference numbers generally indicate identical,
`
`functionallysimilar, and/orstructurally similar elements.. Theie-whichan elementdrawing Fest
`
`
`
`
`outlines (e.g. process blocks. data record fields) may beused irin the drawings to highlight, or
`indicate optional embodiments. None of the drawings, discussions, or materials herein is to be
`interpreted aslimiting to a particular embodiment. The broadestinterpretation is intended. Other
`embodiments accomplishing samefunctionality are within the spirit and scopeofthis disclosure.
`It should be understood that information is presented by example and many embodiments exist
`without departing from the spirit and scope of this disclosure.
`
`BRIEFDESCRIPTION OF #HEDRAWINGS
`
`There is no guarantee thatthere-are-descriptionsin this specification ferexplainingexplain every
`novel feature found in the drawings. Parent application drawings
`hav
`n inclu
`herein for
`ointing out
`some
`present disclosur
`tails
`in light of
`parent
`lications. The present
`disclosure will be described with reference to the accompanying drawings, wherein:
`
`
`
`FIG. 18 depicts a Location Based eXchanges(LBX)architectural illustration for discussing the
`presentdisclosure;
`
`EXHIBIT 1013 - PAGE 0018
`
`APPLE
`
`

`

`FIG. 162 depicts a Location Based Services (LBS) architecturalillustration for discussing prier
`artefthe present disclosure;
`
`FIG. +63 depicts a block diagram of a data processing system useful for implementing a MS,
`iLM,DLM,centratizedservera_ service, or any etherdata processing system carrying out disclosed
`hereinprocessing or functionality;
`
`FIG. +£4 depicts a networkillustration for discussing various depleyments-of
`whereaboutsdeployment embodiments
`of interconnectivity processing aspects of the present
`disclosure;
`
`
`
`FIG. 2€5 depicts an architectural illustration forr ciscussinganexampleofautomaticallylocatinga|
`
`AAAaCOMmunications between any two
`ena
`a
`p
`
`
`
`
`FIG. 2&6 depicts a flowchart for describing a preferred embodiment of a procedurefor inserting
`
`a Whereabouts Data Record (WDR) to an MS whereabouts data queue,_as described in detail
`in the parent applications;
`
`
`
`EXHIBIT 1013 - PAGE 0019
`
`APPLE
`
`

`

`
`
`FIG. 4447 depicts a preferred embodiment of a Whereabouts (or Wireless) Data Record
`
`
`(WDR) 1100 fordiscussingeperations-ofthepresentdisclesuredisclosedin detail in the parent
`applications;
`
`
`
`EXHIBIT 1013 - PAGE 0020
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0021
`
`APPLE
`
`

`

`
`
`FIGS. 398A through 398E depict athe preferred embodiment BNF grammarfor
`isclosed in
`detail in the
`parent
`
`lications:
`
`EXHIBIT 1013 - PAGE 0022
`
`APPLE
`
`

`

`
`
`FIG. 439 depicts a flowchart for describing a preferred embodimentof a procedure for
`configuring MS acceptanceof data from other MSs;
`
`FIG. 4410A depicts a flowchart for describing a preferred embodimentof a procedurefor
`sending MS data to another MS;
`
`FIG. 4410B depicts a flowchart for describing a preferred embodimentof receiving MS
`configuration data from another MS;
`
`
`
`EXHIBIT 1013 - PAGE 0023
`
`APPLE
`
`

`

`
`
`FIG. 5311 depicts a preferred embodimentof a Prefix Registry Record (PRR) ferdiseussing
`i
`i
`isclosed in
`detail in the parent applications:
`
`
`
`FIG. 5512A depicts a flowchart for describing a preferred embodiment of MS userinterface
`processing for Prefix Registry Record (PRR) configuration_disclosed in detail in the parent
`applications:
`
`FIG. 5512B depicts a flowchart for describing a preferred embodiment of Application Term
`(AppTerm) data modification_disclosed in detail in the parent applications;
`
`
`
`
`
`
`
`FIG. 5913A depicts a flowchart for describing a preferred embodimentof a procedure for
`
`
`
`to a remote MS;
`
`EXHIBIT 1013 - PAGE 0024
`
`APPLE
`
`

`

`
`
`FIG. 6413B depicts a flowchart for describing a preferred embodimentof perferming-_processing
`
`in-accordance-withconfiguredchartersfor receiving execution data from another MS:
`
`detail in the
`in
`FIG, 14 depicts a LBX application fields implementation status table disclosed
`
`parentapplications:
`
`FIG. 15 depicts anillustration for discussing various access embodiments to a message
`repository of the present disclosure;
`
`
`
`FIG. 6416A depicts aflowchartNotifyfordeseribing-a-preferred embodiment of a precedure-for
`
`
`
`commandactionMessage Area Data Record
`(MADR) for discussin
`nergistic message
`processing_and configuration;
`
`
`
`FIG. 65A16B depicts aflowchartferdescribing-a preferred embodimentof a precedurefer-Cempose
`command-actienLocation Reference Data Record (LRDR) for discussing message processing;
`
`FIG. 17 depicts a table to facilitate explanation of message repository data processing;
`
`
`
`FIG. 66418 depicts a flowchart for deseribing-a preferred embodimentofaprecedureforConnect
`
`command-actienfor MADR configuration processing;
`
`
`
`EXHIBIT 1013 - PAGE 0025
`
`APPLE
`
`

`

`FIG. 66619 depicts a flowchart for describingonea_preferred embodiment of a-precedurefor
`
`Cennectcommandactenapplication managementprocessing-as-derivedfromthe_precessingofHIG.
`66A;
`
`FIG. 67420 depicts a flowchart for deseribing-a preferred embodimentof a procedure for Find
`
`commandactionpreferred MADR processing_of a particular event for a particular application;
`
`FIG. 6921A depicts a flowchart for describing a preferred embodimentof a-precedureforCepy
`commandactionOCM processing;
`
`
`
`FIG. 70421B depicts a flowchart for describing a preferred embodiment of a-precedure-ferDiscard
`
`commandactienQCM background thread processing;
`
`FIG. 22A is a simplified block diagram depicting a preferred embodimentfor discussing
`architecture used to carry out mixing/multiplexing MADR data with an active call in progress;
`
`
`
`FIG. 74A-depicts-aflewehartfordeseribing22B is a simplified block diagram depicting a preferred
`
`
`
`embodimentefaprecedureforMeve-commandacticnfor discussing architecture used to carry out
`receiving an active call for OGM processing;
`
`
`
`EXHIBIT 1013 - PAGE 0026
`
`APPLE
`
`

`

`
`
`FIG. 73423 depicts a flowchart for describing a preferred embodiment of aprecedurefor
`AdministrationcommandactionOGM processing;
`
`
`
`
`FIG. 73€24 depicts a flowchart for describing ene-embedimentofaprecedureforAdministration
`commandactionpreferred embodiments of AD event configuration processing,as-derivedfromthe
`
`precessing-ofHIG-73A)
`
`FIGEIGS. 7425A depictsand 25B depict a flowchart for describing a preferred embodimentof a
`
`procedure forChange-commandactionprecessingpresenting MADR information;and
`
`FIG. 75826 depicts a flowchart for describing a preferred embodimentof application information
`
`
`resolution processing-ferreceivingexecutiondatafrem-anetherMS:.
`
`
`
`
`DETAILED DESCRIPTION-OFFHEINVENFHON
`
`With reference now to detail of the drawings, the present disclosure is described. Obvious error
`handling is omitted from the flowcharts in order to focus on the-key aspects-ofthe-present
`disclosure. Obvious error handling includes database I/O errors,field validation errors, errors as
`the result of database table/data constraints or unique keys, data accesserrors,
`communicationsinterface errors or packetcollision, hardware failures, checksum validations, bit
`error detections/corrections, and any other error handling as well known to thoseskilled in the
`relevant art in context of this disclosure. A thr
`nchronization
`scheme
`(e.g.
`semaphor
`is assumed where appropriate. A semicolon may be usedin flowchart blocks to represent, and
`separate, multiple blocks of processing within a single physical block. This allows simpler
`
`EXHIBIT 1013 - PAGE 0027
`
`APPLE
`
`

`

`
`flowcharts with Jessfewer blocks in the drawings by placing multiple blocks of processing
`description in a single physical block of the flowchart. Flowchart processing is intended to be
`interpreted in the broadest sense by example, and notforlimiting methods of accomplishing the
`same functionality. Preferably, field validation in the flowcharts checks for SQL injection attacks,
`communications protocol sniff and hack attacks, preventing of spoofing system or MS
`addresses, syntactical appropriateness, and semantics errors where appropriate. Disclosed
`user interface processing and/or screenshots are also preferred embodiment examples that can
`
`be implemented in ethervarious ways without departing from the spirit and scopeofthis
`disclosure. Alternative user interfaces (since this disclosureis not to be limiting) will use similar
`mechanisms, but may usedifferent mechanisms without departing from the spirit and scope of
`
`this disclosure.
`
`EXHIBIT 1013 - PAGE 0028
`
`APPLE
`
`

`

`
`
`Novel features disclosed herein need not be provided asall or none. Certain features may be
`isolated in some MS-embodiments, or may appear as any subsetof features and functionality in
`
`other embodiments.
`
`EXHIBIT 1013 - PAGE 0029
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0030
`
`APPLE
`
`

`

`
`
`EXHIBIT 1013 - PAGE 0031
`
`APPLE
`
`

`

`
`
`FIG. 18 depicts a Location Based exchangeseXchanges (LBX) architecturalillustration for
`discussing the present disclosure. LBX MSsare peers to eachotherfor ‘ecatienalfeatures and
`functionality. An MS 2 communicateswith other MSs without requiring a common functionality
`social service for interaction. For example, FIG. 18 depicts a wireless network 40 offive (5)
`MSs. Eachis able to directly communicate with others thatarein the vicinity (e.g. nearby as
`
`indicated by within a maximum wireless range-43906). In a preferred embodiment,
`communicationsare limited reliability wireless broadcast datagrams having recognizable data
`packetidentifiers. In another embodiment, wireless communicationsare reliable transport
`protocols carried outt by the MSs, such as TCP/IP. In other embodiments, usual communications
`
`data a
`ith-oth
`a
`ate.
`A
`04}(e.g. during
`wireless phone call conversations) nudesnewdatain transmissions for peng recognizedby
`
`MSswithin the vicinity.
`
`axa
`
`an
`
`AYER
`
`2
`
`
`
`
`
`simely communications