Lucent Work

Last Update: Dec 2007

I work in Global Adaptive Feature (GAF) group of CDMA core network since I graduate in July 2004. This group develops and test adaptive features from customers in U.S, China, Russia, Vietnam, India, Poland and other countries. The customers include Verizon Wireless, Sprint PCS, Metro PCS, India Reliance, China Unicom, Telecom New Zealand…In a sense, the team is customer-driven. The Application Engineers convert the customer request in to a RDAF document; System Engineers then write requirements based on this RDAF. Developers and testers in my team do the remaining work. Most of the features are delivered in a couple of months (Dev. + testing), which is really very fast when you compare it with Lucent half year regular product Development cycle.

I'm a full-time feature tester since I join Lucent. Below is part of the features I've taken since 2004 (A feature is basically a functionality required by customer (like color ring back tone) and is indeed a project in other company. This is terminology used in telecommunication community.

MMC for China Unicom (Test Only), Nov 2007 -- Dec 2007

MMC (Mobility Manager Compact) is a new platform of Lucent Mobile Switching Center. It has smaller footprint than old FMM (Flexent Mobility Manager). China UniCom required this product and need some regression test. This project is under way. We are doing test on specific configuration of Unicom, e.g. SS7 ITU-24 Signaling, Two-Way Global Title Translation, Color Ring back Tone, International Roaming, Wireless Intelligent Network, Multiple DCS (Digital Cellular Switch).This feature is being tested in Lucent Shanghai lab.

IT Trigger Based CRBT Service at O-MSC, Sep 2007 -- Apr 2008

Sprint PCS now is using CRBT (Color Ring Back Tone) and need IS-771 WIN service support. Sprint wants to migrate IS-771 to IS-826 WIN service, and required Lucent development a CRBT feature that is compatible with IS-826. 50% of the test will be run in Lucent system lab at Lisle, Chicago.

Per cell based Max CPAGE SMS Bearer Data Size, May 2007 -- Sep 2007

Lucent Base station support sending and receiving short message via traffic channel and paging channel. Whether go via traffic or paging channel are decide on MSC side by the length of the message. Verizon Wireless request Lucent base station make the decision instead of MSC. This feature has development work on both MSC and base station. Interface test are conducted in Beijing lab. ~100 tests are done including deliverable test, Feature test, interaction test, regression test, and cell platform test. The testing team includes Olina, the base station tester and me, the MSC tester.

Support Packet Pipe Information in PCMD, Feb 2007 -- May 2007

Metro PCS requested to place packet pipe information in PCMD for the initial and final cell. The information would have to be data from the CDN for the initial and final cell. This feature has only been tested in the domestic market (North America market).

SDCA Display Suppression for Packet Data Call, Nov 2006 -- Feb 2007: honors!

'Without Data there is no Voice'

The 1st Packet Data feature I took. India Reliance has 'Limited Mobility Services' feature active, which sent SDCA info to mobile station for displaying, thus blocked the calling party number when mobile in Voice/Data call. Then this feature is created to suppress the SDCA info in a data call.

I did all the tests physically in U.S. system lab, which is very similar to Reliance field site.

Initial Cell Based Billing feature enhancement for ISPAGE2, Jun 2006 -- Oct 2006

Initially the problem was found on Russia site that the AMA sub-system (for subscriber billing information on Lucent MSC) get incorrect data when user have slipped (ISPAGE2) to another MSC. The reason is the original serving MSC does not know the cell information on the bordering MSC. To get such information, border MSC have to send the cell information in the ISPAGE2 Return Result and serving MSC store them in the AMA record for later use.

What I did in this feature: ISPAGE2 scenario, Inter-MSC Soft Handoff...

There has been a U.S. patent for this feature but with a little difference: Reliable related billing ID information method for call delivery. They said when you are careful and patient enough, and keep the patent application in your mind, then you can succeed one day...but I doubt we can wait till that day comes.

Deliverable/Feature Test for "Support of Hard Handoff for Voice Transparency", Nov 2005 -- Apr 2006

This feature is for China Unicom, which plans to deploy a new service called Voice Transparency Service to serve government and army for security purpose. Subscriber will use a new type of mobile station (produced by ZTE) with special button. After normal traffic channel set up between A party and B party, the subscriber will push the special button to set up new application upon the traffic channel. The new voice coding and decoding work will be done by mobile station, not voice coder in MSC. The call processing is transparent to MSC and Base station.

Over 80% testing work (Deliverable and Feature Test) are done in U.S. system lab. Basically all the air interface test need to be executed at real system lab, while the code change on the MSC/switch is allowed to be tested in a simulated environment.

My work includes:

Make end-to-end voice call scenario in U.S. system labs. End-to-end call means to use the real handset and real cell site (base station, as the official name). All the Lucent system labs use a Radio Frequency (RF) matrix to control the signal that goes to the handset. This is a good way to minimize the RF leakage. To make it, users have to be a skilled user of QualComm CAIT suite.
Reload, Reboot, bring up and trouble shoot base station. Base stations (Lucent cells) are among the most profitable CDMA products in North America region and Asia-Pacific. They also are such sophisticated equipments that even Lucent engineers have to make great effort to get their knowledge. For testing work on MSC, lab users usually merely need to have basic trouble shooting skills. In this feature’s testing phase, I added a new software package (i.e. a new operating system usually Vxworks) to the cell, bring it up and attenuate it to get the right RF signal I want.
Configure Radio Frequency Signal in multi-carrier env. (AMPS, TDMA, CDMA cellular, CDMA PCS). The cells in the laboratory include CDMA, TDMA and even AMPS (the 1st generation telecommunication system in North America). Lab users have to exclude the interference of unwanted RF signal and make the expected signal 'the active set' on mobile phone.
Deliverable, feature and regression test on Lucent proprietary Soft Handoff, Semi-soft Handoff, Inter-Vender Hard Handoff, including both sunny day and rainy day scenario. Basically the 'Voice Transparency' feature takes most advantage of exiting Inter-Vender Hard Handoff strategy. The result is the minimized development work but large amount of feature interaction test and regression test. The difference between Soft Handoff, Semi-soft and hard Handoff is...to say it in a word, they release and allocate resources in a different level. Soft handoff barely release any resource so get a most stable call, while hard handoff release then seize almost all the resource, so the risk of dropping a call increases.

Mobile Equipment Identifier (MEID), Jul 2005 -- Oct 2005

This is a mandatory feature required by IS2000 for Verizon U.S. MEID is the upgraded mobile Electronic Serial Number (ESN). In this feature no significant architecture is changed but since ESN is widely used in the whole Call Processing (Mobile origination, Mobile Termination, paging and Authentication...), the Development and unit testing work is huge.

My part of Unit Test covered Voice call, Circuit/Packet Data Call, 911 Emergency Call, Call Termination, Short Message Service (SMS), Inter-MSC Soft handoff, malicious call, Over The Air Service Provisioning (OTASP). Also about 12 TI (technical Input) test cases are executed in this phase. TI is widely used in Lucent product for people at service provider and Lucent field engineers to monitor system and make configuration change.

Most of the unit test cases are executed in COOL, which is a simulated MSC (different platform but real code for Application layer). Lucent Development and Verification requirement unit test cases can be executed in simulated environment, while Deliverable/Feature Test and Regression Test must be verified in real laboratory. In real system lab, we have a powerful tool AVS (Automated Verification system) which can reload the whole MSC (switch, base station...) in a couple of hours. In Motorola it takes a couple of days to complete the same task.

ISPAGE Support for CRBT feature, May 2005 -- Jul 2005

This is a very interesting feature, and also a hot feature at the time it was requested. ISPAGE means Inter-System paging. This is a paging strategy introduced by ANSI-41D. Lucent has its own proprietary ISPAGE prior to IS41D. In a word, ISPAGE feature would page the abutting MSC when a subscriber slips (enter but hasn't registered yet) into another MSC, and increases the paging response rate dramatically.

CRBT means Color Ring back Tone. 'Color Ring'...yes you are right, it is the color ring widely used today on users' mobile handset. Indeed Color Ring comes from South Korea with its original name as 'X-Ring'. Lucent development the 'Color Ring' by temporarily connects the incoming trunk to a CRBT server. When called party answer the phone call, MSC disconnect the incoming trunk with the CRBT server and connect it with the called party trunk.

This feature deals with the feature interaction between the ISPAGE and CRBT. Only part of the testing work was done before I was ransferred to other project with higher priority.

Return Cause Code 4 (not 65) to SMDPP for TDMA mobile, Sep 2005 -- Nov -- -- 2005

This feature allows the Lucent MSC with co-existence of TDMA and CDMA base stations to respond with the cause code of 4 (Invalid Teleservice ID) to the Message Center (MC) when receiving the TIA/EIA-41 SMDPP (SMSDeliveryPointToPoint Invoke) message with a CDMA Teleservice ID for a TDMA mobile.

In the test I verified the SMS functionality on an idle/busy Mobile station in both TDMA and CDMA system. Lucent have same MSC for TDMA and CDMA system, There is only different base stations between them.