throbber
WO 01/45343
`
`PCT/GB00/04512
`
`35
`
`within the presence management system is provided to manage
`
`these profiles.
`
`For example, an entity's profile contains the following
`
`items which may be entered by the entity or watched party or
`
`may be default information that is prespecified :-
`
`e Contact addresses for that entity on each of a number of
`
`access communications networks or component parts of an
`
`access communications network.
`
`“e
`
`10
`
`A set of
`the possible context presence values
`for
`the
`entity, e.g. sat hotie®, “at-work”, “travelling”, “not-able-
`ee “unknown”. For many of these the system also
`
`holds attributes, e.g. geographical location.
`
`e Minor changes
`
`to the default
`
`rules
`
`for moving from one
`
`context presence to another.
`
`15
`
`20
`
`e The entity’s own view of what potential
`
`audiences
`
`its
`
`exposed presence has, e.g.
`
`family,
`
`friends,
`
`colleagues.
`
`Members
`
`of
`
`each potential
`
`audience
`
`see a different
`
`projection of
`
`the entity's presence.
`
`In application to
`
`enterprises,
`
`the administrator is able to provide audience
`
`definitions
`
`common
`
`to
`
`many
`
`entities
`
`(ct:
`
`E-mail
`
`distribution lists).
`
`e
`
`A watcher authentication level
`
`for each audience to allow
`
`the entity to have safeguards that a watcher really does
`
`belong to an audience.
`
`25
`
`° For
`
`some sorts of
`
`communication
`
`(e.g.
`
`instant messages
`
`informing of new E-mail)
`
`the entity may wish to exercise
`
`fine-grained control and insist on the watcher making a
`
`SUBSTITUTE SHEET (RULE26)
`
`Epic Games Ex. 1029
`Page 80
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`36
`
`micro-subscription. The attributes of such a subscription
`can also be
`subject "
`€0
`an entity’s
`rules
`(cf. E-mail
`
`filters)
`
`When
`
`an entity is
`
`first
`
`registered with a presence
`
`5 management system server 10 there is a substantial amount of
`data capture required.
`In order
`that
`the work-load of
`the
`entity is reduced reliance is put on default
`information and
`
`a
`
`type of
`
`“wizard”
`
`is used to help the user enter
`
`the
`
`required information quickly and easily. Later,
`
`the data can
`
`10
`
`be
`
`subsequently modified by the watched party or entity.
`
`These
`
`functions are carried out by the profile management
`
`system 56.
`
`For example,
`
`in the case of an entity representing a
`
`human user
`
`the interaction provided by the “wizard” data
`
`15° Capture process can be as follows:
`
`e The user chooses
`
`from a number of
`
`life-styles,
`
`“office-
`
`worker”, “travelling-salesman” or “executive”.
`
`Each life-
`
`style being represented by a template with default values.
`e Each choice leads to a dialog tailored for
`that choice.
`
`20
`
`the
`location of
`to establish the geographical
`For example,
`home and of the office. Additional
`locations are created if
`
`appropriate.
`
`e
`
`In one embodiment,
`
`the presence management system is able
`
`to detect and capture details about
`
`the devices that
`
`the
`
`25
`
`entity uses for communicating.
`e Definitions of potential audiences for the user’s npewende
`
`(family,
`
`friends etc.)
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 81
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`37
`
`e Finally,
`
`the user will decide which contact
`
`information is
`
`notified to members of which audiences for what changes in
`context presence.
`
`Some parts of the configuration are complicated and these are
`
`initially masked from the user until they press the “advanced
`
`options” button.
`
`The presence management
`
`system also contains
`
`a
`
`raw
`
`presence manager 55 which manages an .unprocessed collection
`
`of presence indicators.
`
`The raw presence. manager 55 orders
`
`10
`
`the presence indicators into a table or other structure which:
`
`is indexed by entity.
`
`In this way each presence indicated is
`
`accessible on the basis of
`
`the entity to which it relates.
`
`Large volumes of presence indicators can be stored by the raw
`
`presence manager 55. However, by their very nature, presence
`
`15
`
`indicators
`
`become
`
`redundant
`
`once more
`
`recent’
`
`presence
`
`indicators
`
`about
`
`a given entity become available
`
`and
`
`a
`
`process for updating presence indicators or giving weights to
`
`these indicators on the: basis of age is provided.
`
`The multiple access communications network 11 is made up
`
`20
`
`a public
`such as
`of one Or more communications networks,
`switched telephone network 52 and a wireless communications
`network 51.
`An event gateway,
`specific to the type of
`communications network,
`is provided for _— communications
`
`network or each technology,
`
`such as mobile telephones
`
`and
`
`25
`
`copper wire telephones. Note that
`
`the Internet
`
`is logically
`
`a
`
`federation of
`
`several access networks
`
`and a core data
`
`network using a common Internet Protocol
`
`(IP) substrate.
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic GamesEx. 1029
`Page 82
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`38
`
`
`
`Event from the=accessgateways receive raw data
`
`
`
`
`
`
`
`networks, pre-process this and pass it onto the raw presence
`
`Manager via one or more event
`
`inputs 16.
`
`Examples of
`
`these
`
`events are keyboard activity on a terminal, movement between
`
`cells in a cellular communications network and change of VLR
`
`(Visitor Location Register)
`
`and off-hook events
`
`in a PSTN.
`
`Other events include use of
`the “last offered incoming call”
`service on a public switched peLepnens network, details from
`
`calendar services and the opening of a Palm Pilot
`
`7
`
`(trade
`
`mark)
`lid.
`Event gateways produce an authenticated,
`time
`ordered series of
`location data
`events
`that
`have aan
`
`filtered and homogenised.
`
`That
`
`is, only information about
`
`users being tracked by this presence system is passed to the
`
`raw presence manager.
`
`This is achieved by using a filter in
`
`the event gateway or
`
`in the events input 16.
`
`Also, events
`
`technology
`in a
`are presented to the raw presence manager
`neaeee format
`(all
`the idiosyncrasies of different access
`
`network technology are hidden by the event gateway as far as
`
`possible).
`
`An event gateway is divided into two parts.
`
`A first
`
`part interfaces with the presence management system10 whilst
`
`a second part
`
`interfaces with the access network.
`
`The two
`
`parts of
`
`the event gateway communicate using a protocol over
`
`an interface. Different
`
`types of event gateway are provided:
`
`10
`
`15
`
`20
`
`25
`
`according to the type of access network used.
`
`As described above a subscription is made when a watcher
`
`registers
`
`an
`
`interest
`
`in the presence of
`
`an entity.
`
`A
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 83
`
`

`

`WO 01/45343
`
`;
`
`PCT/GB00/04512
`
`39
`
`subscription manager
`
`57
`
`is provided within the presence
`
`Management
`process.
`
`system 10
`
`in order
`|
`
`to manage
`
`the subscription
`
`Users or
`
`services
`
`(watching parties) outside of
`
`the
`
`presence management
`
`system may
`
`subscribe
`
`to
`
`presence
`
`the
`information about particular clients (watched parties) of
`presence system.
`If the presence management system comprises
`
`multiple servers this request
`is routed to the home server
`for the client
`(watched See in question.
`The subscription
`
`request
`
`is made over one of a number of protocols:
`
`IMPP, WAP
`
`or possibly IcQ.
`
`In each case
`
`the
`
`subscription request
`
`contains
`
`a
`
`return address
`
`for notifications (e.g.
`
`an IMPP
`
`address),
`
`some identification information for the subscriber
`
`or watching party (so that
`
`the presence client's propagation
`
`restrictions can be obeyed) and the identity of
`
`the presence.
`
`client about whom presence information is sought.
`
`In
`
`one
`
`example,
`
`the 1itecine of a subscription is
`
`controlled by the subscriber,
`
`i.e.
`
`the subscriber
`
`(watching
`
`party) declares when its interest
`in a given presence client
`is over.
`However,
`if the watching party does not
`take “—
`action
`declare
`the
`end
`of
`its’
`interest "seme
`old
`
`to
`
`subscriptions
`
`eventually become garbage.
`
`In
`
`one
`
`case,
`
`subscriptions are held persistently (for fault
`
`recovery) and
`
`10
`
`15
`
`20
`
`this creates an issue of garbage collection.
`
`For example,
`
`25
`
`all
`
`subscriptions
`
`that are inactive for one hour may be
`
`deleted.
`
`SUBSTITUTE SHEET (RULE26)
`
`Epic Games Ex. 1029
`Page 84
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`40
`
`In
`
`the
`
`case of
`
`Instant Message notification of
`
`an
`
`awaiting e-mail,
`
`for example,
`
`the decision on whether
`
`the
`
`client
`
`is “on-line” to a particular e-mail notification may
`
`be
`
`a
`
`function of
`
`the
`
`sender,
`
`the
`
`size and possibly of
`
`Rather
`than the
`keywords within the subject of
`the e-mail.
`information at
`subscriber presenting this,
`second order,
`the
`point
`of
`sending
`the
`Instant Message,
`the
`initial
`
`subscription may capture all
`
`the information upon which the
`
`reachability decision is made. What might have been a single
`
`subscription by an e-mail notification service regarding a
`
`single client may then be replaced by a set of
`
`fine-grained
`
`subscriptions
`
`each regarding that client’s willingness
`
`to
`
`receive a certain e-mail notification.
`
`In this
`
`case,
`
`IMPP
`
`is
`
`extended to carry additional
`
`parameters.
`
`This may be in the form of an XML string.
`
`For
`
`example,
`
`in the case of an e-mail notification service,
`
`the
`
`IMPP subscribe also contains <subscription-detail
`
`type="IM”
`
`reftype="e-mail”
`from="fred”">. One possibility is that
`the
`presence system eenpenda to such a subscription by asking for
`further
`information. e.g.,
`if
`the
`rules asserted by
`the
`
`client cover
`
`the “to”
`
`field of
`
`the e-mail
`
`(i.e. who else
`
`has/will
`
`receive it)
`
`then the response
`
`is
`
`to refuse the
`
`subscription giving an appropriate reason.
`
`10
`
`15
`
`20
`
`The presence management
`
`system 10
`
`also comprises
`
`an
`
`25
`
`exposed presence manager 58 as illustrated in Figure 5.
`
`As
`
`described above “exposed presence” is a view of an entity’s
`
`presence
`
`that
`
`is
`
`exposed
`
`to a watcher.
`
`It
`
`is derived
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 85
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`41
`
`according to rules defined for that entity and in this way,
`
`an entity exhibits different exposed presences to different
`
`audiences.
`
`The function of
`
`the exposed presence manager 58
`
`is to “decide” what
`
`information to make available to watching
`
`parties on the basis of
`
`rules 15 and other criteria set by
`
`watched parties or defined as defaults.
`
`In the case that
`
`there is a change in the information
`
`available,
`for example, because new information arrives via
`an event gateway 53,
`then the exposed presence manager 58 25
`
`10
`
`triggered.
`
`The
`
`exposed presence manager
`
`then checks
`
`for
`
`active subscriptions to the watched party in respect of whom
`
`the
`
`new
`
`information
`
`has
`
`arrived.
`
`Tf
`
`some
`
`active
`
`subscriptions are present,
`
`the exposed presence manager
`
`58
`
`consults”
`
`the
`
`rules
`
`15
`
`and
`
`determines what
`
`(if
`
`any)
`
`15
`
`information to make available to the watching parties who
`
`‘have active subscriptions.
`
`The presence management
`
`system 10 may also have
`
`an
`
`interface 59
`
`to ICQ and/or
`
`IMPP
`
`60 or WAP
`
`61 protocol
`
`outputs.
`
`Information that
`
`is made available to watching
`
`20
`
`parties who have active subscriptions can be made via this
`
`interface 59 or these outputs.
`
`The
`
`presence management
`
`system also
`
`comprises
`
`a
`
`connection manager 59
`
`in some examples.
`
`In the cases that
`
`the presence management system itself forwards communication
`
`25
`
`requests direct’ to watched parties,
`
`the connection manager 59
`
`provides this forwarding facility using connect gateways 54.
`
`At
`
`least one connect gateway 54 is provided for each type of
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 86
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`42
`
`access network.
`
`Part of
`
`the
`
`function of
`
`the connection
`
`manager 59 is to “decide” which connect gateway 54 should .be
`
`used for
`
`a particular communication request
`
`and to manage
`
`changes
`
`between
`
`connect
`
`gateways
`
`54
`
`according
`
`to.
`
`the
`
`communication requirements.
`
`As well as this the connection
`
`manager determines which access media is used for
`
`a given
`
`interaction in the event
`
`that more than one access medium is
`
`available and suitable.
`
`10
`
`15
`
`20
`
`In one embodiment the connection manager 59 comprises a
`
`mediation component 62. This enables messages in one format
`e.g. voice to be changed into another format e.g. email,
`in
`
`order to provide flexibility for watched parties and watching
`
`parties.
`
`The mediation component 62 uses rules to decide
`
`whether and how best to change the format of a given message.
`
`The presence management
`
`system also comprises
`
`a
`
`raw
`
`presence manager 55.
`
`The raw presence manager 55 obtains and
`
`stores information from the event gateways
`53 and processes
`this
`information to
`form a
`“context prewencee
`for
`each
`
`watched party.
`
`A plurality of default contexts are defined
`
`such
`
`as
`
`“at
`
`home’,
`
`“at work
`
`desk",
`
`“travelling”
`
`and
`
`information received from the event gateways 53 together with
`
`other watched party information is used'to determine which
`
`context applies for
`
`a given watched party at
`
`a particular
`
`time. Rules are used to aid this determination process.
`
`For
`
`25
`
`example,
`
`rules for mapping location indicators onto presence
`
`contexts are pre-defined. Watched parties are also able to
`
`enter their own rules and presence contexts for use by the
`
`SUBSTITUTE SHEET(RULE 26)
`
`Epic Games Ex. 1029
`Page 87
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`43
`
`raw presence manager 55.
`
`The rules used by the raw presence manager 55 and the
`
`exposed presence manager
`
`58 are always
`
`locally resolvable.
`
`Many of
`
`the other
`
`components of
`
`the presence management
`
`system use rules.
`
`These may be stored in one rule base or
`
`alternatively stored in conjunction with
`
`the particular
`
`components of
`
`the presence management system.
`
`For .example,
`
`the connection manager
`
`59 uses
`
`rules
`
`to. decide which of
`
`several possible connection options to prefer.
`
`10
`
`The
`
`interface between the raw presence manager
`
`55 and
`
`the exposed presence manager 58 may be distributed.
`managers
`55,
`58
`have different requirements.
`
`The two
`The
`raw
`
`presence manager 55 makes only local updates to a data store
`14 based on its input data. It exhibits a low latency so that
`location data from event gateways
`53 need not be backed up
`
`persistently.
`That
`is, once processed by the raw presence
`Manager 55 any sugaimieané changes are held in the data store
`
`14.
`
`The
`
`exposed presence manager
`
`58 has
`
`to engage
`
`in a
`
`number of external
`
`interactions, over a variety of protocols
`
`to propagate ‘presence information to subscribers.
`
`It
`
`is
`
`either triggered directly from the data store 14, as a reflex
`to the updates made by the raw presence manager 55 or
`there
`is a direct Likertade between the two.
`
`In
`computer
`
`computer
`a
`embodiment
`one
`readable medium is orovided.
`
`a
`program stored on
`Figure 6
`is a
`flow
`
`diagram of the method implemented by the computer program.
`
`15
`
`20
`
`25
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 88
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`44
`
`This
`
`computer
`
`program is
`
`adapted to control
`
`a presence
`
`management
`system such that connections are managed between
`watching parties
`and watched parties.
`This
`presence
`
`Management
`
`system is suitable for use in a multiple access
`
`communications network, and said computer program is arranged
`
`to control said presence management system such that:-
`
`(i)
`
`a store of watched party information is created (box 701
`
`of Figure 6);
`
`(ii)
`
`a set of rules about connection criteria are formed (box
`
`10
`
`702 of Figure 6);
`
`(iii) information about events
`
`that occur
`
`in said multiple
`
`access communications network is received in use via an
`
`input
`
`(box 703 of Figure 6); and
`
`(iv) connection requests are received from watchers in use;
`
`15
`
`20
`
`and on receipt of a request
`
`from a watching party for a
`
`connection with a watched party,
`
`information about
`
`whether that watched party currently permits connections
`
`to be established with it is provided, said information
`
`being determined on the basis of said store, said rules
`and suia inmgae
`information about events; and wherein at
`
`least one party is a service (box 704 of Figure 6).
`
`Figure 7 is a flow diagram of another example of such a -
`
`method implemented by a computer program.
`
`In this case,
`
`25
`
`watched parties first register 801 with a presence management
`
`system and input
`
`information 802 which is used to form rules.
`
`This
`
`information is about
`
`the watched party’s communication
`
`SUBSTITUTE SHEET (RULE26)
`
`Epic GamesEx. 1029
`Page 89
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`45
`
`terminal he
`types of
`such as what
`criteria and preferences,
`or she uses and which modes of commundeation are preferred at
`
`different times of the day.
`
`The presence management system may then receive a number
`
`of different types of input.
`
`For example, a subscription 803
`
`from a watching party may be received,
`
`in which case the
`
`subscription details are recorded 809.
`
`For example,
`
`this
`
`could be a request by a watching party to be informed about
`
`any change of state in a watched party.
`
`10
`
`The presence management
`
`system may also receive
`
`an
`
`incoming
`
`event
`
`804.
`
`‘In
`
`this
`
`case,
`
`the method
`
`involves
`
`checking 805 all
`
`the current subscriptions
`
`to see
`
`if
`
`the
`
`incoming
`
`event
`
`is
`
`relevant
`
`to
`
`any
`
`of
`
`these.
`
`If
`
`so,
`
`notifications are sent out B06 to the watching parties who
`made
`the
`relevant’
`subscriptions. ~
`The
`record
`of
`the
`
`15
`
`subscriptions
`
`is
`
`then
`
`updated
`
`805.
`
`For
`
`example,
`
`a
`
`subscription may be arranged to be activated only once and
`
`then deleted.
`
`The presence management
`
`system may also receive an
`
`20
`
`incoming connection request 807
`from a watching party.
`In
`this
`case
`the
`presence management
`system checks "the
`availability of
`the watched
`party
`and
`if
`appropriate
`
`establishes a connection or
`
`forwards
`
`the connection request
`
`to the watched party 808.
`
`25
`
`In one example,
`
`a presence management system comprises:
`
`a first
`
`input arranged to receive requests
`
`from watching
`
`parties in use, each of which may be of one of
`
`three types:
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 90
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`46
`
`(a)
`
`a. notification request being in respect of
`
`a watched
`
`party and,
`
`optionally,
`
`a
`
`specific
`
`event,
`
`(b)
`
`a
`
`contact
`
`request
`
`in respect of a watched party, or (c) a fetch request
`
`in respect of
`
`a watched party.
`
`The presence management
`
`system also
`
`has
`
`a
`
`second
`
`input
`
`arranged
`
`to
`
`receive
`
`information about events,
`
`relating to said watched parties,
`
`that occur
`
`in said multiple access communications network in
`
`use.
`
`As well as this a third input
`
`is provided, arranged to
`
`receive and store information entered by a watched party.
`
`10
`
`This
`
`information relates to the said watched party and is
`
`used to transform the incoming events and control watching
`
`parties in respect of
`
`the information that
`
`they may receive
`
`about
`
`the watched party.
`
`The information is stored so that
`
`it
`
`can be associated with the watched party to which it
`
`15
`
`relates.
`
`The presence management
`
`system has
`
`a processor
`
`arranged such that
`
`in use, when information about an event
`
`relating to a particular watched party is
`
`received,
`
`the
`
`information is transformed in accordance with the information
`
`previously received from the watched party. When information
`
`20
`
`about
`
`an event
`
`relating to a particular watched party is
`
`received, any watching parties who. made woLTeAeatton requests
`
`about
`
`that particular watched party are notified.
`
`This
`
`is
`
`done provided that
`
`the stored information does not
`
`forbid or
`
`restrict
`
`the transmission of
`
`a notification at
`
`that
`
`time.
`
`25
`
`For example,
`
`the watching party may have specified that he or
`
`she should not be interrupted between 9
`
`am and 10 am.
`
`Ifa
`
`contact request
`
`is received, contact
`
`is only established by
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 91
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`47
`
`the presence management system if the required terminals are
`
`available and if the user preferences of both parties allow
`contact
`to be eeeapienes.
`If a fetch request
`is received,
`
`part or all of the information relating to a watched party is
`
`transmitted
`
`to
`
`the watching
`
`party,
`
`according
`
`to
`
`user
`
`preferences and criteria set by the watched party.
`
`In this
`
`way
`
`a watching party can quickly and easily obtain all
`
`available information about a watched party.
`
`the
`A range of applications are within the scope of
`present
`invention. These include any presence sanugemedt:
`systems in which a warched party is able to control who has
`
`access to his or her direct contact details and for how long;
`
`the watched party can also prevent others from gaining access
`
`to his or her direct contact details.
`
`The
`
`invention also
`
`encompasses
`
`a
`
`computer
`
`program for
`
`controlling such
`
`a
`
`presence
`
`management
`
`system
`
`and
`
`a multiple
`
`access
`
`communications
`
`network which
`
`comprises
`
`such
`
`a
`
`presence
`
`management system.
`
`10
`
`15
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 92
`
`

`

`WO 01/45343
`
`Claims
`
`48
`
`PCT/GBO00/04512
`
`1.
`
`A presence management
`
`system suitable for use
`
`in a
`
`multiple
`
`access
`
`communications
`
`network
`
`by watching
`
`parties and watched parties,
`
`said presence management
`
`system comprising:-
`
`(i)
`
`an input arranged to access a store of watched party
`
`information;
`
`(ii)
`
`information about connection criteria;
`
`(iii)
`
`an input arranged to receive information about events
`
`10.
`
`that
`
`occur
`
`in said multiple
`
`access
`
`communications
`
`network in use; and
`
`(iv)
`
`an input arranged to receive connection requests
`
`from
`
`watchers in use;
`
`and wherein said presence management
`
`system is arranged such that,
`
`in use, on receipt of a
`
`15
`
`request
`
`from a watching party for a connection with a
`
`watched party,
`
`a connection address
`
`for
`
`that watched
`
`party is provided under controlled conditions,
`
`said
`
`conditions being determined on the basis of said watched
`
`party information,
`
`said information about
`
`connection
`
`*20
`
`criteria and said input information about events.
`
`A presence management
`
`system as
`
`claimed in Claim 1
`
`wherein said connection address is only operable for a
`
`limited time.
`A pxevemee Management system as claimed in claim 1 or
`
`25
`
`claim 2 wherein said connection address is only operable
`
`for a limited number of connection attempts.
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 93
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`49
`
`A presence management system as claimed in any preceding
`
`claim wherein the request
`
`from the watching party is
`
`forwarded to the connection address provided,
`
`in such a
`
`way
`
`that
`
`the watching party has
`
`no
`
`access
`
`to that
`
`connection address.
`
`A presence management system as claimed in any preceding
`
`claim wherein
`
`at
`
`least
`
`one of
`
`the parties
`
`is
`
`an
`
`automated service.
`
`A presence management
`
`system as
`
`claimed in claim 5
`
`10
`
`wherein said automated service is a watching party.
`
`A presence management
`
`system as
`
`claimed in claim 5
`
`wherein said automated service is a watched party.
`
`A presence management system as claimed in any preceding
`
`claim wherein at
`
`least one of said parties comprises a
`
`15
`
`plurality of individuals.
`
`A presence management system as claimed in any preceding
`
`claim wherein said presence management system is further
`
`arranged to provide information about
`
`the geographical
`
`locationof a watched party in use, on the basis of said
`received information about events
`that occur
`in said
`
`multiple access communications network.
`A presence management system as claimed in any preceding
`
`10.
`
`claim wherein said presence management system is further
`
`arranged
`to
`activity of
`
`provide
`information
`a watched party,
`on
`
`about
`the
`current
`the ee of
`said
`
`received information about events
`
`that occur
`
`in said
`
`multiple access communications network.
`
`20
`
`25
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 94
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`50
`
`11.
`
`A presence management system as claimed in any preceding
`
`claim wherein
`arranged
`to
`
`said
`provide
`
`presence management
`information
`about
`
`system is
`types
`of
`
`connection that a watched party is able to participate
`
`in.
`
`12.
`
`A presence management system as claimed in any preceding
`
`10
`
`13.
`
`claim which further comprises a monitor for monitoring
`said received information about events and wherein said
`presence management
`system is
`arranged
`cor provide
`information about
`a change in the availability of
`a
`
`watched party.
`
`A presence management system as claimed in any preceding
`claim wherein said store of watched party information
`
`comprises watched party connection preferences.
`
`15
`
`14.
`
`A presence management system as claimed in any preceding
`
`15.
`
`20
`
`Claim and wherein
`
`a plurality of
`
`said events
`
`are
`
`initiated
`
`by
`
`watched
`
`parties
`
`and
`
`comprise
`
`a
`
`communication via said multiple access network.
`
`A computer program stored on a computer readable medium,
`
`said computer
`
`program being
`
`adapted
`
`to
`
`control
`
`a
`
`presence management
`
`system,
`
`said presence management
`
`system being suitable for use
`
`in a multiple access
`
`communications network by watched parties and watching
`
`parties, said computer program being arranged to control
`
`25
`
`said presence management system such that:-
`
`(i)
`
`a store of watched party information is accessed;
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic GamesEx. 1029
`Page 95
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`51
`
`(22)
`
`information about connection criteria is accessed;
`
`(iii) information about events
`
`that occur
`
`in said multiple
`
`access communications network is received in use via an
`
`input; and
`
`5
`
`(iv)
`
`connection requests are received from watchers in use;
`
`and on receipt of a request
`
`from a watching party for a
`
`connection with a watched party,
`
`a connection address
`
`for
`
`that watched party is provided under controlled
`
`conditions,
`
`said conditions being determined on
`
`the
`
`basis
`
`of
`
`said watched
`
`party
`
`information,
`
`said
`
`information about connection criteria and said input
`
`information about events.
`
`16.
`
`A multiple access communications network comprising a
`
`presence management
`
`system,
`
`said presence management
`
`system being for use by watching parties and watched
`
`parties, said presence management system comprising: -
`
`(i)
`
`An
`
`input arranged to access a store of watched party
`
`10
`
`15
`
`information;
`
`20
`
`(ii)
`
`information about connection criteria;
`
`(iii)
`
`an input arranged to receive information about events
`
`that
`
`occur
`
`in
`
`said multiple
`
`access
`
`communications
`
`network in use; and
`
`(iv)
`
`an input arranged to receive connection requests from
`watchers
`in use;
`and wherein said presence management
`
`25
`
`system is arranged such that,
`
`in use,
`
`on receipt of a
`
`request
`
`from a watching party for a connection with a
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic GamesEx. 1029
`Page 96
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`52
`
`watched party,
`
`a connection address
`
`for
`
`that watched
`
`party is provided under controlled conditions,
`
`said
`
`conditions being determined on the basis of said watched
`
`party information,
`
`said information about
`
`connection
`
`criteria and said input
`
`information about events.
`
`17.
`
`A method of operating a presence management
`
`system
`
`suitable for use in a multiple access
`
`communications
`
`\
`
`network,
`said presence management system being for use
`by watching parties and watched parties, at least one of
`
`10
`
`said parties being an automated service,
`
`said method
`
`15
`
`20
`
`comprising the steps of:-
`
`(i)
`
`(ii)
`
`accessing a store of watched party information;
`
`accessing information about connection criteria;
`
`(iii) receiving information about events
`
`that occur
`
`in said
`
`multiple access communications network; and
`
`(iv)
`
`‘on
`
`receipt of
`
`a request
`
`from a watching party for
`
`a
`
`connection with a watched party,
`a connection address
`for
`that watched party is provided under controlled
`
`conditions,
`
`said conditions being determined on
`
`the
`
`basis
`of
`said watched
`party
`information,
`said
`in®ocnattod about connection criteria and .said input
`
`information about events.
`
`SUBSTITUTE SHEET (RULE26)
`
`Epic Games Ex. 1029
`Page 97
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`16
`
`12
`
`| 10
`
`13
`
`
`
`WATCHED
`PARTY
`INFORMATION
`
`
`
`
`
`
`
`
`MULTIPLE ACCESS
`COMMUNICATIONS
`NETWORK
`
`11
`
`
`
`WATCHED
`PARTY
`
`
`INFORMATION |
`
`
`
`MULTIPLE ACCESS
`COMMUNICATIONS .
`NETWORK
`
`
`
`11
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 98
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`2/6
`
`
`
` TICKET
`
`AGENCY
`
`WATCHED
`
`SERVICE
`PARTY
`
`
`
`INFORMATION
`
`
`11
`
`
`
` MULTIPLE ACCESS
`COMMUNICATIONS
`NETWORK
`
`anaes
`
`
`INFORMATION |
`
`
`PARTY
`
`
`
`
`MULTIPLE ACCESS
`
`COMMUNICATIONS
`NETWORK
`
`
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic GamesEx. 1029
`Page 99
`
`

`

`PCT/GB00/04512
`
`LINIWISVNV
`
`31140ud
`
`"MOW
`
`'
`
`JONASIud
`
`Mva
`
`vivawasn
`
`sainywasn
`
`SNOLLdIUSANS
`
`si1nv4ad
`
`gas0dx3
`
`JINISAMd
`
`‘MSW
`
`LNIWSOVNVW
`
`QL“et
`
`SalLuVdGAHOLVM
`
`OL
`
`LS
`
`WO 01/45343 eS
`NOILLOANNOD Yt
`
`NOLLdINOSENS
`
`
`‘NHLINY=S3TNY | ‘NLVIG3)
`
` tS3ILYVdSNIHDLVM
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 100
`
`
`
`
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`4/6
`
`CREATE A STORE OF WATCHED PARTY INFORMATION
`
`701
`
`FORM A SET OF RULES ABOUT CONNECTIONCRITERIA
`
`
`
`
`
`
`ACCEPT INPUT INFORMATION ABOUTEVENTS THAT OCCUR
`
`IN THE MULTIPLE ACCESS COMMUNICATIONS NETWORK
`
`_
`
` IF A CONNECTION REQUESTIS RECEIVED FOR CONNECTION TO
`AWATCHEDPARTY THEN:
`
`DETERMINE WHETHER THAT WATCHED PARTY CURRENTLY
`PERMITS CONNECTIONS TO BE ESTABLISHED WITHIT ON THE
`BASIS OF THE STORE, RULES AND INPUT INFORMATION; AND
`
`PROVIDE THE DETERMINED INFORMATION
`
`
`
`
`
`
`
`
`704
`
`Fig. 6
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 101
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`5/6
`
`801
`
`REGISTER
` 802
`
`803
`
`
`INCOMING
`INCOMING
`
`CONNECTION
`SUBSCRIPTIONS
`
`
`REQUESTS
`
`
`
`
`LOOK AT
`
`
`SUBSCRIPTIONS;||MAKE - SenTION 809
`
`
`
`
`
`CONNECTION
`
`
`
`
`
`808
`
`UPDATE RULES
`
`NOTIFICATION
`
`806
`
`Fig. 7
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 102
`
`

