FR2930060A1 - Application or service i.e. Goojet service, creating, organizing, delivering, utilizing and/or accessing method for e.g. mobile phone, involves setting application, if application derived from web is selected - Google Patents

Abstract

The method involves displaying a representation of nodes or descent leaf of node or root of a tree on a screen of a mobile terminal e.g. telephone, and selecting one of the representations on the terminal. An indication of node or leaf corresponding to the selected representation is communicated to the server by the terminal. Identifiers of nodes or descent leaf of the selected node are supplied to the terminal by the server, and the supply, selection and communication operations are repeated, when the node is selected. An application is set, if application derived from a web is selected. Independent claims are also included for the following: (1) a device for creating, organizing, delivering, utilizing and/or accessing an application (2) a computer program comprising instruction for implementing a method for creating, organizing, delivering, utilizing and/or accessing an application (3) a readable information support for implementing a method for creating, organizing, delivering, utilizing and/or accessing an application.

Description

METHOD AND DEVICE FOR CREATING, ORGANIZING, DELIVERING, OPERATING AND / OR ACCESSING SERVICES

The present invention relates to a method and a device for creating, organizing, delivering, operating and / or accessing services. Many systems are known to enable the creation, organization, delivery, operation and access to services. However, these systems are not suitable for communicating mobile terminals and are, therefore, very little used. Three approaches co-exist to date for access to Internet services via a communicating mobile terminal: the applications embedded on the telephones, dedicated to a given single remote service, and which communicate with said service via a proprietary protocol in a so-called heavy client model; 20 - the native browsers embedded in the telephones and which make it possible to access the Internet sites via their representation wml (acronyre of Wireless Markup Language for wireless markup language), WAP (acronym for wireless Application Protocol for wireless application protocol ), html (acronym for HyperText Markup Language for Hypertext Markup Language) or xhtml (an acronym for Extensible 25 HyperText Markup Language for extensible hypertext markup language) and - specialized browsers, conceptually similar to native browsers in that they are not not dedicated to a single service and in that it interprets on the phone a representation in markup language of the remote service or services. The present invention relates more particularly to the third category. The first category is a so-called closed and static system, which does not allow third parties to develop compatible content or services, and requires the user to install and learn as many dedicated applications as he wants to use services. Conversely, the system object of the present invention is open: the mobile client can interpret a non-predefined number of new services, new services can be used, possibly created by third parties, without requiring change or new installation on the client part.

The second category is open but not adapted to mobility: it simply reduces the display format to the size of the screen. Moreover, these native browsers do not make it possible to implement optimized management of the communication protocol, such as intelligent management of cache and prefetch (for pre-loading or advance download) according to the semantics of the services and the profile. behavioral of the user. Finally, these native browsers can not use the basic functions of the phone, such as calling or sending SMS (acronym for short message system for short message system). The present invention offers the openness and genericity of the second category ruais, in addition, allows to extract and to present in a specialized way for the mobility the information of a service of the web (known under its English name of web) , by filtering. It also enables optimized and relevant management of the protocol depending on the services and the user, and an integrated use of the basic functions of the telephone (calls, SMS).

The third category, to which belongs the subject of the present invention, comprises several existing solutions. However, the present invention has, with respect to these solutions, the following advantages: a data representation model that allows a tree and recursive organization of the service space in which the new system makes it possible to navigate; this tree is scalable; the user can navigate step by step in the space thus organized, starting with access to his own and personal space, as he has defined for himself, then accessing, step by step, to the public parties (or for which an explicit nominative right of access has been given) spaces of other users. The user thus benefits from a navigation in a clean space, organized according to his own needs, but not closed and not limited to his meadow; In addition, it benefits from a navigation that passes from local services to remote services in a transparent way: it is the notion of extended menu (local + distant) which allows to distribute and manage mobile applications remotely; - a platform opening that allows third parties to create, distribute and promote new services in the managed services space, without having to develop code; - a social aspect in the platform, which measures and records all uses of all services by all users and derives profiles; and which also makes it possible to use the platform to exchange services and data between users; - finally, a dual mode aspect: each service defined on this system corresponds to two representations, one per mode of access, mobile phone or computer; the representation is optimized for the access mode, not only in terms of layout (taking into account screen sizes) but especially in semantic terms (only the important information in a mobile situation is transmitted to the mobile phone, then that the representation on the computer is enriched semantically and functionally). The present invention aims to present its advantages and therefore to overcome the corresponding drawbacks of the prior art. For this purpose, according to a first aspect, the present invention relates to a method of creation, organization, delivery, operation and / or access to applications, characterized in that it comprises a step of implementation. correspondence of applications with a tree, at least two said applications from the web and, iteratively: - a step of displaying, on the screen of a communicating mobile terminal, representations of nodes or falling leaves of the same node or root of the tree, - a step of selection, on said mobile terminal, of one of said displayed representations, - a step of communication, by the mobile terminal to the server, an indication of the node or of the sheet corresponding to the selected representation, - if a node has been selected, a step of supplying, by the server to the mobile terminal, identifiers of nodes or falling leaves of the selected node and an iteration steps of selection, communication and supply and - if an application from the web is selected, a launching step of this application. The present invention thus meets the needs of mobility, which requires intelligent extraction of a subset of data, within a rich and complete site, which are relevant in a situation of mobility. According to particular characteristics, if the number of representations of nodes or falling leaves of the same node or the root of the tree is less than or equal to nine, during the display step, these representations are displayed. in three lines of three available positions and, during the selection step, a keyboard having at least three lines of at least three keys corresponding, by homothety, to the positions each of the nine keys allowing the selection is implemented. of the representation in the corresponding position. The selection of a representation is thus intuitive and fast. According to particular features, if the number of leaves or nodes descending from the same node or the root is greater than nine, during the display step, a number less than or equal to seven representations of nodes is displayed. or leaves and at least two representations of movements for scrolling the representations of knots or sheets displayed. According to particular features, during the selection step, a line of three additional keys is used to select - help in the form of text superimposed on the representations, these representations taking a graphic form. to access the home page, that is to say the nodes and sheets linked to the root of the tree, and to access the representations displayed before the last step of selecting a node or of a leaf. Thus, by having, at each level of the tree, at most a number of nodes or sheets corresponding to a number of keypad keys of a mobile phone, have allowed the user to navigate with a simple pressure on a touch associated with a node or sheet and reach the computer application that interests him. According to particular characteristics, during the selection step, a support of a duration greater than a predetermined duration causes the display of a contextual menu comprising at least assistance with the use of the node or the corresponding sheet. According to particular features, prior to said iterations, in response to the initial navigation request, the server provides node or leaf identifiers, the first selection step being performed on the nodes or leaves provided by the server in response to the request. initial navigation. According to particular characteristics, before said iterations, the mobile displays identifiers of nodes or sheets stored in memory by said mobile. According to particular features, at least one said application is such that once started, at least one new iteration is performed. Said application therefore has the same ease of navigation as that related to the tree. According to particular characteristics, during each supply step, the server provides, in advance, at least the matrices of nodes or sheets to be displayed after each possible selection. Thanks to these provisions, one pre-loads at least one tree level in advance and saves time for navigation. According to particular features, during the step of mapping applications to a tree, services are mapped to said tree and each leaf corresponds to the content of a service or application.

According to particular features, during the mapping step, hyperlinks of pages are matched with nodes of the tree. According to particular features, during the mapping step, page contents are mapped to tree sheets. These characteristics make it possible not to wait for the pages to be loaded before selecting a link present in this page. These characteristics work all the better that the site with these pages is a partner site adding, in the pages, elements for performing a graphical representation of each link. According to particular features, the method as briefly described above comprises a step of accessing the server from a second terminal, a display step, on a portion of a page displayed on the screen of said second terminal, representations as they would appear during the iterations, on a screen of the mobile terminal. By simulating, on the screen of a computer, access via a mobile phone, the user is allowed to set the usage from a mobile phone, through functions not accessible from the phone mobile. In addition, at least each application or service that can be implemented with a mobile phone can be implemented with a computer. According to particular characteristics, during the tree creation step, the user implements the second terminal and slides or copy-pastes representations in the portion of the displayed page simulating the representations as they would appear. on the screen of the mobile terminal to perform the mapping step. According to particular characteristics, during the selection step, if the user presses on a first predetermined keyboard key different from the keys 1 to 9, the display on the screen of the communicating mobile terminal goes back and displays what which was displayed an iterative cycle earlier.

According to particular characteristics, during the selection step, if the user presses a second predetermined keyboard key different from the keys 1 to 9, the display on the screen of the communicating mobile terminal returns to the first iteration, According to particular characteristics, during the selection step, if the user presses a third predetermined keyboard key different from the keys 1 to 9, the display on the screen of the communicating mobile terminal includes explicit titles of the nodes. and leaves displayed.

According to particular characteristics, during the selection step, if the user makes a long press on a keyboard key among the keys 1 to 9, it opens contextual help related to the node or the sheet corresponding to said key on which a long press is made.

Thanks to each of these four last provisions, browsing the tree is very easy. According to particular characteristics, at least some of the computer applications corresponding to the leaves of the tree structure are among the following: - download and / or display a text, - download and / or display a photo, - download and / or play (streaming ) a music file, - download and / or play (streaming) a video file, - trigger a phone call (with 1 or more people), - trigger the sending of SMS (acronym for short message system for system 15 messages short) or MMS (acronym for multimedia message system for multimedia message system), - trigger the sending of electronic messages (mails), - choose in one or more lists and transmit the choice to the server, - fill a form or a form (in English template) then transmit it to the server 20 and - invoke a predefined web service. Thus, the main actions requested on the web can be launched by the navigation described above. According to particular features, the method as briefly described above comprises a step of personalization, by the user of the tree implemented in response to navigation requests from his communicating mobile terminal. Thus, the user can define, for example by an access to the server over the Internet, possibly from a personal computer, the tree in which it will navigate from its communicating mobile terminal. According to particular features, the method as briefly described above comprises a step of defining an explicit user profile, by said user, the behavior of at least one computer application associated with a leaf of the tree structure. depending on the explicit profile of the user. According to a second aspect, the present invention is directed to a device for creating, organizing, delivering, operating and / or accessing applications, characterized in that it comprises a means for mapping the data. applications with a tree, at least two said applications from the web and: - a display means on the screen of a communicating mobile terminal. of representations of nodes or falling leaves of the same node or of the root of the tree, - means of selection, on said mobile terminal, of one of said displayed representations, - means of communication, by the mobile terminal at the server, an indication of the node or sheet corresponding to the selected representation, - means for supplying, by the server to the mobile terminal, identifiers of nodes or falling leaves of the selected node if a node has been selected so that the display, selection and communication means perform a new iteration and a means for launching an application from the web if its representation is selected. According to a third aspect, the present invention is directed to a computer program, characterized in that it comprises instructions executable by a computer for implementing the method that is the subject of the present invention, as briefly described above. According to a fourth aspect, the present invention is directed to a computer-readable information medium comprising instructions executable by a computer for implementing the method of the present invention as briefly described above. The advantages, aims and particular characteristics of this device, of this computer program and of this information medium being similar to those of the method which is the subject of the present invention, as briefly described above, are not recalled here. . Other advantages, aims and features will emerge from the following description given for explanatory and non-limiting purposes with reference to the accompanying drawings, in which: FIG. 1 represents, in the form of a logic diagram, steps of a communication implemented in at least one particular embodiment of the method which is the subject of the present invention; FIG. 2 represents, in the form of a logic diagram, steps implemented in a particular embodiment of the method which is the subject of the present invention; FIGS. 3 and 4 show, schematically, user interfaces implemented on a mobile user terminal in various embodiments of the method that is the subject of the present invention; FIGS. 5 and 6 show, schematically, interfaces users implemented, on a computer screen, in different embodiments of the method that is the subject of the present invention, FIG. FIG. 7 schematically represents a unified communication infrastructure implemented in particular embodiments of the present invention; FIG. 8 schematically represents a gateway server for implementing a browser object of one of the Aspects of the present invention - Figure 9 illustrates, in the form of a logic diagram, steps implemented in a routing server, according to one aspect of the present invention, -. FIG. 10 illustrates, in the form of a logic diagram, the steps implemented in a conference application and -. Figure 11 illustrates, in the form of a logic diagram, the steps implemented in an automatic creation of computer application. Throughout the description, we use the following definitions: - • Application, a program interacting with a context of execution, Service, the response to the request of a user, regardless of the context, for example to obtain a taxi, to reserve a table . We observe that a web service (in French service of the web) is an application. It is also observed that the implementation of the service generally requires that of applications and - mobile, a communicating mobile terminal, for example a mobile phone, a personal digital assistant (PDA, acronym for personal digital assistant) or a smartphone that brings together mobile phone functions and personal digital assistant functions. The hardware structure supporting the services implemented by the present invention is based on a distributed architecture comprising: a support part (backend), residing on a set of servers, jointly called, in the following description, the server part accessible, in terms of its configuration, via the Internet (see Figures 5 and 6), and - so-called mobile parts, residing on communicating mobile terminals, accessing the server via conventional data links offered by the telephone operators mobile and / or wireless local links (eg, Bluetooth or WiFi, registered trademarks). A new communication protocol or language, defined for the implementation of the present invention, named GML (acronym for Goojet Markup Language for Goojet Markup Language, Goojet being a registered trademark) and implementing tags, manages the interactions between the server and the moving parts. This language is described with reference to FIG.

