DEVICE CONTROLLER AND VIEWER
`
`Inventors:
`
`Kenneth North
`
`Ragini Prasad
`Michael Power
`
`Haroun Ansari
`
`Neeraj Pendse
`
`RELATED APPLICATION
`
`This application claims the benefit of priority to US Provisional Application No.
`
`62/276,640, titled “DEVICE CONTROLLER AND VIEWER,” filed on January 8, 2016, which is
`
`herein incorporated by reference in its entirety.
`
`BACKGROUND
`
`Technical Field
`
`[0001]
`
`The subject matter disclosed herein relates generally to distributing content and more
`
`particularly to distributing content and settings to client devices without physically interacting
`
`with the client device.
`
`Background
`
`[0002]
`
`Existing approaches for remotely distributing and installing content or settings on
`
`client devices typically require a user to be present at the client device because installation
`
`requires the user to initiate or configure the installation. As an example, an operating system on
`
`the client device typically displays a message, such as a pop-up message, requesting permission
`
`from the user to initiate or continue with the installation. In other words, installation cannot
`
`continue unless the user is physically present at
`
`the client device, which is particularly
`
`cumbersome, especially when the client devices are distributed across different locations.
`
`ET-Ol306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`_ 2 _
`
`SUMMARY
`
`[0003]
`
`Provided herein are system, apparatus, device, method and/or computer program
`
`product embodiments, and/or combinations and sub-combinations thereof, for distributing and
`
`installing content and settings on client devices without receiving any user input at the client
`
`devices.
`
`[0004]
`
`An example method embodiment may include steps for remotely configuring and
`
`controlling a client device without user input at the client device where the client device limits usage
`
`of the client device by a user at the client device to a first set of usage activities, wherein the first set
`
`includes an interaction activity at the client device. Other steps of the method may include receiving,
`
`at the client device, an instruction and distributed content from a device controller and initiating
`
`installation of the distributed content on the client device without receiving any input from the user
`
`of the client device to initiate installation of the distributed content and without receiving any input
`
`from the user of the client device during the installation of the distributed content. The client device
`
`may further allow management of the client device by the device controller according to a second set
`
`of the usage activities.
`
`[0005]
`
`An example apparatus embodiment may include a touch—sensitive display and a
`
`processor communicatively coupled to the touch—sensitive display. The processor may be configured
`
`to provide usage activities and limit usage of the client device by a user at the client device to a first
`
`set of the usage activities, wherein the first set includes an interaction activity. The processor may be
`
`further configured to receive an instruction and distributed content for display on the touch—sensitive
`
`display from a device controller and initiate installation of the distributed content on the client
`
`device without receiving any input from the user at the client device to initiate installation of the
`
`distributed content and during the installation of the distributed content. The client device may be
`
`further configured to allow management of the client device by the device controller according to a
`
`second set of the usage activities.
`
`[0006]
`
`Another example method embodiment may include the steps for remotely configuring
`
`and controlling a client device without user input at the client device by receiving, at a device
`
`controller, a selection for remotely configuring the client device and, based on the selection,
`
`determining distributed content for transmitting to the client device. The method may further include
`
`ET—Ol306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`-3-
`
`the step of transmitting, by the device controller, an instruction and the selected distributed content
`
`to the client device, wherein the instruction is configured to cause the client device to install the
`
`selected distributed content without receiving any input from the user of the client device to initiate
`
`installation of the selected distributed content and without receiving any input from the user of the
`
`client device during the installation of the distributed content.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0007]
`
`The accompanying drawings are included to provide a further understanding of the
`
`claims, and are incorporated in and constitute a part of this specification.
`
`The detailed
`
`description and illustrated embodiments described serve to explain the principles defined by the
`
`claims.
`
`[0008]
`
`FIG.
`
`1
`
`is a block diagram of a system environment where embodiments can be
`
`implemented.
`
`[0009]
`
`FIG. 2 is a block diagram of a device controller provisioning client devices, according
`
`to an embodiment.
`
`[0010]
`
`FIG. 3 is a flowchart of a method for distributing content and settings to client
`
`devices without person interaction during installation, according to an embodiment.
`
`[0011]
`
`FIG. 4 is a block diagram of a device controller providing different content to client
`
`devices, according to an embodiment.
`
`[0012]
`
`FIG. 5 is a block diagram of a client device providing content without a network
`
`connection, according to an embodiment.
`
`[0013]
`
`FIG. 6A is a diagram of parameters that may be set on a client device without a
`
`person installing or facilitating installation of the parameters on the client device.
`
`[0014]
`
`[0015]
`
`FIG. 6B is flowchart of a method for distributing content or settings to a client device,
`
`according to an embodiment.
`
`[0016]
`
`FIG. 7 is a diagram of performing drag and drop content installation, according to an
`
`embodiment.
`
`[0017]
`
`FIG. 8A is a diagram of groups of client devices, according to an embodiment.
`
`ET—Ol306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`-4-
`
`[0018]
`
`FIG. 8B is a diagram of a dynamic group of client devices, according to an
`
`embodiment.
`
`[0019]
`
`FIG. 8C is a flowchart that provides content to a dynamically selected group of client
`
`devices, according to an embodiment.
`
`[0020]
`
`FIG. 9 is a diagram of a device controller displaying data analytics associated with
`
`client devices, according to an embodiment.
`
`[0021]
`
`FIG. 10 is a block diagram of a computer system where the embodiments can be
`
`implemented.
`
`[0022]
`
`In the drawings,
`
`like reference numbers generally indicate identical or similar
`
`elements. Additionally, generally, the left-most digit(s) of a reference number identifies the
`
`drawing in which the reference number first appears.
`
`DETAILED DESCRIPTION
`
`[0023]
`
`The embodiments described below overcome the problems discussed above by
`
`utilizing connections with asymmetric elements to couple the pads of the horizontally and
`
`vertically arranged electrodes.
`
`[0024]
`FIG.
`1 is a block diagram 100 of a system environment where embodiments can be
`implemented. Block diagram 100 includes a network 102, client devices 104, a server 106, a
`
`device controller 108, and a computing device 110.
`
`[0025]
`
`In an embodiment, network 102 may include any network or combination of
`
`networks that carry data. Network 102 includes but is not limited to, a local area network,
`
`metropolitan area network, and/or wide area network, such as the Internet. Network 102 can
`
`support technologies, such as the World Wide Web (“the Web”) that provide access to services
`
`and applications using protocols, such as a HyperText Transfer Protocol (“HTTP”). Intermediate
`
`web servers, gateways, or other servers are provided between components of the system 100,
`
`depending upon a particular application or environment.
`
`[0026]
`
`In an embodiment, servers 106 provide data, such as, content, control data, etc., to
`
`client devices 104. For example, servers 106 may download applications, data, and upgrades
`
`onto client devices 104 based on instructions provided by client devices 104 or other devices,
`
`ET—01306
`
`Atty. Dkt. N0. 3450.0570001
`
`
`
`

`

