WO2006136872A1 - Procede, systeme, dispositif et programme de transmission de donnees multimedia - Google Patents

Procede, systeme, dispositif et programme de transmission de donnees multimedia Download PDF

Info

Publication number
WO2006136872A1
WO2006136872A1 PCT/IB2005/001798 IB2005001798W WO2006136872A1 WO 2006136872 A1 WO2006136872 A1 WO 2006136872A1 IB 2005001798 W IB2005001798 W IB 2005001798W WO 2006136872 A1 WO2006136872 A1 WO 2006136872A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
multimedia message
multimedia
media charger
message portion
Prior art date
Application number
PCT/IB2005/001798
Other languages
English (en)
Inventor
Ahti Muhonen
Juha. H. Salo
Janne La Aaltonen
Janne Antola
Ari Pajusalo
Ari HÄNNIKÄINEN
Tapio HÄMEEN-ANTTILA
Original Assignee
Nokia Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Corporation filed Critical Nokia Corporation
Priority to EP05764222A priority Critical patent/EP1894388A1/fr
Priority to US11/922,782 priority patent/US20090111433A1/en
Priority to PCT/IB2005/001798 priority patent/WO2006136872A1/fr
Priority to BRPI0520400-3A priority patent/BRPI0520400A2/pt
Publication of WO2006136872A1 publication Critical patent/WO2006136872A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/06—Message adaptation to terminal or network requirements
    • H04L51/066—Format adaptation, e.g. format conversion or compression
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • the present invention relates to a mechanism for transmitting multimedia data via a communication network.
  • the present invention relates to a system, a sender terminal device, a receiver terminal device, a multimedia message server control element, a multimedia service system for transmitting multimedia messages via a communication network, corresponding methods and computer program products .
  • - a network element acting as a communication device or terminal device may for example be any device by means of which a user may access a communication network; this implies mobile as well as non-mobile devices and networks, independent of the technology platform on which they are based; only as an example, it is noted that terminal devices and network elements operated according to principles standardized by the 3 rd Generation Partnership Project 3GPP and known for example as UMTS elements are particularly suitable for being used in connection with the present invention, but also terminal devices and network elements working according to a different standard, such as GSM (Global System for Mobile communications) , can apply the present invention; - a network element can act as a client entity (terminal device) or as a server entity (multimedia message service control element, media charger server element) in terms of the present invention, or may even have both functionalities integrated therein;
  • a network element can act as a client entity (terminal device) or as a server entity (multimedia message service control element, media charger server element) in terms of the present invention, or may even have both functionalities
  • a content of communications, in particular related to multimedia messages, via a traffic channel may comprise at least one of audio data, video data, image data, text data, and meta data descriptive of attributes of the audio, video, image and/or text data, any combination thereof or even, alternatively or additionally, other data such as, as a further example, program code of an application program to be accessed/downloaded;
  • - method steps and/or devices likely to be implemented as hardware components at one of the server / client entities are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS, CMOS, BiCMOS, ECL, TTL, etc, using for example ASIC components or DSP components, as an example;
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention
  • - devices or network elements can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved.
  • ISDN Integrated Services Digital Network
  • wireless communication networks such as the cdma2000 (code division multiple access) system, cellular 3 rd generation communication networks like the Universal Mobile ⁇ Telecommunications System (UMTS) , the General Packet Radio System (GPRS) , or other wireless communication system, such as the Wireless Local Area Network (WLAN) , took place all over the world.
  • UMTS Universal Mobile ⁇ Telecommunications System
  • GPRS General Packet Radio System
  • WLAN Wireless Local Area Network
  • 3GPP 3 rd Generation Partnership Project
  • ITU International Telecommunication Union
  • 3GPP2 3 rd Generation Partnership Project 2
  • IETF Internet Engineering Task Force
  • the system structure of a communication network is such that one party, e.g. a subscriber's terminal equipment, such as a mobile station, a mobile phone, a fixed phone, a personal computer (PC) , a laptop, a personal digital assistant (PDA) or the like, is connected via transceivers and interfaces, such as an air interface or the like, to an access network subsystem.
  • the access network subsystem controls the communication connection to and from the user equipment and is connected via an interface to at least one corresponding core or backbone network subsystem.
  • the core (or backbone) network subsystem switches the data transmitted via the communication connection to a destination party, such as another user equipment, a service provider (server/proxy) , or another communication network.
  • the core network subsystem may be connected to a plurality of access network subsystems.
  • the actual network structure may vary, as known for those skilled in the art and defined in respective specifications, for example, for UMTS, GPRS, GSM and the like.
  • network elements such as the user equipment and another user terminal, a database, a server, etc.
  • intermediate network elements such as control network elements, support nodes or service nodes are involved.
  • MMS multimedia message service
  • MMS represents a successor to the short message service (SMS) and is a service for terminals, in particular wireless terminals like mobile phones or the like, which enables the user to send multimedia content such as images, sounds, together with text messages, data and the like. Since current mobile phones provide also a digital camera function, it is more and more attractive to take photos and send to other subscribers.
  • SMS short message service
  • Fig. 14 shows a block diagram of a structure of a conventional mobile communication network, for example a GSM/GPRS based or UMTS based network, in which a multimedia message is transmitted.
  • the network comprises base station subsystems (BSS) 31 and 32 which are connected with a circuit switched core network 30 comprising a mobile switching centre (MSC) , a visitor location register (VLR) and a home location register (HLR), for example.
  • MSC mobile switching centre
  • VLR visitor location register
  • HLR home location register
  • a packet switched core or backbone network based on GPRS 40 to which the BSS 31, 32 are connected.
  • the GPRS CN/BB comprises several network elements (not shown) , such as a SGSN, a GGSN and the like for controlling and relaying communications.
  • a short message service center (SMSC) 35 as a control element for a short message service is also connected to the MSC/VLR/HLR 30.
  • WAP wireless application protocol
  • PPG push proxy gateway
  • WAP is a standard protocol for the presentation and delivery of wireless information and telephony services on mobile phones and other (wireless) terminals.
  • MMSC multimedia message service center
  • WAP gateway 1060 controls the transmission of multimedia messages in the communication network.
  • MMSC 1070 provides an application interface and a connection to other external applications (EA) or services, such a e-mail, the Internet, other MMSCs in different networks and the like, via a HTTP or SMTP interface.
  • EA external applications
  • a multimedia message is to be transmitted, for example, from a sender terminal 1010 to a receiver terminal 1020 in the system according to Fig. 14, a signalling as shown in Fig. 15 is executed.
  • the MMSC is needed to perform the required store and forward operations of multimedia messages.
  • the message flow in the GPRS network is described in the following.
  • a multimedia message (MM) is sent from the sender terminal (subscriber A) to the MMSC by using a WAP
  • the WAP gateway (messages MlOOl, M1002) .
  • the message comprises the content of the MM and the MSISDN (Mobile Subscriber Integrated Services Digital Network number) .
  • the MMSC checks to which target the MM is directed. In the present case, it is assumed that the destination is the receiver terminal in the same network, while it is also possible to direct the MM to e-mail systems, at external applications or another MMSC.
  • a WAP PUSH operation is executed (message M1006) by means of which a notification is transmitted (message M1004, M1005) from the MMSC to the receiver terminal via SMS (i.e. the SMSC 35 in Fig. 14) .
  • the receiver terminal After receiving the notification the receiver terminal (subscriber B) sends a WAP GET request to the MMSC via the WAP gateway (messages M1006, M1007) .
  • the MM is delivered from the MMSC to the receiver terminal (messages M1008,M1009) and the MM can be displayed.
  • the downloading process is invisible to the end user and the user is notified when the whole message is downloaded and put in the memory, such as a MMS inbox .
  • the MM is sent from the sender terminal 1010 by using standard Internet protocols.
  • the sender terminal 1010 communicates with the WAP gateway 1060 via the BSS 31 and GPRS CN/BB 40.
  • the WAP gateway may translate WAP POST into a HTTP POST towards the MMSC 1070.
  • the MMSC is the interface and router in the system and stores MM in its database (memory) and can access them. Then it decodes the message to find its destination address. The destination can be an email address or a phone number. Then the MMC transmits a notification to the receiver terminal 1020 with the help of the WAP gateway 1060. This can be done in two ways, i.e.
  • the WAP gateway 1060 now transmits an SMS telling the receiver terminal 1020 that it has an MM to get.
  • the receiver terminal 1020 downloads it from the MMSC using WAP GET which is translated, for example, to a regular HTTP GET by the WAP GW before it reaches the MMSC.
  • a different development for enhancing services of communication networks is a so-called multimedia content delivery service concept, also called media charger service concept.
  • Media charger service builds on an efficient delivery of large content files to mobile phones based on subscriptions.
  • the media charger concept utilizes network resources efficiently and provides the consumers with a pleasant user experience.
  • content is organized into content channels, to which the consumers are able to subscribe based on their personal interests.
  • the content delivery process is highly automated: files are automatically delivered to the client application in the consumers' handsets as new content is published in the server.
  • the service can also be configured to focus the file downloads on a certain time window, for example, to enable a service model, in which file transfers take place only during off-peak hours of the underlying network. After receiving a piece of content, a consumer can consume it wherever and whenever he wants to.
  • the media charger service operates over cellular packet networks. The system is basically content type independent. Based on the service configuration, charging can be performed in two different ways (i.e. based on CDRs
  • Fig. 12 shows a general architecture of a media charger concept.
  • the media charger system is based on the client-server architecture.
  • An example for such a media charger system is for example the Media Charger System 3.0 provided by Nokia.
  • the client application 503 resides in a consumer's mobile handset and communicates with a multimedia content control server or multimedia content control element which is referred to hereinafter as a media charger server 500 using Hypertext Transfer Protocol (HTTP) over packet connection.
  • HTTP Hypertext Transfer Protocol
  • the system is not tied to any specific access technology and therefore, for example,
  • the multimedia content control server i.e. the media charger server 500 is the main part of the media charger system.
  • the server which is operated by a media charger administrator, provides interfaces to mobile consumers to interact with the server system. Based on the system configuration, the communication between the server and clients can be performed using HTTP access, or in the second alternative also SMS (Short Message Service) access may be used together with packet connectivity.
  • Content delivery is the core function, which the whole media charger concept is built on. Through this process the content files, provided by a content source 501, are transmitted from the media charger server to subscribers' terminals. The content delivery process is completely transparent to the consumer.
  • the media charger client 503 takes care of automatically retrieving new content items from the server as the items become available.
  • the client may periodically contact the server to check whether new items are available on the subscribed channels. This process is called periodic polling. As a response, the server tells the client to download new content if available and possibly also tells the client to remove some old content items to free enough memory space for the new ones. The client acts upon these instructions and therefore the content available in the terminal becomes updated. If the content item downloading process becomes interrupted for some reason, the media charger client 503 may have in-built intelligence to continue downloading from the point of interruption and thus make the downloading more efficient. The delivery process may be completely automated in the media charger client thus giving a pleasant user experience to the end-users.
  • a HTTP access interface enables the HTTP-based communication between the media charger server 500 and clients. This interface is used for delivery of content and related control messages. Clients poll periodically updates to channel hierarchy / item information via this interface. As a reply, the download server instructs the client to download the correct content files (on the subscribed channels) and to remove the old content files from the terminal if necessary. Content downloading is performed using a pull mechanism: the client requests content downloading from the server.
  • the download server 500 includes support for recovering from interrupted download sessions. To ensure only legal clients have access to the service, a subscriber is authenticated whenever his client communicates with the server. The communication may be performed with XML-based protocol over HTTP (or HTTPS depending on the configuration) .
  • a signalling diagram for the media charger system according to Fig. 12 is shown.
  • the figure describes content download from Media Charger (MC) server to a MC client in a user terminal.
  • MC server transmits service instructions to the client.
  • the service instructions may be transmitted from the MC server which describe, for example, a content, a content type, a content name, a content size, a content partition / ranges, a download time frame, etc.
  • the client sends to the server a HTTP GET request for a content X and its partition / range 1-n. This will be repeated as many times as is needed for the whole content download (1 to n times) .
  • the client may sends an OK signal to the server.
  • the client In the case there happens a failure in the content download, i.e. the client does not get a data packet (RANGE 1-n) , fully or partially, it has requested, the client will send a new request for the same data packet (RANGE 1-n) to the server. This may happen a certain number of times or a certain time period. It is to be noted that a content upload from the MC client to the MC server is executed in a similar way as described above, except signalling will executed vice versa.
  • the MMS is used to transmit multimedia messages between sender and receiver.
  • a method of transmitting a multimedia message comprising the steps of processing a multimedia message to be transmitted by dividing the multimedia message into at least a first message portion and a second message portion, transmitting the first message portion to a multimedia message service control element, transmitting the second message portion to a media charger server element, notifying a receiver terminal about the transmission of the multimedia message, requesting the transmission of the first message portion from the multimedia message service control element to the receiver terminal and requesting the transmission of the second message portion from the media charger server element to the receiver terminal.
  • a system for transmitting a multimedia message comprising sender terminal comprising a media charger proxy functional means which is configured to process a multimedia message to be transmitted by dividing the multimedia message into at least a first message portion and a second message portion, a multimedia message service control element configured to receive the first message portion, a media charger server element configured to receive the second message portion, a message transmission system configured to notify a receiver terminal about the transmission of the multimedia message, wherein the receiver terminal comprises a media charger proxy functional means which is configured to perform at least one of requesting the transmission of the first message portion from the multimedia message service control element to the receiver terminal and requesting the transmission of the second message portion from the media charger server element to the receiver terminal.
  • the proposed solution may comprise one or more of the following features:
  • the processing of the multimedia message may further comprise a generation of a unique identifier for the multimedia message and a provision of each of the first and second message portions with the unique identifier;
  • the notification of the receiver terminal may be executed when the first message portion is received by the multimedia message service control element; alternatively, the notification of the receiver terminal may be executed when the second message portion is received by the media charger server element;
  • the first message portion may be received before the requesting of the second message portion, and the first message portion and the second message portion may be combined for obtaining the multimedia message transmitted, for example on the basis of the unique identifier included in each of the first message portion and the second message portion; - the combination of the first message portion and the second message portion may be executed by a media charger proxy functionality included in the receiver terminal;
  • the requesting of the transmission of the first and the second message portions may be executed by a media charger proxy functionality included in the receiver terminal;
  • the processing may further comprise a check whether a predetermined condition is fulfilled for the multimedia message to be transmitted, wherein the division of the multimedia message, and possibly the generation and provision of the unique identifier, may be inhibited when the predetermined condition is not fulfilled;
  • the processing may be executed by a media charger proxy functionality in a sender terminal;
  • the first message portion may include a header indicating communication information, obtained from the multimedia message, comprising at least one of a written message part, a media charger tag, a network address of the media charger server element and a unique identifier;
  • the second message portion may include at least one of content data of the multimedia message and a unique identifier
  • At least one of the transmission of the first message portion, the transmission of the second message portion and the notification of the receiver terminal may be effected at least in part by using an IP based communication path;
  • the transmissions of the first message portion and the second message portion may be based at least in part on a transmission path including a wireless application protocol;
  • - the notification of the receiver terminal may include at least in part a transmission via a transmission path including a short message service signaling;
  • - the multimedia message service control element and the media charger server element may be included in one server entity;
  • the notification of the receiver terminal may comprise a transmission of a unique identifier and/or a network address of the media charger server element to a media charger proxy functionality in the receiver terminal; then the requesting of the first message portion and the requesting of the second message portion may be executed simultaneously; alternatively, the requesting of the second message portion may be executed prior to the requesting of the first message portion, wherein the requesting of the first message portion may be executed by the media charger server element after receiving an information on the multimedia message service control element with the request for the second message portion from the receiver terminal;
  • the requesting of the second message portion may be executed by the multimedia message service control element after receiving the request for the first message portion from the receiver terminal;
  • the first message portion may be transmitted together with the second message portion to the media charger server element, wherein the transmission of the first message portion to the multimedia message server control element may be executed by the media charger server element; then, the media charger server element may comprise a media charger proxy functionality.
  • a method of transmitting a multimedia message comprising the steps of processing a multimedia message to be transmitted, generating and providing a unique identifier for the multimedia message, transmitting the multimedia message to a media charger server element, transmitting the multimedia message to a multimedia message service control element, notifying a receiver terminal about the transmission of the multimedia message when the multimedia message is received by the multimedia message service control element, requesting the transmission of the multimedia message from the media charger server element to the receiver terminal obtaining the multimedia message from the multimedia message service control element at the media charger server element, and transmitting the multimedia message from the media charger server element to the receiver terminal-
  • a corresponding system for transmitting a multimedia message comprising the steps of processing a multimedia message to be transmitted, generating and providing a unique identifier for the multimedia message, transmitting the multimedia message to a media charger server element, transmitting the multimedia message to a multimedia message service control element, notifying a receiver terminal about the transmission of the multimedia message when the multimedia message is received by the multimedia message service control element, requesting the transmission of the multimedia message from the
  • the proposed solution may comprise one or more of the following features:
  • the processing may further comprise a check whether a predetermined condition is fulfilled for the multimedia message to be transmitted, wherein the transmission of the - ⁇ multimedia message to the media charger server element and the generation and provision of the unique identifier may be inhibited when the predetermined condition is not fulfilled;
  • the generation and provision of the unique identifier for the multimedia message may be executed by one of a media charger proxy functionality of a sender terminal, the media charger server element and the multimedia message service control element.
  • a terminal device configured to send a multimedia message in a communication system, the communication system comprising a multimedia message service control element and a media charger server element, wherein the terminal device comprises a media charger proxy functional means which is configured to process the multimedia message to be transmitted by dividing the multimedia message into at least a first message portion and a second message portion, to transmit the first message portion to the multimedia message service control element, and to transmit the second message portion to the media charger server element.
  • a media charger proxy functional means which is configured to process the multimedia message to be transmitted by dividing the multimedia message into at least a first message portion and a second message portion, to transmit the first message portion to the multimedia message service control element, and to transmit the second message portion to the media charger server element.
  • the proposed solution may comprise one or more of the following features:
  • the media charger proxy functionality may be further configured to process the multimedia message by generating a unique identifier for the multimedia message and providing each of the first and second message portions with the unique identifier;
  • the media charger proxy functional means of the terminal may be further configured to check whether a predetermined condition is fulfilled for the multimedia message to be transmitted, wherein the division of the multimedia message, and possibly the generation and provision of the unique identifier, is inhibited when the predetermined condition is not fulfilled;
  • the predetermined condition may comprise a predefined threshold for a size of the multimedia message;
  • the first message portion may include a header indicating communication information, obtained from the multimedia message, comprising at least one of a written message part, a media charger tag, a network address of the media charger server element and a unique identifier;
  • the second message portion may include at least one of content data of the multimedia message and a unique identifier;
  • the terminal may be configured to transmit, at least in part, at least one of the first message portion and the second message portion via an IP based communication path;
  • the terminal may be configured to transmit at least one of the first message portion and the second message portion at least in part via a transmission path including a wireless application protocol.
  • a terminal device configured to receive a multimedia message in a communication system, the communication system comprising a multimedia message service control element, a media charger server element, and a message transmission system
  • the terminal device comprises a media charger proxy functional means which is configured to receive a notification of the message transmission system about the transmission of a multimedia message, to request the transmission of a first message portion from the multimedia message service control element, to request the transmission of a second message portion from the media charger server element to the receiver terminal, and to combine the first message portion and the second message portion for obtaining the multimedia message transmitted (for example on the basis of a unique identifier included in each of the first message portion and the second message portion) .
  • a media charger proxy functional means which is configured to receive a notification of the message transmission system about the transmission of a multimedia message, to request the transmission of a first message portion from the multimedia message service control element, to request the transmission of a second message portion from the media charger server element to the receiver terminal, and to combine the first message portion and the second message portion for obtaining the multimedia message transmitted
  • the proposed solution may comprise one or more of the following features :
  • each of the first message portion and the second message portion may include a unique identifier;
  • the media charger proxy functional means of the terminal device may be configured to perform requesting the second message portion after the first message portion is received;
  • the first message portion may include a header indicating communication information, obtained from the multimedia message, comprising at least one of a written message part, a media charger tag, a network address of the media charger server element and a unique identifier;
  • the second message portion may include at least one of content data of the multimedia message and a unique identifier;
  • the terminal device may be configured to receive, at least in part, at least one of the first message portion, the second message portion and the notification about the multimedia message via an IP based communication path;
  • the terminal device may be configured to receive at least one of the first message portion and the second message portion at least in part via a transmission path including a wireless application protocol;
  • the terminal device may be configured to receive at least in part the notification about the multimedia message via a transmission path including a short message service signaling; - the terminal device may be configured to display the transmitted multimedia message on the basis of the first message portion and the second message portion received.
  • a multimedia message service control element of a communication system for transmitting a multimedia message comprising a sender terminal comprising a media charger proxy functional means, a receiver terminal comprising a media charger proxy functional means, a media charger server element, and a message transmission element
  • the multimedia message service control element is configured to receive from the sender terminal a first message portion related to the multimedia message, to notify, via the message transmission system, the receiver terminal about the transmission of the multimedia message, to receive a request from the receiver terminal for transmitting the first message portion, and to transmit the first message portion related to the multimedia message to the receiver terminal.
  • the proposed solution may comprise one or more of the following features:
  • the notification of the receiver terminal may be executed when the first message portion is received by the multimedia message service control element; alternatively, the notification of the receiver terminal may be executed when the multimedia message service control element receives an information from the media"charger server element that the media charger server element has received a second message portion;
  • the first message portion may include a header indicating communication information, obtained from the multimedia message, comprising at least one of a written message part, a media charger tag, a network address of the media charger server element and a unique identifier;
  • the multimedia message service control element may be configured to use, at least in part, an IP based communication path for at least one of transmitting the first message portion and notifying the receiver terminal;
  • the multimedia message service control element may be configured to use at least in part a transmission path including a wireless application protocol for transmitting the first message portion; - the multimedia message service control element may be configured to use at least in part a transmission path including a short message service signaling for notifying the receiver terminal;
  • a multimedia service system for transmitting a multimedia message in a communication system, the communication system comprising a sender terminal comprising a media charger proxy functional means and a receiver terminal comprising a media charger proxy functional means, wherein the multimedia service system comprises a media charger server element, a multimedia message service control element and a message transmission element, wherein the multimedia service system is configured to receive from the sender terminal a first message portion at the multimedia message service control element and a second message portion at the media charger server element, the first and second message portions being related to the multimedia message, to notify, via the message transmission system, the receiver terminal about the transmission of the multimedia message, to receive, at the multimedia message service control element, a request from the receiver terminal for transmitting the first message portion, to transmit the first message portion related to the multimedia message and comprising the unique identifier to the receiver terminal, to receive, at the media charger server element, a request from the receiver terminal for transmitting the second message portion, and to transmit the second message portion related
  • each of the first and second message portions may comprise a unique identifier for the multimedia message
  • the notification of the receiver terminal may be executed when the first message portion is received by the multimedia message service control element; alternatively, the media charger server element may configured to send an information to the multimedia message service control element that the second message portion is received, and the multimedia message service control element may be configured to notify the receiver terminal when multimedia message service control element receives the information from the media charger server element that the media charger server element has received the second message portion;
  • the first message portion may include a header indicating communication information, obtained from the multimedia message, comprising at least one of a written message part, a media charger tag, a network address of the media charger server element and a unique identifier;
  • the second message portion may include at least one of content data of the multimedia message and a unique identifier
  • the multimedia message service control element and the media charger server element may be included in one server entity.
  • the media charger proxy functionality can be loaded to the respective elements, such as the terminal devices and the MC server, via a software upgrade. Also, already installed network elements, such as a conventional MC server, can be used for the further tasks defined by the present invention.
  • Fig. 1 shows a block diagram illustrating a communication system in which a multimedia message is transmitted according to an embodiment of the present invention
  • Fig. 2 shows a flow chart of a method for transmitting a multimedia message according to an embodiment of the present invention
  • Fig. 3 shows a block circuit diagram illustrating a terminal device according to an embodiment of the present invention
  • Fig. 4 shows a block circuit diagram illustrating a multimedia message service control element and a media charger server element according to an embodiment of the present invention
  • Fig. 5 shows a signaling diagram illustrating a multimedia message transmission according to an embodiment of the present invention
  • Fig. 6 shows a block diagram illustrating a communication system in which a multimedia message is transmitted, and a message flow according to a second embodiment of the present invention
  • Fig. 7 shows a signaling diagram illustrating a multimedia message transmission according to a third embodiment of the present invention.
  • Fig. 8 shows a signaling diagram illustrating a multimedia message transmission according to a fourth embodiment of the present invention.
  • Fig. 9 shows a signaling diagram illustrating a multimedia message transmission according to a fifth embodiment of the present invention.
  • Fig. 10 shows a signaling diagram illustrating a multimedia message transmission according to a sixth embodiment of the present invention.
  • Fig. 11 shows a signaling diagram illustrating a multimedia message transmission according to a seventh embodiment of the present invention.
  • Fig. 12 shows a media charger server-client structure
  • Fig. 13 shows a signaling diagram of a message flow in the media charger server-client structure according to Fig. 12;
  • Fig. 14 shows a block diagram illustrating a communication system in which a multimedia message is transmitted conventionally
  • Fig. 15 shows a signaling diagram illustrating a conventional multimedia message transmission in the communication system according to Fig. 14;
  • Fig. 16 shows a signaling diagram illustrating a multimedia message transmission according to a modified embodiment of the present invention.
  • Fig. 17. shows a simplified illustration of an application example of the present invention.
  • the general idea of the present invention is to implement media charger system in an multimedia message system in order to allow a reliable and rigid delivery of large files attached, for example, on the MMS messages.
  • a proxy i.e. a so-called media charger MMS proxy application
  • the media charger MMS proxy application is used to process messages, such as multimedia messages, by scanning them and by modifying them (i.e. the content or structure thereof) when the MMS message is transmitted and received.
  • MMS message MMS message
  • the media charger server wherein at the receiving side the content is received and combined, for example, with user written message and the like.
  • WAP GET operation is used for this purpose.
  • a media charger system is implemented between terminals and MMSC, and content transmission and recovery systems from the media charger system are implemented to a messaging system such as a MMS system.
  • the whole transmission process according to the present invention is transparent for a user, i.e. terminal users see the system as a normal MMS system.
  • a simplified structure of a communication network such as a GSM/GPRS or UMTS wireless network, is shown in which an embodiment of the present invention is applicable.
  • the communication network according to Fig. 1 represents only a simplified architecture of such a system in which the present invention is implemented.
  • the network elements and/or their functions described herein may be implemented by software or by hardware.
  • correspondingly used devices or network elements comprise several means (not shown in Fig. 1) which are required for control, processing and communication functionality.
  • Such means may comprise, for example, a processor unit for executing instructions and processing data, memory means for storing instructions and data, for serving as a work area of the processor and the like (e.g.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-only memory
  • input means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like)
  • user interface means for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like)
  • interface means for establishing a communication connection under the control of the processor unit (e.g. wired and wireless interface means, an antenna, and the like) .
  • the respective interfaces and connection paths between the respective network elements and terminals depend on the used communication network type and are known to those skilled in the art. Thus, a detailed description thereof is omitted herein.
  • the communication network comprises base station subsystems (BSS) 31 and 32 including, for example, a base station controller (not shown) and a base transceiver station (not shown) .
  • BSS base station subsystems
  • the BSS 31, 32 are connected with a circuit switched core network 30 comprising a mobile switching centre (MSC) , a visitor location register (VLR) and a home location register (HLR) , for example.
  • MSC mobile switching centre
  • VLR visitor location register
  • HLR home location register
  • CN/BB packet switched core or backbone network
  • the GPRS CN/BB 40 comprises several network elements (not shown) , such as a SGSN, a GGSN and the like for controlling and relaying communications.
  • a short message service center (SMSC) 35 as a control element for a short message service is also connected to the MSC/VLR/HLR 30.
  • the SMSC 35 represents a type of a message transmission element in the communication network.
  • a wireless application protocol (WAP) gateway or a push proxy gateway (PPG) 60 for relaying WAP signalling between network elements is provided in an IP environment.
  • the WAP GW 50 represents another type of a message transmission element in the communication network.
  • WAP is a standard protocol for the presentation and delivery of wireless information and telephony services on mobile phones and other (wireless) terminals.
  • a multimedia message service center (MMSC) 70 as a multimedia message service control element is provided which is connected with the WAP gateway 60.
  • the MMSC 70 controls the transmission of multimedia messages in the communication network.
  • the MMSC 1070 provides an application interface and a connection to other external applications (EA) or services, such a e-mail, the Internet, other MMSCs in different networks and the like, via a HTTP or SMTP interface.
  • EA external applications
  • MC server 50 a multimedia content control server/element which is referred to hereinafter as media charger (MC) server 50 as a media charger server element.
  • media charger is used only as an explanatory expression and comprises all network- elements or servers which may act as a multimedia content control server.
  • the MC server 50 is connected with the network, for example, via the WAP gateway 60.
  • Terminal devices 10 and 20 located in the communication network act as a sender terminal 10, which transmits the multimedia message, and as a receiver terminal 20 to which the multimedia message is to be transmitted. Both terminal devices are provided respectively with a media charger multimedia message service (MC) proxy functionality or functional means 11, 21.
  • the MC proxy functionality is used for processing the multimedia message at the sending side and for processing messages received at the receiving side, respectively.
  • Fig. 3 shows a block circuit diagram illustrating the terminal device according to an embodiment of the present invention. It is to be noted that the general structure of the sender terminal device 10 and the receiver terminal device is similar. The differences in the processing executed in the respective terminal will be described below. However, it is preferable that each terminal device may act as both a receiver terminal device and a sender terminal device in the communication network.
  • the sender terminal device 10 comprises, amongst other elements not shown, a processor or control means 12, such as a CPU or the like, which executes processing steps of the terminal device and controls the functions thereof.
  • the processor 12 is connected with a memory which comprises, for example, a ROM and/or RAM.
  • the processor 12 is provided with the MC proxy functionality 11, which is, for example, an application program or the like executed by the processor 12.
  • a transceiver unit 14 for communicating with the network, e.g. through an air interface to the BSS 31, is connected to the processor 12, wherein the data received and transmitted by the transceiver element 14 are preferably send via the MC proxy functionality 11.
  • a user interface 15 comprising input means like keys, a display and the like is connected to the processor 12 for informing the user, inputting instructions of the user and displaying data to the user.
  • Fig. 4 shows a block circuit diagram illustrating details of the MMSC 70 and the MC server 50.
  • the MMSC 70 comprises a processor/control means 71, such as a CPU or the like, which is connected to a transceiver unit 72, such as a interface to an IP based network or the like.
  • the transceiver unit 72 connects the MMSC 70 for example to the WAP gateway 60. Also other connections, such as to external networks, other MMSCs, an e-mail application and the like can be provided by the transceiver unit 72.
  • a memory 73 such as a RAM, a ROM, a hard disk and the like is provided which is connected to the processor 71.
  • the memory 73 stores control programs and the like, serves as a working area of the processor 71, is used for storing messages or message portions received via the transceiver 71, and the like.
  • the MC server 50 comprises a processor/control means 52, such as a CPU or the like, which is connected to a transceiver unit 53, such as a interface to an IP based network or the like.
  • the transceiver unit 53 connects the MC server 50 for example to the WAP gateway 60.
  • a memory 54 such as a RAM, a ROM, a hard disk and the like is provided which is connected to the processor 52.
  • the memory 54 stores control programs and the like, serves as a working area of the processor 52, is used for storing messages or message portions received via the transceiver 53, and the like.
  • the processor 52 is provided with a MC proxy functionality or application 51.
  • the MC proxy functionality 51 may provide a connection to the MMSC 70, i.e. to the processor 71 thereof, in order to transmit instructions and data.
  • the connection between the MC proxy functionality 51 and the processor 71 can be directly via a corresponding network part, e.g. an IP based network, or via the transceivers 53 and 72, i.e. via the WAP gateway 60.
  • MMSC 70 and the MC server 50 are shown in Fig. 1 as separate network elements, such as servers or the like, it is also possible that both elements 50 and 70 are combined in one server entity 80. Then the respective functions of the MC server 50 and the MMSC 70 are executed by the same processor, transceiver and memory of the server entity 80.
  • a flow chart of a method for transmitting a multimedia message is shown.
  • a multimedia message is to be transmitted from the sender terminal device 10 to, for example, the receiver terminal device 20, in step 110, a transmission step is initiated and the message is checked.
  • the MC proxy functionality 11 of the sender terminal device 10 checks whether an interception condition is fulfilled.
  • the MC proxy functionality 11 checks whether the multimedia message to be transmitted falls under a predetermined condition which causes that the multimedia message is processed by the MC proxy functionality 11.
  • the predetermined condition can be a threshold value for a size of the multimedia message as a whole, or for a size of the attachment such as a picture file or the like.
  • predetermined conditions for example, settings of a user or a system operator can be used, such as that the multimedia message is always (or never) to be processed by the MC proxy functionality 11, or when a predetermined destination is recognized, for example another mobile terminal, by means of the destination telephone number or the like, or when a predetermined transmission network is recognized, i.e. operator or service provider offering MMS transmission services as defined in the present invention.
  • the latter condition may be provided, for example, by a corresponding signaling from the network. If it is decided in step S120 that the predetermined condition is not fulfilled, the multimedia message is not intercepted by the MC proxy functionality 11 and normally transferred (step S125) , as shown for example in Figs. 14 and 15.
  • step S120 determines whether the multimedia message is intercepted and further processed by the MC proxy functionality 11 in step S130.
  • the multimedia message is divided by the MC proxy functionality 11.
  • the MC proxy functionality 11 divides the message into a first message portion and a second message portion.
  • the first message portion comprises, for example, a header indicating communication information which are obtained from the original multimedia message.
  • the communication information may comprise at least one of a written message part, a media charger tag, a network address of the media charger server element, a unique ID (described later) and the like.
  • the second message portion includes in particular the content data of the multimedia message, and/or in addition also text, e.g. a text message, and/or a unique ID (described later) .
  • the MC proxy functionality 11 may divide the multimedia message into more than two message portions, in particular when the multimedia message includes more than one content file.
  • the content data can be also divided in one or more parts, especially if the content data or file is large. However, the parts are handled further in the same way and like the single second message portion mentioned above.
  • the MC proxy functionality 11 generates (step S140) a unique identification element (ID) which is attached to the multimedia message to be transmitted and thus to the first and second message portions.
  • the unique ID is included in the first and the second (or more) message portions, respectively, for binding the content data and the header together.
  • the first message portion (i.e. the header) is transmitted (step S150) from the sender terminal device 10 (i.e. by the MC proxy functionality 11) to the MMSC 70.
  • the transmission can be effected by means of a WAP POST operation via BSS 31, the GPRS CN/BB 40 and the WAP gateway 60.
  • the one (or more) of the second message portions is transmitted to the MC server 50, for example by means of a HTTP PUT operation via BSS 31, the GPRS CN/BB 40 and the WAP gateway 60. It is to be noted that both the first and the one or more of the second message portions include the unique ID.
  • the MMSC 70 When the MMSC 70 receives the first message portion, it retrieves communication information to obtain the destination and transmits a notification to the destination (step S160) , i.e. to the receiver terminal device 20, in order to notify the transmission of a multimedia message.
  • the notification can be transmitted as a WAP notification over SMS to the receiver terminal device, for example, via the WAP gateway 60 to the SMSC 35, where a preset short message indicating the MMS receipt is prepared and sent to the terminal device 20 via the MSC 30 and the BSS 32.
  • the MMSC 70 can also notify the receiver terminal device 20 by means of another signaling mechanism, such as an IP based signaling.
  • a notification to the destination (compare step S160) , i.e.
  • the receiver terminal device 20 comprises a MC proxy functionality 21 which is used for processing the incoming signalling, i.e. the notification from the MMSC 70.
  • the MC proxy functionality 21 recognizes that a processing of the announced multimedia message is necessary when the message or file size indicated in the notification exceeds the threshold value. Furthermore, the existence of the unique ID or of a special MC tag can be used as the indication for the need of processing by the MC proxy functionality 21. Also a user or network operator presetting for always (never) processing incoming messages by the MC proxy functionality 21 can be used.
  • a request for transmitting the first portion is sent, for example, by the MC proxy functionality 21 to the MMSC 70 (step S170) .
  • This request is for example a WAP GET request transmitted via the WAP gateway 60.
  • a request for transmitting the second portion is sent, for example, by the MC proxy functionality 21 to the MC server 50.
  • the second request is normally transmitted when the first portion is received at the MC proxy functionality 21 since from this portion the address of the MC server 50 is retrieved.
  • - 34 - message portion is transmitted by means of a HTTP GET request, for example, either directly to the MC server 50 through an IP network, or via the WAP gateway 60.
  • step S180 both the first and the second message portion are received at the MC proxy functionality 21. Then the MC proxy functionality 21 is able to combine the first and the second portion by means of the unique ID in order to obtain the complete multimedia message comprising all the header information and content data (step S190) , and the multimedia message can be displayed to the user.
  • the MC server 50 after receiving the request from the MC proxy functionality 21, may postpone the transmission of the second message portion until an off-peak time, or the MC proxy functionality 21 sends the request for transmitting the first and/or the second message portion postponed.
  • the postponement of the transmission of the multimedia message can also be initiated by the MC Proxy functionality 11 of the sender terminal equipment, based, for example, on settings for the terminal device 10.
  • the transmission can be reassumed at the interruption position when the interruption cause is not present anymore .
  • a signaling diagram is shown for illustrating the multimedia message transmission according to the present embodiment of the present invention.
  • the MC proxy functionality checks the message to be transmitted, as described above. For example, if the size of the MMS message is bigger than a threshold size, the message is divided to a content (second message portion) , such as a file attachment, and to a header (first message portion) , such as a message header (i.e. written message). Furthermore, unique message identifiers are created and added for the content and the header wherein that identifiers bind the content and header together.
  • the content with the identifiers is transmitted to the MC server by means of a HTTP PUT operation (message M3) , while the header with the identifiers is transmitted by WAP POST operation via the WAP GW to the MMSC (messages M2 and M5) .
  • the MC server can send one or more notifications to the MC proxy functionality in order a acknowledge the receipt of the content, for example.
  • the MMSC When the MMSC receives the message M5 (i.e. the header with the identifiers), it determines the destination (i.e. subscriber B) , it transmits the notification with said message identifiers about the MMS message to a subscriber B terminal. This is performed by a WAP POST message to the WAP GW (message M6) , which in turn transmits a message M7 indicating a WAP notification over SMS to the SMSC, and the SMSC sends a short message or the like including the WAP notification the MC proxy functionality of the receiver side (message M8) .
  • the MC proxy B When the MC proxy B receives the message M8, it informs the user via the terminal device about the WAP notification (message M9) and receives an instruction to retrieve the message by means of an WAP GET operation initiated by the subscriber B terminal (message MlO) . Then, the MC proxy B sends a request in form of the WAP GET request with the message identifiers via the WAP GW to the MMSC (messages Mil and M12) whereupon the MMSC transmits back the header the header of the MMS message including the message identifiers (messages M13, M14) .
  • the MMSC messages Mil and M12
  • the MC proxy B sends a request to transmit the content to the MC server by means of a HTTP GET message including the message identifiers (message M15) .
  • the MC server transmits from the MC server the content of the MMS message including the message identifiers to the MC proxy B (message M16) , and the MC proxy B confirms the (complete) receipt wit message M18.
  • the WAP GET operation with the subscriber B terminal is completed by means of message M17 where the message is provided to the terminal .
  • Fig. 16 shows a signaling diagram illustrating a multimedia message transmission according to a modified example of the preceding embodiment of the present invention.
  • the signaling diagram according to Fig. 16 is similar to that according to Fig. 5 wherein a new message M55 between messages M5 and M6 is added.
  • the other messages as well as their processing and function are similar to those according to Fig. 5 so that only the differences and the facts resulting therefrom will be described in the following.
  • the notification about the message is sent immediately after the MMSC gets information about a transmitted MMS header information (messages M6 to M8 in Fig. 5) .
  • this immediate transmission of the notification is not optimal.
  • the notification when large contents are t be transmitted by means of the media charger system utilizing a principle of transmitting large contents during off-peak times, there might be a time gap between the notification and when the content is actually available at the MC server.
  • a new message M55 is introduced in the system which informs the MMSC that the whole content is now received at the MC server and is available for download.
  • the MC charger is configured to recognize that the full content is received (by means of message path M3) , and then to send the message M55 to the MMSC.
  • the MMSC is configured to await the message M55 from the MC server before the notification message flow (messages M6 to M8) is started. In other words, only after this message M55 is received by the MMSC, the notification signal M6 is sent to WAP GW which further initiates notification M8 as described above.
  • the signal M55 may include information when the content at the MC server is available for an off-peak downloading. By means of such an information there are several options available for the further processing:
  • the notification message flow (messages M6 to M8) is sent when the off-peak time begins
  • the notification message M8 to the MC proxy B includes information about the off-peak time, that is presented to the user, so that user may wait for that specific time for downloading (i.e. message MlO) .
  • the user may ignore this and initiate downloading immediately after receiving the notification M8.
  • the MC proxy B may be configured to automatically initiate the downloading at off-peak time or immediately, depending on the settings in the MC proxy B (subscriber B) .
  • FIG. 6 a block diagram illustrating a communication system in which a multimedia message is transmitted, and a message flow according to a second embodiment of the present invention is shown.
  • the general architecture of the communication system of the second embodiment is similar to that according to that of the first embodiment shown in Fig. 1.
  • the main differences between the second embodiment and the first embodiment concern the processing and operations of the sender terminal device 210 in connection with the MC proxy functionality 211, the receiver terminal device in connection with the MC proxy functionality 221, the MC server 250 and the MMSC 270.
  • the MMS message is not divided by the MC proxy functionality 211 in the sender terminal device 210. This means that the content, such as a file attachment, of a message is also transmitted to the MMCS 270, whereas in the first embodiment the MMS message is divided to the header and the content and the content is only and directly transmitted to the MC server.
  • the MC proxy functionality 211 checks whether the message is to be intercepted, i.e. whether the message is to be send in a normal way or by means of the operation involving the media charger system.
  • the interception is executed, for example, in one of the following situations: always (e.g. according to a presetting by the user or the network operator) ; when the MMS is above a certain size threshold value (e.g. > 500 kB) ; never (e.g. according to a pre-setting by the user or the network operator) .
  • a certain size threshold value e.g. > 500 kB
  • the MC proxy functionality 211 decides that there is no reason for an interception of the message, it is followed the normal MMS message transmission procedure (indicated by the message flow M201B) .
  • MC proxy functionality 211 adds one or more tags or identifiers to one or more of the existing fields in the message. Then, the MC proxy functionality 211 sends/uploads the message (including the tags or identifiers) to the MC server 250 via the BSS 31, the GPRS CN/BB 40 (see message M201A) . This sending/uploading can happen immediately or delayed (e.g. night time), depending on the settings.
  • the MC proxy functionality 211 does not add one or more tags or identifiers but is only responsible for sending/uploading the message to the MC server 250.
  • either the MC server 250 or the MMSC 270 creates and adds one or more tags or identifiers to one or more of the existing fields in the message when the message is received.
  • MC server 250 When MC server 250 receives the MMS message it forwards it to the MMSC 270.
  • the MMSC 270 receives the MMS massage like any normal MMS message sent.
  • the transmission from the MC server 250 to the MMSC 270 can be performed either through the WAP gateway 60 by means of a WAP POST operation (message M202) , or directly to MMSC 60 by means of a HTTP POST operation (message M203) .
  • the MMSC 270 processes the MMS message received from the MC server 250 in a normal way, i.e. the MMSC 270 sends out a notification message to the receiver terminal device 220, for example by means of a short message via the SMSC 35 (message M204) .
  • a terminal with MC proxy capabilities i.e. the receiver terminal device 220 having the MC proxy functionality 221
  • receives a MMS notification e.g. via the SMSC 35
  • the MC proxy functionality 221 intercepts it.
  • the interception may be based on one of the following settings or situations: always (e.g. according to a presetting by the user or the network operator) ; when the MMS is above certain size threshold value (e.g. > 500 kB) ; the MMS is "tagged" by the MC proxy functionality (i.e.
  • the MMS is 'tagged' by the MC server 250 or by the MMCS 270 (in case the MC proxy functionality 211 has not included such tags or identifiers); never (e.g. according to a pre-setting by the user or the network operator) .
  • the MC proxy functionality 221 intercepts the MMS message transmission, it sends, for example, a WAP GET message to the MC server 250 (message M205) .
  • the MC server Upon reception of the WAP GET message, the MC server requests the MMS message from MMSC 270, either via the WAP gateway 60 by using a WAP GET request (message M206) or directly from the MMSC 270 by using a HTTP GET request (message M207) .
  • the MMS message can be delivered to the terminal by means of media charger methods described above.
  • the MC proxy functionality 221 of the receiver terminal device 220 is configured to put the MMS message received from the MC server 250 to a correct folder for a "normal" MMS reception so that the user does not feel any differences to the normal MMS transmission.
  • third to seventh embodiments according to the present invention are described in connection with signaling diagrams shown in Figs. 7 to 11.
  • the third to seventh embodiments are modifications of the first embodiment and applicable in the communication network according to Fig. 1 and the devices and elements according to Figs. 3 and 4.
  • the differences between the first embodiment and the third to seventh embodiments concern the processing and operation of at least one of the MC proxy functionalities of the sender or receiver terminal devices, the MC server and the MMSC. For the sake of simplicity, only those features being different to the foregoing embodiments are described in greater detail.
  • Fig. 7 a signaling diagram illustrating a multimedia message transmission according to the third embodiment of the present invention is shown.
  • the notification from the MMSC (WAP notification over SMS) is sent to the receiver terminal device (subscriber B) , wherein the notification includes also information necessary for finding the MC server and for identifying the MMS message (i.e. in particular the second message portion) .
  • the MC proxy functionality B sends a HTTP GET message (message M311) directly to the MC server at the same time when the WAP GET request (messages M312 and M313) is sent to the MMSC.
  • the WAP notification includes all the information needed for the direct HTTP GET.
  • the MC proxy functionality B receives the first message portion (header, messages M314 and M315) via the WAP GET operation from the MMSC and the second message portion (content, message M316) via HTTP GET operation from the MC server similar to the first embodiment.
  • the further processing of notifying the MC server (message M318) and combining and displaying the MMS message (message M317) are also similar to the first embodiment.
  • Fig. 8 a signaling diagram illustrating a multimedia message transmission according to the forth embodiment of the present invention is shown.
  • the notification from the MMSC (WAP notification over SMS) is sent to the receiver terminal device (subscriber B) , wherein the notification includes also information necessary for finding the MC server, for identifying the MMS message (i.e. in particular the second message portion) and information about the MMSC (address information, identifier or the like) .
  • the MC proxy functionality B sends a HTTP GET message (message M411) directly to the MC server.
  • a HTTP GET message messages M411
  • the WAP notification includes all the information needed for the direct HTTP GET.
  • the MC server sends a WAP GET message to the MMSC (message M412) at the same time when transmitting HTTP GET to the MC proxy functionality B of the receiver terminal device (subscriber B) (message M415) . Therefore, the MC server needs to know via which MMSC the MMS message is routed. This information is received by the HTTP GET message from the MC proxy functionality B, for example.
  • the MMSC transmits the first message portion to the receiver terminal side (messages M413, M414) upon receipt of the WAP GET message from the MC server (message M412) .
  • the MC proxy functionality B receives the first message portion (header, message M414) via the WAP GET operation from the MMSC and the second message portion (content, message M415) via HTTP GET operation from the MC server similar to the first embodiment.
  • the further processing of notifying the MC server (message M417) and combining and displaying the MMS message (message M416) are also similar to the first embodiment.
  • Fig. 9 a signaling diagram illustrating a multimedia message transmission according to the fifth embodiment of the present invention is shown.
  • the notification from the MMSC (WAP notification over SMS) is sent to the receiver terminal device (subscriber B) , wherein the notification includes also information necessary for finding the MC server, and for identifying the MMS message (i.e. in particular the second message portion) .
  • the MC proxy functionality B informs the user (message M509) and receives the instruction to get the MMS message (message M510, WAP GET), the MC proxy functionality B sends a WAP GET request to the MMSC via the WAP GW (messages M511 and M512) .
  • the MMSC receives the WAP GET message, it sends a HTTP GET message (message M513) to the MC server. Therefore, the MC server needs to know via which MMSC the MMS message is routed. This information is received by the WAP GET message from the MC proxy functionality B, for example .
  • the MC server sends a HTTP GET to the MC proxy functionality B of the receiver terminal device (subscriber B) (message M516) while the MMSC transmits the first message portion to the receiver terminal side (messages M514, M515) upon receipt of the WAP GET message from the MC proxy functionality.
  • the MC proxy functionality B receives the first message portion (header, message M515) via the WAP GET operation from the MMSC and the second message portion (content, message M516) via HTTP GET operation from the MC server similar to the first embodiment.
  • the further processing of notifying the MC server (message M518) and combining and displaying the MMS message (message M517) are also similar to the first embodiment.
  • Fig. 10 a signaling diagram illustrating a multimedia message transmission according to the sixth embodiment of the present invention is shown.
  • the MC proxy functionality A in the sender terminal device sends the HTTP PUT directly to the MC server (message M602) .
  • the MC server sends, when the HTTP PUT message is received, one or more notifications to the MC proxy functionality A for acknowledgement and the like, and transmits the first message portion (header, unique ID and the like) by means of a WAP POST operation to the WAP gateway (message M604) .
  • the MC server is provided with a own MC proxy functionality, which is shown in Fig. 4 at reference sign 51, for example.
  • the WAP POST i.e. the second message portion
  • the WAP POST is forwarded to the MMSC (message M605) which then performs the steps defined in the first embodiment for notifying the receiver terminal device side about the message (messages M606 to M608) .
  • Fig. 12 a signaling diagram illustrating a multimedia message transmission according to the seventh embodiment of the present invention is shown.
  • the MC proxy functionality A in the sender terminal device sends the HTTP PUT directly to the MC server (message M702) .
  • the MC server sends, when the HTTP PUT message is received, one or more notifications to the MC proxy functionality A for acknowledgement and the like, and transmits the first message portion (header, unique ID and the like) by means of a WAP POST operation to the MMSC (message M704) .
  • the MC server is provided with a own MC proxy functionality, which is shown in Fig. 4 at reference sign 51, for example.
  • the MMSC sends the WAP POST to the WAP gateway (message M705) which then further performs the steps defined in the first embodiment for notifying the receiver terminal device side about the message (messages M706 and M707) .
  • Fig. 6 a block diagram illustrating a communication system in which a multimedia message is transmitted, and a message flow according to another embodiment of the present invention is shown.
  • the general architecture of the communication system of the this embodiment is similar to that according to that of the first embodiment shown in Fig. 1.
  • the main differences between the second embodiment and the first embodiment concern the processing and operations of the sender terminal device 210 in connection with the MC proxy functionality 211, the receiver terminal device in connection with the MC proxy functionality 221, the MC server 250 and the MMSC 270.
  • the MMS message is divided by the MC proxy functionality 211 in the sender terminal device 210.
  • the content, such as a file attachment, of a message is not transmitted to the MMCS 270, unlike to the second embodiment, i.e. the MMS message is divided to the header and the content and the content is only and directly transmitted to the MC server.
  • the MC proxy functionality 211 checks whether the message is to be intercepted, i.e. whether the message is to be send in a normal way or by means of the operation involving the media charger system.
  • the interception is executed, for example, in one of the following situations: always (e.g. according to a presetting by the user or the network operator) ; when the MMS is above a certain size threshold value (e.g. > 500 kB) ; never (e.g. according to a pre-setting by the user or the network operator) .
  • the MC proxy functionality 211 decides that there is no reason for an interception of the message, it is followed the normal MMS message transmission procedure (indicated by the message flow M201B) .
  • MC proxy functionality 211 divide the MS message to the header part and one or more content parts and adds one or more tags or identifiers to one or more of the parts in the message. Then, the MC proxy functionality 211 sends/uploads the header part (including the tags or identifiers) to the MMSC server 270 via the BSS 31, the GPRS CN/BB 40 (see also message M201B) . Then, the MC proxy functionality 211 sends/uploads the content (including the tags or identifiers) to the MC server 250 via the BSS 31, the GPRS CN/BB 40 (see message M201A) . This sending/uploading can happen immediately or delayed (e.g. night time), depending on the settings.
  • the MC proxy functionality 211 does not add one or more tags or identifiers but is only responsible for sending/uploading the message to the MC server 250.
  • either the MC server 250 or the MMSC 270 or both creates and adds one or more tags or identifiers to one or more of the existing parts in the message when the message is received.
  • the MMSC 270 processes the MMS message header part received from the MC proxy 211 in a normal way, i.e. the MMSC 270 sends out a notification message to the receiver terminal device 220, for example by means of a short message via the
  • SMSC 35 (message M204).
  • a terminal with MC proxy capabilities i.e. the receiver terminal device 220 having the MC proxy functionality 221
  • receives a MMS notification e.g. via the SMSC 35
  • the MC proxy functionality 221 intercepts it.
  • the interception may be based on one of the following settings or situations: always (e.g. according to a pre- setting by the user or the network operator) ; when the MMS is above certain size threshold value (e.g. > 500 kB) ; the MMS is "tagged" by the MC proxy functionality (i.e.
  • the MMS is ⁇ tagged' by the MC server 250 and/or by the MMCS 270 (in case the MC proxy functionality 211 has not included such tags or identifiers); never (e.g. according to a pre-setting by the user or the network operator) .
  • the MC proxy functionality 221 intercepts the MMS message transmission, it sends, for example, a WAP GET message to the MMSC server 270 (message M208) .
  • the MMSC server 270 Upon reception of the WAP GET message, the MMSC server 270 transmits the MMS message header part to the MC proxy functionality 221, via the WAP gateway 60 by using a WAP GET request (message M209) .
  • the MC proxy 211 may request the MMS message content from MC server 250 by using HTTP GET via link M205. This is similar to that described in the second embodiment, for example, so that a further detailed description thereof is omitted here.
  • FIG. 17 a simplified illustration of a communication network portion is shown by means of which another embodiment, which represents some sort of an application example of the present invention as an use case is described.
  • reference sign 200 denotes a sender terminal device, which may be similar to the sender terminal device 10 according to Fig. 1.
  • Reference sign 900 denotes one or more receiver terminal devices which may be similar to the receiver terminal device 20 according to Fig. 1.
  • Reference sign 300 denotes a media charger server.
  • the media charger server 300 may have the same functionality like those of the preceding embodiments and includes further a dating service application.
  • network elements are to be provided in the communication network in order to be able to perform the message transmission as described below.
  • These network elements include, for example, all additional network elements, servers, communication links and the like as shown and described in Fig. 1.
  • the general idea is to make message exchange to be more comfortable, for example dating to be more comfortable, and to increase the information received from the respective opponent. This is achieved by allowing both sides to create personal information and personal media files, where are both own features as well as what kind of features a party is looking for from the possible opponent. When additional information is set there, it is possible to get solutions, which are matching (matching can be presented, for example, asmin figures) .
  • a possible use of a media charger system is to use a Dating solution to record videogreetings etc. and to send those to the server. Then, it is possible to "subscribe" the persons information as a channel or sub-channel and every time there will be more content, then automatically this information is sent to the terminal device.
  • the greetings can be set to be visible to a) all subscribers (terminal devices 200 and 900), b) set of subscribers based on ID (e.g. only left and right terminal device 900) or c) just one dedicated subscriber (e.g. only leftmost terminal device 900).
  • ID e.g. only left and right terminal device 900
  • c just one dedicated subscriber
  • the concept of the present embodiment is to use the media charger server 300 as a two direction communication channel with grant/deny permission basis. Furthermore, the media charger server 300 is used to handle automatically the distribution list, for example after subscription or inventing based on handling (both user or host can start the discussion / communication chain) . At the same time, the whole system can be managed, measured, handled with secure manners and be extreme personal to create highest possible user experience without loosing anything from usability. In addition, a manual acceptance or auto acceptance can be used, for example, based on a set of rules to decide who can subscribe the personal videogreetings.
  • the personal information and personal media files may be transmitted preferably as MMS messages via MMS and media charger systems. This means, that transmitting and also receiving devices requires special media charger proxy functionalities, like those described above. If the personal media files (content part) are large (larger than, for example, a predetermined threshold value) , they may be routed via the media charger system, while a header part of the MMS message is routed via the MMS system (MMSC) .
  • MMS system MMS system
  • the whole system can be managed, measured, handled with secure manners and be extreme personal to create highest possible user experience without loosing anything from usability, at the same time. Furthermore, it is possible to use a manual acceptance or an automatic acceptance based on a set of rules to decide who can subscribe the personal videogreetings .
  • the system is more personal, for flexible and more usable than a conventional MMS-service providing real communication solution for two- or multidirectional communication. From the other systems, who would the host know, it is possible to receive information about how many other subscribers/terminals has check his/her greeting or announcement. It is to be noted that the system according to this embodiment is able to get information in real-time.
  • the measures defined in the present invention are also applicable to other types of messages to be transmitted via a communication network, in particular to those messages having a larger file attachment or a large size.
  • the actual size of the message or attachment for which the present invention is preferably to be executed may vary, for example, in dependence of the communication network concerned.
  • the described network elements, such as the MC server or the MMSC may be different to those used in another application of the present invention as long as the basic functions like message forwarding and processing are similar.
  • transmission paths defined in the preceding embodiments such as the WAP, SMS, HTTP or IP based transmission paths, can be replaced by other present or future types of transmission paths.
  • the measures defined in the preceding embodiments are implementable by means of a computer program product, such as a software program or the like, which can be directly loaded into the internal memory of a computer which in turn executes the processing steps and functions defined above.
  • the computer program product causes the computer or parts of the computer to act, for example, as the MMSC, the MC server, the terminal device, the MC proxy functionality and the like described above.
  • the computer program product may comprise a computer-readable medium on which corresponding software code portions are stored.
  • a method and system for transmitting a multimedia message wherein a multimedia message to be transmitted is processed by dividing the multimedia message into at least a first message portion and a second message portion.
  • the first message portion is transmitted to a multimedia message service control element, and the second message portion is transmitted to a media charger server element.
  • a receiver terminal is notified about the transmission of the multimedia message
  • the transmission of the first message portion from the multimedia message service control element to the receiver terminal is requested, and the transmission of the second message portion from the media charger server element to the receiver terminal is requested.
  • the first message portion and the second message portion are combined for obtaining the multimedia message transmitted.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