It is noted that the term GML refers to the concept of a tree service structure and can be embodied by both proprietary XML representations (Goojet) and standard HTML representations. This is the structure approach.

In addition to their distributed structure, these services are also original in their behavior which differs from the state-of-the-art of existing mobile services by the following characteristics: - they are centered on the user (in English user-centric), c that is, the behavior and presentation of these services can adapt to each user, as opposed to generic behavior, they have a ubiquity, that is, these services are designed, from their birth, to be accessed both by a mobile (access said mobile) than by a computer connected to the Internet (access said web), - they are community: these services allow several users to 15 share, both reading and in writing, common data, whatever their means of access (mobile or web), and - they implement a navigable space: these services are organized between them by a referencing mechanism that allows the x users to navigate all of these services in successive steps from a mobile. The platform described here is heterogeneous in that it makes it possible to organize, access and use services of different types: simple services for accessing distant information (text, rich text, photo, video, music, RSS feeds, web page, ...), - services created by the platform managing company, 25 - mediation services to third party web services, - interactive services and transactional, based on an end-to-end, state-to-state transaction management system, between the users and the remote services and - services created by the users themselves, by aggregating and configuring unitary bricks into complex and complex wholes. customized, or by developing original services according to the rules and interfaces provided by the company owning the platform. The innovations offered by the implementation of the present invention cover several fields: the structure of the distributed objects and the communication protocol (called GML and described in an annexed paragraph) which together enable the implementation of services or applications object of the present invention, - the structure that allows to organize, manage and operate all of these services, this set being called the service space and includes all the nodes and services of the and - some services object of the present invention.

The infrastructure is based on a human-machine interface remote on mobile, a matrix browser representing three times three icons, a menu of the web (in English Web) and a recursive structure. One of the foundations of the architecture is the intelligent distribution of the work (treatments, data, presentations) between the mobile and the server: each service is divided into: - a presentation part on user interfaces, whose appearance and behavior are modeled in the GML language, and - a heavy part, on the server, comprising data, data processing and interfaces with other components (external web services, other users, etc.). The heaviest part thus resides on the server and is accessible via the Internet, on the one hand, and via the mobile, on the other hand. Thanks to this model, the mobile is relieved of heavy treatments. In addition, each access to a given service is adapted to the user. This distribution of loads and this synchronization on demand between the web (in English web) and the mobile via the GML protocol is, in a way, an extrapolation adapted to mobiles, the thin client model with a web browser. The mobile runtime can thus be considered as a new type of browser, specifically adapted to the structure of the services object of the present invention and the organization of their space. FIG. 1 shows a start-up step 100 of the service implementing the present invention, for example by selecting an application maintained by the mobile device used. At the time of opening the application implementing the objects served by the present invention, the screen of the mobile: - either displays a menu in the format of the 3x3 matrix, called local home menu, present in the phone, - either, which is assumed in the following description of Figure 1, sends a request to the server that manages the navigation, to ask, in GML language, the home page to display for the user considered , in particular when it has been preliminarily identified), during step 105. In this second case, during step 110, the server provides the mobile with code that describes at least one matrix of icons, in GML language. Note that the request sent by the mobile during step 105 allows the server to identify the user or at least part of his profile. The presentation part is sent, on request from the mobile, from the server to the mobile. This presentation part is interpreted immediately by this mobile, in which there is an interpretation environment (referenced under the mobile runtime code) of the GML: during a step 115, the mobile traverses the code received during the step 110 to extract a template, or page, to display. During a step 120, the mobile determines, from an identifier of the user or his mobile, the model to be displayed on the screen of the mobile, as a personal home page of the user. This homepage is formed and parameterized by the user, as shown with reference to FIGS. 5 and 6, preferably by access, with a computer, to a server of the dedicated web (web). During a step 125, the mobile displays the model found, as explained with reference to FIGS. 3 and 4, and puts in memory by pre-loading (prefetch) models that can be called from the home page of the user. During a step 130, the mobile waits and detects the selection of a key on its keyboard. Upon detection of the selection of a key on the mobile keyboard, the mobile deals with the meaning of the selected key or command during one of the steps 140 to 150. If the selected key is one of the number keys between 1 and 9, during a step 140, the mobile treats the contents of the tree corresponding to this key and, if the selected icon corresponds to an application not implementing a template, launches this application. On the other hand, if the selected key concerns a new node of the tree or a model of reception or navigation in an application called fruit of the tree, a new model is selected and one goes to step 155. If the selected key is 0, the mobile returns to the first model, corresponding to the personal reception of the user, during a step 150.

If the selected key is #, the mobile returns to the previous model, during a step 145. If two keys are selected simultaneously, whose key # and a number i represented by the number displayed on one of the keys between 1 and 9, step 145 is deleted from the previous model navigation history (s). For example, if we arrived at the fourth model coming from the second model, the command # and 2 allows to remove from the browsing history the last two models displayed, that is to say to return to the second displayed. Thus the server is able to manage a browsing history for the user. In the case where one of the icons displayed (see Figure 3 or 4) corresponds to a variable assignment, or parameter setting, the management of the variables makes it possible to determine a context or a perimeter of operation of the mobile. This context defines an environment of validity of variables during navigation and associated variables as well as their default value. For this purpose, the use of a command called as: var: value, which comprises the successive selection of the key of the mobile keyboard associated with the variable assignment icon and a key representing a var value represented by the value of a key, between 1 and 9, it is possible to set the variable var to the value value. Thus, even within the GML language (and without implementing a new client-side language), we are able to interpret a command and perform a simple operation. The value of the variable can be retrieved inside the language by using the signs {and}. The value of var is thus represented by {var}. Following one of the steps 140 to 150, the mobile determines, during a step 155, whether it has, in cache, the selected model, thanks to the pre-loading performed during the step If yes, return to step 125 to display the selected template and pre-load the templates to which the selected template can proceed. Otherwise, we return to step 105 to request the selected model from the server. FIG. 2 represents steps implemented in one embodiment of the method that is the subject of the present invention. During a step 205, applications are mapped to a tree, at least one said application from the web. This mapping is done in three steps: on the one hand, step 206, services are created, the creator of the service can be either a partner, the service manager objects of the present invention, or a user, or automatically, from an email (or email) that can cause the creation of an application supporting such a service. This creation is generally done from generic applications (or metagoojets), that is to say generic applications whose parameters are not assigned any value and which, once 25 parameterized, become services (or Goojet). ). For example, a generic meteorological application called weather uses as a parameter a place value and the reception of an email with the weather title Toulouse assigns the value Toulouse to the place parameter, - secondly, step 207, the user copy / paste (drag and drop) icons or 30 available graphics representing the services created, for example in drop-down menus or through a search or catalog dialog box in a 3 x 3 matrix tree , as explained with reference to FIG. 5 and finally, during a step 208, the user can associate service icons with icons of other users (friends or contacts) in order to offer them these services. reciprocally, copying icons proposed by friends or contacts, as shown in Figure 6.

Following step 208, the applications supporting the services and the trees are kept by the server. The user then has a personal navigation space which he can access either by the use of a mobile or by the use of a terminal connected to the Internet.

During a step 210, the user selects the application implementing the present invention. It is assumed here that he uses a mobile. According to the embodiments, the mobile then sends a request to the server to ask for the home page in force for this user, or the last homepage implemented is immediately displayed. It is assumed here that the first variant is implemented. Also, during a step 215, the server, connected to an application database, receives a navigation request from the communicating mobile terminal. During a step 220, the server provides the mobile code written in GML. which describes at least one matrix of icons. Among these matrices, one is a home screen 15 and is immediately displayed by the mobile. During a step 225, the user performs, with his mobile, a step of selecting one of said nodes or one of said sheets. This selection is made by pressing one of the nine keys of the keyboard from 1 to 9, homothetically with what is displayed on the screen. For example, the top-left icon is selected by pressing the 1 key. During a step 230, the mobile communicates to the server, an identifier of the selected node or sheet. During a step 235, the server determines whether a node has been selected. If so, the server returns to step 220 and supplies the mobile with node identifiers or falling leaves of the selected node and iteratively performs the selected selection, communication and icon type determination steps. If the result of step 235 is negative, during a step 240 the server determines whether an application from the canvas has been selected. If so, the server launches this selected application during a step 245. If not, during a step 250, the application maintained by the mobile that has been selected is implemented. In the embodiment described here, at least one such application implements as user interface, the same 3x3 matrix layout associated with 9 keys of the mobile keyboard. A nine-way navigation implemented in particular embodiments of the method and device of the present invention will be described hereinafter. As illustrated with reference to FIGS. 3 and 4, the user sees, on the screen of his mobile, a succession of matrix icons and can very easily select one of the branches of the tree and then a leaf or a fruit (application using the mobile browser defined below) to terminate the tree. A mobile browser is any browser dedicated to the service space, for example in the form of a 3x3 matrix. This browser can be found on any type of media, page of the web, or terminals. This nine-key navigation is a navigation solution that allows a user to use the keys 1-9 of a keypad, for example a mobile phone, to interact with an application displaying, on the screen vis-à-vis -vis the keyboard, nine representations of functions, for example in graphical form and, more particularly, in the form of icons. The nine-key navigation system is generic and can be used on any device, physical or logical, such as a mobile phone or a widget embedded in a website (widgets). The description which is made here, for the sake of simplicity, assumes that the home device of its navigation system is a mobile phone, called, subsequently mobile. Indeed, a mobile phone is particularly adapted to this mechanism because of its small screen, which implies an adapted management of the space and the navigation, on the one hand, and because of the presence, on its keyboard, of keys numbered from 1 to 9, organized according to a 3x 3 matrix, on the other hand). The purpose of the navigation by nine keys and to use the numbered keys 1 20 to 9 of the mobile claver to, on the one hand, navigate in a space of local or distant services (concept of extended menu) and, on the other hand, to use the services thus achieved. This navigation serves not only a navigation interface but also an interface to use certain applications, called fruits, at the end of the tree. The allocation between the physical keys of the mobile and the interface is done using a 3x3 matrix, as follows: 1 2 3 4 5 6 7 8 9 $ 30 Among these matrices, one constitutes a home screen and is immediately displayed by the mobile, in the course of step 125. In the case where at most nine icons are to be displayed, this screen is constructed in the form of a 3x3 matrix (three rows of three columns) corresponding, by homothety, to the nine numbers 1 to 9 in the keyboard matrix of the mobile. At each instant is displayed, 35 on the mobile screen of the user, a 3x3 matrix with nine data, in the form of nine icons.

