AT&T U verse® Enabled · 01/11/2013 · © 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Page 4 of 16

© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

AT&T U-verse® Enabled

User Device Interface Design Guidelines

Publication Date: November 1st, 2013

Legal Disclaimer


i

This document and the information contained herein (collectively, the "Information") is provided to you (both the individual receiving

this document and any legal entity on behalf of which such individual is acting) ("You" and "Your") by AT&T, on behalf of itself and

its affiliates ("AT&T") for informational purposes only. AT&T is providing the Information to You because AT&T believes the

Information may be useful to You. The Information is provided to You solely on the basis that You will be responsible for making

Your own assessments of the Information and are advised to verify all representations, statements and information before using or

relying upon any of the Information. Although AT&T has exercised reasonable care in providing the Information to You, AT&T does

not warrant the accuracy of the Information and is not responsible for any damages arising from Your use of or reliance upon the

Information. You further understand and agree that AT&T in no way represents, and You in no way rely on a belief, that AT&T is

providing the Information in accordance with any standard or service (routine, customary or otherwise) related to the consulting,

services, hardware or software industries.

AT&T DOES NOT WARRANT THAT THE INFORMATION IS ERROR-FREE. AT&T IS PROVIDING THE INFORMATION TO YOU

"AS IS" AND "WITH ALL FAULTS." AT&T DOES NOT WARRANT, BY VIRTUE OF THIS DOCUMENT, OR BY ANY COURSE OF

PERFORMANCE, COURSE OF DEALING, USAGE OF TRADE OR ANY COLLATERAL DOCUMENT HEREUNDER OR

OTHERWISE, AND HEREBY EXPRESSLY DISCLAIMS, ANY REPRESENTATION OR WARRANTY OF ANY KIND WITH

RESPECT TO THE INFORMATION, INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATION OR WARRANTY OF

DESIGN, PERFORMANCE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, OR

ANY REPRESENTATION OR WARRANTY THAT THE INFORMATION IS APPLICABLE TO OR INTEROPERABLE WITH ANY

SYSTEM, DATA, HARDWARE OR SOFTWARE OF ANY KIND. AT&T DISCLAIMS AND IN NO EVENT SHALL BE LIABLE FOR

ANY LOSSES OR DAMAGES OF ANY KIND, WHETHER DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE,

SPECIAL OR EXEMPLARY, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS

INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF GOODWILL, COVER, TORTIOUS CONDUCT OR OTHER

PECUNIARY LOSS, ARISING OUT OF OR IN ANY WAY RELATED TO THE PROVISION, NON-PROVISION, USE OR NON-USE

OF THE INFORMATION, EVEN IF AT&T HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES OR DAMAGES.

Table of Contents


ii

Contents

1 Introduction .......................................................................................................................................... 1

1.1 AT&T Requirements ...................................................................................................................... 1

2 Guidelines for User Devices .................................................................................................................. 2

2.1 U-verse Enabled Pairing Process ................................................................................................... 2

2.2 My U-verse Receivers Screen ........................................................................................................ 4

2.3 Add Receiver Screen in Custom Mode .......................................................................................... 7

2.4 Add New Receiver ......................................................................................................................... 9

2.5 Success ........................................................................................................................................ 11

2.6 Pairing Errors ............................................................................................................................... 13

2.7 Internet and Network Errors ....................................................................................................... 14

Table of Figures


iii

Figure 2-1: U-verse Enabled Pairing Process ................................................................................................ 2

Figure 2-2: My U-verse Receivers Screen ..................................................................................................... 4

Figure 2-3: Add Receiver Screen ................................................................................................................... 7

Figure 2-4: Add New Receiver Screen ........................................................................................................... 9

Figure 2-5: Success Overlay ........................................................................................................................ 11

Figure 2-6: U-verse Receivers Screen ......................................................................................................... 12

Table of Tables


iv

Table 2-1: Display Text .................................................................................................................................. 5

Table 2-2: Display or Hide Add New Receiver Button .................................................................................. 6


Page 1 of 16

1 Introduction

The U-verse Enabled framework enables various internet devices to connect and control U-verse Receivers through the home network. The user devices connecting to the receivers are required to follow the U-verse Enabled pairing process in order to properly connect to the receiver.

This document provides User Interface guidelines for the various devises to initiate and maintain the connection to the U-verse Receivers.

1.1 AT&T Requirements

The guidelines in this document are meant to ensure that our customers are seeing the same language consistently, especially when pairing a device to receivers. As a developer you have near complete control when it comes to your user-interface, however, the following AT&T requirements must be followed:

The set top box (receiver) must always be referred to as an AT&T U-verse Receiver.

Applications should not alter the functions of standard remote control commands.

All AT&T U-verse Enabled apps should provide a consistent method for customers to manage devices and receivers. Developers must comply with all requirements and steps as demonstrated in this document as well as the AT&T U-verse ® Enabled Developer Guidelines. Developers may skin the interface to match the overall application design, but should not change any of the user flows or interactions. Minor content changes are allowed as long as they do not violate any branding guidelines or change the user interactions.

https://developer.att.com/home/develop/sdks/Uverse_Zeus_updated.pdf


Page 2 of 16

2 Guidelines for User Devices

The following guidelines describe the screens and error messages that you must use when designing the UI for user devices.

2.1 U-verse Enabled Pairing Process

The following illustration shows how devices are paired with U-verse Receivers.

Figure 2-1: U-verse Enabled Pairing Process


Page 3 of 16


Page 4 of 16

2.2 My U-verse Receivers Screen

This screen displays the list of set top boxes (STBs) that the device can connect to. The screen can be presented during the setup flow for the app or in the Settings section in an app. The elements of the screen are described following the illustration.

Figure 2-2: My U-verse Receivers Screen


