FR2859848A1 - Future event e.g. show, related information broadcasting process for terminal e.g. mobile telephone, involves providing platform for broadcasting information to mobile telephones according to formats adapted for telephones - Google Patents

Abstract

The process involves providing a platform (12) for collecting information and broadcasting it to mobile telephones according to the formats adapted for the telephones. The platform automatically selects future events based on a parameter in a group consisting of software available to the telephones, size and shape of screen, its memory capacity, its output, language and available display colors. Independent claims are also included for the following: (a) a platform for providing information about the events to take place to a terminal (b) a mobile telephone.

Description

METHOD, SYSTEM AND EQUIPMENT FOR BROADCASTING TO TERMINALS

  INFORMATION ABOUT FUTURE EVENTS

  The invention relates to a method, system and equipment for broadcasting information relating to future events to terminals.

  By future event, we mean here an event scheduled in advance of which, in general, the date is known. These include, for example, shows, publications, marketing products, chats (chats), forums, interviews on the Internet. Broadcasting such events is particularly important for economic actors and consumers. Thus, television programs are probably the greatest publishing success.

  In addition to printed publications, guides to future events are disseminated by electronic means, such as home and business computers, using the Internet.

  The invention results from the recognition that the importance of knowledge of future events is such that it is preferable that it be available practically continuously for users. For example, a person on the move may wish to receive warnings for certain future events.

  Thus, the method according to the invention is characterized in that it provides a connectable platform, in particular via the Internet, to databases or servers of event producers and in that one broadcasts, from of this platform, events by channels and / or mobile phone formats. The name mobile phone is here used in the sense of mobile communication equipment. It includes not only mobile phones of the GSM, GPRS and UMTS types, but also smartphones, ie telephones that can broadcast text, pictures and sound, PDAs and laptops equipped for communications. telephone.

  Thus, users can see real-time, in the form of text, image and / or sound, events since in general users do not separate from their mobile phone.

  Preferably, the platform is such that it formats future events for terminals of other types such as personal computers, television terminals, especially interactive television, or personal assistant type terminals (PDAs). for Personal Digital Assistant).

  According to one embodiment, the platform contains information relating to the characteristics of the mobiles and, thanks to these characteristics, the platform sends the events to the mobile phones so as to transmit to each mobile only the information that he is likely to receive. For example, video will not be transmitted to a mobile phone if the mobile terminal does not have a video receiver. For example, the information can be selected according to the size of the mobile phone screen.

  In one embodiment, the future events transmitted by the platform are introduced in the calendar usually provided in the mobile. However, in a preferred embodiment, the mobile phone has a calendar of future events that is separate from the usual calendar such as the calendar used to record appointments.

  According to one embodiment, the sound type events are accessible on an audiotel type audio server and the information relating to these events is communicated to the mobile telephone so that the user has only a simple maneuver to perform to access the audio server. event in the audio server. For example, the information is transmitted to the mobile in the form of an icon on its screen and if the latter is of the touch type, a simple press on this icon allows access to the sound event in the audio server.

  In one embodiment, when the event occurs at a certain date in the future, means are provided for the user of the mobile phone to issue a request to the platform to be informed a predetermined time before the event. 'event. In this case, the mobile phone comprises means for transmitting to the platform, or server, a pre-event alert request request, for example one hour before the event, and the platform includes means for recording the address of the requesting mobile, that is to say his telephone number, and means for sending to this mobile an alert message at the chosen time, this message being, for example, of the SMS type (text) or MMS (multimedia).

  These required alerts are, according to one embodiment, modifiable using the mobile phone. The modifications may consist of a choice of the moment of the alert or a deletion of the previously selected alert.

  The future events transmitted by the platform to each mobile phone are preferably based on a profile previously transmitted to the platform. The mobile phone can then have means to modify the profile, such as the topics of interest of the user.

  Preferably also, the mobile phone is assigned means for modifying other characteristics of the subscription such as billing mode.

  Communication between mobile phones and information publishers is preferably done directly without going through the platform. In this case, the platform is used to forward communication requests to the event editors.

  In one embodiment, the platform includes service billing means. Thus, in one example, this platform includes means for counting the number of messages such as SMS transmitted to each mobile phone to form the basis of billing. Billing can also depend on the number of themes of interest chosen by each mobile phone user. In this case, the platform will also include means for counting the number of themes chosen by each mobile phone user.

  According to one embodiment, the platform is used to allow the sale of a good or a service corresponding to a future event. For example, the platform transmits to the mobile concerned information in the form of an icon for mobile touchscreen and just press this icon to place the order. In this case, preferably, the control operation performed by the user is followed by a query appearing on his screen requesting authorization to transmit the billing information to the seller and it is only after confirming, for example by simply pressing a corresponding icon, that the command will be carried out.

  Thus, for the sale, as for the other 35 operations, one will choose maneuvers to be performed by the user which are very simple without the user having to enter information via the keys.

  According to one embodiment, it is expected that the platform can enable the establishment of communities or groups from the profile of a user. Thus, the user having chosen a specific profile to receive information on future events, he can offer this profile to other users who will then receive the same calendar and the same information depending, of course, the terminal of each. These groups may concern not only mobile phone owners but holders of other types of terminals.

  In one embodiment, each member of the group has the possibility of adding a new event or requesting the authorization of a manager to add an event, for example a dinner.

  In one embodiment, the platform includes a motor for retrieving information from internet servers and / or databases, which engine preferably uses the XML / DTD standard.

  The platform also preferably includes a tool for administering the information communicated by the content providers. This administration tool makes it possible to add, delete or modify the information contained in the platform, for example under the control of the content providers. The Administration Tool can also be used to check content, approve, select, and / or categorize events in the platform event database.

  Preferably, the information is transmitted directly by a publication member which transmits the information to the mobile telephone via a GSM, GPRS or UMTS channel.

  According to one embodiment, the calendar of future events is not function of a profile.

  Thus, the invention relates to a method for providing terminals with information on future events, which information and / or events can be transmitted by a network, for example of IP type, which is characterized in that a platform The form is intended to collect information and disseminate it to mobile phones in formats adapted to mobile phones, the platform automatically selecting events based on the capacity of subscribing mobile phones.

  Preferably, the selection of the events to be transmitted to the mobile phones is performed taking into account at least one of the parameters included in the following group: the software available to the mobile phone, the size of the screen, the shape of the screen, memory capacity, bit rate, language and display colors available.

  Upcoming events can be introduced into a calendar specific to these events, distinct from the usual calendar of mobile phone appointments.

  Alternatively, a calendar of upcoming mobile phone events is also used for appointments.

  Preferably, for video and / or audio and / or text events that are directly accessible using mobile telephones, the platform sends these mobile phones a software means allowing by a simple maneuver such as the support on a key or contact on the screen, to access the video event and / or audio and / or text.

  According to one embodiment, the platform comprises software means for addressing mobile phones, at the request of the latter, an alert prior to an event, a predetermined time before this event.

  The alert is sent by a message of the SMS or MMS type.

  In one embodiment, the platform comprises software means for establishing the billing of the services related to the events to which the mobile phones access.

  The platform may include software means for forming groups of users having the same event selection profiles.

  Preferably, the platform comprises software means for addressing information on future events to other types of terminals such as computers, television receivers or personal assistants.

  In this case, the platform can operate in server mode and include software means for terminals to access content dedicated to them.

  The platform may also include software means for addressing to the same subscriber, information relating to future events on several terminals, the type of terminal being chosen according to dates or times preselected.

  In one embodiment, future events are displayed and stored in mobile phones.

  The invention also relates to a platform for providing terminals with information on future events that can be transmitted over a network, for example of IP type, which is characterized in that it comprises means for collecting the information future events and broadcast them to mobile phones in formats adapted to the latter and means for automatically selecting events according to the capacity of the mobile phones subscribers.

  Preferably, the platform comprises means for selecting the events to be transmitted to the mobile phone taking into account at least one of the parameters included in the following group: the software available to the mobile phone, the size of the screen, the shape of the screen, its memory capacity, its bit rate, the language and the display colors available.

  The platform may include means for addressing to the mobile phone software means for video and / or audio and / or text events which are directly accessible by mobile telephones, by a simple maneuver such as pressing a key or contact on the screen to access the video event and / or audio and / or text.

  According to one embodiment, the platform comprises software means for addressing mobile phones, at the request of the latter, an alert prior to an event, a predetermined time before this event.

  In this case, the platform may comprise means for addressing the alert by a message of the SMS or MMS type.

  In one embodiment, the platform includes software means for establishing the billing of events-related services accessed by mobile phones.

  The platform may include software means for forming groups of users having the same event selection profiles.

  The platform may also include software means for addressing information on future events to other types of terminals such as computers, television receivers or personal assistants.

  According to one embodiment, the platform is of the server type and includes software means enabling the terminals to access content that is dedicated to them.

  In this case, the platform may comprise software means for addressing to the same subscriber information relating to future events on several terminals, the type of terminal being chosen according to dates or times preselected.

  The invention also relates to a mobile telephone characterized in that it comprises means for connecting to a platform for collecting information on future events that can be transmitted over a network, for example of IP type, and means for receiving data from this platform corresponding to future events, which data is in formats adapted to the capacity of the mobile phone.

  In one embodiment, the mobile phone includes means for future events to be introduced in a calendar specific to these events, distinct from the usual schedule of appointments.

  Alternatively, the mobile phone has a calendar of upcoming events that is also used for appointments.

  In one embodiment, the mobile telephone comprises means for receiving from the platform a software means allowing, for video and / or audio and / or text events that are directly accessible using the mobile telephone, a simple maneuver such as pressing a key or contact on the screen, accessing the video event and / or audio and / or text.

  The mobile phone may include means for addressing a request to the platform to obtain an alert prior to an event, a predetermined time before this event, and means to receive this alert.

  In this case, the mobile phone comprises, for example, means for receiving the alert by a message of the SMS or MMS type.

  Other characteristics and advantages of the invention will become apparent with the description of some of its embodiments, this being done with reference to the accompanying drawings, in which: FIG. 1 shows the main components of a plate FIG. 2 shows the data collection component of the platform shown in FIG. 1, FIG. 3 represents a message receiving component forming part of the platform. FIG. FIG. 4 illustrates an HTTP access to a content provider for a platform according to the invention, FIG. 5 shows a data collection module for the platform according to the invention, the FIG. 6 illustrates a mode of operation of the component shown in FIG. 5, FIG. 7 illustrates another operating mode of the component represented in FIG. 5, FIG. 8 shows another operating mode of FIG. component of FIG. 5, FIG. 9 shows sub-modules of the platform 10 represented in FIG. 1; FIG. 10 represents another sub-module operating mode of the platform according to the invention, and FIG. 11 represents the data administration and management module of the platform according to the invention.

  The description which follows will firstly provide a general functional presentation of a system according to the invention (1) and then the various elements making up this system (2) will be described.

  1. General Functional Overview (Figure 1) 1.1. Collection of contents The events can be collected by the platform 12 in three different ways: E Receipt of messages from the content provider 13 as an XML document.

  É HTTP access offered to the content provider, by which he can send a new event by filling out a form including all the fields described in the XML / DTD format.

  Polling: sends, from the platform, collection requests to the content provider, automatically or manually: A set of requests is defined for each content provider. The purpose of a request is to find events on a content provider's site. A query is in XML format. It is such that it will look for an event at a specific address (URL) and according to pre-established keywords.

  Queries can be started either automatically at predetermined times or manually. They can be launched one by one, or grouped according to the content provider and the rules applied to it, or for all listed content providers.

  A request for a content provider can be modified or created by the Webmaster (platform administrator). The content provider can manually launch its own queries in order to retrieve online the events it has issued itself.

  If it turns out that an issued request does not succeed normally (because of missing links or other problems), an email (email) is sent to the webmaster and / or the sender.

  The events received are saved in a database of 20 data. But they are visible to users only after classification and verification.

  1.2. Verification and classification of events Once the event is recorded in the database, different elements must be checked. If one of these checks is not correct, then the event remains in the temporary state (not visible to users) and an email is sent to the webmaster and / or sender.

  The verification rules may depend on the content provider, or other criteria, for example the previously defined litigious words: the received text is compared with that of the contentious word database. If some words are listed then the event will be rejected.

  The verification rules are modifiable.

  Once the event is recovered and the main fields checked, the event is then ranked according to specific criteria. The event must be classified by industry and sub-industry or category and subcategory (eg Sport / Football / Championship /). If the type of (sub) industry or (sub) category can not be identified, then the event remains in the current state (temporary state) and an email is sent to the webmaster and / or sender.

  The field indicating the expiry date is checked.

  If it is invalid or can not be correctly identified (Date and Time must be greater than or equal to the validity limit of the event), the content provider rule is taken by default and if it is not there is none, a default general expiration date is calculated. This field is always defined.

  If certain fields, the list of which is defined beforehand, are not correctly identified or are not valid, they are replaced by those of the content provider itself, for example for the following fields: Time Zone 20 of the content provider, Country where the event is located, URL Logo. If one of these fields can not be defined, the event remains in the current state (Temporary state) and an email is sent to the webmaster 14 and / or the sender.

  The remaining fields to check are validated against the rules relating to an event (general rules contained in the system database). If one of these fields can not be defined, an email is sent to the webmaster and / or the sender.

  Once all event fields have been verified, all date / time fields of the event are converted to GMT time. The event then changes from the temporary state to the Accessible state, that is, it becomes visible to the user. 30

  An event received twice will be presented only once. However, some events may be presented more than once. The choice of the number of presentations depends on the relationship with the content provider, for example the one that has paid the highest price, or the rank of presentation.

  1.3. Content processing A batch 17 (program running in the background) can be started, either manually or automatically at regular intervals, defined by the administration 14 of the platform, to update the status of the event , regarding visibility and accessibility, and archiving.

  Events that have not yet passed have Visible status.

  Once the event is over, its status changes from Visible to Accessible. The event can no longer be presented in One but is still viewable by users until it expires. This may depend on the contract with the content provider, which is especially relevant for On Demand events that can be viewed after the event date.

  Events whose expiration date has passed 25 are automatically cleared from the database to be saved to other media.

  Similarly, a batch program can check the validity of the links of the recorded events. If the main links no longer exist, the addresses are no longer assigned, the event goes to the non-visible status, and a message is sent to the administrator concerned.

  1.4. Presentation to End Users 15 Viewing Events An event can be viewed in one of two ways: Overview (Events in List).

  Calendar view (Events presented in a calendar 16).

  Four levels of viewing an event are possible: For a non-member user, the events highlighted are the most viewed.

  É For a member user, the events highlighted correspond to their profile, for example only sports events are displayed if the user has chosen only Sport as a category.

  In addition, the user must have access to his personal space, which contains his calendar and his own bookmarks where are stored all the events corresponding to his interests.

  Finally, events should be searchable by theme: categories and subcategories for the general public, industries and sub-industries for professionals. The user can also use keywords.

  If a user logs in as a non-member or a member without a profile, the type of content presented depends directly on the analysis of their environment: language, hardware and software used. In the case where the information on the environment is not accessible, the content corresponds to the most watched events.

  If a user logs in as a member or subscriber, the type of content presented depends directly on their profile, the most watched events, or events that are specifically promoted by the administrator.

  All date / time fields of the events are converted according to the geographical location from which the user registered when he established his profile. In case of displacement, these fields are automatically converted according to the time of the place where the user is. For example, if the event is to take place at 8 pm in Tokyo, it will be indicated at 12 o'clock if the user is in Paris, and will be converted at 11 o'clock if the user moves to London.

  General view (events presented in the middle of the screen). The main events are displayed in the middle of the screen.

  The user has the opportunity to choose how he wishes to view the events of the platform, that is to say, generally, by the most watched events, or with respect to his profile.

  The type of information displayed per event includes the following fields of the XML DTD: - Content Provider Logo.

