FR2823333A1 - INTERACTIVE TERMINAL SYSTEM WITH MULTI-APPLICATION CENTRAL EQUIPMENT AND PERIPHERALS - Google Patents

Abstract

The invention relates to the central equipment (1) of an interactive terminal system (ST) comprising a browser (5) which is dispatched towards the small peripherals (21-31 to 2I-3I). Following a first request (RQP) and following a predetermined message transmitted by the first peripheral (21), the navigation means opens a session of second requests and responses (RQL, RQD; RSL, RSD) with a server (6; SD) and delivers the second response to the second peripheral (31) in the form of at least one first response (RSP). Said first response comprises a predetermined number of data messages which are each transmitted to the second peripheral following a predetermined message produced by the first peripheral (21). The browser (5) can open several sessions following several simultaneous requests (RQP). Each pair of peripherals of the type with buttons (211-214) and a display device (311) benefits from the functionalities of the browser independently of the other peripherals.

Description

<Desc / Clms Page number 1>

Interactive terminal system with multi-application central equipment and peripherals
The present invention relates generally to an interactive terminal system allowing the consultation of information and the control of applications. It relates more particularly to such a system comprising central equipment and peripherals.

 Many terminals are currently capable of being connected to a remote telecommunications network, for internet services for example. In addition to personal computers PC, one can quote in particular personal digital assistants PDA, internal tablets, MP3 audio players, advanced modems, etc.

 These terminals are generally equipped with at least a display and a keyboard, and include an intelligent central unit comprising a navigation software which sends requests to a network server to which they are connected and which renders results of the requests under form of text, graphic or audiovisual responses.

 The navigation software, called the browser, switches the display of one hypertext document to another by means of hypertext links, the transmission of requests to the server and the reception of responses established by the server. A hypertext or more generally hypermedia document contains a set of data relating to text, still or animated images and sound, and is formatted by text tags used to describe and render the document according to a layout adapted to the viewer. of the terminal system. Each document

<Desc / Clms Page number 2>

 hypertext is designated by a URL (Uniform Resource Locator) address which is used to find it at the destination server and to establish links with the document. When the user interface of the terminal, generally composed of a keyboard and a screen, requests the return of a hypertext document to the server, the browser must provide the address of the document either by explicitly indicating it, or by means of a hypertext link.

 Known browsers have several drawbacks which cannot be used in a terminal system architecture which is distributed from a central processing unit to various peripherals.

 Known browsers allow the consultation of several documents respectively in several windows, which consultation can only be carried out by the sequential transmission of requests each corresponding to the passage from one window to another, only one window being active at a time. For example, a browser does not allow two user keyboards to request that requests be sent simultaneously on two separate windows. Conversely, a browser does not allow multiple users to retrieve documents simultaneously from different displays.

 In addition, there is a one-to-one correspondence frozen between a request and a window, the restitution of a document being always carried out on the window which launched the request. It is therefore not possible to switch the result of a query launched in one window to another window.

<Desc / Clms Page number 3>

The present invention aims to remedy the main aforementioned drawbacks and more specifically to provide an interactive terminal system in which peripherals not comprising a browser and constituting the user interface of the system independently of other peripherals benefit from the functionality of a single means. of navigation implemented in a central equipment, while allowing interoperability between the peripherals and a great flexibility in the request and the restitution of documents.

 To this end, an interactive terminal system comprising a central equipment, at least a first peripheral, and at least a second peripheral, is characterized in that the central equipment comprises a means of navigation towards a server means, which receives as many types first request transmitted by the first device that means of action included in the first device and which restores first responses adapted to the second device.

 In general, the navigation means can open a session of second request and response with the server means.

 Each first response can be of the text, or graphic, or image type. Each first response can be transmitted in the form of data messages having a length compatible with the data processing capacity of the second device. Each data message transmitted by the navigation means can be preceded by an activation message transmitted by the first device to the navigation means.

<Desc / Clms Page number 4>

 A first request may be a message which indicates that the second device is ready to receive as the first response the start of a home page and which follows a request for ready status message transmitted by the navigation means to the second device. before the expiration of a predetermined time delay.

 A first request may include a reference to one of the means of action requested in the first device, in particular for the second device to receive another first response making up the second response after shaping, or a first response already transmitted.

 A first request may also include a reference to one of the action means requested in the first device, said reference being interpreted by the navigation means as a file address in the server means, when a line in the first response containing a file designation has been selected in the second peripheral by the command means requested.

 The navigation means according to the invention makes it possible to broadcast the result of a request in a first response to at least one determined second device selected in a first device and different from the second device associated with the first device following a first request. designating said at least second determined peripheral.

 The navigation means can manage several first requests simultaneously coming from several different first devices and therefore a priori used by different users. More particularly, the navigation means can open

<Desc / Clms Page number 5>

 several sessions following several first simultaneous requests transmitted respectively by first peripherals to the central equipment.

 In the navigation means of the invention, certain first responses do not require a first request from a first device beforehand, unlike browsers according to the prior art which cannot send a response to a device without first having the latter l 'asked, either directly by an action of the user on the device, or by an automatic function in the device. In this regard, preferably, the navigation means of the invention matches a predetermined session identifier with at least one second predetermined device so that the navigation means broadcasts a first response to said at least one second predetermined device independently of any first request received by the navigation means, following a second response containing the predetermined session identifier and transmitted by the server means to the navigation means.

 The navigation means thus plays the role of display server for the peripherals and client for the server means in response to first requests from the peripherals so as to retransmit hypermedia documents read in the waiter medium to the designated peripherals.

 According to a preferred embodiment of the invention, the navigation means can comprise a request management means for converting first requests transmitted by first devices into second requests which designate the server means, respectively contain identifiers

<Desc / Clms Page number 6>

 session and are transmitted to the server means, a correspondence means for matching a respective session identifier to any second device designated in each first request, and means for converting each second response transmitted with a respective session identifier into at least one first response respectively switched to any second peripheral corresponding to the respective session identifier in the correspondence means.

 The server means can comprise a remote server connected at least by a telecommunications network to the central equipment, and / or a local server and a memory containing at least hypermedia pages in the central equipment. In the latter case, a local server exchanges second requests and responses with the navigation means in order to introduce into second responses in particular hypermedia documents read from the memory.

 According to a variant of the invention increasing the possibilities of access of the peripherals to numerous documents, the terminal system can comprise a means remote from the central equipment for transmitting a request relating to a determined document requested by a first peripheral in a format , such as HTML, which cannot be returned by the navigation means or a server means included in the central equipment, to a remote server and for translating the requested document returned by the remote server into a format, such as WML, suitable for a second device associated with the first device in order to transmit the document adapted to the browser or to the local server to the second device.

 The server means in the central equipment may include means for executing programs in

