GB2404112A

GB2404112A - Communications system, apparatus and method

Info

Publication number: GB2404112A
Application number: GB0310840A
Authority: GB
Inventors: Uriel Kalman Keen
Original assignee: Individual
Current assignee: Individual
Priority date: 2003-05-10
Filing date: 2003-05-10
Publication date: 2005-01-19
Also published as: GB0310840D0

Abstract

In the field of multimedia messaging, it is known to be able to send a multimedia message from a first terminal to a second terminal. However, terminals are usually only provided with a small number of limited message templates, thereby restricting the scope of what can be sent. Even though templates may be downloadable, the user of the first terminal is not free to compose a message by selecting individual media components, for example images and audio works. The present invention permits the user of a first terminal (120) to browse a WAP site to identify references relating to media components, which the user of the first terminal (120) wants to include in a multimedia message. The user of the first terminal (120) is then able to send a text-based message to a server (128), which can extract the references and retrieve the media components to which the references relate. The server (128) can then compose the multimedia message and send the multimedia message to a second terminal (124) on behalf of the first terminal (120).

Description

24041 1 2 COMMUNICATIONS SYSTEM, APPARATUS AND METHOD The present

invention relates to a communications system of the type, for example, that is capable of supporting a text-based messaging service and a multimedia messaging service. The present invention also relates to a method of communicating a multimedia message for the above-mentioned system, as well as a server apparatus of the type, for example, capable of communicating a multimedia message in the above-mentioned communications system.

For a number of years, it has been possible for a subscriber to a mobile communications network to send a text-based message from a first terminal of the subscriber to a second terminal of another subscriber. In relation to Global System for Mobile communications (GSM) networks, the sending of such text- based messages, colloquially known in the UK as "texts", is supported by a Short Message Service (SMS), for which provision is made in the European Telecommunications Standards Institute (ETSI) GSM standard. The SMS allows messages of up to 160 characters (224 characters if using a 5- bit mode) to be sent to terminals that use a GSM network. Other communications systems, which operate in accordance with other standards, also support the sending of such types of messages.

Text messaging has enabled many subscribers to communicate with each other in a less intrusive way than participation in voice calls. Indeed, text messaging has enabled subscribers to send many different types of brief messages, such as Birthday greetings, congratulatory messages, or other well-wishing messages.

However, due to the limited nature of keypads of mobile telephone handsets, these messages are usually kept brief. To reduce the number of key-presses required to compose a message, an informal abbreviated language has evolved amongst some senders of text messages. Nevertheless, when viewed holistically, the information content of text messages is relatively low, it not being possible to send sound and images.

With the advent of third generation (3G) telecommunications networks, and also so-called "2.5G" intermediary modifications to existing GSM networks, cellular telecommunications network operators have launched Multimedia Messaging Services (MMSs) that enable a so-called "MMS message" to be sent, the MMS message comprising an image file containing, for example a photograph, in combination with an audio file. The possibility of sending multimedia messages therefore constitutes an increase in the sophistication of messaging services, but the level of sophistication of these simple multimedia messages is still relatively low as compared with the full potential of the MMS. Consistent with the saying that a picture is worth a thousand words, the use of simple multimedia messages goes some way towards obviating some of the problems associated with the communication of text-based messages alone, and in particular the need to abbreviate the text-based messages.

Most recently, with the introduction of terminals of increasing technical sophistication, network operators have made it possible to communicate more sophisticated multimedia messages than described above, the multimedia messages comprising text, images and sound for communication between suitably equipped terminals; the combination of text, images and sound is arranged as an animated sequence of the images and the text set to an audio background. The advent of richer multimedia messaging brings with it an ability to communicate more information than by the simple MMS messages alone, and even more information than by text-based messaging alone. However, as mentioned above, the ability to communicate an MMS message between a first terminal and a second terminal in a communications network is contingent upon the terminals having necessary capabilities to compose and play MMS messages, respectively.

At present, only a limited number of mobile terminals are capable of supporting MMS messages.

Further, in relation to MMS-capable terminals, the ability to compose MMS messages is limited by the particular resources of some terminals currently available. For example, it will be appreciated that most terminals have a limited storage capacity, and so the terminals only store a limited selection of MMS template messages. Also, these pre- stored MMS message templates, retrievable from the memory of a given terminal, can only be configured in a very limited way.

In this respect, a given template can comprise, for example, a predefined combination of a pre-defined Synchronised Multimedia Integration Language (SMIL) file, a pre-defined animated Graphics Interchange Format (GIF) file, for example a GIF 89a file, a pre-defined audio file and a text file, only the text file being editable by the subscriber.

The user can not create custom combinations of the above-mentioned file types with a text string message. The only way the user can combine a selection of files with a desired text string message in a multimedia message is if the particular combination of those files already exists in the memory of the terminal as a pre defined template capable of customization by modification of a text string message; such pre-defined templates can find themselves into the memory of the terminal through the process of downloading. It can therefore be seen that it is not possible for a user of a terminal to compose freely, using certain current terminals, a custom combination of images, sound and text. In order to be able to compose MMS messages freely, i.e. "from scratch", a terminal would therefore be required to be able to possess a more sophisticated set of tools than can currently be provided by terminals. The set of tools would have to provide creation/editing utilities as well as a compiler utility to compile the bespoke combination of text, images and audio created with the editing utility. The limited processing power of some terminals may mean that it is not possible to provide such tools.

Additionally, designing an intuitive user interface for the creation/editing utilities is challenging.

According to a first aspect of the present invention, there is provided a communications system comprising: a text-based messaging service; a multimedia messaging service; an initiating terminal arranged, when in use, to send a text-based message to an intermediary entity, the textbased message comprising at least one identity of at least one file corresponding to content for a multimedia message; wherein the intermediary entity is arranged, when in use, to retrieve and use the at least one file identified in the text-based message to compose the multimedia message.

It should be appreciated that occurrences of the term "multimedia message" herein should be construed broadly as embracing messages for communicating at least one item of content, the content being media other than text alone, for example, an image, sound or both. It is not intended that any of the at least one item of content be limited to any particular type of media format, for example, Joint Photographic Experts Group (JPEG) , GIF, Moving Picture Experts Group (MPEG), or Wave (way) formats. Further, the term "multimedia message" is not limited to a particular technical specification and can include messages sent in accordance with other technical specifications, for example, so-called Enhanced Messaging Services (EMSs) and Smart Messaging messages.