- Title of the event.

  - Short description of the event (see below).

  - Long description of the event (see below).

  - Other features (See below).

  Calendar view (events presented by week / month / year).

  All events can be viewed in a daily, weekly, monthly or yearly calendar.

  The calendar can filter events by category or keywords.

  On the user's own calendar appear all events and other information that he has chosen to record there.

  The user has the opportunity to choose how he wants to view the events of the platform, that is to say, either generally by the most watched events, or in relation to his profile or in relation to the elements he has selected before.

  The information presented is adapted to the type of view (daily, weekly, monthly or annual). For example, for a monthly view, only the title of the event is displayed, possibly with the Logo of the event or content provider, while for a daily view, all the information is displayed.

Short description Depending on the status of the event, only some fields of the event

  appear, as the brief description of the event.

Long description

  If a particular event is chosen, a long description of the event must appear, in addition to the information already presented.

  Other Features The following features appear next to each event: - Add the event to its calendar.

  - Add the category or Industry to his profile. 25 - Send to a friend.

- request an alert.

  When a user chooses to send an event to a friend, he has access to his own directory, and only has to select the names of the desired people. Their e-mail addresses or mobile phone numbers are then automatically recorded in the appropriate boxes.

  Content Search by a User A user can search for events of interest by various pre-established criteria: By pre-established (under) category / (under) industry.

  É By language É By the country of origin of the content (US content, European content, French content, etc.).

