AAB_Lab_Onboarding_Guidex

voraciousdrabΛογισμικό & κατασκευή λογ/κού

14 Δεκ 2013 (πριν από 3 χρόνια και 8 μήνες)

160 εμφανίσεις


This document contains trade
secrets and
proprietary information of AT&T Mobility. No use or
disclosure of the information contained herein is
permitte
d without prior written consent.

The
information in this document is subject to change
without notice.



Product Realization

AT&T







AT&T Address Book
(AAB)



Lab
On
-
boarding

Guide
for OEMs










Project Sponsor:

Jon Summers, VP Data Product Realization

For questions
about this document, please contact:

Paul Dubuc

pd4030@att.com

or

Ken Decanio
kd593r@att.com





Revision

1.
5

Revision Date

4
/
3
0
/2010



AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
2

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



©2010

AT&T Intellectual Property

All rights reserved.


AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

Revision History

Date

Revision

Description

0
4/
24
/2008

0
.1

First
draft

0
6/
0
2
/
20
09

0.
5

Draft with updates

0
8/20/
20
09

0.9

Updated IOT test cases and added
Device
-
to
-
Web Field Mapping
Document
.

0
9/10/
20
09

1.0

Update to Device Parameters section: remove IMEI and UA
-
string
from required values.

Updated vCard Matrix

for Phone and Email
fields.

10/20/
20
09

1.1

Removed the list of FOA URLs. Added URLs for Web Login for
production and Lab environments.
Added additional work
-
arounds in
section 4.5
. Update to the vCard Matrix (v1.3)

12/
0
1
/
20
09

1.2

Update to the
formatting of vCard Matrix (v1.4)

0
1/
0
6/
20
10

1.3

Updated the terminology used to identify the lab testing environments
(“Lab1” changed to “QA”, and “Lab2” changed to “OEM”).

0
3/
0
3
/
20
10

1.4

Update to QE test cases in section 6.

Removed section 2.2.6


Device
-
to
-
Web Field Mapping

Added “Server ID” to Appendix C

Updated 4.1 adding new proxies

Updated 4.4 userID/password

Updated Sample DevInf [“CELL (WORK)” => “CELL,WORK”]

04/30/2010

1.5

Create “
17651 AT&T Address Book
-

Data Specification for Mobile
Devices
” replacing #16852

Move much information to new Data Spec document including
Appendix B and C

Moved the DevInf example to “
AAB How To
-

DevInf


Updated login for ENG domain. Must use “
\
” not “/”

Clarified information in section 4.1


AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
3

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



Contents

AAB Lab On
-
boarding Process

................................
................................
.................

5

1.

Getting Started

................................
................................
................................
......

5

1.1.

References

................................
................................
................................

5

2.

Submi
t AAB Deliverables

................................
................................
....................

6

2.1.

AAB Lab Support Contact List

................................
................................
...

6

2.2.

Device Details

................................
................................
............................

6

2.2.1

Comp
rehensive vCard Matrix

................................
...................

6

2.2.2

DevInf.xml

................................
................................
.................

6

2.2.3

Data Validation Rules
................................
................................

7

2.2.4

Device Parameters
................................
................................
....

7

2.2.5

Device Configuration Procedures

................................
.............

8

2.2.6

Device
-
to
-
Web Field Mapping

..

Error! Bookmark not defined.

3.

Physical Access Request

................................
................................
....................

8

3.1.

Lab SIMs

................................
..................

Error! Bo
okmark not defined.

4.

AAB Account Setup

................................
................................
...........................

10

4.1.

Log
ging in to ENG Domain

.......................

Error! Bookmark not defined.

4.2.

Viewing and Editing Contacts Online

.......

Error! Bookmark not defined.

4.3.

Managing Devices

................................
................................
...................

11

4.4.

Workaround for ‘Advice of Charge’ Notice

Error! Bookmark not defined.

4.5.

Other Updates

................................
................................
.........................

11

5.

Inter
-
Operability (IOT) Testing

...............................

Error! Bookmark not defined.

6.

AAB Client Ready for Lab Entry

................................
................................
.......

12

