Engine oil needs to be checked regularly (weekly). Engine oil consumption is influenced by many factors. Under high loads an engine will consume more oil than usual. To check the engine oil use engine oil dipsticks and see if the oil is between min-max scale. Technically, you need to withdraw the dipstick and wipe the blade clean with a lint free cloth and then fully re-insert the dipstick and withdraw again to clearly see the oil level. NEVER allow the oil level to fall below the lower mark/notch on the dipstick.

Engine oil in my case needs to be replaced at least every 10000km. Recommended oil for landrover LR2 2008 is Castrol. Engine oil spec is OW-30 engine oil meeting ACEA A5/B5 spec.The approximate quantity of oil required the level from minimum to maximum on the distick is 1.2 litres (for petrol model only)

Point no. 2 for checking is engine coolant reservoir

This collant as per Wikipedia (http://en.wikipedia.org/wiki/Coolant) is a fluid which flows through a device to prevent its overheating, transferring the heat produced by the device to other devices that use or dissipate it. Hence this is very important, no collant means your engine can be overheated and damaged. In LR2, we will get warning from computer system if the coolant reservoir level drop below the recommendation. Currently I still have no idea the brand used for my car but I will ask my dealer soon, in the manual it’s only mentioned that it;s mixed between 50% water and 50% Texaco XLC antifreeze. Remember to always check things when engine is off and cool.

Please note that we can only use fresh (rain/distilled) water, water contains salt can make serious engine damaged so don’t use it.

Personally, I like both tools and feels that those tool will be very usefull in the future.
I was struggling to find a tool to spy communication between SIMcard and Mobile, but now if I need it,
I will contact both of them

If you like & need it, try to contact them.

So I managed to create my own function that works fine so far (hopefully) (but I don’t care if my algo is not optimal nor bad:)) below:

<?
function strToHex($string)
{
    $hex='';
    for ($i=0; $i < strlen($string); $i++)
    {
        $hex .= dechex(ord($string[$i]));
    }
    return $hex;
}
function hexToStr($hex)
{
    $string='';
    for ($i=0; $i < strlen($hex)-1; $i+=2)
    {
        $string .= chr(hexdec($hex[$i].$hex[$i+1]));
    }
    return $string;
}

function hexbin($hex){
    $bin='';
    for($i=0;$i<strlen($hex);$i++)
        $bin.=str_pad(decbin(hexdec($hex{$i})),4,'0',STR_PAD_LEFT);
       return $bin;
} 

function binhex($bin){
    $hex='';
    for($i=strlen($bin)-4;$i>=0;$i-=4)
        $hex.=dechex(bindec(substr($bin,$i,4)));
   return strrev($hex);
}

function Convert8BitTo7Bit($string){
	// Convert String to Hex first
	// E.g *135# will be converted to 2A 31 33 35 23
	$string = strToHex($string);
	// print   "STR = $string\n";
	$total = "";
	for($i = 0; $i < strlen($string); ){
		// Get 1st character string, it's 2 character hex
		$X = $string[$i++].$string[$i++];
		// Convert it to binary
		$my8bit = hexbin($X);
		//print "(8bit) ==> $my8bit\n";
		// remove left side of octet, it shall be septet
		// e.g 2A in octet is 00101010 (8 bit), remove most left 0 --> 0101010 (7 bit)
		$my7bit = substr($my8bit,1,7);
		//print "(7bit) ==>  $my7bit\n";
        // Concatenate it
		$total = $my7bit.$total;
	}
	// Padding the string
	if(strlen($total) % 8 != 0){
		$p1     = (intval((strlen($total) / 8)) + 1) *  8;
		$total  = str_pad($total,$p1,'0',STR_PAD_LEFT);
	}
	$pad   = 7;
	// Conversion begin
	for($i = strlen($total) - 1; $i >= 0 ; $i--){
		$mypad[$pad--] = $total[$i];
		if($pad < 0 || $i <= 0){
			$pad  = 7;
			$tmp1 = array_reverse($mypad);
			//print_r($tmp1);
			$tmp2 = implode($tmp1);
			$res = binhex($tmp2);
			$result .= "$res";
		}
	}
	return $result;
}

