1. Small Cell An overview Lutz Freydank
January 2011 – updated August 2011

2. Content
Customization – what?
Current problems
Things to consider
One word on shared secrets

3. CPE customization

4. CPE customization
Security mechanisms require hard coded, unchangeable customer specific data programmed into the Small Cells  one specific part number per customer
BU offers customer specific “look and feel” for Home Cells and V1.5 Enterprise Cells
color of casing
customer logos
different casing type (Vodafone only)
examples V2-EC-1 (Home Cell from Zyxel)
So far we have customized versions
17 for V1.2-EC
34 for V1.5-EE
20 for V2-EC – 6 for V2-AC – 12 for V2 Metro program

5. Daily problems
Customization takes too long – up to 8 weeks until all content is clarified (record holder is DU UAE)
TPM’s are not informed about complete background of customization
not allowed to use lab mode Small Cells for commercial use or in unsafe environment
do not know the procedure how to customize with personalization guide
Root certificate are a regular problems – local team have difficulties to generate with the customer
Customer specific user guide, packaging data are sent in not appropriate form (.ai files requested)

6. Daily problems - solutions
Raise awareness at account teams that customization is needed and requires strong action from them
TPM’s need to drive activity and carefully read the personalization guides (these contain a lot of information also in terms of time lines)
Inform the customer openly that he has to provide inputs in time and in right format
If customer wants ALU to do the design of their QSG, this needs to be factored into the timeline (we have no function for that)
Technical training for TPM in terms of certificate generation

7. One word to shared secrets
Shared secrets are secret  only send in encrypted mail ( TPM should use the global ALU certificate to encrypt)
Shared secrets are stored in OLCS – all “generic units” are in one big file – access can be granted if needed – please contact WLS SC to get access (requests will be double checked!)