Differences between current version and revision by previous author of ShortMessageService.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Wednesday, March 16, 2005 11:43:39 am | by CraigBox | |
| Older page: | version 1 | Last edited on Saturday, February 14, 2004 9:59:05 am | by CraigMckenna | Revert |
@@ -1,9 +1,11 @@
ShortMessageService ([SMS]) is the transmission of short text messages to and from a mobile phone, fax machine and/or IP address. Messages must be no longer than 160 alpha-numeric characters and contain no images or graphics.
-Once a message is sent, it is received by a ShortMessageServiceCenter
([
SMSC]
), which must then get it to the appropriate mobile device.
+Once a message is sent, it is received by a ShortMessageService Center
(SMSC), which must then get it to the appropriate mobile device.
-To do this, the [
SMSC]
sends a [SMS] Request to the home location register (HLR) to find the roaming customer. Once the HLR receives the request, it will respond to the [
SMSC]
with the subscriber's status: 1) inactive or active 2) where subscriber is roaming.
+To do this, the SMSC sends a [SMS] Request to the home location register (HLR) to find the roaming customer. Once the HLR receives the request, it will respond to the SMSC with the subscriber's status: 1) inactive or active 2) where subscriber is roaming.
-If the response is "inactive", then the [
SMSC]
will hold onto the message for a period of time. When the subscriber accesses his device, the HLR sends a [SMS] Notification to the [
SMSC]
, and the [
SMSC]
will attempt delivery.
+If the response is "inactive", then the SMSC will hold onto the message for a period of time. When the subscriber accesses his device, the HLR sends a [SMS] Notification to the SMSC, and the SMSC will attempt delivery.
+
+Compare [MMS]
.
