CA2190305A1 - System and method for transmitting a displayable message to a short message entity in more than one data package - Google Patents
System and method for transmitting a displayable message to a short message entity in more than one data packageInfo
- Publication number
- CA2190305A1 CA2190305A1 CA002190305A CA2190305A CA2190305A1 CA 2190305 A1 CA2190305 A1 CA 2190305A1 CA 002190305 A CA002190305 A CA 002190305A CA 2190305 A CA2190305 A CA 2190305A CA 2190305 A1 CA2190305 A1 CA 2190305A1
- Authority
- CA
- Canada
- Prior art keywords
- message
- displayable
- capacity
- data
- fragment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
- H04W28/14—Flow control between communication endpoints using intermediate storage
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/184—Messaging devices, e.g. message centre
Abstract
A system (100) that is capable of transmitting a displayable message to a short message entity (102, 104, or 105) in more than one data package over a conveying network. The system (100) uses a capacity determiner (206) to determine a capacity of the conveying network for transmitting data. Based on this capacity of the conveying network, a fragmenter (204) divides the displayable message into fragments at an application protocol layer. The size of a fragment does not exceed the capacity of the conveying network. Finally, a packager (208) packages the fragments into data packages. The data packages are operable to be separately transmitted by a short message service over the conveying network. The data packages may include a reference parameter corresponding to the position of the fragment in the displayable message. Further, a reference parameter may indicatethe total size of the displayable message being fragmented and packaged. When all of the fragments of the displayable message are received at the terminating short message entity (102, 104 or 105), a fragment retriever (304) retrieves the fragments.
A message reconstructer (306) reconstructs the displayable message. The displayable message is then passed a disposing device (308). (FIG. 1)
A message reconstructer (306) reconstructs the displayable message. The displayable message is then passed a disposing device (308). (FIG. 1)
Description
21g~305 SYSTEM AND METHOD FOR TRANSMITTING A DISPLAYABLE
MESSAGE BLI ~ ;N SHORT MESSAGE ENTl~IES IN MORE
THAN ONE DATA PACKAGE
Field of the Invention The present invention relates to telecomm--nic~tions systems in general and, more particularly, to a system and method for tr:~n~mitting a displayable message between short message entities.
Back~round of the Invention Some telecommunications service providers, including cellular and 10 paging companies, provide a "short message service" which allows a user to send and receive displayable messages via a "short message entity." For purposes of this specification, a short message entity is a device that is capable of composing or disposing of short messages. Both wirelines and wireless terminals, including cellular telephones and pagers, may function as short message entities. Further,15 short message service includes the capability of conveying a short message from an origin~ting short message entity to one or more terminating short message entities.
For example, current page systems can transmit a displayable message that consists of a telephone number to be called. Some wireless systems can also send alpha-numeric text for display on the screen of a wireless termin~l thus allowing users to 20 send more det~iled messages. Alpha-numeric text can also be sent to computingdevices such as desk and lap-top computers over wireless or wired terminals or devices. Unfortunately, current short message services can only handle displayable messages of limited siæ. However, to compete with the burgeoning electronic mailindustry, telecommunications service providers would like to be able to transmit25 longer "short" messages to termin~ting short messages entities.
The Telecommunications Industry Association ("TIA") has prescribed interim standards (de~ign~sed "IS" concatenated with an identifier) for tr~n~mitting displayable messages to short message entities over various wireless air interfaces and networks. Each interim standard specifies a protocol including operations, 30 parameters, operational messages and procedures for transmitting a displayable message as a single data package. For example, IS-9SA and IS-637 specify protocols for wireless systems that use Code Division Multiple Access ("CDMA") technology. Further, the IS-136 family of standards specify protocols for short message service in Time Division Multiple Access ("TDMA") systems. The IS-91 35 family of standards specifies protocols for short message service in advanced mobile 21~0305 -phone service ("AMPS/NAMPS") systems. Finally, IS-41-C specifies protocols for short message service over inter-system networks. Analogous protocols exist in the paging industry. Unfortunately, each of these standards specifies a maximum length for the displayable message. The standards do not contemplate tran~mi~sion of 5 longer displayable messages.
Typically, an origin~ting short message entity generates a displayable message for transmi~ion to a terrnin~ting short message entity. The displayable message is transmitte~ over a "conveying network" or "pipeline" between these short mess~e çntities The conveying network includes the network elements and air 10 interface traversed by the displayable message. The conveying network may include some sign~ling mechanism such as, for example, Sign~ling System 7 ("SS7"), X.25,Internet Protocol ("IP"), Asynchronous Transfer Mode ("ATM"), or Frame Relay.
Further, the air interface may be digital such as TDMA, CDMA or other digital air interface. Alternatively, the air interface may comprise an analog interface. It is 15 noted that the originating and termin~ting short message entities do all of the processing with the short message service at the application protocol layer. Theintervening conveying network simply acts as a conduit for information between these two end points. Unfortunately, the conveying network can only transmit up to a maximum amount of data or information as a single data pac~age due to, for 20 example, operational standards as described above or specific implementation of portions of the conveying network. The capacity of the conveying network thus limits the size of displayable messages that can be transmitted in a data pack~gç
Developers in the paging indush^y have dabbled with systems that divide a displayable mess~ge into multiple fr~gment~ for tr~n~mi~sion. However, such 25 systems are primitive because there is no method to handle fragments that arereceived out of order, or to provide for rehransmissions to make up for lost fragments. Further, fragmentation of operational messages has been used in lowerlayer operations in wireless networks. However, to adapt this capability for use in hran~mitting displayable messages, wireless service providers would have to install 30 numerous sof~wale and hardware upgrades to existing networks -- an expensive task.
Summary of the Invention An illustrative embodiment of the present invention provides a system that is capable of tran~mitting a displayable message to a termin~hng short mess~gç
entity in more than one data package over a conveying network. A capacity 35 detçrminer ascertains the capacity of the conveying network for transmitting data.
Based on the capacity of the conveying network, a fragmenter divides the ~Q`3U~
displayable message into fragments at an application protocol layer. The siæ of a fragment does not exceed the capacity of the conveying network. Finally, a pac~rpac~ges the fragment~ into data p~c~ges. The data p~r~ges are separately tr~n~mitt~d using a ~ ly defined short mess~ge service over the conveying S network.
Advantageously, in the illustrative embodiment, each data package may include a reference parameter corresponding to the position of the fragment in the displayable message, and a referenced parameter indicating the total size of thedisplayable message being fragmented and pack~ge~l Other reference parameters 10 may be included in the data packages such as a parameter that in-lir~tes the identify of the displayable message to which the fragment corresponds.
Another illustrative embodiment of the present invention provides a system capable of reconstructing a displayable message from multiple data pac~ges tr~n~mitted over a conveying network. The system includes a fragment retriever that 15 obtains from the data package a fragment or a displayable message. The siæ of the fragments is based on the capacity of the conveying network to transmit data. In one embodiment, the fragment retriever further obtains from the data package a reference parameter that in~lic~tes the relative position of the fragment in the displayable message. The fragment retriever further orders the corresponding fragments 20 according to the referenced parameters obtained from the data packages. Once all fragments have been received, determinecl by comparing the cumulative siæ of fragments received against the total size parameter, a message reconstructer assembles the fragments into the displayable message.
Brief Description of the Drawin~s Illustrative embodiments of the present invention are described below in conjunction with the accompanying drawings, in which:
FM. 1 is a block diagram of an illustrative embodiment of the present invention that provides a system for transmitting a displayable message over a conveying network;
FIG. 2 is a block diagram of an illustrative embodiment of a portion of a short message entity for use in composing a displayable message for transmis~ion in the tr~n~mi~sion of FIG. l;
FIG. 3 is a block diagram of an illustrative embodiment of a portion of a short message entity for use in reconstructing a displayable message with the system 35 of FIG. 1:
219030~
FIGS. 4a-4b are flowcharts that illustrate embodiments of the present invention for reconstructing a displayable message tr:ln~mitted in more than one data p~c~ge over a con~eying network; and FM. 5 is a sample operational message flow scenario of an illustrative 5 embodiment of the present invention.
Detailed Des~ tion FIG. 1 is a block diagram of an illustrative embodiment of the present invention. Telecommunications system 100 transmits displayable messages between, for example, short message entities 102, 104, and 105 over a conveying 10 network in more than one data package using a short message service. As shown in FIG. 1, a short message entity may reside in a wireless terminal (e.g., short message entities 104 and 105 which may comprise cellular or mobile telephones, or a pager), a wireline termin~l (e.g., short message entity 102 which may comprise a wireline telephone, facsimile machine or computer) or other ap~r~liate terminal for 15 tr~n~mitting displayable messages.
Telecommunications systems 100 includes serving wireless system 106.
Wireless system 106 includes wireless switching center ("WSC") 108 that routes displayable mess~ges through base stations 110 1 1102 and 1103 to and from wireless terminals such as short message entities 104 and 105. Each base station20 1 lOn services a region 111 n referred to as a "cell." For simplicity, each cell 111 n is depicted as a hexagon. However, the actual shape of a cell 111 n is ~ t~ted by factors such as the terrain and electromagnetic sources. It is noted that each cell 111 n may be further divided into two or more sectors. Each base station 1 lOn includes antennas and radios for commlmiç~ting with wireless terminals. Each base 25 station 1 lOn further includes transmission equipment for communicating with wireless switching center 108.
Short message entity 102 is coupled to wireless switching center 108 through at least two types of paths. First, network 114 couples short msss~ge entity 102 to wireless switching center 108 through an "indirect" path. Network 114 may30 comprise, for example, a network employing SS7, X.25, IP, ATM or frame relay technology. Further, short message entity 102 may be coupled to wireless switching center 108 through a direct path.
In operation, short message entities can transmit displayable messages over telecommunications system 100 in at least two ways. First, short message 35 entities can transmit displaying messages directing to a termin~ting short message entity over telecommunications system 100. Further, short message entities can 21gO30s transmit displayable messages to an intermediate node, such as a message center, in network 114 for storage until such time as the termin~ting short message entity is ready to receive the displayable message. This is referred to as "store and fol~val.l"
tran~mi~siQn of a displayable message.
In direct tr~n~mission~ short message entity 102, for example, generates a displayable message for tr~nsmissiQn to short mes~ ç entity 104. The displayable mess~ç may comprise alpha-numeric characters tran~mitP,d as form~tted (octets) or unform~tted binary bits. The conveying network or pipeline between short mçss~geentity 102 and short message entity 104 comprises network 114, wireless switching center 108 and base station 1101.
As described above, the maximum amount of data or information (e.g., form~tted or unformatted binary bits) that can be tran~mittçd through the conveying network as a single package of data is defined as the "capacity" of the conveying network. Short message entity 102 determines the capacity of the conveying 15 network that is to be used to transmit the displayable message to short message entity 104. Based on this capacity, short message entity 102 divides the displayable mess~ge into fragments that are less in size than that capacity and packages these fragments for tr~nsmi~sion over the conveying network.
Short message entity 104 receives the packages from base station 110 and reconstructs the displayable message. Short message entity 104 then displaysthe displayable message on, for example, a screen. Thus, system 100 can transmit a displayable message to short message entity 104 that exceeds the capacity of theconveying nel~olk and the short message service used to transmit the displayablemessage. The fragmentation and reconstruction of the displayable message can be carried out at the teleservice (application) protocol layer, thus not requiring an expensive modification to components of network 114 or wireless network 106.
Alternatively, telecommunications system 100 can also support store and fOl~ald tr~n~mis~ n of a displayable message. For example, short message entity 105 can transmit a displayable message to short message entity 104. Short30 message entity 105 generates a displayable message for tr~n~mi~ n to short message entity 104. If short message entity 104 is not available, telecommunications system 100 identifies a message center in network 114 or wireless switching center 108 to receive and store the displayable message. Short message entity 105 determines the capacity of the conveying network that is to be used to transmit the 35 displayable message to the message center. Based on this capacity, short message entity 105 divides the displayable message into fragments that are less than that capacity and packages these fragments for tr~n~mission over the conveying network 21903o~
to the mess~ge center.
When short message entity 104is available to receive the message, the meSs~ge center determines the capacity of a conveying nelv~ol~ to be used to carry the displayable mçss~e to short message entity 104. Short message entity 104 5 receives the pac~ges from base station 110 1 and reconstructs the displayable meSs~ge Short message entity 104 then displays the displayable message on, for example, a screen. It is noted that in both direct and store and fol ~ald techniques, network 114 may include nodes that pelrul~l~ the functions of short message entities 102, 104, and 105. For example, these functions may be ~lro~",ed in a messag~
10 center, a home location register, a wireless switching center or other a~r~,iate network node.
It is noted that short message entities 104 and 105 are both shown for convenience in wireless system 106. It is understood that short message entities 104 and 105 may communicate displayable messages over telecommunic~tions system 15 100 even when short message entities 104 and 105 are not located in the same wireless system or are not using the same wireless switching center.
Example In a cellular system using SS7 as the inter-system carriage protocol, the message package capacity is limited to 272 octets. A short message delivery 20 operation, designated "SMDPP," can therefore carry only 272 octets of information.
A con.~iderable portion of this is used for "overhead" information, such as addressing and other parameters, some that are mandatory and some that are optional. The size of this overhead governs how much will remain to carry the displayable message in the data package. In an SS7 network, the component of the SMDPP operation that 25 transmits the displayable message is referred to as "bearer data."
In a typical implementation, the overhead information may require 92 octets, leaving 180 octets available for tr~n~mit~;ng the displayable mçss~ge asbearer data. According to the illustrative embodiment, for displayable messages that exceed 180 octets, the composite displayable message is broken into fragments of30 180 octets or less and tr~n~mitte-~ with separate SMDPP operations.
If a serving wireless ~witching center ("WSC") could only handle 100 octets, then the size of the fragments is further limited. Considering the 100 octet pipe capacity imposed by the serving WSC, at least three SMDPP operations would be needed to carry a displayable message with between 200 and 300 octets of data.
35 Each SMDPP operation can carry different amounts of data so long as no SMDPP
operation exceeds the 100 octet pipe capacity defined by the WSC. ~ltçrn~tively, all 21gO3~S
but one SMDPP operation can carry the data equal to the capacity while the last SMDPP operation carries data that is less than the capacity.
If any one of the fragments does not arrive at the termin~ting short meSs~ge entity, the resulting autom~tic negative acknowledgment that already exists 5 as part of the existing standards for single data p~c~ge short message service would in~tig~te the origin~ting short message entity to retransmit that particular fra~nçnt The integrity of each short message service delivery would also be guaranteed bylower layer checks (e.g., CRC, etc.).
For clarity, FIGS. 2 and 3, described below, only show cilcuilly for 10 tr~n~mitting a displayable message in one direction. Thus, FIG. 2 illustratesCil~;uill,y that is used to compose a displayable message for tr~n~mi~sion. Similarly, FIG. 3 illustrates circuilly that is used to reconstruct a displayable message. It should be understood that short message entity 102 may included circuitry similar to FIG. 3 and that short message entity 104 may comprise cilcuilly similar to FIG. 2.
15 Further, for purposes of this specification, a short message entity that is used to compose a displayable message is referred to as an "origin~ting short message entity." Similarly, a short message entity that is used to reconstruct a displayable message is referred to as a "terminating short message entity."
FIG. 2 is a block diagram of an embodiment of an ori~in~ting short 20 message entity for use in telecommunications network 100 of FIG. 1. Originating short message entity 102 processes displayable messages for tr~n~mi~sion to a termin~ting short message entity. Originating short message entity 102 includes message composer 200. Message composer 200 provides displayable messages to message buffer 202. Message buffer 202 and capacity determiner provides inputs to 25 fragmenter 204. Fragmenter 204 provides an output to package 208.
In operation, originating short message entity 102 divides a displayable message entered with message composer 200 into fragments for tr~nimi~sil~n over a conveying network to a termin~ting short message entity. Capacity determin~tion operation 206 determines the capacity for the virtual. As described in more detail 30 below with respect to FIG. 5, capacity determiner 206 may determine the capacity of the conveying network in part based on a value of a parameter that is included in an autonomous registration process for a wireless terminal that roams into a regioncovered by wireless switching center 108. Originating short message entity 102 may use data on limitations of other aspected of the conveying network to set the size of 35 the fragments. Fragmentation operation 204 divides the displayable message into fragments such that the fragments do not exceed the capacity of the conveying network. By thus dynamically sizing the data packages, the illustrative embodiment of the present invention advantageously allows displayable messages to be sent with increased usage of network resources. P~c~ging operation 208 places the fragments in data p~a~g-es for tran~mi~ion.
In ad~lition to the fragmçnt~, the data pac~ges may include other 5 ltr~nce p~ulletel~. For example, the data pa~ges may include a parameter, e.g., SMS_Fragment_Number, in-lic~ting the position of each fragment within the displayable mess~ge Additionally, the data p~ k~ges may each include an indicia of the size of the displayable message, e.g., SMS_Total_Payload_Siæ. Finally, each data p~c~a~ may include a parameter, e.g., Msg_ID, that identifies the displayable 10 message to which the data package belongs. It is noted that the capacity, as defined previously, is the siæ of the largest data package that the virtual circuit can transmit.
Thus, the capacity of the circuit includes space for "overhead" information used in tran~mitting data that is included with each package of data. This overhead may include, for example, the short message service protocol as well as the parameters 15 SMS_Fragment_Number, SMS_Total_Payload_Size, and Msg_ID.
While fragmçnter 204 may use a parameter co~ s~onding to the relative position of the fragment, the sequence of the fragments may be preserved in other ways. Fragmenter 204 may, for example, pass each fragment to package 208 and await the corresponding automatic acknowledgment before opelaling on the next 20 fragment thereby passing the fragments to the packager in the order corresponding to the displayable message.
As previously noted, the conveying network between the short meSsage entity 102 and short message entity 104 mererly transmits each data package according to existing protocols. No processing of the contents of the data protocols 25 occurs in the conveying network thus allowing implementation without requiring ~ignifi~nt modifications to sof~w~e or hardware or both.
FIG. 3 is a block diagrarn of a portion of a termin~ting short message entity for use in telecommunications system 100 of FM. 1. Terminating short message entity 104 includes buffer 302. Buffer 302 provides an input to fragment30 retriever 304. Fragment retriever 304 provides an input to message reconstructer 306. Finally, message reconstructer 306 drives disposing device 308 which may, for example, comprise a display for displaying a displayable message to a user.
In operation, buffer 302 receives more than one data package relating to a displayable message tr~nsmitted from origin~ting short message entity 102 to 35 termin~ting short message entity 104. Buffer 302 stores the data p~ck~ges.
Fragment retriever 304 retrieves a fragment of a displayable message and a reference parameter from each data package that indicates the position of the fragment relative 219~305 to the other fragments in the displayable message. Fragment retriever 304 further orders the fragments according to the reference parameters retrieved from the data p~c~g~s Message reconstructer 306 reconstructs the displayable message and provides the displayable message to disposing device 308. It is noted that fragment 5 retriever 304 may process data packages corresponding to different displayable messages in parallel if a parameter such as Msg_ID is used.
FM. 4a is a flowchart illustrating an embodiment of the present invention. The method begins at block 402. At block 404 the method retrieves a data ~~c~ At block 406, the method determin~s whether the data package has 10 already been received by, for example, checking the SMS_Fragment_Number and the Msg_ID parameters against a list of received data packages. If the answer is yes, the data package has been previously received and the method returns to block 404 to retrieve another data package. Thus, terminating short message entity 104 canreject duplicate fragments that may have been received due to retr~n~miisions. A15 retr~n~mi~sion by the originating short message entity may occur, for example, because an acknowledgment to an earlier tr~nimi~sion was not receiveed in time, e.g., prior to expiration of a timer at the originating short message entity.
If, however, the answer at block 406 is no, then the data package has not been previously received. At block 408, the fragment is retrieved from the data 20 package and stored. Receipt of the fragment may be recorded by, for example, ~;cordillg the parameters SMS Fragment Number and Msg_ID for the data p~cl~ge At block 410, the method determines whether all fragments corresponding to the displayable message have been retrieved. The parameter SMS_Total_Payload Size included in at least one data package may be used in 25 determining whether all fragments have been retrieved. If not all fragments have been retrieved, the method returns to block 404 and continues to receive data p~ ges If h~wever, if the answer is yes, the method proceeds to block 412 and marks the displayable message ready for reassembly. At block 413, the method disposes of the displayable message by, for example, displaying the displayable 30 message. The method ends at block 414.
FIG. 4b is a flowchart of an illustrative embodiment of the present invention. The method begins at block 416. At block 418, the method retrieves a fragment from a data package. At block 420, the method appends the fragment to the end of the displayable message undergoing reassembly. The method determines 35 whether there are other fragments to be appended to the displayable message at block 422. This determination may be based on whether the number of characters in the reassembled message is equal to the value of a parameter such as 21 9o3o5 SMS_Total_Payload_Siæ. If the answer is yes, then the method returns to block 418 and retrieves and processes the next fragment When the answer at block 422 is no, then the entire displayable mçss~e has been reassembled, and the method endsat block 424.
FM. 5 is a sample operational message flow scenario of an illustrative embodiment of the present invention. Origin~ting short message entity 500 sends a displayable mess~ge to termin~ting short message entity 502. For illustrative purposes, termin~ting short message entity 502 comprises a wireless terminal such as a cellular telephone or pager. Termin~ting short message entity 502 is capable of 10 commllnir~ting with a serving base station 504 over a prescribed air int~,lrace such as TDMA, CDMA, AMPS/NAMPS or other standard that supports short message service. Base station 504 is coupled to wireless switching center ("WSC") 506.
Visited location register 508 is associated with wireless switching center 506 and contains a listing of wireless terminals that are in the area covered by wireless switching center 506. Message center 510 and home location register 512 are associated with the home wireless telecommunications network of termin~ting short message entity 502. It is noted that message center 510 and origin~ting short mess~ge entity 500 may reside in a single device such as a personal col-lpulel, a wireless or wireline terminal or other device for sending a short message.
In operation, originating short message entity 500 deposits a displayable mess~ge with message center 510. Message center 510 sends a Short Message Service Request (SMREQ) invoke to home location register 512. If termin~ting short message entity 502 is being served by its home wireless telecomm~mic~tion~system or a visited wireless telecommunications system with which termin~ting 25 short message entity 502 has previously registered (e.g., by autonomous registration), then home location register 512 sends a short message service request (smreq) return result, including, among other things, a parameter SMS_Maximum_Fragment_Size (SMFS), giving the capacity of wireless switching center 506 and base station 504.
If, however, termin~ting short message entity 502 has roamed into a wireless telecommunications system and has not registered, then the smreq from home location register 512 will indic~te a failure. Message center 510 stores the displayable mess~ge until termin~ting short message entity 502 accesses serving wireless ~wi~ching center 506, and REGNOT and SMSNOT operations are 35 performed.
- As shown in FIG. 5, to register in the visited system, t-rmin~ting short mçss~e entity 502 performs a "system access," which may in~lude among other things, placing a call in the serving system through base station 504 and wireless switching center 506. Wireless switching center 506 sends a S "RegistrationNotifi~tion" mçss~ge (REGNOT) to visited location register 508.
Visited loc~tion register 508 in turn transmits the REGNOT mess~ge to home loc~,tion register 512. Wireless switching center 506 includes a parameter SMFS that gives the capacity of wireless switching center 506 and base station 504 in the REGNOT mess~ge if wireless switching center 506 is capable of performing short 10 message service. The capacity typically depends on the internal design of wireless switching center 506 or base station 504 or other components of the conveying network. Home location register 512 transmits the SMFS parameter to message center 510 in the SMS Notification (SMSNOT) invoke. Message center 510 uses the SMFS parameter to divide the displayable message into a~plopliately sized 15 fr~gment~ for transmission over the conveying network via, for example, an SMDPP
operation. As also shown in FIG. 5, message center 510 sends an SMS notification(smnot) return result to home location register 512. Home location register 512 in turn sends a RegistrationNotification (regnot) return result to the visited loc~tion register 508. Visited location register 508 in turn sends a regnot return result20 message to wireless switching center 506.
Once mess~ge center 510 has received either the smreq message or the SMSNOT mess~ge, message center 510 may fragment the displayable message according to the pipe capacity given in the SMFS parameter. If the capacity of the portion of the conveying network of the home wireless telecommunications system 25 is smaller than the portion of pipeline of wireless switching center 506 and base station 508, as given in the SMFS, then the SMFS will be adjusted at home location register 512.
Message center 510 transmits the fragments to wireless switching center 506 and base station 504 using, for example, the short message delivery operation 30 (SMDPP). Base station 504 transmits the fragments to terminating short message entity 502 in a message labeled, for example, first Short Message Delivery Request (lst SMD-REQ). Termin:lting short message entity 502 acknowledges receipt in a first Short Message Delivery Acknowledgement (lst SMD-ACK) message to base station 504. An smdpp return result for the first SMDPP operation is tr~n~mitted35 from wireless switching center 506 to message center 510. Message center 510 similarly sends each fragment to termin~ting short message entity 502. As shown,when the Nth, or final fragment has been transmitted by message center 510 and 2I9030~
received by termin~ting short message entity 502, tr~nsmi~sinn is complete. The fragmentation and tr~n~mission process ends. Termin~ting short message entity 502 then reconstructs the displayable message from the fragments as described above. It is noted that operational mess~ges such as SMSREQ and REGNOT exist in some 5 form in current standards such as IS-41 thus making the illustrative embo~i...e more easily implemented. Further, other operational mess~ges may be used to accomplish the result as described above.
It should be understood that the operative el~ment~ of the system architect~lre relevant to the invention are highlighted above. Many others, while 10 present in the architecture, are only tangentially relevant to the present invention, so they are either not referred to or grouped with other elements in a boarder description of their function at the system level. Further, the present invention involves systems that process and transmit data, where many operations may be done in a dirr~,le~ t order or using a dirrerent methodology to achieve the same end result. For example, 15 reassembly of the displayable message may be done concull~nlly with the fragment retriever by simply concatenating the fragments as they are received and shifting previously receive data and inserting any fragments received out of order. Further, the capacity determination may take into account more than just the capacity of the serving wireless switching center. The capacity of each element of the conveying20 network may be considered in determining the size of the fragments. Further, the te~ching~ of the present invention are also applicable to termin~ting short mess~ge entities that are in the process of being handed off or are in sleep mode. Finally, the illustrative systems discussed in conjunction with the figures relate to cellular wireless systems, but the concepts also apply to wireline and other wireless systems, 25 such as paging systems.
MESSAGE BLI ~ ;N SHORT MESSAGE ENTl~IES IN MORE
THAN ONE DATA PACKAGE
Field of the Invention The present invention relates to telecomm--nic~tions systems in general and, more particularly, to a system and method for tr:~n~mitting a displayable message between short message entities.
Back~round of the Invention Some telecommunications service providers, including cellular and 10 paging companies, provide a "short message service" which allows a user to send and receive displayable messages via a "short message entity." For purposes of this specification, a short message entity is a device that is capable of composing or disposing of short messages. Both wirelines and wireless terminals, including cellular telephones and pagers, may function as short message entities. Further,15 short message service includes the capability of conveying a short message from an origin~ting short message entity to one or more terminating short message entities.
For example, current page systems can transmit a displayable message that consists of a telephone number to be called. Some wireless systems can also send alpha-numeric text for display on the screen of a wireless termin~l thus allowing users to 20 send more det~iled messages. Alpha-numeric text can also be sent to computingdevices such as desk and lap-top computers over wireless or wired terminals or devices. Unfortunately, current short message services can only handle displayable messages of limited siæ. However, to compete with the burgeoning electronic mailindustry, telecommunications service providers would like to be able to transmit25 longer "short" messages to termin~ting short messages entities.
The Telecommunications Industry Association ("TIA") has prescribed interim standards (de~ign~sed "IS" concatenated with an identifier) for tr~n~mitting displayable messages to short message entities over various wireless air interfaces and networks. Each interim standard specifies a protocol including operations, 30 parameters, operational messages and procedures for transmitting a displayable message as a single data package. For example, IS-9SA and IS-637 specify protocols for wireless systems that use Code Division Multiple Access ("CDMA") technology. Further, the IS-136 family of standards specify protocols for short message service in Time Division Multiple Access ("TDMA") systems. The IS-91 35 family of standards specifies protocols for short message service in advanced mobile 21~0305 -phone service ("AMPS/NAMPS") systems. Finally, IS-41-C specifies protocols for short message service over inter-system networks. Analogous protocols exist in the paging industry. Unfortunately, each of these standards specifies a maximum length for the displayable message. The standards do not contemplate tran~mi~sion of 5 longer displayable messages.
Typically, an origin~ting short message entity generates a displayable message for transmi~ion to a terrnin~ting short message entity. The displayable message is transmitte~ over a "conveying network" or "pipeline" between these short mess~e çntities The conveying network includes the network elements and air 10 interface traversed by the displayable message. The conveying network may include some sign~ling mechanism such as, for example, Sign~ling System 7 ("SS7"), X.25,Internet Protocol ("IP"), Asynchronous Transfer Mode ("ATM"), or Frame Relay.
Further, the air interface may be digital such as TDMA, CDMA or other digital air interface. Alternatively, the air interface may comprise an analog interface. It is 15 noted that the originating and termin~ting short message entities do all of the processing with the short message service at the application protocol layer. Theintervening conveying network simply acts as a conduit for information between these two end points. Unfortunately, the conveying network can only transmit up to a maximum amount of data or information as a single data pac~age due to, for 20 example, operational standards as described above or specific implementation of portions of the conveying network. The capacity of the conveying network thus limits the size of displayable messages that can be transmitted in a data pack~gç
Developers in the paging indush^y have dabbled with systems that divide a displayable mess~ge into multiple fr~gment~ for tr~n~mi~sion. However, such 25 systems are primitive because there is no method to handle fragments that arereceived out of order, or to provide for rehransmissions to make up for lost fragments. Further, fragmentation of operational messages has been used in lowerlayer operations in wireless networks. However, to adapt this capability for use in hran~mitting displayable messages, wireless service providers would have to install 30 numerous sof~wale and hardware upgrades to existing networks -- an expensive task.
Summary of the Invention An illustrative embodiment of the present invention provides a system that is capable of tran~mitting a displayable message to a termin~hng short mess~gç
entity in more than one data package over a conveying network. A capacity 35 detçrminer ascertains the capacity of the conveying network for transmitting data.
Based on the capacity of the conveying network, a fragmenter divides the ~Q`3U~
displayable message into fragments at an application protocol layer. The siæ of a fragment does not exceed the capacity of the conveying network. Finally, a pac~rpac~ges the fragment~ into data p~c~ges. The data p~r~ges are separately tr~n~mitt~d using a ~ ly defined short mess~ge service over the conveying S network.
Advantageously, in the illustrative embodiment, each data package may include a reference parameter corresponding to the position of the fragment in the displayable message, and a referenced parameter indicating the total size of thedisplayable message being fragmented and pack~ge~l Other reference parameters 10 may be included in the data packages such as a parameter that in-lir~tes the identify of the displayable message to which the fragment corresponds.
Another illustrative embodiment of the present invention provides a system capable of reconstructing a displayable message from multiple data pac~ges tr~n~mitted over a conveying network. The system includes a fragment retriever that 15 obtains from the data package a fragment or a displayable message. The siæ of the fragments is based on the capacity of the conveying network to transmit data. In one embodiment, the fragment retriever further obtains from the data package a reference parameter that in~lic~tes the relative position of the fragment in the displayable message. The fragment retriever further orders the corresponding fragments 20 according to the referenced parameters obtained from the data packages. Once all fragments have been received, determinecl by comparing the cumulative siæ of fragments received against the total size parameter, a message reconstructer assembles the fragments into the displayable message.
Brief Description of the Drawin~s Illustrative embodiments of the present invention are described below in conjunction with the accompanying drawings, in which:
FM. 1 is a block diagram of an illustrative embodiment of the present invention that provides a system for transmitting a displayable message over a conveying network;
FIG. 2 is a block diagram of an illustrative embodiment of a portion of a short message entity for use in composing a displayable message for transmis~ion in the tr~n~mi~sion of FIG. l;
FIG. 3 is a block diagram of an illustrative embodiment of a portion of a short message entity for use in reconstructing a displayable message with the system 35 of FIG. 1:
219030~
FIGS. 4a-4b are flowcharts that illustrate embodiments of the present invention for reconstructing a displayable message tr:ln~mitted in more than one data p~c~ge over a con~eying network; and FM. 5 is a sample operational message flow scenario of an illustrative 5 embodiment of the present invention.
Detailed Des~ tion FIG. 1 is a block diagram of an illustrative embodiment of the present invention. Telecommunications system 100 transmits displayable messages between, for example, short message entities 102, 104, and 105 over a conveying 10 network in more than one data package using a short message service. As shown in FIG. 1, a short message entity may reside in a wireless terminal (e.g., short message entities 104 and 105 which may comprise cellular or mobile telephones, or a pager), a wireline termin~l (e.g., short message entity 102 which may comprise a wireline telephone, facsimile machine or computer) or other ap~r~liate terminal for 15 tr~n~mitting displayable messages.
Telecommunications systems 100 includes serving wireless system 106.
Wireless system 106 includes wireless switching center ("WSC") 108 that routes displayable mess~ges through base stations 110 1 1102 and 1103 to and from wireless terminals such as short message entities 104 and 105. Each base station20 1 lOn services a region 111 n referred to as a "cell." For simplicity, each cell 111 n is depicted as a hexagon. However, the actual shape of a cell 111 n is ~ t~ted by factors such as the terrain and electromagnetic sources. It is noted that each cell 111 n may be further divided into two or more sectors. Each base station 1 lOn includes antennas and radios for commlmiç~ting with wireless terminals. Each base 25 station 1 lOn further includes transmission equipment for communicating with wireless switching center 108.
Short message entity 102 is coupled to wireless switching center 108 through at least two types of paths. First, network 114 couples short msss~ge entity 102 to wireless switching center 108 through an "indirect" path. Network 114 may30 comprise, for example, a network employing SS7, X.25, IP, ATM or frame relay technology. Further, short message entity 102 may be coupled to wireless switching center 108 through a direct path.
In operation, short message entities can transmit displayable messages over telecommunications system 100 in at least two ways. First, short message 35 entities can transmit displaying messages directing to a termin~ting short message entity over telecommunications system 100. Further, short message entities can 21gO30s transmit displayable messages to an intermediate node, such as a message center, in network 114 for storage until such time as the termin~ting short message entity is ready to receive the displayable message. This is referred to as "store and fol~val.l"
tran~mi~siQn of a displayable message.
In direct tr~n~mission~ short message entity 102, for example, generates a displayable message for tr~nsmissiQn to short mes~ ç entity 104. The displayable mess~ç may comprise alpha-numeric characters tran~mitP,d as form~tted (octets) or unform~tted binary bits. The conveying network or pipeline between short mçss~geentity 102 and short message entity 104 comprises network 114, wireless switching center 108 and base station 1101.
As described above, the maximum amount of data or information (e.g., form~tted or unformatted binary bits) that can be tran~mittçd through the conveying network as a single package of data is defined as the "capacity" of the conveying network. Short message entity 102 determines the capacity of the conveying 15 network that is to be used to transmit the displayable message to short message entity 104. Based on this capacity, short message entity 102 divides the displayable mess~ge into fragments that are less in size than that capacity and packages these fragments for tr~nsmi~sion over the conveying network.
Short message entity 104 receives the packages from base station 110 and reconstructs the displayable message. Short message entity 104 then displaysthe displayable message on, for example, a screen. Thus, system 100 can transmit a displayable message to short message entity 104 that exceeds the capacity of theconveying nel~olk and the short message service used to transmit the displayablemessage. The fragmentation and reconstruction of the displayable message can be carried out at the teleservice (application) protocol layer, thus not requiring an expensive modification to components of network 114 or wireless network 106.
Alternatively, telecommunications system 100 can also support store and fOl~ald tr~n~mis~ n of a displayable message. For example, short message entity 105 can transmit a displayable message to short message entity 104. Short30 message entity 105 generates a displayable message for tr~n~mi~ n to short message entity 104. If short message entity 104 is not available, telecommunications system 100 identifies a message center in network 114 or wireless switching center 108 to receive and store the displayable message. Short message entity 105 determines the capacity of the conveying network that is to be used to transmit the 35 displayable message to the message center. Based on this capacity, short message entity 105 divides the displayable message into fragments that are less than that capacity and packages these fragments for tr~n~mission over the conveying network 21903o~
to the mess~ge center.
When short message entity 104is available to receive the message, the meSs~ge center determines the capacity of a conveying nelv~ol~ to be used to carry the displayable mçss~e to short message entity 104. Short message entity 104 5 receives the pac~ges from base station 110 1 and reconstructs the displayable meSs~ge Short message entity 104 then displays the displayable message on, for example, a screen. It is noted that in both direct and store and fol ~ald techniques, network 114 may include nodes that pelrul~l~ the functions of short message entities 102, 104, and 105. For example, these functions may be ~lro~",ed in a messag~
10 center, a home location register, a wireless switching center or other a~r~,iate network node.
It is noted that short message entities 104 and 105 are both shown for convenience in wireless system 106. It is understood that short message entities 104 and 105 may communicate displayable messages over telecommunic~tions system 15 100 even when short message entities 104 and 105 are not located in the same wireless system or are not using the same wireless switching center.
Example In a cellular system using SS7 as the inter-system carriage protocol, the message package capacity is limited to 272 octets. A short message delivery 20 operation, designated "SMDPP," can therefore carry only 272 octets of information.
A con.~iderable portion of this is used for "overhead" information, such as addressing and other parameters, some that are mandatory and some that are optional. The size of this overhead governs how much will remain to carry the displayable message in the data package. In an SS7 network, the component of the SMDPP operation that 25 transmits the displayable message is referred to as "bearer data."
In a typical implementation, the overhead information may require 92 octets, leaving 180 octets available for tr~n~mit~;ng the displayable mçss~ge asbearer data. According to the illustrative embodiment, for displayable messages that exceed 180 octets, the composite displayable message is broken into fragments of30 180 octets or less and tr~n~mitte-~ with separate SMDPP operations.
If a serving wireless ~witching center ("WSC") could only handle 100 octets, then the size of the fragments is further limited. Considering the 100 octet pipe capacity imposed by the serving WSC, at least three SMDPP operations would be needed to carry a displayable message with between 200 and 300 octets of data.
35 Each SMDPP operation can carry different amounts of data so long as no SMDPP
operation exceeds the 100 octet pipe capacity defined by the WSC. ~ltçrn~tively, all 21gO3~S
but one SMDPP operation can carry the data equal to the capacity while the last SMDPP operation carries data that is less than the capacity.
If any one of the fragments does not arrive at the termin~ting short meSs~ge entity, the resulting autom~tic negative acknowledgment that already exists 5 as part of the existing standards for single data p~c~ge short message service would in~tig~te the origin~ting short message entity to retransmit that particular fra~nçnt The integrity of each short message service delivery would also be guaranteed bylower layer checks (e.g., CRC, etc.).
For clarity, FIGS. 2 and 3, described below, only show cilcuilly for 10 tr~n~mitting a displayable message in one direction. Thus, FIG. 2 illustratesCil~;uill,y that is used to compose a displayable message for tr~n~mi~sion. Similarly, FIG. 3 illustrates circuilly that is used to reconstruct a displayable message. It should be understood that short message entity 102 may included circuitry similar to FIG. 3 and that short message entity 104 may comprise cilcuilly similar to FIG. 2.
15 Further, for purposes of this specification, a short message entity that is used to compose a displayable message is referred to as an "origin~ting short message entity." Similarly, a short message entity that is used to reconstruct a displayable message is referred to as a "terminating short message entity."
FIG. 2 is a block diagram of an embodiment of an ori~in~ting short 20 message entity for use in telecommunications network 100 of FIG. 1. Originating short message entity 102 processes displayable messages for tr~n~mi~sion to a termin~ting short message entity. Originating short message entity 102 includes message composer 200. Message composer 200 provides displayable messages to message buffer 202. Message buffer 202 and capacity determiner provides inputs to 25 fragmenter 204. Fragmenter 204 provides an output to package 208.
In operation, originating short message entity 102 divides a displayable message entered with message composer 200 into fragments for tr~nimi~sil~n over a conveying network to a termin~ting short message entity. Capacity determin~tion operation 206 determines the capacity for the virtual. As described in more detail 30 below with respect to FIG. 5, capacity determiner 206 may determine the capacity of the conveying network in part based on a value of a parameter that is included in an autonomous registration process for a wireless terminal that roams into a regioncovered by wireless switching center 108. Originating short message entity 102 may use data on limitations of other aspected of the conveying network to set the size of 35 the fragments. Fragmentation operation 204 divides the displayable message into fragments such that the fragments do not exceed the capacity of the conveying network. By thus dynamically sizing the data packages, the illustrative embodiment of the present invention advantageously allows displayable messages to be sent with increased usage of network resources. P~c~ging operation 208 places the fragments in data p~a~g-es for tran~mi~ion.
In ad~lition to the fragmçnt~, the data pac~ges may include other 5 ltr~nce p~ulletel~. For example, the data pa~ges may include a parameter, e.g., SMS_Fragment_Number, in-lic~ting the position of each fragment within the displayable mess~ge Additionally, the data p~ k~ges may each include an indicia of the size of the displayable message, e.g., SMS_Total_Payload_Siæ. Finally, each data p~c~a~ may include a parameter, e.g., Msg_ID, that identifies the displayable 10 message to which the data package belongs. It is noted that the capacity, as defined previously, is the siæ of the largest data package that the virtual circuit can transmit.
Thus, the capacity of the circuit includes space for "overhead" information used in tran~mitting data that is included with each package of data. This overhead may include, for example, the short message service protocol as well as the parameters 15 SMS_Fragment_Number, SMS_Total_Payload_Size, and Msg_ID.
While fragmçnter 204 may use a parameter co~ s~onding to the relative position of the fragment, the sequence of the fragments may be preserved in other ways. Fragmenter 204 may, for example, pass each fragment to package 208 and await the corresponding automatic acknowledgment before opelaling on the next 20 fragment thereby passing the fragments to the packager in the order corresponding to the displayable message.
As previously noted, the conveying network between the short meSsage entity 102 and short message entity 104 mererly transmits each data package according to existing protocols. No processing of the contents of the data protocols 25 occurs in the conveying network thus allowing implementation without requiring ~ignifi~nt modifications to sof~w~e or hardware or both.
FIG. 3 is a block diagrarn of a portion of a termin~ting short message entity for use in telecommunications system 100 of FM. 1. Terminating short message entity 104 includes buffer 302. Buffer 302 provides an input to fragment30 retriever 304. Fragment retriever 304 provides an input to message reconstructer 306. Finally, message reconstructer 306 drives disposing device 308 which may, for example, comprise a display for displaying a displayable message to a user.
In operation, buffer 302 receives more than one data package relating to a displayable message tr~nsmitted from origin~ting short message entity 102 to 35 termin~ting short message entity 104. Buffer 302 stores the data p~ck~ges.
Fragment retriever 304 retrieves a fragment of a displayable message and a reference parameter from each data package that indicates the position of the fragment relative 219~305 to the other fragments in the displayable message. Fragment retriever 304 further orders the fragments according to the reference parameters retrieved from the data p~c~g~s Message reconstructer 306 reconstructs the displayable message and provides the displayable message to disposing device 308. It is noted that fragment 5 retriever 304 may process data packages corresponding to different displayable messages in parallel if a parameter such as Msg_ID is used.
FM. 4a is a flowchart illustrating an embodiment of the present invention. The method begins at block 402. At block 404 the method retrieves a data ~~c~ At block 406, the method determin~s whether the data package has 10 already been received by, for example, checking the SMS_Fragment_Number and the Msg_ID parameters against a list of received data packages. If the answer is yes, the data package has been previously received and the method returns to block 404 to retrieve another data package. Thus, terminating short message entity 104 canreject duplicate fragments that may have been received due to retr~n~miisions. A15 retr~n~mi~sion by the originating short message entity may occur, for example, because an acknowledgment to an earlier tr~nimi~sion was not receiveed in time, e.g., prior to expiration of a timer at the originating short message entity.
If, however, the answer at block 406 is no, then the data package has not been previously received. At block 408, the fragment is retrieved from the data 20 package and stored. Receipt of the fragment may be recorded by, for example, ~;cordillg the parameters SMS Fragment Number and Msg_ID for the data p~cl~ge At block 410, the method determines whether all fragments corresponding to the displayable message have been retrieved. The parameter SMS_Total_Payload Size included in at least one data package may be used in 25 determining whether all fragments have been retrieved. If not all fragments have been retrieved, the method returns to block 404 and continues to receive data p~ ges If h~wever, if the answer is yes, the method proceeds to block 412 and marks the displayable message ready for reassembly. At block 413, the method disposes of the displayable message by, for example, displaying the displayable 30 message. The method ends at block 414.
FIG. 4b is a flowchart of an illustrative embodiment of the present invention. The method begins at block 416. At block 418, the method retrieves a fragment from a data package. At block 420, the method appends the fragment to the end of the displayable message undergoing reassembly. The method determines 35 whether there are other fragments to be appended to the displayable message at block 422. This determination may be based on whether the number of characters in the reassembled message is equal to the value of a parameter such as 21 9o3o5 SMS_Total_Payload_Siæ. If the answer is yes, then the method returns to block 418 and retrieves and processes the next fragment When the answer at block 422 is no, then the entire displayable mçss~e has been reassembled, and the method endsat block 424.
FM. 5 is a sample operational message flow scenario of an illustrative embodiment of the present invention. Origin~ting short message entity 500 sends a displayable mess~ge to termin~ting short message entity 502. For illustrative purposes, termin~ting short message entity 502 comprises a wireless terminal such as a cellular telephone or pager. Termin~ting short message entity 502 is capable of 10 commllnir~ting with a serving base station 504 over a prescribed air int~,lrace such as TDMA, CDMA, AMPS/NAMPS or other standard that supports short message service. Base station 504 is coupled to wireless switching center ("WSC") 506.
Visited location register 508 is associated with wireless switching center 506 and contains a listing of wireless terminals that are in the area covered by wireless switching center 506. Message center 510 and home location register 512 are associated with the home wireless telecommunications network of termin~ting short message entity 502. It is noted that message center 510 and origin~ting short mess~ge entity 500 may reside in a single device such as a personal col-lpulel, a wireless or wireline terminal or other device for sending a short message.
In operation, originating short message entity 500 deposits a displayable mess~ge with message center 510. Message center 510 sends a Short Message Service Request (SMREQ) invoke to home location register 512. If termin~ting short message entity 502 is being served by its home wireless telecomm~mic~tion~system or a visited wireless telecommunications system with which termin~ting 25 short message entity 502 has previously registered (e.g., by autonomous registration), then home location register 512 sends a short message service request (smreq) return result, including, among other things, a parameter SMS_Maximum_Fragment_Size (SMFS), giving the capacity of wireless switching center 506 and base station 504.
If, however, termin~ting short message entity 502 has roamed into a wireless telecommunications system and has not registered, then the smreq from home location register 512 will indic~te a failure. Message center 510 stores the displayable mess~ge until termin~ting short message entity 502 accesses serving wireless ~wi~ching center 506, and REGNOT and SMSNOT operations are 35 performed.
- As shown in FIG. 5, to register in the visited system, t-rmin~ting short mçss~e entity 502 performs a "system access," which may in~lude among other things, placing a call in the serving system through base station 504 and wireless switching center 506. Wireless switching center 506 sends a S "RegistrationNotifi~tion" mçss~ge (REGNOT) to visited location register 508.
Visited loc~tion register 508 in turn transmits the REGNOT mess~ge to home loc~,tion register 512. Wireless switching center 506 includes a parameter SMFS that gives the capacity of wireless switching center 506 and base station 504 in the REGNOT mess~ge if wireless switching center 506 is capable of performing short 10 message service. The capacity typically depends on the internal design of wireless switching center 506 or base station 504 or other components of the conveying network. Home location register 512 transmits the SMFS parameter to message center 510 in the SMS Notification (SMSNOT) invoke. Message center 510 uses the SMFS parameter to divide the displayable message into a~plopliately sized 15 fr~gment~ for transmission over the conveying network via, for example, an SMDPP
operation. As also shown in FIG. 5, message center 510 sends an SMS notification(smnot) return result to home location register 512. Home location register 512 in turn sends a RegistrationNotification (regnot) return result to the visited loc~tion register 508. Visited location register 508 in turn sends a regnot return result20 message to wireless switching center 506.
Once mess~ge center 510 has received either the smreq message or the SMSNOT mess~ge, message center 510 may fragment the displayable message according to the pipe capacity given in the SMFS parameter. If the capacity of the portion of the conveying network of the home wireless telecommunications system 25 is smaller than the portion of pipeline of wireless switching center 506 and base station 508, as given in the SMFS, then the SMFS will be adjusted at home location register 512.
Message center 510 transmits the fragments to wireless switching center 506 and base station 504 using, for example, the short message delivery operation 30 (SMDPP). Base station 504 transmits the fragments to terminating short message entity 502 in a message labeled, for example, first Short Message Delivery Request (lst SMD-REQ). Termin:lting short message entity 502 acknowledges receipt in a first Short Message Delivery Acknowledgement (lst SMD-ACK) message to base station 504. An smdpp return result for the first SMDPP operation is tr~n~mitted35 from wireless switching center 506 to message center 510. Message center 510 similarly sends each fragment to termin~ting short message entity 502. As shown,when the Nth, or final fragment has been transmitted by message center 510 and 2I9030~
received by termin~ting short message entity 502, tr~nsmi~sinn is complete. The fragmentation and tr~n~mission process ends. Termin~ting short message entity 502 then reconstructs the displayable message from the fragments as described above. It is noted that operational mess~ges such as SMSREQ and REGNOT exist in some 5 form in current standards such as IS-41 thus making the illustrative embo~i...e more easily implemented. Further, other operational mess~ges may be used to accomplish the result as described above.
It should be understood that the operative el~ment~ of the system architect~lre relevant to the invention are highlighted above. Many others, while 10 present in the architecture, are only tangentially relevant to the present invention, so they are either not referred to or grouped with other elements in a boarder description of their function at the system level. Further, the present invention involves systems that process and transmit data, where many operations may be done in a dirr~,le~ t order or using a dirrerent methodology to achieve the same end result. For example, 15 reassembly of the displayable message may be done concull~nlly with the fragment retriever by simply concatenating the fragments as they are received and shifting previously receive data and inserting any fragments received out of order. Further, the capacity determination may take into account more than just the capacity of the serving wireless switching center. The capacity of each element of the conveying20 network may be considered in determining the size of the fragments. Further, the te~ching~ of the present invention are also applicable to termin~ting short mess~ge entities that are in the process of being handed off or are in sleep mode. Finally, the illustrative systems discussed in conjunction with the figures relate to cellular wireless systems, but the concepts also apply to wireline and other wireless systems, 25 such as paging systems.
Claims (12)
1. A system that is capable of transmitting a displayable message to a terminating short message entity in more than one data package over a conveying network, the system CHARACTERIZED BY:
a capacity determiner that determines a capacity of the conveying network for transmitting data;
a fragmenter that divides the displayable message into fragments at an application protocol layer based on the capacity determined by the capacity determiner such that the size of the fragments does not exceed the capacity of the conveying network; and a packager that packages the fragments into the data packages such that the data packages are operable to be separately transmitted by a short message service over the conveying network.
a capacity determiner that determines a capacity of the conveying network for transmitting data;
a fragmenter that divides the displayable message into fragments at an application protocol layer based on the capacity determined by the capacity determiner such that the size of the fragments does not exceed the capacity of the conveying network; and a packager that packages the fragments into the data packages such that the data packages are operable to be separately transmitted by a short message service over the conveying network.
2. The system of claim 1, CHARACTERIZED IN THAT the capacity determiner determines a number of bits in the displayable message that are operable to be transmitted in the data packages.
3. The system of claim 1, CHARACTERIZED IN THAT the data packages further include an indicia of the size of the displayable message and a reference parameter corresponding to the position of the fragment in the displayable message.
4. The system of claim 3, CHARACTERIZED IN THAT the packager adds the indicia of the size of the displayable message and the reference parameter corresponding to the position of the fragment into the data packages.
5. The system of claim l, CHARACTERIZED IN THAT the data packages further include an indicia of the identity of the displayable message.
6. The system of claim 5, CHARACTERIZED IN THAT the packager adds the indicia of the identity of the displayable message into the data packages.
7. The system of claim 1, CHARACTERIZED IN THAT the capacity determiner determines the capacity based on a capacity indication from a servingwireless telecommunications network in the conveying network.
8. The system of claim 1, CHARACTERIZED IN THAT the capacity determiner, the fragmenter and the packager comprise a displayable message center coupled to a serving wireless telecommunications network that transmits the displayable message to the wireless terminal.
9. A wireless telecommunications system that is capable of registering visiting wireless terminals associated with a different home location register, the system CHARACTERIZED BY:
a wireless switching center that is operable to receive calls and registration information from visiting wireless terminals through one of a plurality of base stations;
a visited location register coupled to the wireless switching center that is operable to provide an indicia of the capacity of the wireless system during a registration operation to the home location register of the wireless terminal for use in fragmentation and reassembly of displayable messages transmitted on a short message service that exceed the capacity of the system.
a wireless switching center that is operable to receive calls and registration information from visiting wireless terminals through one of a plurality of base stations;
a visited location register coupled to the wireless switching center that is operable to provide an indicia of the capacity of the wireless system during a registration operation to the home location register of the wireless terminal for use in fragmentation and reassembly of displayable messages transmitted on a short message service that exceed the capacity of the system.
10. A system capable of transmitting a displayable message over a conveying network in more than one data package, the system CHARACTERIZED
BY:
a fragmenter for dividing a displayable message having an amount of data greater than the capacity of the components of the conveying network into fragments each having an amount of data less than or equal to the capacity of the conveying network; and a packager for packaging the fragments into multiple data packages, the data packages including a reference parameter corresponding to the position of the fragment in the displayable message.
BY:
a fragmenter for dividing a displayable message having an amount of data greater than the capacity of the components of the conveying network into fragments each having an amount of data less than or equal to the capacity of the conveying network; and a packager for packaging the fragments into multiple data packages, the data packages including a reference parameter corresponding to the position of the fragment in the displayable message.
11. A system capable of reconstructing a displayable message from multiple data packages transmitted over a conveying network with a short message service, the system CHARACTERIZED BY:
a fragment retriever for retrieving a fragment of a displayable message and a reference parameter from the data package wherein the size of the fragment is based on the capacity of the conveying network, the position of the fragment in the displayable message is determined by the reference parameter retrieved from the data package for the fragment, the fragment retriever ordering the corresponding fragments according to the reference parameters retrieved from the data packages; and a message reconstructor for assembling the fragments into the displayable message according to their reference parameter.
a fragment retriever for retrieving a fragment of a displayable message and a reference parameter from the data package wherein the size of the fragment is based on the capacity of the conveying network, the position of the fragment in the displayable message is determined by the reference parameter retrieved from the data package for the fragment, the fragment retriever ordering the corresponding fragments according to the reference parameters retrieved from the data packages; and a message reconstructor for assembling the fragments into the displayable message according to their reference parameter.
12. The system of claim 11, CHARACTERIZED IN THAT the fragment retriever identifies the total amount of data in the displayable message from an indicia included in at least one data package.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US08/572,481 US6108530A (en) | 1995-12-14 | 1995-12-14 | System and method for transmitting a displayable message between short message entities in more than one data package |
| US572,481 | 1995-12-14 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2190305A1 true CA2190305A1 (en) | 1997-06-15 |
Family
ID=24288012
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002190305A Abandoned CA2190305A1 (en) | 1995-12-14 | 1996-11-14 | System and method for transmitting a displayable message to a short message entity in more than one data package |
Country Status (4)
| Country | Link |
|---|---|
| US (3) | US6108530A (en) |
| JP (1) | JP3597000B2 (en) |
| KR (1) | KR100456708B1 (en) |
| CA (1) | CA2190305A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1103888A1 (en) * | 1999-11-26 | 2001-05-30 | Siemens Aktiengesellschaft | Method for the transmission and display of information on a wireless communication unit |
| EP1107618A2 (en) * | 1999-11-30 | 2001-06-13 | Samsung Electronics Co., Ltd. | Method of transmitting and receiving multimedia data using short message service in portable radio telephone |
| CN100358385C (en) * | 1999-03-19 | 2007-12-26 | 三星电子株式会社 | Data transmitting and receiving apparatus and method for a digital mobile station |
Families Citing this family (64)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6108530A (en) * | 1995-12-14 | 2000-08-22 | Lucent Technologies Inc. | System and method for transmitting a displayable message between short message entities in more than one data package |
| FI102869B (en) * | 1996-02-26 | 1999-02-26 | Nokia Mobile Phones Ltd | A device, method, and system for transmitting and receiving information relating to various applications |
| US7088990B1 (en) * | 1996-02-26 | 2006-08-08 | Nokia Mobile Phones, Ltd. | Communication network terminal supporting a plurality of applications |
| DE19640219A1 (en) * | 1996-09-30 | 1998-04-02 | Siemens Ag | Method for indicating that a text message is present in a central message module of a mobile radio network |
| US6097961A (en) * | 1996-11-06 | 2000-08-01 | Nokia Mobile Phones Limited | Mobile station originated SMS using digital traffic channel |
| US6178174B1 (en) * | 1997-08-26 | 2001-01-23 | International Business Machines Corporation | Optimistic, eager rendezvous transmission mode and combined rendezvous modes for message processing systems |
| FI106282B (en) * | 1997-09-22 | 2000-12-29 | Nokia Networks Oy | A method and system for transmitting a short message over a telecommunications network |
| KR100346117B1 (en) * | 1998-04-14 | 2002-10-19 | 삼성전자 주식회사 | Method for transmitting continuous user data in reverse common channel of mobile communication system |
| US6327478B1 (en) * | 1998-12-23 | 2001-12-04 | Northern Telecom, Ltd. | Short message park and page system and method |
| KR100677063B1 (en) * | 1999-02-13 | 2007-02-01 | 삼성전자주식회사 | Data transmission method and terminal using short message service |
| US6523062B1 (en) * | 1999-06-29 | 2003-02-18 | International Business Machines Corporation | Facilitating memory constrained client devices by employing deck reduction techniques |
| KR100532274B1 (en) * | 1999-09-08 | 2005-11-29 | 삼성전자주식회사 | Apparatus for transfering long message in portable terminal and method therefor |
| AU7358300A (en) * | 1999-09-20 | 2001-04-24 | Neopoint, Inc. | System and method for constructing a composite sms message from multiple sms messages |
| US6493559B1 (en) * | 2000-01-07 | 2002-12-10 | Motorola, Inc. | Method for receiving SMSCB messages during GPRS/EDGE data transfer mode |
| US6446118B1 (en) * | 2000-02-29 | 2002-09-03 | Designtech International, Inc. | E-mail notification device |
| US7275093B1 (en) * | 2000-04-26 | 2007-09-25 | 3 Com Corporation | Methods and device for managing message size transmitted over a network |
| EP1217848A3 (en) * | 2000-12-22 | 2003-03-12 | Siemens Aktiengesellschaft | Method for indication and transmission of chained Short Messages |
| WO2002071754A1 (en) * | 2001-03-02 | 2002-09-12 | Digeo, Inc. | Messaging via a third party in an interactive video system |
| US20020124252A1 (en) * | 2001-03-02 | 2002-09-05 | Schaefer Scott R. | Method and system to provide information alerts via an interactive video casting system |
| GB0109525D0 (en) * | 2001-04-18 | 2001-06-06 | Telsis Holdings Ltd | Managing text message traffic in mobile telephone networks |
| KR20020095947A (en) * | 2001-06-18 | 2002-12-28 | 엘지전자 주식회사 | Method of Communicating Data Between Client and Server |
| US7668535B2 (en) * | 2001-07-09 | 2010-02-23 | Palm, Inc. | Notification infrastructure for sending device-specific wireless notifications |
| GB2377532B (en) * | 2001-07-11 | 2005-06-29 | Sendo Int Ltd | Communications devices operable to electronically process text data for representing characters of a text message, and methods for operating such devices |
| WO2003017701A1 (en) * | 2001-08-16 | 2003-02-27 | Celltick Technologies Ltd | Concatenated point-to-multipoint (ptmp) broadcast messages for displaying display messages in cellular phones |
| US7050408B2 (en) * | 2001-09-26 | 2006-05-23 | Microsoft Corporation | Communicating multi-part messages between cellular devices using a standardized interface |
| US20030093467A1 (en) * | 2001-11-01 | 2003-05-15 | Flying Wireless, Inc. | Server for remote file access system |
| US20030084045A1 (en) * | 2001-11-01 | 2003-05-01 | Flying Wireless, Inc. | Systems and protocols for remote file access |
| US9332058B2 (en) | 2001-11-01 | 2016-05-03 | Benhov Gmbh, Llc | Local agent for remote file access system |
| US7032224B2 (en) * | 2001-12-31 | 2006-04-18 | Slam Dunk Networks, Inc. | Method for the secure and timely delivery of large messages over a distributed communication network |
| AU2003224237A1 (en) * | 2002-03-25 | 2003-10-08 | Intellprop Limited | Telecommunications services apparatus |
| AU2003237090A1 (en) * | 2002-04-22 | 2003-11-03 | Inphonic, Inc. | Method and system for short message service (sms) transactions for wireless devices |
| KR100541880B1 (en) * | 2002-07-10 | 2006-01-10 | 주식회사 케이티프리텔 | A short message communication system having recombination function using a waiting time over broadcast and a method thereof |
| US20040027999A1 (en) * | 2002-08-08 | 2004-02-12 | Lorenzo Casaccia | Broadcast message segmentation for wireless communication systems |
| US20040081299A1 (en) * | 2002-10-24 | 2004-04-29 | Sbc Properties, L.P. | System and method for select messaging |
| US7042857B2 (en) | 2002-10-29 | 2006-05-09 | Qualcom, Incorporated | Uplink pilot and signaling transmission in wireless communication systems |
| US7319860B2 (en) * | 2002-11-07 | 2008-01-15 | Research In Motion Limited | Pseudo-interactive input processing in wireless environments |
| US7177297B2 (en) | 2003-05-12 | 2007-02-13 | Qualcomm Incorporated | Fast frequency hopping with a code division multiplexed pilot in an OFDMA system |
| US20050009542A1 (en) * | 2003-07-11 | 2005-01-13 | Valentin Oprescu-Surcobe | Wireless communications network and method for enabling wireless presence-based services |
| KR20060088118A (en) * | 2003-09-30 | 2006-08-03 | 코닌클리즈케 필립스 일렉트로닉스 엔.브이. | Communications device comprising a receiver for important information, method of transmitting such information, and transmitting system using such a method |
| US8611283B2 (en) | 2004-01-28 | 2013-12-17 | Qualcomm Incorporated | Method and apparatus of using a single channel to provide acknowledgement and assignment messages |
| US20050198353A1 (en) * | 2004-03-05 | 2005-09-08 | Robert Zmrzli | Method and apparatus for providing dynamic network content to target devices |
| US20050208929A1 (en) * | 2004-03-05 | 2005-09-22 | Robert Zmrzli | Method and apparatus for providing updated network content to target devices |
| US20050208930A1 (en) * | 2004-03-05 | 2005-09-22 | Robert Zmrzli | Method and apparatus for arranging network content on mobile devices |
| US8891349B2 (en) | 2004-07-23 | 2014-11-18 | Qualcomm Incorporated | Method of optimizing portions of a frame |
| AU2005287981B2 (en) * | 2004-08-17 | 2008-08-28 | Nokia Technologies Oy | Method and system for forming and transmitting/receiving neighbor base station information in a BWA communication system |
| US8831115B2 (en) | 2004-12-22 | 2014-09-09 | Qualcomm Incorporated | MC-CDMA multiplexing in an orthogonal uplink |
| US8238923B2 (en) * | 2004-12-22 | 2012-08-07 | Qualcomm Incorporated | Method of using shared resources in a communication system |
| US7941165B2 (en) * | 2005-03-02 | 2011-05-10 | Cisco Technology, Inc. | System and method for providing a proxy in a short message service (SMS) environment |
| WO2007040310A1 (en) * | 2005-10-05 | 2007-04-12 | Ktfreetel Co., Ltd. | System and method for decorating short message from origination point |
| US8355701B2 (en) | 2005-11-30 | 2013-01-15 | Research In Motion Limited | Display of secure messages on a mobile communication device |
| US7840207B2 (en) * | 2005-11-30 | 2010-11-23 | Research In Motion Limited | Display of secure messages on a mobile communication device |
| KR20080096549A (en) * | 2006-01-17 | 2008-10-30 | 샌드-엠 리미티드. | Apparatus and method for many-to-many mobile messaging |
| CN101047880B (en) * | 2006-03-31 | 2010-05-12 | 华为技术有限公司 | Message transmission method and system |
| NZ549548A (en) * | 2006-08-31 | 2009-04-30 | Arc Innovations Ltd | Managing supply of a utility to a customer premises |
| US9191793B2 (en) | 2007-10-19 | 2015-11-17 | Duc Anh Ngo | Interactive system and process |
| BRPI0717647A2 (en) * | 2006-10-19 | 2013-10-15 | Deloitte Services Pty Ltd | INSTRUCTIONS FOR PROVIDING INSTRUCTIONS FOR DEVICE OR APPLICATION INSTALLED ON MOBILE USER DEVICE CONNECTED TO A SOFTWARE IMPLEMENTED NETWORK AND SOLUTIONS |
| CN101321362B (en) * | 2007-06-08 | 2013-04-24 | 华为技术有限公司 | Charging method, system and device |
| US20090064258A1 (en) * | 2007-08-27 | 2009-03-05 | At&T Knowledge Ventures, Lp | System and Method for Sending and Receiving Text Messages via a Set Top Box |
| US7949355B2 (en) | 2007-09-04 | 2011-05-24 | Research In Motion Limited | System and method for processing attachments to messages sent to a mobile device |
| US8254582B2 (en) * | 2007-09-24 | 2012-08-28 | Research In Motion Limited | System and method for controlling message attachment handling functions on a mobile device |
| CN101360278A (en) * | 2008-09-17 | 2009-02-04 | 华为技术有限公司 | Method, apparatus and system for instant message receiving and transmitting |
| US8909261B1 (en) * | 2008-12-16 | 2014-12-09 | Sprint Communications Company L.P. | Dynamic determination of file transmission chunk size for efficient media upload |
| US20150381381A1 (en) * | 2014-06-30 | 2015-12-31 | Motorola Solutions, Inc | Methods and systems for transmitting group data using a downlink group data channel |
| US10728719B1 (en) * | 2020-04-22 | 2020-07-28 | Bandwidth, Inc. | Techniques for combining segmented messages in a communications network |
Family Cites Families (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4074230A (en) | 1976-05-24 | 1978-02-14 | Teledyne Industries, Inc. | Communication method and apparatus for providing an enhanced signal from diverse signals |
| US4868824A (en) | 1987-12-28 | 1989-09-19 | American Telephone And Telegraph Company | Measurement of missed start-up rate and missed message rate |
| US5093824A (en) * | 1990-03-27 | 1992-03-03 | Bell Communications Research, Inc. | Distributed protocol for improving the survivability of telecommunications trunk networks |
| FI94581C (en) * | 1991-02-12 | 1995-09-25 | Nokia Telecommunications Oy | System for automatically communicating contact information in a mobile telephone network or the like |
| NZ243730A (en) * | 1991-08-01 | 1995-04-27 | Ericsson Ge Mobile Communicat | Mobile radio; access to base station on digital multiple access control channel |
| FI98183C (en) | 1992-02-14 | 1997-04-25 | Nokia Mobile Phones Ltd | Arrangement for connecting a data adapter to a GSM cellular telephone |
| US5313454A (en) * | 1992-04-01 | 1994-05-17 | Stratacom, Inc. | Congestion control for cell networks |
| US5392398A (en) * | 1992-04-20 | 1995-02-21 | International Business Machines Corporation | System and method for deallocation a first message independently of the deallocation of a second message in a bundle of messages |
| DE69330661T2 (en) | 1992-04-27 | 2002-06-27 | Nippon Telegraph & Telephone | Packet network and method for avoiding congestion of such a network |
| US5282205A (en) * | 1992-05-29 | 1994-01-25 | Motorola, Inc. | Data communication terminal providing variable length message carry-on and method therefor |
| US5311516A (en) * | 1992-05-29 | 1994-05-10 | Motorola, Inc. | Paging system using message fragmentation to redistribute traffic |
| FI91700C (en) * | 1992-08-14 | 1994-07-25 | Nokia Telecommunications Oy | A method for transmitting packet data and a mobile station for a cellular radio system |
| FI91699C (en) * | 1992-08-14 | 1994-07-25 | Nokia Telecommunications Oy | Method for transmitting packet format user data in a cellular radio system and mobile station |
| US5603081A (en) * | 1993-11-01 | 1997-02-11 | Telefonaktiebolaget Lm Ericsson | Method for communicating in a wireless communication system |
| US5508732A (en) * | 1993-03-22 | 1996-04-16 | International Business Machines Corporation | Data server, control server and gateway architecture system and method for broadcasting digital video on demand |
| US5594740A (en) * | 1993-08-27 | 1997-01-14 | Axion Logistics Corporation | Wireless communications application specific enabling method and apparatus |
| US5557724A (en) * | 1993-10-12 | 1996-09-17 | Intel Corporation | User interface, method, and apparatus selecting and playing channels having video, audio, and/or text streams |
| US5410698A (en) * | 1993-10-12 | 1995-04-25 | Intel Corporation | Method and system for dynamic loading of software libraries |
| FI98688C (en) * | 1994-07-20 | 1997-07-25 | Nokia Telecommunications Oy | Method for initiating a short message transmission in a cellular radio system, a cellular radio system and subscriber register in a cellular radio system |
| US5546394A (en) * | 1994-12-09 | 1996-08-13 | Motorola, Inc. | Message fragmenting in a time diversity radio system |
| US5603084C1 (en) * | 1995-03-02 | 2001-06-05 | Ericsson Inc | Method and apparatus for remotely programming a cellular radiotelephone |
| US5577045A (en) * | 1995-08-16 | 1996-11-19 | Motorola, Inc. | Selective call receiver for recovering garbled message fragments |
| US5657452A (en) * | 1995-09-08 | 1997-08-12 | U.S. Robotics Corp. | Transparent support of protocol and data compression features for data communication |
| US5742588A (en) * | 1995-09-18 | 1998-04-21 | Telefonaktiebolaget Lm Ericsson | Packet switched traffic management in a cellular telecommunications system |
| US5666348A (en) * | 1995-09-18 | 1997-09-09 | Telefonaktiebolaget L M Ericsson (Publ.) | Packet switched radio channel admission control in a cellular telecommunications system |
| US5946629A (en) * | 1995-11-28 | 1999-08-31 | Telefonaktiebolaget L M Ericsson | Cellular telephone network having short message service interaction with other networks |
| US5920821A (en) * | 1995-12-04 | 1999-07-06 | Bell Atlantic Network Services, Inc. | Use of cellular digital packet data (CDPD) communications to convey system identification list data to roaming cellular subscriber stations |
| JPH09182134A (en) * | 1995-12-07 | 1997-07-11 | Motorola Inc | Message transmission system |
| US6108530A (en) * | 1995-12-14 | 2000-08-22 | Lucent Technologies Inc. | System and method for transmitting a displayable message between short message entities in more than one data package |
| US5920822A (en) * | 1996-01-18 | 1999-07-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Formatting of short message service messages in a cellular telephone network |
| US5805997A (en) * | 1996-01-26 | 1998-09-08 | Bell Atlantic Network Services, Inc. | System for sending control signals from a subscriber station to a network controller using cellular digital packet data (CDPD) communication |
| DE19622007C2 (en) * | 1996-05-31 | 1998-11-19 | Ericsson Telefon Ab L M | USSD scheduler for mobile switching center MSC |
| US5946630A (en) * | 1996-07-10 | 1999-08-31 | Telefonaktiebolaget L M Ericsson (Publ) | Method for storing and forwarding short messages to mobile subscribers in a cellular communications system |
| US5905954A (en) * | 1997-01-14 | 1999-05-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for transferring subscriber information in a radio telecommunications network |
| US6075114A (en) * | 1997-04-25 | 2000-06-13 | Toray Industries, Inc. | Liquid-crystalline resin compositions and moldings |
| US5978685A (en) * | 1997-12-15 | 1999-11-02 | Telefonaktiebolaget L/M Ericsson | Digital cellular telecommunications with short message service over the packet channel |
-
1995
- 1995-12-14 US US08/572,481 patent/US6108530A/en not_active Expired - Lifetime
-
1996
- 1996-11-14 CA CA002190305A patent/CA2190305A1/en not_active Abandoned
- 1996-12-13 KR KR1019960065036A patent/KR100456708B1/en not_active IP Right Cessation
- 1996-12-16 JP JP33525896A patent/JP3597000B2/en not_active Expired - Fee Related
-
1999
- 1999-01-08 US US09/227,748 patent/US6141550A/en not_active Expired - Lifetime
-
2000
- 2000-04-03 US US09/541,301 patent/US6868274B1/en not_active Expired - Fee Related
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100358385C (en) * | 1999-03-19 | 2007-12-26 | 三星电子株式会社 | Data transmitting and receiving apparatus and method for a digital mobile station |
| US7603132B2 (en) | 1999-03-19 | 2009-10-13 | Samsung Electronics Co., Ltd. | Data transmitting and receiving apparatus and method for a digital mobile station |
| EP1103888A1 (en) * | 1999-11-26 | 2001-05-30 | Siemens Aktiengesellschaft | Method for the transmission and display of information on a wireless communication unit |
| EP1107618A2 (en) * | 1999-11-30 | 2001-06-13 | Samsung Electronics Co., Ltd. | Method of transmitting and receiving multimedia data using short message service in portable radio telephone |
| EP1107618A3 (en) * | 1999-11-30 | 2002-04-17 | Samsung Electronics Co., Ltd. | Method of transmitting and receiving multimedia data using short message service in portable radio telephone |
Also Published As
| Publication number | Publication date |
|---|---|
| US6141550A (en) | 2000-10-31 |
| JPH09200268A (en) | 1997-07-31 |
| US6868274B1 (en) | 2005-03-15 |
| KR970055840A (en) | 1997-07-31 |
| US6108530A (en) | 2000-08-22 |
| KR100456708B1 (en) | 2004-12-23 |
| JP3597000B2 (en) | 2004-12-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2190305A1 (en) | System and method for transmitting a displayable message to a short message entity in more than one data package | |
| US7616639B2 (en) | Transmitting and receiving control protocol data unit having processing time information | |
| EP0989704A2 (en) | Method and apparatus for fragmenting messages for a wireless network using group sharing of reference numbers | |
| KR100447162B1 (en) | Method for length indicator inserting in protocol data unit of radio link control | |
| KR101298407B1 (en) | Method and apparatus for transmitting data packet, and method and apparatus for receiving data packet | |
| US6795435B1 (en) | Method for transmitting data transmission flows | |
| US5936967A (en) | Multi-channel broadband adaptation processing | |
| KR100222222B1 (en) | Data processing method for efficient transporting multimedia packets over conventional digital packet switching system | |
| EP1047243A2 (en) | Method for the transmission of multimedia messages | |
| EP0777394A1 (en) | Method and apparatus for electronic mail transmission as short messages towards a mobile radio terminal | |
| US20020013154A1 (en) | Method for generating multimedia events using short message service | |
| EP1088461A2 (en) | A method for delivering messages in a wireless communications system using the same protocol for all types of messages | |
| US7136396B2 (en) | Method and apparatus for compiling a protocol data unit | |
| KR100257563B1 (en) | Method for processing sms service of pcs | |
| US7684811B2 (en) | Method for transmitting short messages | |
| FI112141B (en) | Non-transparent data transfer in a mobile network | |
| KR100742437B1 (en) | System and method for providing indication of maximum teleservice payload size in a wireless communication network | |
| IES20000432A2 (en) | Adaptation of WAP to SMS in PDC networks | |
| WO2012004780A1 (en) | A message router for concatenated sms | |
| WO2000049825A1 (en) | A transaction orientated data transport mechanism for use in digital cellular networks | |
| GB2401219A (en) | Mobile subscriber database with the value of a sort byte representing the digit length of a variable length key | |
| CN1666546A (en) | Mms message transfer method and system | |
| KR100426774B1 (en) | How to handle supplementary service messages at the exchange | |
| EP1162776A1 (en) | Method of measuring the block error rate | |
| KR20010008721A (en) | Method for transmitting/receiving long size data message in cordless exchange system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued | ||
| FZDE | Discontinued |
Effective date: 20040301 |