É By keyword.

É By other predefined words.

  The criteria according to which an event is sought are adaptable and are not limited to the predefined categories. All fields in the XML / DTD format can be used to search for an event.

  Management of the user profile The user has the possibility to define his profile in three steps, which facilitates the task of defining the profile.

  He has at his disposal three levels of profile. These profile levels can also be adjusted according to the type of terminal on which the user connects (mobile phone or PC).

  The list of fields described below is provided as an example. It depends on the terminal used.

  Basic Profile - Level 1 Name, First Name, Password, Confirmation of Password, Email, Telephone (not required).

  Advanced profile - Level 2 Mobile phone, address, geographical position, language, mobile connection speed (GSM, GPRS or UMTS), preferred reception support depending on the date and time, security question, security answer, limitation number of alerts.

  Expert Profile - Level 3 The user can define his profile manually, with a list of his interests, (Sub) industries for professionals (Example: Financial services, etc.), (sub) categories for individuals (Example : Sport, Music, Cinema, etc.), or use an automated definition: for the sake of simplification, pre-categories are proposed where different interests have been chosen.

  As an indication, these pre-categories can be: Women (contains, for example, the categories: Cinema, People).

  Teenagers (contains, for example, categories: games, shows, music).

  Sport (contains for example the categories: Sport, Cinema).

  Young executives, or prosumers (contains categories: Financial Services, Football, Fl).

  Automatic display The user's data is automatically filled, for example when verifying his personal data or when making a payment. For example, if he visits a site selling consumer products, and if he wants to buy a product, a message appears asking him permission to automatically send the seller his personal payment data. These are transmitted after authorization and validation of the form presenting these data.

  Display media Events or other types of information can be sent as alerts to the following devices: • Mobile phone (including WAP, GPRS or 3G compatible).

  É Internet (PC) É Interactive television.

Personal Assistants.

  The displayed pages appear so that the media format is respected.

  The user can access the information in a simple, easy and fast way, for example by clicking on a link present on the sent event. 10

  All the information extracted from the system is easily accessible from the various types of terminals.

  É For mobile phones: via SMS (text), MMS (multimedia) or the transformation of text into speech.

É For computers by Email.

  É For PDAs by Synchronization.

  The information is sent to the user according to his profile. The user chooses the type of terminal on which he wishes to receive his information. The type of terminal may be different depending on the time of day.

  Other system functions The platform groups together all the data relating to the user. This data is defined in order to secure its access, personalize the proposed content as well as its mode of distribution / access, manage all the features - free or paid - which it can benefit: É Personal data.

É Interests.

  É Filters (eg language).

  All the information present in the platform can be viewed and modified from any terminal and at any time.

  Personal data This is the set of personal details of the user.

  Some of this information (login, password, e-mail address) is required in order to benefit from the basic functionalities of the platform.

  In general, activation of the various features of the platform (eg reminders, shared calendar, unified messaging, etc.) is directly correlated to the type and amount of personal information provided by each user. .

  Interests The most relevant content is proposed to each user. The platform thus ensures, through semantic and contextual filters, that the proposed content truly corresponds to the content specifically requested.

  In addition, the platform dynamically offers each user to complete his interests based on content regularly requested but not yet recorded in his profile. In this way, the profile database can be updated regularly. For example, if a user wants to buy a car, he will look at events related to the sale of cars. The corresponding interest can then be added to his profile, and he will automatically receive this type of event.

  We group together all categories, subcategories and keywords chosen by each user to customize the content that will be sent.

  We can, at first, limit to three the tree of each category, for example Sport / Football / Dl. Each of these categories or sub-categories may have one or more keywords associated with them to increase the relevance of the proposed content (for example, a particular Dl player).

  The filters Each user can define the following filters: Origin of the content, for example countries, such as France, Germany and China.

