Showing posts with label BIP Server. Show all posts
Showing posts with label BIP Server. Show all posts

Wednesday, February 20, 2008

CLOSE CHANNEL BIP

After OPEN Channel, You should know how to close it. Here are some important things you should be aware.
  1. Command details*
    1. command details tag = '81'
    2. length = '03' (1 byte)
    3. command number 01 - FE (1 byte)
    4. Type of Command ='41' (CLOSE CHANNEL)
    5. Command Qualifier :
      • RFU for BIP Client Mode
      • bit 1
        • 0 : close TCP Connection and go to "TCP in CLOSED state"
        • 1 : close TCP Connection and go to "TCP in LISTEN state"
  2. Device identities*
    1. device identities tag = '82'
    2. Length = '02'
    3. Source Device identity = '81' --> UICC
    4. Destination Device Identity = '21'-'27' --> channel ID (PRE_ID _CHANNEL_BASE='20')
  3. Alpha Identifier
    1. Alpha identifier TAG = '05'
    2. Length = 0
    3. Alpha Identifier (TS 131 102)
  4. Icon Identifier
    1. Icon Identifier Tag
    2. Length = '02'
    3. Icon Qualifier
      1. bit 1, 0 = self explanatory, 1 = non self explanatory
      2. bit 2-8 =0 (RFU)
    4. Icon Identifier (TS 131 102)
  5. Text Attribute
    1. Text Attribute Tag = '50'
    2. Length
    3. Text formatting ( TS 123 040)
  6. Frame Identifier
    1. Frame Identifier Tag
    2. Length = '03'
    3. Identifier of Frame, the value is between '00' - '0F'
You don't need to remember the tag value if you use appendTLV function. All of the tag value are explained briefly in uicc.toolkit.ToolkitConstant library.

note :
* mark means mandatory
Channel indentifier must be valid

OPEN CHANNEL BIP TCP Server Mode

I have already posted BIP TCP client mode requirement before. Here are my little explanation for TCP Server mode.
  1. Command details*
    1. command details tag = '81'
    2. length = '03' (1 byte)
    3. command number 01 - FE (1 byte)
    4. Type of Command ='40' (OPEN CHANNEL)
    5. Command Qualifier : RFU
  2. Device identities*
    1. device identities tag = '82'
    2. Length = '02'
    3. Source Device identity = '81' --> UICC
    4. Destination Device Identity = '82' --> Terminal
  3. Alpha Identifier
    1. Alpha identifier TAG = '05'
    2. Length = 0
    3. Alpha Identifier (TS 131 102)
  4. Icon Identifier
    1. Icon Identifier Tag
    2. Length = '02'
    3. Icon Qualifier
      1. bit 1, 0 = self explanatory, 1 = non self explanatory
      2. bit 2-8 =0 (RFU)
    4. Icon Identifier (TS 131 102)
  5. Buffer Size*
    1. Buffer Size Tag = '39'
    2. Length = '02'
    3. Byte 3-4 = Buffer size, for example 1000 bytes = 03E8
  6. UICC/ Terminal Interface
    1. UICC/ Terminal Interface level tag = '3C'
    2. Length = '03'
    3. Transport Protocol Type = '03' (TCP,UICC in server mode)
    4. Port Number(2 bytes) = '0DBC' (3516)
  7. Text Attribute
    1. Text Attribute Tag = '50'
    2. Length
    3. Text formatting ( TS 123 040)
  8. Frame Identifier
    1. Frame Identifier Tag
    2. Length = '03'
    3. Identifier of Frame, the value is between '00' - '0F'
You don't need to remember the tag value if you use appendTLV function. All of the tag value are explained briefly in uicc.toolkit.ToolkitConstant library.

note :
* mark means mandatory