When more than nine icons are to be displayed, preferentially, only six of them are displayed, for example on the upper part of the screen (two lines of three icons) and the following lines are affected in the following way: <= 8 = * * 0 #t The arrows corresponding to the 7 and 9 keys make it possible to scroll through the icons displayed in the first two lines, among all the icons to be displayed on the page considered. Thus, when a selected node has more than 9 icons, only the six positions of the two highest lines (2x3) are assigned to icons and the three icons in the third line are used to scroll the icons on the first two lines, the 7 being associated with an arrow to the left (previous) and the 9 being associated with an arrow to the right (next). The central key of the third line of icons, corresponding to the 8 of the keyboard, is not used for navigation and remains available for features chosen by the application. This type of navigation node corresponds to a representation of two lines of icons on a virtual cylinder and makes it possible to manufacture a navigation tree whose nodes comprises an unlimited number of options (icons), while remaining in the same paradigm one-finger navigation. The system automatically adapts the display format of a node (3x3 or virtual cylinder) when adding or retracting options descending from the same node, depending on whether the number is less than or equal to nine or greater than nine . In the case of mobile phones, the navigation is also based on the keys *, 0 and #, respectively assigned to the following navigation functions: * provides access to help in the form of text superimposed on the icons, these 25 texts, Very short, briefly explaining the content represented by each icon - 0 allows you to go directly to the current home page for the user and # allows direct access to the previous page. Selecting an icon leads to one of the following actions - in the case where the icon that is selected by pressing a key on the keyboard is a navigation node in the service tree, another page is opened. matrix of 3x3 icons; the user thus navigating to a level of greater depth, where, recursively, he finds nine icons or - invocation of a terminal action: the selected icon corresponds to a sheet of the service tree; the user is at the end of his navigation with regard to the path followed and invokes the service. Two types of terminal actions exist: -. atomic actions: the navigation infrastructure has a certain number of possible atomic terminal actions, which together make it possible to construct a service, by successive aggregation and by hierarchical and recursive organization. These atomic terminal actions include (non-limiting list): - download and / or display text, - download and / or display a photo, - download and / or play (streaming) a music file, - download and / or play ( streaming) a video file, - trigger a phone call (with 1 or more people), - trigger the sending of SMS (short message system acronym for short message system) or MMS (acronym for multimedia message system for system of short messages) multimedia messages), - trigger the sending of electronic messages (mails), - choose from one or more lists and transmit the choice to the server, - fill a form or a form (in English template) by entering textual or numerical data, then send it to the server and - invoke a predefined web service. - applications: an application is a set of processes and actions that run either on the mobile or on the server, possibly interactively with the user, at the end of navigation, but which require a level of sophistication more higher than predefined atomic actions that must be performed in the same context. An application can thus consist of several successive choices, of several information fills, and of several transactions with the server, but while remaining in leaf of the tree, that is to say remaining in a unitary context , without additional navigation in the tree. An application is therefore distinguished by its contextual unity (in the sense of navigation) and by its complexity, as opposed to atomic action. Note that an application can be created by aggregation of several atomic actions in the same navigation context as described above, that is to say with pages comprising, at most nine icons associated with the nine keys of the keyboard 1 to 9. Such an application is therefore fully modeled by GML. It is also called, in the description, a fruit of the tree. An application, still in navigation sheet, can also invoke a clean mobile executable. Such applications do not render their service by interpretation of GML, but use GML and the recursive tree of services to be made accessible. As such, the structure implemented in the implementation of the present invention is, at the same time, a set of services interpreted by GML and an organization structure, which can comprise heterogeneous services (pure GML, or comprising a part executable on the mobile). It is important to note that the nine-key navigation solution allows you to invoke native applications and services (such as, for example, in the phone, the address book, the calling function, a game installed by the manufacturer phone, etc.) and remote applications / services, residing on the web and thus requiring communication and interaction with external systems on the phone. The user therefore uses the same navigation system for all services and the location of the application is no longer important for the user. It is an extended menu concept, where the same paradigm of navigation and usage extends from a local navigation to a distant navigation, but also from a navigation to a terminal action within a application. The data model for the nine-key navigation mechanism thus breaks the boundaries between local and remote and between navigation and execution, allowing a unified and simplified view of usage.

Preferably, a long press (of a duration greater than a time limit, possibly configurable) on one of the nine keys, gives access to a contextual menu with help on the content associated with the icon concerned by the support and options, such as sending the service to a friend or contact. The system makes the resolution by addressing shortcuts during navigation, and can position itself on the target of a navigation without going through the intermediate steps (navigation node): for example, if a service is on the Rth position of the Qth position of the Pth position of the current page, the basic navigation asks to press P, then Q when the corresponding page (node) has been displayed, then R, etc. The system offers a shortcut mechanism that makes it possible to press P, Q and R quickly, actions following which the system will directly seek the required final position, thus saving the intermediate steps. These are the shortcuts by compression. The system also allows to assign explicit access shortcuts for the services accessible by navigation by nine keys: when organizing a navigable space by the nine-way navigation system, it is possible to specify to the system the desired shortcut, and the system will place the service at the corresponding location, if available, in the tree. For example, 63836 can be entered in the system for a weather service (at the touch of a cell, 63836 may be the letters of the word weather). This feature allows the user to access a service directly without knowing or in the structure is the service; these are the mnemonic shortcuts.

As for the contents of the menus, they are dynamic. Indeed, the structure of the navigation tree is built and stored on the server side. This allows the user to access his service tree from several types of clients, such as a web browser on a desktop computer: the structure is unique but its access is shared and multimodal. If the user makes a change to his service space using for example a website, he can immediately see the changes on his mobile phone. To help in this modification (or editing) a window represents a 3x3 matrix similar to that which will be displayed on the screen of the mobile phone. Once the nine-key navigation solution is installed, users can add and remove services for their phone, without having to change their phone configuration or install additional software. The navigation system allows you to send several pages at a time to the phone. With a cache system on the phone, the system does not need to contact the server when the user is navigating between pages. A navigation on remote services can therefore be temporarily local on the phone, thus reducing the latency of access to services. The system marks the dynamic information that must be refreshed during a cache navigation. In addition, when defining a service or a space (set of navigation nodes and services forming a coherent whole, conceptually similar to a thematic portal), it is possible to mark several nodes or unit services as correlated. to force the load into a single atomic query on the phone. The data set thus loaded when accessing the entry point in this service or space is therefore heavier than the simple data corresponding to this entry point, but the correlation has been established to then enable local navigation. (cached) without additional request to the server, thus decreasing the overall latency of the navigation through this service or this space. The system keeps a complete log of any user navigation through the tree managed by this nine-key navigation process. This log is used to dynamically define the profile of each user according to their navigation. This profile is then displayed by the system for third-party and external uses, such as for example the targeted sending of messages to certain users according to their profile. But this profile profile calculation mechanism is also used internally and intrinsically to the nine-way navigation method, by means of a prefetching algorithm based on the navigation profile: statistical navigation paths are calculated for each user. and the nodes or successive services of the most frequent statistical navigation paths are dynamically correlated for each user, so that the entry in such a path by a user triggers the atomic loading at N level navigation level on the said path . The object is once again to reduce the number of requests between the browser and the server and thus reduce the overall latency. The number N of level is calculated according to the frequency of the path and the memory available on the cache. The frequency of the path is the main datum of the profile (for example, the profile determines that the Lambda user, when accessing the node N1, then goes in X% of the cases to access the node or service N2, then in Y% of the case to access node N3, etc. Such a calculation leads to the definition of a statistical weight, also called frequency, for each node of the navigation path - in this case the weight of node N3 is X * Y from node N1 for the Lambda user). The size of the cache available, it is known thanks to the static profile of the browser (depending on the mobile it uses to navigate, whose characteristics are known in a database called static profiles). The prefetching algorithm, based on the profile, correlates dynamically (that is to say that this correlation decision is recalculated after each navigation) for the user, all the nodes of the navigation path whose frequency is greater than a threshold (for example 80%, system adjustment variable) and as long as the cache memory allows. This correlation decision on a navigation profile can then be refined by two additional algorithms. The first, called super profile is relative to a group profile. To simplify calculations and make the system more efficient overall, the profile system also creates group navigation schemes, making it possible to proactively prefetch for a user who has not yet traveled a certain path: the profiles of all users are compared with each other and behavior patterns are defined. A super profile, for a given path, is a navigation profile that corresponds, within the limit of a variable adjustment of the system, to the navigation profile of several users. These users are then grouped together based on the homogeneity of their navigation in a number of paths. When a user is considered to belong to a super profile, based on his browsing behavior on N paths, and he will navigate for the first time on an N + 1 th path, and if there is a typical profile of navigation for this path N + 1 in the super profile to which this user adheres, then the system will pro-actively correlate the elements of said path for said user, depending on this super profile, although this user has never navigated on this path. The second additional algorithm concerns a custom correlation: the user has the possibility to force prefetching, that is to say the correlation of navigation path elements, during the management of his navigation tree. The concept is similar to that of using caches and correlations, except that, previously, the correlation concerned a set of elements constituting, together, an all homogeneous and thus correlated generically for all these users, whereas here the user can decide to correlate, for him only, elements of his tree which do not, a priori, use correlation. It is only the customization of its navigation paths and not the aggregation of elements in a homogeneous whole.

Intelligent cache management and different prefetching algorithms are mainly motivated by reducing the number of requests between the browser and the server, in order to improve the overall user experience (the latency is lower because the navigation is as local as possible). Another important motivation for cached local browsing is the disconnected mode: the fraction of the tree that is loaded in cache remains accessible to the nine-way navigation process even in the event of absence, voluntary or involuntary, of connection between the browser and the server. The method of navigation clearly indicates to the browser that some data is potentially obsolete but allows their use locally without connection. The data is then refreshed on demand during the next connected mode navigation. This method, used in conjunction with the custom correlation method described above, makes it possible, among other things, to load into memory, in a single request, a set of data explicitly identified and organized in the global tree as a set of data, a priori heterogeneous and dispersed, and to keep them in memory. In case of disconnection, the part of the tree that was not loaded into memory is no longer accessible by the nine-way navigation method (until the next connection) but the cached data remains accessible via the same navigation and use mechanism. The structure that organizes, manages and operates all services is called a space. When a user defines services or applications or space or part of a space, he can indicate the desired audience for these elements, among the following choices: - public: everyone has access and therefore all the users of the platform form can increase their own service space by referring, in one of the nodes 30 or leaf of their tree, to this element; - private: this service can only be navigated and used by the user himself, - Community: this service can be referenced (and thus sailed and used) by one or more designated user groups by the creator of the service. In addition to the sharing capacity, this possibility gives a significant dynamic characteristic to the service space and its navigation: a user can refer, in his own space, to a public part of the space of another user, which can be enriched, the other user adding branches or services that are also added to the navigable space of the first user. A user can, in turn, refer to a public or community part of a third, etc. From one to another, spaces can thus have an intersection or inter-pollenize, allowing a navigation by successive affinities in a living space, dynamic and open, although still controlled and always user-centric. With regard to the promotion of the platform, as we have seen, the space of a user is a tree structure, with its public or private branches, chosen and / or defined by the user via a web interface . This tree becomes navigable via his mobile and leads, in his sheets, to a collection of services. The fact that some of these branches are references to other public branches creates a first level of dynamism in the user's space structure, because the public branches that it refers to can evolve. When browsing a tree, using the nine-key navigation method, the user can, at any time, mark a service (or navigation node) visited as preferred (bookmark concept). The reference of an element thus marked will be duplicated, by the system, in a predefined branch of the tree (branch called preferences defined in the administration area, itself present, for example, in icon 1 in the page of The user can therefore at any time, by simply navigating in his preferences branch, find a direct access to any element he may have discovered during his navigation. in the tree structure, as explained above, the tree is dynamic and can grow and be modified Moreover, and in addition to this dynamic aspect, the tree management method comprises, for each user, a navigation branch Dedicated for the reception of new element (node or service), conceptually similar to the branch dedicated to the references of preferred elements, the method navigation system has nine keys in an identical space for each user, a branch referencing the items received by each user. This allows the user to navigate a simple and consistent path to discover new items added to their space. It is noted that, as for the elements referenced in the preference branch, the elements referenced in the branch of reception of new elements can be, if it wishes it and when it wishes it, to arrange by each user in a place that he considers relevant in his tree structure - therefore including nowhere if the element concerned is not or more interesting for the user; this arrangement has the effect of deleting the reference of the branches of preference or reception concerned. As far as recursion is concerned, in the structure implemented, the model is open. Each object (atomic action, navigation node or application) is attached an identifier and an icon. An atomic terminal action is a service. A sophisticated application is also a service. A node in the tree opens a door to other nodes and / or services. A service can therefore, by extension of the model, be a subspace, a complete branch, in which are then organized several other levels of services, several other branches, etc. By analogy to the semantics of the web, a complex service that aggregates several other services, or even several branches of services, can also be called a portal. As far as the user's service space and the customization of this space are concerned, it is kept in a service database, each of which is potentially constituted by the tree aggregation of other services. Each user then defines his own service space, which is the mobilization of a service subspace defined for this user: the service space of a user is therefore a service tree, organized according to the same structuring rules as the global space (thus based on matrices, recursion, nodes of atomic actions and applications). FIG. 5 shows that, when accessing the user interface 500 of the services that are the subject of the present invention, from a computer (or a terminal having a screen of sufficient resolution), the user has a list 505 of services, represented by icons 510 and a representation 515 simulating the 3x3 matrix organization as it will be displayed on the mobile terminal when accessing from this terminal mobile. This representation 515 includes boxes 520 predefined in the 3x3 matrix. To select a service and incorporate it into the tree, which is reminded that a 3x3 matrix represents the descendants of the same node, the user places himself, first, in the part of the tree where the icon must be inserted, using the 515 representation as if he were using a mobile to navigate. Then, the user performs a drag and drop of an icon in the list 505. In other words, after having the pointer of a pointing device, such as a mouse, on an icon 510, in the list 505, the user c @ iques on the left button of the pointing device and moves the pointer to the box 520 of the matrix 515 where he wishes to see this icon, then he releases the left button of the pointing device . It is observed that a drop-down menu allows the user to navigate in the list 505. As seen in Figure 6, to submit a service to a correspondent (usually called friend), the user performs the same procedure of drag and drop since the representation 515, to a representation 610 of his correspondents.

