throbber
[1.0] A method
`comprising:
`
`[32.0] A non-
`transitory
`computer
`readable storage
`medium having
`instructions
`stored thereon,
`the instructions
`comprising:
`
`Independent Claims 1, 7, 14, 20, 26, and 32
`[7.0] A routing
`[14.0] A method
`[20.0] An
`[26.0] An article
`network
`comprising:
`apparatus
`of manufacture
`comprising:
`comprising:
`including a
`computer-
`readable storage
`medium having
`instructions
`stored thereon,
`execution of
`which by a
`computing
`device causes
`the computing
`device to
`perform
`operations
`comprising:
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 1 of 14
`
`

`

`
`
`
`
`[32.1]
`instructions for
`providing a data
`representation to
`a client device
`coupled to a
`routing network,
`wherein the data
`representation
`includes at least
`one live object
`recognizable by
`the client device,
`and
`
`[14.1] providing,
`using a
`processing
`device of an
`input source, a
`data
`representation to
`a client device,
`different from
`the input source,
`coupled to a
`routing network,
`wherein the data
`representation
`includes at least
`one live object
`recognizable by
`the client device,
`and
`
`[20.1] an input
`source device
`configured to
`provide a data
`representation to
`a client device,
`different from
`the input source,
`coupled to a
`routing network,
`wherein the data
`representation
`includes at least
`one live object
`that is
`recognizable by
`the client device,
`and
`
`[26.1] providing,
`using a
`processing
`device of an
`input source, a
`data
`representation to
`a client device,
`different from
`the input source,
`coupled to a
`routing network,
`wherein the data
`representation
`includes at least
`one live object
`that is
`recognizable by
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 2 of 14
`
`

`

`
`
`
`
`[14.2] causing
`the client device
`to respond to the
`live object of the
`data
`representation
`by determining
`an object
`identifier (ID) of
`the live object
`and to register
`for updates of
`the live object
`with the routing
`network, such
`that registering
`the client device
`
`[20.2] that
`causes the client
`device to
`determine an
`object identifier
`(ID) of the live
`object to register
`for updates of
`the live object
`with the routing
`network, such
`that registering
`the client device
`with the routing
`network
`provides client
`connection
`
`the client device,
`and
`[26.2] that
`causes the client
`device to
`respond to the
`live object by
`determining an
`object identifier
`(ID) of the live
`object to register
`for updates of
`the live object
`with the routing
`network, such
`that registering
`the client device
`with the routing
`network
`
`[32.2] wherein
`the client device
`is configured to
`respond to the
`live object of the
`data
`representation
`by determining
`an object
`identifier (ID) of
`the live object to
`register for
`updates of the
`live object with
`the routing
`network, such
`that registering
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 3 of 14
`
`

`

`with the routing
`network
`provides client
`connection
`information to a
`node in the
`routing network;
`and
`[14.3] sending,
`using the
`processing
`device of the
`input source, an
`update message
`to the routing
`network,
`wherein the
`update message
`identifies the
`
`information to
`the routing
`network,
`
`provides client
`connection
`information to
`the routing
`network; and
`
`[20.3] wherein
`the input source
`device is
`configured to
`route an update
`message to the
`routing network,
`wherein the
`update message
`identifies the
`live object and
`
`[26.3] sending,
`using the
`processing
`device of the
`input source, an
`update message
`to the routing
`network,
`wherein the
`update message
`identifies the
`
`the client device
`with the routing
`network
`provides client
`connection
`information to
`the routing
`network; and
`[32.3]
`instructions for
`providing, using
`a processing
`device of an
`input source,
`different from
`the client device,
`an update
`message to the
`routing network,
`
`[1.1] receiving,
`using a
`processing
`device, an update
`message from an
`input source, the
`update message
`identifying a live
`object and
`containing data
`for updating a
`
`[7.1] a gateway
`device
`configured to:
`receive an
`update message
`from an input
`source, the
`update message
`identifying a live
`object and
`containing data
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 4 of 14
`
`

`

`property of the
`live object;
`
`for updating a
`property of the
`live object,
`
`live object and
`contains update
`data that updates
`a property of the
`live object,
`
`contains update
`data for updating
`a property of the
`live object,
`
`live object and
`contains update
`data for updating
`a property of the
`live object,
`
`[1.2] identifying
`a category of the
`update message
`based on the
`input source;
`determining a
`node having a
`node type to
`which the update
`message is to be
`routed based on a
`
`[7.2] identify a
`category of the
`update message
`based on the
`input source;
`determine a node
`having a node
`type to which
`the update
`message is to be
`routed based on
`
`[14.4] wherein a
`gateway device
`at the routing
`network is
`configured to
`identify a
`category of the
`update message
`based on the
`input source, to
`determine a node
`
`[20.4] wherein a
`gateway device
`at the network is
`configured to
`identify a
`category of the
`update message
`based on the
`input source, to
`determine a node
`type to which
`
`[26.4] wherein a
`gateway device
`at the routing
`network is
`configured to
`identify a
`category of the
`update message
`based on the
`input source, to
`determine a node
`
`wherein the
`update message
`identifies the
`live object and
`contains update
`data for updating
`a property of the
`live object,
`[32.4] wherein a
`gateway device
`at the routing
`network is
`configured to
`identify a
`category of the
`update message
`based on the
`input source, to
`determine a
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 5 of 14
`
`

`