?>

To use that code, we simply call the function like this

print Convert8BitTo7Bit("*135#")."\n";

It will print “AAD8AC3602″ which represent hexcode to be send on top of TP-UD GSM 03.40

Another wxample: we have 160 characters to send like below
“Test SMS content 160 characters will be displayed as 140 octets. Test SMS content 160 characters will be displayed as 140 octets.Test SMS content 160 characters”

With calling

print Convert8BitTo7Bit("Test SMS content 160 characters will be displayed as 140 octets. Test SMS content 160 characters will be displayed as 140 octets.Test SMS content 160 characters");


We get 140 octets/bytes hexadecimal code for this:


d4f29c0e9a36a7a0f1db4d2fbbe9a0980d061aa3c3f2f0985e96cf41f7349b0d129741e4f41cce0ee7cb6450780e8ad160a0f7985ea6cf5d206a794e074d9b53d0f8eda697dd7450cc06038dd16179784c2fcbe7a07b9acd0689cb20727a0e6787f36532283c07c56830d07b4c2fd3e72e6a794e074d9b53d0f8eda697dd7450cc06038dd16179784c2fcbe7


Anyway, there’s 1 thing missing here:
as per GSM 03.38

If the total number of characters to be sent equals (8n 1) where n=1,2,3 etc. then there are 7 spare bits at the end of the message. To avoid the situation where the receiving entity confuses 7 binary zero pad bits as the @ character, the carriage return or character (defined in clause 6.1.1) shall be used for padding in this situation, just as for Cell Broadcast.
If is intended to be the last character and the message (including the wanted ) ends on an octet boundary, then another must be added together with a padding bit 0. The receiving entity will perform the carriage return function twice, but this will not result in misoperation as the definition of in clause 6.1.1 is identical to the definition of .
The receiving entity shall remove the final character where the message ends on an octet boundary with as the last character.

So please fix this function and if the latest one is 0×00, replace it with 0X1A (Carriage Return)

This is example of APDU for Send USSD Proactive Command on javacard with USSD string *113#.
The code for sending is very simple:

ProHdlr.init((byte)PRO_CMD_SEND_USSD,(byte)0x00,(byte)DEV_ID_NETWORK);
ProHdlr.appendTLV(TAG_ALPHA_IDENTIFIER, USSD_TITLE_EN,(short)0x00,(short)USSD_TITLE_EN.length);
ProHdlr.appendTLV((byte)(TAG_USSD_STRING), USSDBuffer, (short)0x01, (short)f);
ProHdlr.send();

Where ProHdlr is ProactiveHandler, USSD_TITLE_EN is static byte for alpha identifier to be used
during sending the USSD request, USSDBuffer is buffer for USSD string, f is length of data of USSD string.

The most important thing here is that USSD string consist of:
1. Data Encoding Scheme (which most probably use 0x0F)
2. USSD string itself, which must be 7-bit encoded just like normal 7bit SMS.

E.g we have assigned below *113#

byte lenUSSDBuffer = (byte)0x01;
USSDBuffer[(byte)lenUSSDBuffer++] = (byte)0x0F; // Data encoding scheme
USSDBuffer[(byte)lenUSSDBuffer++] = (byte)'*';
USSDBuffer[(byte)lenUSSDBuffer++] = (byte)'1';
USSDBuffer[(byte)lenUSSDBuffer++] = (byte)'1';
USSDBuffer[(byte)lenUSSDBuffer++] = (byte)'3';
USSDBuffer[(byte)lenUSSDBuffer] = (byte)'#';

*113# will become 0xAA 0×58 0x6C 0×36 0×02 once we code it in 7-bit encoding rule (see TS 23.038).
0x0F is encoding scheme which follow standard encoding scheme for Cell Broadcast (see TS 23.038).
0x0F means GSM 7 bit default alphabet – language unspecified.