The user defines this tree through a web interface that provides several tools for intuitive construction of his space. Once created on the website, this tree is called mobile, that is to say, accessible by mobile, thanks to the GML protocol. The user can then, when he wishes, come back on this web interface to edit his service area. The base (root) of this tree will be the home page of the application supporting the services, on the mobile screen of this user. From this page, the user can then navigate in his services area. This space is constituted by the user: the user has chosen the services to which he wishes to access via his mobile and organized them according to his tastes. Its service space is not the entirety of the universal service space, or global, but a subset, organized according to the tastes and needs of each user.

The interest of this user centric view (thus filtered) of the global world is very different from the global view of the Internet as given by conventional web browsers based on the WAP protocol. The importance of this filtered and user-centric view comes from the fundamental difference in usage behavior between a web situation (where the user has a certain comfort and in general a certain time, and where he waits so completeness and richness during navigation) and a mobility situation (where the user has a more limited terminal and probably a more pressing environment, and where it requires speed, ease and relevance); this filtered view of a user-dependent global navigable world is one of the preferred features of the implementation of the present invention and rests, on the one hand, on the matrix organization recursively modeled by the GML and, on the other hand, on profiling and profiling services (in English profiling) that make it possible to extract custom views. With reference to the section on recursion, above, it is understood that the personal space of a user consisting of a service tree is itself a service. With regard to intelligent cache management, from an execution point of view, this tree which represents the service space specific to a given user is maintained in the server; its representation is sent to the mobile on demand, depending on the navigation of the user: when the user invokes a service on his mobile, the system sends him (always via GML) the representation of his home page, to from which he can navigate and invoke services. As this navigation and its invocations progress, the server, via GML, sends to the mobile the necessary representations (following pages of services and nodes in the tree structure, representation of the required terminal actions, etc.). This representation information GML is dynamic and relies on an intelligent management of the cache: the system optimizes the exchanges between the mobile and the server in favor of the user experience, that is to say to reduce the times of latency during navigation. Typically, this implements prefetching algorithms (prediction of future choices) which are based on the user's usage profile as well as on the structure of his service area: when sending a page representing nine services, if, in general, during its passage on this node, the user then goes in more than 80% of the cases on the 4 cell of the next node and then invokes the terminal action 7, at least two pages of this path will be pre-loaded (prefetch) during the first invocation (deep pre-loading). If, on the other hand, the system does not know where the user will probably navigate, the system will preload, in width, the entirety (or the maximum, depending on the capabilities of the mobile) of the service representations of the next level. .

With regard to the customization of services, explicit profiles and inferred profiles, beyond the aspect of creating a personal view to each user of the global tree, the system also makes it possible to adapt the behavior final, that is to say the terminal action or the application that is invoked at the end of navigation. Thus, the terminal actions generally comprise parameters that can be chosen for the user, either explicitly by the user during his definition and optimization of his own space, or automatically by the system, then based on preferences data indicated by the user when defining his profile, or on inferences by the system based on the dynamic behavior of the user when he is in his service area. Typically, if a user often browses branches or often uses terminal actions referring to Paris, he will be offered a setting using Paris if he is navigating a terminal car rental action. For private branches, public branches, the dynamic evolution of a service area, and successive affinity navigation, when a user defines services (or service branches, or service portals), he may indicate the audience of these services. - public: everyone has access and therefore all the users of the application supporting the services can increase their own space of services by referring, in one of the node or leaf of their tree, to this service - private: this service does not may be navigated and used only by the user or - Community: this service may be referenced (and thus navigated and used) by one or more sets of users designated (s) by the creator of the service. In addition to the virtue of sharing, this possibility gives an important dynamic characteristic to the service space and its navigation: a user can refer, in his own space, to a public part of the space of another user, who can be enriched, the other user adding branches or services which, by transitivity, are also added to the navigable space of the first user. A user can, in turn, refer to a public or community part of a third, etc. From one to another, the spaces can thus have an intersection or inter-pollenize TN, allowing successive affinity navigation in a living, dynamic and open space, although still controlled and always user-centric.

As regards the promotion of services, as we have seen, the space of a user is a tree structure, with its public or private branches, chosen and / or defined by the user via a web interface. This tree becomes navigable via his mobile and leads, in his sheets, to a collection of services. The fact that some of these branches are references to other public branches creates a first level of dynamism in the user's space structure, because the public branches that it refers to can evolve. A second level of dynamism is offered by the mechanism called InGoojet: in any space of any user, a branch is reserved by the system supporting the implementation of the present invention, to dynamically add services available to this user: is an extension of the concept of mailbox, but structured for referencing services. This reserved branch is structured in a linear way: on the first page, it contains only two representations of services: an empty service, which is a place reserved for the first service that will be sent to this user (empty service says placeholder) and a second service. node service that simply leads, on the second page, to a page structured in the same way as the first one (this node service is therefore a following service), and so on, recursively, as needed. This allows the user to simply navigate linearly in this branch, whose size varies dynamically depending on the services it receives. Services can be sent to users through promotions: on the website or via their mobile, a user can decide to share a service with another user or with a user community and thus promote this service, which reference will be added dynamically by the server on the tree representations of each recipient, at the end of the InGoojet branch list. Each user has immediate access to a new service. He may, if he wishes, remove it from his InGoojet branch; it can also, via the web interface, reorganize its service area and put this service, if it wishes to keep it, to another place in its own service area. In addition to its use in the context of promotion or exchange of services, this InGoojet dynamic branch is also used directly by the user if he wishes to add access to a service in his service area without, however, have access to a web interface (which is, as described above, the nominal means of creating and managing a service area). This need can be opportunistic and urgent: the system thus makes available to the user, via its mobile interface and in addition to the web interface, a special service called Goojet Picker which allows the user to select a service in the service base by entering its unique identifier. The reference of the service thus selected will be added to the user's InGoojet, as for a service received by promotion of a third party. The fundamental notion associated with this ability to promote or to visibility of a goojet picker service is the establishment of a service directory specific to the system implementing the present invention. In other words, the system defines the GRL (acronym for Goojet Ressouce Link or Goojet resource link). GRL is a multimodal identifier that provides access to a single mobile and web service. On the Web, the GRL has its source after the notion of URL (www.goojet.com). On the mobile, this gives direct access to a set of resources / applications authenticated by the organization managing the services that are the subject of the present invention and represented on an icon that can be in different trees depending on the mobiles that reference it but which remaining referencing the same unique resource. When a user creates a service, it is assigned a unique identifier (GRL) This identifier provides a unique entry in the directory services. The server provides access to information about the property of the service, through a Whols mechanism. The example illustrating the interest of the mechanism is that of a restaurant service.

One can with the platform of services, create an application which makes it possible to inform a restaurant (place, menus, prices, coordinates) and at the same time to make a reservation for this said restaurant. If it is possible for anyone without a guarantee of uniqueness on the part of the platform to create a restaurant service, we can end up with a major inconsistency in mobility situation (book a restaurant that is not the expected one ). In a similar way to InGoojet, the system offers the user a third level of dynamism: the bookmark, or bookmark:. The bookmark is a linear structure in every respect similar to InGoojet, in which are dynamically added the references to the services that the user wants to make immediately available. The bookmark is particularly useful when the user navigates an unknown branch of space (typically a public branch to which he has had access by successive public navigation) and finds an interesting service there. The fact of marking it, or bookmarker, during its passage, sends the reference in the InGoojet, for immediate access and for eventual reorganization, if used by the user of the web interface.

With regard to the creation of services, the system allows the user to create his own mobile space by selecting and aggregating atomic actions, services, service branches or public spaces between them, in a tree organization that suits. Using these same mechanisms of selection, parameterization and aggregation, the user can also create services (or under services) not necessarily to reference them in his own space, but to make them available to other users. Thus, the system provides the new ability to a user, by aggregating and setting pre-existing items, to create new services, which will be available to other mobile users, without having to develop computer code nor having to distribute , by any channel, mobile applications. The global space of services is therefore open to navigation but is also open to contribution and frees the user of the steps deemed complex linked, in the absence of the implementation of the present invention, the creation, distribution and the exploitation of mobile applications. For explicit communities and inferred communities, just as user profiles can be explicit or inferred, communities (for example, to declare branch access, for service promotions) can be: - explicit, that is to say, defined by explicit lists of identifiers of users or mobile numbers, - inferred, ie calculated, in real time, by the system based on usage and behavior statistics. Typically, such an inference uses a semantic distance calculation between the users: based on the type of navigation and the type of services used, the system dynamically identifies communities of use (sportsmen living in Paris, teenagers who love rock'n'roll roll, etc.). These inferred communities are used for the relevant promotion of services, for various community services (eg, tennis partner search, carpool service, etc.) and, to allow, in commercial operations of commercial partners, to reach with relevance the optimal audience for their messages and promotions. The server thus makes the constant acquisition of data on all users and services to feed profiling algorithms (in English profiling), the results of which are then used for the customization of services and service areas and for the sending relevant information or services. This capability is one of the pillars of the commercial operation of the system. Regarding ubiquitous mobile web, the services defined on the implemented infrastructure are intended to be referenced in accessible trees of mobile to offer services in a mobility situation. But the structure of these services also makes them accessible via the internet (via a web browser). This allows users to share information, data and services regardless of their means of access. Moreover, the system recognizes the means of access to a service and offers a different level of wealth depending on the means of access used. For example, the server supporting a voting application simply displays the current result of the vote during a mobile access, while it offers a wide variety of statistical and historical analysis during a web access. Figure 7 schematically shows a unified communication infrastructure 701, also called ICU. This infrastructure can handle four standard message flow types (IM for instant messaging or instant messaging, SMS, email and voice communication), as well as the one provided by a proprietary community platform. The ICLJ infrastructure provides bridges between these types of flows (incoming / outgoing).

The infrastructure comprises: a gateway 702 to and from voice transmission services, in particular on the Internet, a gateway 703, to and from SMS short message services, a gateway 704, to and from e-mail servers, the server 705 retaining software and data for implementing the present invention and supporting the infrastructure 701, and a gateway 706 to and from instant messaging services. In embodiments, the ICU 701 manages a routing (function known as conditional transfer or forwarding) according to: - the identity of the sender of the message, - a given period (hour, day ...), - content elements and / or a presence signal (if the recipient is identified as present on one of the channels configured in the routing, the message is first or only transmitted on this channel) . The ICU can also manage a routing workflow. This means that there is a transmission priority level for each channel and a waiting time between each transmission. This feature avoids duplicating the content of the message if the user considers that from the moment he has acknowledged it, he does not wish to see it on another medium.