<Desc / Clms Page number 7>

 function of parameters contained in second requests and possibly of pages of files read in the memory in order to establish and transmit second responses to the navigation means.

 The means for executing can comprise means for interrogating a mailbox in a remote server following a second request containing an identifier of the mailbox designated by a first device and for entering information retrieved from the mailbox in a second response intended for a second device associated with the first device, and / or a means for delivering a home page to a second device determined following a second request sent by the navigation means at the request of a first device associated with the second peripheral device.

 According to certain embodiments of the invention, the means for executing may comprise means for transmitting in a second response a form read in the memory to a second peripheral associated with a first peripheral having requested it and for constructing a home page intended to the second device as a function of the completed form retransmitted by the first device, then in a second request from the navigation means, and / or a means for replacing a home page for a second device with a page recently received by the latter , and / or means for replacing a home page for a second device with a page selected from a memory file system.

 According to particular embodiments of the invention, the means for executing may comprise means for generating a page of source commands

<Desc / Clms Page number 8>

 sound in a second response to a second predetermined peripheral and for controlling sound reproduction via at least one sound source in the central equipment as a function in particular of an audio file identifier and of commands returned in a second request via the navigation means from a first device associated with the first predetermined device, and / or may comprise means for generating an order page of a high-fidelity chain in a second response to a second predetermined device and for retransmitting an order contained in a second request transmitted via the navigation means from a first device associated with the second device, in a second response intended for another second device controlling the high-fidelity chain. The high-fidelity chain can constitute a second peripheral connected through a sound adaptation means to the means for executing in the central equipment in order to retransmit sound from local and / or distant sound sources towards the high-fidelity chain.

 In practice, a first device and a second device are included in a common pocket box including a microcontroller, control buttons and a display. The central equipment is then adapted to the type of pairs of first and second peripherals, in particular to adapt the first responses to the display characteristics of the second peripheral, for example in order to personalize a home page and other information dedicated personally to the user of the housing. In particular, the navigation means offers each user of a peripheral unit,

<Desc / Clms Page number 9>

 information adapted in custom formats in order to trigger predetermined local applications in the local server. Each peripheral unit has no browser and benefits from the functionalities of the navigation means distributed according to the invention, which reduces the cost of the peripheral unit.

- la figure 2 est un bloc-diagramme d'un couple de premier et deuxième périphériques selon l'invention ; - la figure 3 est un diagramme d'échange de messages entre un navigateur distribué de l'équipement central et le couple de premier et deuxième périphériques ; la figure 4 est un algorithme de phase d'initialisation dans le navigateur de l'équipement central ; la figure 5 est un algorithme de requêteréponse d'affichage dans un automate de microcontrôleur du couple de premier et deuxième périphériques ; - la figure 6 est un diagramme de requêtes et réponses entre des périphériques, le navigateur distribué et des serveurs ; et - la figure 7 est un bloc-diagramme fonctionnel d'un moyen de traduction de format de document selon une variante de l'invention. Other characteristics and advantages of the present invention will appear more clearly on reading the following description of several preferred embodiments of the invention with reference to the corresponding appended drawings in which: - Figure 1 is a block diagram of a system interactive terminal according to the invention;

- Figure 2 is a block diagram of a pair of first and second peripherals according to the invention; - Figure 3 is a message exchange diagram between a browser distributed by the central equipment and the pair of first and second peripherals; Figure 4 is an initialization phase algorithm in the browser of the central equipment; FIG. 5 is a display response request algorithm in a microcontroller automaton of the pair of first and second peripherals; - Figure 6 is a request and response diagram between devices, the distributed browser and servers; and - Figure 7 is a functional block diagram of a document format translation means according to a variant of the invention.

<Desc / Clms Page number 10>

 With reference to FIG. 1, an interactive terminal system ST according to the invention comprises interactive central equipment 1, for example installed substantially in the center of an apartment or a pavilion, at least one first device, called request device, and at least one second device, called the response device. More generally, the terminal system ST comprises several first peripherals 21, 22, ... 21 and several second peripherals 31, 32, ... 31. The number I of peripherals with I 2 1 is not fixed a priori and can dynamically evolve as the needs and connections of peripherals to the equipment evolve. The equipment is capable of communicating with one or more remote servers, an SD of which is represented in FIG. 1, through a user telecommunications line LT and a telecommunications network RT including a packet network such as the internal network .

 The first peripherals 21 to 21 are respectively connected to input ports 121 to 121 of the equipment 1 by which they in particular transmit first RQP requests. Output ports 131 to 131 of the equipment 1 respectively serve the second peripherals 31 to 31 and transmit to them first RSP responses. Although in particular a first device can be physically linked to a second device in the same small box, it will be considered below that the first and second devices are distinct. When a first device and a second device are linked, the corresponding input and output ports can constitute a bidirectional port which can be a serial port, or a

<Desc / Clms Page number 11>

 parallel type port, or a USB bus (Universal Serial Bus).

 Alternatively, instead of wired links between the central equipment and the peripherals, one of, or more, or all of the peripherals 21-31 to 21-31 are connected to the equipment 1 through a link manager 4 which manages the establishment and termination of proximity digital radio communications between the equipment and the peripherals, as shown in dotted lines in FIG. 1. Typically, the proximity radio links conform to the Bluetooth protocol, or more generally to any proximity digital radio system protocol, and the peripherals are recognized by the central equipment within a coverage radius of a few tens of meters. After establishing communication with a pair of peripherals, the requests and responses exchanged between the pair of peripherals and the equipment pass transparently through the link manager 4.

 The central equipment 1 is permanently energized and periodically scans the input ports 121 to 121 so as to detect there messages signaling the presence of peripherals following their energization. A user possessing a pair of peripherals, such as the pair 21-31, accesses the equipment 1 almost immediately to start navigation by means of a browser 5 included in the equipment, after a delay of one second. approximately following the power up of the peripherals.

The access time to information, particularly local information in the equipment, is very reduced compared to putting a personal PC computer into operation.

<Desc / Clms Page number 12>

 Typically, a request device, such as the device 21, simply comprises four means of action such as command buttons 211 to 214.