- Language of the content.

  - Terminals on which this information will be accessible: PC, Mobile, PDA (personal assistant).

  - Maximum number of alert emails per day.

  - Time and terminal for receiving alerts. Several slots are possible: day, week, hours, 35 terminal.

  Filters also customize the user interface and the type of content assigned to each device.

  Message Center The purpose of the Message Center is to enable each user to communicate easily within a community: chat, forum, instant messaging, but also outside: management of mail, address books, etc. The following technologies are used: unified messaging, text to voice and voice to text converters, and synchronization with all terminals.

  The message center allows billing, including the sending of SMS and all features with high added value, that the user can pay either by accepting an advertising message associated with each use, or by pre-payment or by payment with each use.

  Address Directories A user can create an unlimited number of directories which he can name as he wishes, for example: friends, business relations, restaurants, etc. It has the ability to simultaneously view data from all its directories.

  The user can in one click call a blank card, change one or more fields of a contact, or erase an existing contact.

  By clicking either on the e-mail field or on the mobile phone field, the user accesses a window for editing and sending messages, the e-mail address or the mobile number being automatically placed in the corresponding field.

  The user can also search for a contact by keyword (search of the word on all the fields) or by categories (eg Ville = Paris) of information on all of its directories.

  The calendar The calendar is one of the central elements of the system, since it allows each user to create his own guide of the events he wants to follow on the Internet. In this central profiled guide function, the calendar associates specific functionalities, notably allowing it to be recalled or to retransmit easily its events to contacts or a community.

  The user can also use the calendar in a traditional way (making appointments, notes, reminders of birthdays, etc.) while benefiting from the same associated functionalities.

  The user can choose to display his calendar: in day, week, month, year format. An additional monthly calendar is always present on the screen in order to be able to point to a specific date, which is then displayed on the main calendar.

  The event pointer displays the event titles that correspond to both the date chosen on the calendar and the profile (points of interest) defined by the user.

  An add button associated with each title allows the user to reference in a click the event on the chosen calendar.

  By clicking on the title of the event, the user 25 obtains a more complete description and accesses all the functionalities associated with an event.

  Only the user has the option to record an event on his calendar, not the platform manager.

  Each event recorded on the calendar is associated with the following functions / indications: delete the event, activate / deactivate an alert, relay to a friend.

  The user can enter an appointment, a note or any other information on his calendar independently of the events. At each of its inputs, the user can associate the same functionalities as for an event. Features É Activate an alert. This function enables the sending of a reminder message by e - mail or SMS (to be specified by the user) X minutes / hours / days before the start of the event. The presence of a logo indicates whether this feature has been activated or not for each event.

  When the user chooses to be alerted by e-mail, their e-mail address automatically appears in the sending address. If his email address is not present in his personal data, a message invites him to complete his profile with this information.

  If the user chooses to be alerted via SMS on their mobile or landline phone, or they agree to pay by billing on their phone subscription, by micro-payment, or deduction from their pre-paid account, or they agree to receive advertising with the SMS sent. The user can choose to limit the number of SMS messages received per day.

  É Choice of the calendar. At each new entry, the user specifies on which calendar he wishes to save the entry. This function is active only if the user has created more than one calendar.

  É Retransmit the event / entry. This function allows to send, to one or several contacts, in the form of e-mail and / or SMS, the title, the date, as well as the time of beginning and end of the event and / or of the entry . The user accesses his address book in one click and easily selects the e-mail address or the mobile number.

  If the numbers entered do not appear in the database, a message proposes to the user to qualify this contact in his address book.

  Multiple calendars The user has the possibility to create several calendars which he can name as he wishes. The all calendars function makes it possible to display on a single calendar all the events and referenced entries.

  System Information Dialogue data is provided that contains the following 5 elements: System Description / Privacy Policy / Use / Advertising and Subscription / Partner Program / Contact Us.

  When the user clicks on one of these sections, a text description of the section appears. Help

  A dialog contains the following elements: Using the system / first visit / questions / contact us.

  When the user clicks on one of these 15 sections, a text description of the section must appear. Event registration Add to my calendar: In one click, you can record an event in the chosen calendar, automatically integrating its title, date, start time and end time.

  Add to my profile: Next to each event, a button add to my profile allows you to save the category or subcategory on which the event depends in the profile my interests of the user.

  Sending to a friend: we can retransmit an event to a contact present at no in the address book of the user, either as an email or as SMS.

  Request an alert: The user can activate an alert for each of the events present on one of his calendars.

  For each event, he can choose on which internet terminal he wants to be alerted (e-mail, SMS), and how long before the event he wants to receive the alert (minutes / hours / days) A pictogram indicates when a alert is enabled for an event.

  Options Tabs: The user can define his own tabs representing the areas of interest he has chosen (for example: Football, Zidane, etc.). These tabs appear in the user's home page. The name of these tabs is editable or erasable.

  News The system offers two distinct editorials: É the first is common to all users in the same country and is edited by an administrator.

  The second is specific to each user according to the categories and subcategories present in their profile of interests. It is composed of the most representative events of each category, the selection being done through the administrator of the system.

  System user access The user 's access is by means of: • cookies, in order to personalize the home page according to the known profile of the user.

  É a login and password to secure 1 access.

  É an additional password for all 25 transaction areas, which are otherwise secure. 1.5. Other users Content provider Each content provider has access to a login and password secured area, including: É the list of its referenced events, É the service providers on which its events are referenced, É the related statistics visitors who have been drained on each of their events, and É the list of specific services to which he has subscribed.

  Service Provider Each Service Provider has access to a secure login and password 5 area, which includes: É the number of clients who have subscribed to the service offered, DPG, and subscribed.

  É the statistics relating to the customers using the É the list of the specific services to which he has

2. Technical description

  2.1. General Architecture This is shown in Figure 1 which is an integral part of this description.

  2.1.1. Role of each of the actors 1. Service Provider 18 A service provider represents a group of end-users. This is for example the operator through which a person X connects to the platform.

  The services that the user can access may vary by service provider.

  The platform manager defines the services and categories of the service providers. The service provider then proposes to its users to subscribe to a certain number of services selected from the sets of services that it can offer.

  2. End-User 15 An end-user is necessarily associated with a service provider and can only subscribe to the services contained in the service packages offered by this service provider.

  Each user is associated with a profile (center of interest), which allows him to filter events according to his 35 favorite categories.

  3. Content Provider 13 Each recognized content provider has more or less restricted access to the platform's site.

  Content providers therefore have access to certain specific services, which then allow them to track their information.

  4. Webmaster 14 This is the site administrator.

  5. Editorialist The editorialists represent the content management team of the site.

  An editorialist is responsible for the events presented on the categories of categories he is responsible for administering. It receives alert messages about new events classified in its branch and that could not be fully validated, and therefore still invisible to users. He decides to make them available or not.

  2.1.2. XML / DTD Format The XML / DTD format is a standard for representing 20 events between the platform and content providers. 2. 1.3. The platform components The main components of the platform are: É The collector 19: This is the main component, which retrieves and processes the contents, and stores them in the content base.

  É The Administration component 14: It is in charge of the administration of the different actors, the resources, the categorises and the events.

  É The Calendar and Notification 16: Il 30 component is responsible for managing the calendar and reporting events to end users.

  É Data presentation 17: it provides access interfaces to the different actors.

  These components are based on an infrastructure providing the necessary services. This infrastructure includes: É The operating system.

  É The database management system.

  É Access to networks for messaging and file transfer.