It should be understood that it may be desirable to charge different rates per multimedia message, depending upon the type and/or amount of content contained in the multimedia message.

Preferably, the multimedia message composed is in accordance with a technical specification associated with the multimedia messaging service. More preferably, the intermediary entity is further arranged, when in use, to communicate the multimedia message to a recipient terminal.

Preferably, the multimedia message composed is other than in accordance with a technical specification associated with the multimedia messaging service.

The multimedia message may be reproduced on a recipient terminal in a manner different to that for reproduction of multimedia messages generated in accordance with a technical specification associated with the multimedia messaging service.

Conveniently, the technical specification is an MMS Encapsulation Protocol

specification.

Preferably, the initiating terminal is capable of browsing a number of a plurality of files accessible to the intermediary entity. More preferably, the initiating terminal is capable of browsing the number of the plurality of files using a Wireless Application Protocol (WAP) browser.

The at least one identity of the at least one file may be the identities of at least two files from a number of a plurality of files.

Preferably, the text-based messaging service is a Short Messaging Service (SMS).

Preferably, the intermediary entity composes the multimedia message by compiling the at least one file identified into a multimedia message file.

Preferably, the intermediary entity is arranged to generate a multimedia choreography file. More preferably, the multimedia choreography file is a Synchronised Multimedia Integration Language (SMIL) file.

Preferably, the at least one identity of the at least one file contained in the text based message is accompanied by a text string to be incorporated into the multimedia message for presentation. More preferably, the intermediary entity is further arranged to extract the text string from the text based message.

The intermediary entity may be further arranged to extract the at least one identity of the at least one file from the text-based message.

Preferably, the intermediary entity is arranged to identify a level of technical capability of the recipient terminal to reproduce the multimedia message. More preferably, the intermediary entity is arranged, when in use, to communicate the multimedia message in a modified manner to the recipient terminal so as to cause the recipient terminal to reproduce the multimedia message in the manner different to that for reproduction of the multimedia message in accordance with the technical specification, the communication of the multimedia message in the modified manner being in response to the level of technical capability of the recipient terminal identified.

Alternatively, the intermediary entity is arranged to communicate the multimedia message as a series of time-spaced mark-up language pages. The series of time- spaced mark-up language pages may be generated and communicated using the at least one file identified in the text-based message and the multimedia choreography file.

Preferably, the intermediary entity is a server.

The at least one identity of the at least one file may be the identity of at least two files, the at least two files identified in the text-based message having different file types associated with each other.

The at least one file identified in the text-based message may comprise an identity of an image file and an identity of an audio file.

In one embodiment of the invention, there is provided a communications system for communicating a multimedia message, the system comprising: a server capable of storing a plurality of data files; an initiating terminal capable of browsing a number of the plurality of data files stored, the initiating terminal being arranged to select, when in use, at least two data files from the plurality of data files and being capable of communicating to the server the identities of the at least two data files; wherein the at least two data files have different file types associated therewith; the server is arranged, when in use, to retrieve the at least two data files selected and to generate the multimedia message using the at least two data files; and the server is further arranged to communicate the multimedia message to a recipient terminal.

According to a second aspect of the present invention, there is provided a method of communicating a multimedia message for a communications system supporting a multimedia messaging service, the method comprising the steps of: an initiating terminal sending a text-based message supported by a text-based messaging service to an intermediary entity, the text-based message comprising at least one identity of at least one file corresponding to content for a multimedia message; the intermediary entity retrieving and using the at least one file identified in the text- based message to compose the multimedia message.

Preferably, the method further comprises the step of: composing the multimedia message in accordance with a technical specification associated with the multimedia messaging service.

The method may further comprise the step of: the intermediary entity communicating the multimedia message to a recipient terminal.

The method may further comprise the step of: composing the multimedia message other than in accordance with a technical specification associated with the multimedia messaging service.

Preferably, method may further comprise the step of: reproducing the multimedia message on a recipient terminal in a manner different to that for reproduction of multimedia messages generated in accordance with a technical specification associated with the multimedia messaging service.

The technical specification may be an MMS Encapsulation Protocol specification.

Preferably, the method further comprises the step of: the initiating terminal browsing a number of a plurality of files accessible to the intermediary entity.

More preferably, the number of the plurality of files are browsed from the initiating terminal using a Wireless Application Protocol (WAP) browser.

The step of composing the multimedia message may comprise the step of: compiling the at least one file identified into a multimedia message file.

Preferably, the method may further comprise the step of: generating a multimedia choreography file. Conveniently, the multimedia choreography file is a Synchronised Multimedia Integration Language (SMIL) file.

The text-based message may include a text string to be incorporated into the multimedia message for presentation. The intermediary entity may also extract the text string from the text-based message.

Preferably, the method may further comprise the step of: the intermediary entity extracting the at least one identity of the at least one file from the text-based message.

The method may further comprise the step of: identifying a level of technical capability of the recipient terminal to reproduce the multimedia message.

The method may further comprise the step of: the intermediary entity communicating the multimedia message in a modified manner to the recipient terminal so as to cause the recipient terminal to reproduce the multimedia message in the manner different to that for reproduction of the multimedia message in accordance with the technical specification, the communication of the multimedia message in the modified manner being in response to the level of technical capability of the recipient terminal identified.

Preferably, the method may further comprise the step of: the intermediary entity communicating the multimedia message as a series of time-spaced mark-up language pages. More preferably, the method may further comprise the step of: using the at least one file selected and identified in the text-based message and the multimedia choreography file, generating and communicating the series of time-spaced mark-up language pages.

The intermediary entity may be a server.

In another embodiment of the invention, there is provided a method of communicating a multimedia message for a communications network, the method comprising the steps of: from a database of a plurality of data files, browsing a number of the plurality of data files using an initiating terminal; selecting at least two data files from the plurality of data files, the at least two data files having different file types associated therewith; communicating to a server the identities of the at least two data files selected; the server retrieving the data files selected; generating the multimedia message using the at least two data files selected; and communicating the multimedia message from the server to a recipient terminal.