The ICU can allow the management (creation / modification / deletion) of all or part of applications as described in the presentation of the creation of rich applications on the fly. The ICU 701 thus realizes, in a routing server, as illustrated in FIG. 9: a step 910 for receiving data to be transmitted, said data removing associated with an identifier of the recipient, a step 915 for determining a context of transmitting the data to the recipient, a step 920 of selecting at least one receiving channel associated with said recipient according to said context and a step 925 of transmitting the data on each selected reception channel.

Thus, the channel, or channels, used to transmit the data to the recipient varies depending on the context. During step 915, the routing context is representative of: an identifier (unique address on a channel, e-mail address, e-mail address, telephone number, for example) of the sender of the data to be transmitted, a time stamp of the data to be transmitted, for example their hour and minute of reception by the server, of the content of the data to be transmitted, of an access to a channel available to the user (that is to say the information, for each channel, that the user is connected to the support of this channel), and / or - a priority of channels. Thus, for example: the user can request that the data coming from at least one interlocutor be transmitted to him on a predefined channel or on all the channels allowing the transmission of the data, for example, - conversely, the authorities or a hierarchical superior of the recipient can obtain that all data from them is transmitted by all the reception channels associated with the user, - the user can request that the data arriving at office hours be transmitted to him on a predefined channel then that the same data arriving outside office hours will be transmitted to him on another predefined cana, - the user can request that the data of a message including a particular reference (for example a file number) be transmitted to him on a predefined channel, - when the user does not have access to the mobile telephone network, for example, he can obtain the data are transmitted on a fixed line, and / or - the user can request that the data of a message be transmitted to him on a first predefined channel, in the absence of acknowledgment of receipt from him within a predetermined time they are transmitted to it on a second predefined channel and so on. This avoids duplicating the content of the message on different channels while optimizing the chances of rapid receipt of data by the user.

In embodiments, during the selection step, a mapping table is implemented between context parameter values and data transmission channels. The selection is thus easy and the correspondence table can be easily edited by the user.

In embodiments, during the data transmission step, the data is formatted according to the transmission channel on which the data is transmitted, as set forth below. We can thus go from voice to text, or vice versa, from an email to a short message, or vice versa, etc. In embodiments, during the transmission step, an application program is created according to the data to be transmitted and the application program is transmitted to the user. In the particular embodiment set forth in FIG. 7, the ICU infrastructure performs the following operations: ICU 701 receives a message from gateway 702, 703, 704 or 70E3, or server 705; the ICU 701 analyzes the content of the message according to the issuer in order to extract structuring elements therefrom; for each recipient of the message: the ICU 701 determines, in the conversion table, the items to be produced and the ICU 701 sends the message for each channel configured according to a set of management rules (conditional). The association of tags, or Tag, with the incoming flows makes it possible to enrich the behavior of the platform during the creation of the outgoing flows. The infrastructure makes it possible to broadcast any type of media using formatting capabilities adapted to the medium.

The transmitters or recipients of media considered are, in particular: - a computer via: - a web browser on a dedicated URL, - a mail client on a dedicated account, - an IM client and - a dedicated application on a proprietary format and - a phone via: - the SMS client, - a dedicated application, - a WAP browser and - a voice mailbox. The ICU is configured by each user to define the gateways he wishes to configure. The table below gives a presentation of different flows.

The user informs, during the configuration of the ICU: - the IM accounts used, -. for SMS, the telephone number, - for e-mails, the e-mail address, - for voice communications, the telephone number and -. for the use of the platform implementing the services objects of the present invention, an account identifier. The table below references, by numbers between 1 and 20, the need for stream conversion: Emission / Reception IM SMS Voice Mail Platform IM x 1 2 3 4 SMS 5 x 6 7 8 Mail 9 10 X 11 12 Vocale 13 14 15 x 16 Platform 17 18 19 20 x This table lists the different types of messages sent and received. This means that the numbers appearing in the different boxes will be included to explain the treatments carried out by the infrastructure in each case. The x present in the diagonal of the table mean that there is, a priori, no necessary treatment. Sending an SMS: When an SMS is received by the ICU, each text ending with the @ symbol is analyzed as a recipient. For example, the message Dl @ D2 @ hello how are you? : will be treated as the message hello how are you? issued to the ICU for recipients Dl and D2.

The ICU performs the following processing: Case 1 (the recipient to configure one or more IM channels on which he wishes to be informed): the entire SMS (excluding recipient fields) is transmitted on the IM with the identity of the Transmitter Cas 10 (the recipient to configure an email address on which he wishes to be informed): the entire SMS (excluding recipient fields), and the identity of the issuer are incorporated into the body of the email. The subject contains the platform informs you of the receipt of an SMS Case 14 (the recipient to set up a mailbox): the entire SMS (excluding recipient fields) is converted by a TextTOSpeach process as well as the identity of The transmitter. For each recipient of the message, the ICU makes a voice call.

Case 18 (the recipient subscribes to a community platform): the entire SMS is sent to the platform for analysis. The destination fields are processed: on the platform (Recipient IDs may be different from those known by the ICU).

Emails e-mail: When an e-mail is sent to the recipient's address through the Unified Messaging infrastructure, it is analyzed in the following cases: Case 2 (the recipient to configure one or more IM channels on which he wants to be informed): the subject of the email is transmitted on the IM first with the identity of the issuer. The text content is extracted from the body of the email and formatted to be transmitted on the IM. Case 6 (the recipient to configure the SMS channel): the subject of the email is transmitted in the body of the SMS, as well as the identity of the sender. Case 15 (The recipient to set up a mailbox): The subject of the email is converted by a TextTOSpeach method as well as the identity of the sender. Case 19 (the recipient is subscribed to a community platform): the whole email is analyzed as follows: - subject: the subject can contain a tag giving a business character to the message (example: [ALARM] intrusion at destination will solicit the platform with the tag ALARM to generate a behavior dedicated to the processing of an alarm). If the platform can not interpret the tag, it uses the default behavior; attached parts: each attachment is analyzed to define the type of document is thus allow the platform to perform a transformation on the source 25 to adapt it to the capabilities of the platform; - body of the message: the body of the message may contain tags that guide the platform on the treatment of the body of the message complement generally with the Tag contained in the subject. Sending a voice call: When a voice call is received by the ICU, the message is registered and the ICU requests to enter the identifiers of the recipients of the message. The identifiers may be preregistered identifiers on the ICU and associated with the caller's number. Example: A user with the phone number 0607080910 predefined the recipients D1 and D2 by giving them the identifiers 1 and 2. When he calls the ICU from his mobile, the ICU identifies the calling number and at the end of the voice message if the user enters # 1 # 2 #, the ICU will forward the message to the recipients D1 and D2 . The ICU will perform the following: Case 3 (the recipient to configure one or more IM channels on which he wishes to be notified): the following message is posted on the IM: The person at number xxxx you to leave a voice message. Case 7 (the recipient to configure the SMS channel): the following message is sent by SMS: The person at the number xxxx you to leave a voice message. Case 11 (the recipient to configure an email address on which he wishes to be informed): the voice message is attached as an attachment to the email. The subject contains the platform informs you of the receipt of a voice message left by xxxxx. Case 20 (the recipient is subscribed to a community platform): the voice message is transmitted to the platform and the Ids entered at the end of the message. Platform transmission: When the platform sends a message to the ICU, it pre-processes the message for the different categories of existing streams. The ICU receives directly transmittable formatted data: Case 4 (the recipient to configure one or more IM channels on which he wishes to be informed): text for the IM. Case 8 (the recipient to configure the SMS channel): text intended for sending SMS. Case 12 (the recipient to configure a voice mailbox): voice message intended to be left on a voice mailbox. Case 16 (the recipient to configure an email address on which he wishes to be informed): the whole email is prepared: - subject, -. attached parts and - body of the message. The ICU can optionally manage a routing (function known as the transfer or forward) conditional depending on: the identity of the sender of the message, a given period (time, day ...), content elements and / or a heartbeat (if the recipient is identified as present on one of the configured channels in the routing, the message is first or only transmitted on that channel) The ICU can also manage a workflow Routing. This means that there is a transmission priority level for each channel and a waiting time between each transmission. This feature avoids duplicating the content of the message if the user considers that from the moment he has acknowledged it, he does not wish to see it on another medium.

The ICU can enable the management (creation / modification / deletion) of all or part of applications as described in the discussion of creating rich applications on the fly, below. In the remainder of this description, additional descriptive elements are given, on the architecture of an embodiment of the system implementing the present invention, and on the services object of the present invention. To warn the user of the occurrence of an event related to a service, ping or signals are transmitted using telephone lines. A call implementing a predefined caller number is briefly transmitted to the user (who does not pick 10) to notify him of an event (new message, new update, etc.), the predefined number serving as an identifier of the event. After receiving this short call, the user only has to connect to the server. In one service, a user may import all or part of another user's service space into his own. This makes the notion of shared services and information transparent. For this purpose, we use the level of visibility assigned to each other user's service, much like we can do on Flickr with images (public / friends / family), and we can not do an action (eg a reservation) instead of a person because one has imported his space into his. Moreover, the addition to the buddy-list should be subject to authorization (as in most systems). Partitioning of data driven by social proximity: in systems with very large volume, a database is no longer sufficient to store all data, and it is necessary to partition, ie to have databases containing only some of the users. Traditional approaches are simply based on a modulo of a unique identifier (genus id-user% nb-machines) or a data volume balancing. In embodiments of the system implementing the present invention, the efficiency of the system is improved by keeping highly connected users on the same server. Partitioning is then controlled by the connectivity of the graphs. This does not preclude the geographic distribution of the data, since a related user graph can be stored in a datacenter located at the average location of that graph. The present invention enables the creation of rich applications on the fly via the use of different media. For example, it is about creating an application from receiving an email, scanning the sender and, if known to go to his account, subject, body and e-mail attachments. are transformed into a computer application. For example, an email with attached photos becomes a photo album application with the subject of the email as its title. In another example, an e-mail having, as a subject, according to a particular syntax, date / time and place of rendezvous, is transformed in a calendar application into an event for the date / time with, as a title, the place of appointments and, as description, the body of the email.

In the previous examples, it was only considered the email media. However, one can also take into account many other media, for example the following media: SMS, MMS, IM, telephone (electronic representation of a telephone call: sound file :), fax (electronic representation of the fax: tiff, pdf , ..) and UL Web (HTML, XHTML, ...).

More generally, all electronic sources (textual, sound, image, whatever the formats with or without syndication of sources (text + image, text only, ...)) is the input source for the creation of an application rich taking up all or part of the content. It is understood by rich application any complete application already existing, partial, generated on the fly, owner or not.

As far as user identification is concerned, in most cases a user identification may / must be necessary to allow this new application to be added to his account. In most of the source media proposed above, there are means of automatic identification without adding this information to the rest of the content: caller number, identifier or pseudo, etc. The method makes it possible to manage all or part of rich applications by sending, submitting or retrieving any document (single or multiple) of the formats listed below (lists of formats and types of format are not exhaustive) using any media (telephone, email, IM, Fax, ...). 30 Sound File Formats: RAW, WAV, MP3 (MPEG-1 Layer III), XAC, AIFF, AIFC, IFF, AU, VOC, SND, Ogg Vorbis (or OGG), AAC or MPEG-2 AAC, MP3pro, VQF or TwinVQ (acronym for Transform-domain Weighted Interleave Vector Quantization for weighted interlaced vector quantization of domain transformation), WMA (acronym for Windows Media Audio, registered trademark), ASF (acronym for Advanced 35 Streaming Format for advanced flow format), SDS, SMP, VOX, MAT and FLAC.

Image formats: JPEG, GIF, TIFF, APNG, MNG, PNG, PCX, BMP, IRIS Silicon Graphics, SUN Raster, PPM, Encapsulated Postscript, Pixmap X, Photoshop, PGM, DICOM, Bitmap X, AliasIWavefront PIX. Video formats: Divx, QuickTime, Real, Xvid, VP7, X264, AAC, Ogg Vorbis.