É Publishers.

É Browsers.

  É XML / DTD processing.

  2.2. Operation 2.2.1. Collection of data at the content provider. This collection is represented in FIG.

  1.- The collection module 22 sends a request http 20 for collecting new content at a frequency determined by the administrator and corresponding to the source information of this content provider.

  This module 22 has the function of collecting, classifying, storing, analyzing, administering and managing the rules relating to events.

  2. Upon receiving this request, the content provider 24 returns (26) a document conforming to the XML / DTD representation, describing a new event.

  3. In the module 22, the event collector then sends this document to a filing means.

  4. After analysis by the ranking means, the content is sent (28) for storage in a database 30 by means of an indexing system allowing its rapid search according to the information of the representation XML / DTD.

  In the case where the contents could not be classified correctly, the filing means informs (32) the person responsible for the content, by sending on his terminal 34 an electronic mail.

  5. After classifying the event, the module 22 queries (36) the Content Provider Database 38 to retrieve information about the content provider having declared the event (for example, the rules specific to this provider). This database 38 administers the contents, provides the rules and stores the events.

  6.- Then the XML document is analyzed in order to verify its conformity with the rules established in the base 42 of the rules. Some rules depend on the content provider, others are general rules. The analysis is carried out in module 22 with consultation (44) of base 42 in base 30.

  7.- The document is positioned (46) in the state (compliant or non-compliant) in the base 30.

  7 '.- In the event of non-compliance, the event analyzer of module 22 informs (50) the responsible person (administrator in general) by sending him an electronic mail via module 34.

  8 '.- The module 34 then activates (54) a notification interface.

  9 '.- The interface 52 then activates (56) a mail module 58 to generate the sending of an email to the administrator.

  10 '.- The module 58 generates sending (60) mail to the administrator through its integrated SMTP client.

  2.2.2. Receiving messages from the content provider.

  This reception is shown in FIG.

  1. Content provider 70 sends (72) the XML document by email to the address of a SMTP daemon listener.

  2. Upon receiving this e-mail, the SMTP daemon 74 transmits (76) the received document to the module 22 through the interface provided by the latter.

  3.- The treatment is then similar to that described in 2.2.1.

  2.2.3. HTTP access offered to the content provider 35 This access is represented in FIG. 4.

  1.- The content provider can declare and send (82) a new event using a page 84 including all the fields described in the XML / DTD format. This page is presented as a form; the event is generated and sent (86), after authentication, to the event collector.

  2. Upon receiving the XML document, the module then sends this document to its classification means to verify that the event is classifiable.

  3. After verifying that the event was classifiable, information about the content provider that reported the event is retrieved (88) from the content provider database 41.

  4. Then the xml document is scanned for compliance with the rules stored in the rule base.

  5.- Depending on the result of these processes, a response is sent back to the event collector.

  6. This response is returned to the content provider 80 via page 84.

  7.- Depending on the results contained in this response, the content provider 80 has the following choices: E either repeat the operations from 2 to 6, if the results are not correct, E either request the storage of the event in the database 30 of the platform if the results are correct.

  8. The module 22 is informed by its event recuperator 84 of the storage request.

  9.- The content is stored in the base 30 through an indexing system for its quick search information DTD.

  10.- and 11.- The content provider 80 via the module 22.

  2.3. Description of the software modules

  in office is informed 2.3.1. Data Collection Figure 5 shows the module 22.

  The purpose of the module 22 is to retrieve the events, analyze them and store them in the database.

  This module 22 is an application based on an infrastructure capable of sending HTTP requests to the internet servers of the content providers, automatically and repeatedly or in a timely manner, then retrieving the response from the remote site, extracting one or several events that will be verified and validated, then stored in the database to make them easily available for any portal application (categorization, event guide ...). On the content provider side, an internet server must be able to receive an event request and return the relevant data in explicitly defined format. The module 22 comprises the following sub-modules: É An event collector (ECOL), or event collector, managing the process of collecting and processing information.

