轉自：http://www.gsmworld.it/frame.asp?URL=http://www.gsmworld.it/smspdu_pid.htm
The TP-Protocol-Identifier parameterconsists of one octet, and the bits in the octet are used as follows: The MSwill interpret reserved or unsupported values as the value 00000000 but shallstore them exactly as received. The SC may reject messages with aTP-Protocol-Identifier containing a reserved value or one which is notsupported.
|
Bit 7 |
Bit 6 |
Usage |
|
0 |
0 |
Assigns bits 0..5 as defined below |
|
0 |
1 |
Assigns bits 0..5 as defined below |
|
1 |
0 |
Reserved |
|
1 |
1 |
Assigns bits 0..5 for SC specific use |
In case where bits 7 and 6 both are 0:
|
Bit 5 |
Description |
|
0 |
no interworking, but SME-to-SME protocol |
|
1 |
telematic interworking |
In the case of telematic interworking, thefollowing five bit patterns in bits 4..0 are used to indicate types oftelematic devices:
|
Bits 4..0 |
Description |
|
00000 |
implicit - device type is specific to this SC, or can be concluded on the basis of the address |
|
00001 |
telex (or teletex reduced to telex format) |
|
00010 |
group 3 telefax |
|
00011 |
group 4 telefax |
|
00100 |
voice telephone (i.e. conversion to speech) |
|
00101 |
ERMES (European Radio Messaging System) |
|
00110 |
National Paging System (known to the SC) |
|
00111 |
Videotex (T.100/T.101) |
|
01000 |
teletex, carrier unspecified |
|
01001 |
teletex, in PSPDN |
|
01010 |
teletex, in CSPDN |
|
01011 |
teletex, in analog PSTN |
|
01100 |
teletex, in digital ISDN |
|
01101 |
UCI (Universal Computer Interface, ETSI DE/PS 3 01-3) |
|
01110.. |
(reserved, 2 combinations) |
|
10000 |
a message handling facility (known to the SC) |
|
10001 |
any public X.400-based message handling system |
|
10010 |
Internet Electronic Mail |
|
10011.. |
(reserved, 5 combinations) |
|
11000.. |
values specific to each SC, usage based on mutual agreement between the SME and the SC (7 combinations available for each SC) |
|
11111 |
A GSM mobile station. The SC converts the SM from the received TP-DCS to any data coding scheme supported by that MS (e.g. the default). |
If bit 5 has value 1 in an SMS-SUBMIT PDU,it indicates that the SME is a telematic device of a type which is indicated inbits 4..0, and requests the SC to convert the SM into a form suited for thatdevice type. If the destination network is ISDN, the SC must also select theproper service indicators for connecting to a device of that type.
If bit 5 has value 1 in an SMS-DELIVERPDU, it indicates that the SME is a telematic device of a type which isindicated in bits 4..0.
If bit 5 has value 0 in an SMS-DELIVERPDU, the value in bits 4..0 indicates the SM-AL protocol being used between theSME and the MS.
Note that for the straightforward case ofsimple MS-to-SC short message transfer the Protocol Identifier is set to thevalue 0.
In the case where bit 7 = 0, bit 6 = 1,bits 5..0 are used as defined below
|
Bits 5..0 |
Description |
|
000000 |
Short Message Type 0 |
|
000001 |
Replace Short Message Type 1 |
|
000010 |
Replace Short Message Type 2 |
|
000011 |
Replace Short Message Type 3 |
|
000100 |
Replace Short Message Type 4 |
|
000101 |
Replace Short Message Type 5 |
|
000110 |
Replace Short Message Type 6 |
|
000111 |
Replace Short Message Type 7 |
|
001000..011110 |
Reserved |
|
011111 |
Return Call Message |
|
100000..111100 |
Reserved |
|
111101 |
ME Data download |
|
111110 |
ME De-personalization Short MEssage |
|
111111 |
SIM Data download |
A short message type 0 indicates that theME must acknowledge receipt of the short message but may discard its contents.
The Replace Short Message feature isoptional for the ME and the SIM but if implemented it shall be performed asdescriped here.
For MT short messages, on receipt of ashort message from from the SC, the MS shall check to see if the associatedProtocol Identifier contains a Replace Short Message Type code.
If such a code is present, the the MS willcheck the originating address and replace any existing stored message havingthe same Protocol Identifier code and originating address with the new shortmessage and other parameter values. If there is no message to be replaced, theMS shall store the message in the normal way. The MS may also check the SCaddress as well as the Originating Address. However, in a network which hasmultiple SCs, it is possible for a Replace Message type for a SM to be sent viadifferent SCs and so it is recommended that the SC address should not bechecked by the MS unless the application specifically requires such a check.
If a Replace Short Message Type code isnot present then the MS will will store the message in the normal way.
In MO short messages the SC reactssimilarly but only the address of the originating MS or any other source ischecked.
A Return Call Message indicates to the MSto inform the user that a call (e.g. a telephone call) can be established tothe address specified within the TP-OA. The RP-OA contains the address of theSC as usual. The message content (if present) gives displayable information(e.g. the number of waiting voice messages). The message is handled in the sameway as all other messages of the Replace Short Message Types.
The ME De-personalization Short Message isan ME-specific message which instructs the ME to de-personalities the ME (seeGSM 2.22). The TP-DCS shall be set to Uncompressed, Default Alphabet, andMessage Class 1 (Me-specific), which corresponds to a bit coding og 00010001.The TP-UD field contains de-personalization information coded according to GSM02.22. This information shall not be displayed by an ME which supports thescheme. The acknowledgement to this message is a SMS-DELIVER-REPORT for RP-ACKin ehich the TP-User-Data shall be coded according to GSM 02.22.
SIM Data download is a facility wherebythe ME must pass the short message in its entirety including all SMS elementscontained in the SMS deliver to the SIM using the mechanism descriped in GSM11.11. The DCS shall be set to 8 bit message class 2 (either bit coding11110110 or 00010110). The entire user data field is available for SIM Datadownload.
ME Data download is facility whereby theME shall process the short message in its entirety including all SMS elementscontained in the SMS deliver to the ME. The DCS shall be set to message class1. The entire user data field is available for ME data download.