Text document formats: Doc, Docx, Odt, Sxw, Rtf, Sdw, Pdf, Txt, XML, HTML and XHTMIL. As illustrated in FIG. 11, to create computer applications, from the reception of a message having a content, step 1105, a type of computer application that can be associated with said content is determined according to said content, step 1110 and setting up a generic application of the determined type of application with said content to constitute said computer application, step 1115. When determining a type of computer application, the type of computer application depends on: the identity of the sender of said message, at least one attachment to said message and / or keywords included in the content of said message. With regard to web browsing, (web), the present invention also relates to an advanced web browser for low capacity terminals. Indeed, the success of the web is due, in part, to the fact that HTML (language of description of web pages) and Javascript (programming language of dynamic web pages) are provided by web servers to browsers as text source. On the one hand, this avoids having to define binary representations that could have been dependent on a platform, and on the other hand allowed any user to learn how to develop web pages by simply examining their source.

But this approach imposes a significant workload on the browser, which must analyze the source of HTML and Javascript before being able to display and execute them respectively. This is not a constraint on modern personal computers with high computing power, large memory capacity and fast network connection, but becomes very problematic in constrained environments such as mobile phones. or mid-range. To enable low-capacity mobile phones to display HTML web pages, as well as JavaScript code execution, these elements are pre-analyzed in a gateway between the phone and the website. Moreover, we also offer the ability, offered to Javascript code contained in the web page, to use so-called native features of the phone such as sending SMS, establishing communications or image capture. There is also a mechanism to use the same Javascript code for similar functions on the browser of a personal computer.

The browser thus created is able, in addition or replacement of the GMI_, to receive HTML and Javascript code in a particular binary form, allowing its operation on any type of mobile. The binarization is performed by a server called gateway server 840 (see Figure 8). To access a web server 880, the browser 820 on mobile 810 sends a request 890a to this gateway server 840, which transmits it, by the message 890b, to the effective server 880. This effective server provides the web page and its Javascript code, The gateway server 840 performs the binarization / compilation process and transmits the result of this process, via the message 815, to the Goojet browser of the mobile phone 820.

The binarization has several actions (the actual order may be different from the one presented below) performed by the gateway server: expansion of CSS 850 styles, defining the appearance (size, font, color) of each element of the HTML page , - transcoding HTML 860 elements into a binary representation that can be used effectively by the mobile phone, - compiling the Javascript 870 code into a compact bytecode that can be efficiently interpreted by the mobile phone An optional feature of the navigation method is that the transformation is completely transparent for the Javascript code contained in the page. In particular, it can modify the structure of the page after it is displayed on the mobile terminal 810. The DOM Document Object Model interface is available to allow the construction of local interactions at the terminal, not involving the server. origin. Another optional feature is that the result of the transformations can be maintained by the gateway server 840 in a temporary storage system 825 so as not to perform repetitively the transformation of the same content that would be requested frequently either by the same mobile phone or by different phones. Using the phone's native features The environment in which the Javascript code is executed in the phone has special features that allow you to use the native 830 functions and devices of the mobile phone. In particular, and without limitation: - sending SMS, - establishing telephone communications, - consulting the address book and - using the built-in camera on the phone to capture still images or video.

With the present invention aimed at providing a transparent execution environment for applications, these functions will also be available on a browser running on a personal computer. For this purpose, the personal computer runtime environment provides the web pages with a JavaScript runtime environment including an implementation of these functions. The means used will be, without limitation: - a web / SMS gateway for sending SMS, - the use of telephones implementing the SIP or Skype software (registered trademarks) for the establishment of telephone calls, 10 - the consultation of the address book downloaded from the phone and synchronized with the server, - the use of browser extension, Flash plugin type to use a vvebcam or other photography and video device connected to the computer. For this purpose, a pre-analysis is performed on the gateway server of the formatting characteristics of the HTML content (CSS styles) on the server, HTML is transformed on the gateway server and formatted in a compact binary form. , we compile Javascript on the gateway server by directly executable bytecode instructions This ensures a transparency of the process of binarization / compilation for the Javascript code contained in the web pages, the provision of Javascript of 20 functions to access the native functions the phone and the implementation of the native functions of the phone for personal computer browsers using soft phones and webcam or other photography and video capture device. With regard to the services that are the subject of the present invention, the infrastructure set up makes it possible to develop, promote and exploit innovative services, the examples of which are set out below: 1 / service of e: conference cati or synchronous teleconference on demand: this service makes it possible to simultaneously connect several remote users on their mobile phone without having to prepare or book a conference. This service is particularly practical in situation of mobility and dispersion of interlocutors. This service allows a user to select either by explicit entry of mobile identifiers or by automatic entry of identifiers by the system (interpreting the list of contacts represented in the page from which the service is invoked) of the candidates. to a conference call. The mere evocation of the conference call terminal action, chosen in the user's service space, causes the server to send the conference invitation notifications to the applicants. These notifications can be multimodal and include, among other things, an SMS and a notification via the service interface (GML response to polling). Upon receipt of the notification, each recipient can, by simple acceptance, be put directly in contact with the server that organizes the conference. The mobile part of this service consists of candidate selection and notification management (user-side triggering that invited, guest-side acceptance). The task of the server then consists, essentially, in sending the notifications and putting them in contact with the acceptance of each recipient. Beyond this function, the server of this conference application also offers value-added conference management functions, such as records and / or statistics, whose operation is accessible via the web interface. Each potential interlocutor, or candidate, receives a call number and a graphical interface indicating the correspondents whose telephone numbers are being dialed (action to call the number and ring on the active number). The system reserves the number for the conference because, knowing the number of potential callers, it can filter out unwanted people who would call the number at the same time. The person in charge (in English leader) of the conference can decide, with a simple click, to switch everybody in conference (start of the billing for each caller). When a user is invited to a conference, he has a trigger. The selection, or click, on this trigger causes the appearance of a page with the avatars of the persons invited to the conference call (for an unidentified person, one makes appear his name or his telephone number). A status is shown next to or on each icon of the avatar and indicates whether the corresponding user has entered the conference call. Optionally, the status identifies who is speaking. Preferably, the server does not take the communication of a participant, as long as there is not at least one other participant who calls him. This saves a user from being connected for nothing.

Figure 10 illustrates a particular embodiment of the method implementing this conference call application. In the description, the terms user and interlocutor are equivalent and used interchangeably. We first observe, in FIG. 10, a step 1005 of launching the communication, by a first user, during which the first user selects an application in a tree structure, with his mobile phone, as explained above. . Then, during a step 1010, a selection is made, by said first user, of at least two users, said second. This selection can be made: second caller by second caller, by dialing their phone numbers or selecting this number from a directory or by selecting avatars or photos representing them and / or by selecting an application in which a set of second contacts potential is already referenced (with possible elimination of potential interlocutors). After validation by the first party of the list of second interlocutors invited to the conference, a server implementing the conference service receives this list from the first party, during a step 1015 and reserves a number assigned to said conference. During a step 1020, the server makes a notification of each second selected user, during which each second user receives information from a graphical interface representing the first user and each other selected second user as well as the reserved number. For the notification step, the server can implement different types of communication channels with the different second users. In addition, the notifications may be multimodal, depending on the communication capabilities of the second parties. Preferably, during the notification step, in the absence of a response from a second user, said second absent user is notified again via a communication channel different from that used for the first notification of the second user. second user absent. Thus, an interlocutor who did not answer with a mobile phone can be called on a landline, for example. During a step 1025, each second user terminal provided with the conference application displays said graphical interface. During a step 1030, the server determines whether a second interlocutor has agreed to participate in the conference. To accept, each second user only has to select an acceptance icon represented on the graphical interface. If No, During a step 1035, the server determines if a second party has refused to participate in the conference. To refuse, each second user only has to select a refusal icon represented on the graphical interface. If not, return to step 1030. If the result of step 1035 is positive, during a step 1040, each talker, first or second, is sent a graphical interface information representing the refusal of participate from the second party, and the identification of the second party and returns to step 1025. If the result of step 1030 is positive, in a step 1045, is transmitted to each interlocutor , first or second, GUI information representing the acceptance to participate from the second party, and the identification of the second speaker and each GUI performs the display of this information. Then, during a step 1050, it is determined whether the first party initiates the conference. To trigger the conference, the first party only has to select an icon in the GUI. If no, we return to step 1030. If yes, during a step 1055, the first party and each second party having agreed to participate in the conference receives the number reserved for the conference and, possibly after a last validation on the part of the second users, all the mobiles of the interlocutors who have accepted the conference are put in telephone or videophone communication, for those who have the means of videophone, by means of the reserved number. During a step 1060, if the first user has selected a recording option, and for each second interlocutor subsequently accepting to participate in the conference, a registration authorization is requested from each second party participating in the conference. In the event of authorization, during a step 1065, a recording of the content of the conference is carried out and, at the end of the conference, step 1075, a step 1080 is made to make said recording available to each participant in the conference, for example by transmitting an audio and / or video file to participants' e-mail addresses. During the conference, step 1070, the talker is detected (by simple processing of the audio signal of the different participants and the display on the graphical interfaces of the different participants is displayed, an identification of the user who speaks.

The follow-up of the conference is thus facilitated. It should be noted that, when the first user calls between the steps 1005 and 1070, this call is rejected. This avoids a third party not invited to the conference disrupts the event. In a variant, instead of step 1050, the communication is automatically initiated when at least one second user has accepted the conference. This avoids billing the communication to the first user awaiting acceptance of the conference by the second users. The notifications indicated above can be made by short message (SMS), multimedia short message (MMS), voice call with voice message, voice call and on-hook, e-mail, message in the conference application or any other compatible application or connected. 2 / autonomous web-mobile transactional services: in this service, the server manages transactions between customers and suppliers, and can therefore, in some cases, substitute for IT or heavy Internet services. These services are made possible thanks to the intelligent division of the processes between mobile presentation and server. For example, the reservation service is defined as follows: - the provider, for example a restaurant, to create his service - this service is a branch of various aggregated services, including information about the restaurant, links to other services deemed relevant or related by the restaurant. One of the sheets of the tree is the application service of reservation, set by the restaurant for its need, during the creation of its transactional service. Once created, this complex service in which the application reservation service set for this restaurant is located, is available to the community of users of the present invention. Public, he can be promoted. Thus, it can be found in the spaces of potential users without these having had to search for this service.