* É A polling system (EPOL), allowing to get content from content providers by acting as an HTTP client.

  É A mail receiver (EMAI), attached to the Notification server. It is associated with an e-mail address reserved for the reception of events. It is able to extract usable data from received mails.

  É An access door (EJSP), allowing content providers to access the platform themselves to request the recording of events. These events are verified and validated in the same way as when they arrive by polling or email, except that the operator is immediately notified of the non-compliance or non-validity of his event.

  É A means of classification (ECLA). Once the XML has been parsed and checked for compliance with the DTD, it performs the categorization of the event.

  É An event analyzer (EANA), receives uncommitted events from polling, form or mail, after the sub-module has been classified by ECLA. By interpreting and applying the rules contained in base 42, he decides on the validity of events.

  2.3.1.1. The ECOL event collector 2.3.1.1.1. Objective ECOL is the central sub-module of module 22. It aims to distribute access to other sub-modules and manage the reception of data received by the different entries (polling, mail, JSP page).

  This module is also responsible for querying sites of content providers, either automatically and planned, through EPOL, or one-off, via pre-formatted queries.

  2.3.1.1.2. Management of punctual requests A request to a content provider may be initiated punctually by the administrator or by an authorized person via the administration interface. 1. The administration interface proposes the list of providers of

  available content and their requests. There may be several possible queries per content provider.

  2. The administrator selects the content provider (s) to query and the queries to use.

  3. He can then launch the queries by clicking on the Launch button.

  4. The requests are launched one after the other.

  5. For each of them: 6. The information request means (ISRQ) reconstructs the URL (address of the content provider to be interrogated).

  7. The EPOL submodule uses this URL to query the Content Provider server.

  8. It waits in response for an XML stream in the predefined format.

  9. This flow is returned to the ECOL submodule.

  10. The administrator is informed if there is a problem with one of the requests.

  2.3.1.1.3. Scheduled query management An automatic query system for content providers allows the updating of the event database. These queries are set via the administration interface: which content providers are queried, on which queries and according to which time interval.

  Querying remote sites is the same as for a one-time query.

  2.3.1.2. EPOL Submodule At regular intervals, which depend on the source information to be retrieved, this submodule generates HTTP requests to the content provider. In response to these requests, the content provider's HTTP server returns a document in XML (DTD-compliant) format containing the description of one or more events.

  After recovery, the event (or the list) is transmitted to the sub-module (ECOL) for further processing (classification, analysis, storage, state management).

  This operation is shown in FIG.

  1. and 2.- At regular intervals, ECOL queries (90 and 92) the databases 43 via the DAMA module in order to retrieve information related to the content providers.

  3.- ECOL activates (94) EPOL to retrieve the new source information associated with the content provider.

  EPOL then generates an HTTP 96 request for information request to the content provider.

  5.- In return (normal case) EPOL receives (98) an XML document describing one or more new events.

  6.- EPOL then transmits (100) to ECOL this new event.

  7.- 8 and 9.- ECOL then starts the treatments by activation (102) of ECLA to determine the category in which the event will be classified. For this ECLA queries the category table 108.

  10 .-, 11.-, 12.- 13.- and 14.- ECOL activates (110) then the EANA analysis sub-module to determine the state in which it will position the event (s) ( s). For this it queries the basis of the rules 43 of the content providers and the table 45 of the rules of events.

  15.- and 16.- After ECOL analysis stored at 114 and 15 positions the (or) event (s) in the determined state. 2.3.1.3. EMAI submodule EMAI is a server program that is constantly listening on a command port. It is able to interpret the SMTP protocol in order to recover the body of the message in MIME multimedia format. From this message body the content of the XML is extracted and returned to the ECOL submodule.

  This operation will be described using Figure 7.

  1. EMAI receives (120) in the body of an e-mail, an XML document describing one or more new events.

  2.- EMAI (122) then transmits to ECOL this new event.

  3.- 4.- and 5.- ECOL then starts the ECLA activation 124 treatments to determine the category in which the event will be classified. For this ECLA queries 126, 128) the category table 108.

  6.-, 7.-, 8.-, 9.- and 10.- ECOL then activates (130) the EANA analysis module in order to determine the state in which it will position the (or) event ( s). For this it queries the base of the rules of the content providers 43 and the table 45 of the event rules.

  11.- and 12.- After the event (s) in 2.3.1.4. Content management: EJSP In order to allow self-declaration of graphical interface, in form Page) is proposed. From form) the provider seamlessly, an XML document defining a new event.

  The EJSP submodule is user-activated and provides direct access to the ECOL submodule.

  Figure 8 shows the collection of contents using the EJSP submodule.

  1.- EJSP manages the connection of the content provider and its entries in the form.

  2. When requesting registration after the seizure of its event, EJSP transmits (130) this document to ECOL.

  3.- 4.- 5.- 6.-, 7.- ECOL then activates (132) the EANA analysis module in order to determine the state in which it will position the (or) event (s). For this it queries the base 43 of the rules of the content providers and the table of the 25 event rules 45.

  8.- A diagnosis 134 is returned to the user offering two possibilities: É Retype the form if the diagnosis is negative.

  É Repeat to record another event.

  In the first case, we repeat the operations from 1 to 8. If the diagnosis is positive, ECOL asks to store the event in the database.

  9 and 10 - ECOL stores and positions the event (s) in the state determined in the base 144.

  ECOL analysis stores and sets the determined state in the base 114.

  provider entries of content providers of new events, a JSP file (Java Server of this interface (format content can provide, A preliminary analysis, concerning the formatting of data and their consistency between them, is performed during the submission This allows you to quickly warn the user of trivial problems.

  2.3.1.5. Sub-module: ECLA The purpose of the ranking method is to identify in the event just analyzed its position in the category tree.

  As shown in Figure 9, ECLA is activated by ECOL before storage. He transmits the event to him to determine the path of each event in the category tree. ECLA checks this path for each event. In case of uncertainty to classify (use of subcategory label for example), a state value is set. Depending on the status value, ECOL decides whether to send an alert e-mail.

  ECLA has interfaces with ECOL and DAMA.

  It is activated by ECOL for identifying the branch of the category tree in which the event is to be classified. It uses the services offered by DAMA to access the category management table.

  2.3.1.6. The EANA Event Analyzer The purpose of the Analyzer (EANA) is to determine the state to be assigned to an event, from a rule base provided by a manager and describing a list of criteria related to the provider of content and events.

  After classifying the event, the ECOL event handler instructs the EANA event analyzer to parse its contents (the attributes).

  This analysis takes place in two stages: É One verifies the right to the registration of his content provider according to the data of his contract, and of any rules which are related to him.

  É To validate the event, all the necessary rules are applied, these rules being differentiated according to the content provider.

  Examples of validation rules: É The content provider must be known.

  É Fields must be correctly filled and formatted.

  É URLs must be valid (see LCHK).

  The expiration date must be after the current date.

  The result of this validation is a status (correct, passable, insufficient), accompanied by the list of errors encountered, and possibly modified attributes.

  Only the ECOL event manager makes the decision to make this event visible to users and / or send alerts to the Webmaster or editorialist.

  It should be noted that events originating from a content provider with a high level of trust (through an appropriate contract) may be validated more accurately than those from a less recognized content provider. For example, an interview provided by a reputable financial site will be better classified than an event from an unknown site.

  As shown in Figure 10, activated by ECOL, EANA returns the status of the event. ECOL then activates DAMA to store the event, and depending on the status value returned by EANA, ECOL decides whether to send an alert email.

  2.3.2. Data Management and Administration This MADM module, shown in Figure 11, is responsible for the management of: People, Collector E, Event Categories, Package E, Promotion E.

  The MADM module is the basic administration component that carries out data analysis and validation processes. MADM contains a set of submodules and each sub-module handles the management of a particular type of data.

  É CAAD: category administration module.

  É CPAD: module for the administration of content providers and its rules.

  É POAD: module of the administration of the frequency of the requests (polling) of the events.

  EVAD: module of the administration of the events.

  E TRIM: module for administering the expiration of events.

  ERAD: module for rule administration for event validation.

  É The DAMA module is the data access manager. MADM uses the set of submodules that make up the database access DAMA module to retrieve and store administrative data. These submodules are: É CAAC: category database access module 108.

  E CPAC: access module to the base 43 provider of content and its rules.

  EVAC: access module to the base 114 of the events.

  É ERAC: access module to the base 48 of the rules.

  In general, for each type of data, two types of access methods are available: one by graphical interfaces, the other by scripts performing batch operations.

  2.3.2.1. Parameterization of the polling frequency by the submodule (POAD).

  A Polling System is provided to retrieve events from a content provider. The polling frequency for each event is configurable by the administrator based on the source information. The results are stored in the base 43 of the content provider rules.

  2.3.2.2. Event Database Manager (EVAD). The EVAD sub-module uses the services provided by the EDAC sub-module for the recovery and storage of events in the database 114.

  It allows the following operations for the event management: • Add a new event in the database 114.

  É Modify the attributes of an event.

  É Delete an event from the database 114.

  The table below shows an example of an event description.

Field Type Description

  Type entire Event / info / on-demand / lotteries / meetings / Others Full size Video / Audio / Media / Chat / Interview / Auction Category Theme (Nx) Sport / cinema / Music ...

  Domain Chain New event category features Leading Channel

Short description Chain

Long description Chain

  Keywords String Representation URL URL Start Date dd / mm / yy hh / mm / ss am or pm Valid until Date dd / mm / yy hh / mm / ss am or pm Start of Availability Date dd / mm / yy hh / mm / ss am or pm Expiration Date Date dd / mm / yy hh / mm / ss am or pm Recurring Boolean yes / no Day Integer Mo / tu / we / th / fr / sat / sùn URL of the event URL URL Level 1 SubsectionURL URL URL Level 2 Home URL URL URL Level 3 Admission Integer FreeIf Subscriber / Bonus / Payment Each Time Price Channel (If payment is required to access the event.) Required Software Real Channel / Wind. Media / Quick Time / Yahoo Media [?] Login Webmaster Password Channel address Webmaster Tel. of the Webmaster String Name of the Content Channel Provider LogoURL URL Time Zone of the Content Provider Chain Country of the Event Channel US, UK, France, Europe, World, etc. Producer Channel Issuer String Name of Group String Name of Company Chain Activity Company Channel Name Stock Market Channel Language Channel An, fr, Bandwidth Channel Media Channel TV, internet, wap, radio Country of origin Channel US, UK, ...

  2.3.2.3. Event Validation Rules Manager (ERAD) The event validation rules are used to check whether a new event complies with established rules.

  The management of these validation rules is supported by the ERAD sub-module and the ERAC sub-module.

  The different operations that the webmaster and editorialists can perform are the following: • Add a new validation rule to the base 45.

  É Modify the attributes of a rule in the base 45.

  É Delete a rule from the base 45.

  The table below shows an example of a description field for event validation rules.

Field Type Description

  Rule ID Integer Key Event Type Integer Prohibited Words String Must Have a Post Date Boolean The content provider is registered boolean Existence of subcategories boolean Contains all tags [?] Boolean 2.3.2.4. Category Manager Manager (CAAD) CAAD allows you to define or modify the category database. These categories are represented as an event referencing tree.

  The graph below shows an example of the category tree: Racine News Sport Arts Operations for 1 category arb have on Media Weather Golf Football Films Television 0 tiJoLILeL uit i1VUVCLl uciLCyuLLC Ud11J 1 'a1JJLC É Change the name of a category in the tree E Delete a category

Field Type Description

  Category ID Integer Key Name String Category Name Parent ID Integer Parent Key 2.3.2.5. End User Administration It allows the management of the profile, and the services, as well as the management of the users (addition, deletion, modification).

  2.3.2.6. Content Provider Administration (CPAD) 2.3.2.6.1. Managing the CPAD content provider database allows you to define a new content provider or modify the information of existing content providers.

  The list of operations for administering the content provider database is as follows: E Add a new content provider to the database.

  E Modify the attributes (rights and characteristics) 20 of a content provider.

  Delete a content provider from the database. A content provider in ACTIVE state can not be removed, it must be set to INACTIVE.

  Show the list of content providers in the database according to the contract types and / or content provider statuses The table below provides an example of a description field for content providers.

Field type Description

  Name String Content Provider Name Contract String Contract with Manager (4 contract types) Start Date Date Contract Start Date dd / mm / yy hh / mm / ss am or mp End Date Date Contract End Date dd / mm / yy hh / mm / ss am or mp URL of the home page URL URL of the home page of the content provider Email of the administrator Email string of the content provider Webmaster Administrator login String Administrator's password Channel Administrator's phone Channel Status Channel Content provider status: The values are ON or OFF Time zone Channel G1T, GMT + 1 ...

  LogoURL Logo Url chain of the content provider Mail authorized Boolean true. Events arriving by mail from this content provider are allowed Form Boolean authorized true. If this content provider has access to the event record form Number of recorded events Integer Number of valid events recorded for this content provider 2.3.2.6.2. Content Provider Rule Database Management (CRAD) The content provider rules describe information about event collection requests. A single content provider may have one or more rules. CRAD allows you to perform the following tasks: E Add a rule to the Edit Rule Attributes Base.

É Delete a rule.

  É Display the Rule List The table below shows examples of rule description fields for content providers.

Field Type Description

  Vendor ID Integer Content Provider Content ID Confidence Level Integer Used to validate the step. Possible levels: Full, Medium, Low Query URL String Collect Allowed Boolean True If the URL can be collected Frequency of Collection String 2.3.2.7. Administration of links and states (TRIM) The sub-module of administration of links and states makes it possible to verify, at regular intervals, the validity of a link (URL) or the date of validity of an event. TRIM (trigger manager) is composed of a programming means to trigger the different treatments and a set of submodules performing the treatments.

  The administration operations are as follows: É Checking the status of links (event URL). É Check the status of the event (expiration date). 2.3.3. User Access and Overview The user interface allows various types of users to access the platform.

  2.3.3.1. End user The presentation of data can be adapted to the type of terminal that the user uses to access his calendar, his accounts, his interests. These types of terminals can be: mobile phone, PDA (personal assistant), ITV (interactive TV), workstation (intranet / extranet, Internet) ...

  The content provider may insert his logo on the screen.

  The operations accessible to end-users are: É personalization of the home page, authentication, authorization, * login and password filling interface * additional password for secure accesses, É system for managing subscriptions, * access to the interface of the subscription during the first contact, É system of management of its profile, * interface of adding or removing new services or categories, É base of the events in a simple and intuitive way, * navigation in the category tree * display the list of events in a category, * display the calendar of events, * search for an event by one or a combination of the following criteria: pre-established category, language, country of origin , 20. keywords, any other XML / DTD event description field, * event display, adding event to personal calendar, 25. adding category holding the event in the profile, sending an alert to a friend (mail and / or SMS and / or MMS), E managing personal notebooks, É Viewing news.

  Event presentation: For large screen terminals, the viewing screen is divided into three parts: É category tree (left), É calendar view or event (center), É list of events belonging to the current category ( to the right).

  The category tree can be represented as a profile.

  The tree can contain only the branches contained in the user's profile.

  The tree can also contain all the categories included in the set to which it subscribed.

  The tree can also contain all the categories corresponding to the maximum set accessible for the service provider concerned.

  This event part presents: É A view of titles, time and category of events.

É Long description.

  É The buttons needed to send the event to the personal calendar, sending mail or notification to a friend, adding to the profile or personal notification via SMS.

  This list contains events belonging to the current category.

  For telephone terminals, the viewing screen is not divided. The presentation of the information is more succinct and is displayed successively on the screen. The user will have to unwind the page more than on the big screens.

  É The category tree is a clickable category list at the top of the page. By clicking on a category (for example: Sport), it appears a list forming a succession of clickable titles of sports events of the day. By clicking on one of these events, (for example: Publication of a sports interview), the detailed presentation of this event appears with the time and the link to the pledge of the content provider.

  Several buttons are associated: o Backup in the calendar o Return information by SMS, e-mail or other means of communication o Request a reminder alert so as not to miss this event. This alert can be done by SMS, MMS, e-mail, voice messages or any other appropriate means, the calendar view is done in full screen. This uses the weeks and months visualization with points that appear for days when events occur.

  For the detailed view of the day view, a traditional one-day display with the indication of the times and the events programmed at these times is provided.

  É For weekly viewing, to take into account the usual forms of mobile phone screens, this is in the form of a vertical table and not a horizontal one. The days Monday, Tuesday ... are displayed vertically. Each day is assigned a non-exhaustive list of events in the database. To have access to all the events of the chosen day, the user must click on the link of the chosen day.

  At the bottom of each page, there are several buttons such as a back button on the home page, a subscription button to a newsletter, or a subscription button.

  The tables below show examples of various menus for the on-screen display of a mobile phone.

Table I

  Main Menu 1) News / Weather 2) Sports / Entertainment 3) Music / Radio / TV / Web 4) Company / Culture 5) Info / Practice 7) Trip / Travel 8) Outings 9) Couriers / Chat 10) Melodies / Images 11 ) Games / Humor 12) Purchasing 13) Bank / Stock Exchange If item 3 is selected, by clicking on the corresponding line, if the user is subscribed the following screen is shown in Table II below.