The four buttons 211 to 214 allow a user to transmit respectively four types of RQP request to the equipment 1. The buttons 211 and 212 provide scrolling up and down functions on a display 311 in the response device 31 associated with the peripheral 21. The button 213 allows validation of information by returning a control character to the equipment.

The button 214 gives the possibility of returning to a previous page of display. The basic functions provided by the four buttons 211 to 214 allow the user to navigate through hypertext and more generally hypermedia documents. The buttons 211 to 214 can be push buttons or tactile keys for example.

 The display 311 includes a liquid crystal display and comprises for example N = 4 lines LI to L4 each of twenty characters with lighting.

(eXtended Markup Language) adaptée à la norme d'affichage WAP (Wireless Access Protocol) pour terminal radiotéléphonique. Le format WML est essentiellement textuel et volontairement concis afin que la consultation sur l'afficheur 311 de petite taille ne soit pas trop pénible. Typically, the characteristics of the second peripheral 31 are adapted after layout into small pages to display textual information of WML type, that is to say of small pages according to the description standard for layout of XML documents.

(eXtended Markup Language) adapted to the WAP (Wireless Access Protocol) display standard for radiotelephone terminals. The WML format is essentially textual and deliberately concise so that consultation on the small 311 display is not too difficult.

<Desc / Clms Page number 13>

 As shown in FIG. 2, the peripherals 21 and 31 have in common a microcontroller 215 without a browser. The microcontroller 215 comprises a protocol automaton 216 for controlling the link between the central equipment 1 and the buttons 211 to 214 and the display unit 311, and an input / output manager 217 for adapting in particular the size of data messages exchanged with the navigator 5 with the length of the display lines in the display 311. The peripherals 21 and 31 include a link interface 218 compatible with the link manager 4 of the equipment 1. A small pocket case, similar to that of a device for receiving messages, known as a "pager", encloses the peripherals 21 and 31 and has buttons 211 to 214 and the display 311 on the front face.

 In the pair of peripherals 21-31, the automaton 216 establishes a protocol exchange with the equipment 1 at an initialization phase IN during which the pair of peripherals indicates its presence to the browser 5 in the equipment 1 and the browser indicates that it is finally ready to receive requests and transmit responses. The browser then loads a configurable home page containing personalized user services. A home page can be any WML page which generally includes a series of links constituting a "portal", that is to say referring to a series of external sites containing information on particular themes, for example stations radio programs broadcast internally, news, sport and stock market and / or links to local files such as messaging, cooking recipes, audio files, high-fidelity channel (Hi-Fi). WML language allows formatting

<Desc / Clms Page number 14>

 text in drop-down form and adapted to the rendering capabilities of peripherals and hypertext mechanisms. The browser can add "footer" links to any current page that is not the home page, such as a link to return to the home page, a link to a URL (Uniform Resource Locator) ) for example a script or executable program CGI (Common Gateway Interface) allowing to establish the current page as home page, and a link allowing to explore local WML files in the central equipment.

 As shown in FIG. 4, with reference to the beginning of FIG. 3, an initialization phase IN in the browser 5 so that it loads the home page in the devices 21-31 comprises steps II to 15.

message sur le port 121, le navigateur 5 émet un message de demande d'état"Prêt ?"à l'automate 216, à l'étape 12. La demande"Prêt ?"signifie que le navigateur souhaite savoir si le microcontrôleur 215 est prêt à accepter les données de la page d'accueil. In step II, the browser 5 monitors the input port 121 corresponding to the peripheral 21, awaiting an "I am present" message to be sent by the protocol controller 216. As soon as an activity is signaled by receiving at least one character from

message on port 121, the browser 5 sends a status request message "Ready?" to the controller 216, in step 12. The request "Ready?" means that the browser wants to know if the microcontroller 215 is ready to accept data from the home page.

The browser then goes into a listening state of the input port 121, waiting for a message "Ready!" transmitted by the controller 216. In steps 14 and 15, as long as the browser has not received a message ["Ready!" upon reception of a home page] during a predetermined TPN timeout, or else has received a message different from "Ready!", the initialization phase returns to step 12. As soon as the

<Desc / Clms Page number 15>

 browser 5 received a "Ready!" message in step 14, the browser finishes initialization and will look for a home page for the devices 21, 31 in a local server 6 in response to a first activation message DTR (Data Terminal Ready) transmitted by the peripheral 21 and preceding the first data message relating to the line LI of the home page to be formatted and transmitted to the peripheral 31.

 The processing capacity of the microcontroller 215 is relatively limited and its processing speed relatively low. The size of the data messages, which may each include one or more line characters or bytes, exchanged with the browser 5 are adapted to this processing capacity.

 The protocol exchange in the microcontroller of the peripherals 21 and 31 to load the home page after the initialization phase (FIG. 4) or more generally to load any page constituting one or more first RSP responses transmitted by the browser 5, to following an RQP request initiated by the request of a command button 211 to 214, is governed according to the display request-response algorithm shown in FIG. 5, comprising steps P1 to P7 after phase d initialization IN.

 By way of example, FIG. 3 shows a WML home page comprising a first small AGI page with a title "Portal-XXXX" and two "News" and "Sports" headings on lines L3 and L4 which can be selected, and following the pressing of the scroll down button 212, a second small page AC2 with four headings "Stock exchange", "Horoscope", "Transport" and "Local files". Figure 3 also shows a

<Desc / Clms Page number 16>

first page of local information made up of at least a first small PAl page with four local "Messaging" ... "HiFi" sections after validation of the "Local files" section in the second small AC2 home page by the validation button 213; and a second page of remote information PA2 composed of at least four sports sections following the validation of "Sports" on the home page. The symbol "." Indicates the character "space".

Returning to FIG. 5, for each of the N = 4 lines L1 to LN = L4 to be displayed from the home page, as shown at the top of FIG. 3, or from any page PA1, PA2 as also shown in the FIG. 3, the memory in the microcontroller 215 retrieves the display information line by line transmitted by the central equipment 1 in step Pi.

The display of a data message (line) is preceded by a DTR activation message transmitted by the controller 216 to the equipment 1 in order to indicate to the browser that the peripherals 21-31 are ready to receive a line. text to display. The line-by-line loading protocol is a simple flow control which optimizes the display speed in the peripheral 31 according to the processing capacities of the microcontroller 215.

 For the sake of simplification, it is assumed in FIG. 3 that each data message transmitted after a DTR activation message comprises data for one line of the display 311, although often, in practice, several data messages, each preceded by a DTR message, are transmitted to display a complete line through the manager 217.