Good luck with your USSD !

Menambahkan tulisan mas Adie ini, saya justru kepikiran Allah sedang mulai melakukan skenario mencabuti ilmu2 Quran pelan2 dengan mewafatkan orang2 yang mukmin diantara kita….

Kebohongan yang merajalela setelah gempa
By Adie Jordan

Sun at 8:32pm
Beberapa saat setelah gempa Sumbar terjadi, banyak status di
Facebook yang mengkait-kaitkan gempa ini dengan ayat Alqur’an 17.16
yang berbunyi :

“Dan jika Kami hendak membinasakan suatu negeri, maka Kami
perintahkan kepada orang-orang yang hidup mewah di negeri itu (supaya
menta’ati Allah) tetapi mereka melakukan kedurhakaan dalam negeri itu,
maka sudah sepantasnya berlaku terhadapnya perkataan (ketentuan Kami),
kemudian Kami hancurkan negeri itu sehancur-hancurnya.”

Tentu saja ini membuat gerah sebahagian korban yang tertimpa
musibah ini, mereka merasa sebagai “korban yang dihakimi”.

Kenapa sampai ayat ini dijadikan vonis bahwa mereka adalah
orang-orang “berhidup mewah yang melakukan kedurhakaan kepada
Allah”.??

Hal ini sangat menggelitik bagi kami untuk mencari dari gempa yang
terjadi di Aceh 26 Desember 2004. Kenapa tidak dikaitkan dengan
satupun ayat Al-Qur’an? Berikut rekam kejadian gempa Aceh :

Gempa terjadi pada waktu 7:58:53 WIB. Pusat gempa terletak pada
bujur 3.316° N 95.854° EKoordinat: 3.316° N 95.854° E kurang lebih 160
km sebelah barat Aceh sedalam 10 kilometer. Gempa ini berkekuatan 9,3
menurut skala Richter dan dengan ini merupakan gempa bumi terdahsyat
dalam kurun waktu 40 tahun terakhir ini yang menghantam Asia Tenggarai

http://id.wikipedia.org/wiki/Gempa_bumi_Samudra_Hindia_2004

Lalu apa “Ramalan” Al Qur’an pada waktu kejadian tersebut..??

[7:58] Dan tanah yang baik, tanaman-tanamannya tumbuh subur dengan
seizin Allah; dan tanah yang tidak subur, tanaman-tanamannya hanya
tumbuh merana. Demikianlah Kami mengulangi tanda-tanda kebesaran
(Kami) bagi orang-orang yang bersyukur.

Sebenarnya yang menjadi masalah adalah dalam kaitan Ayat 17.16
yang dihubungkan, “Ahli-ahli tafsir” dadakan ini seolah olah
mengaitkan bahwa korban gempa di Padang sama dengan orang yang
dimaksud dalam Ayat 17.16 tersebut.

Apakah orang2 yang menghakimi tersebut pernah ke kota Padang atau
tinggal di kota Padang.?

Di Sumatera Barat secara umum dan Padang khususnya dalam 5 tahun
belakangan ini sangat bersungguh-sungguh untuk menjadi kota yang
bertaqwa kepada Allah (setidaknya itu dari pandangan saya selama
bekerja disana). Setiap pagi ada gerakan Subuh Mubarakah dan di setiap
Masjid lantunan Asma’ul Husna terdengar hampir setiap pagi.

Lihatlah para pelajar di kota padang, selalu menggunakan busana
muslim di setiap hari dan rata-rata mereka hapal dengan Asma’ul Husna.

http://www.padang.go.id/v2/content/view/1646/1/

Apakah ini negeri yang “Durhaka kepada Allah” itu.?

Kita seharusnya sepakat bahwa negeri itu sedang disayang Allah
karena mereka sedang mendekatkan diri kepada Nya sesuai dengan Firman
Allah