According to a third aspect of the present invention, there is provided a method of serving a multimedia message for a communications system supporting a multimedia messaging service, the method comprising the steps of: receiving a text-based message supported by a text-based messaging service, the text-based message comprising at least one identity of at least one file corresponding to content for the multimedia message; and retrieving and using the at least one file identified in the text-based message to compose the multimedia message.

Preferably, the method further comprises the step of: communicating the multimedia message to a recipient terminal.

According to a fourth aspect of the present invention, there is provided a computer program element comprising computer program code means to make a computer execute the method as set forth above in accordance with the second or third aspect of the present invention.

Preferably, the computer program element is embodied on a computer readable medium.

According to a fifth aspect of the present invention, there is provided a server apparatus for communicating a multimedia message in a communications system supporting a multimedia messaging service, the apparatus comprising a processing unit and a storage device capable, when in use, of supporting: a text- based message processing entity capable of receiving a text-based message supported by a text-based messaging service, and capable of processing at least one identity of at least one file contained in the text-based message, the at least one identity of the at least one file corresponding to content for the multimedia message; a data retrieval entity for retrieving the at least one file identified in the text-based message; and a multimedia message processing entity arranged to use the at least one file retrieved to compose the multimedia message for communication to a recipient terminal.

The apparatus may further comprise a web serving entity for serving or obtaining serving of at least one web page for presenting a number of a plurality of files.

The multimedia message composed may be in accordance with a technical specification associated with the multimedia messaging service.

The processing unit may further support: a message communication entity arranged, when in use, to communicate the multimedia message to the recipient terminal.

Preferably, the multimedia message is reproduced on the recipient terminal in a manner different to that for reproduction of multimedia messages generated in accordance with a technical specification associated with the multimedia messaging service.

The technical specification may be an MMS Encapsulation Protocol specification.

The at least one web page may be at least one Wireless Application Protocol (WAP) web page.

Preferably, the at least one identity of the at least one file is the identities of at least two files from a number of a plurality of files.

Conveniently, the text-based messaging service is a Short Messaging Service 1 0 (SMS).

Preferably, the multimedia message processing entity composes the multimedia message by compiling the at least one file identified into a multimedia message file.

Preferably, the multimedia message processing unit may be arranged to generate a multimedia choreography file. More preferably, the multimedia choreography file is a Synchronised Multimedia Integration Language (SMIL) file.

Preferably, the at least one identity of the at least one file contained in the text- based message are accompanied by a text string to be incorporated into the multimedia message for presentation. More preferably, the text-based message processing entity is further arranged to extract the text string from the text-based message received.

The text-based message processing unit may be further arranged to extract the at least one identity of the at least one file contained in the textbased message received.

The processing unit may further support: a terminal capability identification entity arranged to identify a level of technical capability of the recipient terminal to reproduce the multimedia message.

The processing unit may further support a message communication entity arranged, when in use, to communicate to the recipient terminal the multimedia message in a modified manner so as to cause the recipient terminal to reproduce the multimedia message in the manner different to that for reproduction of the multimedia message in accordance with the technical specification, the communication of the multimedia message in the modified manner being in response to the level of technical capability of the recipient terminal identified.

Preferably, the message communication entity is arranged to communicate the multimedia message as a series of time-spaced mark-up language pages. More preferably, the series of time-spaced mark-up language pages is generated and communicated using the at least one file identified in the text-based message and the multimedia choreography file.

Preferably, the at least one identity of the at least one file is the identity of at least two files, the at least two files identified having different file types associated with each other.

According to a sixth aspect of the present invention, there is provided a server apparatus for communicating a multimedia message, the apparatus comprising: means for receiving a text-based message, the text-based message comprising at least one identity of at least one file corresponding to content for a multimedia message; and means for retrieving and using the at least one file identified in the text-based message to compose the multimedia message.

According to a seventh aspect of the present invention, there is provided a use of a text-based message to communicate at least one desired media component of a multimedia message to a server capable of generating the multimedia message comprising the desired media components.

According to a eighth aspect of the present invention, there is provided a text- based message for support by a text-based messaging service, the text- based message comprising at least one identity of at least one file corresponding to content for a multimedia message.

It is thus possible to provide a system, method and apparatus capable of providing the first terminal with a means of composing and sending multimedia messages, even though the first terminal may not be technically capable of composing and sending the multimedia messages. The use of a text-based message to serve as a first leg of a multimedia message communications path also constitutes a reduction in bandwidth needed to communicate a given multimedia message. The reduction in bandwidth is beneficial to network operators as well as subscribers who pay for their data services on a "per bit", or similar metered basis. Further, a wider range of content can be sent from the first terminal to the second terminal, the user of the first terminal (when MMS capable) not being limited to the small number of template multimedia messages provided with the first terminal. By avoiding composition and transmission of the multimedia message from the first terminal, the subscriber associated with the first terminal can benefit from cost savings associated with a difference in cost between sending a multimedia message and a text-based message. Additionally, the multimedia message can still be delivered and reproduced in some circumstances when the second terminal is not technically capable to reproduce multimedia messages.

At least one embodiment of the invention will now be describes, by way of example only, with reference to the accompanying drawings, in which: Figure 1 is a schematic diagram of a communications network constituting a first embodiment of the present invention; Figure 2 is a schematic diagram of a server apparatus for use in the network of Figure 1; Figure 3 is a flow diagram of a method of operation of an initiating terminal in the communications network of Figure 1; Figures 4a and 4b are flow diagrams of a method of operation of a server for use with the communications network of Figure 1; and Figure 5 is a flow diagram of a method of operation of a recipient terminal in the communications network of Figure 1.

A communications network (Figure 1), for example, a cellular telecommunications network, such as a GSM cellular telecommunications network 100 comprises a first cell 102 supported by a first base station 104, a second cell 106 supported by a second base station 108 and a supporting network infrastructure 110 capable of communicating with the first and second base stations 104, 108 via a first communications link 112 and a second communications link 114, respectively.

