|Publication number||US7274926 B1|
|Application number||US 10/089,623|
|Publication date||Sep 25, 2007|
|Filing date||Aug 17, 2000|
|Priority date||Oct 1, 1999|
|Also published as||DE19956023A1, DE20024015U1, DE20024016U1, DE50012027D1, EP1222782A1, EP1222782B1, EP1610511A1, EP2262192A2, EP2262192A3, WO2001026310A1|
|Publication number||089623, 10089623, PCT/2000/2780, PCT/DE/0/002780, PCT/DE/0/02780, PCT/DE/2000/002780, PCT/DE/2000/02780, PCT/DE0/002780, PCT/DE0/02780, PCT/DE0002780, PCT/DE002780, PCT/DE2000/002780, PCT/DE2000/02780, PCT/DE2000002780, PCT/DE200002780, US 7274926 B1, US 7274926B1, US-B1-7274926, US7274926 B1, US7274926B1|
|Inventors||Josef Laumen, Joerg Reinecke, Frank Schange, Gunnar Schmidt|
|Original Assignee||Robert Bosch Gmbh|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (18), Non-Patent Citations (8), Referenced by (47), Classifications (41), Legal Events (9)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates to a method of telecommunication between at least one main station and one terminal, and to a matching device.
Methods of telecommunication between one main station and one terminal are conventional.
In the so-called Internet e-mail Service, messages are created by a so-called mail client and are transmitted via the Internet to a mail server of a recipient using the so-called SMTP (simple mail transfer protocol) according to RFC 821 (request for command) of the IETF (Internet Engineering Task Force), or using the ESMTP (enhanced simple mail transfer protocol) according to RFC 1869 of the IETF. The recipient can access the transmitted message from the mail server, also with the aid of a mail client. Appropriate protocols are used for access to the transmitted message, for instance, POP (post office protocol) according to RFC 1729 of IETF, or IMAP (Internet message access protocol) according to RFC 2060 of IETF, or even protocols specific to manufacturers. These protocols regulate the exchange of messages between the recipient and the mail server, such as, for instance, the logging on of a mail client to the mail server, authentication of the mail client, etc. For transmission of messages from mail server to mail client, SMTP or ESMTP are generally used. In order to register new messages on the mail server, the mail client checks the mail server sporadically or regularly. This procedure is called polling. If the mail client detects messages present on the mail server for the user of the mail client, it signals this to the user. The user can then initiate access to the message stored for him on the mail server. The initiation of access is also called pull mode. The message is then transmitted from mail server to mail client and can be reproduced there for the user. The method described here is intended essentially for dedicated connections, where the mail client has a permanent connection to the e-mail server, or a connection with relatively brief interruptions. SMTP was originally provided for text messages, by the use of MIME (multipurpose Internet mail extensions) according to RFC 1521 of IETF, such messages can be expanded by attachments. In this connection, the attachments can have any format desired, and are not limited to text messages. However, for transmission, these messages are recoded so that they can also be transmitted in the form of simple text messages.
The SMS service (short message service) according to the GSM standard (global system for mobile communications), GSM 03.40 ETSI differs fundamentally from the internet e-mail service described. It is limited exclusively to text messages having a maximum length of 160 characters, there being (the possibility of) expansions by concatenation of a plurality of such text messages. The SMS service is further based on transmitting the text message from an SMS transmitter to an SMS server, which then automatically transmits it to a mobile terminal. This method is also denoted as push mode. If the mobile terminal in the mobile radio network is not available, for instance, because it is switched off, the message is stored temporarily in the SMS server. Following that, when the mobile terminal can be reached again, this is signaled to the SMS server, and it automatically begins transmission of the text message to the mobile terminal.
According to an example embodiment of the present invention, the message exchange by a matching device between at least one main station and the terminal may be controlled in dependence on at least one input from the terminal or from the at least one main station. The use of the matching device may make possible the matching of main stations or servers of various services to one terminal, without having to establish a direct connection between the terminal and each respective main station, and without it being necessary to transmit between terminal and each respective main station service-specific protocols and thus different protocols depending on the main station involved. According to the example embodiment of the present invention, the respective main station is not visible to the terminal; only the matching device is visible. Thus, various services for message exchange between terminal and various main stations may be integrated by the matching device, so that a uniform message exchange between the terminal and the matching device becomes possible for the implementation of various services. In the case where only one single main station is connected to the matching device, and the case where a plurality of main stations are connected to the matching device, the matching device may match the message exchange between each respective main station and the terminal to inputs from the user of the terminal, to the properties and capability of the terminal or to inputs from the respective main station. In this manner, the message exchange may be individually and flexibly optimized in dependence upon user inputs or equipment properties for each connection to be established between a main station and a terminal.
By the use of the matching device, service-specific features for the message exchange between the terminal and the respective main station may be canceled out and replaced by user-specific features, which, for transmission of messages to the terminal, may be defined by an input from the terminal, or rather, the user of the terminal.
A transmitting mode independent of the service used may be input by the user of the terminal, so that by means of the matching device, for example, even in SMS service a pull mode may be realized, and in Internet e-mail service a push mode may be realized.
A plurality of messages, from different main stations for example, may be transmitted jointly by the matching device to the terminal in different modes. In this manner, clarity upon receipt of the messages may be enhanced for the user, and it avoids having to activate the terminal several times for receiving messages from various main stations.
The matching device may segment individual parts of a message which includes a plurality of elements and processes them, depending upon the input from the terminal. In this manner, automatic, user-individual preprocessing of such messages may be implemented which requires no input from the user at the terminal, as long as the input for processing of such messages is not to be changed.
A plurality of different data records may be input by a user of the terminal for various functionalities implementable using the terminal, and may be stored in a storage device assigned to the matching device. In this manner, one may match the message exchange between each main station and the terminal to the properties and the capability of various terminal configurations via the matching device. Due to the storage of the data records in the storage device, the data records may not have to be transmitted each time a connection is established between the terminal and the matching device, but only have to be selected in the storage device, which may save transmitting capacity.
The terminal user may select a data record. The terminal may transmit the characterizing identification character of the selected data record to the matching device. A check is performed in the matching device. A data record including the identifying character received may be stored in the storage device. If the data record associated with the identifying character received is present in the storage device, then this data record may be selected. In this manner, only the appropriate identifying character may have to be transmitted from the terminal to the matching device for the selection of the desired data record, so that the data volume required to be transmitted for the selection of the desired data record may be minimized, and the transmitting capacity may be impaired as little as possible.
The data records may be numbered in the sequence in which they are stored in the storage device, the identifying character of the data records may be formed in each case from this numbering. This may provide a very simple and not very costly possibility to form identifying characters, the identifying characters thus may be formed in each case formed as a number, and therefore may require an especially low quantity of transmitting capacity for their transmission.
An example embodiment of the present invention is represented in the drawings and explained in detail in the following description.
Within the framework of standardization of UMTS (universal mobile telecommunications system) a multimedia messaging system (MMS) has currently been specified according to publication “Multimedia Messaging Service, Functional Description”, 3GPP TS 23.140, v.0.1.0., 3GPP Technical Subgroup Terminals 1999-10. MMS is a service which, starting from today's SMS service in GSM (SMS: short message service; GSM: global system for mobile communications) is supposed to make possible sending and receiving of messages using, for example, a terminal 5 formed as a mobile phone.
Today's SMS service is limited to a maximum of 160 characters per message, and only text can be transmitted, that is, there exists a limited character set that can be used.
In contrast to an SMS, an MM (multimedia message) is not to be limited either to a certain length or to text representation. Instead, MM is supposed to support multiple media types.
In the MMS service, a matching device denoted as MMS relay has a central function. This element may be connected, via media of the greatest difference, to different kinds of main stations 1, 2, 3 denoted as servers or service providers, such as an e-mail server, fax server, voice mailbox, MMS server or the like, as illustrated in
Thus, via MMS relay 15, the user of terminal 5 may have access to his e-mails lying in an e-mail server, to faxes “waiting” for him on a fax server, and to voice messages recorded for him on a voice mailbox.
Aside from the receipt of messages, however, it is also intended that the user may be able to write messages and send these to the desired recipient via MMS relay 15.
Referring now to
In addition, a first interface 11, a second interface 12 and a third interface 13 may be connected to control unit 30. A first main station 1 may be connected to matching device 15 via first interface 11. A second main station 2 may be connected to matching device 15 via second interface 12. A third main station 3 may be connected to matching device 15 via third interface 13.
In this connection, each of main stations 1, 2, 3 may provide one or more services. The services provided by main stations 1, 2, 3 thus differ from one another in the example embodiment described here. In order to be able to use a service from one of main stations 1, 2, 3, terminal 5 does not have to establish in each case a service-specific connection to the appropriate main station. Rather, terminal 5 establishes a connection to matching device 15, for each service to be used, and it converts the various services of main stations 1, 2, 3 into a uniform style for terminal 5. This uniform style may be input by terminal 5 or rather the user of terminal 5, and may be transmitted by terminal in the form of a data record via telecommunications network 10 to matching device 15, and stored in storage device 25.
In the following, assume the first main station 1 is provided, for example, for an electronic postal service, such as e-mail. Assume the second main terminal 2 is provided, for instance, for an SMS service. Assume, the third main station 3 is provided, for instance, for a fax mail service. Now, for example, assume the input from terminal 5 is stored in storage device 25, such that messages from matching device 15 to terminal 5 are to be transmitted in the form of SMS messages. In another example embodiment, in a corresponding manner in the opposite direction, SMS messages in the form of e-mail could also be transmitted by matching device 15 to terminal 5. Furthermore, the input of terminal 5 stored in storage device 25 may provide that the messages are transmitted in the pull mode described from matching device 15 to terminal 5, that means, then, only at the prompting of terminal 5. A message received in first main station 1 for terminal 5 may be recognized by control device 30, on account of appropriate signaling from first main station 1. Subsequently, matching device 15 signals terminal 5 via telecommunications network 10 that there is a message for terminal 5 in first main station 1. By sending an appropriate prompting signal via telecommunications network 10, terminal 5 may thereafter prompt matching device 15 to transmit the message present in first main station 1. At the detection of this prompting signal, control unit 30 induces first main station 1 to transmit the message present for terminal 5. If, for example, this message is present as e-mail, control unit 30 recognizes this. According to the input from terminal 5 stored in storage device 25, control unit 30 converts the e-mail message to one or more SMS messages, depending on the length of the e-mail message. This SMS message or these SMS messages may, as necessary, also be stored temporarily in storage device 25 via telecommunications network 10, when terminal 5 is temporarily inaccessible. Transmission of the SMS message or of the SMS messages by matching device 15 to terminal 5 then occurs when terminal 5 is accessible, and, as described, on the assumption that the prompting signal was detected by control unit 30.
In a corresponding manner, control device 30 converts a fax message received by third main station 3 via third interface 13 to one or more SMS messages, and sends these, after prompting by terminal 5, via fourth interface 20 and telecommunications network 10 to terminal 5.
An SMS message received at matching device 15 from second main station 2 via second interface 12 may be recognized as such by control unit 30, and thus may not need to be converted, but may, after prompting by terminal 5, be transmitted, in the pull mode described, via fourth interface 20 and telecommunications network 10 to terminal 5.
In corresponding fashion, control device 30 may recognize messages that were received from terminal 5 via telecommunications network 10 and fourth interface 20 at matching device 15, and convert them, according to an input from a main station addressed by these messages, to a format requested by this main station and transmit them to this main station, e.g., text to voice mail or text to fax. In this connection, the inputs made by the respective main stations may also be stored in storage device 25. The inputs of a plurality of main stations may also be stored there.
With the aid of
The MMS server and MMS relay 15 may not necessarily have to be separated from each other as illustrated in
In this context, MMS relay 15 performs a matching of the message exchange between the MMS server and the MMS client. In this context, for one message which is to be sent from the MMS server to the MMS client, the second protocol layer sequence 40 of MMS relay 15 may be run through from bottom to top. Subsequently a change of form of the message occurs in MMS relay 15, according to the input of terminal 5. Thereafter, the message thus changed in form runs through the first protocol layer sequence 35 of MMS relay 15, assigned to air interface Uu, from top to bottom, so that the message may be dispatched to the MMS client. The protocol and message conversion runs correspondingly in the opposite direction for messages to be transmitted from MMS client via MMS relay 15 to MMS server. The protocol layer sequence of second main station 2 and third main station 3 may each be distinguished the protocol layer sequence of first main station 1 as in
The functions to be performed by MMS relay 15 may be subdivided into several groups. A first group of such functions may make possible the integration of different services or different MMS servers by matching device 15. The MMS servers of different services, such as e-mail, voice mail or fax send their messages via MMS relay 15, which converts these messages into the same form, to terminal 5. In this case it may be necessary to convert different data formats, such as fax format to graphics format. However, it may also be necessary, additionally or alternatively, to convert the data type of such a message, for instance, to transcribe a text message into a voice mail message, so that the text message may be reproduced acoustically at terminal 5.
A second group of functions in MMS relay 15 may be necessary for determining whether terminal 5 may be reached by matching device 15 via telecommunications network 10. For this, it may be necessary for MMS relay 15 to have a connection to a further message element, such as an HLR (home location register), in order to receive information as to whether terminal 5 is logged on or available in telecommunications network 10. If the respective terminal 5 cannot be reached, the message to be communicated may be stored in storage device 25. As soon as terminal 5 may be reached again, and MMS relay 15 finds this out via the described network element, MMS relay 15 automatically continues the communicating process previously broken off by storing the message.
A third group of functions relates to the transmission mode to be set for transmitting messages from matching device 15 to terminal 5. Here, it should be possible, on the one hand, to transmit messages directly from matching device 15 to terminal 5 in push mode. On the other hand, it may be possible for terminal 5 only to be informed by matching device 15 that a message for terminal 5 is stored in matching device 15 or in one of associated main stations 1, 2, 3. These messages may then be retrieved at terminal 5 via matching device 15 or may be passed on to another mail system. This transmission mode corresponds to the pull mode described. The user of terminal 5 may preselect by a data record which transmission mode may be used for which message or which data type of message, and he may send this data record to matching device 15 for storage in storage device 25. Such a data record is also described as a profile. When MMS relay 15 recognizes the receipt of a new message for terminal 5 in one of main stations 1, 2, 3, or when this is signaled to MMS relay 15 by one of main stations 1, 2, 3, MMS relay 15 checks, in dependence upon the profile inputs stored in storage device 25, in which transmission mode the message is to be transmitted to terminal 5, such as whether in push or in pull mode. In accordance with the input transmission mode, the transmission of the message to terminal 5 may then be controlled by control device 30.
A further group of functions of matching device 15 relates to segmenting or combining messages. Messages may be composed of several elements, such as e-mail, which may have different attachments. MMS relay 15 may treat each element of a message individually, that is, under certain circumstances it may pass on individual elements of the message to terminal 5, store others in storage device 25, cancel yet others, or send them on to another mail system. This method is denoted as segmentation of messages. Correspondingly, a message may be newly combined, for example, from message elements from different main stations 1, 2, 3. Here, for instance, all new elements input into main stations 1, 2, 3 which are to be transmitted to terminal 5 in push mode, and all new elements input into main stations 1, 2, 3 which are to be transmitted to terminal 5 in pull mode are combined, in each case, and are transmitted in the respective transmission mode to terminal 5. All message elements which are supposed to be sent to the same address, for instance, passed on in a different mail system, may be combined into a single message and passed on to this mail system. Now, whether messages from different main stations should be combined to a common message, if they are to be transmitted to terminal 5 using the same transmission mode, may also be specified in a user-defined profile. The same goes for segmentation of a message of several message elements which was received from a single main station for terminal 5. In this context, it may be specified by the user of terminal 5, with the aid of a profile, which data types or data formats of message elements of such a message are to be treated individually in which of the described forms. For example, all message elements in a video format may be passed on to another terminal in another mail system which may be in a position to reproduce the video data. Message elements having text messages may be provided in this example, for dispatching to terminal 5 according to profiles, and message elements in fax form may be provided according to profiles, in this example, for storage in storage device 25 for later retrieval.
A message for terminal 5, input in a respective manner, for example, in first main station 1, having such attachments or message elements, may then be segmented according to the specifications in the user-defined profile stored in storage device 25, in order to be able to process the individual message elements of this message according to the specifications of the profile as described.
In general, the user-defined profile may be a data record which may be determined by the user of terminal 5 and may be stored in storage device 25 of MMS relay 15. It determines the behavior of MMS relay 15 and specifies which messages or message elements are transmitted directly or after retrieval, i.e., in push or pull mode, to terminal 5, which messages or message elements are automatically passed on to another mail system or cancelled, which messages or message elements are converted to another format, etc. In order to be able to perform the processing provided with the aid of profiles for the messages or message elements, these messages or message elements must be able to be differentiated from one another and identified. Differentiating features for identifying the messages or message elements are, for example, data type, that is, fax, voice mail, e-mail, SMS, etc., and the length of the messages or the message elements. In this connection, data type and length of the messages or the message elements may be ascertained by control unit 30 in a suitable manner, for instance, by evaluating the header information having the necessary specification, which is attached to the messages or the message elements. The profile may also contain specifications specific to a terminal, which may not be influenced by the user, and which specify the resources available to terminal 5, for instance, the graphics capability of an indicator device of terminal 5, the storage capacity of terminal 5 or the like as boundary conditions. However, it may also be provided that the user himself specifies which of the functionalities that may be implemented with terminal 5 are to be taken up into the profile. It is already known from the publication “Composite Capability/Preference Profiles (CC/PP): A User Side Framework for Content Negotiation”, W3C Note, Jul. 27, 1999, how a user may determine and change his profile.
Several such profiles may also exist, so as, for example, to give general consideration to capabilities of different indicator devices of terminal 5, or capabilities of different terminal configurations, which may result from the fact that external components such as their own indicator devices may be connected to terminal 5. Such an external component may be, for example, a laptop.
The settings for the current profile, depend on the functionalities of terminal 5, which may be currently available to the user. Even more than today, in the future a mobile user will be able to connect external equipment to his mobile terminal 5 developed, for instance, as a mobile phone or mobile radio, in order to vary, in such a manner, the implementable performance capabilities, using terminal 5, depending on need or what is offered. For reasons of mobility, size of the devices and stand-by time, many mobile radio devices will only offer basic functionalities, even in future. However, the user may broaden these functionalities, for example, by coupling an electronic notebook or an electronic organizer to mobile terminal 5.
If the user of terminal 5 wants to undertake changes in the current profile, the publication “Composite Capability/Preference Profiles (CC/PP): A User Side Framework for Content Negotiation” offers for this a bandwidth-efficient solution. Via telecommunications network 10, developed as a mobile radio network in this example, mobile terminal 5 transmits only the changes with respect to the previous profile to storage device 25, which may also be denoted as profile database, and which may also be arranged outside matching device 15, in connection with it and assigned to it. However, storage device 25 may also be positioned in matching device 15, as illustrated in
According to the present invention, the user of terminal 5 may be permitted the use of several, or any number of different profiles. Depending on which external devices the user connects to his mobile terminal 5, that is, depending on which functionalities may be currently available to him, he should then be able to select a suitable profile from a list of his profiles.
For this purpose, the list having the different profiles is stored in profile database 25. In each of these profiles, the user determines which functionalities are available to him and which properties the MMS service is to have with this profile.
The user may give each of these profiles a profile name that is as unique and as declarative as possible. In addition, between mobile terminal 5 and profile database 25, identifying characters, such as in the form of numbers, may be agreed upon for each of these profiles, so that a definite map of an identifying character may be possible for a profile name of each profile and thus for the content of the corresponding profile. A simple manner of agreeing on such identifying characters between mobile terminal 5 and profile database 25 is, for example, to number them in the sequence in which they were stored in profile database 25. All the profiles input by the user of mobile terminal 5 may be transmitted in an initializing phase from terminal 5 via telecommunications network 10 to matching device 15 or rather profile database 25 and stored in profile database 25, for instance, in the sequence of their arrival. Additional profiles defined and input by the user may also be transmitted at a later point in time from terminal 5 to profile database 25, in the manner described, and may there be stored, for instance, in the sequence of their arrival.
Thus, for example, the user of a terminal 5 developed as a GSM mobile radio device may determine a first profile to which he gives the name “pure GSM (SMS only)”. In this profile he will then determine that his GSM mobile radio device 5 only supports SMS, and that, therefore, he does not want e-mails present for him on an Internet e-mail server to be sent to him automatically, but in this case rather have them left on the Internet e-mail server. The same applies to other messages, different from SMS messages, present for the user, which he also wants to remain stored in the respective servers.
The user may apply a second profile for the case in which he connects an electronic organizer to his GSM mobile radio device 5. On the organizer he now also has a calendar functionality which may access an organizer server, via mobile radio network 10 and MMS relay 15. In general, any desired number of servers or main stations, respectively, may be connected to matching device 15 in the manner described in
He may apply a third profile for the case in which he connects an electronic notepad to his GSM mobile radio device 5. On the electronic notebook he now has several possibilities or applications. Therefore, in the third profile, which he calls, for instance, “GSM+notebook”, he sets the following: With mobile terminal 5 thus broadened, not only SMS and calendar functionalities may be implemented, but also, for example, e-mail and fax. Since, generally only urgent and important information may be sent to him by fax, but he gets all kinds of messages by e-mail, he determines, for instance, in profile 3 that messages in SMS, calendar and fax formats are to be automatically sent to him, but e-mails are to remain on the Internet e-mail server. Messages of other types, which differ from the types of messages named, should also remain stored on the assigned server.
In a fourth profile, the user of mobile terminal 5 will consider the case, for instance, that he is not traveling in his home network but is staying outside the country, for example. In such a case, the applicable roaming fees may be too high, so that he may indeed wish to continue to receive SMS messages, but only wants to be informed by SMS concerning incoming calendar messages or faxes, without those being automatically delivered. E-mails and messages of other message types, which differ from the types of messages named, should also remain stored on their associated server.
When beginning to use SMS service, according to the present invention, the user needs further only to select that profile, on his list having profile names, which may be stored in mobile terminal 5, and which corresponds to his wishes and the current functionalities of mobile terminal 5, or the additional current external devices or components that are currently connected. In mobile terminal 5 this selection, this profile name is then mapped on the respective identifying character. This identifying character is then the only thing that has to be transmitted from mobile terminal 5 to MMS relay 15 via the air interface, or rather mobile radio network 10, in order to start MMS service as desired. Because, via this identifying character, MMS relay 15 may obtain the setting for the profile associated with the identifying character in profile database 25.
A user may have to set the capabilities of his terminal 5, or the possible combination of devices in the form of external additional devices or components connected to terminal 5, and his desired configuration of the MSS servive, only one single time or may allow MSS relay 15 to set them at profile database 25. If there is a change in the device combination and/or in his wishes, he only has to select the matching profile from the list.
In each case from the identifying character of the profiles, according to one embodiment of the present invention, it is not the information on the difference from the previous profile that has to be transmitted via the air interface, but only the identifying character of the desired profile. This may save data, and thus, resources on the mobile radio channel in mobile radio network 10, and may speed up the setting of the MMS service.
In MMS relay 15, data type conversions and/or data format conversions are also performed as described. In dependence upon the inputs of the user-defined profile or upon terminal-specific standard inputs, messages or message elements which are present in one of main stations 1, 2, 3 for terminal 5 in a first data type, such as a fax or as text, are changed to another data type, such as fax to graphic, or text to voice. Correspondingly, a message present in a first data format may be converted by MMS relay 15 into a second data format. For example, a GIF graphic (graphic interchange format) may be converted into a JPEG graphic (joint picture expert group), or the text of a first alphabet may be converted into the text of a second alphabet.
It may be provided that MMS relay 15 notifies terminal 5 if new messages or message elements are not automatically passed on to terminal 5, for example, according to the pull mode. To this effect, notification of terminal 5 may be done by MMS relay 15 if messages or message elements, depending on the input of the profile or profiles, are automatically passed on to another mail system or are cancelled.
MM transfer protocol I between MMS relay 15 and MMS client may include, besides the functions for the transmission of a message from matching device 15 to terminal 5, three functional elements: 1) the possibility of establishing a connection from MMS relay 15 to terminal 5, in order to implement the push mode; 2) the possibility of establishing signaling from MMS relay 15 to terminal 5, in order to notify terminal 5 of a message present in one of main stations 1, 2, 3, in order to implement the pull mode; and 3) the possibility of establishing a connection from terminal 5 to MMS relay 15, in order to retrieve a message for terminal 5 stored in one of main stations 1, 2, 3, and thereby to complete the pull mode or to send messages.
The present invention is described below, in light of three different example embodiments. Starting from
In the first example embodiment according to
If terminal 5 cannot be reached via communications network 10, those message elements may also be stored, for example, in storage device 25 of MMS relay 15, which are to be transmitted to terminal 5 in push mode. Correspondingly, notifications may be stored intermediately in storage device 25 of MMS relay 15, which have to be transmitted by MMS relay 15 to terminal 5 with respect to message elements that are not to be transmitted in push mode. The storage of the message elements which are to be transmitted in push mode and/or of the notifications continues until MMS relay 15 is notified, for example, by the HLR that terminal 5 may now be reached via telecommunications network 10. Thereafter, transmission of message elements in push mode or of notifications to terminal 5 may be continued. The storage of message elements and/or notifications may occur in this example in the Internet e-mail server or in MMS relay 15.
Besides the transmission modes, the profile regulates, for instance, conversions of data formats of messages, as is described above. If terminal 5 supports only the JPEG data format in the case of graphics, this may be entered in the profile according to the standard, and MMS relay 15 may automatically convert all graphics message elements received for terminal 5 to JPEG format.
According to the first embodiment, POP is used as an example. Alternatively, the IMAP (Internet message access protocol) or other protocols available for this purpose could also be used.
Starting from the first example embodiment as in
In this connection,
Common to all implementations is the uniform service functionality from the point of view of the MMS client, which may be ensured by MMS relay 15, MMS relay 15 being developed either as a separate protocol element or as being functionally integrated with the MMS server.
Several terminals may be connected to fourth interface 20 in the manner described, so that MMS relay 15 may be used in the manner described for several terminals at the same time, at least one profile of each of the connected terminals may be stored in storage device 25 in the manner described.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5377354||Jun 8, 1993||Dec 27, 1994||Digital Equipment Corporation||Method and system for sorting and prioritizing electronic mail messages|
|US5742668||Jun 6, 1995||Apr 21, 1998||Bell Communications Research, Inc.||Electronic massaging network|
|US5842210 *||Oct 30, 1996||Nov 24, 1998||Motorola, Inc.||Method and apparatus for selectively retrieving data from a database in a data communication system|
|US5895471 *||Dec 22, 1997||Apr 20, 1999||Unwired Planet, Inc.||Providing a directory of frequently used hyperlinks on a remote server|
|US5903845 *||Jun 4, 1996||May 11, 1999||At&T Wireless Services Inc.||Personal information manager for updating a telecommunication subscriber profile|
|US5917897 *||Jan 6, 1998||Jun 29, 1999||Summit Telecom System, Inc.||System and method for controlling a telecommunication network in accordance with economic incentives|
|US5958018 *||Oct 30, 1996||Sep 28, 1999||Lucent Technologies Inc.||Wireless services data network translating mac address to asynchronous transfer mode (ATM) address|
|US6023700 *||Jun 17, 1997||Feb 8, 2000||Cranberry Properties, Llc||Electronic mail distribution system for integrated electronic communication|
|US6088594 *||Nov 26, 1997||Jul 11, 2000||Ericsson Inc.||System and method for positioning a mobile terminal using a terminal based browser|
|US6138158 *||Apr 30, 1998||Oct 24, 2000||Phone.Com, Inc.||Method and system for pushing and pulling data using wideband and narrowband transport systems|
|US6243739 *||Dec 22, 1997||Jun 5, 2001||Phone.Com, Inc.||Reducing perceived latency in servicing user requests on low-bandwidth communication channels|
|US6370389 *||Oct 30, 1998||Apr 9, 2002||Nokia Mobile Phones, Ltd.||Communication network terminal supporting a plurality of applications|
|US6466783 *||Jun 8, 1998||Oct 15, 2002||Openwave Systems Inc.||Visual interface to mobile subscriber account services|
|US6473609 *||Sep 14, 1998||Oct 29, 2002||Openwave Systems Inc.||Method and architecture for interactive two-way communication devices to interact with a network|
|US6560640 *||Jan 22, 1999||May 6, 2003||Openwave Systems, Inc.||Remote bookmarking for wireless client devices|
|US6947738 *||Dec 21, 2001||Sep 20, 2005||Telefonaktiebolaget Lm Ericsson (Publ)||Multimedia messaging service routing system and method|
|EP0924946A1||Dec 8, 1998||Jun 23, 1999||Siemens Aktiengesellschaft||Telecommunications system and method for information exchange between an E-mail service and a subscriber in a telecommunications network|
|GB2328110A||Title not available|
|1||Composite Capability/Preference Profiles (CC/PP): A User Side Framework for Content Negotiation, W3C Note, (Jul. 27, 1999).|
|2||Livre Mouly et Paulet, pp. 560 and 563.|
|3||Multimedia Messaging Service , Functional Description, 3GPP TS 23.140, v.0.1.0., 3GPP Technical Subgroup Terminals (Oct. 1999).|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7362700||Jun 27, 2002||Apr 22, 2008||Extreme Networks, Inc.||Methods and systems for hitless restart of layer 3 packet forwarding|
|US7483370 *||Dec 22, 2003||Jan 27, 2009||Extreme Networks, Inc.||Methods and systems for hitless switch management module failover and upgrade|
|US7630705 *||Jun 30, 2003||Dec 8, 2009||Motorola, Inc.||Message format conversion in communications terminals and networks|
|US7653573 *||Dec 17, 2004||Jan 26, 2010||Accenture Llp||Customer messaging service|
|US7817987 *||Mar 7, 2006||Oct 19, 2010||Motorola, Inc.||Apparatus and method for handling messaging service message adaptation|
|US8000682||Dec 16, 2009||Aug 16, 2011||At&T Intellectual Property I, L.P.||Apparatus and method for restricting access to data|
|US8050660 *||Mar 7, 2006||Nov 1, 2011||Motorola Mobility, Inc.||Apparatus and method for handling messaging service message adaptation|
|US8073474 *||Mar 23, 2007||Dec 6, 2011||Zumobi, Inc.||Systems and methods for controlling group messaging|
|US8243893 *||Jan 19, 2010||Aug 14, 2012||Accenture Global Services Limited||Customer messaging service|
|US8243908||Dec 12, 2006||Aug 14, 2012||At&T Intellectual Property I, Lp||Systems and methods for restricting the use and movement of telephony devices|
|US8249570 *||Jul 16, 2010||Aug 21, 2012||At&T Intellectual Property I, L.P.||Apparatus, method, and computer-readable medium for interfacing devices with communications networks|
|US8275371||Dec 18, 2009||Sep 25, 2012||At&T Intellectual Property I, L.P.||Apparatus and method for providing communications and connection-oriented services to devices|
|US8416804||Apr 14, 2010||Apr 9, 2013||At&T Intellectual Property I, L.P.||Apparatus and method for providing a user interface for facilitating communications between devices|
|US8504625 *||Sep 27, 2008||Aug 6, 2013||T-Mobile International Ag||Method for transmitting messages using the multimedia message service (MMS)|
|US8526466||Sep 2, 2010||Sep 3, 2013||At&T Intellectual Property I, L.P.||Apparatus and method for prioritizing communications between devices|
|US8543098 *||Dec 16, 2009||Sep 24, 2013||At&T Intellectual Property I, L.P.||Apparatus and method for securely providing communications between devices and networks|
|US8554187||Aug 11, 2010||Oct 8, 2013||At&T Intellectual Property I, L.P.||Apparatus and method for routing communications between networks and devices|
|US8583106||Dec 7, 2007||Nov 12, 2013||At&T Intellectual Property I, L.P.||Cellular docking station|
|US8583748 *||Sep 1, 2010||Nov 12, 2013||At&T Mobility Ii, Llc||Method and apparatus for messaging service internetworking|
|US8731097||Jun 2, 2003||May 20, 2014||Siemens Aktiengesellschaft||Transmission of mms messages with the conversion of data types and/or data formats|
|US8885666||Apr 8, 2013||Nov 11, 2014||At&T Intellectual Property I, L.P.||Apparatus and method for providing a user interface for facilitating communications between devices|
|US9258845||Nov 11, 2013||Feb 9, 2016||At&T Intellectual Property I, L.P.||Cellular docking station|
|US9411505||Dec 30, 2011||Aug 9, 2016||Apple Inc.||Single-handed approach for navigation of application tiles using panning and zooming|
|US9495144||Dec 8, 2014||Nov 15, 2016||Apple Inc.||Systems and methods for controlling application updates across a wireless interface|
|US20040001485 *||Jun 27, 2002||Jan 1, 2004||Frick John Kevin||Methods and systems for hitless restart of layer 3 packet forwarding|
|US20040266411 *||Jun 30, 2003||Dec 30, 2004||Galicia Joshua D.||Message format conversion in communications terminals and networks|
|US20050059382 *||Jul 23, 2004||Mar 17, 2005||Arnaud Brun||Method and a system for submitting a message deposited in an in-box of a messaging service|
|US20050165658 *||Dec 17, 2004||Jul 28, 2005||Accenture Llp, An Illinois Limited Liability Partnership||Customer messaging service|
|US20050174261 *||Jun 2, 2003||Aug 11, 2005||Josef Laumen||Transmission of mms messages with the conversion of data types and/or data formats|
|US20050275406 *||Jun 15, 2004||Dec 15, 2005||Hatalkar Atul N||Apparatus and method of dynamic usage profile acquisition and utilization in a wireless mobile device|
|US20070213076 *||Mar 7, 2006||Sep 13, 2007||Mian Mubashir A||Apparatus and method for handling messaging service message adaptation|
|US20070213077 *||Mar 7, 2006||Sep 13, 2007||Mian Mubashir A||Apparatus and method for handling messaging service message adaptation|
|US20080016144 *||Jul 27, 2006||Jan 17, 2008||Samsung Electronics Co., Ltd.||Method for providing information service and push mode service|
|US20080192768 *||Dec 30, 2005||Aug 14, 2008||Steven Tischer||Apparatus, method, and computer-readable medium for interfacing communication devices|
|US20080194208 *||Dec 30, 2005||Aug 14, 2008||Steven Tischer||Apparatus, method, and computer-readable medium for communicating between and controlling network devices|
|US20080194225 *||Dec 30, 2005||Aug 14, 2008||Steven Tischer||Apparatus and method for providing emergency and alarm communications|
|US20080207178 *||Dec 30, 2005||Aug 28, 2008||Steven Tischer||Apparatus and method for restricting access to data|
|US20080207179 *||Dec 30, 2005||Aug 28, 2008||Steven Tischer||Apparatus and method for testing communication capabilities of networks and devices|
|US20080207197 *||Dec 30, 2005||Aug 28, 2008||Steven Tischer||Apparatus, method, and computer-readable medium for interfacing devices with communications networks|
|US20080220775 *||Dec 30, 2005||Sep 11, 2008||Steven Tischer||Apparatus, method, and computer-readable medium for securely providing communications between devices and networks|
|US20100183125 *||Jan 19, 2010||Jul 22, 2010||Hayes Jr Marc F||Customer messaging service|
|US20100281120 *||Sep 27, 2008||Nov 4, 2010||Roebke Matthias||Method for transmitting messages using the multimedia message service (mms)|
|US20120053932 *||Aug 8, 2011||Mar 1, 2012||Claus Rist||Method and System for Automatic Transmission of Status Information|
|US20120054287 *||Sep 1, 2010||Mar 1, 2012||At&T Mobility Ii, Llc||Method and Apparatus for Messaging Service Internetworking|
|US20140040405 *||Oct 11, 2013||Feb 6, 2014||At&T Mobility Ii Llc||Method and Apparatus for Messaging Service Internetworking|
|WO2007103907A2 *||Mar 6, 2007||Sep 13, 2007||Motorola Inc.||Apparatus and method for handling messaging service message adaptation|
|WO2007103907A3 *||Mar 6, 2007||May 7, 2009||Naga Venkata S Korukonda||Apparatus and method for handling messaging service message adaptation|
|U.S. Classification||455/414.1, 715/864, 709/217, 455/414.2, 709/219, 715/738, 709/218, 370/349, 455/426.1, 455/419, 455/412.2, 455/412.1, 455/414.3|
|International Classification||G06F13/00, H04L29/06, H04J3/24, G06F15/16, H04M3/42, H04M3/53, H04L12/28, H04L12/58, H04M3/533, H04W28/06, H04W4/18|
|Cooperative Classification||H04L51/24, H04L51/38, H04L51/12, H04L69/24, H04L29/06, H04W28/06, H04M3/5307, H04L51/06, H04M3/533, H04L51/066, H04W4/18|
|European Classification||H04L51/06, H04L51/06B, H04L29/06, H04L12/58C2, H04W4/18, H04L12/58C|
|Jul 30, 2002||AS||Assignment|
Owner name: ROBERT BOSCH GMBH, GERMANY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LAUMEN, JOSEF;REINECKE, JOERG;SCHANGE, FRANK;AND OTHERS;REEL/FRAME:013127/0913;SIGNING DATES FROM 20020516 TO 20020521
|Jan 18, 2008||AS||Assignment|
Owner name: IPCOM GMBH & CO. KG, GERMANY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ROBERT BOSCH GMBH;REEL/FRAME:020371/0881
Effective date: 20071126
|Oct 20, 2009||RR||Request for reexamination filed|
Effective date: 20090813
|Mar 21, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Apr 3, 2013||AS||Assignment|
Owner name: KAROLS DEVELOPMENT CO LLC, NEW YORK
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IPCOM GMBH & CO. KG;REEL/FRAME:030144/0766
Effective date: 20080403
|May 7, 2013||AS||Assignment|
Owner name: KAROLS DEVELOPMENTCO LLC, NEW YORK
Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE TYPE OF DOCUMENT PREVIOUSLY RECORDED ON REEL030144, FRAME 0766. ASSIGNORS HEREBY CONFIRMS THE DOCUMENT SHOULD HAVE BEEN SUBMITTED AS A SECURITY AGREEMENT NOT AN ASSIGNMENT;ASSIGNOR:IPCOM GMBH 7 CO. KG;REEL/FRAME:030407/0253
Effective date: 20080403
|Jun 7, 2013||AS||Assignment|
Owner name: LANDESBANK BADEN-WUERTTEMBERG, GERMANY
Free format text: SECURITY AGREEMENT;ASSIGNOR:IPCOM GMBH & CO. KG;REEL/FRAME:030571/0649
Effective date: 20130607
|Nov 11, 2014||B1||Reexamination certificate first reexamination|
Free format text: CLAIMS 2-4, 7-11, 14-20 AND 22-26 ARE CANCELLED.CLAIMS 1, 5, 6, 12, 13 AND 21 ARE DETERMINED TO BE PATENTABLE AS AMENDED.NEW CLAIMS 27-34 ARE ADDED AND DETERMINED TO BE PATENTABLE.
|Mar 18, 2015||FPAY||Fee payment|
Year of fee payment: 8