`

`WO 01/45343
`
`PCT/GB00/04512
`
`6/6
`
`
`
`JIDIAYNASTWNYALX3
`
`
`
`NI-MO3HOANITHIV
`
`‘NOILVULSIDSY
`
`
`
`T3LOH‘9S
`
`AVM3LV9
`
`LN3A3
`
`LNSWNASVNVIN
`
`JONIS3ud©
`
`|
`
`WALSAS
`
`206
`
`706
`
`006
`
`§‘S17
`
`£06
`
`
`
`ALYVdGSHOLVM
`
`uY¥3aLsio3ay
`
`SUBSTITUTE SHEET (RULE 26)
`
`Epic Games Ex. 1029
`Page 103
`
`
`
`
`
`

`

`iotiim History -- Sittply Relevant
`
`Page 1 of 4
`
`
`
`Ottawa Asterisk User Group kickoff »
`
`iotum History
`
`You may,or maynot, know thehistory of iotum. Weincorporated in December 2003, and hired our
`first developer, Todd Jefferson in August 2004. From August 2004 until March 2005, we experimented
`with a numberofdifferent product concepts. Webuilt, tested, and threw away prototypesuntil we
`arrived at the current concept for iotum. It was codenamed Boomerang Server Edition, or BSE.
`
`Last Friday, the team updated our desktop plugins and server code, based on several months of feedback
`from ourfirst beta. This morning wereleased our Asterisk integration kit to the web,andalsoourfirst
`broad beta. And, partway through the morning,I got this email from Todd.
`
`With this commit into Subversion:
`
`1516 | andrewh | 2005-03-14 15:36:26 -0500 (Mon, 14 Mar2005)| 2 lines
`
`Continuousintegration for #305:
`
`Beginning to port the classes from the old rule code.
`
`Boomerang Server Edition was born.
`
`621 tests,
`
`1396 webapptests,
`
`6 platform/switchintegrations,
`
`~110000lines of code
`
`3 awards
`
`3 patent applications
`
`and 385 dayslater, we release.
`
`Cool! Congratulations to the team. It’s a great accomplishment.
`
`htto:/Aiotum.com/simplyrelevant/2006/04/03/iotum-history/
`
`5/15/2006
`
`Epic Games Ex. 1029
`Page 104
`
`

`