`mapping of
`categories of
`update messages
`to node types, the
`mapping
`controlling an
`amount of update
`message traffic
`through nodes of
`a routing
`network;
`
`[1.3] routing,
`using the
`processing
`device, the
`update message
`to the node
`having the
`
`a mapping of a
`categories of
`update messages
`to node types,
`the mapping
`controlling an
`amount of
`update message
`traffic through
`nodes of a
`routing network;
`and
`[7.3] route the
`update message;
`and
`the node
`configured to:
`receive the
`update message
`
`type to which
`the identified
`category maps,
`
`the identified
`category maps,
`and
`
`type to which
`the identified
`category maps,
`and
`
`node type to
`which the
`identified
`category maps,
`and
`
`[14.5] and to
`route the update
`message to the
`node, having the
`node type, at the
`routing network,
`
`[20.5] to route
`the update
`message to a
`node of the node
`type at the
`routing network,
`
`[26.5] to route
`the update
`message to a
`node of the node
`type at the
`routing network,
`
`[32.5] to route
`the update
`message to a
`node of the node
`type at the
`routing network,
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 6 of 14
`
`

`

`from the
`gateway device,
`wherein the node
`is configured to
`be mapped to the
`node type,
`[7.4] determine a
`client, different
`from the input
`source, that has
`registered for
`updates of the
`live object, and
`route the update
`message from
`the node to the
`client,
`
`determined node
`type;
`
`[1.4] causing the
`node, through the
`update message,
`to determine a
`client, different
`from the input
`source, that has
`registered for
`updates of the
`live object;
`causing the node
`to route the
`update message
`
`[14.6] wherein
`the node is
`configured to
`identify the
`client device as a
`registered device
`and to route the
`update message
`to the client
`device, and
`
`[20.6] wherein
`the node is
`configured to
`identify the
`client device as a
`registered device
`and route the
`update message
`containing the
`update data to
`the client device,
`and
`
`[26.6] wherein
`the node is
`configured to
`identify the
`client device as a
`registered device
`and to route the
`update message
`to the client
`device, and
`
`[32.6] wherein
`the node is
`configured to
`identify the
`client device as a
`registered device
`and to route the
`update message
`containing the
`update data to
`the client device,
`and
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 7 of 14
`
`

`

`from the node to
`the client; and
`[1.5] causing the
`client to process
`the update
`message and to
`update the
`property of the
`live object.
`
`[7.5] wherein the
`client is adapted
`to process the
`update message
`and to update the
`property of the
`live object.
`
`[14.7] wherein
`the client device
`processes the
`update message
`upon receipt to
`update the
`property of the
`live object at the
`client device.
`
`[20.7] wherein
`the client device
`is configured to
`process the
`update message
`upon receipt to
`update the
`property of the
`live object at the
`client device.
`
`[26.7] wherein
`the client device
`is configured to
`process the
`update message
`upon receipt to
`update the
`property of the
`live object at the
`client device.
`
`[32.7] wherein
`the client device
`is configured to
`process the
`update message
`upon receipt to
`update the
`property of the
`live object at the
`client device.
`
`
`
`
`Dependent Claims 2-6 and 8-13
`[2.0] The method of claim 1, further comprising:
`[8.0] The routing network of claim 7, wherein the node
`causing the node to extract an object identifier (ID)
`is configured to extract an object identifier (ID) from
`from the update message, to establish a connection
`the update message and to determine a connection to
`with the client, and to determine if the client has
`the client to route the data to the client.
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 8 of 14
`
`

`

`registered for updates of the live object based on the
`object ID.
`[3.0] The method of claim 2, further comprising:
`causing the node to determine at least one client proxy
`with which the client communicates;
`causing the node to route the update message to the
`client proxy; and
`causing the client proxy to route the update message to
`the client to determine the connection.
`[4.0] The method of claim 3, further comprising
`causing the node to maintain client registration
`information concerning the client connection.
`[5.0] The method of claim 3, further comprising
`causing the node to maintain client registration
`information concerning the client connection at the
`client proxy.
`[6.0] The method of claim 1, wherein the property of
`the live object has a direct effect on a visual
`representation of the live object in a data
`
`[9.0] The routing network of claim 8, wherein the node
`is configured to determine the connection by
`determining at least one client proxy with which the
`client communicates and to route the update message to
`the client proxy.
`
`[10.0] The routing network of claim 9, wherein client
`registration information concerning the client
`connection is configured to be maintained at the node.
`[11.0] The routing network of claim 9, wherein client
`registration information concerning the client
`connection is configured to be maintained at the client
`proxy.
`
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 9 of 14
`
`