Appendix A


DevInf Sample

................................
........

Error! Bookmark not defined.

Ap
pendix B


Device Configuration Settings

.............

Error! Bookmark not defined.

Appendix C


Manual Provisioning

..............................

Error! Bookmark not defined.



AT&T Address Book (AAB)


Lab On
-
boarding Guide for OE
Ms

©2008 AT&T Intellectual Property


Page
4

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



Acknowledgments


The following people have contributed to this document:



Paul Dubuc



Ken Decanio



Jon Bylin



Andre Okada



Trent Burkard



Ron Barchi



Leland Yu


AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
5

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



AAB Lab On
-
boarding Process


This document details the process for OEM vendors to setup testing in AT&T Mobility labs
against the AAB lab server.
The following sections will detail out the stages in the AAB Lab On
-
boarding process:


1.

Getting Started

The AAB server uses SyncML protocol to synchronize the device’s Personal Information
Management (PIM) data. Details of this interface and the supported PIM data types are
provided in the following documents:

1.1.

References

T
he AAB Document Rel
e
ase package

should already have been
delivered to your
team by AT&T SPE

(Subscriber Product Engineering) and it
contains the
documents

listed below
. If you have not received

any of these reference
documents
, simply
notify your AAB project sponsor
.

[R1]

AT&T Address Book I
nterface Specifications for Mobile Terminal