`-5-
`
`such as a computing device 110 that includes device controller 108, which is discussed below.
`
`Servers 106 may be part of a network cloud that includes multiple servers that host applications
`
`and data, perform calculations, and distribute same to client devices 104. In an embodiment,
`
`servers 106 may include servers that provide client devices 104 with access to applications,
`
`content generated by third-parties, servers that enable communication between client devices
`
`104, servers that include vast amounts of computing resources, such as processors and memory
`
`operable to perform mathematically intensive calculations, servers that collect and store data,
`
`servers that store files and/or folders, servers that provide client devices 104 with media content
`
`(such as digital video and/or digital audio) as programmed, on—demand, or through media
`
`streaming, servers that provide client devices 104 with access to web pages and web content, etc.
`
`[0027]
`
`In an embodiment, client devices 104 are electronic devices controlled and/or
`
`manipulated by users. Client devices 104 request and/0r receive resources, content, applications,
`
`videos, media streams, etc., from servers 106 over network 102. Client devices 104 may include,
`
`but are not limited to, personal computers, laptop computers, smartphones, tablets, kiosks, point
`
`of sale stations, etc. Additionally, client devices 104 may be computing devices that are
`
`distributed to customers and installed in customer owned locations, such as retail establishments.
`
`Once installed, client devices 104 provide access to information associated with products and
`
`services provided in the retail establishments. Additionally, client devices 104 may be used by
`
`users who enter the retail establishments and purchase the goods or services. In an embodiment,
`
`a retail establishment may place client device 104 at particular
`
`locations in the retail
`
`establishment, such as, in one or more aisles so that client devices 104 are accessible to multiple
`
`users.
`
`In another embodiment, users may carry client devices 104 throughout
`
`the retail
`
`establishment.
`
`[0028]
`
`Client devices 104 may have some or all components of a computing device as
`
`described in FIG. 10.
`
`[0029]
`
`Client devices 104 may be controlled by a device controller 108. In an embodiment,
`
`device controller 108 may be installed on a computing device 110, such as a laptop, a desktop, a
`
`tablet, a smartphone, etc. In another embodiment, device controller 108 may be installed on
`
`server 106 and include a front—end component 108A and a back-end component 108B. For
`
`ET—Ol306
`
`Atty. Dkt. N0. 3450.0570001
`
`

`