The supporting network infrastructure 110 comprises a first SMS Center (SMSC) 116 to support a text-based messaging service, such as an SMS, a Multimedia Messaging Service Center (MMSC) 117 to support a Multimedia Messaging Service (MMS), a Wireless Application Protocol (WAR) gateway 118 and a PushProxy gateway 119. The skilled person will, of course, appreciate that the supporting network infrastructure 110 comprises other hardware and software to support the numerous known functions required to support normal operation of the network 100. Since the present invention and the examples set forth herein do not relate, directly, to the normal functions of the network, for the purposes of clarity and conciseness of description, further details of the supporting network infrastructure 110 will therefore not be described. However, further information concerning the structure and operation of GSM networks can be found in the book entitled: "The GSM System for Mobile Communications" (M. Mouly and M.B.

Pautet, 1992).

In this example, a first, originator, terminal 120 is located within the first cell 102 and is capable of communicating with the first base station 104 via a first Radio Frequency (RF) interface 122. Similarly, a second, recipient, terminal 124 is located within the second cell 106 and is capable of communicating with the second base station 108 via a second RF interface 126.

An intermediary entity, for example, a server 128 is disposed at any convenient location from which, in this example, communication with a computer network can be achieved. The server 128 can be any suitable server running an appropriate operating system, such as Windows 2000 server or a suitable version of Linux.

In this example, the server 128 is capable of communicating with the Internet 130 via a third communications link 132 and an Internet Service Provider (ISP - not shown). The supporting network infrastructure 110 is capable of communicating data with the server 128 via a fourth communications link 134, the Internet 130 and the third communications link 132.

Referring to Figure 2, the server 128 comprises a processing unit 200capable of storing data to and retrieving data from a storage device 202, for example, a Hard Disc Drive (HOD). The processor 200 is suitably programmed to support a second SMSC 204 coupled to an inpuVoutput port 206 for transmitting and receiving data using one or more incoming and outgoing "line", respectively. The SMSC 204 is capable of communicating with a text message parser entity 208, the text message parser entity 208 being capable of communicating data to a data retrieval entity 210. The data retrieval entity 210 is operatively coupled to the storage device 202 in order to retrieve data therefrom. The data retrieval entity 210 is also capable of communicating with a message composition entity 212, the message composition entity 212 being arranged to communicate with a communications entity 214, as well as store and retrieve multimedia messages to and from the storage device 202. The communications entity 214 is coupled to the inpuVoutput port 206.

Although not shown in Figure 2, the server 128 also comprises a web server entity for serving a web and/or WAP site, the server 128 being arranged to serve information relating to a plurality of multimedia and multimedia-related files through the web/WAP site. It should be appreciated that the web server entity is not essential and/or that the web/WAP site need not be served from the server 128; an alternative resource can be used to serve the web/WAP site.

In operation (Figure 3), a first user of the first terminal 120 desires to send a multimedia message to the second terminal 124. The first user, using a WAP browser (not shown) provided with the first terminal 120, accesses a WAP site served by the server 128, for example wan. linhtmvfibre.com. The first user is then able to browse a plurality of images and audio works. The plurality of images and audio works respectively correspond to image files, such as GIF files or animated GIF files, and audio files. Each of the plurality of images and audio works is identified by a unique reference and the first user, whilst browsing the WAR site, notes (step 300) references corresponding to at least one file, for example an image file and an audio file, from which the user wants to compose the multimedia message, i.e. the first user freely selects the content of the multimedia message.

It should be appreciated that while the at least two files are, in this example, of different types, files of like type can also be used.

With an additional option, a plurality of choreographies for images, audio works and/or text strings can be provided for browsing by the first user, thereby providing the first user with an ability to further customise the multimedia message by choosing a particular "running order" for the content already chosen. In common with the images and audio works browsable, each choreography is identified by a unique reference and corresponds to a respective choreography file, such as a Synchronised Multimedia Integration Language (SMIL) file.

The first user, having noted a number of references corresponding, in this example, to at least one image and at least one audio work, composes and sends (step 302) a requesting SMS message to a destination telephone number corresponding to the second SMSC 204 of the server 128, the requesting SMS message containing the unique references for the image file, the audio file and, optionally, the choreography file chosen. The requesting SMS message also contains, of course, the telephone number of the second terminal 124. The first user can also include, as a text string, a message constituting, for example, a greeting to be incorporated into the multimedia message. The first terminal 120 then awaits (step 304) an incoming reply SMS message from the server 128.

At the server 128 (Figure 4a), the second SMSC 204 awaits receipt of the requesting SMS message sent by the first terminal 120. Upon receipt (step 400) of the requesting SMS message, the second SMSC 204 passes the requesting SMS message to the parser entity 208 and the parser entity 208 parses (step 402) the requesting SMS message received in order to extract all salient information required from the first user and/or the subscription associated with the first terminal 120 in order to compose the multimedia message. The parser entity 208 then validates (step 404) the extracted information, by checking the information provided in the requesting SMS message against the relevant files stored by the storage device 202, in order to determine (step 406) whether or not the extracted information contains one or more error. In the event that the information extracted from the requesting SMS message is erroneous, the server 128, through the second SMSC 204, sends (step 408) a reply SMS message to the first terminal 120, the content of the reply SMS message reporting the fact that an error has occurred, and the second SMSC 204 continues to await other requesting SMS messages. If the information extracted is error-free, the parser entity 208 determines (step 410) whether or not the subscriber or the first user associated with the first, originator, terminal 120 is registered with the service provided by the server 128. If the subscriber or the first user associated with the first terminal 120 is not registered with the server 128, the server 128 sends (step 412) the reply SMS message to the first terminal 120, the content of the reply SMS message requesting registration. The reply SMS message requesting registration can, for example, simply request a reply thereto in order for the second SMSC 204 to confirm the telephone number associated with the first terminal 120. The reply by the first terminal 120 to the reply SMS message, in this example, serves as a way for the first user of the first terminal 120 to confirm acceptability of receipt, or opt-in to the receipt, of premium-rate SMS messages as well as to avoid the operator of the service provided by the server 128 falling victim to so-called telephone number "spoofing". Thereafter, or if the subscriber associated with the first terminal 120 is determined (step 410) to be registered with the server 128, the information extracted by the parser entity 208 is passed to the data retrieval entity 210 and the data retrieval entity 210 retrieves (step 414) the files identified in the requesting SMS message sent from the first terminal 120, for example, the image file and the audio file (and, optionally, the choreography file). The communications entity 214 then searches (step 416) a database of telephone numbers and so-called User Agent Profiles (UAProfs), or Capability and Preference Information (CPI), stored in the storage device 202 of the server 128, using the telephone number associated with the second terminal 124 communicated in the requesting SMS message, in order, firstly, to determine if the server 128 has the UAProf of the second terminal 124 or information relating thereto stored in the file store 202. If the service provided through the server 128 has been previously used to send a multimedia message to the second terminal 124, the server 128 should have the UAProf of the second terminal 124 or data derived from the UAProf of the second terminal 124. Using the information provided in the UAProf of the second terminal 124, the retrieved image and audio files are then passed, along with the text string, by the data retrieval entity 210 to the message composition entity 212 and the message composition entity 212, using the retrieved files, composes the multimedia message in accordance with one or more technical standard, for example, an MMS encapsulation protocol specification, associated with the multimedia messaging service supported by the MMSC 117. In this example, the message composition entity 212 compiles the retrieved identified files (and any text string) into a multimedia message file. Whatever the format of the multimedia message generated, the multimedia message is, in this example, compatible with attributes of the second terminal 124, such as screen size, range of colours, browser capabilities, and/or supported media formats, derivable from the UAProf of the second terminal 124. The message composition entity 212 then temporarily stores (step 418) in the storage device 202 the multimedia message file. For the purpose of being able to reproduce the multimedia message via a web browser, the multimedia message file can be stored in a publicly accessible part of the storage device 202 for serving by the web server entity (not shown). The message composition entity 212 also stores (step 418) details of the multimedia message created as part of a transaction log for billing purposes, as well as to have available details of the multimedia message so that the multimedia message can be reconstructed in a modified form if necessary, described in more detail later herein, without having to decompile the multimedia message already created.