<Desc / Clms Page number 17>

correspondant à la requête précédente RQP, à l'étape PI. After N = 4 cycles each comprising a DTR activation message from the peripheral 21 to the browser 5 followed by a line transmission of the page to be displayed by the browser 5 to the peripheral 31, so as to display a composed RSP response page from N = 4 lines L1 to L4 in the display 311 in step P2, the controller 216 of the peripherals 21 and 31 monitors any request for buttons 211 to 214 in step P3. Pressing one of these buttons in step P4 triggers the transmission of a first specific RQP request containing a button reference, such as the button number, by the controller 216 to the browser 5 at the step P5. The RQP request is followed by a DTR activation message to signal to the browser that the devices 21-31 desire a page to be displayed. After the RQP request and the DTR message, the controller 216 returns to the reception state of the first line of a page

corresponding to the previous request RQP, in step PI.

If no button in step P4 is pressed, the microcontroller 215 of the peripherals 21-31 remains in a state of listening to the connection with the browser 5. At the expiration of a predetermined time delay TPP, if no message or control character is not received in step P7, monitoring continues again in step P3. On the other hand, in response to a control character transmitted by the browser 5 in step P7 for a broadcasting mode described below, the microcontroller 215 switches from the listening state to the initial reception state PI from a line to display.

 The browser 5 is transmitted in an RSP response consisting of N = 4 messages of display lines of "local" data which it has in

<Desc / Clms Page number 18>

 memory if for example the scroll button 211 or 212 was pressed as shown at the level of the transmission of the page PAl in FIG. 3, either transmits a second request RQL, RQD and waits for a second response RSL, RSD, as is will see below, when for example the validation button 213 has been pressed in order to retransmit an RSP response relating to the page PA2 as shown at the bottom of FIG. 3.

 The central equipment 1 essentially comprises the distributed browser 5 and a local server 6. The equipment communicates with the peripherals through a communication interface adapted to them, such as the link manager 4, and with the remote servers SD through a TCP / IP or UDP / IP communication interface. The equipment 1 does not include any graphics card, the functionalities of which are developed in the peripherals 31 to 31. The "multi-application" nature of the central equipment is based on an operating system of the LINUX type for example.

 The navigator 5 is connected to the device pairs 21-31 to 21-31 by the ports 121-131 to 121-131, if necessary through the manager of proximity digital radioelectric communications links 4. For each pair of devices, the browser 5 independently supports all the usual functions of a conventional browser relating to homepages (homepages) adapted respectively to the second device, the history of the WML pages already visited by the devices and particularly at least the last page displayed, preferred hypertext links, etc.

<Desc / Clms Page number 19>

 The browser 5 is connected inside the equipment 1 to the local server 6, as well as to at least one remote server SD through the telecommunications line LT, and behaves like a client with respect to the servers 6 and SD . At the request of the browser-client, connections are established between the browser 5 and each of the servers 6 and SD in the form of TCP sessions by means of TCP / IP (Transmission Control Protocol / Internet Protocol) packets exchanged between them. Alternatively, the User Datagram Protocol (UDF) transport protocol is used in place of the TCP protocol. During each session, the browser and the server 6 or SD interact at the application level by exchanging data. These data are for example hypertext documents designated by URLs (Uniform Resource Locator) and formatted according to the WML language in the HTTP protocol (HyperText Transfer Protocol), or else e-mail messages exchanged between a POP server (Post Office Protocol) ) and POP client software hosted at server level 6 in device 1.

Second RQL and RQD requests are based on the HTTP protocol and transmitted by the browser 5 respectively to the local server 6 and the remote server SD. Second RSL and RSD responses are also based on the HTTP protocol and contain in particular hypermedia documents and transmitted respectively by servers 6 and SD to the browser 5. Within the meaning of the invention, a hypertext document is a hypermedia document containing text and / or still or moving image (video) and / or sound.

 From a functional point of view, the browser 5 mainly comprises, as shown in detail in FIG. 1, a request manager 51, a table

<Desc / Clms Page number 20>

 52, a document interpreter 53 and a port switch 54.

 The request manager 51 is connected to the input ports 121 to 121 and centralize the first RQP requests sent by the first peripherals 21 to 21. Each request received on a predetermined input port is assigned a network session identifier IS , such as a session number, assigned by the manager 51. The manager 51 thus permanently scans the input ports 121 to 121 to detect the first requests there. In addition, the manager 51 and the interpreter 53 keep in memory an image or current page of the latest information displayed in each second peripheral 31 to 31 and restored by the interpreter 53 so as to be able to correctly interpret an action of the user under the form of a reference to one of the buttons 211 to 214 in each first device.

 The manager 51 converts each first RQP request designating a server or a file in a server into a second RQL or RQD request transmitted in the telecommunications line LT to the designated server, for example which is the local server 6 in the equipment 1 or the remote server SD connected to the telecommunication network RT. The manager 51 considers the number of the input port having received an RQP request as an IS session identifier according to the TCP or UDP transport protocol and introduces into the RQL or RQD request the address of the server designated in the RQP request as as destination address and port number

<Desc / Clms Page number 21>

 IS input port that received the RQP request in the application source port (socket).

 Before the conversion, the manager 51 verifies that access to the designated server is authorized for the first device which issued the RQP request. The access rights of a pair of peripherals, such as the pair 21-31, can be different from those of other pairs of peripherals so that each pair of peripherals respectively access respective local applications in the server 6 and respective remote applications in at least the remote server SD. For example, a pair of peripherals 21-31 dedicated to parents is authorized to access local applications in the server 6 such as consulting an electronic mailbox, while another pair of peripherals 22-32 dedicated to parents. children is not authorized to access the electronic mailbox but can access playful applications in predetermined remote servers for example.

 The correspondence table 52 stores the correspondences between the session identifiers IS and the NPS output port numbers designated in first RQP requests. The content of table 52 changes as a function of the connection or disconnection of the peripherals to the ports of the equipment 1 and as a function of the availability of the sessions on the RT network. The correspondence table is constantly updated by the request manager 51 and consulted by the interpreter 53.

 Each RSL, RSD response contains in the destination port the IS network session identifier corresponding to the source port in the second RQL, RQD request received by the corresponding server.