`-6-
`
`example, front-end component 108A may be installed on computing device 110, or be accessible
`
`using a browser of computing device 110, while back—end component 108B may operate on
`
`server 106.
`
`[0030]
`
`In an embodiment, device controller 108 or front—end component 108A includes a
`
`user interface 112. User interface 112 displays data provided by device controller 108 and also
`
`receives input from a user, which may be a customer that purchases, rents, or owns client device
`
`104. Based on the input, device controller 108 issues instructions that control client devices 104
`
`or download content or applications to client devices 104. In an embodiment, once user interface
`
`112 receives user input, front-end component 108A transmits the input to back—end component
`
`108B, which then distributes instructions received from the input or associated with the input to
`
`client devices 104.
`
`[0031]
`
`In an embodiment, device controller 108 eliminates user interaction with client
`
`devices 104 during set-up, application installation, or content downloads. Instead, a customer
`
`using device controller 108 may select content that is downloaded and displayed on client device
`
`104 to the users of client device 104 in a retail establishment. Users of client device 104 at retail
`
`establishments, on the other hand, have limited interaction of client device 104. Example
`
`interaction may be limited to browsing content provided to client device 104 by device controller
`
`108. In another embodiment, device controller 108 may also control various settings, such as
`
`brightness/contrast settings, screen resolution, speaker activation, volume control, application
`
`activation, network configuration, etc., on client devices 104 without requiring physical input
`
`from users who use client devices 104 at a retail establishment to change or agree to a change in
`
`the settings.
`
`[0032]
`
`In an embodiment, device controller 108 allows a user to remotely manage one or
`
`more client devices 104. For example, device controller 108 determines what content client
`
`devices 104 are currently playing, determines the content client devices 104 will be playing in
`
`the future, adjusts volume on client devices 104, reboots client devices 104, determines
`
`screensavers for client device 104, etc.
`
`[0033]
`
`In an embodiment, device controller 108 may include a content library. The content
`
`library may include content that may be played and/or installed on client devices 104. Example
`
`ET-01306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`-7-
`
`content may include, but is not limited to, applications, mobile applications, websites, website
`
`links, presentations (such as PowerPoint presentations), movies, advertisements, streaming
`
`content, etc. In an embodiment, content in the content library may be stored and accessed using
`
`back—end component 108B and displayed using front-end component 108A. A user (such as a
`
`customer) using device controller 108 may use front-end component 108A to select content from
`
`the library, select one or more client devices 104, and distribute the selected content to the client
`
`devices 104.
`
`[0034]
`
`In an embodiment, prior to device controller 108 installing content on client devices
`
`104, device controller 108 sets up or provisions client devices 104 in device controller 108. The
`
`provisioning allows the customer to set settings and install content on client devices 104 without
`
`a device administrator or another user interacting with client devices 104. FIG. 2 is a block
`
`diagram 200 of a device controller provisioning client devices, according to an embodiment.
`
`Block diagram 200 describes device controller 108 in terms of front-end component 108A and
`
`back—end component 108B, but the implementation is not limited to this embodiment.
`
`[0035]
`
`In an embodiment, client device 104 is associated with a serial number 202. Serial
`
`number 202 is unique to each client device 104 and may be assigned to client device 104 at the
`
`time that client device 104 is manufactured in a manufacturing facility. When a customer
`
`purchases client devices 104, the customer may identify the purchased client devices 104 by the
`
`serial numbers 202. In another embodiment, serial number 202 is assigned to hardware that is
`
`installed on client device 204. In this case, customer purchases the hardware and installs the
`
`hardware on client devices 204 and serial number 202 of the hardware is associated with the
`
`client device.
`
`[0036]
`
`In an embodiment, once client device 104 is activated and powered on, client device
`
`104 connects to network 102 and is able to communicate with other devices in network 102, such
`
`as server 106 and computing device 110. When client device 104 or hardware installed on client
`
`devices causes client device 104 to connect to network 102, client device 104 may be pre—
`
`programmed to access device controller 108 and provide serial number 202 to device controller
`
`108 or back-end component 108B of device controller 108. Device controller 108 receives serial
`
`number 202 and stores serial number 202 in a repository associated with device controller 108.
`
`ET—01306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`—8—
`
`Example repository may be a database 204 or another memory device conducive to storing large
`
`amounts of data that is described in FIG. 10.
`
`[0037]
`
`In an embodiment, client device 104 is associated with a customer. A customer is an
`
`entity that purchases or rents one or more client devices 104 that are installed in various retail
`
`establishments, such as stores, hotels, or at other locations. In order for client device 104 to be
`
`associated with a customer, the customer creates an account using device controller 108. For
`
`example, a customer may use front-end component 108A to create an account, such as account
`
`206. Account 206 may be specific to a customer and may require customer credentials, such as a
`
`customer or system chosen user name or email address, and a corresponding password. Once a
`
`customer creates account 206, device controller 108 may store account 206 and customer
`
`credentials in database 204.
`
`[0038]
`
`In an embodiment, a customer may use account 206 to enter serial numbers 202 of
`
`client devices 104 that are associated with the customer. For example, a customer may use front-
`
`end component 108A and user interface 112 to enter serial numbers 202. Once entered, device
`
`controller 108 associates client devices 104 having serial numbers 202 with account 206. In
`
`another embodiment, device controller 108 may associate serial numbers 202 of client devices
`
`104 based on the criteria, such as an email or user name, that the customer used to purchase
`
`client device 104 with account 206. In an embodiment, when client device 104 connects to
`
`network 102 and accesses device controller 108, device controller 108 uses serial number 202 to
`
`identify account 206 associated with client device 104.
`
`[0039]
`
`In an embodiment, a customer may also use account 206 to select and load content
`
`208 to client devices 104. For example, a customer may use front-end component 108A to
`
`upload content 208 to device controller 108 or select content 208 from one of the content
`
`libraries provided by device controller 108 and displayed using front—end component 108A to a
`
`customer.
`
`[0040]
`
`In an embodiment, there may be several sources of content 208. Content 208 may be
`
`uploaded to device controller 108 via user interface 112 and front—end component 108A and
`
`stored in the content library. Content 208 may also be provided by a third—party server that client
`
`device 104 may access using network 102. In this case, a customer may select a link that
`
`ET—01306
`
`Atty. Dkt. N0. 3450.0570001
`
`

`

