EP1689104B9 - Radio pourvue d'un affichage pour des informations textuelles faisant référence à d'autres objets d'informations textuelles - Google Patents

Radio pourvue d'un affichage pour des informations textuelles faisant référence à d'autres objets d'informations textuelles Download PDF

Info

Publication number
EP1689104B9
EP1689104B9 EP06009464A EP06009464A EP1689104B9 EP 1689104 B9 EP1689104 B9 EP 1689104B9 EP 06009464 A EP06009464 A EP 06009464A EP 06009464 A EP06009464 A EP 06009464A EP 1689104 B9 EP1689104 B9 EP 1689104B9
Authority
EP
European Patent Office
Prior art keywords
text information
user
information object
currently displayed
objects
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.)
Active
Application number
EP06009464A
Other languages
German (de)
English (en)
Other versions
EP1689104A1 (fr
EP1689104B1 (fr
Inventor
Alexander Zink
Markus Prosch
Olaf Korte
Michael REICHENBÄCHER
Gerd Kilian
Thomas Jaumann
Thomas FRÜHWALD
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.)
Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Original Assignee
Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
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 Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV filed Critical Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Priority to PL06009464T priority Critical patent/PL1689104T3/pl
Publication of EP1689104A1 publication Critical patent/EP1689104A1/fr
Application granted granted Critical
Publication of EP1689104B1 publication Critical patent/EP1689104B1/fr
Publication of EP1689104B9 publication Critical patent/EP1689104B9/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/40—Arrangements for broadcast specially adapted for accumulation-type receivers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
    • H04H60/25—Arrangements for updating broadcast information or broadcast-related information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
    • H04H60/27—Arrangements for recording or accumulating broadcast information or broadcast-related information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
    • H04H60/35—Arrangements for identifying or recognising characteristics with a direct linkage to broadcast information or to broadcast space-time, e.g. for identifying broadcast stations or for identifying users
    • H04H60/46—Arrangements for identifying or recognising characteristics with a direct linkage to broadcast information or to broadcast space-time, e.g. for identifying broadcast stations or for identifying users for recognising users' preferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/16—Arrangements for broadcast or for distribution of identical information repeatedly
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/86—Arrangements characterised by the broadcast information itself
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/86—Arrangements characterised by the broadcast information itself
    • H04H20/93—Arrangements characterised by the broadcast information itself which locates resources of other pieces of information, e.g. URL [Uniform Resource Locator]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H2201/00—Aspects of broadcast communication
    • H04H2201/10—Aspects of broadcast communication characterised by the type of broadcast system
    • H04H2201/20—Aspects of broadcast communication characterised by the type of broadcast system digital audio broadcasting [DAB]

Definitions

  • the present invention relates to radios, and more particularly to those having an indicator for displaying textual information.
  • DAB Digital Audio Broadcasting
  • Text-based news services are already using this possibility of digital broadcasting to broadcast text messages to terminals.
  • broadcasters broadcast in addition to the actual broadcast program, so the audio information, text information that can be displayed on the display of the user's radio receiver, such as the name of the broadcast program or current news or the like.
  • the program manager decided on the type and order of the information.
  • Previous text-based messaging services allowed a user to have limited control over the selection of text messages displayed on their display, such as by switching programs.
  • a user of a broadcast receiver arrives at text information much faster when a text information object included in the broadcast signal that is being displayed on the broadcasting system's display includes a reference to another text information object in the broadcast signal and, by simply operating a user selection means, the user is allowed to cause the text information to be displayed to be changed from the text information of the current text information object to the text information of the text information object referred to by the current text information object.
  • the additional effort here is very limited, as in today's radio receivers mostly a "blank" button, which has an assigned function only in special situations of use of the radio receiver and is thus occupied, exists and can be used as a user selection device.
  • the text information objects become in the broadcast signal sequentially among other information in the broadcast signal, such as the audio information or other information, broadcast from a broadcasting station, each text information object having an object ID. If a text information object references another text information object, its object IDs will be different.
  • the introduction of the object IDs makes it possible to divide the content of the text information objects in the broadcast signal into groups and to transmit them cyclically repeatedly for receivers and thereby to update them.
  • a broadcast receiver can thus, without having to analyze the content of the text information objects, ie the text information, recognize whether a particular text information object just received, although different from the current one, affects the same subject as a previously received one and thus represents an update, or whether the currently received text information object content relates to a completely different subject.
  • An update can be easily made by comparing the object ID of a text information object immediately or not immediately following the currently displayed text information object in the broadcast signal with the object ID of the currently displayed one. Depending on whether the comparison results in the identity of the object IDs, the update is made or not.
  • the update for the broadcast receivers can be made less expensive by the text information objects next to the object ID still have a revision index, which provides information about which version of the text information associated with this object ID, this text information object concerns. Consequently, a radio receiver is not forced to perform an update blindly whenever a text information object whose object ID matches the object ID of the currently displayed text information object is broadcast again in the broadcast signal. Rather, the update is still made dependent on whether the revision index has changed. Image construction and other rendering mechanisms are therefore omitted if the new text information object with the same object ID can not differ in content from that already displayed, since it concerns the same version of the text information for this object ID.
  • the additional expenditure due to the burden on the transmission channel by the revision index in each text information object is comparatively small.
  • the update can also be made more user-friendly by distinguishing between the individual text information objects.
  • menu objects, list objects, and plain text objects exist. Each text information object is assigned to one of these types by an object descriptor or object type ID.
  • object descriptor or object type ID In the case of menu items or list items, the broadcast receiver performs the update immediately, ie, without user interaction, while otherwise updating is conditional on the user's consent to update so that it will not be abruptly interrupted due to a possibly minor update when reading a coherent longer text.
  • the display displays a section of the text information of this new text information object that is at least partially associated with a section overlays that the ad showed before updating from the old text information object.
  • this has the advantage that the user does not have to re-orientate himself in the list or the menu after the update has taken place, and that nevertheless he still receives the update when scrolling further.
  • the radio receiver or the radio has a cache memory for temporarily storing text information objects already received, it is possible for the text information of the current text information object to be displayed to change text information of the text information object with a different object ID
  • the current text information object refers to first look in the cache memory to see if a text information object with that object ID is not already in the cache. The user thus gets to the new text information of the new text information object faster and does not have to wait for the time duration until a text information object with the desired object ID pointed to by the current text information object is re-broadcast in the broadcast signal.
  • a cache hit identifier may be provided which first caches text information objects for all object IDs associated with menu items of the menu item and then, by modifying the textual information to be displayed, causes the Menu options for which text information objects are present in the cache for which users are visibly distinguishable from those for whom no text information objects are still present in the cache memory. This speeds up for a user zapping through the menus, ie the node of the object tree according to which the text information objects are arranged.
  • a broadcast receiver supports favorite functionality.
  • a favorites memory for this purpose one or more object IDs of text information objects are stored, which relate to objects that repeats the user, for example, every morning on the way to work, interest and which he can retrieve by operating a favorite query device.
  • object IDs which relate to objects that repeats the user, for example, every morning on the way to work, interest and which he can retrieve by operating a favorite query device.
  • a text information object includes a static flag. The add-listen functionality of the broadcast receiver is activated only if the static flag is set, otherwise not, thereby avoiding pointless addition of randomly assigned object IDs.
  • the text information broadcasting service after Fig. 1 which is also sometimes referred to as the "NewsService Journaline", will be in Fig. 1 to a pair of a broadcasting station 10 and a radio receiver 12.
  • the broadcasting station 10 is a stationary central broadcasting station that broadcasts broadcast signals 16 to a plurality of broadcast receivers such as the broadcasting receiver 12 via an antenna 14 such as a broadcasting tower.
  • the broadcast signal 16 includes, in addition to audio information that may relate to different broadcast programs, text information intended for the radio receivers or terminals 12 and their users in the context of the text message broadcast service.
  • the broadcast signal 16 corresponds to the DAB standard, for example.
  • the radio transmitter 10 comprises, among other components intended for audio transmission or for the transmission of the audio information and not shown here for reasons of clarity, a memory 18 and an embedding device 20.
  • the memory 18 contains a list 22 of text information objects , As will be described in more detail later, each includes Text information object at least one object identification number or object ID and the actual text content, ie the text information. In addition, text information objects also contain further information depending on their type, as will also be described in more detail below.
  • the text information objects in list 22 are maintained and updated by a service operator. He makes the selection of topics that affect the objects, the structure in which the objects are ordered, and the length of time in which they are repeatedly broadcast cyclically.
  • the embedding means 20 is connected to the memory 18 for reading out the text information objects from the memory 18 and incorporating them into the broadcast signal to broadcast the same via the antenna 14 as the broadcast signal 16.
  • the readout or transmission by the binding device 20 takes place cyclically for each text information object, so that a total of all text information objects are transmitted cyclically one after the other in the broadcast signal 16, with different cycle repetition times, as will be explained later on FIG. 5 will be described in more detail.
  • a radio receiver 12 comprises a receiving device 24, a control device 26, a loudspeaker 28, a display or a display 30, a memory 32, a first control panel 34 and a second control panel 36.
  • the receiver 24 is provided with a data input an antenna 38, to receive the broadcast signal 16 via the same 38.
  • the receiving device 24 is designed to be suitable for converting the audio signal 16 from the broadcast signal 16 and extract the text information and pass it to the controller 26 via its data output.
  • the controller 26, such as a processor or the like, first forwards the audio information to the speaker 28.
  • the forwarding of selected audio signals can be done either via an internal line to an integrated speaker 28, as in FIG. 1 is shown with solid lines, or via a speaker terminal or by outputting suitable audio signals to an external speaker 40, which is arranged externally to the radio receiver 12, as it is with dotted lines in FIG. 1 is shown.
  • the user of the radio receiver 12 can change from one broadcast program to the other via the control panel 36, which comprises, for example, only one toggle switch with two tilt positions or tilt positions.
  • the control panel 36 is for this purpose connected to the control device 26, which in turn is designed to change the current program and thus the audio signals to the loudspeakers 28 and 40, depending on the presence of a respective tilt position.
  • the control panel 34 consists of four buttons, one with an arrow down, one with an arrow up, one with an arrow to the left and another with an arrow to the right, or out two toggle switches, which are arranged perpendicular to each other, or a diamond-shaped toggle switch, but other possibilities for the control panel 34 exist. Instead of a control panel with buttons, for example, a voice input could be provided.
  • the control panel 34 is provided so that the user can supply via the control panel 34 of the control means 26 control signals with which it can influence in a manner as will be discussed in more detail below, which text information the control means 26 as to be displayed Forwards text information to the display 30.
  • the text information which the controller 26 forwards to the display 30 extracts the same from the text information objects contained in the broadcast signal 16 and extracted from the broadcast signal by the receiver 24.
  • the text information display functionality is completely detached from the reproduction of the audio information, so that upon actuation of the control panel 34, the sound reproduction or the currently played over the speaker 28 or 40 program is not interrupted.
  • the radio receiver 12 of FIG. 1 further comprises in the memory 32, which is also referred to below as a cache memory, and is for example a RAM, a list of text information objects 42 already received, an object path list 44 of object IDs, their content and meaning in the following will be discussed in more detail, and a list or an array of object IDs, referred to as favorites list 46, the meaning of which will also be specified in more detail below.
  • the user of the radio or radio receiver 12 can easily and immediately access information according to his or her current interest type.
  • the information is in plain text.
  • the text information is contained in the text information objects.
  • menu objects, text objects and list objects are listed objects.
  • FIG. 2 illustrates how the text information objects according to the present embodiment are arranged in a tree structure.
  • FIG. 2 shows an exemplary example of an object tree 50 of text information objects.
  • the text information objects are in FIG. 2 with square rectangles or rounded rectangles.
  • Each text information object is labeled with an "M", "T” and "L" for menu, text or list object.
  • every text information object has an object ID assigned to it.
  • it is assumed that the text information object at the root of the object tree 50 is assigned the fixed object ID 0, ie, 0x0000.
  • This main menu object, indicated at 52, is located in the first hierarchical level of the object tree 50 and is first of all transmitted to the display 30 by the control device 26 as soon as it has been broadcast via the broadcast signal 16 after switching on the radio 12 forwarded to the ad.
  • the main menu item 52 is thus initially shown when the user is using the radio or the NewsServcie Journaline functionality of the radio 12 first time without requesting a specific object ID.
  • the text information object at the root of the object tree 50 is a menu object.
  • each menu item comprises in its text information a plurality of menu options or menu items to which a reference to a text information object of a next higher hierarchical level in the form of an object ID is assigned.
  • the menu object 52 includes four menu options, and thus four references to other text information objects, as indicated by arrows 54.
  • the menu object 52 refers to two further menu objects 56 and 58 and two text objects 60 and 62, all of which form the text information objects of the second hierarchical level.
  • menu items 56 and 58 of the second hierarchical level in turn have references to other text information objects indicated by arrows 64 and 66, text objects, and thus also the text objects 60 and 62, do not include a reference to another text information object. They contain only text information.
  • the text objects "T” thus form the leaves of the object tree 50. The same applies to list objects "L”.
  • the exemplary object tree 50 of FIG. 2 four hierarchical levels, but any other number is conceivable. Furthermore, it is conceivable that two menu objects (possibly different hierarchical levels) refer to the same text information object as in FIG. 2 at Arrows 64 and 66 and the text information object 68 in the third hierarchical level.
  • the number of hierarchical levels of the tree structure may be set to a particular value, such as e.g. 20, be limited so that the receiving side at the radio receivers 12, the storage space for storing the data path 44 can be suitably dimensioned.
  • each text information object hereinafter also sometimes simply referred to as an object, must be referenced by at least one menu object, or at least one menu object must have a reference thereto. Only for the object 52 at the root of the object tree 50 does not need to exist a text information object that refers to the same. Of course, this would be possible.
  • the text information objects are therefore as in Fig. 2 structured. All of these text information objects in the object tree 50 are stored in the list 22 in the memory 18 of the broadcast transmitter 10. Should for any reason the broadcaster 10 be unable to provide the "News Service Jouranline" service, the object at the root of the object tree 50 may also be a text object such that the object tree 50 has only one hierarchical level, the textual information in that textual object, for example indicate the temporary failure of the service.
  • Fig. 3 shows an embodiment for the construction of text information objects according to an embodiment of the present invention.
  • Text information object 100 into an object header section 100a and an object content section 100b and is a maximum of 2044 bytes long.
  • the maximum length is not mandatory.
  • the storage of the objects 100 on both the receiving side and the transmitting side can be done in a simple manner in arrays in which the objects are arranged with an offset of 2044 bytes or a multiple thereof to each other and therefore easy to handle.
  • the object header section 100a is divided into a standard 3-byte header 100a1 and an extension header 100a2, assuming the latter has a length of n bytes, where n is an integer greater than or equal to zero.
  • the object contents section 100b is m bytes long, where m is an integer greater than zero.
  • the standard header 100a decomposes again into a 2-byte or 16-bit long object ID 102, which at the main object 52 (FIG. FIG. 2 0x0000 as mentioned, and an object descriptor 104 occupying the eight lower-order bits of the standard header 100.
  • the number of 16 bits of the object ID limits the number of allocatable IDs to 2 16 , that is about 10 6 .
  • the bits of the object descriptor 104 have different meanings.
  • the object type ID 108 indicates by its value the object type of the text information object 100, as shown in the following table.
  • Object type ID value Property Type 0x1 Menu object 0x2 Text object 0x3 Title-only object 0x4 List object
  • the list can of course always be supplemented with new object types that would have to be ignored by previous recipients.
  • the static flag has the meaning that, when set, it allows the user to add the object ID 102 to the favorites list 46.
  • the static flag is set or not set by the text information broadcast service operator, depending on whether the object ID is assigned only randomly and temporarily, ie displays only the same content information for a limited time, in which case adding to the favorites does not make sense would be, or if the assignment of the object ID is permanent, and so that a favorite addition would be useful, as will be discussed in more detail below.
  • the compression flag 114 indicates whether or not the object contents section 100b is compressed in a predetermined manner.
  • the revision index is set by the service operator to indicate in the cyclically repeatedly serially transmitted text information objects with the same object ID, Which version of the text information or object to which these textual information objects are related. For each update, the revision index 110 is incremented on the send side. For example, if the textual information of a particular object ID is related to the soccer match of a football match that is currently taking place, the text information "0: 0" indicating the score would appear in the first text information objects having this object ID together with the revision index 000b ( FIG.
  • the revision index allows updates to be made at the receiving end depending on whether the revision index has changed from an already received text information object to a newly received text information object or not, without analyzing the content to have to.
  • the object ID is linked on the send side with text information, which is then contained in the object content section 10b, as will be explained below.
  • text information which is then contained in the object content section 10b, as will be explained below.
  • object IDs that are randomly and only temporarily assigned, and where the static flag 112 is not set, and those where the object IDs are fixed with some kind of textual information (for example, the current weather report of a City), which is updated if necessary, in which case the revision index 110 is incremented.
  • the extension header 100a2 represents an extension option for the message service. If the data application signaling information of the broadcast system, that is, the control information in the broadcast signal besides the audio information and the text information, indicates that the extension header 100a2 contains additional header information, For example, a recipient who is unable to work with the extension header can easily ignore this section. Since the display is in the use of the extension header and the usual data application signaling information of the broadcast system, the length of the extension header 100a2 is the same for all objects of the "NewsService Journaline".
  • the actual text content or text information is contained in the text information objects in the object content section 100b.
  • FIGS. 6a to 6d each show an example of a screen display, as it results depending on the object type on the display 30. It should be noted that the examples assume a display capable of representing a plurality of lines on a screen, but that the service can of course also be implemented on existing car radio displays, which can display mostly only one line of 16 characters.
  • a text information or a text-only message of a text object is divided into a title 150 and the actual text 152, the so-called text body.
  • the title 150 and the subsequent actual text portion 152 are displayed on the screen of the automatic line break display 30.
  • the user may scroll vertically through the text, for example, by operating a vertically positioned toggle switch or the like on the control panel 34.
  • the title 150 is appended to the text portion 152 so that it may be included in the displayed portion of the display along with the remaining text 152 as appropriate 30 is pushed. Any font can be used for display.
  • the amount of textual information of a textual object is larger than a displayable amount, so that only a part of the textual information can be displayed on the screen of the display 30.
  • This displayable portion is moved by operating corresponding keys on the control panel 34 via title 150 and text 152.
  • This possibility is indicated to the user by means of corresponding arrows on the right-hand edge of the screen of the display 30, as shown in FIG. 6a at 154 and 156 can be seen.
  • the displayable section is at the beginning of the entire text message. Another scrolling upwards does not make sense. This is indicated by a corresponding, for example color highlighting the arrow 154, which points upward.
  • Appropriate Emphasis is made at arrow 156 when the displayable area or section is at the end of the message and therefore scrolling down is no longer possible.
  • Title-only messages only include a title 150 that is displayed on the screen of the display 30.
  • a text section 152 or body text is not provided.
  • the title text 150 is displayed on the screen of the display 30 again, for example, with automatic line break. If necessary, the user can scroll through the text. In the present case, however, the title can be displayed completely on the screen of the display 30, so that, by the absence of the arrows 154 and 156, the user is indicated that the title 150 has been completely displayed and there is no possibility of scrolling.
  • the representation of a pure title message can, for example, always be centered both in the line and in the vertical direction. As a font, in turn, each is equally usable.
  • a list message includes a title 160 and a list of text lines 162a-162d.
  • the title should differ from the ones in FIG. 6a text messages always displayed on the screen of the display 30, while the user scrolls through the lines 162a to 162d of information in the body section 162. It may be advantageous to use a font having a uniform character spacing in the row direction to represent list objects. as in the example of FIG. 6 to allow two-column tables by providing spaces. If the title 160 or any of the lines 162a to 162d exceeds a line length of the screen of the display 30, this list item is cut off at the end of the line, for example.
  • a menu contains a title 170 and a list of menu options 172a, 172b and 172c.
  • Each menu option is associated with a reference to another text information object, in the form of an object ID.
  • the user can scroll through the menu options.
  • One of the menu options on the screen of the display 30 is always highlighted, in this case the menu option 172b.
  • the user By pressing a suitable button on the control panel 34, such as the button to the right, the user indicates that he wants to access the text information object referenced by the menu option reference currently highlighted and its content through the text in the highlighted line of the menu as well as possible, as in the present case by the menu option text "Second Corporation 32nd round", as will be described below, the text information of this text information object is next displayed on the display, whereby the current object or textual information on the screen of the display 30 is replaced by the new one.
  • a suitable button on the control panel 34 such as the button to the right
  • a menu option consists of a reference to another text information object and a label that contains a line on the screen of the display 30 represents and denotes or circumscribes the content of the referenced text information object. If the title or label exceeds the length of one line of the screen of the display 30, the corresponding content could be cut off.
  • square brackets 174 highlight menu options that can not be displayed immediately because they are not yet in the cache memory 32 , as will be discussed in more detail below.
  • FIG. 6 Examples of textual information of textual information objects of different object type have been described below with reference to FIG Figure 4a-4e exemplarily the coding of this text information in the object content section 100b ( FIG. 3 ). Because of the strong limitation of the available bandwidths of common broadcasting systems for data services, as efficient as possible codings are used in the generation of the text information objects to be transmitted.
  • the object content section is usually divided into a title and a body section. Only for title-only objects does the body section in the object content section be missing.
  • escape sequences may be provided to introduce text formatting information, such as textual information.
  • text formatting information such as textual information.
  • Text highlighting, forced word wrapping, etc., as well as additional functionalities e.g. Information areas that can easily be ignored by recipients who are unable to handle the additional functionality or who do not support this additional functionality.
  • NML codes and escape sequences are one-byte codes ranging from 0x00 to 0xlF, called UTF-8 control codes.
  • the NML codes range from 0x00 to 0xOF and the escape sequences range from 0x10 to 0xlF.
  • FIGS. 4a to 4e Examples of text information objects ( FIGS. 4a to 4c ) or information blocks in the object content section ( FIGS. 4d and 4e ).
  • Each object block in the object content section is started with an NML code and by either the NML code "End", the occurrence of another NML code or the end of the object content section completed.
  • the NML codes are defined as examples in the following way:
  • 0x00 is the NML code for "end". It is used to terminate a section or block within the object content section without requiring another section or another block is started. It is applicable to every object type.
  • 0x01 be the NML code for "Title” and indicate by its appearance in the object content section 100b at the receiving end the beginning of the title section or title block. Exactly one title block must exist per object for all previously defined object types, ie the NML code 0x01 will appear at least once in section 100b. The title block must also be the first block in the object content section 100b. The NML code 0x01 is also applicable to all object types.
  • 0x02 be the NML code for a menu option block start. So this code represents the beginning of every menu option in a menu object. This code is therefore only intended for menu objects.
  • the receiver or decoder (not shown) provided in the controller 26 first awaits, in the subsequent bytes, the destination address or object ID of the referenced text information object referred to, and then the text of the menu option that should be displayed and describes the content of the referenced object. For each menu item of a menu item, the code 0x02 occurs once in the item contents section.
  • the decoder in the controller 26 expects the code 0x02 to be followed by two bytes indicating the object ID of the referenced object, ie the object to be displayed if the user selects this menu option, and then another n bytes, which indicate the menu option description to be displayed, in one line of the menu should be displayed to the user and to allow him virtually the selection of all menu options.
  • FIG. 4a displays a text information object for the menu object of FIG. 6a with the NML codes 0x00 to 0x02 for illustration.
  • the object 100 begins with an object header 100a, which in the present example is n bytes long. This is followed by the object content section 100b.
  • the first byte of the object content portion 100b is 0x01, that is, the NML code indicating the beginning of the title block whose textual content immediately follows the NML code 0x01 at the byte position 0 + 1 and byte 0 + 2 extends to byte k.
  • this section 200 in a manner as will be further specified below, the title of the menu of FIG. 6d saved, namely "sports Germany football".
  • the receive-side decoder knows when the title 200 is finished, since, as mentioned above, the text information of the title is encoded only with one-byte or multi-byte UTF-8 codewords other than NML codes or Escape Sequences are. Thus, once the receive-side decoder encounters the NML code 0x02 at byte k + 1 as shown, it knows that this is the beginning of a next block, namely the first menu option block.
  • the following two bytes k + 2 and k + 3 indicate by object ID OxAABB the next text information object to be displayed, in case that this menu item is selected. This is followed at 202 within bits k + 4 through p by the text encoding for the first menu option of the menu FIG.
  • the byte p + 1 again an NML code 0x02 to indicate the beginning of a menu option block.
  • the menu option blocks are again at the reference numerals 204a, 204b and 204c.
  • the NML code 0x00 occurs at byte t + 1. It indicates the end of the entire text information object 100 in this case.
  • This NML code 0x00 may be missing if, for example, the extension header contains the length of the entire text information object, so that the end of the entire object can be detected at the receiving end by appropriate syntactic analysis.
  • 0x03 be the NML code indicating the beginning of a body block in the object content section.
  • the NML code 0x03 is missing in the Object Content section because they do not have a body but only a title.
  • a coding example for a title information object is in FIG. 4b exemplary for the text object of FIG. 6a shown.
  • the body block is visible at 206. It consists of the NML code 0x03 followed by the UTF-8 encoding for the body text 152, namely "The cash position of the municipalities ".
  • the NML code 0x04 indicates the beginning of a bullet block in the object content section. This code only occurs with list objects in the Object Content section. In the list-point blocks, the NML code 0x04 is followed by the encoding for the text to be displayed for that list item in a row of the list on the screen of the display.
  • Figure 4c shows an example of a coding of a text information object exemplified by the example of the list object of FIG. 6c , The bullet point blocks are indicated at 208a, 208b and 208c.
  • FIGS. 4a to 4c Various embodiments of text information objects for illustrating the NML codes have been described with reference to FIGS Figures 4d and 4e describe the encoding of the textual information in the individual blocks 204a-204c, 206 and 208a-208c.
  • a block in the content section may have multiple escape sequences that should not be immediately displayed to the user.
  • escape sequences may include rendering pointers for the display, such as a display. an indication of a portion of text to be highlighted, a forced line break, a preferred line break, etc., or highlight portions of text that are not intended for direct rendering, such as textual editing; Binary code, that is, things that need to be ignored by recipients who are unable to process those data.
  • Escape or ESC codes can be for example: ESC code Surname description 0x10 preferred line break If applicable, such as when the radio is equipped with a multi-line screen or a dedicated rendering device, the receiver or its display should display the text following the code 0x10 starting on a new line. If not applicable to a particular type of rendering device for a display, insert a space. 0x11 Hyphenation point If a word does not fit completely in the end of a screen line, a receiver can insert a hyphen character at the receiving end when 0x11 occurs and a line break at this position: Otherwise, this code is ignored without being replaced by another character. The code 0x11 is especially recommended for words with more than 15 letters.
  • 0x12 Highlighting start If applicable, on the receive side, the text between the "highlight start” and “highlight stop” codes should be displayed in a highlighted form according to the recipient's rendering capabilities or display. 0x13 Highlighting stop Also, these codes should simply be ignored if the rendering device (not shown in the figures) of the display is not capable of highlighting at the receiving end.
  • 0x1A Data section start These escape codes specify a section within the text that is not processed by NewsService receivers 12.
  • 0x1B Data section sequel which is not able to evaluate the data section.
  • the data portion may include, for example, HTML / XML compliant labels or binary data.
  • FIG. 4d An example of the section of an object content section that encodes this text sequence is, for example, in FIG. 4d shown. If the data portion is more than 256 bytes, the "data portion continuation" escape code is inserted immediately after the previous data portion to make the data portion longer by max. 256 bytes to expand with each repetition. An example of coding for this is in Figure 4e shown. The embodiments of FIGS. 4d and 4e may thus be used to indicate the text passages in blocks 204a-204c, 206 and 208a-208c for suitably equipped receivers with corresponding indicators in a particular way. 0x1C Extension code beginning These escape codes allow the signaling of extended escape sequences.
  • Extension code end extended code value that is one byte long.
  • extension code contains only a single code without an explicit start / end version, you should always continue with the “extension code begin” code. If a receiver is unable to interpret "extension codes,” it may have the “extension code begin / end” escape code (1 byte) and the following “extension code value” (1 byte ) to ignore.
  • the text information objects are transmitted by the transmitter 10 in the broadcast signal 16, and in the controller 26 by means of a decoder or parser (not shown) therein, with reference to FIG FIG. 3 and 4 explained manner syntactically analyzed.
  • the control device 26 comprises an image processing device, not shown, which generates from the syntactically analyzed text information in the object content section of the text information object to be displayed suitable data, such as pixel data, which is then sent to the display 30 become. It should be noted, however, that the division regarding the image generation or processing and text extraction from the text information object to be displayed can also be proportionately shifted to the display 30 or that specially provided modules are connected between the control device 26 and the display 30.
  • FIG. 5 shows by way of example in a line 300 a section of a broadcast signal 16.
  • An arrow 302 indicates which part of the broadcast signal 16 is broadcast earlier or later, ie according to FIG FIG. 5 the left part before the right part.
  • individual text information objects are indicated by blocks. Each text information object is numbered. The number is the object ID associated with the text information object.
  • FIG. 5 Although that in FIG. 5 is shown as if the text information objects would be broadcast in temporal succession, it is of course possible that the transmission of individual text information objects is temporally quasi-same time. Nevertheless, an order is defined among the text information objects in any case, namely by the serial transmission of the transmitted text information objects received at the antenna 38 by the receiver 12, so that the representation in FIG FIG. 5 also applicable to this case.
  • the text information objects are thus sequentially arranged in the broadcast signal 300 in a certain order.
  • the transmitter 10 Depending on the priority, each text information object radiates repeatedly with a certain frequency. In the FIG.
  • the text information object with the object ID 1 with the repetition period ⁇ 1 and the object ID 25 with ⁇ 25th The frequency or repetition time depends on the expected frequency with which the respective text information object is desired by users of terminals, ie for weather news more frequently than for specific news from home or abroad.
  • the service provider constantly updates the text information objects in the memory 18. This means, on the one hand, the addition of text information objects to the list 22 with the assignment of new object IDs. However, this must also be accompanied by the change of at least one menu object, which must now have a further menu item or a further menu option with a reference to this new text information object. Therefore, there is also a change of the corresponding entry in the list 22 to the corresponding object ID of this changed menu object.
  • Fig. 5 it refers to an object transmitted in the broadcast signal, but on the other hand to all objects having a specific object ID. So are strictly speaking in Fig. 2 not text information object arranged in the tree, but object IDs. Each object ID represents a plurality of text message objects broadcast one after the other, with the corresponding object ID. For their part, these do not all have to be identical, but can be updated over time. Nonetheless, it is clear from the context of meaning in which way the term "text information object” has just been used.
  • FIG. 7 shows how the controller 26, in a display update process, examines a text information object just received to see whether or not updating of the screen content of the display 30 should be performed.
  • the controller 26 first checks in a step 400 whether the object ID of a currently received text information object is identical to the object ID of a currently displayed text information object. This would mean that the newly received text information object could include any changes to the older one currently being displayed. If the comparison in step 400 does not result in an identity, the display update process ends at 402 to restart upon receipt of the next received or subsequent text information object. If there is identity at step 400, control unit 26 checks in step 404 whether the revision index (110 in FIG FIG. 3 ) in the currently received and currently displayed text information object.
  • step 404 the display update process thus ends at 406 to begin again with the text information object immediately following it.
  • the controller 26 checks the object type ID (108 in FIG. 3 ), either the currently received or the currently displayed text information object, whether it is displaying a list, menu, or title-only object type, ie, 0x1, 0x3, or 0x4. If so, then in a step 410, the newly received text information object is displayed on the display 30, whereby the text information on the display 30 is updated.
  • a display controller (not shown) causes the current scroll position the user is maintained. This prevents the user, who has been laboriously scrolling or crawling through a part of a list or menu, to start over again when updating.
  • updating step 410 results in a menu option line of the menu prior to updating, such as row 172b in FIG FIG. 6d has the same screen position even after the update, provided that the new menu item has enough rows or enough menu options, or that it still has this menu option at all.
  • updating step 410 results in a list line of the list being displayed at the same screen position before the update as after the update, provided that the new list object has enough rows.
  • step 410 the updating of step 410 is performed such that the so-so-many menu option and / or list line appears at the same screen position before and after the update. This also means that the displayable area before and after the update at least partially overlaps, so that user confusion during an update is avoided.
  • the object ID of the menu entry or the text of the menu or list entry can also be used.
  • step 410 it may be provided simply to include the updated textual content of the newly received object as a new object new object ID easy to start from the beginning, since title-only news anyway have by definition no larger body text. A possible new "scrolling" does not hurt.
  • the user is thereby asked at the same time, whether he wants an update or would like to avoid such or rejects.
  • the consent can be expressed by the user via the control panel 34, such as by pressing a certain key, or by another confirmation device.
  • the rejection may be a no-response operation, such as not pressing a key.
  • the possibility that the user expresses his consent may also be limited in time, such as by a maximum consent period.
  • the controller checks, whether the user gives or disapproves. In the event that the user refuses an update, the display update process ends 414 until it is restarted. Otherwise, a display update is made 416. However, the display update in step 416 is performed without retaining the current display position as in step 410, but preferably as in displaying a text information object with a new object ID from the beginning, that is, in the scrolled position to the beginning.
  • FIG. 8 shows another process that is executed by the controller 26 constantly upon arrival of a newly received text information object.
  • the process of FIG. 8 is a cache update process.
  • the cache update process of FIG. 8 serves to ensure that the receiver 12 always has at least part of the text information objects already received, more precisely, for each object ID, the text information object with the latest available version, for fast display or access.
  • the controller 26 first checks in a step 450, based on the object ID of the newly received text information object, whether a text information object having this object ID is included in the list 22 in the memory 32.
  • step 452 it is checked in step 452 whether the revision index of the newly received text information object is different from the revision index of the text information object stored in memory 32 and the same object ID. If step 452 results in the identity of the two revision indexes, the cache update process ends at 454 to arrive of the subsequent text information object to start again from the beginning. If the check in step 452 reveals that the revision index of the newly received text information object is different from that in the cache memory 32, in step 456 the replacement of the corresponding entry in the list 42 is performed by the newly received text information object.
  • step 450 indicates that there is no entry with such an object ID in the list 42 of the cache memory 32, ie, a cache miss
  • the controller 26 checks in a step 458 whether the entry for the list 42 in the Memory 32 is full space, or if there is enough space to make an entry in the list 42. If the cache is not full, then in a step 460, the controller 26 enters the newly received text information object in the list 22 and the cache memory 32, respectively. However, this will only be the case in an initial phase after switching on the receiver 12 or the "NewsService Journaline" functionality of the receiver 12. After some time, the cache memory 32 will be full. In this case, in a step 462, the controller 26 checks for a certain cache displacement strategy, as follows FIG.
  • the check 462 takes into account the tree structure of the text information objects and defines, among the text information objects, a priority order depending on whether they are being interspersed by the currently displayed text information object or a text information object in the data path the root object and the currently displayed text information object or not, or more generally, because of its position in the tree or its relative position to the currently displayed text information object within the tree structure.
  • the time of the last reception or content update or the frequency of reception or content updates can be evaluated.
  • FIG. 9 again exemplified an object tree shown, with menu objects are again marked with M and text objects with T. All menu items are numbered by a number at the bottom left corner indicating the item ID.
  • the currently displayed text information object is the text object with the object ID 100. It is in the fourth hierarchical level.
  • the user had to change the text information objects or the menu objects with the object ID 3 in the second one Go through the hierarchy level and the object ID 12 in the third hierarchical level.
  • the sequence of object IDs of the text information objects from the main object with the object ID 0 to and including the currently displayed object with the object ID 100, with the menu objects lying therebetween in the object tree form the object object.
  • Path 44 the receiver 12 stores in the memory 32, and will be discussed in more detail later. It is actually created to allow the user to return to higher menu levels, and therefore also saved to each "Favorites".
  • the object path is ⁇ 0, 3, 12, 100 ⁇ . All objects whose object ID in the object path 44 ( FIG. 1 ) are included in FIG. 9 encircled by a dashed line. By a semicolon line are in FIG.
  • the object path objects framing all objects that will be referenced by at least one of the objects in the object path; these are in the example of FIG. 9 the objects with the object IDs 1, 2, 4, ..., 9, 13.
  • the currently displayed text information object was in the example of FIG. 9 a text object. If it were a menu object, the semicolon line would include objects located in the fifth hierarchical level of the object tree.
  • the cache update process ends at 464 if it is determined at step 462 that no lower priority cache object exists in the cache memory. If such exists, at step 466, the lowest priority object is replaced with the currently received object. Even if several objects of equal priority in the memory are the ones with the lowest priority, the oldest-received one should be replaced.
  • FIG. 10 shows a process performed by the controller 26 when a user on the control panel 34, while displaying a text information object on the display 30, operates keys intended for scrolling, such as the up-arrow and arrow-down arrows. down key.
  • the control device 26 shifts the text detail of the text information of the currently displayed object to be displayed downwards or upwards, if still possible.
  • the title is always displayed on the screen of the display.
  • FIG. 11 shows a process executed by the controller 26 when, with the text information object displayed, the user operates a select key that may be a dedicated key on the operator panel 34, or is, for example, the right arrow key.
  • a select key that may be a dedicated key on the operator panel 34, or is, for example, the right arrow key.
  • the controller 26 Upon actuation of this button or selection device checks the controller 26, in a step 550, whether or not the currently displayed text information object is a menu item. If this is not the case, the selection key is not assigned, ie it is not assigned a function, and the process of FIG. 11 ends at 552. If it is a menu object, then in a step 554 the controller 26 looks in the memory 32 to see if it contains an object with an object ID associated with the highlighted menu option (cf. 172b in FIG. 6d ).
  • step 556 the controller 26 changes the text information to be displayed to that of the object contained in the cache memory 32. Since the access to the cache memory 32 is fast, the screen change to the display 30 for the user thus imperceptibly, ie immediately. However, if the look-up at 554 results in a cache miss, then in step 558 the controller 26 waits for an object having the searched object ID to be broadcast in the broadcast signal 16. Of course, during step 558 all other processes are performed as usual, in particular the processes of FIG. 7 and FIG. 8 at the incoming objects.
  • the controller 26 changes in a step 560 the text information to be displayed on the screen of the display 30 to that of the currently received object with the searched object ID.
  • steps 560 and 556, respectively, in step 562 an object-path update is performed as described in FIG. 12 is shown in more detail.
  • FIG. 12 represents the object path update process of step 562 the controller 26 looked up in the memory 32 whether the new object ID, ie the object ID of the now newly displayed on the display 30 object that was associated with the selected menu option, already exists in the object path 44. If so, simply adding the new object ID to the end of the object path list of object IDs would result in a circular reference. Consequently, if the lookup results in a hit in step 580, the controller 26, in a step 582, causes the object path list 44 to be deleted up to this object ID, ie, to end with that object ID. Otherwise, ie in the case of a miss at lookup step 580, in a step 584 the new object ID is appended to the end of the object path list 44 unless the object path is length limited and has already reached its maximum length.
  • the new object ID ie the object ID of the now newly displayed on the display 30 object that was associated with the selected menu option
  • the management of the object path list 44 is intended to allow menu-back functionality as described with reference to FIG. 13 10, which illustrates a process that the controller 26 executes upon pressing a back key, such as the left-arrow key on the operation panel 34, when a text information object is being displayed on the display 30.
  • a step 600 the controller 26 retrieves, from the object path list 44, the object ID immediately preceding the object path of the object ID of the currently displayed object in the object path, and its object thus refers to it.
  • pressing the back button there would cause the object ID 12 to be detected in step 600.
  • the controller 26 beats in the memory 32 for an object with this object ID.
  • a step 604 the controller 26 changes the text information to be displayed to that of the object contained in the cache memory 32. Otherwise, ie in the event of a failure, the controller 26 waits in step 606 until an object having the searched object ID is broadcast in the broadcast signal 16, whereupon, as in a step 608, the text information to be displayed is that of the currently received object with searched object ID changes.
  • the controller 26 updates the object path list 44 by truncating it around the last object ID, namely the object ID of the text information object that was displayed before the change 604, 608.
  • step 612 determines whether the object ID path 44 has more than one object ID at all. The length would be one if the user were currently in the main menu (ie 0x0000). If so, the operation of the menu back key would have no consequences and the process ended at 614. Otherwise, the process would start at 600 as described above.
  • the receiver 12 includes favorite functionality to allow a user to store certain menu or message objects for fast and direct future access, for example, by giving them the highest priority in the cache memory.
  • the receiver 12 comprises a dedicated key, the user's long press of which may express his desire to add the object ID of the currently displayed text information object to the favorites list, while pressing the same key briefly in that the control means uses the favorite object ID in the favorite memory for the next text information object to be displayed.
  • FIG. 14 illustrates a favorite addition key activation control process. If the user indicates the desire to add, then in step 700 the controller 26 first checks whether the currently displayed object has a set static flag. If this is the case, this means that the object ID for a particular menu or a specific message object (eg, topic-related) is static or permanently provided.
  • a menu object regarding "weather forecast for Bamberg" could always be offered by a particular news service or news service under object ID 0x0020.
  • the controller 26 adds the object ID to the favorites list 46 in the memory 32 in a step 702.
  • the rejection 704 may be accompanied by, for example, a tone drowning the normal audio signal from the speaker 28 or 40 and indicating the rejection to the user, or accompanied by a brief fade.
  • a receiver 12 that supports the favorites functionality also for each favorite object ID, the full path of object IDs from the main object with the main object ID (eg 0x0000) down to the respective favorite object. Otherwise, the recipient will not be able to provide the menu-back functionality or return-to-higher-menu functionality to a user if a user has invoked this favorite object, although of course the object itself as well the immediate sub-objects, in the case that it is a menu object pointing to them, would still be reachable. If a menu from the object ID path should no longer exist (be shipped) upon restoration of a favorite seer, the controller could instead jump directly to the default main menu (e.g., 0x0000).
  • an object with a particular object ID is currently displayed to the user and at the same time provides an updated version of the same object, i. an object with identical object ID but different revision index is received
  • the user could always be displayed, independently of the object type, that such a current version of this object has been received, such as e.g. by showing a flashing "update" sign on the screen.
  • a recipient could evaluate to the list-line or object text or, in the case of a menu object, the object ID of the referenced object.
  • menu object contains references to object IDs that have not yet been received, these menu items or menu options are nevertheless offered to the user. This could of course be omitted. However, it is preferred to offer all menu options, but to clearly indicate to the user which menu options are immediately available, since the objects have already been received and are in the cache, and which are not immediately available, such as eg by framing the menu option label or title with square brackets, as in FIG. 6d shown.
  • the receiver could only keep in its memory the currently displayed object along with the object ID path associated with the currently displayed object. If the user then requests another object, he must wait until the requested object is received in the next time.
  • An MSC data group would then contain the following items: An MSC data group header of two or four bytes, a session header which would be optional and which would be 3 + n bytes long, an MSC data group field includes a "NewsService Journaline" object or text information object of, for example, m bytes, max. however, 2044 bytes, and finally an MSC data group CRC of two bytes, which is mandatory for "NewsService Journaline".
  • the main 11-bit "user application type" ID for the "News Service Journal” could be 0x44A from the range of proprietary user applications until officially standardized by DAB bodies. The value corresponds to 10001001010 b .
  • NewsService Journaline can also be broadcast via DRM ("Digital Radio Musice”) as well as via FM / RDS after adjustment of data service signaling.
  • the inventive scheme for controlling a radio can also be implemented in software.
  • the implementation may be on a digital storage medium, in particular a floppy disk or a CD with electronically readable control signals, which may interact with a programmable computer system such that the corresponding method is executed.
  • the invention thus also consists in a computer program product with program code stored on a machine-readable carrier for carrying out the method according to the invention when the computer program product runs on a computer.
  • the invention can thus be considered as a computer program with a program code to implement the method when the computer program runs on a computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Circuits Of Receivers In General (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (15)

  1. Récepteur de radiodiffusion avec
    un moyen de réception (24) destiné à recevoir un signal de radiodiffusion comportant des objets d'informations textuelles (100) dans lesquels sont contenues des informations textuelles (100b), les objets d'informations textuelles dans le signal de radiodiffusion (16) étant disposés de manière successive dans le temps, et chaque objet d'informations textuelles (100) présentant un ID d'objet (102);
    un écran d'affichage (30) destiné à afficher des informations de texte à afficher;
    un moyen de sélection d'utilisateur (34) pouvant être actionné par un utilisateur;
    un moyen de commande (26) qui est réalisé de manière à changer, en fonction d'un actionnement du moyen de sélection d'utilisateur (34) par l'utilisateur, les informations textuelles à afficher des informations textuelles actuellement affichées d'un objet d'informations textuelles actuellement affiché à des informations textuelles d'un objet d'informations textuelles auquel est fait référence par l'objet d'informations textuelles actuel, l'ID d'objet (102) de l'objet d'informations textuelles actuel différant de l'ID d'objet (102) de l'objet d'informations textuelles auquel fait référence ce dernier,
    chaque objet d'informations textuelles présentant un drapeau statique, le récepteur de radiodiffusion présentant, par ailleurs, la caractéristique suivante:
    un moyen d'appel de favoris pouvant être actionné par l'utilisateur;
    un moyen d'addition d'utilisateur pouvant être actionné par l'utilisateur;
    une mémoire de favoris destinée à mémoriser un ID d'objet;
    le moyen de commande étant réalisé de manière à changer, en fonction d'un actionnement du moyen d'appel de favoris par l'utilisateur, les informations textuelles à afficher des informations textuelles actuellement affichées à des informations textuelles d'un objet d'informations textuelles présentant le même ID d'objet que celui mémorisé dans la mémoire de favoris, et le moyen de commande étant réalisé de manière à examiner, en fonction de l'actionnement du moyen d'addition de favoris par l'utilisateur, le drapeau statique de l'objet d'informations textuelles actuellement affiché et, au cas où le drapeau statique n'est pas placé, à omettre l'actionnement et, au cas où le drapeau statique est placé, à entrer l'ID d'objet de l'objet d'informations textuelles actuellement affiché dans la mémoire de favoris.
  2. Récepteur de radiodiffusion selon la revendication 1, présentant, par ailleurs, la caractéristique suivante:
    un moyen de mise à jour destiné à comparer (400) l'ID d'objet d'un objet d'informations textuelles suivant l'objet d'informations textuelles avec l'ID d'objet de l'objet d'informations textuelles actuellement affiché et à mettre à jour (402, 410, 416) les informations textuelles à afficher en modifiant les informations textuelles actuellement affichées de l'objet d'informations textuelles actuellement affiché à des informations textuelles de l'objet d'informations textuelles suivant en fonction de la comparaison.
  3. Récepteur de radiodiffusion selon l'invention 2, dans lequel chaque objet d'informations textuelles 100 présente un indice de révision (110), et le moyen de mise à jour étant réalisé de manière à comparer l'indice de révision de l'objet d'informations textuelles suivant l'objet d'informations textuelles actuellement affiché avec l'indice de révision de l'objet d'informations textuelles actuellement affiché (404) et à n'effectuer la mise à jour qu'en cas d'ID d'objet identique et d'indice de révision différent (410, 416).
  4. Récepteur de radiodiffusion selon la revendication 2 ou 3, dans lequel chaque objet d'informations textuelles présente, par ailleurs, un identificateur de type d'objet (108), et le moyen de mise à jour est réalisé de manière à effectuer la mise à jour également en fonction de l'identificateur de type d'objet de l'objet d'informations textuelles actuellement affiché ou de l'objet d'informations textuelles suivant, notamment en fonction de ce dernier, soit directement (410), soit après une demande d'utilisateur (416).
  5. Récepteur de radiodiffusion selon l'une des revendications 2 à 4, dans lequel l'écran d'affichage (30) est réalisé de manière à afficher, lors de la mise à jour, au cas où la quantité d'informations textuelles de l'objet d'informations textuelles suivant est supérieure à une grandeur affichable, un segment de l'information textuelle de l'objet d'informations textuelles suivant qui vient au moins partiellement en recouvrement avec un segment qu'affichait l'écran d'affichage avant la mise à jour.
  6. Récepteur de radiodiffusion selon l'une des revendications 1-5, dans lequel l'objet d'informations textuelles actuellement affiché est un objet de menu, et les informations textuelles actuellement affichées comprennent une liste d'options de menu, l'objet de menu présentant, pour chaque option de menu, un ID d'objet associé, le moyen de commande étant réalisé de manière à changer, en fonction de l'actionnement du moyen de sélection d'utilisation (34) par l'utilisateur, les informations textuelles à afficher des informations textuelles actuellement affichées de l'objet d'informations textuelles actuellement affiché aux informations textuelles d'un objet d'informations textuelles qui présente le même ID d'objet que celui qui est associé à une option de menu mise en évidence comme sélectionnée.
  7. Récepteur de radiodiffusion selon la revendication 6, présentant, par ailleurs, un moyen de défilement (scroll) actionnable par l'utilisateur, le moyen de commande étant réalisé de manière à changer, en fonction de l'actionnement du moyen de défilement par l'utilisateur, l'option de menu actuellement mise en évidence comme sélectionnée à une autre des options de menu.
  8. Récepteur de radiodiffusion selon l'une des revendications 1-7, présentant, par ailleurs, une antémémoire (42) destinée à mémoriser temporairement des objets d'informations textuelles déjà reçus.
  9. Récepteur de radiodiffusion selon la revendication 8, présentant, par ailleurs, la caractéristique suivante:
    un moyen de mise à jour d'antémémoire destiné à comparer (450) l'ID d'objet d'un objet d'informations textuelles actuellement reçu dans le signal de radiodiffusion avec l'ID d'objet de chaque objet d'informations textuelles mémorisé dans l'antémémoire (42) et à remplacer un objet d'informations textuelles mémorisé dont l'ID d'objet coïncide avec celui de l'objet d'informations textuelles actuellement reçu dans le signal de radiodiffusion par l'objet d'informations textuelles actuellement reçu.
  10. Récepteur de radiodiffusion selon la revendication 8 ou 9, présentant, par ailleurs, la caractéristique suivante:
    un moyen de refoulement d'antémémoire (462, 464, 466) destiné à comparer (450) l'ID d'objet d'un objet d'informations textuelles actuellement reçu dans le signal de radiodiffusion avec l'ID d'objet de chaque objet d'informations textuelles mémorisé dans l'antémémoire et à mémoriser l'objet d'informations textuelles actuellement reçu dans le signal de radiodiffusion, lorsque l'ID d'objet de ce dernier ne coïncide avec l'ID d'objet d'aucun des objets d'informations textuelles mémorisés.
  11. Récepteur de radiodiffusion selon la revendication 10, dans lequel les objets d'informations textuelles sont disposés selon une structure d'arbre et le moyen de commande est réalisé de manière à effectuer la mémorisation par mémorisation en superposition d'un objet d'informations textuelles à mémoriser en superposition parmi ceux mémorisés dans l'antémémoire, tel qu'indiqué par une stratégie de refoulement, la stratégie de refoulement définissant une priorité entre l'objet d'informations textuelles actuellement reçu et ceux mémorisés dans l'antémémoire en fonction de leur position et de la position de l'objet d'informations textuelles actuellement affiché dans la structure en arbre, parmi les objets d'informations textuelles mémorisés dans l'antémémoire entrant en ligne de compte comme possible objet d'informations textuelles à mémoriser en superposition ceux à priorité inférieure à celui de l'objet d'informations textuelles actuellement reçu.
  12. Récepteur de radiodiffusion selon l'une des revendications 8 à 11, dans lequel le moyen de commande est réalisé de manière à tout d'abord consulter dans l'antémémoire, lors de la modification des informations textuelles à afficher, l'autre objet d'informations textuelles auquel fait référence l'objet d'informations textuelles actuellement affiché, à l'aide de l'ID d'objet et à attendre, uniquement dans le cas d'un échec, jusqu'à ce qu'il soit reçu dans le signal de radiodiffusion.
  13. Récepteur de radiodiffusion selon l'une des revendications 8 à 12, présentant, par ailleurs, la caractéristique suivante:
    un identificateur de réponse pertinente d'antémémoire, avec
    un moyen destiné à consulter, pour chaque ID d'objet à laquelle fait référence l'objet d'informations textuelles actuellement affiché, s'il est présent dans l'antémémoire un objet d'informations textuelles avec l'ID d'objet; et
    un moyen pour mettre en évidence parmi les informations textuelles actuellement affichées les parties auxquelles sont associées à des ID pour lesquels est présent dans l'antémémoire un objet d'informations textuelles, par rapport aux parties dans les informations textuelles actuellement affichées auxquelles sont associées des ID pour lesquels il n'est pas présent d'objet d'informations textuelles dans l'antémémoire.
  14. Procédé pour commander un récepteur de radiodiffusion avec un moyen de réception (24) destiné à recevoir un signal de radiodiffusion comprenant des objets d'informations textuelles (100) dans lesquels sont contenues des informations textuelles (100b), un écran d'affichage (30) destiné à afficher des informations textuelles à afficher, et un moyen de sélection d'utilisateur (34) pouvant être actionné par un utilisateur, les objets d'informations textuelles étant disposés successivement dans le temps dans le signal de radiodiffusion (16), et chaque objet d'informations textuelles (100) présentant un ID d'objet (102), le récepteur de radiodiffusion présentant par ailleurs
    un moyen d'appel de favoris pouvant être actionné par l'utilisateur, un moyen d'addition d'utilisateurs pouvant être actionné par l'utilisateur, et une mémoire de favoris destinée à mémoriser un ID d'objet, le procédé présentant les étapes suivantes consistant à:
    changer, en fonction d'un actionnement du moyen de sélection d'utilisateur (34) par l'utilisateur, les informations textuelles à afficher des informations textuelles actuellement affichées d'un objet d'informations textuelles actuellement affiché aux informations textuelles d'un objet d'informations textuelles auquel est fait référence par l'objet d'informations textuelles actuel, l'ID d'objet (102) de l'objet d'informations textuelles actuel différant de l'ID d'objet (102) de l'objet d'informations textuelles auquel il fait référence;
    changer, en fonction d'un actionnement du moyen d'appel de favoris par l'utilisateur, les informations textuelles à afficher des informations textuelles actuellement affichées aux informations textuelles d'un objet d'informations textuelles présentant le même ID d'objet que celui mémorisé dans la mémoire de favoris;
    examiner, en fonction de l'actionnement du moyen d'addition de favoris par l'utilisateur, le drapeau statique de l'objet d'informations textuelles actuellement affiché;
    au cas où le drapeau statique n'est pas placé, omettre l'actionnement; et
    au cas où le drapeau statique est placé, entrer l'ID d'objet de l'objet d'informations textuelles actuellement affiché dans la mémoire de favoris,
  15. Programme d'ordinateur avec un code de programme pour mettre en oeuvre le programme selon la revendication 14 lorsque le programme d'ordinateur est exécuté sur un ordinateur.
EP06009464A 2003-08-26 2004-08-25 Radio pourvue d'un affichage pour des informations textuelles faisant référence à d'autres objets d'informations textuelles Active EP1689104B9 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PL06009464T PL1689104T3 (pl) 2003-08-26 2004-08-25 Radioodbiornik z wyświetlaczem informacji tekstowych odnoszących się do innych obiektów informacji tekstowej

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE10339537A DE10339537A1 (de) 2003-08-26 2003-08-26 Radio
EP04764470A EP1658689B1 (fr) 2003-08-26 2004-08-25 Radio pourvue d'un affichage pour des informations textuelles faisant reference a d'autres objets d'informations textuelles

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
EP04764470A Division EP1658689B1 (fr) 2003-08-26 2004-08-25 Radio pourvue d'un affichage pour des informations textuelles faisant reference a d'autres objets d'informations textuelles

Publications (3)

Publication Number Publication Date
EP1689104A1 EP1689104A1 (fr) 2006-08-09
EP1689104B1 EP1689104B1 (fr) 2007-10-10
EP1689104B9 true EP1689104B9 (fr) 2008-08-20

Family

ID=34202119

Family Applications (3)

Application Number Title Priority Date Filing Date
EP07015293A Active EP1845643B1 (fr) 2003-08-26 2004-08-25 Emetteur de radiodiffusion des objets d'information textuelle
EP04764470A Active EP1658689B1 (fr) 2003-08-26 2004-08-25 Radio pourvue d'un affichage pour des informations textuelles faisant reference a d'autres objets d'informations textuelles
EP06009464A Active EP1689104B9 (fr) 2003-08-26 2004-08-25 Radio pourvue d'un affichage pour des informations textuelles faisant référence à d'autres objets d'informations textuelles

Family Applications Before (2)

Application Number Title Priority Date Filing Date
EP07015293A Active EP1845643B1 (fr) 2003-08-26 2004-08-25 Emetteur de radiodiffusion des objets d'information textuelle
EP04764470A Active EP1658689B1 (fr) 2003-08-26 2004-08-25 Radio pourvue d'un affichage pour des informations textuelles faisant reference a d'autres objets d'informations textuelles

Country Status (9)

Country Link
US (1) US7590381B2 (fr)
EP (3) EP1845643B1 (fr)
AT (2) ATE512514T1 (fr)
CA (2) CA2672277C (fr)
DE (2) DE10339537A1 (fr)
ES (3) ES2294754T3 (fr)
HK (1) HK1094488A1 (fr)
PL (3) PL1845643T3 (fr)
WO (1) WO2005022790A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7415243B2 (en) 2003-03-27 2008-08-19 Honda Giken Kogyo Kabushiki Kaisha System, method and computer program product for receiving data from a satellite radio network
US7643788B2 (en) 2004-09-22 2010-01-05 Honda Motor Co., Ltd. Method and system for broadcasting data messages to a vehicle
US20060158357A1 (en) * 2005-01-19 2006-07-20 Visteon Global Technologies, Inc. Text compression method for multi-level display
GB2423877B (en) 2006-03-06 2007-05-30 Imagination Tech Ltd A method and system for selectively storing information received from a broadcast signal
US8099308B2 (en) 2007-10-02 2012-01-17 Honda Motor Co., Ltd. Method and system for vehicle service appointments based on diagnostic trouble codes
JP5440004B2 (ja) * 2008-10-20 2014-03-12 セイコーエプソン株式会社 情報配信システム、情報配信システムのサービス実現方法およびそのプログラム
JP5293086B2 (ja) * 2008-10-28 2013-09-18 セイコーエプソン株式会社 情報配信システム、情報配信システムのサービス実現方法およびそのプログラム
KR101574603B1 (ko) 2008-10-31 2015-12-04 삼성전자주식회사 컨디셔널 프로세싱 방법 및 장치
EP2242249B1 (fr) * 2009-04-14 2017-07-19 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Transmission d'informations à base de texte

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2546501B2 (ja) * 1993-07-12 1996-10-23 日本電気株式会社 無線電話装置，それを備えた無線電話システム，及び無線電話応答方法
EP0762680A3 (fr) 1995-08-23 2001-04-25 Fraunhofer-Gesellschaft Zur Förderung Der Angewandten Forschung E.V. Méthode pour la transmission et l'installation et/ou l'actualisation de logiciel et/ou de données
DE19619491C2 (de) 1995-08-23 1999-03-25 Fraunhofer Ges Forschung Verfahren zur Übertragung und Installation und/oder Aktualisierung von Software und/oder Daten
FI99065C (fi) * 1995-10-05 1997-09-25 Nokia Oy Ab Ohjelmatiedoston käsittely digitaalisessa yleisradiojärjestelmässä
FI98676C (fi) * 1995-10-05 1997-07-25 Nokia Oy Ab Tietostoryhmän siirto digitaalisessa yleisradiojärjestelmässä
JPH10327111A (ja) * 1997-05-26 1998-12-08 Alpine Electron Inc Ｄａｂ受信機の番組受信方法
JP4196473B2 (ja) 1998-06-26 2008-12-17 パナソニック株式会社 デジタルデータ受信装置及びデジタルデータ受信方法並びにコンピュータ読み取り可能な記録媒体
EP1146673A1 (fr) 2000-04-10 2001-10-17 Sony International (Europe) GmbH Procédé de transmission d' un service d' information dans un système de transmission de radiodiffusion
US7180917B1 (en) * 2000-10-25 2007-02-20 Xm Satellite Radio Inc. Method and apparatus for employing stored content at receivers to improve efficiency of broadcast system bandwidth use
EP1384378A1 (fr) * 2001-04-03 2004-01-28 Gemstar Development Limited Guide electronique de programme permettant d'indiquer la rediffusion future des anciens programmes
DE10150596B4 (de) * 2001-10-12 2009-04-02 Audi Ag Vorrichtung zum Empfangen und Verfahren zur Aktualisierung von TMC-Meldungen
US20030110272A1 (en) * 2001-12-11 2003-06-12 Du Castel Bertrand System and method for filtering content
JP3965126B2 (ja) * 2002-03-20 2007-08-29 松下電器産業株式会社 コンテンツを再生する再生装置
US7228100B2 (en) * 2003-03-25 2007-06-05 Visteon Global Technologies, Inc. Program data display in duplicative digital audio broadcasting system
US7415243B2 (en) * 2003-03-27 2008-08-19 Honda Giken Kogyo Kabushiki Kaisha System, method and computer program product for receiving data from a satellite radio network

Also Published As

Publication number Publication date
EP1658689A1 (fr) 2006-05-24
EP1658689B1 (fr) 2011-06-08
EP1689104A1 (fr) 2006-08-09
ES2294754T3 (es) 2008-04-01
CA2672277C (fr) 2014-07-08
CA2537181C (fr) 2013-11-12
WO2005022790A1 (fr) 2005-03-10
ES2366553T3 (es) 2011-10-21
EP1845643A2 (fr) 2007-10-17
EP1845643B1 (fr) 2012-06-27
CA2537181A1 (fr) 2005-03-10
ES2389976T3 (es) 2012-11-05
HK1094488A1 (en) 2007-03-30
DE10339537A1 (de) 2005-03-24
PL1658689T3 (pl) 2011-11-30
CA2672277A1 (fr) 2005-03-10
DE502004005230D1 (de) 2007-11-22
US7590381B2 (en) 2009-09-15
EP1689104B1 (fr) 2007-10-10
EP1845643A3 (fr) 2007-10-31
US20060229056A1 (en) 2006-10-12
PL1845643T3 (pl) 2012-12-31
ATE512514T1 (de) 2011-06-15
ATE375641T1 (de) 2007-10-15
PL1689104T3 (pl) 2008-03-31

Similar Documents

Publication Publication Date Title
DE69920411T2 (de) Verfahren und system zum übertragen von audiodaten zusammen mit anderen daten, umfassend ansteuerdaten, an einen empfänger
DE69031510T2 (de) Abstimm-Steuergerät mit der Möglichkeit einer Abstimmung mittels Etiketten und unter Verwendung alphabetischer Etikettenspeicherung
EP1689104B9 (fr) Radio pourvue d'un affichage pour des informations textuelles faisant référence à d'autres objets d'informations textuelles
EP0610313A1 (fr) Systeme de radiodiffusion et recepteur de radiodiffusion
EP2126733B1 (fr) Dispositif et procédé de production d'un flux de données et dispositif et procédé de lecture d'un flux de données
DE60115627T2 (de) Sende-Empfänger und Verfahren zum Bereitstellen von züsatzlichen Diensten
EP0256295A2 (fr) Décodeur de vidéotexte avec une mémorisation de vidéotexte spécifique pour un programme de télévision
EP2034641A2 (fr) Procédé et dispositif de représentation d'informations RDS pouvant être affichées
DE60019802T2 (de) System und gerät zur erzeugung von nachrichten in mehreren sprachen für die verteilung an set-top-endgeräte in einem rundfunkfernsehsystem
EP2197202B1 (fr) Procédé et dispositif destinés au traitement de données et système comprenant ce dispositif
DE102005026539B3 (de) Verfahren zur Bereitstellung von Informationen betreffend Rundfunkinhalte an einen Nutzer
DE19645435A1 (de) Rundfunkprogrammsignal sowie Verfahren zum Verarbeiten dieses Signals
DE602004002186T2 (de) Verfahren zum Übertragung von Multimedianachrichten zu einer heterogenen Endgerätgruppe
EP0923195B1 (fr) Récepteur de recevoir des signaux DAB
EP1248398B1 (fr) Récepteur pour radiodiffusion RDS à sélection PTY
EP0836292B1 (fr) Méthode et dispositif pour la présentation sélective, selon la région ou se trouve le récepteur, de messages codés numériques radiodiffusés
DE10309612B4 (de) Verfahren zur Alarmierung mittels Funkruf und Funkrufempfänger
DE4422235A1 (de) Rundfunkempfänger
EP0742668B1 (fr) Méthode de reproduction de signaux de données dans des canaux d'émissions de télévision ou de radio
DE102005014527A1 (de) Verfahren und Übertragen von Daten
WO2003019801A2 (fr) Procede de reproduction de fichiers multimedia dans un terminal
DE102011078237B4 (de) Programmführungseinrichtung für einen Fernsehempfänger und Verfahren zum Generieren eines Programminformationsmenüs
DE19914077A1 (de) Verfahren und Vorrichtung zur Anzeige von über ein Netzwerk übertragene Echtzeitvideoinformationen
WO2005022909A1 (fr) Guide electronique de programme
DE10063731A1 (de) Verfahren zur Bereitstellung von Zusatzinformationen zu einer Fernsehsendung

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060508

AC Divisional application: reference to earlier application

Ref document number: 1658689

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1094488

Country of ref document: HK

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

17Q First examination report despatched

Effective date: 20070622

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AC Divisional application: reference to earlier application

Ref document number: 1658689

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REF Corresponds to:

Ref document number: 502004005230

Country of ref document: DE

Date of ref document: 20071122

Kind code of ref document: P

GBT Gb: translation of ep patent filed (gb section 77(6)(a)/1977)

Effective date: 20071109

REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1094488

Country of ref document: HK

ET Fr: translation filed
REG Reference to a national code

Ref country code: PL

Ref legal event code: T3

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2294754

Country of ref document: ES

Kind code of ref document: T3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080110

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080310

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080110

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

26N No opposition filed

Effective date: 20080711

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080111

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071010

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080411

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 15

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230512

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: LU

Payment date: 20230821

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: TR

Payment date: 20230817

Year of fee payment: 20

Ref country code: IT

Payment date: 20230831

Year of fee payment: 20

Ref country code: IE

Payment date: 20230821

Year of fee payment: 20

Ref country code: GB

Payment date: 20230824

Year of fee payment: 20

Ref country code: ES

Payment date: 20230918

Year of fee payment: 20

Ref country code: CH

Payment date: 20230902

Year of fee payment: 20

Ref country code: AT

Payment date: 20230818

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: PL

Payment date: 20230816

Year of fee payment: 20

Ref country code: FR

Payment date: 20230822

Year of fee payment: 20

Ref country code: DE

Payment date: 20230822

Year of fee payment: 20

Ref country code: BE

Payment date: 20230822

Year of fee payment: 20