L'invention concerne un procédé et un système de transmission (10) d'un message multimédia, procédé dans lequel un message multimédia à transmettre est traité en divisant le message multimédia en au moins une première portion de message et une seconde portion de message. La première portion de message est transmise à un élément de contrôle de service de message multimédia (70), et la seconde portion de message est transmise à un élément serveur chargeur média (50). Un terminal récepteur (20) est notifié quant à la transmission du message multimédia. La transmission de la première portion de message, de l'élément de contrôle du service de message multimédia (70) au terminal récepteur (20), est demandée, et la transmission de la seconde portion de message, de l'élément serveur chargeur média (50) au terminal récepteur (20) est demandée. Au terminal récepteur (20), la première portion de message et la seconde portion de message sont combinées en vue d'obtenir le message multimédia transmis.
PCT/IB2005/001798 2005-06-24 2005-06-24 Procede, systeme, dispositif et programme de transmission de donnees multimedia WO2006136872A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP05764222A EP1894388A1 (fr) 2005-06-24 2005-06-24 Procede, systeme, dispositif et programme de transmission de donnees multimedia
US11/922,782 US20090111433A1 (en) 2005-06-24 2005-06-24 Method, System, and Program for Transmission of Multimedia Data
PCT/IB2005/001798 WO2006136872A1 (fr) 2005-06-24 2005-06-24 Procede, systeme, dispositif et programme de transmission de donnees multimedia
BRPI0520400-3A BRPI0520400A2 (pt) 2005-06-24 2005-06-24 método, sistema, dispositivo e produto de programa de computador para transmissão de dados multimìdia

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2005/001798 WO2006136872A1 (fr) 2005-06-24 2005-06-24 Procede, systeme, dispositif et programme de transmission de donnees multimedia