`-9-
`
`accesses the content and provides a link to a browser executing on client device 104 or causes
`
`client device 104 to download content 208 from the third—party.
`
`[0041]
`
`In a further embodiment, a customer may use account 206 to load client device
`
`settings or simply settings 210 to client device 104. A customer may select settings 210 from the
`
`settings displayed on user interface 112. Settings 210 may include volume settings, brightness
`
`settings, contrast settings, color settings, etc.
`
`[0042]
`
`Once selected, front-end component 108A may transmit content 208 or settings 210
`
`to back-end component 108B. Back-end component 108B may receive content 208 and settings
`
`210 from front-end component 108A and store content 208 and settings 210 in database 204 or in
`
`a temporary memory of server 106. Then, when client devices 104 associated with account 206
`
`become accessible via network 102 or when device controller 108 determines that client devices
`
`104 are connected to network 102, device controller 108 may distribute content 208 and settings
`
`210 to client devices 104.
`
`[0043]
`
`When client devices 104 receive content 208 and/or settings 210 from device
`
`controller 108, client devices 104 install content 208 and/or settings 210. Client devices 104 may
`
`include an operating system 212. Operating system 212 is a component that installs content 208
`
`and/or settings 210 on client devices 104. In an embodiment, operating system 212 may be
`
`proprietary and may be modified to execute specifically on client devices 104. As part of the
`
`installation, operating system 212 installs content 208 on client devices 104 without invoking
`
`system calls or generating pop-ups that require a person’s input during installation. In this way,
`
`operating system 212 seamlessly installs content 208 on client devices 104 without input or
`
`permission from persons interacting with client devices 104 in for example, retail establishments.
`
`In a further embodiment, operating system 212 also changes settings on client devices 104 as
`
`specified by settings 210. For example, operating system 212 changes the current or default
`
`volume, brightness, contrast, color, etc., settings on client devices 104 to settings 210. Similar to
`
`content installation, operating system 212 does not invoke system calls or asks permissions to
`
`change the settings, and thus, does not require input from a person using client device 104 to
`
`change the settings on client devices 104.
`
`ET-01306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`-10-
`
`[0044]
`
`FIG. 3 is a flowchart of method 300 for distributing content and settings to client
`
`devices without person interaction during installation, according to an embodiment. Prior to
`
`method 300, client devices 104 or the hardware that
`
`is installed on client devices 104 is
`
`manufactured, assigned serial numbers 202, distributed to customers, and connected to network
`
`102. Method 300 can be performed by processing logic that can comprise hardware (e.g.,
`
`circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions run
`
`on a processing device), or a combination thereof.
`
`[0045]
`
`At step 302, serial numbers are provided. For example, once client devices 104
`
`connect to network 102, client devices 104 provide serial numbers 202 to device controller 108.
`
`As discussed above, serial numbers 202 may be assigned during manufacturing and are unique to
`
`each client device 104. Once provided, device controller 108 stores serial numbers 202 in
`
`database 204.
`
`[0046]
`
`At step 304, an account is set up. For example, device controller 108 receives input
`
`from a customer that purchased client devices 104. The input includes instructions that set-up
`
`account 206 for the customer and customer credentials that are associated with account 206.
`
`[0047]
`
`At» step 306, serial numbers are associated with an account. For example, device
`
`controller 108 receives input from a customer that includes serial numbers 202 of client devices
`
`104 that are owned or rented by the customer. These serial numbers 202 are associated with the
`
`customer's account 206.
`
`[0048]
`
`At step 308, content is selected. For example, device controller 108 receives input
`
`from a customer that includes selection for content 208 to be displayed on client devices 104.
`
`[0049]
`
`At step 310, settings are selected. For example, device controller 108 receives input
`
`from a customer that includes selection of settings 210 for client devices 104.
`
`[0050]
`
`At step 312, serial numbers are matched and client devices are selected. For example,
`
`serial numbers 202 that are provided in step 306 are matched against serial numbers 202 that are
`
`provided in step 302. If the match is successful, client devices 104 are selected for receiving
`
`content 208 and/or settings 210.
`
`ET—01306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`-11-
`
`[0051]
`
`At step 314, content and settings are distributed to client devices. For example, device
`
`controller 108 distributes content 208 and settings 210 to client devices 104 associated with
`
`serial numbers 202 matched in step 312.
`
`[0052]
`
`At step 316, content and settings are installed. For example, client devices 104
`
`receive content 208 and settings 210. Once received, client devices 104 install content 208
`
`without interaction or verification with a person for proceeding with installation. Additionally,
`
`client devices 104 also install settings 210 without interaction or verification with a person for
`
`proceeding with installation.
`
`[0053]
`
`In an embodiment, device controller 108 may also be used to provide different
`
`content 208 or change content that exists and is displayed on client devices 104.
`
`In an
`
`embodiment, device controller 108 may change content 208 or a version of content 208 on client
`
`devices 104 or a subset of client devices 104 that are associated with a particular account 206.
`
`FIG. 4 is a block diagram 400 of a device controller providing different content to client devices,
`
`according to an embodiment. In block diagram 400, a customer accesses device controller 108.
`
`Device controller 108 then receives a selection for distributing content 208A to client devices
`
`104A. In an embodiment, content 208A may be a new version of an application executing on
`
`client devices 104A of client devices 104. Once selected, device controller 108 may upload
`
`content 208A to only client devices 104A. Once content 208A is installed and successfully
`
`executes on client devices 104A, device controller 108 distributes content 208A to remaining
`
`client devices 104 associated with account 206, such as client devices 104B, if so desired.
`
`[0054]
`
`In another embodiment, a customer accesses device controller 108. Device controller
`
`108 then receives a selection for distributing content 208A to client devices 104A and content
`
`208B to client devices 104B. Content 208A and content 208B may be different applications that
`
`execute in different departments of a customer’s store or in different stores. Once selected,
`
`device controller 108 may upload content 208A to client devices 104A and content 208B to
`
`client devices 104B.
`
`[0055]
`
`In an embodiment, client device 104 may not be able to connect to network 102. FIG.
`
`5 is a block diagram of client device providing content without a network connection, according
`
`to an embodiment.
`
`In block diagram 500, client device 104 cannot connect to network 102.
`
`ET-01306
`
`Atty. Dkt. No. 3450.0570001
`
`

`

