Patent Application
20060291471
The present disclosure relates to smart-home networking and messaging
Multimedia messages or service messages of various types employed in communication services such as SMS (Short Message Service), MMS (Multimedia Message Service), e-mail (electronic mail), IM (Instant Messaging), and others are typically transmitted on the downlink and uplink between a communication server in the service center and a terminal embodied in the mobile radio network as a mobile telephone (cell phone) and in the circuit-switched and/or packet-switched fixed network as a communication terminal that can be used for this purpose in a “Smart Home” scenario.
As a successor to the very widely disseminated Short Message Service (SMS), mobile radio operators have developed and introduced the Multimedia Message Service (MMS). This is characterized in that images, sound, and text files are transmitted in unison, delivered directly to the recipient, and visualized by the terminal. A prerequisite is for the recipient to have an MMS-enabled terminal. If that is not the case the recipient will be notified accordingly via another route (SMS, telephone call, e-mail, etc.) and at the same time be offered a link to a “URL (Unified Resource Locator)” via which he or she will be able to retrieve the message at a later time using a “WEB browser”.
According to the prior art, a special gateway, in particular an “F-MMS gateway”, and a terminal designed for the service, in particular an MMS-enabled terminal, is required for delivering service messages, in particular “multimedia messages”, to a terminal (for example a DECT telephone) that is not directly connected to the mobile radio system. However, such terminals for fixed networks are only being introduced into, and available on the market gradually. For a swift launch of the various services, in particular the MMS service, in a fixed network it is therefore necessary also to enable users to receive such service messages using any terminals.
According to the prior art a terminal designed for the service, in particular an MMS-enabled terminal, is again necessary for producing service messages, in particular MMS messages. Alongside this, “WEB clients” are also employed on the personal computer for producing messages of said type. So that the above-described reception of service messages, in particular MMS messages, on any terminals can be employed to practical advantage, a concept is also required for producing and sending service messages, in particular MMS messages, on terminals that are not suitable for this purpose.
To enable the individual communication subscribers offered the communication services cited at the beginning to have uniform access to the services and so that data transmitted therein can be administered, it is known that providers of such communication services operate special internet portals such as, for example, “WEB.DE” (http://web.de), and offer them for use. The “WEB.DE” offering comprises a large, editorially maintained directory of German-language internet pages and services relating to navigation, information, communication, discussion, and entertainment. “WEB.DE” moreover also offers what is termed the “Unified Messaging” service which includes, inter alia, an e-mail service, an SMS service, an organizer service (calendar, appointment, and address management), and a telefax service, and further offers the possibility of conducting telephone calls.
Accordingly, a method, terminal, and server for transmitting service messages in a fixed and/or mobile network is disclosed, wherein various types of service messages such as, for example, multimedia messages (MMS messages), short messages (SMS messages), e-mail messages, facsimile messages, “voice mail” messages, “Instant Messaging” messages etc. that are available or provided in a service center or generated in the terminal are transmitted between the service center and terminal without the terminal's having to be embodied as a “client” with reference to transmitting and processing the service message.
Different multimedia messages may be transmitted from a service center directly or indirectly, via an intermediate server, to a server embodied as a “message server” which edits the message in accordance with the present disclosure, and forwards them therefrom in edited form for output on a fixed/mobile network-specific terminal to the terminal and, in the opposite direction, to transmit multimedia message content from the terminal to the server, which produces a multimedia message from said content then forwards said message again directly or indirectly to the service center.
The technical features include:
The components include the following functions and characteristics:
Server
Registering, authenticating, authorizing, and administering registered terminal subscribers (senders/recipients).
Accepting incoming service messages using, for example, an SMTP protocol.
Analyzing and structuring incoming messages (from whom, which media, semantic analysis of audio, images, and video—identifying characteristic features to simplify and speed up later locating, filtering, and converting); describing by means of structure information in, for example, MPEG-7 format.
Archiving received messages in personal directories.
Delivering notifications to the terminal about the arrival of new messages in the form of “PUSH” via TCP/IP; alternatively as an SIP notification or, as the case may be, message.
Editing the service message in a form harmonized with the terminal and the terminal subscriber's personal preferences; XSLT transformation based on stored style sheets and, depending on terminal features and personal preferences, a presentation of the message generated from the elements of the received message; producing a presentation in a format that is suitable for the terminal, for example HTML, for a “WEB browser” (alternatively also SMIL, WML, XML, etc.).
Provisioning of control functions such as, for instance, the deletion of messages, implemented using, for example, JavaScripts.
Administering statuses of logged-on terminal subscribers with reference to the retrieval of service messages. This will allow several users of one and the same terminal, for example a set-top box used in conjunction with a television set, to retrieve and manage their personal messages individually.
Accepting message elements from the terminal for sending as an MMS.
Composing an MMS and sending it via SMTP to the MMSC.
Terminal
Can be any terminal and in a specific embodiment is, for example, a set-top box used in conjunction with a television set.
Makes an application available for the purpose of outputting, for example visualizing presentations/media, for example a “WEB browser”.
Implements a communication component, called a notification recipient or “listener”, which accepts the notifications from the server.
It is alternatively also possible for an “SIP client” to be implemented in the terminal.
The “listener” visualizes the notifications, which can contain both text and images, audio, and video components. Visualizing in the form of text, audio data, images, window size, window position, and commands is controlled via an “Application Programming Interface (API)”. The notification recipient can alternatively also forward the received content to the “WEB browser” for visualizing.
The “listener” makes a “Unified Resource Locator (URL)” available to the “WEB browser” via which URL said browser can retrieve the actual message edited for the terminal.
The notification recipient allows an application, for example the browser, to be called up directly from the notification for retrieving the entire message.
The terminal can, as either a “plug-in” or an autonomous application, implement an application for sending messages. Said application conveys the produced/selected information (text, image, audio, video) to the server along with the structure information [for example a form of address, closing phrase, meaning/function of text elements (for example main text, comment, footnote, etc.), and references] which is determined automatically during editing and described in, for example, MPEG-7 format.
Notification:
A particular feature is that the type and scope of the notification (the way the notification message appears) can be individually set by the terminal subscriber. For this purpose he/she informs the server of the required mode during log-on:
Insertion of a window in which are displayed the semantically most important message elements of the received information or, as the case may be, parts of said elements. In the case of a set-top box used in conjunction with a television set the window is inserted over the current TV picture. Both the size of the window and its position on the television screen can vary and should not completely cover the TV screen. The content is extracted from the received service message by the server.
Insertion of information in a status line, with in particular the sender and addressee being displayed. What type of message the service message is constitutes a useful addition if the notification system is used for different service messages.
A result of the status-line solution is that there will be no notification, which is to say that the subscriber will not be disturbed or, as the case may be, interrupted.
The server uses the stored structure information to extract the relevant message elements for the mode that has been set and sends said message elements to the notification recipient in accordance with the mode that has been set.
The components hardware configuration is mostly based on known technologies; special features include component design and combination in a way allowing new functions or, as the case may be, functionalities to be realized in a novel manifestation:
The use of terminals [for example a set-top box, Personal Digital Assistant (PDA), etc.] not designed for a specific communication service for any asynchronous multimedia communication services (SMS, MMS, e-mail, Instant Messaging, chat, etc.).
The delivery of notifications (for example MMS, SMS) does not require a separate circuit-switched connection (for example POTS, ISDN).
Individualized message receipt/delivery can also be realized via a non-personal telephone number/address.
Implementing of a message archive that can administer any messages from any services and display them on any terminals, which do not require a specific “client”.
Retrieval of messages from any terminal, adapted to the terminal's features and to personal preferences.
Uniform access to any asynchronous communication services; no need to implement a separate “client” etc. for each service (SMS, MMS, e-mail, IM, chat).
Description of “transmitting an MMS message” scenario:
A terminal subscriber (subscriber B) purchases a new set-top box and wants to use the “MMS-on-TV” service. To be able to use the service the terminal subscriber first has to register with the server or, as the case may be, server operator. When this is done, an “account” is set up on the server for him/her under which he/she can then log on and retrieve messages. His/her telephone number to which MMS messages would normally be forwarded is also passed on to the “Multimedia Message Service Center (MMSC)” for configuring same.
Subscriber B is at home and watching TV and wants, while doing so, to be notified of the arrival of new messages. His/her set-top box is connected to the “internet” over an existing TCP/IP connection via his/her “Internet Service Provider (ISP)”. The connection can be provided via a modem (POTS, ISDN, for example), xDSL, CableModem, PowerLine, or WLAN, etc.
Subscriber B launches the “WEB browser” via the set-top box's menu and calls up the pre-configured start page for logging on to the server. He/she logs on there using his/her personal password, thereby automatically storing the IP address under which he/she will henceforth be accessible and wants to receive messages. He/she also informs the server of which terminal he/she wishes henceforth to use for receiving and retrieving messages (the set-top box). He/she finally indicates how he/she wishes to be notified of the arrival of new messages (not at all, via a short notice, fully via an Instant Message, etc.)
The server administers this configuration in a database (see table below).
The notification recipient program, which, for example, opens a TCP port and listens for events (for example TCP packets) directed at said port, is launched at the same time.
From a mobile telephone (cell phone) or an MMS-enabled fixed-network telephone, another subscriber (subscriber A) then sends an MMS message to subscriber B, who is known in a fixed network and registered there through his/her telephone number.
The MMS message arrives at the operator's “MMSC”, which is configured in such a way that all messages addressed to registered destination telephone numbers (among which is subscriber B's telephone number) will be forwarded to the server. Present-day systems forward an MMS message in the mobile radio network to the destination mobile telephone or to an F-MMSC gateway or an e-mail/WEB portal.
The forwarding mechanism is based on the SMTP protocol, behind which is a standardized mail protocol.
An SMTP server accepts the message on the server and forwards it for message analysis.
The message is here disassembled into its various components (for example images, text, audio, video, presentation scripts, and other data) and the structure analyzed. From the information contained the structural analysis attempts to identify the semantic meaning of individual components (for example comment, form of address, closing phrase, descriptive metadata such as, for example, camera parameters, etc.), but also the cross-referencing between elements (references, for example text refers to an image). This analysis also includes analyzing the media, in particular video data. For example video clips are disassembled into semantically relevant scenes, which are in turn represented by means of individual key images. When the message is retrieved, video clips can thus also be displayed in the form of short video compilations or of individual key images. The same applies to audio clips. The structure information is described and stored in, for example, MPEG-7 format.
The analysis module identifies the recipient using the information contained in the MMS message, either from the telephone number, where applicable with a number extension, and/or from the form of address (greeting), and/or by means of an explicit address entry in the MMS-specific structure information (Note: The MMS message can itself also contain structure information/metadata). The message and its elements are stored in the recipient's personal message archive, with each message being assigned its own subdirectory. For example:
Because subscriber B is logged on and has set the notification mode to “Full” (see table), a message compositor will produce a notification. For this purpose said compositor receives the most important text components (image, audio, where applicable video) from the analysis module as well as a “Unified Resource Identifier (URI)” under which the entire message can be retrieved.
The message compositor sends the notification, for example as a TCP packet, to the IP address of the set-top box with the port of the notification recipient.
The notification recipient accepts the packet and, since the notification mode is “Full”, opens a “top-level” window on the television screen in which the message components contained are displayed. The notification simultaneously contains details of actions to be initiated when specific keys are actuated.
By pressing the remote control key “OK”, subscriber B can hence go immediately to message retrieval.
The notification recipient for this purpose launches the “WEB browser” and gives it the “URL/URI” from the notification.
The “WEB browser” issues an “http request” with the “URL/URI” contained in the notification.
From the “URL/URI” the server recognizes who wants to retrieve which message. Because subscriber B has specified a set-top box as the terminal, the XSLT transformer produces an HTML presentation of the message from the style-sheet-based configuration profile designed for a television set and from the structure information of the message, with the media elements being “inserted” into the presentation and adjusted to the format.
Said matching of the media elements to the presentation format is performed by a media adapter which scales and rotates images, matches color spaces, and converts formats (the set-top box requires only one decoder for a single format) etc. Modality changes such as, for example, text-to-speech and video-to-still images, etc. can also be realized here.
An image composed of, for example, 4 quadrants is assembled on the set-top box.
An overview of the messages contained in the message archive is produced in the top left quadrant which overview displays which messages have been read or, as the case may be, are unread, and which message is being read. The subscriber can scroll through the list and select messages. This selection function is implemented in JavaScript form and triggers the compilation of a new HTML presentation on the server. The currently opened message is visualized, for example, having a colored background.
The television program in progress is shown scaled in the top right quadrant.
The text portion of the message containing the links to the media is shown in the bottom left quadrant.
The bottom right quadrant shows the currently selected image.
Subscriber B can change between the quadrants using the “right” and “left” cursor keys, with the selected quadrant again being, for example, color-highlighted.
The “up” and “down” cursor keys are used to scroll within a window.
Subscriber B is furthermore able to use supporting functions such as
These functions are controlled by means of JavaScripts, with new HTML pages being generated accordingly by the server.
Subscriber B can by selecting an application open an editor for producing a message. He/she is presented with a pre-specified structure via a mask. Images, video, and audio can be inserted alongside a text. The media can be “grabbed” from an archive on the set-top box, from a memory card inserted into the box, from the server, or from the program in progress.
The editor conveys the media elements together with the structure information pre-specified by the mask (in, for example, MPEG-7) to the server (using, for example, the http protocol), which generates a valid MMS message therefrom. This is then forwarded to the “MMSC” for sending.
The various objects, advantages and novel features of the present disclosure will be more readily apprehended from the following Detailed Description when read in conjunction with the enclosed drawings, in which:
a and 4b are a first flowchart for transmitting a service message according to the “one-server concept” shown in
a and 5b are a second flowchart for transmitting a service message according to the “two-server concept” shown in
Of the service centers SZ1 . . . SZ5, the first service center SZ1, the second service center SZ2, and the third service center SZ3 are each connected via a first packet-switched connection V1 to a server SV. A server/service center-specific transmission protocol SMTP, MM1 . . . MM7-over-TCP/IP is handled via said first connection V1 between the respective service center SZ1 . . . SZ3 and the server SV. The transmission protocol is preferably a “Simple Mail Transfer Protocol (SMTP)” or MMS-specific protocol specified by the “3GPP” standardizing body based on MMS interfaces MM1 . . . MM7 which in either case is handled in the course of a “Transmission Control Protocol/Internet Protocol (TCP/IP)”. Although the packet-switched connection is basically present again between the server SV and the respective service center SZ4, SZ5 when service messages are transmitted according to the “Voice Mail/Phone Call/Fax” service and the “Instant Messaging” service, additional measures or, as the case may be, components are required to be able to control the respectively cited service with the aid of the server SV.
Various protocols are used for the “Instant Messaging” service all of which have in common that it is assumed that the terminal EG is ready to receive and the IM messages can be delivered immediately. The IM message is generally not stored or may be the responsibility of the “client” installed on the terminal EG. A preferred implementation of the “Instant Messaging” service is based on the server SV being configured as a “Session Initiation Protocol (SIP)” server having an SIP-based User Authentication and on the SIMPLE protocol based on the “Session Initiation Protocol” being used. Arriving IM messages are routed to the server SV, which terminates the SIP session, via an SIP redirector SIP-U embodied as an “SIP redirect server”. If the terminal EG has an “IM client” based on the SIMPLE protocol, the terminal subscriber will also be able to use the “Instant Messaging” service directly.
In the case of the “Voice Mail/Phone Call/Fax” service, regular telephone calls conducted over, for instance, a circuit-switched network ISDN, PSTN (Integrated Services Digital Network, Public Switched Telephone Network) will, if a call is not answered, be switched to a converter KON, embodied as a “gateway”, which will accept the call and convert it into an “SIP call”. For that purpose the converter has a POTS (Plain Old Telephone Service) interface and an SIP interface. Said “SIP call” is terminated by the server SV in the form of an SIP-based answering machine which stores the voice mail as a message in the archive and notifies the terminal subscriber of the voice mail's arrival. Fax messages are also accepted and forwarded to the server SV in an analogous manner.
The server SV at which the service messages SN transmitted by the service centers SZ1 . . . SZ5 arrive has, for processing said service messages SN, an editing unit ABE that is connected to a service message memory SNS. Besides the service message memory SNS the editing unit ABE is also assigned a user database NDB that is also used by an “SIP proxy” SIP-P. The service message memory SNS and/or the user database NDB are/is either located outside the server SV or form/forms a constituent part thereof.
The “SIP proxy” SIP-P is preferably located in a “client-server architecture” between the “client” and server. In
The server SV is assigned via a second packet-switched connection V2 to a packet-switched network PVN embodied preferably as the internet. Via the second connection V2 the packet-switched network PVN is furthermore assigned an “Internet Service Provider” ISP and a router RT in the “Smart Home” scenario SHU as a coupling module for coupling the terminal EG to the packet-switched network PVN. The data or, as the case may be, information transmitted over the second packet-switched connection V2 between the router RT, the “Internet Service Provider” ISP, and the server SV is transmitted in accordance with a server-/terminal-specific transmission protocol HTTP, SIP-over-TCP/IP. The cited transmission protocol is preferably a “HyperText Transfer Protocol (HTTP)” or “Session Initiation Protocol (SIP)” handled in each case in the course of the “Transmission Control Protocol/Internet Protocol (TCP/IP)”.
In the “Smart Home” scenario SHU a cordless base station BS embodied as an “Access Point (AP)” is connected between the router RT and the respective terminal EG. The base station BS has a connection to an ISDN/PSTN-specific circuit-switched network and a connection to the “SIP proxy” SIP-P. Via a DECT/WLAN air interface, the base station BS is furthermore assigned a conventional cordless mobile unit MT for circuit-switched cordless telephony. Besides the mobile unit MT, the base station BS is also assigned a multiplicity of potential terminals EG. For example a set-top box STB connected to a television set FA via SCART or S-video interface, a personal computer PC, a “Personal Digital Assistant” PDA, and a smart telephone STF are embodied in the “Smart Home” scenario SHU as a terminal EG. While the set-top box STB, the “Personal Digital Assistant” PDA, and the smart telephone STF are each connected to the base station BS via a short-range radio interface embodied preferably according to the IEEE 802.11 standard (WLAN standard) or Bluetooth standard, the personal computer PC is connected to the base station BS via a USB port.
Of the service centers SZ1 . . . SZ5 the first service center SZ1, the second service center SZ2, and the third service center SZ3 are again each connected via a first packet-switched connection V1 to a first server SV1. A server/service center-specific transmission protocol SMTP, MM1 . . . MM7-over-TCP/IP is again handled via said first connection V1 between the respective service center SZ1 . . . SZ3 and the first server SV1. The transmission protocol is again preferably a “Simple Mail Transfer Protocol (SMTP)” or MMS-specific protocol specified by the “3GPP” standardizing body based on MMS interfaces MM1 . . . MM7 which in either case is handled in the course of a “Transmission Control Protocol/Internet Protocol (TCP/IP)”. Although the packet-switched connection is basically present again between the first server SV1 and the respective service center SZ4, SZ5 when service messages are transmitted according to the “Voice Mail/Phone Call/Fax” service and the “Instant Messaging” service, additional measures or, as the case may be, components are required to be able to control the respectively cited service with the aid of the first server SV1.
Various protocols are used for the “Instant Messaging” service all of which have in common that it is assumed that the terminal EG is ready to receive and the IM messages can be delivered immediately. The IM message is as a rule not stored or, as the case may be, said function is the responsibility of the “client” installed on the terminal EG. A preferred implementation of the “Instant Messaging” service is based on the first server SV1 being configured as a “Session Initiation Protocol (SIP)” server having an SIP-based User Authentication and on the SIMPLE protocol based on the “Session Initiation Protocol” being used. Arriving IM messages are routed to the first server SV1, which terminates the SIP session, via an SIP redirector SIP-U embodied as an “SIP redirect server”. If the terminal EG has an “IM client” based on the SIMPLE protocol, the terminal subscriber will also be able to use the “Instant Messaging” service directly.
In the case of the “Voice Mail/Phone Call/Fax” service, regular telephone calls conducted over, for instance, a circuit-switched network ISDN, PSTN (Integrated Services Digital Network, Public Switched Telephone Network) will, if a call is not answered, be switched to a converter KON, embodied as a “gateway”, which will accept the call and convert it into an “SIP call”. For that purpose the converter has a POTS (Plain Old Telephone Service) interface and an SIP interface. Said “SIP call” is terminated by the first server SV in the form of an SIP-based answering machine which stores the voice mail as a message in the archive and notifies the terminal subscriber of the voice mail's arrival. Fax messages are also accepted and forwarded to the first server SV in an analogous manner.
In contrast to the server SV in
The “SIP proxy” SIP-P is located in a “client-server architecture” between the “client” and server. In
The first server SV1 is again assigned via a second packet-switched connection V2 to a packet-switched network PVN embodied preferably as the internet. Via the second connection V2 the packet-switched network PVN is again furthermore assigned an “Internet Service Provider” ISP and a router RT in the “Smart Home” scenario SHU as a coupling module for coupling the terminal EG to the packet-switched network PVN. The data or, as the case may be, information transmitted over the second packet-switched connection V2 between the router RT, the “Internet Service Provider” ISP, and the server SV is transmitted in accordance with a server-/terminal-specific transmission protocol HTTP, SIP-over-TCP/IP. The cited transmission protocol is preferably a “HyperText Transfer Protocol (HTTP)” or “Session Initiation Protocol (SIP)” handled in each case in the course of the “Transmission Control Protocol/Internet Protocol (TCP/IP)”.
In contrast to
Finally, the set-top box STB is connected to a plurality of potential terminals EG, that is to say a “Personal Digital Assistant” PDA and a smart telephone STF. The connection between the set-top box STB and the cited terminals is again based preferably on a short-range radio interface embodied according to the IEEE 802.11 standard (WLAN standard) or Bluetooth standard. The set-top box STB is additionally connected to a television set FA via a SCART or S-Video interface, with the set-top box STB and television set FA forming a further terminal EG.
a and 4b show a first flowchart having a plurality of flow phases AP1 . . . AP6 for transmitting a service message SN according to the “one-server concept” shown in
In an initial status AZ the terminal EG is put into operation by a user. In a directly ensuing first flow phase AP1 a network address NAD containing, for example, a telephone number or e-mail address is transmitted from the terminal EG to the server SV for registering the terminal EG with the server SV. The server SV stores the network address NAD and forwards it to the service center SZ1 . . . SZ5, where the network address NAD is likewise stored.
This is shown in the respective change-of-state diagram in
On receiving the network address NAD, server SV responds by transmitting an access authorization ZGB to the terminal EG.
The terminal EG logs on to the server SV in a directly ensuing second flow phase AP2. For this purpose said terminal transmits a communication system address KSAD containing, for example, an IP address, device information GIF comprising, for example, type or features, and control information STIF, comprising, for example, a password or the type and scope of a notification message, to the server SV. The server SV stores the communication system address KSAD and the device and control information GIF, STIF and transmits a service message generating template SNEV to the terminal EG which template is presented, for example, in different formats such as “HyperText Markup Language (HTML)”, “EXtensible Markup Language (XML)”, “WAP (Wireless Application Protocol) Markup Language (WML)” or “Synchronized Multimedia Integration Language (SMIL)”.
This is also shown or, as the case may be, indicated, substantially excepting obvious individual storage operations, in the change-of-state diagrams in
In a third flow phase AP3 the server SV uses the received information GIF, STIF to generate a configuration profile which is stored by the server SV.
How the configuration profile is generated is shown, substantially excepting obvious individual storage operations, in the change-of-state diagram in
The configuration profile KFP is consequently the result of parameterizing the configuration template KFV by means of the device and control information GIF, STIF.
In a first follow-on status FZ1 a service message SN arrives in the service center SZ1 . . . SZ5 for the user of the terminal EG. In a fourth flow phase AP4 the service center SZ1 . . . SZ5 thereupon transmits the service message SN to the server SV for example in accordance with the server/service center-specific transmission protocol SMTP, MM1 . . . MM7. The received service message SN is analyzed and stored in the server SV. The server SV then transmits a notification message MN to the terminal EG informing the terminal EG that a service message SN intended for the terminal EG is in the server SV and can be collected. For this purpose the notification message MN contains a “Unified Resource Location (URL)”.
This is also shown, substantially excepting obvious individual storage operations, in the change-of-state diagram in
The service message stored in the server SV is disassembled into its individual components during analyzing and disassembling in the sixth SV status SVZ6 and the structure of the message and/or the semantic meaning of the individual components analyzed. The results of said analysis are then compiled into structure information SIF, preferably in MPEG-7 format, and stored. In parallel with the above-described analysis, a notification is generated in the eighth SV status SVZ8 concerning the service message's arrival in the server SV, where applicable (as an additional option) also taking account of individual message content, after which the notification message MN is transmitted with the “Unified Resource Location (URL)” to the relevant terminal EG in accordance with the network address and communication system address NAD, KSAD stored in the server.
In a directly ensuing fifth flow phase AP5 the terminal EG transmits a retrieval request AAF to the server SV to collect the service message SN stored in the server SV. On receiving said retrieval request AAF the server SV edits the stored service message SN for outputting and presenting the message content on the terminal EG and, for this purpose, produces a presentation message PN that is presented, for example, in different formats such as “HyperText Markup Language (HTML)”, “EXtensible Markup Language (XML)”, “WAP (Wireless Application Protocol) Markup Language (WML)” or “Synchronized Multimedia Integration Language (SMIL)” and which it transmits to the terminal EG in accordance with the server-/terminal-specific transmission protocol HTTP, SIP. After receiving the presentation message PN the terminal EG presents said presentation message PN acoustically, graphically, and/or optically.
This is also shown or, as the case may be, indicated, substantially excepting obvious individual storage operations, in the change-of-state diagram in
In a second follow-on status FZ2 the user of the terminal EG wishes to send someone (for example a distant mobile radio subscriber) a service message SN. In a sixth flow phase AP6 the user of the terminal EG first generates the content of said service message then inserts the generated content into the service message generating template SNEV received from the server SV during the log-on phase. If the service message generating template SNEV is not available to the user at this time, which may certainly be the case if, as a possible alternative to the case shown in
This is also shown or, as the case may be, indicated, substantially excepting obvious individual storage operations, in the change-of-state diagram in
a and 5b show a second flowchart having a plurality of flow phases AP1′. . . AP7′ for transmitting a service message SN according to the “two-server concept” shown in
In an initial status AZ′ the second server SV2 and the terminal EG are put into operation by a user. In a directly ensuing first flow phase AP1′ a network address NAD containing, for example, a telephone number or e-mail address is transmitted from the second server SV2 to the first server SV1 for registering the second server SV2 with the first server SV1. The first server SV1 stores the network address NAD and forwards it to the service center SZ1 . . . SZ5, where the network address NAD is likewise stored.
This is shown in the respective change-of-state diagram in
On receiving the network address NAD, the first server SV1 responds by transmitting an access authorization ZGB to the second server SV2.
The second server SV2 logs on to the first server SV1 in a directly ensuing second flow phase AP2′. For this purpose the second server transmits a first communication system address KSAD1 containing, for example, an IP address to the first server SV1. The first server SV stores the first communication system address KSAD1.
This is shown in the respective change-of-state diagram in
The terminal EG logs on to the second server SV2 in a then ensuring third flow phase AP3′. For this purpose said terminal transmits a second communication system address KSAD2 containing, for example, an IP address, device information GIF comprising, for example, type or features, and control information STIF, comprising, for example, a password or the type and scope of a notification message, to the second server SV2. The second server SV2 stores the second communication system address KSAD2 and the device and control information GIF, STIF and transmits a service message generating template SNEV to the terminal EG which template is presented, for example, in different formats such as HyperText Markup Language (HTML)”, “EXtensible Markup Language (XML)”, “WAP (Wireless Application Protocol) Markup Language (WML)” or “Synchronized Multimedia Integration Language (SMIL)”.
This is also shown, substantially excepting obvious individual storage operations, in the change-of-state diagrams in
In a fourth flow phase AP4′ the second server SV2 uses the received information GIF, STIF to generate a configuration profile which is stored by the second server SV2.
How the configuration profile is generated is shown, substantially excepting obvious individual storage operations, in the change-of-state diagram in
The configuration profile KFP is consequently the result of parameterizing the configuration template KFV by means of the device and control information GIF, STIF.
In a first follow-on status FZ1′ a service message SN arrives in the service center SZ1 . . . SZ5 for the user of the terminal EG. In a fifth flow phase AP5′ the service center SZ1 . . . SZ5 thereupon transmits the service message SN to the first server SV1 for example in accordance with the server/service center-specific transmission protocol SMTP, MM1 . . . MM7, which server forwards said message to the second server SV2. The received service message SN is analyzed and stored in the second server SV2. The second server SV then transmits a notification message MN to the terminal EG informing the terminal EG that a service message SN intended for the terminal EG is in the second server SV2 and can be collected. For this purpose the notification message MN contains a “Unified Resource Locator (URL)”.
This is also shown, substantially excepting obvious individual storage and forwarding operations, in the change-of-state diagram in the change-of-state diagram in
The service message stored in the second server SV2 is disassembled into its individual components during analyzing and disassembling in the eighth SV2 status SV2Z8 and the structure of the message and/or the semantic meaning of the individual components analyzed. The results of said analysis are then compiled into structure information SIF, preferably in MPEG-7 format, and stored. In parallel with the above-described analysis, a notification is generated in the tenth SV2 status SV2Z10 concerning the service message's arrival in the second server SV2, where applicable (as an additional option) also taking account of individual message content, after which the notification message MN is transmitted with the “Unified Resource Location (URL)” to the relevant terminal EG in accordance with the network address and second communication system address NAD, KSAD2 stored in the second server.
In a directly ensuing sixth flow phase AP6′ the terminal EG transmits a retrieval request AAF to the second server SV2 to collect the service message SN stored in the second server SV2. On receiving said retrieval request AAF the second server SV2 edits the stored service message SN for outputting and presenting the message content on the terminal EG and, for this purpose, produces a presentation message PN that is presented, for example, in different formats such as “HyperText Markup Language (HTML)”, “EXtensible Markup Language (XML)”, “WAP (Wireless Application Protocol) Markup Language (WML)” or “Synchronized Multimedia Integration Language (SMIL)” and which it transmits to the terminal EG in accordance with the server-/terminal-specific transmission protocol HTTP, SIP. After receiving the presentation message PN the terminal EG presents said presentation message PN acoustically, graphically, and/or optically.
This is also shown or, as the case may be, indicated, substantially excepting obvious individual storage operations, in the change-of-state diagram in
In a second follow-on status FZ2′ the user of the terminal EG wishes to send someone (for example a distant mobile radio subscriber) a service message SN. In a seventh flow phase AP7′ the user of the terminal EG first generates the content of said service message then inserts the generated content into the service message generating template SNEV received from the second server SV2 during the log-on phase. If the service message generating template SNEV is not available to the user at this time, which may certainly be the case if, as a possible alternative to the case shown in
This is also shown or, as the case may be, indicated, substantially excepting obvious individual storage operations, in the change-of-state diagram in
The editing unit ABE contains a service message analyzing module SNAM and a notification message generating module MNEM, with the latter having an I connection (INPUT connection) to the service message analyzing module SNAM. Both the service message analyzing module SNAM and the notification message generating module MNEM moreover also have an I connection to the SS interface SS-S. The service message analyzing module SNAM also has an O connection (OUTPUT connection) to the service message memory SNS, while the notification message generating module MNEM also has an I connection to the user database NDB and an O connection to the SE interface SE-S, SE-S′. The transmitting and processing operations belonging to the flow phase AP4, AP5′ in
The editing unit ABE furthermore has a configuration module KFM, a “style sheet” archive SSA, a “WEB server” module WSM, and a media adaption module MAM, with the configuration module KFM having an I connection to the service message memory SNS and “style sheet” archive SSA and an I/O connection (INPUT/OUTPUT connection) to the user database NDB and the “WEB server” module WSM, with the “WEB server” module WSM having, alongside the I/O connection to the configuration module KFM, in each case a further I/O connection to the user database NDB, the SE interface SE-S, and the media adaption module MAM, and an O connection to the SS interface SS-S, and with the media adaption module MAM having, alongside the I/O connection to the “WEB server” module WSM, an I connection to the user database NDB.
The transmitting and processing operations belonging to the flow phases AP1, AP1′, AP2, AP2′, AP3′ in
The transmitting and processing operations belonging to the flow phases AP3, AP5, AP4′, AP6′ in
Besides the “WEB server” module WSM and the user database NDB, the editing unit ABE contains a service message generating module SNEM, a template producing module VEM, and a template archive VA, with the “WEB server” module WSM having, alongside the I/O connection to the user database NDB and the SE interface SE-S, an O connection to the service message generating module SNEM and an I/O connection to the template producing module VEM, with the template producing module VEM having, alongside the I/O connection to the “WEB server” module WSM, an I connection to the user database NDB and the template archive VA, and with the service message generating module SNEM having, alongside the connection to the “WEB server” module WSM, an O connection to the SS interface SS-S.
The transmitting and processing operations belonging to the flow phases AP6, AP7′ in
The wireless interface DL-S sets up the wireless connection, preferably embodied as an infrared or radio link, to the remote control instrument FBE, which can be embodied as, for example, a computer keyboard or a television remote control unit.
The buffer memory PSP serves to buffer the output data transmitted via a SCART or S-video interface to the television set FA having a television screen FBS.
The processing unit VAE of the set-top box STB contains a “WEB browser” module WBM and a message receiver module MEM embodied as a “listener” or, as the case may be, notification recipient. Both the “WEB browser” module WBM and the message receiver module MEM have in each case I/O connections to the buffer memory PSP, the SE interface SE-S, and the wireless interface DL-S. The “WEB browser” module WBM furthermore has an I connection to the message receiver module MEM.
For displaying the output data on the television screen this is subdivided into four quadrants Q1 . . . Q4. The content of a message archive is displayed in a first quadrant Q1 (top left on the screen). The television program in progress is displayed in a second quadrant Q2 (top right on the screen), while the respective message text or, as the case may be, current media element, for example an image or video, is displayed in a third quadrant Q3 (bottom left on the screen) and a fourth quadrant Q4 (bottom right on the screen).
The remote control instrument FBI has an OK key, for example for selecting a message, and in each case two vertical cursor keys (“top/up” and “bottom/down” arrow keys) and horizontal cursor keys (“left” and “right” arrow keys). The vertical cursor keys make it possible to navigate in the message archive while the horizontal keys are used to change between the individual quadrants Q1 . . . Q4. The OK key and cursor keys of the remote control instrument FBI can alternatively be embodied as softkeys.
The wireless interface DL-S again sets up the wireless connection, preferably embodied as an infrared or radio link, to the remote control instrument FBE, which can be embodied as, for example, a computer keyboard or a television remote control unit.
The buffer memory PSP again serves to buffer the output data transmitted via a SCART or S-video interface to the television set FA having a television screen FBS.
The processing unit VAE of the set-top box STB again contains a “WEB browser” module WBM and a modified message receiver module MEM′ embodied as a “listener” or, as the case may be, notification recipient. Both the “WEB browser” module WBM and the message receiver module MEM′ again have in each case I/O connections to the buffer memory PSP, the SE interface SE-S, and the wireless interface DL-S. The “WEB browser” module WBM furthermore has an I connection to the message receiver module MEM′.
For displaying the output data on the television screen this is again subdivided into four quadrants Q1 . . . Q4. The content of a message archive is displayed in a first quadrant Q1 (top left on the screen). The television program in progress is displayed in a second quadrant Q2 (top right on the screen), while the respective message text or, as the case may be, current media element, for example an image or video, is displayed in a third quadrant Q3 (bottom left on the screen) and a fourth quadrant Q4 (bottom right on the screen).
The remote control instrument FBI again has an OK key, for example for selecting a message, and in each case two vertical cursor keys (“top/up” and “bottom/down” arrow keys) and horizontal cursor keys (“left” and “right” arrow keys). The vertical cursor keys make it possible to navigate in the message archive while the horizontal keys are used to change between the individual quadrants Q1 . . . Q4. The OK key and cursor keys of the remote control instrument FBI can alternatively be embodied as softkeys.
While the invention has been described with reference to one or more exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiments disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10 2004 013 103.1 | Mar 2004 | DE | national |
| 10 2004 013 102.3 | Mar 2004 | DE | national |
| 10 2004 013 101.5 | Mar 2004 | DE | national |
| 10 2004 013 100.7 | Mar 2004 | DE | national |
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/EP05/02888 | 3/17/2005 | WO | 3/17/2006 |
