12.07.2015 Views

MCPC-TR-002 Hands-Free Profile 1.5 Application Guideline ...

MCPC-TR-002 Hands-Free Profile 1.5 Application Guideline ...

MCPC-TR-002 Hands-Free Profile 1.5 Application Guideline ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

©Copyright 2006-2011 Mobile Computing Promotion Consortium (<strong>MCPC</strong>)<strong>MCPC</strong> <strong>TR</strong>-<strong>002</strong> <strong>Hands</strong>-<strong>Free</strong> <strong>Profile</strong> <strong>1.5</strong> <strong>Guideline</strong> Version <strong>1.5</strong>1 Appendix A- If the address cannot be classified, it shall be described in Field-2.(11) Company name: ORG- Company name shall be set in Field-1.- Section name shall be set in Field-2(12) Send property for each IrMC Level:- Data transfer in IrMC Level 1The main case is expected between cellular phones of different users. In this case, propertiesfor Group settings and speed dial settings shall not be transferred in order to avoidinconsistency of date between the sender and the receiver. Secret property shall be transferredas the default value, PUBLIC.- Data transfer in IrMC Level 2/3/4 The main case is expected between cellular phones or PC of the same user. In this case, allproperties implemented shall be transferred as their settings(13) Entire objects:- When creating entire objects, the owner information shall be added as the head data. If theowner information is missing, the head data shall be empty.- As an example of creating entire objects for a cellular phone which does not support Static Indexof IrMC Level 3, the method of sorting the second data and the following data in Gojyu-on, theJapanese syllabary, order is expected.< Import >(1) Character code settings: CHARSET, ENCODING- Receiving objects, which CHARSET is SHIFT-JIS or UTF8, shall be enabled. If CHARSET is notdefined, it shall be regarded as SHIFT-JIS.- If ENCODING is QUOTED-PRINTABLE or BASE64, the object shall be able to be received. IfENCODING is not defined, the object shall be able to be received as no ENCODING.- If CHARSET/ENCODING is defined other types, the object shall be able to be receivedaccording to the feature of the cellular phone.(2) Version information: VERSION- VERSION:2.1 indicated vCard shall be able to be received.- If there is no VERSION property, it shall be received as VERSION:2.1.- If VERSION:3.0 is indicated, vCard3.0, it shall be able to be received according to the feature ofthe cellular phone.(3) Name: N- Data in Field-1 of N shall be set as the last name, Field-2 as the first name.- If N is not divided in Fields, whole data shall be set as the last name.- If there is no N property, or if N is NULL and FN exists, data in FN shall be set as a name. In thiscase, whole data shall be set as the last name.(4) Furi-gana: SOUND or Sort_String- Data shall be set as Furi-gana which property is indicated in extended parameter after SOUNDor Sort_String.- It is recommended that data between „‟ can be received.(5) Telephone number: TEL- Example of the parameter and type of TEL:VOICE-> General phone [default]CELL-> Cellular phoneHOME;VOICE -> HomeWORK;VOICE -> WorkFAX-> FAX9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!