[2:214] Apakah kamu mengira bahwa kamu akan masuk syurga, padahal
belum datang kepadamu (cobaan) sebagaimana halnya orang-orang
terdahulu sebelum kamu? Mereka ditimpa oleh malapetaka dan
kesengsaraan, serta digoncangkan (dengan bermacam-macam cobaan)
sehingga berkatalah Rasul dan orang-orang yang beriman bersamanya:
“Bilakah datangnya pertolongan Allah?” Ingatlah, sesungguhnya
pertolongan Allah itu amat dekat.

Maka dari itu, agar teman2 dapat menyebarkan pesan ini kepada
teman lain di Facebok atau dimanapun. Marilah kita sama-sama
bertaubat, karena bisa jadi bukan mereka yang dihukum, tapi kita yang
sedang diberi kesempatan kedua.

[53:32] (Yaitu) orang-orang yang menjauhi dosa-dosa besar dan
perbuatan keji yang selain dari kesalahan-kesalahan kecil.
Sesungguhnya Tuhanmu maha luas ampunanNya. Dan Dia lebih mengetahui
(tentang keadaan)mu ketika Dia menjadikan kamu dari tanah dan ketika
kamu masih janin dalam perut ibumu; maka janganlah kamu mengatakan
dirimu suci. Dialah yang paling mengetahui tentang orang yang
bertakwa.

Wallahu’alam

============================================================

|—[:] COMMAND DETAILS
|—[:] Command Number: 01
|—[:] Command Type: Set Up Call
|—[:] Command Qualifier: Set up call, but only if not currently busy on another call, with redial
|—[:] DEVICE IDENTITIES
|—[:] Source Device identity: UICC
|—[:] Destination Device identity: Network
|—[:] ALPHA IDENTIFIER
|—[:] Alpha identifier details Calling…
|—[:] ADDRESS
|—[:] Type-OF-Number: International number
|—[:] Numbering-Plan-Identification: ISDN/telephony numbering plan (‘The internationalpublic telecommunication numbering plan’ and E.163 recommandation)
|—[:] Dialling number: 66 15 55 67 81 11
|—[:] Card Status: 90 00
\—[:] Raw data: D01E010301100102028183050A43616C6C696E672E2E2E0607916651557618119000
============================================================

If you already register for Call Control by SIM, then below envelope data will be available to
your SIM java applet first

============================================================
[+] APDU Command: ENVELOPE – Call control
|—[:] DEVICE IDENTITIES
|—[:] Source Device identity: Terminal
|—[:] Destination Device identity: UICC
|—[:] ADDRESS
|—[:] Type-OF-Number: International number
|—[:] Numbering-Plan-Identification: ISDN/telephony numbering plan (‘The internationalpublic telecommunication numbering plan’ and E.163 recommandation)
|—[:] Dialling number: 66 15 55 67 81 11
|—[:] CAPABILITY CONFIGURATION PARAMETERS
|—[:] 06 60 04 02 00 05 81
|—[:] LOCATION INFORMATION
|—[:] Mobile Country & Network Codes(MCC & MNC): XX XX XX
|—[:] Location Area Code(LAC): 01 96
|—[:] Cell Identity Value(Cell ID): 13 A9
|—[:] Header: 80C2000021
\—[:] Data: D41F020282810607916651557618110707066004020005811307XXXXXX019613A9
============================================================

Sorry I remove MCC/MNC information

Once it’s allowed by SIM (by Call Control by SIM envelope command), then terminal/handset
will start calling

============================================================
[+] APDU Command: TERMINAL RESPONSE
|—[:] COMMAND DETAILS
|—[:] Command Number: 01
|—[:] Command Type: Set Up Call
|—[:] Command Qualifier: Set up call, but only if not currently busy on another call, with redial
|—[:] DEVICE IDENTITIES
|—[:] Source Device identity: Terminal
|—[:] Destination Device identity: UICC
|—[:] RESULT
|—[:] RESULT DETAILS : Command performed successfully
|—[:] Header: 801400000C
\—[:] Data: 010301100102028281030100
============================================================