Publications (1)

Publication Number Publication Date
WO2006136872A1 true WO2006136872A1 (fr) 2006-12-28

Family

ID=35789383

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2005/001798 WO2006136872A1 (fr) 2005-06-24 2005-06-24 Procede, systeme, dispositif et programme de transmission de donnees multimedia

Country Status (4)

Country Link
US (1) US20090111433A1 (fr)
EP (1) EP1894388A1 (fr)
BR (1) BRPI0520400A2 (fr)
WO (1) WO2006136872A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013074006A1 (fr) * 2011-11-17 2013-05-23 Telefonaktiebolaget L M Ericsson (Publ) Remise de messages multimédia divisés

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100397819C (zh) * 2004-05-26 2008-06-25 华为技术有限公司 一种多媒体消息计费的实现方法
CA2631770A1 (fr) * 2005-12-01 2007-06-07 Firestar Software, Inc. Systeme et procede pour echanger des informations entre des applications d'echange
KR100810246B1 (ko) * 2006-02-24 2008-03-06 삼성전자주식회사 휴대용 단말기에서 멀티미디어 메시지 수신 방법
US20080065728A1 (en) * 2006-09-08 2008-03-13 Pitney Bowes Incorporated Method and system for service provider to be compensated for delivering e-mail messages while reducing amount of unsolicited e-mail messages
US8060063B1 (en) * 2007-09-07 2011-11-15 Sprint Communications Company L.P. Presenting messages on a mobile device that is currently presenting other media content
US8595748B1 (en) * 2007-12-21 2013-11-26 Ibiquity Digital Corporation Systems and methods for transmitting and receiving large objects via digital radio broadcast
US8078693B2 (en) * 2008-04-14 2011-12-13 Microsoft Corporation Inserting a multimedia file through a web-based desktop productivity application
US8463932B2 (en) * 2008-08-28 2013-06-11 Red Hat, Inc. Fast HTTP seeking
JP5489807B2 (ja) * 2010-03-25 2014-05-14 キヤノン株式会社 情報処理装置、帳票データ作成方法、及びコンピュータプログラム
CN103037314B (zh) * 2011-09-30 2016-03-09 国际商业机器公司 用于在自主网络中的移动终端上群发消息的方法
US20130315161A1 (en) * 2012-05-24 2013-11-28 Seven Networks, Inc. Wireless network traffic routing through traffic optimization and tracking of destination address to facilitate service provider billing
CN103139049B (zh) * 2013-01-29 2015-09-30 腾讯科技（深圳）有限公司 信息交互方法
US10484493B2 (en) * 2015-11-17 2019-11-19 At&T Intellectual Property I, L.P. Method and apparatus for communicating messages
US11930357B2 (en) * 2022-08-01 2024-03-12 Syniverse Technologies, Llc Trusted sender signature messaging system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040117312A1 (en) * 2002-12-17 2004-06-17 Elena Lialiamou Messaging services for pre-pay users
US20050054287A1 (en) * 2003-09-06 2005-03-10 Lg Electronics Inc. Apparatus and method for dividing MMS message in a mobile terminal

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005086507A (ja) * 2003-09-09 2005-03-31 Alps Electric Co Ltd 無線通信システム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040117312A1 (en) * 2002-12-17 2004-06-17 Elena Lialiamou Messaging services for pre-pay users
US20050054287A1 (en) * 2003-09-06 2005-03-10 Lg Electronics Inc. Apparatus and method for dividing MMS message in a mobile terminal

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Access and Terminals (AT); Fixed network Multimedia Messaging Service (F-MMS); PSTN/ISDN; Part 4: Multimedia Message communication between a fixed network Multimedia Messaging Terminal Equipment and a Multimedia Messaging Service Centre; ETSI ES 202 314-4", ETSI STANDARDS, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE, SOPHIA-ANTIPO, FR, vol. AT-Features, no. V111, May 2004 (2004-05-01), XP014015419, ISSN: 0000-0001 *
"Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Fixed network Multimedia Messaging Service (F-MMS); Combined PSTN/ISDN & IP network access and native IP network access; Service description", ETSI STANDARDS, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE, SOPHIA-ANTIPO, FR, no. v0.0.5, September 2004 (2004-09-01), XP014029453 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013074006A1 (fr) * 2011-11-17 2013-05-23 Telefonaktiebolaget L M Ericsson (Publ) Remise de messages multimédia divisés
US9985915B2 (en) 2011-11-17 2018-05-29 Telefonaktiebolaget Lm Ericsson (Publ) Divided mulitmedia messaging delivery

Also Published As

Publication number Publication date
BRPI0520400A2 (pt) 2009-05-05
EP1894388A1 (fr) 2008-03-05
US20090111433A1 (en) 2009-04-30

Similar Documents

Publication Publication Date Title
US20090111433A1 (en) Method, System, and Program for Transmission of Multimedia Data
JP4440779B2 (ja) Ｓｍｓおよびテキストメッセージを送信するシステム並びに方法
US6629130B2 (en) Method and apparatus for processing electronic mail
JP4584515B2 (ja) 無線通信システムにおけるテキストメッセージのマルチメディア添付ファイルを送信するシステム及び方法
KR100738962B1 (ko) 멀티미디어 메시징 서비스
US7653734B1 (en) Method for implementing a multimedia messaging service, a multimedia messaging system, a server of a multimedia messaging system and a multimedia terminal
JP4695078B2 (ja) メッセージ処理
JP4819308B2 (ja) テレコミュニケーション装置とテレコミュニケーションネットワークとの間でマルチメディアメッセージングサービスを制御するための方法、各スマートカードおよびテレコミュニケーション装置
KR100585781B1 (ko) 모바일 인스턴트 메시징 서비스의 파일 전송 방법
US20070178895A1 (en) Method, network entity, system, mobile device and computer program product for automatic provisioning of a service
JP5589099B2 (ja) 特定用途向け登録データまたは登録解除データの送信方法、そのための、システム、サーバ、通信端末
WO2004099895A2 (fr) Systeme, appareil et procede permettant le traitement automatique des messages dans des terminaux
EP2334035B1 (fr) Gestion des informations de présence dans un système de communication
WO2007095816A1 (fr) Procédé et système d'acheminement de messages d'un service de messagerie multimédia
US20050256959A1 (en) Method of and system for multimedia messaging system interoperability
RU2323543C2 (ru) Способ передачи данных, в особенности с мультимедийным содержанием, в сети мобильной связи
JP2009296100A (ja) メッセージ通信処理方法、メッセージ通信処理システム及び通信端末装置
JP5255915B2 (ja) メール送信処理方法及び通信端末装置
KR100727762B1 (ko) 광대역 코드분할다중접속 네트워크를 통해 전송되는 단문메시지(ｓｍｓ)를 장식하는 방법 및 시스템
KR100559347B1 (ko) 멀티미디어 메시징 서비스 구현 방법, 멀티미디어 메시징시스템, 멀티미디어 메시징 시스템 서버 및 멀티미디어단말기
JP2009296099A (ja) 電話通信処理方法、電話通信処理システム及び通信端末装置
JP5011208B2 (ja) メール処理システム及び通信端末装置
JP5011210B2 (ja) 通信システム
JP5011209B2 (ja) メール処理システム及び通信端末装置
JP5227665B2 (ja) 通信端末装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2005764222

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: DE

WWE Wipo information: entry into national phase

Ref document number: 10135/DELNP/2007

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2007149030

Country of ref document: RU

WWE Wipo information: entry into national phase

Ref document number: 11922782

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 2005764222

Country of ref document: EP

ENP Entry into the national phase

Ref document number: PI0520400

Country of ref document: BR

Kind code of ref document: A2