Page 5 of 16

Screen elements include the following:

Close Button: In a step-by-step Setup flow, display ‘Next’ as the label and display the next screen on tap. In the Settings section, on tap hide this screen and display the previously displayed screen.

Instruction text: Display relevant text based upon the following scenarios.

Scenario Displayed Text

No U-verse Receivers Detected

There are no U-verse Receivers in your network. If you have U-verse TV service, make sure that you are connected to the same U-verse wireless network as your U-verse receivers, and that the receivers are powered ON.

No U-verse Enabled Receivers Detected

You have not configured any receivers. Tap on ‘Add New Receiver’ for instructions on how to connect this device to a receiver.

U-verse Enabled Receivers Detected

Tap on a receiver name to connect your device to that receiver.

All Receivers Detected are U-verse Enabled

Tap on a receiver name to connect your device to that receiver.

Table 2-1: Display Text

Available STB List: Display an alphabetically ordered list of all STBs on the Wi-Fi network that match any of the following criteria:

o STBs with connection mode set to Default.

o STBs with connection mode set to Custom, but pairing code has already been entered.

STBs with connection mode set to Custom, but no code has yet been entered. In this case, display the

entered. In this case, display the STB name with a lock and details button as shown in the second item in

button as shown in the second item in the list. Tapping on the details icon will display an Add Receiver in

icon will display an Add Receiver in Custom Mode screen. For details, see Section 0

see Section 0


Page 6 of 16

o Add Receiver Screen in Custom Mode.


Page 7 of 16

Add New Receiver Button: Display or hide this button based upon the following scenarios.

Display Hide

No U-verse Enabled Receivers detected

Some U-verse Enabled Receivers detected

OnTap: Display an Add New Receiver screen

No U-verse Receivers Detected: All Receivers Detected are U-verse

Enabled

Table 2-2: Display or Hide Add New Receiver Button


Page 8 of 16

2.3 Add Receiver Screen in Custom Mode

When a user selects to add a receiver that has already been set up to custom connection mode, the following screen is displayed. The elements of the screen are described following the illustration.

Figure 2-3: Add Receiver Screen


Page 9 of 16


Done button: This button should be disabled until all code input fields are populated.

On tap, display an Adding Receiver Overlay screen.

Back button:

On tap, display a My U-verse Receivers screen shown in Figure 2-2.

Instructional text and graphics: Display step-by-step instructions as shown. The receiver name in Step 1 should be updated to reflect the name of the receiver that is being added.

Code Input fields: Display four input boxes for the PIN code. Characters entered in the keyboard will be displayed in the field, as shown below. As a character is entered in a field, the cursor will automatically advance to the next field (standard behavior).

2 4 5 9

If the user taps the Delete key, clear out the last character entered.

Numeric keyboard: Display standard OS numeric keyboard.


Page 10 of 16

2.4 Add New Receiver

When a user selects to add a new receiver that has not yet been set up, the following screen is displayed. The elements of the screen are described following the illustration.

Figure 2-4: Add New Receiver Screen


Page 11 of 16


Next button: On tap,

o If the connection mode has not been set, display an STB connection mode not set. See Error Code 2-1: Pairing Errors.

o If the user has selected custom connection mode during the STB set up, display the Add Receiver screen shown in Figure 2-3.

o If the user has selected any default mode for the STB, display the Success overlay shown in Figure 2-5 or the relevant error.

o If the user has disabled the connection to the STB, display a disabled connection mode error. See Error Code 2-1: Pairing Errors.

Back button: On tap, display a My U-verse Receivers screen (Figure 2-2)

Instructional text and graphics: Step-by-step wizard on the TV.


Page 12 of 16

2.5 Success

This overlay is displayed over the screen that represents the last step of the pairing path taken by the user. For various paths to this overlay, see Section 2.1 U-verse Enabled Pairing Process. At this point, the system will try to pair with the U-verse receiver in question. During this process, display the modal as shown with animated loading indicator.

Figure 2-5: Success Overlay


Page 13 of 16

When the connection process is successful, display the following screen with the newly added Receiver name added at its alphabetical place in the available receivers list. Also display a ‘NEW’ tag next to the name if the receiver has just been added to the list. This tag will be removed once user exits this screen.

Figure 2-6: U-verse Receivers Screen

The newly added receiver should be the one that is currently connected to the device. All other interactions on this screen remain the same as documented in Section Figure 2-2 My U-verse Receivers Screen.

For unsuccessful connection, display the applicable Pairing error (Error Code 2-1).


Page 14 of 16

2.6 Pairing Errors

These errors are displayed as overlays over the screen that initiated the error.

If the PIN entered by the user is incorrect, display this error.

On tap, the Try Again button displays the Add Receiver (

Figure 2-3) or Add New Receiver (

Figure 2-4) screens.

If user taps on the Next button in the Add New Receiver screen before the STB connection mode has been set, display the following error: STB connection mode not set:

On tap, the Dismiss button displays the Add New Receiver (

Figure 2-4) screen.

If there was an error in connecting to the STB after several attempts, display this error.

On tap, the Dismiss button displays the My U-verse Receivers screen (

Figure 2-2).

If the user sets the connection mode to “disabled” during the setup wizard, display this error.

On tap, display the My U-verse Receivers screen (

Figure 2-2) without the corresponding receiver listed.

Error Code 2-1: Pairing Errors


Page 15 of 16

2.7 Internet and Network Errors

If there was a network error during the launch of a U-verse Enabled on the device, the following errors are displayed in place of the U-verse

Receivers list shown in

Figure 2-2.


Page 16 of 16

Wi-Fi/Internet Error

U-verse Network Error

Error Code 2-2: Network Errors

AT&T U verse® Enabled · 01/11/2013 · © 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Page 4 of 16

Documents