[go: up one dir, main page]

WO2007080570A1 - Insertion d'image pour messagerie texte - Google Patents

Insertion d'image pour messagerie texte Download PDF

Info

Publication number
WO2007080570A1
WO2007080570A1 PCT/IL2007/000005 IL2007000005W WO2007080570A1 WO 2007080570 A1 WO2007080570 A1 WO 2007080570A1 IL 2007000005 W IL2007000005 W IL 2007000005W WO 2007080570 A1 WO2007080570 A1 WO 2007080570A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
text
messages
user
mmsc
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IL2007/000005
Other languages
English (en)
Inventor
Eyal Gura
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
PicScout Israel Ltd
Original Assignee
PicScout Israel Ltd
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 PicScout Israel Ltd filed Critical PicScout Israel Ltd
Publication of WO2007080570A1 publication Critical patent/WO2007080570A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72439—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for image or video messaging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42382—Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/0024—Services and arrangements where telephone services are combined with data services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Definitions

  • the present invention relates to a method and apparatus for image insertion into text messaging, such as a cellular telephone SMS 5 and, more particularly, but not exclusively to such image insertion that relies upon an automatic analysis of the text.
  • apparatus for enhancement of text messages passing over a network comprising: a text analyzer for analyzing at least one of text of said passing messages, and a context of said message, a search unit for searching for a media file in accordance with said analysis, and a media inserter for inserting media from said search into said analyzed messages, thereby to enhance said passing messages for sending on to said recipient.
  • a method for enhancement of text messages passing over a network comprising: analyzing at least one of text of said passing messages, and a context of said message, searching a database of media files in accordance with a result of said analysis, and inserting media files retrieved by said search into said analyzed messages, thereby to enhance said passing messages for sending on to said recipient.
  • a method of enhancing text messages passing over a network comprising: analyzing respective text messages, using said analysis to identify a suitable media file from a database of media files, and inserting said media file into said text message to provide a media-enhanced text message for sending on to a recipient.
  • a user client for a message enhancement engine for enhancing text messages being sent over a network comprising: a text message interception unit for interception of text messages prior to sending; a model for indicating which messages are to be enhanced; and a message director, associated with said text message interception unit and said model for sending respective text messages to said message enhancement engine if they correspond to said model.
  • Implementation of the method and system of the present invention involves performing or completing certain selected tasks or steps manually, automatically, or a combination thereof.
  • several selected steps could be implemented by hardware or by software on any operating system of any firmware or a combination thereof.
  • selected steps of the invention could be implemented as a chip or a circuit.
  • selected steps of the invention could be implemented as a plurality of software instructions being executed by a computer using any suitable operating system.
  • selected steps of the method and system of the invention could be described as being performed by a data processor, such as a computing platform for executing a plurality of instructions.
  • Fig. Ia is a simplified diagram illustrating a text message being enhanced according to a first preferred embodiment of the present invention
  • Fig. Ib is a simplified block diagram illustrating an exemplary system in which the text enhancement apparatus receives text message inputs from multiple input devices/applications and outputs an appropriately formatted enhanced message;
  • Fig. 2 is a simplified diagram illustrating an apparatus for enhancing of a text message according to a preferred embodiment of the present invention
  • Fig. 3 is a flow chart showing the operation of a preferred embodiment of the present invention.
  • Fig. 4 is another simplified diagram showing an application server according to a preferred embodiment of present invention.
  • Fig. 5 is a simplified diagram showing components of and around the application server of Fig. 4,
  • Fig. 6 is a diagram illustrating message flow in a successful message enhancement scenario according to a preferred embodiment of the present invention.
  • Fig. 7 illustrates message flow in a first unsuccessful message enhancement scenario according to a preferred embodiment of the present invention.
  • Fig. 8 illustrates message flow in a second unsuccessful message enhancement scenario according to a preferred embodiment of the present invention
  • Fig. 9 is a simplified block diagram of an apparatus for enhancement of text messages passing over a network, according to a preferred embodiment of the present invention.
  • Fig. 10 is a simplified flow chart of a method for enhancement of text messages passing over a network, according to a preferred embodiment of the present invention.
  • Fig. 11 is a simplified flow chart of a method for enhancing text messages passing over a network, according to a preferred embodiment of the present invention.
  • the present embodiments comprise an apparatus and a method for enhancement of a text message as it passes over a network, typically a cellular network.
  • the message is enhanced by the addition of media files (also denoted media items) such as image, sound and video files. Enhancement is based on understanding the text or context of the originating message. In some embodiments the enhancement is first returned to the sender for approval. Other embodiments teach a user-configured model for defining which messages are enhanced and which not.
  • a text message 10 is sent by the user of a first cellular telephone 12. Over the network the message is enhanced by the addition of images 16 and 18 to form enhanced message 20.
  • the message as sent is an SMS message. However the message as received is an MMS message, since it includes multimedia attachments.
  • the enhancement is preferably carried out over the cellular network as will be explained below.
  • the simple text message is personalized by automatically including content reflecting the text meaning, based on an analysis of the message text, context, and user preferences. Examples of such text messages include:
  • Application-to-application messages i.e. instant messaging
  • Blog posts and Blog post titles the image may be automatically selected to suit the content that is described in the blog or in its title).
  • Fig. Ib illustrates an exemplary system in which the text enhancement apparatus 100 receives text message inputs from multiple input devices/applications, 110.1-110.5, and outputs the enhanced message formatted for the particular device/application on which the enhanced message will be displayed, such as cellular telephone 120.1 or IM application 120.5.
  • Fig. 2 is a simplified diagram showing an apparatus for enhancement of text messages passing over a cellular network according to a first preferred embodiment of the present invention.
  • the apparatus is preferably located in the cellular network and is associated with the servers that provide SMS and MMS features to the network, namely the Short Message Service Center (SMSC) 20 and the Multimedia Service Center (MMSC) 22.
  • SMS Short Message Service Center
  • MMSC Multimedia Service Center
  • a message interpreter 24 receives the SMS message and analyzes it for suitable enhancements. The analysis may involve analyzing the text of the message being sent for keywords or key phrases, based on which images may be selected. Thus, keywords indicating sentiment may be used to select images illustrating the corresponding emotion. Alternatively the context of the message, say the identity of the recipient may be matched with pre-set lists of the sender. Thus certain images may be used for groups of users, say business contacts, and other images may be used for personal contacts. Yet again other images or sets of images may be used for designated close personal contacts.
  • the location of the sender or recipient may be used to include images that include greetings in the local language, or the location may be used to include characters of local appearance, including locally recognized costumes or local racial appearance.
  • a particular preferred embodiment uses both keywords from text and the message context.
  • the context indicates a set or collection of images to be used and the keywords point to individual images within the set or collection.
  • the message inserter thus includes both a text analyzer 26 which finds sentiments within the text of the message, and a context analyzer 28, which determines the context of the message.
  • the text analyzer is preferably able to analyze text, including abbreviations often used in text messaging, such as "gr8" for "great". Such text analyzers are known in the art. Principally the feature is intended to allow machine analysis of the text, and may include text recognition and natural language processing (NLP) algorithms as appropriate. The algorithms used are optimized to understand context from very short messages and are preferably self-learning.
  • NLP natural language processing
  • An image database 30 stores images for insertion into the message.
  • the image database is preferably a large database in which the images are selected and categorized in ways that are appropriate for use with the message interpreter. That is to say images are chosen for their suitability with text messages, and are indexed for usability with the message interpreter.
  • the database is connected to an image inserter 32 which takes the images selected at the database and inserts them into the text messages.
  • the result is a multimedia message which is an enhanced version of the original text message.
  • the multimedia message is then sent on to the recipient.
  • the database may include a set of stock images or videos, for example of the kind provided by Gettyimages.com and clipart.com, or stock animations such as provided by animationfactory.com.
  • the text of the original message is correlated with images in the image database.
  • the context may be determined by comparing the recipient against user lists of his recipients.
  • the user may designate particular recipients as business associates, others as customers, others as personal Mends, yet others as close personal friends etc. Alternatively the user may designate individual recipients as special.
  • a message grabber 34 may be supplied to identify and grab messages originating from subscribed senders only. Thus the service becomes an added-value service for which it is possible to charge.
  • the message grabber may be located on the network or may be a client installed at the sender's telephone.
  • a preview functionality is provided.
  • the preview functionality bounces the enhanced message back to the sender for approval prior to sending on to the recipient, allowing the user to approve or disapprove of the selected images. If the enhanced message is not approved, the user may select a "shuffle" function, and return the message for enhancement with different media files from those currently proposed.
  • a learning feature can be added to allow the network to learn the preferences of the user. Such a learning feature may include a feedback mechanism that allows images to be ranked according to user approval. Higher ranked images are then more often inserted. The ranking may be based on individual users or an overall ranking may be made based on all users, or users having similar characteristics, say male users under the age of 25.
  • a user feedback mechanism may be provided for allowing a user to directly indicate preferred images for insertion.
  • a user client at the sender may include the message grabber. The operational procedure with such a client is as illustrated in Fig. 3.
  • the message grabber grabs the SMS before leaving the handset and sends it to the server (step 1).
  • the server analyzes the text or content or both of the message
  • step 2 uses the analysis result to get a suitable media file for inserting into the text (step 3).
  • the enhancement is inserted (step 4) and is then sent as a preview MMS for approval by the sender (steps 5-6).
  • the MMS Upon approval the MMS is sent to the recipient (step 7). If not approved, the text is resubmitted for enhancement.
  • the approval stage may be left out and the message is sent straight to the recipient.
  • the sender has the option of selecting the preview stage by pressing a "compose” button before sending the SMS.
  • the compose button If the compose button is used then the text is transmitted to the server and the result is sent as a preview. Upon approval the sender presses "send”, and the message is sent as MMS.
  • the user upon pressing send the user is queried by the message grabber whether the message should be enhanced. The user then indicates whether the enhancement process should be performed or if the message should be sent to the recipient as an unenhanced text message.
  • the application is preferably activated automatically upon SMS submission.
  • the application may require an initial installation procedure to install and configure the user client.
  • the installation procedure may ask the user for preferences of his future MMSs (i.e. his location, whether he prefers art images or 3d images or motion pictures or cartoons, whether different preferences should be used for different recipients etc.
  • the images are provided in a format that makes it difficult to reuse them in other applications, say for copyright purposes.
  • the user client may work together with handset features such as the phone book, calendar and others.
  • the user can be given the option to set the application to be his default SMS sending system.
  • the user is provided with a personalized web site to manage his accounts, set up new preferences for new recipients etc.
  • the user may be set up to adjust his account both directly from his telephone or from the website as convenient.
  • the following features may be provided via the website/direct updating: • The user can set his preferences at any given time for images/video/music he likes to be added to his text.
  • the user can rank files.
  • the website is preferably connected to the server on which the service is provided and images may be ranked according to their actual usage as well. Thus if the user did not like the image and asked for the message to be recomposed, then the image will get a negative rank. The more often the image is approved of the higher the ranking.
  • the user downloads the application, or obtains it using his handset from the carrier.
  • the application is configured.
  • the application sends the SMS text to the server.
  • the server matches appropriate images or other media files to the text and sends them back to the user.
  • the application presents a preview of the enhanced message that is going to be sent. 9. The user may press "compose” again and ask for other images.
  • the MMS is displayed to the receiver, preferably with a link to download the application for his handset
  • the present embodiments provide an application whose purpose is to send a text message enhanced with MMS media, typically but not limited to pictures which are sent to friends.
  • the sender produces regular SMS text for sending.
  • the message is sent in the normal way to the SMSC 20 but is then diverted to an application server 40, which searches for pictures based on words in the message text.
  • the application server 40 enhances the original text messages with the selected pictures and sends this upgraded MMS message to the destination on behalf of the sender.
  • the application server communicates with the SMSC 20 and the MMSC 22 of the network operator.
  • the application server is connected to a large image database 30 (also denoted a content "bank") of pictures or other media files.
  • the application server can be integrated into networks based on Global System for Mobile Communications (GSM), Code-Division Multiple Access (CDMA), Time Division Multiple Access (TDMA) or Integrated Digital Enhanced Network (iDEN) networks since it is signaling independent, and in fact can be work on Voice over IP (VoIP) and any other networks that can send text messages with media files.
  • GSM Global System for Mobile Communications
  • CDMA Code-Division Multiple Access
  • TDMA Time Division Multiple Access
  • iDEN Integrated Digital Enhanced Network
  • the application server comprises: 1. Image inserter Engine 50 2. SMSC Connector 52
  • CDR Call Detail Record
  • WEB tools are preferably provided:
  • Database 30 preferably stores: • MMS Pictures
  • the image inserter engine 50 (also denoted the “enhancement engine”, the “application engine” or the “engine") is the main business logic of the application. It is responsible for some or all of the following tasks:
  • the SMSC connector 52 is responsible for interfacing with the SMSC to carry out the following tasks: 1. Connecting on initialization and continuously maintaining connections to the SMSC in order to receive Incoming Packets and send outgoing messages,
  • the MMSC connector 54 is responsible for interfacing with the MMSC to carry out the following tasks: 1. Sending outgoing MMS messages to recipient, and 2. Requesting a delivery report from the MMSC and handling the response, timeout and failures.
  • a Picture Administration & Provisioning Interface is preferably provided for
  • Picture Administration & Provisioning is done through a web client who prepares the data for quick searching by the application.
  • the Users Administration & Provisioning Interface is preferably provided to add or delete a new user, and managing the sender model, to be described hereinbelow.
  • API application program interface
  • CDR Collector 62 preferably collects transaction records written by the server application component, and inserts them for concentrated storage for future data warehousing and for transfer it to Off-Line billing operator mediation.
  • the On-Line Billing Connector (Pre-Paid) 56 provides access to the operators online billing system.
  • the connector is responsible for generating charging requests to the online billing system for authorized actions.
  • the CDR Statistics & Reporting unit 62 operates a scheduled process which summarizes the collected CDRs to statistics on daily and monthly basis, and sends the report to the appropriate customers.
  • the billing system allows for the system to be used with digital asset management to ensure that sources of the media material are rewarded for their work.
  • the Topology & Monitoring manager 58 preferably manages the application initiation process by proving processes with information on other existing processes and notifying in case of process failure and restart.
  • the manager 58 sends Simple Network Management Protocol (SNMP) traps in case of a failure in interconnect internal components and about failure in connection to other home domains.
  • SNMP Simple Network Management Protocol
  • the manager exposes the SNMP interface for getting dynamic data onto the application servers.
  • a logging unit is a server-side facility that provides logging capabilities to server components.
  • Server components may launch operations and receive events. It is noted that the ability to monitor these tasks is contributive to quality management of the entire platform.
  • Each one of these components can run multiple instances and load-sharing and can run on multiple severs. This approach supports redundancy and scalability since failure of one server does not interfere with the performance of other transactions.
  • the application engine preferably works using an N+l model, meaning it is divided into N+l instances. All the registered users are divided between the N instances of each engine, so that each engine takes one N-th part of the users. The consequence is that inter-routing to the engine depends on the Sender.
  • the topology unit 58 ensures that there is always a standby instance ready as backup in case one of the active message enhancement Engine instances fails.
  • Each Server runs the following processes: 1. Topology and Monitoring agent 2. CDR Collection.
  • the components communicate among themselves using internal transactions. Most of the Transactions are non-synchronic to allow high traffic.
  • the system includes a database (DB) and storage.
  • DB database
  • the following information is stored in the DB:
  • the database information is for backup only. During real-time operation the components update the DB but read the content from their cache.
  • the Users Table and the User Sending Models are distributed between the Message Enhancement Engine instances to reduce DB access.
  • the temporary text message sits both in the DB and in the Message Enhancement Engine until MMS delivery to reduce DB access.
  • Figure 6 is a flow chart of a positive scenario, in which an incoming SMS is received, the application converts the SMS to an MMS message, and the MMSC succeeds in delivering the MMS to the recipient.
  • Figs. 7 and 8 illustrate failures in the flow procedure.
  • Fig 7 shows a procedure in which no conversion is carried out of the incoming SMS into an MMS. The result is that the outgoing message to the recipient is the original incoming SMS Message.
  • Fig. 8 shows a procedure in which the message is successfully generated but is then rejected by the recipient so the original SMS is sent instead.
  • the SMSC Connector receives the incoming SMS message, acknowledges the SMSC for positive delivery and sends the incoming text message to one of the application Engines. Choosing the appropriate Engine instance is based on the MSISDN of the Sender.
  • the message always contains data about the following:
  • the application engine verifies that: • The Sender is a subscribed user
  • the application engine decodes the text body and searches for key words.
  • the key words are organized in a hash table for quick search, with references to the pictures. In case no picture is found, the message is sent back to the SMSC connector
  • the text message is stored in the database for backup. If Pre-Paid users are supported, the application Engine queries the Pre-Paid
  • the application composes the MMS Messages from the Text and the associated pictures. Then the message is sent to the MMSC connector.
  • the message insertion engine chooses one of the MMSC connectors, for example using Round Robin type selection, and sends the chosen connector the MMS Message body, Original Sender, destination and DB Message Index.
  • the MMSC Connector and sends the MMS message to the chosen MMSC that it has configured.
  • the MMS messaging is either by MM7 submission or the MMS Vendor API.
  • Each MMSC Connector can send to all of the operators' MMSCs.
  • the Original Sender is inserted as the Sender and as the user who is charged for the service.
  • the Destination can be a non-MMS Client, say a user with an older mobile telephone.
  • the server therefore requests an acknowledgement if the message arrives within a certain period.
  • the MMSC Connector requests a Delivery Report as part of the submission.
  • the MMSC Connector In the event of a failure in the submission, the MMSC Connector either retransmits the MMS Message to another MMSC or sends a failure indication to the Insertion Engine, as discussed in greater detail below. In the event of successful submission, the MMSC Connector updates the database with the Message ID returned from the MMSC. The connector would also take responsibility for timing matters associated with the delivery report in the event that the MMSC does not support such a timer.
  • the MMSC itself preferably verifies the submission request. There may be several causes of delivery failure, for example: the destination cannot be resolved, the application is not allowed to send, the message overrides the allowed size, and other reasons. In these cases the MMSC responds with an indication of submission response failure. The MMSC tries to deliver the message. It sends the end-user an
  • MMl_Noification Request In any case it sends an MM7 Delivery Report request to the application with the following exemplary return codes in case of failure: End-User rejected the request, Time-Out, etc., or reports successful message delivery.
  • the Message ID indicates the message. Since there is a Load Balancer in front of the image inserter Engine, each MMSC Connector can receive the MM7 Delivery Report Request. The MMSC Connector acknowledges its response to the MMSC using the MM7 Delivery Report.
  • MMSC connector From MMSC connector to Image Inserter Engine The MMSC connector sends the Delivery Report Response to the appropriate image inserter Engine or instance thereof. Choosing the Engine comprises finding the instance that is responsible for the given sender.
  • the MMSC Connector sends a Cancel request to the MMSC and sends a Failed Delivery Report to the image inserter engine with the appropriate return code.
  • the Engine itself verifies the return code of the Delivery Report. In the event of an error, the engine fetches the originating message from its cache memory, and sends it to the destination as an unenhanced SMS message, as discussed below.
  • the image inserter Engine generates a computer data record CDR with the information of the Sender, Destination, number of pictures and size, and the return code. The CDR may subsequently be used to determine billing.
  • the text message may in certain cases be returned to the SMSC connector for sending on to the recipient as an unenhanced message.
  • Such cases include the following:
  • the message could not be delivered to the destination as an MMS message. Typically because the recipient is not sufficiently powerful to receive MMS. In any of the above cases the Image Inserter Engine sends the text message back to the SMSC connector to be sent on to the recipient as an unenhanced message.
  • the Image Inserter Engine typically chooses between the available SMSC connectors using the Round Robin protocol.
  • the SMSC Connector uses the round robin protocol to choose an available connection to send the SMS message.
  • each SMSC connector is connected to all the SMSCs of the given Operators so that the traffic is distributed equally.
  • the Sender of the message is retained in the send field as the Original Sender, thus the message is delivered and received as if the sender has sent a simple text message.
  • the SMSC connector interfaces between the SMSC and the image insertion engine.
  • the connector is initialized and then connects continuously to the SMSC in order to receive incoming packets and send outgoing messages.
  • the connector accepts incoming SMS messages from originators so that they can be passed to the engine for enhancement.
  • the connector sends outgoing Text messages from the engine to the recipient in case no enhanced MMS message was produced, as discussed above.
  • SMSC connector Communication between SMSC connector and Message Enhancement Engine
  • the engine sends outgoing messages to the recipient in case of MMSC failure or for any other reason that the application is not available.
  • SMSC Connector may be several instances of the SMSC Connector in one message enhancement system, either for redundancy, load sharing, or both.
  • Different SMSC Connectors may run on different machines or on the same machine.
  • the SMSC connector may connect to one SMSC or to different SMSCs, depending on whether it is provided for redundancy or for load sharing (on the SMSC resource). Different instances of the SMSC Connector may connect to different SMSCs or to the same SMSCs, or a combination of both. In the event of an outgoing SMS message, the SMSC chooses one of the connections using the Round Robin protocol as explained above, and sends the message over the selected connection.
  • protocol implementations are preferably supported (in descending order):
  • One configurable character set is supported per installation.
  • the default character set is GSM-7.
  • messages are processed in UTF-8 character sets. Whenever a message is sent to or received from an SMSC, it is transcoded from/to UTF-8 to/from the local character set.
  • the SMSC Connector makes use of the keep-alive mechanisms provided within the SMSC communication protocols, polling the SMSC periodically in order to verify it is still connected and responding.
  • the keep-alive mechanism is configured separately for each SMSC. If the keep-alive mechanism fails, then the SMSC Connector resets the connection to that SMSC.
  • the keep-alive mechanism is also used to stop firewalls from disconnecting the connection when idle.
  • the SMSC Connector has a mechanism intended to recover from errors while sending messages to the SMSC.
  • Three types of "sending errors" are recognized:
  • the retransmission is carried out on another connection selected via Round Robin.
  • the MMSC connector component is now considered in greater detail.
  • the MMSC connector preferably interfaces with the MMSC in order to send outgoing MMS messages, that is the enhanced SMS messages, to the recipient.
  • the MMSC connector requests a Delivery Report in every MM7 Submit message and takes care that the delivery report expires within a predetermined period.
  • the main reason for the expiry is for Non-MMS supporting
  • Clients at the recipient, and as discussed, the main fallback comprises sending the original SMS message.
  • the message enhancement Engine sends MMS outgoing messages to the recipient
  • the MMSC connector sends Delivery Report responses (Success or Failure) to the message enhancement Engine
  • SMSC connector there may be several instances of the MMSC Connector in one message enhancement system, either for redundancy, load sharing, or both.
  • MMSC Connectors may run on different machines or on the same machine, again as with the SMSC connectors. Connections to MMSC
  • the MMSC connector may connect to one MMSC or to different MMSCs, either for redundancy or for load sharing over the MMSC resource. Different instances of the MMSC Connector may connect to different MMSCs or to the same
  • MMSCs or a combination of both, depending on whether the purpose is for redundancy or for load sharing.
  • the first MM7 message is an
  • MM7_Submit Request and Response which comprises a request from the MMSC Connector to the MMSC, and a response from the MMSC to the MMSC Connector.
  • the second MM7 message is an MM7_Delivery_Report Request and Response, which comprises a request from the MMSC to the MMSC Connector, and a response from the MMSC Connector to the MMSC.
  • the MM7_Submit Response from the MMSC may return with an error indicating that the end-user is not an MMSC Client.
  • the MMSC preferably returns an OK in the MM7_Submit Response.
  • the Message_ID is returned, so as to associate it later with the MMl_DeliveryReport Request.
  • a requirement is set to ensure delivery of the message within a certain period.
  • MMSCs there is support for an ExpiryDate.
  • a string of XML using the dateTime or duration datatypes may specify the point in time after which MMSC does not attempt to delivers the message. In this case the MMSC is responsible for timekeeping and there is no need for the MMSC Connector to take this time. In the event that the MMSC does not support the ExpiryDate feature, the
  • MMSC Connector takes responsibility for counting from when a positive MM7_Submit Response is received from the MMSC.
  • the MMSC preferably returns a negative MM7_Deliver Request to the MMSC Connector with the appropriate Status Code and with the appropriate Message lD.
  • the MMSC preferably sends a Cancel Request to the MMSC with the appropriate Message_ID.
  • the MM7 now tries to deliver the message to the end-user.
  • the destination may reject the message. That is, the user receives an Indication that an MMS message is waiting for him and he himself chooses to reject and not to retrieve it, an option with MMS.
  • the MMSC sends a negative MM7_Delver Request to the MMSC Connector with the appropriate Status Code and with the appropriate MessageJOD.
  • the MMSC sends a positive MM7_Deliver Request to the MMSC Connector with the appropriate Message_ID.
  • the MMSC connector has a mechanism intended to recover from errors while sending messages to the MMSC.
  • Two types of "sending errors” are recognized: • No acknowledgement received from the MMSC
  • the user preferably subscribes to the application and decides on a message enhancement model which may be one of the following alternatives:
  • the user should decide on the size of the MMS message or on a preferred number of pictures to associate with the MMS message.
  • the XML interface may be exposed to allow the operator to manage CRM commands. This is suitable for cases where the operator builds the user interface or the user requests the operator by phone to join the application.
  • the web client may be exposed for the end-user. The client is re-directed from the Portal Operator. A De-Registration command from the application is also supported.
  • the message enhancement server and product preferably provides a tool to work with the database.
  • the tool allows picture banks or other media sources to insert a new picture into the database or to add key words for searching for the pictures.
  • the tool also allows for maintenance of the current pictures.
  • the message enhancement engine preferably supports two types of Billing: 1) Off-line Billing - Two CDRs are generated for billing purposes. The first is when an outgoing MMS message is submitted, and the message enhancement Engine tries to send the MMS message. The second is when the outgoing MMS message is delivered, and the destination receives the MMS message.
  • the message enhancement engine queries the Operator Pre-Paid server about whether the sender who is the charging user has permission or the necessary balance to send an MMS message. In case no account is allowed, the service is not allowed to the sender and the message is sent back to the SMSC for delivery as an unenhanced text message.
  • the message enhancement system preferably collects the CDRs and maintains system and usage statistics.
  • the statistics are provided for different audiences, such as marketing managers, operator system engineer, and picture or media bank engineers.
  • CDRs A summary of the computer data records, CDRs, that may be generated by the system is as follows:
  • the following items are monitored through the message enhancement Product by the Topology & Monitoring manager.
  • An SNMP trap is sent to the Operator operations and maintenance (O&M). Failure or initialization of a message enhancement component - for every process that starts running or fails the Operator O&M is informed.
  • O&M Operator operations and maintenance
  • DB DB
  • the Pictures Administration & Provisioning Interface updates the DB Pictures and key words table.
  • the DB Process updates the message enhancement engine cache with the updated pictures table.
  • the Prime message enhancement Engine meaning the engine or the instance serving the present user, stores the SMS message for backup.
  • the Prime message enhancement Engine updates the SMS message for backup.
  • An example of an update is providing the MMS Message ID.
  • the cellular environment is one of those environments where high reliability is mandated.
  • the following discusses issues of the architecture that provide for high reliability.
  • the Message Enhancement system can run more than one instance or server process, of most system components. These instances have already been referred to above.
  • a multi-instance configuration increases the level of system survivability and the service level. For some components, multiple instances significantly improve system performance.
  • Multi Sever Message enhancement components are able to run on more than one server. Such a feature is crucial for high availability of the system configuration, and prevents a physical server from becoming a single point-of-failure.
  • Load sharing is a very basic mechanism of load distribution between system resources, utilized internally by the message enhancement system, where the system uses a sharing algorithm, usually the round robin algorithm, to allocate tasks to various components and servers.
  • Load balancing is a more comprehensive mechanism of system load distribution. This is achieved by a physical Load Balancer.
  • a robust hardware system design should support hardware hot-swapping or alternative path for all hardware and software components.
  • the redundancy principle means that each system element (hardware or software) is duplicated.
  • all system elements are preferably redundant, with no single points-of-failure in the system.
  • Such a principle is reflected in local and shared storage, all server hardware elements (i.e. CPU, Power Supply, Fans etc.), local network devices (which can be implemented by multi-pathing with a standby Ethernet card) or trunk (dual Ethernet card sharing) solutions.
  • All server hardware elements i.e. CPU, Power Supply, Fans etc.
  • local network devices which can be implemented by multi-pathing with a standby Ethernet card
  • trunk dual Ethernet card sharing
  • the message enhancement system offers gradual scalability, allowing operators to start with a relatively small system, and scale upwards to support millions of users, as all components and processes can run multiple instances. Resulting from built-in load balancing between components, scalability is near linear. When traffic grows, scaling the system upwards means adding servers and configuring the system to utilize them. There is no downtime involved in such upgrades, as the same mechanism that manages faulty components and ensures high availability is also responsible for the addition of new components into a live system.
  • SMSC may route the Message to the message enhancement application. These include: Specific Short Code, SMSC with enhanced routing capabilities, and Concentrator / Aggregator.
  • Specific short code is a simple solution -
  • the Short Code is preferably provided for the service by the Operator.
  • the specific short code makes the routing very simple it is generally regarded as an unfriendly solution.
  • SMSC SMSC to route the SMS Message to the message enhancement server whenevever an SMS message is submitted from the list of subscribed Users.
  • This Users List preferably resides in the SMSC or lightweight directory access protocol (LDAP). If the Sender exists in this List, the SMSC preferably delivers the message to the application with all the information - Sender, Destination and message Body.
  • LDAP lightweight directory access protocol
  • MO Mobile Originated
  • MT Mobile Terminated SMSCs
  • the MO SMSC sends its incoming traffic to an Aggregator which carries out the routing.
  • the message enhancement application is preferably connected to the Aggregator using Short Message Peer to Peer (SMPP) or even HTTP access. Instead of connecting to many SMSCs the application is connected to a small number of Aggregators.
  • SMPP Short Message Peer to Peer
  • the Aggregator routes the SMS Message to the message enhancement server every time an SMS message is submitted from anyone belonging to the Users list.
  • This Users List preferably resides in the Aggregator or LDAP. If the Sender exists in the list, the Aggregator should deliver the message to the application with all the information - Sender, Destination and message Body.
  • Apparatus 900 includes a text analyzer 910, a search unit 920, and a media inserter 930.
  • the text analyzer 910 analyzes at least one of a text of the passing messages, and a context of the passing messages.
  • the search unit 920 searches for a media item in accordance with the analysis.
  • Search unit 920 preferably searches for the media item(s) in database 925, which contains media items for insertion, such as images, video clips, music clips, etc...
  • the media inserter 930 inserts media from the search into the analyzed messages, thereby enhancing the passing messages for sending on to the recipient.
  • Fig. 10 is a simplified flow chart of a method for enhancement of text messages passing over a network, according to a preferred embodiment of the present invention.
  • step 1010 the text and/or context of the passing messages is analyzed.
  • step 1020 a database of media files is searched in accordance with a result of the analysis.
  • step 1030 media files retrieved by the search are inserted into the analyzed messages, thereby to enhance the passing messages for sending on to the recipient.
  • Fig. 11 is a simplified flow chart of a method for enhancing text messages passing over a network, according to a preferred embodiment of the present invention.
  • step 1110 respective text messages are analyzed.
  • step 1120 the analysis is used to identify a suitable media file from a database of media files.
  • step 1130 the media file is inserted into the text message to provide a media-enhanced text message for sending on to a recipient.
  • a user client for a message enhancement engine for enhancing text messages being sent over a network includes: a text message interception unit for interception of text messages prior to sending, a model for indicating which messages are to be enhanced, and a message director, associated with the text message interception unit and the model for sending respective text messages to the message enhancement engine if they correspond to the model.
  • the user client may be installed in a cellular telephone device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Human Computer Interaction (AREA)
  • Multimedia (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Dispositif améliorant les messages textuels transmis sur un réseau, comprenant : un analyseur de texte, une unité de recherche et un système d'insertion multimédia. L'analyseur analyse au moins un texte des messages transmis, et un contexte des messages transmis. L'unité de recherche recherche un élément multimédia en conformité avec l'analyse. Le système d'insertion multimédia insère un élément multimédia à partir de la recherche, dans les messages analysés, ce qui améliore les messages à transmettre au destinataire via le réseau.
PCT/IL2007/000005 2006-01-08 2007-01-03 Insertion d'image pour messagerie texte Ceased WO2007080570A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IL173011 2006-01-08
IL173011A IL173011A (en) 2006-01-08 2006-01-08 Image insertion for cellular text messaging

Publications (1)

Publication Number Publication Date
WO2007080570A1 true WO2007080570A1 (fr) 2007-07-19

Family

ID=37983365

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IL2007/000005 Ceased WO2007080570A1 (fr) 2006-01-08 2007-01-03 Insertion d'image pour messagerie texte

Country Status (2)

Country Link
IL (1) IL173011A (fr)
WO (1) WO2007080570A1 (fr)

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2457118A (en) * 2007-12-19 2009-08-05 Cvon Innovations Ltd Replacing character strings with auxiliary content when processing messages
WO2010021833A2 (fr) 2008-08-21 2010-02-25 Yahoo! Inc. Système et procédé de messagerie contexte améliorée
EP2154932A4 (fr) * 2007-12-17 2010-12-15 Huawei Tech Co Ltd Procédé et système de conversion d'informations de service
US8199892B2 (en) 2006-10-26 2012-06-12 Tekelec Methods, systems, and computer program products for providing a call attempt triggered messaging service in a communications network
US8204057B2 (en) 2006-10-26 2012-06-19 Tekelec Global, Inc. Methods, systems, and computer program products for providing an enriched messaging service in a communications network
CN102625266A (zh) * 2011-01-28 2012-08-01 北京云系天瑞科技有限公司 智能终端及其信息处理方法
EP2544437A1 (fr) * 2011-07-06 2013-01-09 Samsung Electronics Co., Ltd. Appareil et procédé pour la transmission de messages dans un terminal mobile
WO2013096482A2 (fr) 2011-12-19 2013-06-27 Machine Zone, Inc. Systèmes et procédés d'identification et de suggestion d'émoticônes
EP2480017A4 (fr) * 2009-10-21 2014-04-02 Zte Corp Procede et systeme pour l'attribution de rapports de distribution
EP2713323A1 (fr) * 2012-09-27 2014-04-02 BlackBerry Limited Appareil et procédé se rapportant à des émoticônes automatiquement suggérés
US20140115070A1 (en) * 2012-10-22 2014-04-24 Nokia Corporation Apparatus and associated methods
US8908864B2 (en) 2009-03-11 2014-12-09 Tekelec Netherlands Group, B.V. Systems, methods, and computer readable media for detecting and mitigating address spoofing in messaging service transactions
US8909266B2 (en) 2009-03-11 2014-12-09 Tekelec Netherlands Group, B.V. Methods, systems, and computer readable media for short message service (SMS) forwarding
WO2015119605A1 (fr) * 2014-02-05 2015-08-13 Facebook, Inc. Idéogrammes basés sur une analyse de sentiment
US9152979B2 (en) 2013-11-04 2015-10-06 Meemo, Llc Word recognition and ideograph or in-app advertising system
US9372608B2 (en) 2014-07-07 2016-06-21 Machine Zone, Inc. Systems and methods for identifying and suggesting emoticons
US9515968B2 (en) 2014-02-05 2016-12-06 Facebook, Inc. Controlling access to ideograms
US9525983B2 (en) 2009-07-27 2016-12-20 Tekelec, Inc. Methods, systems, and computer readable media for providing mobile network operator controlled content to mobile subscribers using social networking messages
RU2633597C2 (ru) * 2013-08-30 2017-10-16 Йота Девайсез Ипр Лтд Система отображения оповещений и способ замены контента оповещения с использованием изображений
US10013601B2 (en) 2014-02-05 2018-07-03 Facebook, Inc. Ideograms for captured expressions
US10294666B2 (en) 2006-01-20 2019-05-21 Material Innovations Llc Carpet waste composite
US10318109B2 (en) 2017-06-09 2019-06-11 Microsoft Technology Licensing, Llc Emoji suggester and adapted user interface
US10409488B2 (en) 2016-06-13 2019-09-10 Microsoft Technology Licensing, Llc Intelligent virtual keyboards
US10528219B2 (en) 2015-08-10 2020-01-07 Tung Inc. Conversion and display of a user input
US10877629B2 (en) 2016-10-13 2020-12-29 Tung Inc. Conversion and display of a user input

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1271971A2 (fr) * 2001-06-07 2003-01-02 Sonera Oyj Transmission de messages dans un système de télécommunication
WO2004019583A2 (fr) * 2002-08-14 2004-03-04 Telecom Italia S.P.A. Procede et systeme pour la transmission de messages sur un reseau de telecommunication et terminal expediteur correspondant
US20050156873A1 (en) * 2004-01-20 2005-07-21 Microsoft Corporation Custom emoticons

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1271971A2 (fr) * 2001-06-07 2003-01-02 Sonera Oyj Transmission de messages dans un système de télécommunication
WO2004019583A2 (fr) * 2002-08-14 2004-03-04 Telecom Italia S.P.A. Procede et systeme pour la transmission de messages sur un reseau de telecommunication et terminal expediteur correspondant
US20050156873A1 (en) * 2004-01-20 2005-07-21 Microsoft Corporation Custom emoticons

Cited By (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10294666B2 (en) 2006-01-20 2019-05-21 Material Innovations Llc Carpet waste composite
US8199892B2 (en) 2006-10-26 2012-06-12 Tekelec Methods, systems, and computer program products for providing a call attempt triggered messaging service in a communications network
US8204057B2 (en) 2006-10-26 2012-06-19 Tekelec Global, Inc. Methods, systems, and computer program products for providing an enriched messaging service in a communications network
EP2154932A4 (fr) * 2007-12-17 2010-12-15 Huawei Tech Co Ltd Procédé et système de conversion d'informations de service
GB2457118A (en) * 2007-12-19 2009-08-05 Cvon Innovations Ltd Replacing character strings with auxiliary content when processing messages
EP2329450A4 (fr) * 2008-08-21 2012-10-24 Yahoo Inc Système et procédé de messagerie contexte améliorée
WO2010021833A2 (fr) 2008-08-21 2010-02-25 Yahoo! Inc. Système et procédé de messagerie contexte améliorée
US8909266B2 (en) 2009-03-11 2014-12-09 Tekelec Netherlands Group, B.V. Methods, systems, and computer readable media for short message service (SMS) forwarding
US8908864B2 (en) 2009-03-11 2014-12-09 Tekelec Netherlands Group, B.V. Systems, methods, and computer readable media for detecting and mitigating address spoofing in messaging service transactions
US9525983B2 (en) 2009-07-27 2016-12-20 Tekelec, Inc. Methods, systems, and computer readable media for providing mobile network operator controlled content to mobile subscribers using social networking messages
US9118692B2 (en) 2009-10-21 2015-08-25 Zte Corporation Method and system for allocating delivery reports
EP2480017A4 (fr) * 2009-10-21 2014-04-02 Zte Corp Procede et systeme pour l'attribution de rapports de distribution
CN102625266A (zh) * 2011-01-28 2012-08-01 北京云系天瑞科技有限公司 智能终端及其信息处理方法
CN102866987A (zh) * 2011-07-06 2013-01-09 三星电子株式会社 移动终端中发送消息的装置及方法
EP2544437A1 (fr) * 2011-07-06 2013-01-09 Samsung Electronics Co., Ltd. Appareil et procédé pour la transmission de messages dans un terminal mobile
US9244907B2 (en) 2011-12-19 2016-01-26 Machine Zone, Inc. Systems and methods for identifying and suggesting emoticons
CN104335607A (zh) * 2011-12-19 2015-02-04 机械地带有限公司 用于识别和建议表情符号的系统和方法
EP2795441A4 (fr) * 2011-12-19 2015-10-07 Mach Zone Inc Systèmes et procédés d'identification et de suggestion d'émoticônes
WO2013096482A2 (fr) 2011-12-19 2013-06-27 Machine Zone, Inc. Systèmes et procédés d'identification et de suggestion d'émoticônes
US10254917B2 (en) 2011-12-19 2019-04-09 Mz Ip Holdings, Llc Systems and methods for identifying and suggesting emoticons
EP3352092A1 (fr) * 2011-12-19 2018-07-25 Machine Zone, Inc. Systèmes et procédés pour identifier et suggérer des émoticônes
EP2713323A1 (fr) * 2012-09-27 2014-04-02 BlackBerry Limited Appareil et procédé se rapportant à des émoticônes automatiquement suggérés
US20140115070A1 (en) * 2012-10-22 2014-04-24 Nokia Corporation Apparatus and associated methods
RU2633597C2 (ru) * 2013-08-30 2017-10-16 Йота Девайсез Ипр Лтд Система отображения оповещений и способ замены контента оповещения с использованием изображений
US9152979B2 (en) 2013-11-04 2015-10-06 Meemo, Llc Word recognition and ideograph or in-app advertising system
US9317870B2 (en) 2013-11-04 2016-04-19 Meemo, Llc Word recognition and ideograph or in-app advertising system
US9515968B2 (en) 2014-02-05 2016-12-06 Facebook, Inc. Controlling access to ideograms
US10013601B2 (en) 2014-02-05 2018-07-03 Facebook, Inc. Ideograms for captured expressions
WO2015119605A1 (fr) * 2014-02-05 2015-08-13 Facebook, Inc. Idéogrammes basés sur une analyse de sentiment
US10050926B2 (en) 2014-02-05 2018-08-14 Facebook, Inc. Ideograms based on sentiment analysis
US9372608B2 (en) 2014-07-07 2016-06-21 Machine Zone, Inc. Systems and methods for identifying and suggesting emoticons
US9690767B2 (en) 2014-07-07 2017-06-27 Machine Zone, Inc. Systems and methods for identifying and suggesting emoticons
US10311139B2 (en) 2014-07-07 2019-06-04 Mz Ip Holdings, Llc Systems and methods for identifying and suggesting emoticons
US10579717B2 (en) 2014-07-07 2020-03-03 Mz Ip Holdings, Llc Systems and methods for identifying and inserting emoticons
US10528219B2 (en) 2015-08-10 2020-01-07 Tung Inc. Conversion and display of a user input
US11199941B2 (en) 2015-08-10 2021-12-14 Tung Inc. Conversion and display of a user input
US10409488B2 (en) 2016-06-13 2019-09-10 Microsoft Technology Licensing, Llc Intelligent virtual keyboards
US10877629B2 (en) 2016-10-13 2020-12-29 Tung Inc. Conversion and display of a user input
US10318109B2 (en) 2017-06-09 2019-06-11 Microsoft Technology Licensing, Llc Emoji suggester and adapted user interface

Also Published As

Publication number Publication date
IL173011A0 (en) 2006-06-11
IL173011A (en) 2012-01-31

Similar Documents

Publication Publication Date Title
WO2007080570A1 (fr) Insertion d'image pour messagerie texte
US12028782B2 (en) Mobile messaging platform
US8954102B2 (en) System and method for determining and delivering appropriate multimedia content to data communication devices
US8645471B2 (en) Device message management system
US8797906B2 (en) Method and system for wireless message-based advertising
US20030158902A1 (en) Multimedia instant communication system and method
EP1523165B1 (fr) Notification d'événements par Internet
US20090264100A1 (en) Flexible Messaging System For Mobile Phone Users
US20060064307A1 (en) Method and system for session management wherein a client session identifier is used
US20110195729A1 (en) Internet Security Updates Via Mobile Phone Videos
US8799374B2 (en) Method and apparatus for search history based messaging
US20050276397A1 (en) System and method for providing availability information to a user
WO2007109125A2 (fr) Systeme et procede de controle d'activite et d'alerte
US7802304B2 (en) Method and system of providing an integrated reputation service
EP2015530B1 (fr) Système et service de messagerie
US12256044B2 (en) Call center mobile messaging
US8341396B1 (en) Dynamic selection and insertion of signature blocks during message transmission
WO2008027962A2 (fr) Système et procédé d'interaction perfectionnée
CN101278531B (zh) 异步消息的接收通知
CN101472246B (zh) 消息发送方法、消息鉴权方法及相应的系统
WO2007014568A1 (fr) Procede de transmission d'un message audio vers une adresse electronique quelconque a partir d'un terminal mobile
CN1980410A (zh) 用于实现短消息前转的通信系统和方法
US11172067B1 (en) Call center mobile messaging
KR20050088084A (ko) 클라이언트 세션 식별자를 이용한 세션 관리 방법 및시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07700698

Country of ref document: EP

Kind code of ref document: A1