(document #16572)

[R2]

AT&T Address Book
-

Data Specification for Mobile Devices

( #1
7651
)

[R3]

AT&T Address Book
Native Sync MAXD

[R4]

13340 Chapter 52


[R5]

AAB Display o
f Provisioning Errors by Device

AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
6

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



2.

Submit AAB Deliverables


Prior to entering AT&T Mobility labs for testing, you are requested to submit the
Phase 1
Device D
eliverables
(see below)
to
your AAB sponso
r

at Lab Entry
-
21 weeks and
Phase 2 Device Deliverables by

Lab Entry
-
13 weeks.


Your AAB project sponsor’s contac
t information:

Paul Dubuc

Product Realization Manager

Work #: 425
-
580
-
8563

pd4030@att.com

Jon Bylin

Product Realization Manager

Work #: 425
-
580
-
4906

Jb048g@att.com


2.1.

AAB Lab Support
Contact List

The first step is to please fill out the contact details for each member of your team
who is requesting access to the AT&T Mobility Lab environment.


2.2.

Device
Deliverables


Phase 1

2.2.1

Comprehensive
vCard
Ma
trix

You are requested to
provide a comprehensive AAB vCard list for all fields on the
device client, formatted to support vCard 2.1 as defined in the AAB Data Specification
document
[R2]
.

Based on the recommendation and examples provided in the attached
matrix, p
lease fill
-
in
Column
s D, E, and F

with the vCard 2.1
implementation
for
every
field
on your device

(please include

all examples of field types as well)
. If applicable,
please be sure to include the details for any additional fields supported on your device
that are not listed in this matrix by adding additional rows at the end of the table.


2.2.2

Dev
Inf.xml

In order
for all fields on your device to synchronization with the
AAB server
, the
AAB
server support team will need the device information like device make, model, device
data store details, device sync capabilities, etc.

This information is
required by
AT&T so the AAB Sync S
erver can be customized for
your

handset. This process typically takes up to 8
-
10 weeks. If the handset team
AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
7

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



does not deliver this information in a timely manner, the AAB server cannot be updated
in preparation for hand
set testing.

This information is exactly same as the ‘
DevInf
’ data that the device will be

exchanging
with a SyncML server. For an example see the document “
AAB How To
-

DevInf
”.

Please fill in the Device Parameters
in the
table below and attach your
device’s
DevInf.xml file along with the request your request.

2.3.

Device
Deliverables


Phase 2

2.3.1

Data Validation Rules

Please specify any data validation rules that are applied to the data stored in the
device’s address book. These details will help determine
the expected result of
synchronizing data between device & server during application testing.

Data validation rules may include, for example
:

1.

Must any fields be populated in order to create a valid contact? If so, which
ones?

2.

Does the device client
validate characters entered in the email field to make sure
the user includes the @
-
symbol and a period?

3.

Must phone numbers contain only numerical digits?

4.

Are special characters such as
-

) ( * supported or are they stripped out for
certain fields (e.g.,

phone number)?

5.

Field lengths: list of maximum characters supported for each field.

6.

Does your device client

perform any vCard validation prior to sending data to
AAB

server
?

7.

Any additional validation rules?

2.3.2

Device Parameters

Device Parameter


Value

Mode
l


S/W version


What version of
SAN

do you
support
?

SAN version #

Groups
: please add a checkmark in
the box

below
if your device client support synchronization of
Groups
AT&T Address Book (AAB)


Lab On
-
b
oarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
8

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.





as listed in the
Data Specification

document

[R2]
:


<Ext><XNam>SynchronizeGroup</XNam><XVal>X
-
CT</XVal></Ext>


2.3.3

Device

Configuration Procedures

Please provide detailed step
-
by
-
step procedures and screenshots for configuring your
device for AAB client provisioning, as per the following use cases:

1.

How to change devic
e settings for the sync service:



Steps:


Screenshots:


2.

How to set the Lab AAB server URL

for contacts:


Steps:


Screenshots:


3.

How to set the Lab AAB server URL for SOAP Web Services:


Steps:


Screenshots:

3.

Physical Access
Request

At Lab Entry
-
13 weeks
,

your AAB project sponsor

will work with your test
ing team to
make arrangements for access to the AT&T Mobility lab environment.

3.1.

On
-
Site Testing in Redmond, WA

If your device has not passed the AT&T Protect the Network ‘PTN’ certification process,
you will be required to
test on
-
site in Redmond, WA using

lab SIMs
over the restricted
Lab RF network
. Lab SIMs operate within the AT&T Lab network which has a very
limited range, being only accessible within the RTC
-
2 building in Redmond.


To make use of the AT&T Mobility Lab testing
facilities
, here is a list of items your testing
team will need to bring into the lab:



Mobile device
(s)

for testing



Laptop to access the AAB
Web UI from the
lab
environment

AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
9

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.





Ethernet cable (optional)

Other items that your sponsor will prepare
in advance of
your
arrival:



Reservation of a test area in AT&T Mobility labs



Lab SIMs



AT&T Photo Id*



AT&T Access Badge*



User a
ccount
(s)

on the ENG domain to access the AT&T network and use the
lab ticketing system

(URL:
http
://lab
-
support.mobilephone.net
)

*
Note
: if you have not received your AT&T Photo Id and Access Badge prior to your
arrival, your sponsor will make arrangements to provide a day
-
badge for each person
who is requesting access. Requests must be made at least
3 business days prior to
the date of arrival.

Prior to entering lab, you must review the AT&T Mobility Lab Non
-
Employee Worker
Orientation (attached). It contains details on the above items and also includes rules,
policies, and procedures that apply to
AT&T Mobility Labs.


3.1.1

Accessing the AT&T Network from your PC Terminal

To access the AT&T Network

from within RTC
-
2 from your PC terminal
, you
will need
an ENG account
to login. This information should have been sent
to you via email.


To login, browse to this URL:

http://lab
-
support.mobilephone.net



For

username
enter
:


ENG
\
[username]


then enter your password
.

3.2.

R
emote Testing

If your device has passed the AT&T Protect the Network ‘PTN’ certification process, you
will be
able to run your testing remotely using production
SIMs
over the AT&T production
network
.
Please follow the instructions in the rest of this document and your sponsor will
assist you in getting started.

AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
10

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



4.

AAB Account

Setup

T
o
access
the AAB servers, please configure your device
with
the URLs and proxy
settings listed in
AT&T Address Book
-

Data

Specification for Mobile Devices
.

4.1.

Logging in to AAB Web UI Staging Environment

You can access your
Address Book Contacts online by logging in through the
AAB staging site and accessing the AAB
SyncML Server at the following address:



OEM Web Login URL:
https://intaab.stage.att.net/


In order to successfully login to any AAB
web
environment,
first,
your AAB
account must be provisioned in the database. You can activate a new AAB
account
using your client’s
registration/provisioning SOAP functionality (ref.
document #16572). If your device does not yet support SOAP provisioning, you
may submit a request to
your AAB sponsor to manually create an AAB account

on
the OEM server
.

Second
, y
our AAB sponsor
will
n
eed to
manually create login credentials for
each
of your test
account
s

to
gain
log in
access
to the

AAB ‘OEM’
W
eb
UI
.
If you are
testing with AT&T production SIMs, p
lease
send to your AAB sponsor account
information for each SIM you are testing with. Th
e following account data is
needed:


MSISDN
: “2223334444” for phone number (222) 333
-
4444

Subscriber Number
: One way to find the Subscriber Number for a device is
to point the Web Browser on the device to <
http://gallax.org/proxy
> and look
for “SubID:”

SubID is a long string that looks something like this:
T_GLR_CIN_1234124123532463456457


If you are testing
on
-
site in
the AT&T Lab environment in RTC
-
2, you will
also
need to input the proxy settings into your
computer’s
browser. Here are the
instruct
ions for Internet Explorer:

Tools > Internet Options > Connections > LAN Settings > check ‘use auto config
settings’ and paste the URL:


F
or people in

the

Pacific N
orth

West, USA

http://N
cache.entp.attws.com:8081/proxy_pac_file.js


AT&T Address Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
11

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



For p
eople in the
Southern USA

http://Scache.entp.attws.com:8081/proxy_pac_file.js


(if you fail to connect, please try again without
http://
)


Web Login URL for alternate testing environment
:




‘QA’ servers
:
https://aab.stage.att.net/

Web Login URL
AAB Production environment:



Production

servers
:
https://addressbook.att.net/


4.2.

Managing Devices

on Web UI

From the homepage, you can click the
Settings tab and the ‘My
De
vices


sub
-
tab
to
view
more
information

about the device
that
is set to synchronize

with your

profile.

4.3.

Startup Issues with Data Connectivity

The AT&T
Production
network has a feature that can cause data loss *the first
time* a handset sends data to any destination if the AT&T account does not have
a data plan. If the account has been created with a data plan, this will not
happen. If the account has been used i
n another phone this will not happen.

NOTE: this will not happened with Lab SIMs

This is caused when the network recognizes that the account has not been
provisioned with a data plan. It can take up to 120 seconds for the network to
update all the necess
ary billing databases and allow the handset to send data
from the handset to a destination.

Once the handset has been provisioned for data, this delay will never happen
again for that account.


AT&T Address

Book (AAB)


Lab On
-
boarding Guide for OEMs

©2008 AT&T Intellectual Property


Page
12

AT&T Proprietary

v

1.5



The information contained here is for use by authorized



4/30/2010


person only and is not for general distribution.



The effect this can have on users is that the very first
IsValidSubscriber call will
fail. The HTTP request will be received by the network, but it will not be sent to
the destination.

Please be aware of this issue if you are testing with brand new accounts.

The AT&T solution to this is to direct the user to r
estart the Address book
provisioning process by manually starting a synchronization. This is will be
defined updates to the MAXD or will be provided directly to the OEM by the
OEM’s AAB Program Manager


4.4.

SyncML Authentication

According to OMA SyncML speci
fication, a
UserID and Password

must be

specified in
the Sync Profile. Although AAB does not authenticate using the Sync Profile, the
values cannot be blank
.
We recommend that you use the 11 digit MSIDSN of the
device as both the UserID and the Password.

Example [12065551234 / 12065551234]

5.

AAB Client Ready for Lab Entry

Once you have successfully complete IOT testing and any additional dev testing, your
AAB client will
be ready for hand
-
off to SPE at

Lab Entry.

The
AAB
Quality Engineering (QE) team
is
available to run through user
-
acceptance
testing on your client prior to Lab Entry, if this is acceptable
.
We have found that early
testing of the client leads to much higher success and is of great benefit to help ensure
that as many defects as possible a
re identified and fixed prior to Lab Entry.

For your reference,
please find attached
a
sample test
of
AAB test cases that the QE
team
will run against the client: