RE: new ECML v 2 requirements from Nokia

I would argue that the loyalty card number does not need to be longer than 19 digits, simply
because a standard credit card magstripe cannot hold much more than 19 digits. In fact many loyalty
programs today use ISO standard card numbers.

As for the loyalty expiry date, why not have a single field formatted as an XML date (CCYY-MM-DD)?

_________________________________________________

Christopher Brandt
Interfaces Manager
Ernex Marketing Technologies
Suite 225
4259 Canada Way
Burnaby, BC, V5G 1H1
Ph:  604-415-1554
Cell: 604-728-1537
Fx:  604-415-1589
[email protected]
www.ernexinc.com


-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, June 03, 2002 5:44 AM
To: [email protected]
Subject: new ECML v 2 requirements from Nokia


NEW ECML v 2 REQUIREMENTS from Nokia

Nokia has identified need for new ECML fields, we  would like to see these in ECML version 2. Below
is short description on the need for fields and a proposal for the field name, length and usage
notes.

Nokia among other companies is driving for ticketing usage of mobile terminal in MeT forum
www.mobiletransaction.org. In these scenarios a ticket is purchased remotely using ECML, but as an
identifier for possible later ticket refunds and for using the mobile device as the access token ,
a device unique ID number is given for the ticketing service provider. Thus a new ECML field is
needed where the ticketing service provider requests the ID and terminal can respond. Also
information on the ID type is given.

Ecom_Device_ID       
length: 70     Note: alphanumeric unique identifier (length=IPv6 space)

Ecom_Device_ID_type  
Required if Device ID used.
length: 20     Note: name or brand of deviceID system used

Also for remote purchasing, a need for loyalty card information has been identified. Thus in
payment situations the user can also tell the commerce site a loyalty card number and receive bonus
points etc. It is assumed that the user will select the correct bonus card system, so that the site
can advertise that it accepts  "e.g."  a K-shop loyalty card and user will send the correct card if
he/she has multiple loyalty cards. 

Loyalty cards often include expiry date. Loyalty cards may contain credit payment to that shop or
chain, therefore the data needed for a loyalty card is similar to payment card data. Systems
already hanfle loyalty cards with same data as magnetic stripe payment cards. Small difference is
that loyalty card numbers do not seem to have any common standard (as comapred to payment card
number, ISO 7812), so longer field is needed.

Ecom_Loyalty_Card_Name
    
Ecom_Loyalty_Card_Number    
Requried minimum data for loyalty usage.
length:60         Note: Not purely number, number field may contain also characters (e.g. flight
bonus  cards)

Ecom_Loyalty_Card_Type
lenght:20		Note: longer text field needed due to amount of loyalty systems

Ecom_Loyalty_Card_Verification

Ecom_Loyalty_Card_ExpDaate_Day
Ecom_Loyalty_Card_ExpDate_Month
Ecom_Loyalty_Card_ExpDate_Year

And a need for generic user data for simple content personlaization has been identified. User can
send some generic personal information fo further allow the service to tailor the content for the
age and or location of the user.

Ecom_UserData_BirthDate_Day        
lenght: 2                

Ecom_UserData_BirthDate_Month     
length: 2

Ecom_UserData_BirthDate_Year       
length: 4

Ecom_UserData_Country          
length:20

Ecom_UserData_Language       
length:20

Ecom_UserData_Gender          
length:1
M(ale)/F(emale)

Ecom_UserData_Preferences   
length:60    Note: This would be free text 


sincerely,
- Lauri Piikivi 
-------------------------------------------------------- 
Specialist, SW Architecture 
Nokia Mobile Software
[email protected] 
phone: +358 7180 47045 
mobile:+358 40 559 7045 
--------------------------------------------------------