`-12-
`
`When operating system 212 on client device 104 detects that client device 104 cannot connect to
`
`network 102, operating system 212 determines whether a portable memory storage device 502,
`
`such as a USB stick, is inserted into a USB port of client device 104. Once operating system 212
`
`determines that a USB stick exists in a USB port, operating system 212 accesses a folder at a
`
`predetermined path or having a predetermined name and begins to play content 208 stored in the
`
`folder. A person skilled in the art will appreciate that memory storage devices 502 are not limited
`
`to a USB stick and may include other devices, such as a compact disc (CD) to provide content to
`
`client device 104 in the absence of a connection to network 102.
`
`[0056]
`
`In an embodiment, content 208 stored in memory storage device 502 may be website
`
`generating content. To display a website, portable memory device 502 may include URL links
`
`and webpages described in HyperText Markup Language (HTML), EXtensible Markup
`
`Language (XML), cascading style sheets (CSS) and other languages that may be processed by a
`
`browser of client device 104 and display a website.
`
`[0057]
`
`In a further embodiment, memory storage device 502 may provide content to client
`
`device 104 offline so that client device 104 may test the content in a controlled test environment,
`
`prior to the content being deployed to multiple client devices 104.
`
`[0058]
`
`In an embodiment, device controller 108 may manipulate parameters on client device
`
`104 that affect the display of content 208 on client device 104 and access to applications,
`
`settings, browser, etc., that execute on client device 104. FIG. 6A is a block diagram 600A of
`
`parameters that may be set on a client device without a person installing or facilitating the
`
`installation of the parameters on the client device. In an embodiment, front—end component 108A
`
`via user interface 112 may provide a selection of parameters on client device 104 that may be
`
`remotely controlled by a customer using device controller 108. Example parameters may be
`
`browser parameters that control the display of content on a browser executing on client device
`
`104. For example, browser parameters may determine whether to display a browser navigation
`
`bar, display a webpage loading bar, or disable user-initiated downloads from user—accessible
`
`websites on client device 104. Another example parameter may include the mode of content 208
`
`displayed on client device 104, such as whether content 208 may be displayed on full screen or a
`
`portion of the screen. Another example parameter may be a homepage timeout parameter. The
`
`ET—01306
`
`Atty. Dkt. No. 3450.0570001
`
`
`
`

`