Subsequently, based upon the result of the search (step 416) of the database of telephone numbers and UAProfs, the server 128 formally determines (step 420) if the second terminal 124 is already known to the server 128; the second terminal 124 is known to the server 128 if the telephone number associated with the second terminal 124 is found in the database of telephone numbers and UAProfs.

The implication of the telephone number of the second terminal 124 existing in the database of the telephone numbers and UAProfs is that the server 128 will "know" the technical capabilities of the second terminal 124 and so knows a technically most advanced manner possible to communicate the multimedia message to the second terminal 124.

If the UAProf corresponding to the second terminal 124 is not in the database of telephone numbers and UAProfs, the second SMSC 204 sends (step 422) an alert SMS message to the second terminal 124, the alert SMS message containing a hyperlink to an wml interrogation page served by the server 128, the hyperlink including an identifier for the alert message sent to the second terminal 124. The alert SMS message also contains a request for a second user of the second terminal 124 to activate, or "click on", the hyperlink.

Referring to Figure 5, the second terminal 124 awaits (step 500) receipt of a communication from the server 128. The second terminal 124 then determines the type of communication received. If the communication is the alert SMS message prompting the second user of the second terminal 124, in this example, to respond to the alert SMS message by activating the hyperlink, the second terminal 124 prompts the second user of the second terminal 124 to open the alert SMS message. The second user of the second terminal 124 can decide to either read the alert SMS message or ignore the alert SMS message. Assuming that the second user wishes to receive the multimedia message, the second user opens the alert SMS message and activates (step 502) the hyperlink contained therein.

In response to the activation of the hyperlink, the second terminal 124 attempts to establish (step 504) a WAP connection with the WAP gateway 118 in order to communicate a request to the server 128 for the wml interrogation page.

At the server 128 (Figure 4b), the message communication entity 214 awaits (step 424) an attempt by the WAP gateway 118 to connect to the server 128. As mentioned above, in response to activating the hyperlink, the WAP connection is established (step 424) between the WAP gateway 118 and the server 128, and the server 128 receives the request for the wml interrogation page (step 506) by the second terminal 124. The wml interrogation page then assesses the capabilities of the second terminal 124 through the request for the wml interrogation page, the request including the UAProf associated with the second terminal 124. The UAProf of the second terminal 124 is then identified (step 426) and used by the server 128 to determine (step 428) the most technically advanced way of communicating the multimedia message to the second terminal 124. This information is, of course, stored in the database of telephone numbers and UAProfs.

In this example, the determination of the most technically advanced way of communicating the multimedia message to the second terminal 124 is a determination (step 428) as to whether the second terminal 124 is able to receive and reproduce the multimedia message as stored, i.e. in the format as composed, or whether the multimedia message can be reproduced on the second terminal 124 in a modified manner different to that for reproduction of multimedia messages generated in accordance with the one or more technical specification associated with the multimedia messaging service, or whether the second terminal 124 is not at all capable of receiving the multimedia message.

If the second terminal 124 is technically capable of receiving the multimedia message as composed, the WAP connection is terminated by the communications entity 214 and the termination of the WAP connection is detected (step 508) by the second terminal 214. Thereafter, the communications entity 214 sends (step 430) an MMS notification to the second terminal 124, the notification, once received, prompting the second terminal 124 to retrieve the multimedia message. Referring back to Figure 5, the second terminal 124, following step 500 above, identifies the MMS notification and initiates (step 510) a data connection, such as a General Packet Radio Service (GPRS) connection, with a service provider of the second terminal 124. Using the data connection, the second terminal 124 makes a request to the WAP gateway 118 to retrieve (step 512) the multimedia message, via the data connection. The multimedia message is, after acknowledgement of receipt of the multimedia message by the second terminal 124, reproduced (step 514) by the second terminal 124 in accordance with the technical specification associated with the multimedia messaging service supported by the MMSC 117.

However, if the second terminal 124 is determined (step 428) not to be technically able to receive and present the multimedia message in the format composed, as a result, for example, of the second terminal 124 not having multimedia messaging functionality, but the second terminal 124 is capable of reproducing the multimedia message in the modified manner, the WAP connection is terminated by the communications entity 214 and the termination of the WAP connection is detected (step 508) by the second terminal 214. Thereafter, the second SMSC 204 sends (step 432) a further SMS message to the second terminal 124, the further SMS message containing another hyperlink to another part of the WAP site served by the server 128 from where the multimedia message can be communicated in the modified manner. Alternatively, the communications entity 214 can send a Service Indication (Sl) to the second terminal 124 comprising a Uniform Resource Indicator (URI), the URI being activatable by the second user of the second terminal 124, resulting in a WAP connection being established to access the another part of the WAP site mentioned above.