Table II

  Subscriber Your selection today On the Web Sport: Tour de France follow live Music: Album en Listen, Junior Senior ...

YOUR CALENDAR See Edit

ALL THE PROGRAMS

  1) Sport 2) Music 3) Film 4) Hobbies 5) Finance 6) Culture 7) Games 8) Miscellaneous YOUR SUBSCRIPTION See Change If the user is not subscribed, the screen is shown in Table III.

Table II1

  No Followers Today on the Web, Sport: Tour de France Follow Live Music: Album en Listen, Junior Senior ... Ciné: Johnny English, Interview Mr Bean !! To be notified of events by e-mail !! Subscribe ALL THE PROGRAMS Choose the theme you are interested in 1) Sport 2) Music 3) Film 4) Leisure 5) Finance 6) Culture 7) Games 8) Miscellaneous Finally, Table III shows an example screen with buttons and their meanings: Table III EUROSPORT.FR Tour de France Thursday 24 July 14h30 Live the 17th stage A Tour de France would no longer be quite the tour of France. Thursday the Great Loop will put his bags there for the 78th time. Flat as a cake, crossing the Landes offers McEwen or Zabel, martyred by Petacchi the first week, the opportunity to finally hang a victory. Follow this stage live! www.eurosport.fr/home/page/^ ..