Once connected and you register for Call Connected Event, below event will be available to your card applet
============================================================
[+] APDU Command: ENVELOPE – Event download
|—[:] EVENT LIST
|—[:] Event list detail: Call connected
|—[:] DEVICE IDENTITIES
|—[:] Source Device identity: Network
|—[:] Destination Device identity: UICC
|—[:] TRANSACTION IDENTIFIER
|—[:] List :
|—[:] Transaction Identifier 1
|—[:] TI Flag is true TI Value : 268435448
|—[:] Header: 80C200000C
\—[:] Data: D60A190101020283811C0180
============================================================

Once finished and call disconnected, below event will be available
============================================================
[+] APDU Command: ENVELOPE – Event download
|—[:] EVENT LIST
|—[:] Event list detail: Call disconnected
|—[:] DEVICE IDENTITIES
|—[:] Source Device identity: Terminal
|—[:] Destination Device identity: UICC
|—[:] TRANSACTION IDENTIFIER
|—[:] List :
|—[:] Transaction Identifier 1
|—[:] TI Flag is false TI Value : 0
|—[:] CAUSE E0 90
|—[:] Header: 80C2000010
\—[:] Data: D60E190102020282811C01001A02E090
============================================================

Handset Response to UICC:
——————————————————————————–
[+] APDU Command
|—[:] COMMAND DETAILS
|—[:] Command Number: 01
|—[:] Command Type: Provide Local Information
|—[:] Command Qualifier: IMEI of the terminal
|—[:] DEVICE IDENTITIES
|—[:] Source Device identity: Terminal
|—[:] Destination Device identity: UICC
|—[:] RESULT
|—[:] RESULT DETAILS : Command performed successfully
|—[:] IMEI: 3A 45 02 03 03 18 38 00
|—[:] Header: 8014000016
\—[:] Data: 81030126010202828103010014083A4502030318xxxx

We get IMEI 3A 45 02 03 03 18 xx xx, sorry I override 2 latest byte