The application reservation service consists of several input pages of choice (each choice entry page being a configurable atom), which together form the elements of a request. For example, the user chooses a time and a number of people (the same concept of course applying to any type of request, the number of successive choices and the candidates for each of these choices being parameters entered by the creator of the service at its creation). Then he sends his request, which the server receives and processes. The processing of the server consists of sending the request to the restaurant, in the format chosen by the restaurant during the creation of its reservation service. The restaurant can choose a multimodal notification: for example by SMS, email, phone call, invocation of a web service with its management computer system, whose content is manufactured by the server according to the parameters sent by the mobile part of the server. client during his request. Among the many possible modes, one is also a service: the restaurant can have the mobile part provider of the same service. This service is structured into a mobile client part, used by each customer of the restaurant to send their request, a server to process requests, and a mobile provider that completes the transaction. With this service, the restaurant can receive the request directly in the application space and process the request in near real time, from its mobile: on acceptance or rejection, it completes the transaction via the server to the issuer of the request. It can also use its mobile provider part for management operations (for example display complete for future users). It can also, by using a web access to the server, have access to more wealth on this service, including various statistics on the use of the service, information on the applicants, etc. Thanks to its distributed structure and thanks to its bimodal web-mobile access, this new type of service replaces both a voice reservation service and a conventional information and management system. The transactional reservation service, based on a complementary pair of mobile parties, one for the customer and the other for the provider and on a mediation and management server is new. 3 / service of interaction between real universe and virtual universe: it is a question of allowing to enter a virtual world with the tools of communications of the real world (telephone connection, access to an instantaneous message, such as IM, registered mark or email, or email). The novelty is based on the fact that we can connect two avatars between them by hiding their identity in real life. Taking into account the profile of the avatar is integrated in the use of a voice filter, for example a filter transposing the treble frequencies in the treble for the voice of a man who chooses a female avatar. For the implementation of this interaction service between real and virtual universes: the platform implemented by the server makes it possible to reference the identities of each user in different environments or virtual worlds, the platform receives and processes messages from different virtual worlds and - for each recognized identity, the platform proceeds to route messages to the adapted / user-configured channel (owner of the identifier). For example, in the virtual world MV1, the user U1 has the identifier ul and a person U2 of this virtual world MV1 has the identifier u2. ul calls u2 using the service MV1, the application supporting the interaction service makes a connection request in the world MV1 from ul to u2 (without knowing the real identity of U2), the service interaction gets the coordinates of U2, - the interaction service transmits the request to the ICU (see Figure 7), which performs all actions associated with U2 (if U2 is not identified on the ICU only the call is possible) 25 - the interaction service triggers U2 related actions (ICU parameterization) or a simple ul call (because this service knows the number of the subscriber) to u2 if U2 n is not known. What is described above is true for any type of messages that can be sent from an MV1 world to the real world or from an MV1 world to an MV2 world or within the same MV1 virtual world. 4 / mobile billboard service: this is an infrastructure that allows advertisers to publish information on a dedicated page. The concept of this advertising service is based on that of an advertising message that appears in the user space from time to time, this message preferably comprising information related to the user's profile. For the implementation of this advertising service: - the user has a publicity space that resides permanently on his phone (depending on the subscription he has taken, he is more or less invited to consult this space), - when a service is requested by the user, the platform supporting the advertising service determines if there is an advertising element that is related to its request, - if the platform finds at least one related advertising element, the advertising space is enriched with at least one new advertisement and the user is informed. Dedicated to advertisers, this space is filled according to complex algorithms including the target that the advertiser wants to reach and the number of publications he wants to have. This space can also be used to transmit targeted messages, for example, advertising information that the user to accept to receive, in various media. 5 / Digital DNA service: this is a modeling of an individual through a string of binary data. This service implements a suite of binary properties that can represent any individual, both what he is and what he likes. This universal and public description of the digital genome can be used to make pattern matching between individuals. 6 / Push to Get service: the aim is to offer a mobile prompter communication infrastructure that can be interactive. The mobile is subscribed to a stream of immediate messages that scroll according to the news produced by an authenticated source (eg AFP, aufeminin.com, Auto / motorcycle, trademarks). The user can request more information by pressing a certain key on the mobile when the message appears. In response, the server takes into account the message object of the request and builds a folder that is sent to the user on the media he has chosen (e-mail, voice, services object of the present invention). 7 / service of Tamagoshi (registered trademark): it allows to create virtual living objects (animals or others) and to animate them alone or in community since his / her services. Objects / classes implemented on the server side manage behaviors of the virtual animal. The user can derive these classes and create other virtual animals or worlds. We note that the exchanges between the server and mobile is managed by the server. Each element constituting the animation of the life of Tamagoshi is mapped to a touch of the phone, via an icon. 8 / match service: it connects two teams, rules to pass a ball from one user to another and conditions of interception and shooting on goal. 9 / collaborative service: the infrastructure of the services of the present invention allows the development of collaborative services, defined as services requiring opportunities for interaction and sharing between multiple users. Recall that conventional services for reading shared information, to which several users can access from their mobile, read-only, are not considered collaborative. The new service offered, in collaborative terms, consists of implementing the following elements together: - a distributed application having: - a centralizing part residing on the Internet; it is the server part, - several parts distributed on mobile terminals - the mobile client parts, accessing the server part via the GML protocol, - accesses via web browsers, on thin client parts, on PC, - interactions between the server part and other applications residing on other web servers, using APIs or web services on the internet, - the possibility given to mobile parts to provide information (data, requests) to the server part and to others mobile parts, via the server part, and - the possibility given to the client parties to simultaneously access and modify shared data managed by the server part. In this service object of the present invention, a dedicated application that allows sharing and transactions is present in the moving parts. On this principle, several collaborative services are offered by the system, including Glog, an extension of the mobile blog concept. Glog is a shared database resident on and managed by the server part. This database allows orderly access to data submitted to it. The data submitted to Glog are any object that can be generated and transmitted by a mobile (text, photo, sound, video, voice message, data structured by GML such social signal, identification of a service and choice of action in this service, etc.). The data, stored by Glog, are ordered according to several criteria: - thread (thread), - theme - date / time and - origin. A thread is a linear ordering based on the notion of answer: a thread at a starting point then a simple navigation by following! previous (in reading), and a response to a thread simply adds an element at the end of the thread, thus enlarging the size. A selected Glog yarn can be read by a mobile via a service object of the present invention: the last elements, up to a maximum of nine, are accessible via a dedicated service page and displayed on demand according to their format (text, sound, image, etc.). Accessing a thread can add an element (response). The wires are heterogeneous and can contain elements of any type. The theme is a metadata selected by the creator of a thread. The theme allows thread readers to do targeted searches. As Glog is, like any service object of the present invention, designed for the ubiquity of web-mobile access, the theme can be freely chosen at creation if the creation (initialization of a thread) is made from the website. If the creation is made from a mobile, the creator can either freely choose a theme by entering a text, or choose a theme from nine via a dedicated page. The nine themes proposed are either the nine themes that the user has chosen on his profile, via the web (general philosophy of preparation via the web of his own mobile space, which, once mobile, is not as exhaustive as the web, but is targeted for its own use, relevant and fast), the nine most used themes on Glog, as calculated by the system and offered to the user. In access of an existing son, the reader can also select a theme via the same theme window, or select via the window that indicates the nine most active children, or via his subscription window to his nine favorite sons, as he can define it on his glogor profile, via the web. The Date and time field allows, on the one hand, a chronological organization but also, via a web access, searches in time (whereas the mobile access will give by default the last nine entries in each thread).

The origin field is the identity of the user who initialized the thread as well as the identity, for each entry in the thread, of the contributor. The glog server part also uses this field to calculate, and offer via web access, activity statistics by glog or user. It is noted that the glog can be used in conjunction with the gVote service which allows, generically, each user to allocate a status (from a maximum of nine predefined statuses for each instance of the gVote service) to a candidate (from a maximum of nine predefined candidates for each instance of the gVote service). A typical instance of gVote may be to allocate a rating to an object (service, photo, chat, event, etc.). In conjunction with Glog, gVote allows users to rate threads, themes, contributions, and contributors. The mobile part of gVote allows to give a note and display the current result, while the server part, accessed via the web, allows to display a great wealth of historical and statistical results, thus enriching Glog. 10 / Another collaborative service is the shared alarm service. It is an element of a set of services around the organization of time within a group of people; this set includes, among others, a shared agenda, offered by a third-party web application, and to which the server part is mediating, thus allowing mobile users to access, both read and write, an agenda sharing. The alarm service falls into this category. It includes two structural differences with the agenda: on the one hand, it is fully managed by the system and does not require mediation to a third party service and, on the other hand, it requires event processing in the moving parts The group alarm service operates as follows: - A user uses his mobile or web interface to select the date and time of an alarm and the hearing of that alarm. It can also select the media used by the system to inform the audience of the alarm when it is triggered. Except for such specific selection (mail, call by automatic voice server, etc.), the system will work in two steps: - the alarm service server, upon receipt of a group alarm request, add a corresponding item in the box events of each member of the destination group who is a service user object of the present invention; - When these users will update their events, by the generic mechanism of management and notification of service events, GML sends to their respective mobile part a reinforcement of their local alarm. These users are then notified of the triggering of the alarm locally by their mobile. The advantage of this remote arming (as opposed to remote alarm notification) is that the recipients are alarmed even if they are not receiving the service at the time of the alarm and - for recipients not users of services object of the present invention, or for the recipients who would not have synchronized their event manager before the time of the alarm, the server part of the alarm service sends a message by a channel selected by the user who organized this alarm; typically, an SMS. A group alarm thus organized includes a time and date, an audience, but also a theme, which can be a free text or a theme among nine selectable via a dedicated selection window. As in any other service object of the present invention, these nine themes are either the preferred themes of the user defined in his profile for this service, via the web, or, by default, the nine most likely themes calculated and proposed by the system based on the usage profiles of this service. It should be noted, with regard to the service event management service that is the subject of the present invention, that several service usage cases require that a user be notified that an event concerns him. Since the system's server does not have the ability to spontaneously send a request to a mobile client user, it can not itself notify the user of the event that concerns it. The generic mechanism used is therefore the following: -. first, for each user, there is a space in the server where the events relating to this user are stored, according to their arrival time and their priorities (these events may have varied and heterogeneous sources such as an autonomous service requiring the sending of information or notification to a user, or a collaborative service by which another user wishes to interact with this user, or a request from a third party service for which the system is mediating to mobile users). This event space is replicated on the mobile during synchronization operation: the mobile part is automatically informed of the state of the event space. The event space is, itself, organized according to the tree structure having, preferably, a maximum of nine branches at each node. - Then the mobile part - or the user himself for notifications not leading to automatic operations - can treat these events as necessary. The mobile part will inquire about the eventual need for synchronization of the event list each time access to the web server is required; thus, synchronization is frequent.

Furthermore, an additional user-configurable polling (time draw) ensures a periodic synchronization which, itself, ensures that the events do not become too obsolete even in the case of a prolonged period without access to the server. by the moving part. And, finally, for high priority events, an SMS (or other media chosen by the user, such as a synthesized voice call or an e-mail) is sent to the user, in case the priority event is imminent. and where the last synchronization is old. 11 / Reverse Messaging service: In this new method of email processing, there is only one instance of the message, which is stored on the server of the sender. The recipients of the message read the message on the server of the issuer. This mode of treatment is particularly adapted to messages between correspondents identified within the same organization or community group. When a message is sent by a transmitter E to recipients Dn, the recipients are notified that E has sent them a message. Each recipient Dn can then connect to the server E with its identifier (secure) and thus read all the message that E sent to Dn. If E sent several messages to Dn then Dn will see the list of messages that E sent to him (new and old). If the emitter E wishes to send a message to a recipient D with whom he has not established a relationship of trust, the server sends an email following the conventional method to ask the recipient if he agrees to establish a relationship of trust with E. If the recipient accepts, he is connected to E and vice versa.