---------------

-------------------

  Send to a friend Create your Email Alert Back List Results Request an alert .- Back Home Save, date, time, event in my calendar n

Claims (29)

  A method for providing terminals with information on future events, which information and / or events can be transmitted over a network, for example of IP type, characterized in that a platform (12) is provided for collect the information and broadcast it to mobile telephones (15) in formats adapted for mobile phones, the platform automatically selecting the events according to the capacity of the mobile phones subscribers.   2. Method according to claim 1, characterized in that the selection of events to be transmitted to mobile phones is performed taking into account at least one of the parameters included in the following group: the software available to the mobile phone, the size of screen, screen shape, memory capacity, bit rate, language, and available display colors.   3. Method according to claim 1 or 2, characterized in that the upcoming events are introduced in a calendar specific to these events, distinct from the usual schedule of appointments of the mobile phone.   4. Method according to claim 1 or 2, characterized in that a calendar of future events of the mobile phone is also used for appointments.   5. Method according to one of claims 1 to 4, characterized in that, for video events and / or audio and / or text that are directly accessible using mobile phones, the platform addresses these phones mobile software means allowing by a simple maneuver such as pressing a key or a touch on the screen, to access the video event and / or audio and / or text.   6. Method according to one of the preceding claims, characterized in that the platform comprises software means for addressing mobile phones, at the request of the latter, an alert prior to an event, a predetermined time before this event.   7. Method according to claim 6, characterized in that the alert is addressed by a message of the type SMS or MMS.   8. Method according to one of the preceding claims, characterized in that the platform comprises software means for establishing the billing services related to the events to which mobile phones access.   9. Method according to one of the preceding claims, characterized in that the platform comprises software means for forming groups of users having the same event selection profiles.   10. Method according to one of the preceding claims, characterized in that the platform comprises software means for addressing information on future events to other types of terminals such as computers, television receivers or television sets. personal assistants.   11. The method of claim 10, characterized in that the platform operates in server mode and includes software means for terminals to access content dedicated to them.   Method according to one of the preceding claims, characterized in that the future events are displayed and stored in the mobile telephones.   13. The method of claim 10, characterized in that the platform comprises software means for addressing to the same subscriber, information relating to future events on several terminals, the type of terminal being chosen according to dates or times preselected.   14.Plateform intended to provide terminals with information on future events that may be transmitted over a network, for example of IP type, characterized in that it comprises means for collecting information relating to future events and broadcasting them to mobile phones in formats adapted to the latter and means for automatically selecting events according to the capacity of the mobile telephones subscribers.   15.Platform according to claim 14, characterized in that it comprises means for selecting the events to be transmitted to the mobile phone taking into account at least one of the parameters included in the following group: software available to the phone mobile, the size of the screen, the shape of the screen, its memory capacity, its bit rate, the language and the available display colors.   16. Platform according to claim 15, characterized in that it comprises means for addressing to the mobile phone software means for video and / or audio events and / or text that are directly accessible using the mobile phones, by a simple maneuver such as pressing a key or touch on the screen to access the video event and / or audio and / or text.   17.Platform according to one of claims 14 to 16, characterized in that it comprises software means for addressing mobile phones, at the request of the latter, an alert prior to an event, a predetermined time before this event .   18. Platform according to claim 17, characterized in that it comprises means for addressing the alert by a message type SMS or MMS.   19. Platform according to one of claims 14 to 18, characterized in that it comprises software means for establishing the billing services related to the events to which mobile phones access.   20. Platform according to one of claims 14 to 19, characterized in that it comprises software means for forming groups of users having the same event selection profiles.   21.Platform according to one of claims 14 to 20, characterized in that it comprises software means for addressing information on future events to other types of terminals such as computers, television receivers or personal assistants.   22. Platform according to one of claims 14 to 21, characterized in that it is of the server type and includes software means for terminals to access content dedicated to them.   23. Platform according to claim 21, characterized in that it comprises software means for addressing to the same subscriber information relating to future events on several terminals, the type of terminal being chosen according to dates or times preselected .   24.Mobile telephone characterized in that it comprises means for connecting to a platform for collecting information on future events that can be transmitted by a network, for example of the IP type, and means for receiving messages. data from this platform corresponding to future events, these data being in formats adapted to the capacity of the mobile phone.   25.Mobile phone according to claim 24, characterized in that it comprises means for future events to be introduced in a calendar specific to these events, separate from the usual schedule of appointments.   26.Mobile phone according to claim 24, characterized in that it comprises a calendar of events to come which is also used for appointments.   27. Mobile telephone according to one of claims 24 to 26, characterized in that it comprises means for receiving from the platform a software means for video and / or audio events and / or text that are directly accessible using the mobile phone, by a simple maneuver such as pressing a key or a contact on the screen, to access the video event and / or audio and / or text.   28. Mobile telephone according to one of claims 24 to 27, characterized in that it comprises means for addressing a request to the platform to obtain an alert prior to an event, a predetermined time before this event, and ways to receive this alert.   29. Mobile telephone according to claim 28, characterized in that it comprises means for receiving the alert by a message of the SMS or MMS type.