[+] APDU Command: TERMINAL PROFILE
|—[:] First byte (Download)
|—[:] *Call Control send by NAA
|—[:] *Reserved by 3GPP (USSD string data object support in Call Control by USIM)
|—[:] *Timer expiration
|—[:] *Reserved by 3GPP (SMS-PP data download)
|—[:] *Menu Selection
|—[:] *Reserved by 3GPP (Cell Broadcast Data Download)
|—[:] *Reserved by 3GPP (SMS-PP data download)
|—[:] *Profile Download
|—[:] Second byte (Other)
|—[:] *Display Text
|—[:] *UCS2 Display supported
|—[:] *UCS2 Entry supported
|—[:] *Call Control by NAA
|—[:] *Reserved by 3GPP (MO Short message control)
|—[:] *Call Control by NAA
|—[:] *Call Control by NAA
|—[:] *Command Result
|—[:] Third byte (Proactive UICC)
|—[:] *Proactive UICC : REFRESH
|—[:] *Proactive UICC : POLLING OFF
|—[:] *Proactive UICC : POLL INTERVAL
|—[:] *Proactive UICC : PLAY TONE
|—[:] *Proactive UICC : MORE TIME
|—[:] *Proactive UICC : GET INPUT
|—[:] *Proactive UICC : GET INKEY
|—[:] *Proactive UICC : DISPLAY TEXT
|—[:] Fourth byte (Proactive UICC)
|—[:] *Proactive UICC : PROVIDE LOCAL INFORMATION (NMR)
|—[:] *Proactive UICC : PROVIDE LOCAL INFORMATION (MCC, MNC, LAC, Cell ID & IMEI)
|—[:] *Proactive UICC : SET UP MENU
|—[:] *Proactive UICC : SET UP CALL
|—[:] *Proactive UICC : Reserved by 3GPP (SEND USSD)
|—[:] *Proactive UICC : Reserved by 3GPP (SEND SS)
|—[:] *Proactive UICC : Reserved by 3GPP (SEND SHORT MESSAGE with 3GPP-SMS-TPDU)
|—[:] *Proactive UICC : SELECT ITEM
|—[:] Fifth byte (Event driven information)
|—[:] *Event : Idle screen available
|—[:] *Event : User activity
|—[:] *Event : Location status
|—[:] *Event : Call disconnected
|—[:] *Event : Call connected
|—[:] *Event : MT CALL
|—[:] *Proactive UICC : SET UP EVENT LIST
|—[:] Sixth byte (Event driven information extensions)
|—[:] *Event : Channel status
|—[:] *Event : Data available
|—[:] *Event : Browser termination
|—[:] *Event : Language selection
|—[:] Eighth byte (Proactive UICC)
|—[:] *Call Control by NAA
|—[:] *SETUP CALL
|—[:] *SET UP IDLE MODE TEXT
|—[:] *GET INKEY
|—[:] *Proactive UICC : PROVIDE LOCAL INFORMATION(date, time and time zone)
|—[:] *Proactive UICC : TIMER MANAGEMENT (get current value)
|—[:] *Proactive UICC : TIMER MANAGEMENT(start, stop)
|—[:] Ninth byte
|—[:] *Proactive UICC : LAUNCH BROWSER
|—[:] *Proactive UICC : LANGUAGE NOTIFICATION
|—[:] *Proactive UICC : Reserved by 3 GPP (PROVIDE LOCAL INFORMATION, Timing Advance)
|—[:] *Proactive UICC : PROVIDE LOCAL INFORMATION (language)
|—[:] *Proactive UICC : PROVIDE LOCAL INFORMATION (NMR)
|—[:] *SEND DTMF command
|—[:] *DISPLAY TEXT
|—[:] Twelfth byte
|—[:] *Proactive UICC : GET CHANNEL STATUS
|—[:] *Proactive UICC : SEND DATA
|—[:] *Proactive UICC : RECEIVE DATA
|—[:] *Proactive UICC : CLOSE CHANNEL
|—[:] *Proactive UICC : OPEN CHANNEL
|—[:] Thirteenth byte
|—[:] *GPRS
|—[:] *Number of channels supported by terminal 7
|—[:] Fourteenth byte (Screen height)
|—[:] *Screen sizing Parameters supported
|—[:] *Number of characters supported down the terminal 5
|—[:] Fifteenth byte (Screen width)
|—[:] *Number of characters supported across the terminal display : 15
|—[:] Seventeenth byte
|—[:] *UDP
|—[:] *TCP
|—[:] Twenty-first byte (Extented Launch Browser Capability)
|—[:] *CHTML
|—[:] *HTML
|—[:] *XHTML
|—[:] *WML
|—[:] Additional Profile Data In: 00
|—[:] Header: 8010000017
\—[:] Data: FFFFFFFF7F0F00DF7F00001FE2850F00030000000F0000

Hi Javacard developer, this is for your reference on Launch browser APDU

|—[:] COMMAND DETAILS
|—[:] Command Number: 01
|—[:] Command Type: Launch browser
|—[:] Command Qualifier: Launch browser if not already launched
|—[:] DEVICE IDENTITIES
|—[:] Source Device identity: UICC
|—[:] Destination Device identity: Display
|—[:] URL: 78 78 78 78 78 78 78 2e 78 78 2e 78 78
|—[:] Card Status: 90 00
\—[:] Raw data: D018010301150002028102310D787878787878782e78782e78789000

URL is 78 78 78 78 78 78 78 2e 78 78 2e 78 78 (xxxxxxx.xx.xx)

Salah satunya adalah apartemen saya, dari harga 110rb AED/tahun
bisa dinego jadi 65rb AED/tahun.