`-13-
`
`homepage timeout parameter controls a time interval at the end of which client device 104 may
`
`return to a home screen and display content 208 associated with the home screen.
`
`In an
`
`embodiment, the time specified in the time out parameter begins to run after receiving the last
`
`input from a person using client device 104 at, for example, a retail establishment. In an
`
`embodiment, the timeout parameter may be set to a number of minutes (or another time interval)
`
`from device controller 108. Another example parameter is a cache size parameter. The cache size
`
`parameter indicates the size of a cache that is available to a browser or another application that
`
`displays content 208. Yet another parameter may be a time interval that clears browser related
`
`cookies or user data from client device 104. For example, as a user browses content 208 on client
`
`device 104, a user may store one or more items in a shopping cart associated with a website, and
`
`then stop using client device 104 without clearing contents from the shopping cart. Device
`
`controller 108 may control the time interval during which client device 104 will keep the items in
`
`the shopping cart without deleting the items.
`
`[0059]
`
`Other example parameters may also include web site or client device 104 specific
`
`tags or settings. These tags may be changed or manipulated using device controller 108.
`
`[0060]
`
`Once selected, device controller 108 may transmit content 208 and/or the selected
`
`parameters to client device 104 as discussed above. In response, operating system 212 of client
`
`device 104 installs content 208 for display on client device and also stores the transmitted
`
`parameters. For example, browser parameters that control the behavior of the browser may be
`
`stored within the browser of client device 104, and the home screen parameter and timeout
`
`parameter may be stored within operating system 212 of client device 104. In an embodiment,
`
`operating system 212 installs content 208 and the transmitted parameters without invoking API
`
`or pop—ups that require additional
`
`input activity and without requiring directed response
`
`interaction with client device 104 to enable installation progression.
`
`[0061]
`
`In another example, device controller 108 may also cause client device 104 to display
`
`content 208, such as a slide show, a video of a short advertisement, or another video clip when
`
`client device 104 is not in use or to run as a screensaver on client device 104. In this case,
`
`content 208 may be used to attract a person browsing in, for example a retail establishment, back
`
`to client device 104 or to a product displayed on client device 104. In a further embodiment,
`
`ET—Ol306
`
`Atty. Dkt. No. 3450.0570001
`
`
`
`

`

`-14-
`
`once played on client device 104, content 208 may be interrupted and another application that
`
`has previously been used (such as a website that has previously been browsed by a person using
`
`client device 104) may be displayed.
`
`[0062]
`
`In an embodiment, to determine content 208 that is displayed on client device 104 to
`
`attract a person at a retail establishment, front-end component 108A may provide, via user
`
`interface 112, a selection of content 208 that a customer of device controller 108 may select. As
`
`discussed above, a customer is typically an entity who owns or rents client devices 104. In an
`
`embodiment, user interface 112 may include a selection of content 208 and a timer. The timer
`
`may indicate the time interval after which content 208 may be displayed after a period of
`
`inactivity on client device 104.
`
`[0063]
`
`Once selected, device controller 108 may transmit content 208 and the selected time
`
`interval to client device 104. In response, operating system 212 of client device 104 installs
`
`content 208 as a screensaver on client device 104 and also stores the time parameter that controls
`
`when content 208 may be played. In an embodiment, operating system 212 installs content 208
`
`and the time parameter without invoking APIs or pop—ups that require additional input activity
`
`and without requiring directed response interaction with client device 104 to enable installation
`
`progression.
`
`[0064]
`
`In yet another embodiment, client device 104 may be a point of sale (POS) devic