<Desc / Clms Page number 22>

 6, SD in order to read the NPS output port number (s) from the correspondence table 52 corresponding to the received session identifier IS. The data, in particular hypertextual, received in each RSL, RSD response in a format, in particular of the WML type, are converted by the interpreter 53 into data messages the length of which is compatible with the data processing capacity of the protocol automaton. 216 which supplies these data messages to the manager 217 in order to format them as display lines for the display 311 per small page of at most N = 4 lines. The interpreter temporarily stops the transmission of data messages as soon as it no longer receives a DTR activation message, which means that a small page has been transmitted. These interpretation and splitting of RSL, RSD responses into data messages are adapted to the rendering capacities of the second peripheral (s) connected to the corresponding output ports whose numbers have been found in the correspondence table 52. The interpreter then controls the switch ports 54 so that the data thus formatted are routed to the corresponding second peripheral (s).

 When no second peripheral 31 to 31, that is to say no output port 131 to 131, is designated in a first RQP request, the manager 51 associates by default the output port, for example port 131 of the second peripheral 31 which is linked to the first peripheral 21, to the input port 121 according to the example in which the RQP request is detected without an output port number, as indicated in a first line of the table 52.

 If one or more output ports, such as 132 and 133, are designated in an RQP request, the

<Desc / Clms Page number 23>

 manager 51 establishes a dynamic correspondence in table 52 by writing the session number IS relating to the input port, for example 122, which received the RQP request in correspondence with the designated output port or ports, as indicated in a line table 52, so that the interpreter 53 broadcasts small RSP response pages to the second devices connected to the designated output ports.

 The request manager 51 in the browser manages several RQP input requests transmitted simultaneously by different first peripherals 21 to 23 and therefore a priori used by different users. Likewise, the correspondence table 52 is consulted simultaneously by the interpreter 53 to convert second RSL and RSD responses transmitted respectively by the local server 6 and the remote server SD into first RSP responses to the second peripherals 31 to 31 through the port switch 54 and the output ports 131 to 131. Under these conditions, the management of the first RQP requests and therefore of the first "keyboard" type devices 21 to 21 by the manager 51 is independent of the management of the first RSP responses and therefore second peripherals 31 to 31 of the "display" type by the interpreter 53.

 By way of example, FIG. 6 shows the simultaneity of the management of two requests RQP1 and RQP2 transmitted by the peripherals 21 and 22 following the solicitation of determined buttons, for example respectively the validation button to validate the transmission of a document from the remote SD server to the peripherals

<Desc / Clms Page number 24>

RSP1 aiguillée vers les périphériques 31 et 33 par le commutateur 54, à la suite de la lecture des numéros de port de sortie NPS 131 et 133 en correspondance avec l'identifiant IS = 121 dans la table 52. selected 31 and 33 and the button to return to the previous page. In response to the request RQP1, the manager 51 opens a session with the remote server SD designated in the request RQP1, maps the session identifier 121 to the output ports 131 and 133 in the table 52 and transmits a request to the server SD HTTP RQD1. In response to the RQP2 request, the manager opens a session with the local server 6 designated in the RQP2 request, assigns by default to the session identifier 122 the output port 132 and transmits to the server 6 an HTTP RQL2 request. The local server 6 retransmits an RSL2 response containing the previous hypertext page which is converted into at least one RSP2 response and routed by default to the peripheral 32 by the interpreter 53 and the switch 54. When the interpreter 53 receives an RSD1 response from the SD server, it converts it into a suitable response

RSP1 routed to the peripherals 31 and 33 by the switch 54, after reading the NPS output port numbers 131 and 133 in correspondence with the identifier IS = 121 in the table 52.

 According to a particular aspect of the invention relating to a broadcast mode (FIG. 5), the interpreter 53 broadcasts at least one RSP response to one or more second predetermined peripherals 31 to 33 independently of the reception of a specific RQP request by the request manager 51 sent by one of the first peripherals linked to the second predetermined peripherals, that is to say independently of any voluntary user action on the first peripherals 21 to 21.

<Desc / Clms Page number 25>

 In this case, the correspondence table 32 has previously stored the correspondence between a predetermined session identifier IDP and the output port numbers 131, 132 and 133 connected to the second predetermined peripherals 31, 32 and 33, as indicated on a last line in the table 52.

The predetermined session identifier IDP (socket) is reserved for broadcasting data to predetermined devices. The identifier IDP identifies in at least one server, such as the server 6, SD, a destination port linked to a predetermined application and introduced into a determined response RSL, RSD of the server. The determined response contains, for example, an advertising banner or personal information, such as the deposit of a message in an electronic mailbox. The server 6, SD transmits this determined response to the interpreter 53 for example when the equipment 1 is put into operation and after a protocol exchange between the server 6, SD and the browser 5, or else after the opening of one of predetermined sessions with the server by the browser, that is to say in particular when launching one of the predetermined applications. In all cases, the interpreter 53 in the browser 5 takes the initiative in broadcasting the determined response RSL, RSD in the form of one or more small pages of RSP response to the second predetermined peripherals 31, 32 and 33.

 Following the determined response received RSL, RSD, prior to the broadcasting of any small RSP page, the interpreter 53 transmits a predetermined message or control character (step P7; FIG. 5) to the protocol automats 216 in the second peripherals predetermined connected to the ports of

<Desc / Clms Page number 26>

 designated outputs in order to make them switch from the button request waiting state (step P4, FIG. 5) to the line message reception state (step PI, FIG. 5).

 Thus, the correspondence table 52 is configurable statically or dynamically to make an input port, called session identifier, correspond to one or more output ports, depending on whether the correspondence was introduced by an RQP request or was preprogrammed in the browser. Thus an RQP request can be restored to any second device.

 For example, the selection of a link of the type "display the weather in the device 23-33" in the device 21-31 invites the manager 51 in the browser 5 to write the correspondence [IS = 21, NPS = 33] in table 52 and to open a session with a remote weather server which returns an RSD response containing a destination port IS and meteorological information which is converted by the interpreter 53 into at least one RQP response routed to the peripheral 33.

 The local server 6 hosts a home portal. WML pages making up the home portal are stored locally in a mass memory 7 which can be a hard disk or a non-volatile memory of the EEPROM or Flash EEPROM type for example. The server 6 reads home application pages in the memory 7 via a link 67 under the control of the RQL queries of the browser 5 and returns RSL responses which are interpreted and routed by the browser 5 respectively to the peripherals 31 to 31.

<Desc / Clms Page number 27>