Cuman, konon kabarnya tunjangan rumah kita-kita pun akan segera disesuaikan
dengan kondisi pasar sekarang.

Jadi apakah bisa saving dari tunjangan rumah? Tidak tau

Lalu apa itu “Du”? Coba lihat-lihat websitenya di www.du.ae agar lebih mengerti

Anda bekerja di perusahaan yang punya nama perusahaan lebih singkat daripada saya?

1. Tunjangan rumah
Fungsi tunjangan rumah adalah untuk membayar biaya sewa rumah.
Pada saat awal bergabung, maka kita akan diberikan X kali lipat dari tunjangan rumah bulanan kita
untuk digunakan membayar sewa rumah. Setelah itu, tunjangan diberikan bulanan.

Tergantung memanfaatkan tunjangan rumah ini dan kondisi pasar properti, maka kita bisa nabung atau nombok dari uang
tunjangan rumah ini.

Besarnya tergantung grade/level kita. Tapi lumayan OK lah daripada gak dikasih.

2. Tunjangan transportasi
Diberikan agar pekerja memiliki ongkos untuk pulang pergi dari kantor. Di Dubai tunjangan ini cukup untuk menyicil
pembelian mobil yang harganya memang relatif murah di Dubai.

Besarnya tergantung grade/level kita. Tapi lumayan OK lah daripada gak dikasih.

3. Tunjangan Relokasi
Diberikan berupa 20ft container untuk mengangkut barang2 dari tempat asal kita ke Dubai. Tunjangan ini tidak saya pakai
karena saya gak punya barang apa2 untuk diangkut ke Dubai dari Indonesia/Singapura. Tunjangan ini tidak bisa diuangkan
jadi kalau tidak dipakai ya hangus.

4. Tunjangan Pendidikan anak
Diberikan untuk anak kita yang berumur 4-18 tahun. Besarnya 12rb AED/year. Jumlah yang kecil di Dubai ini, namun OK lah
daripada gak dikasih

5. Tunjangan Telepon
Ya buat nelpon. Jatah saya relatif kecil tapi sejauh ini, tagihan telepon saya selalu 0, karena telepon internasional
dapat diskon 50% dan rate-nya khusus pegawai Du. Sementara telepon ke telepon rumah di Dubai juga gratis.

6. Tunjangan tiket pesawat PP ke negara asal
Patokannya tiket ekonomi menggunakan airline Emirates dengan harga tiket ekonomi termahal untuk setiap anggota keluarga.
Jadi bisa disiasati untuk menggunakan airline yang lebih murah atau ambil tiket yang lebih murah jadi bisa disimpan sisanya.

7. Tunjangan kesehatan
Berupa asuransi kesehatan, intinya biar berobat gratis untuk seluruh anggota keluarga. Asuransi meliputi seluruh negara kecuali
US/Canada. Tapi di sini ada American Hospital, jadi sama saja seperti berobat di US.

8. End of Service Benefit
Jadi suatu ketika kita mengundurkan diri, kita akan mendapatkan pesangon yang besarnya tergantung berapa lama kita sudah bekerja
di perusahaan. Minimal dihitung 21 hari kerja relatif terhadap gaji pokok bulanan

9. Jatah Cuti
– Normal Cuti: 30 Hari Kerja setaun atau 1,5 Bulan
– Cuti Haji : Kalau haji dapat cuti tambahan khusus untuk haji
– Compassionate Leave: Kalau ada famili yang meninggal maka dapat cuti 7 hari + tiket PP untuk balik ke rumah

10. Gaji Pokok + Bonus
Ya kalau gak digaji pokok, gimana bisa makan sehari2.

The answer is: SIMCard, a smartcard that personalized for telecommunication purpose. Yes, as we know physically GSM operator sell a SIMCard,  the rest are services upon it including SMS, call service, MMS, Voice Mailbox  and many things.