The communications entity 214 then requests, or substantially simultaneously requests or previously has requested, the composition entity 212 to compose (step 434) the multimedia message, in this example, as a series of time-spaced mark-up language pages, for example, wireless markup language (wml) pages, using the files identified in the requesting SMS message, the text string message and by parsing the choreography file to obtain "running order" information, including timing sequences. The multimedia message is therefore in a modified form and so is other than in accordance with the one or more technical specification associated with the multimedia message. The multimedia message, following composition in the modified form, is passed back by the composition entity 212 to the communications entity 214 for communication to the second terminal 124 in the modified manner, in this example, as the series of time-spaced mark-up pages.

The communications entity 214 then awaits (step 436) the second user of the second terminal to activate (step 502) the another hyperlink contained in the further SMS message, and to establish (step 504) the WAP connection with the WAP gateway 118. Once the WAP connection is established the multimedia message is communicated (step 438) to the second terminal 124 as a series of time-spaced wml pages (step 506) and the WAP connection is then terminated (step 508).

Whilst, in this example, the multimedia message is composed in the modified form prior to communication to the second terminal 124 by the communications entity 214, the images can be converted and communicated in real-time, i.e. "on the fly", by the message composition entity 212 and the communications entity 214. In such an example, the image and audio files are converted to appropriate formats, if formats compatible with the second terminal 124 exist, for example a series of time-spaced ".wml" format pages, and communicated to the second terminal 124 in real-time.

Lastly, if the second terminal 124 is incapable of reproducing the multimedia message for the second user, the communications entity 214 instructs the second SMSC 204 to send (step 440) an advisory SMS message to the second terminal 124 explaining to the second user that the second terminal 124 is technically unable to reproduce the multimedia message, but that the multimedia message can be viewed from a multimedia message presentation website, in this example, supported by the web server entity (not shown) of the server 128.

Once either the multimedia message has been communicated to the second terminal 124, or communicated in the modified manner, or the advisory SMS message has been sent, the message communication entity 214 instructs the SMSC 204 to send (step 442) a premium-rate reply SMS message to the first terminal 120 as a way of advising the user of the first terminal 120 that the multimedia message has been sent successfully in one form or another and as a way of billing the subscriber associated with the first terminal 120 for the service provided. Upon receipt of the premium-rate reply SMS message, the first terminal (step 306) stores the premium-rate reply SMS message for subsequent review by the first user. The server 128 then continues to await other requesting SMS messages.

Referring back to Figure 4a, if, after having searched (step 418) the database of telephone numbers and UAProfs, the server 128 identifies (step 420) the telephone number associated with the second terminal 124 and therefore possesses the UAProf of the second terminal, the server 128 proceeds directly to the determination (step 428) of the most technically advanced way of communicating the multimedia message to the second terminal 124 and then proceeds with the communication of the multimedia message to the second terminal 124 in the most technically advanced manner possible in accordance with steps 430 to 440 described above.

As an alternative, or in addition, to the ways described above to communicate the multimedia message to the second terminal 124, the message contained in the advisory SMS message can be sent to an e-mail mailbox of the user of the second terminal 124, or the subscriber associated with the second terminal 124, the message containing a hyperlink to an appropriate part of the multimedia message presentation website mentioned above. Altematively, the e-mail can contain the multimedia message as an attachment or embedded object, the multimedia message being embodied in a Macromedia Flash file, or other suitable media presentation file.

Whilst, in the above example, the composition of the multimedia message has been described in the context of the first user selecting content components for communication to the server 128 for compilation, it should be appreciated that the server 128 could in addition to, or as an alternative, offer template multimedia messages for selection by the first user. The template multimedia messages may optionally be customizable, for example, by the first user providing a text string message for inclusion in the multimedia message to be communicated to the terminal 124.

Although the above examples describe identification of terminal capabilities and communication of multimedia messages composed other than in accordance with a technical specification associated with a given multimedia messaging service in the context of initiation by a text-based message, it should be appreciated that other embodiments are envisaged that employ the above-mentioned identification and composition stages without the need for selection and initiation stages involving a user of an originating terminal. Consequently, a message service provider is able to compose messages that can be reproduced on a recipient terminal in a manner different to that for reproduction of multimedia messages generated in accordance with the technical specification associated with the multimedia messaging service.

Alternative embodiments of the invention can be implemented as a computer program product for use with a computer system, the computer program product being, for example, a series of computer instructions stored on a tangible data recording medium, such as a diskette, CD-ROM, ROM, or fixed disk, or embodied in a computer data signal, the signal being transmitted over a tangible medium or a wireless medium, for example microwave or infrared. The series of computer instructions can constitute all or part of the functionality described above, and can also be stored in any memory device, volatile or non-volatile, such as semiconductor, magnetic, optical or other memory device.

Claims

Claims: 1. A communications system comprising: a text-based messaging