This new approach to messaging allows: - to reduce the consumption of memory space on mail servers, - to actually remove unsolicited messages, or spam, because, to send a message to a recipient, it is necessary to that he has established the relationship of trust. 'In the establishment of the trust relationship, there is no possibility to pass any message or attachment, - to the issuer to know if the message has been read by one or by all recipients, - manage a new notion of a message sent to only the first ones (defined by a predetermined number by the sender of the message) which read it: an emitter E can send a message to N recipients by mentioning that as soon as at least one number X of recipients have read the message the others are no longer notified that they have a message to read, -. manage validity dates on a message, - better detect an internal or external messaging problem because if the message is not read by one or more of the recipients is that there is a potential problem. -. to limit the visibility of certain parts of the same message according to the category of recipients (restricted list management), -. to limit the diffusion / proliferation of a message by not allowing it to be repatriated locally to the recipient's post. If E does not want the message to be broadcast or retrieved by the recipient (s), it uses an encryption option that will only allow the screen copy to duplicate the content and - • remove or edit a message sent. The reverse messaging approach is appropriate for the notion of multichannel broadcast. The transmitter server can support several classes of readers: - specific applications (reader, or reader, on computer or mobile), -. using a classic email client and -. Web application (usable from a PC or phone browser). 12 / The present invention also relates to the concept of complementary widgets. That is to say, the services offered include the concept of Yin and Yang applications: two complementary services can offer a complete service (this is the case of the social signal for example, or for the restaurant reservation described ci -above). 13 / Social Signal Service: The complementary services Social Picker and Social Reader aim to offer the functionality of social presence. The Social Picker allows users to tell where they are, what they are doing, who they are with, how they are going to go through the service portal of the present invention. The social reader is an aggregator of all these flows. Each user defines who is a member of their community and follows the status updates for those members. With regard to the configuration, the social picker is a service that can be modulated by the user: he chooses, on the corresponding portal, what types of information, the category he wants to update and communicate when he will be in a situation of mobility. He can therefore choose between one and several categories (what, how, or, etc ...). An appendix category also allows him to enter a personalized text directly. After having selected the categories he wants for the social picker, the user can configure this category by adding 1 to x actions, represented by 10 images (to choose from the proposed action bank or by uploading a personalized image). The configuration of the social reader is relatively simple: it is just a question of selecting the friends whose status will be visible and updated automatically. Regarding the use: to update its status, the user will simply pick or select in the social picker the new elements that characterize it. He can therefore choose one or more categories to update. To update, he will just have to select the action icon. When he has finished updating the category or categories, he can validate and the information is sent. This information is updated and can be viewed in two different ways: - by going to the social picker of a user: by opening the social reader which then displays the last x updates of the friend profiles. Furthermore, this application can interface with other types of web services 25 since the status information can be formatted (sentence form for example) and sent to third-party services (twitter). By the principle of picking information is therefore a very innovative way to update external microblogging tools available. 14 / Notes and Images services are services that are part of the range of office services that can display content on the mobile. Thanks to the architecture of the system implementing the present invention, the ubiquity between the web and the mobile is used by these services. The content can be modified at leisure on the web, and it is automatically updated on the mobile phone. Thanks to these instantaneous technical elements of services, the uses can be many (updated shopping lists in real time by the person remained at home, collaborative work between a mobile person and another in front of a computer connected to the web , etc.) 15 / the To-do-list service is part of the office services category. This is to give the possibility to manage a list of tasks. Each task is represented by a box of the matrix and has several parameters: deadline, category, detail, title, person, etc ... and finally a button to mark the task as performed or not 16 / the Agenda service also part of the category of mobile office services. It makes it possible to follow events and is interfaced with other services which can come to insert information etc ... Thanks to the architecture of the system implementing the present invention, these services can be accessible directly via the agenda. The Agenda service can import and export information from Ical usage standards etc ... 17 / the Vote service allows the user to create a voting or election procedure, and to promote it to his friends, to get their opinion on a subject. On the portal, it is sufficient for the user to select the question, as well as the answers (and the associated image icons) and the voting service is automatically created. The user is then responsible for defining the vote audience, where it is public, to simply promote it by sending it to friends. Users who display the mobile voting service can vote by simply selecting the answer. On the portal, additional possibilities are offered concerning the results and the statistics of the vote: one can follow the evolution of the scores in the time, 20 know the number of voters etc ... In a very easy way, the users can therefore conduct real surveys and obtain valuable information on friends, customers etc ... 18 / the MCQ service (acronym for multiple choice questionnaire) is an extension of the Vote service since it is a question of Following this service Vote, any number of questions. Unlike the voting service, however, the results will not be displayed on the mobile, but will only be available on the web (and for the creator of the multiple-choice questionnaire). In the same way as for the voting service, advanced tools on the web portal allow the administration of the MCQ service as well as the collection and interpretation of the 30 results. Thanks to the architecture of the system implementing the present invention, users can therefore, in a few moments, create polls for mobiles which gives them a very interesting and instantaneous information gathering vector. 19 / The Party Planner service is a service that aims to facilitate the organization of events within a community. This is a folder that allows you to create or view events, or events. For each event, this includes: - the choice of the name, - the choice of a hearing (persons entitled to see and act on the event), - votes on the date, the place, the time. These are initial proposals by the initiator of the event but he can decide whether to accept the new proposals, -. a list of tasks (things to do, things to bring, etc ...). The audience can add items or mark as done, -. a page of information, - the integration of a conference service cati (described above) and - a page of comments, to follow the evolutions. This service is the first that allows users on the move to organize themselves without having to go back and forth. This is the first time that management tool, project management is offered to mobile users. On the portal, more advanced tools of administration and statistics are proposed. 20 / shared To-Do List service, is the first service in the range of collaborative services for project management uses, for office automation etc ... The shared to-do list is a to-do list which is editable by a group of people.

This makes it possible to organize remotely during a set of tasks to be done etc ... Via this service, people can know who should do what and especially who did what. 21 / the Ask the community service is a self-help service for questions and answers between users. When the user is traveling, in a situation of mobility, he may suddenly need information but he does not have access to the internet to search and find it. Through the service, he did not anticipate this need so he was unable to place the appropriate service in his service area, and he does not remember the service of a friend who would meet his need (and possibly is there still no service associated with this need). Thanks to the Ask the community service, he can send a question to the community and it will take care of finding the answer, since either the person will have the answer directly or will have a web access that will allow him to search the net. . In other words, this service answers the question of the user: I am in a situation of mobility, I need information but I had not planned so it is not (yet) in my service area. With the Ask the community service, people can search for information for this user.

To encourage people to respond, community tools are put in place to promote the best profiles, but the bottom line is that micro-communities respond. Regarding the configuration, on the mobile, the use of the service is to open a new question, which is typed via the phone keypad and then sent to the system. Several questions can be opened at the same time. On the other side, the community (or a micro-community) can activate to answer the question. The people (who chose who they wanted to receive requests and questions) have several ways to receive and answer questions from the service ask the community: via the web portal, via a desktop widget, via email, via instant messenger but also via a response service. Each time, the technical solution makes it possible to read the question, and to answer it. When the user has received the correct answer, he / she can close the question and archive it, which is also visible to the community, so that the latecomers can not reply. The system implementing the present invention is the first tool that connects an isolated person with a connected community. The environment keeps track of these requests and can make proposals for creating services based on the actual requests of users. The services thus created by the person, by the community or directly by the specialized developers have a very good chance to meet a real need, and to please many users. The system can also search to see if the question has not already been asked and if the answer does not exist. 22 / the Sudoku (trademark) service concerns a game well known to the general public. This service sends a 9x9 matrix and the user can then fill it at his own pace, in several times etc ... without any web access. Only when the user chooses to send the information is sent for verification etc. 23 / the Poker service implements the collaborative capabilities of the system implementing the present invention. With these capabilities, it is possible to do asynchronous poker games. That is, the game only continues when all participants have completed their action. A log makes it possible to follow these actions. 24 / the Inbox service corresponds to an Inbox folder that gathers two types of elements: - on the one hand the services that have been sent and proposed by the community (community of friends, subscriptions to services, directly by the system etc.) ...) and - on the other hand all the event logs of the services. This Inbox allows to receive all the elements. 25 / the transactional application services respond to requests that are very well known to users: horoscope, television program, cinema program, weather, RSS feeds, etc. Thanks to the architecture of the system implementing the present invention, which makes it possible to segment and profile the users of the service, it is possible to offer the content qLi will please the user or, at least, match him. By a system of filters, one proposes only the contents of which the user is likely to need. The cinema or television programs can therefore be configured on the web portal by the user but they will then be proposed dynamically, according to the defined criteria and according to similarities detected.

Claims (1)

CLAIMS1 - A method for creation, organization, delivery, operation and / or access to applications, characterized in that it comprises a step of mapping applications to a tree, at least two said applications from the web and, iteratively: - a step of displaying, on the screen of a communicating mobile terminal, representations of nodes or falling leaves of the same node or the root of the tree, - a step of selecting, on said mobile terminal, one of said displayed representations, - a step of communication, by the mobile terminal to a server, of an indication of the node or sheet corresponding to the selected representation, - if a node has been selected, a step of providing, by the server to the mobile terminal, identifiers of nodes or falling leaves of the selected node and an iteration of the steps of selection, communication and supply; e and - if an application from the web is selected, a launching step of this application. 2 - Process according to claim 1, characterized in that, if the number of representations of nodes or falling leaves of the same node or the root of the tree is less than or equal to nine, during the step display, these displays are displayed in three lines of three positions available and, during the selection step, is implemented a keyboard having at least three lines of at least three keys corresponding, by homothety, positions each of the nine keys allowing the selection of the representation in the corresponding position. 3. Process according to claim 1, characterized in that, if the number of leaves or nodes descending from the same node or the root is greater than nine, during the display step, a lower number is displayed. or equal to seven representations of nodes or sheets and at least two representations of movements for scrolling the representations of knots or sheets displayed. 4 - Process according to any one of claims 1 to 3, characterized in that, during the selection step, is implemented, in addition, a line of three additional keys to select: - from the help in the form of text superimposed on the representations, these representations taking a graphic form, - accessing the homepage, that is to say the nodes and sheets linked to the root of the tree and - of access the representations displayed before the last step of selecting a node or sheet. Process according to any one of Claims 1 to 4, characterized in that, during the selection step, a support of a duration greater than a predetermined duration causes the display of a context menu comprising at least less help with the use of the corresponding node or sheet. 6. Process according to any one of claims 1 to 5, characterized in that, before said iterations, in response to an initial navigation request, the server provides identifiers of nodes or sheets, the first selection step being performed on the nodes or sheets provided by the server responds to the initial navigation request. 7 - Process according to any one of claims 1 to 5, characterized in that, before said iterations, the mobile displays identifiers of nodes or sheets stored in memory by said mobile. 8. Process according to any one of claims 1 to 7, characterized in that at least one said application is such that once initiated, at least one new iteration is performed. 9 - Process according to any one of claims 1 to 8, characterized in that, during each supply step, the server provides, in advance, at least the matrices of nodes or sheets to be displayed after each possible selection. . A method according to any one of claims 1 to 9, characterized in that, during the step of mapping applications to a tree, services are mapped to said tree and each sheet corresponds to to content of a service or an application. 11. A method according to any one of claims 1 to 10, characterized in that, during the mapping step, hyperlinks of pages are mapped to nodes of the tree. The method of any one of claims 1 to 11, characterized in that, during the mapping step, page contents are mapped to tree sheets. 13. Process according to any one of claims 1 to 12, characterized in that it comprises a step of accessing the server from a second terminal, a display step, on a portion of a page displayed on the screen. screen of said second terminal, representations as they appear during the iterations, on a screen of the mobile terminal. 14. Process according to claim 13, characterized in that, during a tree creation step, a user implements the second terminal and slides or copy-pastes representations into the portion of the displayed page. simulating the representations as they would appear on the screen of the mobile terminal to perform the matching step. A method according to any one of claims 1 to 14, characterized in that, during the selection step, if a user presses a first predetermined keyboard key different from the keys 1 to 9, the display on the communicating mobile terminal screen goes back and displays what was displayed an iterative cycle earlier. A method according to any one of claims 1 to 15, characterized in that, during the selection step, if a user presses a second predetermined keyboard key different from the keys 1 to 9, the display on the screen of the communicating mobile terminal returns to the first iteration. 17. Process according to any one of claims 1 to 14, characterized in that, during the selection step, if a user presses a third predetermined keyboard key different from the keys 1 to 9, the display on the screen of the communicating mobile terminal has explicit titles of the nodes and sheets displayed. 18. Process according to any one of claims 1 to 17, characterized in that, during the selection step, if a user makes a long press on a keypad key among the keys 1 to 9, one opens a context-sensitive help related node or sheet corresponding to said key on which is made a long press. 19 - Process according to any one of claims 1 to 18, characterized in that at least a portion of the computer applications corresponding to the leaves of the tree are among the following: - download and / or display a text, - download and / or display a photo, - download and / or play (streaming) a music file, 25 - download and / or play (streaming) a video file, - trigger a phone call (with 1 or more people), - trigger sending SMS (acronym for short message system for short message system) or MMS (acronym for multimedia message system for multimedia message system), 30 - triggering the sending of electronic messages (mails), - choose in a or lists and transmit the choice to the server, - fill a form or form (in English template) then transmit it to the server and - invoke a predefined web service. The method according to any one of claims 1 to 19, characterized in that it comprises a personalization step, by a user of the tree implemented in response to navigation requests from his communicating mobile terminal. 21. Process according to any one of claims 1 to 20, characterized in that it comprises a step of defining an explicit user profile, by said user, the behavior of at least one computer application associated with a leaf of the tree varying according to the explicit profile of the user. 22 - Device for creation, organization, delivery, operation and / or access to applications, characterized in that it comprises means for mapping applications to a tree, at least two so-called applications from the web and: a means for displaying, on the screen of a communicating mobile terminal, representations of nodes or falling sheets of the same node or the root of the tree, - a selection means, on said mobile terminal, of one of said displayed representations, - means of communication, by the mobile terminal to a server, of an indication of the node or sheet corresponding to the selected representation, - a means of supply, by the server to the mobile terminal, node identifiers or falling leaves of the selected node if a node has been selected for the display, selection and communication means to perform a new iteration and - a means of launching an application from the canvas if its representation is selected. 23 - Computer program, characterized in that it comprises instructions executable by a computer to implement the method according to any one of claims 1 to 21. 24 - Computer readable information medium and having executable instructions by a computer for implementing the method according to any one of claims 1 to 21.