`

`representation, has an effect on an internal aspect of the
`live object and has no effect on the visual
`representation of the live object in the data
`representation, or has a direct effect on one aspect of
`the visual representation of the live object in the data
`representation and has no effect on other aspect of the
`visual representation of the live object in the data
`representation.
`
`
`
`
`
`
`[12.0] The routing network of claim 7, wherein:
`the gateway device is configured to route the update
`message to the node adapted to receive messages of
`more than one message category, and
`the node is configured to determine a connection with
`at least one client proxy with which the client
`communicates and to route the data to the client proxy.
`[13.0] The routing network of claim 7, wherein the
`node type is configured to identify the node that
`receives the update message from the gateway device.
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 10 of 14
`
`

`

`
`
`
`[15.0] The method of
`claim 14, wherein
`providing the data
`representation to the
`client device includes
`providing the live object
`that causes the client
`device to register with a
`client proxy of the
`routing network.
`[16.0] The method of
`claim 14, wherein
`providing the data
`representation to the
`client device includes
`providing the live object
`
`Dependent Claims 15-19, 21-25, 27-31, and 33-37
`[21.0] The apparatus of
`[27.0] The article of
`claim 20, wherein the live
`manufacture of claim 26,
`object of the data
`wherein the live object of
`representation is
`the data representation
`configured to cause the
`causes the client device to
`client device to register
`register with a client
`with a client proxy of the
`proxy of the routing
`routing network.
`network.
`
`[33.0] The non-transitory
`computer readable storage
`medium of claim 32,
`wherein the live object of
`the data representation
`causes the client device to
`register with a client proxy
`of the routing network.
`
`[22.0] The apparatus of
`claim 20, wherein the live
`object of the data
`representation is
`configured to cause the
`client device to register
`
`[28.0] The article of
`manufacture of claim 26,
`wherein the live object of
`the data representation
`causes the client device to
`
`[34.0] The non-transitory
`computer readable storage
`medium of claim 32,
`wherein the live object of
`the data representation
`causes the client device to
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 11 of 14
`
`

`

`that causes the client
`device to register with
`the node of the routing
`network.
`[17.0] The method of
`claim 14, wherein
`providing the data
`representation to the
`client device includes
`providing an activation
`module that is executed
`by the client device and
`that registers the live
`object with the routing
`network.
`[18.0] The method of
`claim 17, wherein
`providing the activation
`module includes
`
`with the node of the
`routing network.
`
`register with the node of
`the routing network.
`
`register with the node of the
`routing network.
`
`[23.0] The apparatus of
`claim 20, wherein the
`received data
`representation includes an
`activation module that is
`configured to be executed
`by the client device and
`adapted to register the live
`object with the routing
`network.
`
`[29.0] The article of
`manufacture of claim 26,
`wherein the received data
`representation includes an
`activation module
`executed by the client
`device and adapted to
`register the live object
`with the routing network.
`
`[35.0] The non-transitory
`computer readable storage
`medium of claim 32,
`wherein the data
`representation includes an
`activation module that is
`executed by the client
`device and that is adapted to
`register the live object with
`the routing network.
`
`[24.0] The apparatus of
`claim 23, wherein the
`activation module is
`configured to determine a
`
`[30.0] The article of
`manufacture of claim 29,
`wherein the activation
`module determines a
`
`[36.0] The non-transitory
`computer readable storage
`medium of claim 35,
`wherein the activation
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 12 of 14
`
`

`

`providing the activation
`module that is
`configured to determine
`a node type that handles
`registration and that
`causes the client device
`to register with the node
`corresponding to the
`node type.
`[19.0] The method of
`claim 17, wherein
`providing the activation
`module includes
`providing the activation
`module that is
`configured to determine
`a message category of
`the data representation
`and that causes the client
`
`node type for handling
`registration and to cause
`the client device to register
`with the node of the node
`type.
`
`node type that handles
`registration and causes
`the client device to
`register with the node of
`the node type.
`
`module determines a node
`type for handling
`registration and causes the
`client device to register with
`the node of the node type.
`
`[25.0] The apparatus of
`claim 23, wherein the
`activation module
`determines a message
`category of the data
`representation and causes
`the client device to register
`with the node having a
`node type corresponding to
`the message category.
`
`[31.0] The article of
`manufacture of claim 29,
`wherein the activation
`module determines a
`message category of the
`data representation and
`causes the client device to
`register with the node
`having a node type
`
`[37.0] The non-transitory
`computer readable storage
`medium of claim 35,
`wherein the activation
`module determines a
`message category of the
`data representation and
`causes the client device to
`register with the node
`having the node type
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 13 of 14
`
`

`

`device to register with a
`node having a node type
`corresponding to the
`message category.
`
`
`
`corresponding to the
`message category.
`
`corresponding to the
`message category.
`
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1021
`Page 14 of 14
`
`

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