comptes tels que comptes d'accès à internet et comptes de messagerie, des pages HTML, des fichiers audio MP3, une boîte aux lettres locale électronique (messagerie), un agenda, etc. Dans un exemple de réalisation, des pages HTML dans la mémoire 7 servent à configurer une page d'accueil WML en choisissant un sous-ensemble de rubriques parmi une liste pré- établie. Le serveur local 6 peut également décider de donner accès à des informations précises telles que l'actualité, la bourse, des résultats sportifs, des horaires de transport, etc. dans des sites extérieurs à travers le réseau RT. The memory 7 contains not only WML pages organized in a tree structure as well as other local data such as for example configuration files in order to choose a home page associated with a playback device 31 to 31, history files, identifiers of

accounts such as internet access accounts and email accounts, HTML pages, MP3 audio files, local electronic mailbox (email), calendar, etc. In an exemplary embodiment, HTML pages in the memory 7 are used to configure a WML home page by choosing a subset of headings from a pre-established list. The local server 6 can also decide to give access to precise information such as news, the stock market, sports results, transport schedules, etc. in external sites through the RT network.

 Based on executable links contained in RQL requests, the local HTTP server 6 transmits parameters to executable programs, for example scripts or executables CGI (Common Gateway Interface) in an interaction manager 8 which returns a WML page to the server 6 via a link 68. The interaction manager 8 allows a CGI program, by implementing relatively simple functions, to retrieve parameters by means of an HTTP RQL request associating a URL address designating the program with a GET method or POST, which is transmitted to it by the HTTP server 6. In return, the manager 8 provides a WML page or more generally data encapsulated in a RSL response of the HTTP protocol.

<Desc / Clms Page number 28>

Instead of locally providing WML pages by the server 6, a variant of the invention provides for translating HTML pages into WML pages outside of the central equipment 1 so that the pairs of peripherals access formats of much more data. The adaptation of the content is carried out by a PR-SC translation means in the RT network which, in response to a specific request, will seek information and adapt the content thereof in order to respond to the client in a suitable format. . Functionally, the translation means comprises a PR format conversion proxy and a content server SC as shown in FIG. 7.

 One of the first peripherals 21 issues an RQP request for a determined document that the browser 5 or the server 6 is not capable of rendering directly, for example "http: // www. Actualite. Fr / article. Html". The browser 5 or the server 6 transmits to the proxy PR a request containing a reference to the determined document, but the format of which is not adapted to the rendering capabilities of the associated device 31, for example "ADAPT http: // www. Actualite .com / article. html ". The PR proxy extracts the URL address of the request and sends a request relating to the document in question to the content server SC: "GET http: // www. Actualite. Fr / article. Html". The content server returns the determined document by entering it in a "<! DOCTYPE html ...> <HTML> ..." response. The PR proxy adapts the format of the response according to the translation rules, in this case HTML to WML, which it has. The proxy response to device 1 is "<! DOCTYPE wml ...> <WML> ...". Browser 5 or server 6

<Desc / Clms Page number 29>

 interprets and renders the document to device 31.

 CGI executable programs read and write to local memory 7, in particular WML pages and configuration files which are ASCII text files and which can be read and / or modified by CGI executable programs via a link 78. Executable programs CGI are also capable of sending and receiving requests and responses, in particular HTTP and POP, exchanged with remote SD servers via a link 81 with the LT line.

 The CGI programs also launch, via a link 89, the execution of non-CGI executable programs in a software module 9 which notably includes a player of sound sources 92 for reproducing sound for example from a selected radio program station connected to the RT network, via a sound adaptation card 91 and the link manager 4 to a second device 3C of Hi-Fi system type. The Hi-Fi device 3C is conventionally remotely controlled by wire, infrared or radio by another second device 3T of the chain remote control type which receives commands which are included in RSP responses from the interpreter 53 through the switch 54 and the link manager 4, following HTTP RSL responses transmitted by the interaction manager 8 via the local server 6 when one of the peripherals 21 to 21 has selected and transmitted a command in an RQP request.

 The non-CGI executable programs in module 9 are applications that differ from CGI programs in that they do not generate

<Desc / Clms Page number 30>

 no output WML file and cannot be called directly from the HTTP 6 server, but can be called indirectly by a CGI executable program. For example, an audio file player 92 in the module 9 is called by a CGI driver 86 in the manager 8, via the link 89, in order to read an MP3 file in the memory 7 via a link 79 or to connect the equipment. central to a radio station station site broadcast internally.

 In a preferred embodiment, the manager 8 comprises the following CGI executable programs: a POP client 82, a home page constructor 83, a home page choice modifier 84, a system tree explorer of 85 files, an audio file player driver 86 and a high fidelity channel driver 87.

 The POP 82 client is used to query a POP email account associated with a remote SD mail server and generates a WML page indicating the number of messages for a user on the queried mail server using links 81 and 78. For each message, the WML page contains fields such as the sender, the date, the subject and the size of the message.

 In this regard, the POP client 82 receives as a parameter via a second HTTP GET request from the server 6, an identifier of the electronic messaging to be interrogated designated by the first device 21 of a user. Using this parameter and with a configuration file in memory 7, the client 82 retrieves the name of the mail server, the user name and the password

<Desc / Clms Page number 31>

 necessary for the teleconsultation of the email account in the remote server. These parameters are given to a POP automaton contained in the client program 82 so that it recovers the number of messages in the mailbox and the headers of M last electronic messages (e-mail) received, with M = 10 for example. From each of these headers, the POP automaton extracts the date of reception, the name of the sender and the subject of the electronic message.

Having retrieved all this information, the client 82 formulates a WML response page in accordance with the CGI mechanism and introduces all this information therein so that the server 6 sends it in the form of an RSL response to the user's device 31, after interpretation in the browser 5 following a second RQL request sent by the browser at the request of the first device 21.

 A WML home page broken down into small RSP display pages by the interpreter 53 is obtained according to one of the three methods for a pair of given peripherals 21-31.

 According to a first method, the home page constructor 83 sends in a second RSL response an HTML form read in the memory 7 which is in the form of RSP responses transmitted to the given peripheral 31 following a request to construct RQP home page by the device 21. The user validates responses in the form received, for example of the checkbox type, which are chained and returned via the browser 5 and the server 6 so that the constructor 83 build a home page based on chained responses.