The next question, since SIMcard will be hold by customer inside their mobile phone, how could GSM operator manage the SIMcard remotely?  Things like managing javacard applet & filesystem inside the SIMCard. The answer is by OTA (over the air) using SMS and or CAT-TP bearer (GPRS based), but we will focus on the one using SMS (short message protocol).

GSM 03.48 define RFM and also RAM as standard mechanism for doing remote file management (RFM) and remote applet management. We are now focus on RFM, please note the implementation for this feature is vendor specific.

OK, let me give an example as our case study, one day we as operator need to do OTA campaign for updating file EF_SMSP (7F10/6F42) since the address of SMSC is now changed. As we know, based on 3GPP TS 31.102 document, EF_SMSP contains SMSC information that will be used by mobile phone for sending mobile originated  (MO) SMS. For example the content of file EF_SMSP (7F10/6F42) is now

534D532043454E545245FFFFE1FFFFFFFFFFFFFFFFFFFFFFFF07915892020430F1FFFFFFFF0000A9

You can refer to TS 31.102 document for the structure of EF_SMSP, but simply said the SMSC address defined here is: 85292040031. Now, operator want to change it to 85292040034 over the air.

So, technically we need to:
1. Prepare APDU for updating the file
2. Construct appropriate 03.48 + 03.40 APDU command
3. Send it over the air to customer

The result is, the file on customer SIMcard is updated silenty without user intervention.

534D532043454E545245FFFFE1FFFFFFFFFFFFFFFFFFFFFFFF07915892020430F1FFFFFFFF0000A9

to

534D532043454E545245FFFFE1FFFFFFFFFFFFFFFFFFFFFFFF07915892020430F4FFFFFFFF0000A9

is by executing these 4 APDU(s):

A0A40000023F00
A0A40000027F10
A0A40000026F42
A0DC010428534D532043454E545245FFFFE1FFFFFFFFFFFFFFFFFFFFFFFF07915892020430F4FFFFFFFF0000A9

Details of each APDU is:

1) APDU for select 3F00 ==> A0 A4 00 00 02 3F 00
2) APDU for select DF 7F10 under MF 3F00 ==> A0 A4 00 00 02 7F 10
3) APDU to select EF 6F42 under DF 7F10 ==> A0 A4 00 00 02 6F 42
4) APDU to update record 1 of EF 6F42 to 534D532043454E545245FFFFE1FFFFFFFFFFFFFFFFFFFFFFFF07915892020430F4FFFFFFFF0000A9:

A0 DC 01 04 28 534D532043454E545245FFFFE1FFFFFFFFFFFFFFFFFFFFFFFF07915892020430F4FFFFFFFF0000A9

Let say,
1. the TAR is B0 00 10, please note this value is very specific to card vendor.
2. MSL is 0×25 means content must be encrypted and use CHryptographic CHecksum
3. Keyset to use is keyset 2 with algo Triple DES using outer CBC-Mode with 2 different keys and

KiC: 00112233445566778899AABBCCDDEEFF
KiD: 00112233445566778899AABBCCDDEEFF

Then we can generate APDU SMS-PP Download like this:

A0 C2 00 00 7B D1 79 02 02 83 81 06 04 00 21 43
F5 0B 6D 63 05 00 99 40 F1 7F F6 01 01 01 01 01
01 00 5D 02 70 00 00 58 15 06 01 25 25 B0 00 10
25 4E 56 31 DF D0 4D 77 DC 9C 64 90 30 E6 E8 97
DF 57 49 4B FC 45 11 71 56 2B 5E D3 FF C0 11 AA
62 CA 46 B6 4A 51 B0 A8 52 B3 CC 9F D0 6B 0D 95
C0 E8 DB E7 BF 44 25 39 67 90 B6 E2 22 BE C3 3F
EF 5B 35 2D 9D F7 97 22 15 08 67 F4 AA 29 A5 73
00

Next step is send this APDU over the air using SMS and the file inside SIMCard will be updated without user intervention.

Good luck