service; a multimedia messaging service; an initiating terminal arranged, when in use, to send a text-based message to an intermediary entity, the text- based message comprising at least one identity of at least one file corresponding to content for a multimedia message; wherein the intermediary entity is arranged, when in use, to retrieve and use the at least one file identified in the text-based message to compose the multimedia message.
2. A system as claimed in Claim 1, wherein the multimedia message composed is in accordance with a technical specification associated with the multimedia messaging service.
3. A system as claimed in Claim 2, wherein the intermediary entity is further arranged, when in use, to communicate the multimedia message to a recipient terminal.
4. A system as claimed in Claim 1, wherein the multimedia message composed is other than in accordance with a technical specification associated with the multimedia messaging service.
5. A system as claimed in Claim 1, wherein the multimedia message is reproduced on a recipient terminal in a manner different to that for reproduction of multimedia messages generated in accordance with a technical specification associated with the multimedia messaging service.
6. A system as claimed in any one of Claims 2 to 5, wherein the technical specification is an MMS Encapsulation Protocol specification.
7. A system as claimed in any one the preceding claims, wherein the initiating terminal is capable of browsing a number of a plurality of files accessible to the intermediary entity.
8. A system as claimed in Claim 7, wherein the initiating terminal is capable of browsing the number of the plurality of files using a Wireless Application Protocol (WAP) browser.
9. A system as claimed in any one of Claims 1 to 6, wherein the at least one identity of the at least one file is the identities of at least two files from a number of a plurality of files.
10. A system as claimed in any one of the preceding claims, wherein the text- based messaging service is a Short Messaging Service (SMS).
11. A system as claimed in any one of the preceding claims, wherein the intermediary entity composes the multimedia message by compiling the at least one file identified into a multimedia message file.
12. A system as claimed in any one of the preceding claims, wherein the intermediary entity is arranged to generate a multimedia choreography file.
13. A system as claimed in Claim 12, wherein the multimedia choreography file is a Synchronised Multimedia Integration Language (SMIL) file.
14. A system as claimed in any one of the preceding claims, wherein the at least one identity of the at least one file contained in the text- based message is accompanied by a text string to be incorporated into the multimedia message for presentation.
15. A system as claimed in any one of the preceding claims, wherein the intermediary entity is further arranged to extract the at least one identity of the at least one file from the text-based message.
16. A system as claimed in Claim 14, wherein the intermediary entity is further arranged to extract the text string from the text based message.
17. A system as claimed in Claim 5, wherein the intermediary entity is arranged to identify a level of technical capability of the recipient terminal to reproduce the multimedia message.
18. A system as claimed in Claim 17, when dependent upon Claim 5, wherein the intermediary entity is arranged, when in use, to communicate the multimedia message in a modified manner to the recipient terminal so as to cause the recipient terminal to reproduce the multimedia message in the manner different to that for reproduction of the multimedia message in accordance with the technical specification, the communication of the multimedia message in the modified manner being in response to the level of technical capability of the recipient terminal identified.
19. A system as claimed in any one of Claims 1 to 18, wherein the intermediary entity is arranged to communicate the multimedia message as a series of time- spaced mark-up language pages.
20. A system as claimed in Claim 19, wherein the series of time-spaced mark- up language pages is generated and communicated using the at least one file identified in the text-based message and the multimedia choreography file.
21. A system as claimed in any one of the preceding claims, wherein the intermediary entity is a server.
22. A system as claimed in any one of the Claims 1 to 21, wherein the at least one identity of the at least one file is the identity of at least two files, the at least two files identified in the text-based message having different file types associated with each other.
23. A system as claimed in any one of Claims 1 to 22, wherein the at least one file identified in the text-based message comprises an identity of an image file and an identity of an audio file.
24. A method of communicating a multimedia message for a communications system supporting a multimedia messaging service, the method comprising the steps of: an initiating terminal sending a text-based message supported by a text based messaging service to an intermediary entity, the text-based message comprising at least one identity of at least one file corresponding to content for a multimedia message; the intermediary entity retrieving and using the at least one file identified in the text- based message to compose the multimedia message.
25. A method as claimed in Claim 24, further comprising the step of: composing the multimedia message in accordance with a technical specification associated with the multimedia messaging service.
26. A method as claimed in Claim 24 or Claim 25, further comprising the step of: the intermediary entity communicating the multimedia message to a recipient terminal.
27. A method as claimed in Claim 24, further comprising the step of: composing the multimedia message other than in accordance with a technical specification associated with the multimedia messaging service.
28. A method as claimed in Claim 24, further comprising the step of: reproducing the multimedia message on a recipient terminal in a manner different to that for reproduction of multimedia messages generated in accordance with a technical specification associated with the multimedia messaging service.
29. A method as claimed in any one of Claims 25 to 28, wherein the technical specification is an MMS Encapsulation Protocol specification.
30. A method as claimed in any one of Claims 24 to 29, further comprising the step of: the initiating terminal browsing a number of a plurality of files accessible to the intermediary entity.
31. A method as claimed in Claim 30, wherein the number of the plurality of files are browsed from the initiating terminal using a Wireless Application Protocol (WAP) browser.
32. A method as claimed in any one of Claims 24 to 29, wherein the at least one identity of the at least one file is the identities of at least two files from a number of a plurality of files.
33. A method as claimed in any one of Claims 24 to 32, wherein the textbased messaging service is a Short Messaging Service (SMS).
34. A method as claimed in any one of the Claims 24 to 33, wherein the step of composing the multimedia message comprises the step of: compiling the at least one file identified into a multimedia message file.
35. A method as claimed in any one of Claims 24 to 34, further comprising the step of: generating a multimedia choreography file.
36. A method as claimed in Claim 35, wherein the multimedia choreography file is a Synchronised Multimedia Integration Language (SMIL) file.
37. A method as claimed in any one of Claims 24 to 36, wherein the textbased message includes a text string to be incorporated into the multimedia message for presentation.
38. A method as claimed in any one of Claims 24 to 37, further comprising the step of: the intermediary entity extracting the at least one identity of the at least one file from the text-based message.
39. A method as claimed in Claim 37, further comprising the step of: the intermediary entity extracting the text string from the text-based message.
40. A method as claimed Claim 28, further comprising the step of: identifying a level of technical capability of the recipient terminal to reproduce the multimedia message.
41. A method as claimed in Claim 40, when dependent upon Claim 28, further comprising the step of: the intermediary entity communicating the multimedia message in a modified manner to the recipient terminal so as to cause the recipient terminal to reproduce the multimedia message in the manner different to that for reproduction of the multimedia message in accordance with the technical specification, the communication of the multimedia message in the modified manner being in response to the level of technical capability of the recipient terminal identified.
42. A method as claimed in any one of Claims 24 to 41, further comprising the step of: the intermediary entity communicating the multimedia message as a series of time-spaced mark-up language pages.
43. A method as claimed in Claim 42, further comprising the step of: using the at least one file selected and identified in the text-based message and the multimedia choreography file, generating and communicating the series of time-spaced mark-up language pages.
44. A method as claimed in any one of Claims 24 to 43, wherein the intermediary entity is a server.
45. A method as claimed in any one of Claims 24 to 44, wherein the at least one identity of the at least one file is the identities of at least two files, the at least two files identified in the text-based message having different file types associated with each other.
46. A method as claimed in any one of Claims 24 to 45, wherein the at least one file identified in the text-based message comprises an identity of an image file and an identity of an audio file.
47. A method of serving a multimedia message for a communications system supporting a multimedia messaging service, the method comprising the steps of: receiving a text-based message supported by a text-based messaging service, the text-based message comprising at least one identity of at least one file corresponding to content for the multimedia message; and retrieving and using the at least one file identified in the text-based message to compose the multimedia message.
48. A method as claimed in Claim 47, further comprising the step of: communicating the multimedia message to a recipient terminal.
49. A computer program element comprising computer program code means to make a computer execute the method as claimed in any one of Claims 24 to 48.
50. A computer program element as claimed in Claim 49, embodied on a computer readable medium.
51. A server apparatus for communicating a multimedia message in a communications system supporting a multimedia messaging service, the apparatus comprising a processing unit and a storage device capable, when in use, of supporting: a text-based message processing entity capable of receiving a text-based message supported by a text-based messaging service, and capable of processing at least one identity of at least one file contained in the text-based message, the at least one identity of the at least one file corresponding to content for the multimedia message; a data retrieval entity for retrieving the at least one file identified in the text based message; and a multimedia message processing entity arranged to use the at least one file retrieved to compose the multimedia message for communication to a recipient terminal.
52. An apparatus as claimed in Claim 51, further comprising a web serving entity for serving or obtaining serving of at least one web page for presenting a number of a plurality of files.
53. An apparatus as claimed in Claim 51, wherein the multimedia message composed is in accordance with a technical specification associated with the multimedia messaging service.
54. An apparatus as claimed in Claim 53, wherein the processing unit further supports: a message communication entity arranged, when in use, to communicate the multimedia message to the recipient terminal.
55. An apparatus as claimed in Claim 51, wherein the multimedia message composed is other than in accordance with a technical specification associated with the multimedia messaging service.
56. An apparatus as claimed in Claim 51, wherein the multimedia message is reproduced on the recipient terminal in a manner different to that for reproduction of multimedia messages generated in accordance with a technical specification associated with the multimedia messaging service.
57. An apparatus as claimed in any one of Claims 53 to 56, wherein the technical specification is an MMS Encapsulation Protocol specification.
58. An apparatus as claimed in Claim 52, wherein the at least one web page is at least one Wireless Application Protocol (WAP) web page.
59. An apparatus as claimed in Claim 51, wherein the at least one identity of the at least one file is the identities of at least two files from a number of a plurality of files.
60. An apparatus as claimed in any one of Claims 51 to 59, wherein the text- based messaging service is a Short Messaging Service (SMS).
61. An apparatus as claimed in any one of Claims 51 to 60, wherein the multimedia message processing entity composes the multimedia message by compiling the at least one file identified into a multimedia message file.
62. An apparatus as claimed in any one of Claims 51 to 61, wherein the multimedia message processing unit is arranged to generate a multimedia choreography file.
63. An apparatus as claimed in Claim 62, wherein the multimedia choreography file is a Synchronised Multimedia Integration Language (SMIL) file.
64. An apparatus as claimed in any one of Claims 51 to 63, wherein the at least one identity of the at least one file contained in the text-based message are accompanied by a text string to be incorporated into the multimedia message for presentation.
65. An apparatus as claimed in any one of Claims 51 to 64, wherein the text- based message processing unit is further arranged to extract the at least one identity of the at least one file contained in the text-based message received.
66. An apparatus as claimed in Claim 64, wherein the text-based message processing entity is further arranged to extract the text string from the text-based message received.
67. An apparatus as claimed in any one of Claims 51 to 66, wherein the processing unit further supports: a terminal capability identification entity arranged to identify a level of technical capability of the recipient terminal to reproduce the multimedia message.
68. An apparatus as claimed in Claim 67, when dependent upon Claim 56, wherein the processing unit further supports a message communication entity arranged, when in use, to communicate to the recipient terminal the multimedia message in a modified manner so as to cause the recipient terminal to reproduce the multimedia message in the manner different to that for reproduction of the multimedia message in accordance with the technical specification, the communication of the multimedia message in the modified manner being in response to the level of technical capability of the recipient terminal identified.
69. An apparatus as claimed in Claim 54, wherein the message communication entity is arranged to communicate the multimedia message as a series of time- spaced mark-up language pages.
70. An apparatus as claimed in Claim 69, wherein the series of timespaced mark-up language pages is generated and communicated using the files identified in the text-based message and the multimedia choreography file.
71. An apparatus as claimed in any one of Claims 51 to 70, wherein the at least one identity of the at least one file is the identity of at least two files, the at least two files identified having different file types associated with each other.
72. An apparatus as claimed in any one of Claims 51 to 71, wherein the files identified in the text-based message comprises an identity of an image file and an identity of an audio file.
73. A server apparatus for communicating a multimedia message, the apparatus comprising: means for receiving a text-based message, the textbased message comprising at least one identity of at least one file corresponding to content for a multimedia message; and means for retrieving and using the at least one file identified in the text- based message to compose the multimedia message.
74. A use of a text-based message to communicate at least one desired media component of a multimedia message to a server capable of generating the multimedia message comprising the desired media components.
75. A text-based message for support by a text-based messaging service, the text-based message comprising at least one identity of at least one file corresponding to content for a multimedia message.

S À li! i' SU )' - (I-) hi. raw INVESTOR IN PEOPLE Application No: GB 0310840.4 Examiner: Dr Jan Miasik Claims searched: All Date of search: 16 September 2003 Patents Act 1977: Search Report under Section 17 Documents considered to be relevant: Category Relevant Identity of document and passage or figure of particular relevance to clauns X 1 - 3, 6 - DE 10126847 A (Siemens, AG): see the abstract 8, 11,24, X,-31',64, JP 100326236 A (Mitsubishi Electric Corp.): see the abstract Categories: X Document ndcatmg lack of novelty or Inventive step A Document mdcabng technological background and/or state of the art.

Y Document mdcabng lack of mvenOve step If combined P Document published on or after the declared pnorty date but before the with one or more other documents of same category fihng date of this Invention & Member of the same patent family E Patent document published on or after, but with pronty date earner than, the filing date of this apphcabon

Field of Search:

Search of GB, EP, WO & US patent documents classified m the following areas of the UKCV: H4L Worldwide search of patent documents classified In the following areas of the IPC7: l H04L, H04Q I The following online and other databases have been used m the preparation of this search report: l Online: EPODOC, WPI, JAPIO l An Executvc Agency ol the Department of Trade and Industry