<Desc / Clms Page number 32>

 According to a second method, a WML home page can be replaced at any time by a page selected by the user and recently received by the given device 31, by returning the URL address of this page by the browser under the command of the device given 21 to the home page choice modifier 84 which is used to configure the home page selected for a pair of devices 21-31 according to the URL address. The WML page then generated is the selected home page.

 In this regard, the browser 5 uses the modifier 84 when it recognizes a keyword (PageAccueilSetUp) in the URL address contained in the RQP request transmitted by the first predetermined device and reformulated into an RQL request by inserting the number the input port of the predetermined device as the IS session identifier. The modifier 84 receives via the server 6 as a parameter in an HTTP GET request, the selected address URL of the new home page and the number of the input port IS of the first given device 21. The modifier 84 writes to a file configuration of memory 7 this association between the URL address and the input port number so that the next browsing session relating to the given peripherals 21-31 begins with said new home page. The configuration file is read locally by browser 5, although it can also download it. The modifier 84 then opens the WML file corresponding to the new home page to transmit the content as an RSL response.

 According to a third method, a WML home page is selectively replaced by the user, by any page constituting a file found during

<Desc / Clms Page number 33>

 navigation in the tree structure of a local file system, in particular of configuration in memory 7, using the file system explorer 85. The explorer reads the list of files present in a current directory and generates a WML page whose links are associated with directories or files and allow respectively to recursively navigate to a "child" directory or else to modify the choice of a home page via the modifier 84.

 In this regard, the CGI explorer 84 receives via the server as a parameter an HTTP GET request containing a node of the file system tree, that is to say the name of a directory. The explorer 85 reads the contents of this directory by "primitive" functions of the operating system and thus establishes a list of directories and files which is filtered in a filter to eliminate symbolic links and data of no interest to it. 'user; this filter is also present in the configuration file. The explorer returns a WML page containing this list of the second given device of the user via the browser 5. Each entry in the list is a link whose validation by the user causes the emission of an RQP request then of an HTTP RQL request with a URL address containing the name of the file or directory to explorer 85. If the link is a directory, the new page, as an RSL response returned by the explorer, is the content of this directory , in accordance with the mechanism described above; a particular symbol, for example "..", makes it possible to go up in the tree structure to the first node of the file system. If the link is a file name, the link includes the word-

<Desc / Clms Page number 34>

 key which is contained in the corresponding RQP and RQL queries and which makes it possible to establish this file as a home page.

 The audio file player driver 86 is used to control the audio file player software 92 in the module 9 so as to reproduce sound by local sound sources in the central equipment 1. The driver 86 takes as parameter the reference on an audio file or URL address designating the audio stream from an internal radio station, or command instructions such as play, pause, etc. The CGI driver 86 generates in a second RSL response a WML page giving for example the state of the audio player and references on possible sound source commands to a pair of predetermined requesting peripherals 22-32.

 In this regard, the player driver 86 recovers the name of the audio file reader in a memory configuration file 7 and recovers from an RQL request sent at the request of the first requesting device 22 an identifier of the audio file to be played and searches in a second configuration file for the file corresponding to this identifier. When the driver 86 knows the name of the audio file player and the identifier of the audio file, it starts the player 92 passing it the name of the audio file as a parameter. Certain audio file identifiers are specific and correspond to codes which cause the driver 86 to launch an instruction to the player to influence the behavior of the player according to commands received for example to raise or lower the volume or stop the music or select a radio station. In accordance with the CGI mechanism, the

<Desc / Clms Page number 35>

 driver 86 returns a WML page to the second requesting device 32 in the form of an RSL response to the browser 5. This WML page contains the name of the file played by the player and links to driver 86 to change the behavior of player 92.

 The high-fidelity chain driver 87 generates, following an RQP request from the first requesting device 22 via the browser 5 and the server 6, a WML page presenting all the possible commands on the Hi-Fi system, such as volume control, compact disc player control, radio tuner control, tape recorder control, etc. The control page is transmitted in RSL responses to the second device 32. Each elementary function of the 3C Hi-Fi system , such as play, pause, radio, radio station selection, cassette, CD, high volume, low volume, is encoded by a control character that the chain is able to recognize. The string driver 87 extracts from an HTTP GET request transmitted by the browser 5 corresponding to an RQP request from the first device 22, the command character of the elementary function chosen in the device 32. The command character is retransmitted in a response HTTP RSL to browser 5 which interprets it in an RSP command response intended via port 13T for the remote control device 3T which controls the function chosen in the Hi-Fi system 3C.

 This allows the user equipped with the pair of peripherals 22-32 and located for example in his kitchen to choose for example a radio station program or a local sound file, which can possibly come from a remote site or from memory 7 via sound card 91, and

<Desc / Clms Page number 36>

 which is reproduced by the 3C chain located in another room, such as the living room. Then the pilot 87 signals to the pair of peripherals by a WML page transmitted to the browser 5 that the GET request with the chosen command character has been taken into account.

 The use of the chain driver 87 illustrates a situation where one of the second peripherals of the central equipment has no screen and nevertheless renders a WML page.

 Although the invention has been described in the particular context of domestic central equipment, the equipment can also be used in a public place. For example a museum provides a couple of peripherals to each visitor to allow him to consult cultural databases through the equipment. According to other examples, a visitor equipped with a pair of inventive peripherals can consult local information on exhibitors in a trade fair by interrogating the equipment, or can consult transport schedules or advertising or other local information, by querying equipment installed at an airport or station.

Claims (29)

 1-Interactive terminal system comprising a central equipment (1), at least a first peripheral (21), and at least a second peripheral (31), characterized in that the central equipment (1) comprises a navigation means (5 ) to a server means (6, SD), which receives as many types of first request (RQP) transmitted by the first device as there are action means (211-214) included in the first device (21) and which restores first responses (RSP) adapted to the second device (31).  2-System according to claim 1, wherein the navigation means (5) opens a session of second request and response (RQL, RQD; RSL, RSD) with the server means (6, SD).  3-System according to claim 1 or 2, wherein each first response is of the textual, or graphic, or image type.  4-System according to any one of claims 1 to 3, wherein each first response is transmitted in the form of data messages having a length compatible with the data processing capacity (216) of the second device (31).  5-System according to claim 4, wherein each data message transmitted by the navigation means (5) is preceded by an activation message (DTR) transmitted by the first device (21) to the navigation means. <Desc / Clms Page number 38>  6-System according to any one of claims 1 to 5, wherein the first request (RQP) is a message (14) which indicates that the second device (31) is ready to receive as the first response the start of a home page (AGI) and which follows a ready status request message (12) transmitted by the navigation means (5) to the second device before the expiration of a predetermined time delay (I5, TPN).  7-System according to any one of claims 1 to 6, wherein the first request (RQP) comprises a reference to one of the action means (211-214) requested in the first device (21) in particular for that the second peripheral (31) receives another first response (AC2) composing the second response (RSL, RSD) after shaping, or a first response already transmitted.  8-System according to any one of claims 1 to 7, wherein the first request (RQP) comprises a reference to one of the action means (211-214) called in the first device (21), said reference being interpreted by the navigation means as a file address in the server means (6, SD), when a line in the first response (RSP) containing a file designation has been selected in the second device (31) by the control means requested.  9-System according to any one of claims 1 to 8, comprising several second <Desc / Clms Page number 39>  peripherals (31-31), and wherein the navigation means (5) broadcasts a first response (RSP) to at least one second determined peripheral (31-31) following a first request (RQP) designating said at minus second determined device.  10-System according to any one of claims 1 to 9, comprising several first peripherals (31-31), and in which the navigation means (5) opens several sessions following several first simultaneous requests (RQP1, RQP2 ) transmitted respectively by first peripherals (21-22) to the central equipment (1).  11-System according to any one of claims 1 to 10, wherein the navigation means (5) by default associates a second device (31) linked to a first device (21) which has transmitted a first request (RQP) without designation of second device.  12-System according to any one of claims 1 to 11, wherein the navigation means (5) maps a predetermined session identifier (IDP) to at least one second predetermined device (31-33) so that the means navigation broadcasts a first response (RSP) to said at least one second predetermined device (31-33) independently of any first request received by the navigation means, following a second response (RSL, RSD) containing the predetermined session identifier (IS) and transmitted by the server means (6, SD) to the navigation means. <Desc / Clms Page number 40>  13-System according to claim 12, wherein the navigation means (5) broadcasts a control message to said at least one second predetermined device prior to the broadcast of the first response (RSP) in order to switch said at least second predetermined device in a line message receiving state (L1).  14-System according to any one of claims 1 to 10, wherein the navigation means (5) comprises a request management means (51) for converting first requests (RQP) transmitted by first devices (21- 21) in second requests (RQL, RQD) which designate the server means (6, SD), respectively contain session identifiers (IS) and are transmitted to the server means (6, SD), a correspondence means (52) to match a respective session identifier (IS) to any second device (31-31) designated in each first request, and means (53,54) to convert each second transmitted response (RSL, RSD) with a session identifier respective in at least one first response (RSP) respectively switched to any second peripheral corresponding to the respective session identifier in the correspondence means.  15-System according to any one of claims 1 to 14, the server means comprises a remote server (SD) connected at least by a telecommunications network (RT) to the central equipment (1). <Desc / Clms Page number 41>  16-System according to any one of claims 1 to 15, wherein the server means comprises in the central equipment (1) a memory (7) containing at least hypermedia documents and a local server (6) for exchanging second requests and responses (RQL, RSL) with the navigation means (5) in order to introduce into second responses (RSL) in particular hypermedia documents read in the memory.  17-System according to any one of claims 1 to 16, comprising means (PR) remote from the central equipment for transmitting a request relating to a determined document requested by a first peripheral in a format which cannot be restored by the means of navigation (5) or a server means (SD) included in the central equipment (1), to a remote server (SC) and to translate the requested document returned by the remote server into a format suitable for a second device (31) associated with the first device in order to transmit the document adapted to the browser or the local server to the second device.  18-System according to claim 17, wherein the server means in the central equipment comprises means (8) for executing programs according to parameters contained in second requests (RQL, 68) and in particular of files read in the memory (7) in order to establish and transmit second responses (RSL) to the navigation means.  19-The system of claim 18, wherein the means for performing (8) comprises a <Desc / Clms Page number 42>  means (82) for interrogating a mailbox in a remote server (SD) following a second request (RQL) containing an identifier for the mailbox designated by a first device (21) and for entering information retrieved from the mailbox in a second response (RSL) intended for a second peripheral (31) associated with the first peripheral.  20-System according to claim 18 or 19, wherein the means for executing (8) comprises means (83, 84, 85) for delivering a home page to a second peripheral (31) following a second request (RQL) sent by the navigation means (5) at the request of a first device (21) associated with the second device.  21-System according to any one of claims 18 to 20, in which the means for executing comprises means (83) for transmitting in a second response (RSL) a form read in the memory (7) to a second peripheral ( 31) associated with a first device (21) having requested it and to build a home page intended for the second device according to the completed form transmitted by the first device then in a second request (RQL) from the navigation means ( 5).  22-System according to any one of claims 18 to 21, wherein the means for executing comprises means (84) for replacing a home page for a second device (31) with a page recently received by the latter. . <Desc / Clms Page number 43>  23-System according to any one of claims 18 to 22, wherein the means for executing comprises means (85) for replacing a home page for a second device (31) with a page selected from a file system in memory (7).  24-A system according to any one of claims 18 to 23, wherein the means for executing comprises means (86) for generating a page of sound source commands in a second response (RSL) to a second predetermined device (32 ) and to control a sound reproduction via at least one sound source (92) in the central equipment (1) as a function in particular of an audio file identifier and of commands returned in a second request (RQL ) via the navigation means (5) from a first peripheral (22) associated with the first predetermined peripheral.  25-System according to any one of claims 18 to 24, wherein the means for executing comprises means (86) for generating a command page of a high-fidelity chain (3C) in a second response (RSL) to a second predetermined peripheral (32) and for retransmitting a command contained in a second request (RSL) transmitted via the navigation means (5) from a first peripheral (22) associated with the second peripheral, in a second response (RSL) intended to another second peripheral (3T) controlling the high-fidelity chain. <Desc / Clms Page number 44>  26-System according to claim 25, wherein the high-fidelity chain constitutes a second peripheral (3C) connected through a sound adaptation means (91) to the means for executing (8) in the central equipment (1) in order to retransmit sound from local and / or remote sound sources to the high-fidelity channel.  27-System according to any one of claims 1 to 26, wherein a first device and a second device are included in a common pocket housing (21-31 to 21-31).  28-The system of claim 27, wherein the first and second peripherals (21-31) in the housing include a microcontroller (215), control buttons (211-214), and a display (311).  29-System according to any one of claims 1 to 28, in which at least one peripheral (21-31 to 21-31) is connected to a port of the central equipment (1) by a proximity radio link ( 4).