`. iotiim History -- Simply Relevant
`
`Page 2 of 4
`
`
`This entry was posted on Monday,April 3rd, 2006 at 11:07 pm andis filed under Business, News. You can follow any
`
`
`responsesto this entry through the RSS 2.0 feed. You can leave a response,or trackback from your ownsite.
`
`9 Responses to “iotum History”
`
`1. J./ Million Lines -- Alec Saunders .LOG Says:
`April 3rd, 2006 at 11:14 pm
`
`[...] A little iotum history was made today. Read aboutit on SimplyRelevant.[...]
`
`2. Martin Dufort Says:
`April 4th, 2006 at 8:14am
`Ah!!! The mythical LOC number. Funny howtime passesand wearestill sticking to that
`figure!!!. However,I think the best part of this post is the numberoftests, close to 2000. I think
`the best figure to publish is the ratio between TLOC (T=Testing) and ALOC (A=Application).
`
`Striving for a high numberwithin this area is key andthis is the difference we are now seeing
`between projects doneat the end of the 80’s / early 90’s and today’s project.
`
`Congratulations and give us a sense of the T/A LOCratio.
`
`Bye - Martin
`
`
`3. Frank Miller Says:
`
`April 4th, 2006 at 8:16 am
`
`I’m confused. Is the 1.1 Million supposed to be 110,000 lines of code?
`
`4. Randy Charles Morin Says:
`April 4th, 2006 at 10:08 am
`
`Congrats!
`
`5. Rick Duff Says:
`April 4th, 2006 at 10:30 am
`
`Was the lines of code 1.1M or 110k? (yourtitle says one thing, the text another)
`
`Regardless, congrats are in order.
`
`Rick..
`
`6. Alec Says:
`
`Yes - I must be getting old! Dropped a zero. Will correctit.
`
`>
`
`7. Jim Says:
`
`http://iotum.com/simplyrelevant/2006/04/03/iotum-history/
`
`5/15/2006
`
`Epic GamesEx. 1029
`Page 105
`
`

`

`« iotitm History -- Simply Relevant
`
`Page 3 of 4
`
`April 8th, 2006 at 5:26 pm
`
`Congratulations, Alec!
`
`8. Jim Says:
`April 8th, 2006 at 5:42 pm
`
`And congratu

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket