WO2014096683A2 - Method of access to a multimedia content, mobile terminal, fixed terminal and software module corresponding thereto - Google Patents

Abstract

The invention relates to a method of access to a multimedia content accessible via a telecommunication network, initialized from a mobile terminal (OM_UI) identified with a mobile operator. The method comprises: a phase of discovery (Sq1, Sq2) by the mobile terminal of a fixed terminal (TV) in proximity, comprising a storing by the mobile terminal of profile data (device type) of the fixed terminal, a transmission (Sq3, Sq4, Sq5.1, Sq5.2, Sq5.3, Sq5.4) from the mobile terminal of a request for activation of a service for access to the multimedia content, enriched with profile data (device type) of the fixed terminal to a server (PSF TV) for managing the services offer of a content provider, a verification (Sq6, Sq6.1, Sq6.2, Sq6.3, Sq6.4, Sq6.5, Sq.6.6) of a legitimacy of access to the content as a function (Sq6.1) of a services offer subscribed to by the user of the mobile terminal with the content provider (FC), a selecting of an application corresponding to the service requested, to be installed on the fixed terminal, as a function of profile data of the fixed terminal, an adapting of the application by the offer management server as a function of user configuration data relating to the service, an installing on the fixed terminal of the application downloaded from the mobile terminal.

Description

 Method of accessing multi-media content, mobile terminal, fixed terminal and corresponding software module

Field of the invention

 The present invention generally relates to access to accessible content in telecommunications networks and their viewing from a terminal. The invention relates generally to the field of telecommunications and more particularly to techniques that involve streaming.

 The word streaming is used by reference to the possibility that an application to use synchronized data streams, for example audio or video, continuously while these streams are transmitted to the client by a data network. At the application level, live services are often distinguished from on-demand services. Examples for live services include the provision of radio content or live TV programs, and for on-demand services include music, podcast news and on-demand video-on-demand.

Streaming services in an IP-based packet network are subject to standardization actions, particularly within 3GPP. The TS 26 234 standard (ETSI TS 126 234) specifies the protocols and codecs (decoder coders) associated with these services. The standard TS 22 233 (ETSI TS 122 233) specifies the general architecture of the telecommunication network involved in streaming services. This architecture is illustrated by FIGS. 1 and 2 which respectively correspond to a 2G / 3G (UMTS) architecture with a GPRS backbone and a 2G / 3G / 4G architecture and an EPC backbone. A streaming service operates on a client / server schema, it relies on at least one content server and a streaming destination client. The content server is located behind the Gi interface. Other entities located behind this interface Gi can intervene in the service, in particular portals, profile servers, cache and proxy servers. A portal is a server that allows access to streaming content, for example it can be used to search. The simplest portal is a WEB ((X) HTML) / WAP page with a list of downloadable or streaming content links pointing to a generally remote server located behind the Gi interface. Profile servers store device profiles that combine user-specific data with device-specific (terminal) data. These profiles can be used to control the presentation of content multi media streaming to the terminal user as shown in Figure 3. The client (UE PS S client) initializes the service and connects to the selected content server. The profile server can be contacted during an initial phase. User-specific data is used to set up the streaming service with the user's preferences. Terminal-specific data is used by the streaming service to decide whether or not the client terminal is capable of receiving the streaming content. FIG. 4 is a schematic representation of the contents of an equipment profile which is broken down into user-specific data and equipment-specific data (terminal). User-specific data essentially includes the user's preferences in the use of this equipment for the particular service. The equipment-specific data can be broken down into three modules, a description module of the hardware capabilities of the terminal (terminal type, model number, screen size, inputs / outputs, etc.), a module describing terminal software capabilities (operating system (OperatingSystem), compatible video and audio encoders, etc.) and a hardware and software plug-in module.

 In the context of the invention, a distinction is made between a fixed terminal and a mobile terminal. The fixed terminal is conventionally a television or screen accessible via a telecommunication network which is used to display video content and more generally to restore the user to a multi-media content. The mobile terminal is conventionally a mobile phone, for example a smartphone, tablet, ipod, etc., which allows to establish a telephone communication and more widely communications of different types depending on the subscription subscribed by the customer with a mobile operator.

 Prior art

 Terminal users often have several types of fixed and mobile terminals that they configure according to their preferences. They can choose for example to view only certain TV channels as their favorite channels that are then highlighted in the home page, they can fill a grid of programs and mark programs they want to view. Today, the user usually has to specifically configure each terminal according to his preferences.

 Presentation of the invention

The subject of the invention is a method for accessing accessible multi-media content via a telecommunication network, initialized from a mobile terminal identified with a mobile operator. The method comprises:

 a discovery phase by the mobile terminal of a nearby fixed terminal, comprising storing by the mobile terminal of the fixed terminal profile data,

 a transmission from the mobile terminal of a request for activation of a multi-media content access service enriched with fixed terminal profile data to a service provider management server of a content provider,

 a verification of a legitimacy of access to the content according to a service offer subscribed by the user of the mobile terminal with the content provider,

 a selection of an application corresponding to the service required, to be installed on the fixed terminal, according to the fixed terminal profile data,

 an adaptation of the application by the bid management server based on user configuration data relating to the service,

 an installation on the fixed terminal of the application downloaded to the mobile terminal.

 The identifier of the mobile terminal corresponds to the identifier assigned by the mobile operator to the user when subscribing to a communication offer with a mobile terminal. This identifier is known by the acronym MSISDN in the GSM and UMTS standards and is more commonly known as the telephone number. According to these standards, this identifier is embedded in the SIM card which is inserted in the mobile terminal. The identifier is then associated with the mobile terminal that embeds the SIM card.

According to the invention, the request for activation of the service starts from the mobile terminal and is transmitted to a multi-media content delivery platform via a mobile access network. This activation request is parameterized with data previously retrieved by the mobile terminal from the fixed terminal during a discovery phase. The platform checks the eligibility of the access from the fixed terminal to the content according to the offer subscribed by the user. The platform selects the application based on the fixed terminal. The platform adapts the application to be installed on the fixed terminal to access the multi media content taking into account a personal configuration of the user relating to the requested service. The user does not need to intervene on the fixed terminal, the application is downloaded to the mobile terminal and then installed on the fixed terminal, typically via a short distance communication between the mobile terminal and the fixed terminal. Thus, regardless of where the fixed terminal is located, provided that it has IP connectivity, the user of the mobile terminal can view on the fixed terminal the multi media services of an offer subscribed with a content provider while automatically benefiting from this fixed terminal of its configuration data. This configuration data may come from the preferences of the user registered in a profile associated with his mobile terminal or possibly associated with another fixed terminal and / or data related to the use of this service by the user. Thus, the user is no longer forced to manually configure the fixed terminal to find his personal configuration.

 According to the invention, the mobile terminal is used as a trusted personal terminal in order to securely configure for the user access to its content offer on a new fixed terminal. In addition, the user can privilege the use of his mobile terminal to subscribe to new content services that will be made available on a fixed terminal TV, by launching an update of its service offering. The mobile terminal can thus be used as a privileged personal terminal for subscription actions to content offers. These content offers can then be delivered on a fixed terminal for viewing.

 According to one embodiment, the method for accessing a multi-media content is that:

 the discovery phase further comprises storing by the mobile terminal characteristics of the fixed access network,

 the mobile terminal also transmits the characteristics of the fixed access network to the service provider management server of the content provider, the fixed terminal having an addressable IP address via the telecommunications network.

This mode is more particularly adapted when the fixed terminal accesses the telecommunications network via an Internet Service Provider (ISP) and this access provider is able to provide data on the infrastructure of the fixed access network by means of for example, the TR-69 protocol defined by the Broadband Forum between the fixed terminal and an access network operator server. The implementation of the recovery of these data by the mobile terminal from the fixed terminal can be done using the UPnP protocol and the Discovery function. In particular, the message SSDP Notify can be populated with fixed access network data such as latency, jitter, and packet loss. The data of the fixed access network may be used by the bid management server to determine whether the subscription of services subscribed by the user makes the requested service eligible in an activation context on the fixed terminal.

 According to one embodiment, the method for accessing a multi-media content is such that the activation request is transmitted from the mobile terminal via a cellular mobile access network, and the method furthermore comprises:

 the substitution by the mobile access network of an identifier of the mobile terminal present in the activation request by a known identifier of the content provider.

 Cell-type mobile access networks automatically insert the identifier of the mobile terminal into the activation request, ie the user identifier assigned by the mobile operator when subscribing a communication offer with a mobile terminal. mobile terminal. This mode is particularly suitable when the mobile operator and the content provider are different economic entities. By transmitting only an alias from the mobile identifier to the content provider, the mobile operator guarantees the confidentiality of the user's mobile identifier. This identifier generally corresponds to the telephone number associated with its subscription data with this mobile operator. Vis-à-vis the content provider, the mobile operator plays the role of trusted third parties in identity management.

 According to one embodiment, the method for accessing a multi-media content is such that:

 the content provider's service provider management server requests the mobile terminal to identify itself to obtain a mobile terminal identifier in the absence of the activation request of an identifier of this mobile terminal.

Mobile type mobile access networks automatically insert the identifier of the mobile terminal into the activation request. This mode therefore applies more particularly when the mobile terminal is not attached to a cellular mobile access network but accesses the telecommunications network via an access point, for example of the WiFi type which is not interconnected to the mobile network. mobile core network ("3GPP core network" of Figure 1). In this case, the access network does not know how to insert the identifier of the mobile terminal since it is not a cellular mobile access network.

According to one embodiment, the method of accessing a multi-media content further comprises: generation by the content provider of the content provider of a unique configuration key from an identifier of the mobile terminal, from the fixed terminal profile data and from the required service,

 inserting into the application parameters to download the configuration key and routing parameters for access from the fixed terminal to the multi-media content by the application to be downloaded,

 a request to activate the application from the fixed terminal set with the routing parameters and the configuration key.

 According to this mode, the content provider generates a configuration key from the identifier he knows of the mobile terminal and which is associated with the identity of the user, that is to say either the identifier mobile, the alias of this identifier known to the content provider, especially when the latter is not the mobile operator. This key makes it possible to authenticate and certify that the request for activation of the content from the fixed terminal is associated with the mobile terminal, thus with the user who is definitively identified with the mobile operator. The mobile operator can therefore guarantee the content provider the identity of the user who requests activation of the service from his mobile terminal. This authentication and certification ensures the payment mechanism between the user, the operator, the owner of the fixed terminal and the content provider. The generation of the key is dynamic which offers a great flexibility of use. The routing parameters consist for example of a URL which points to the portal of access to the content service on a streaming server.

 This mode allows management of several personal configurations of users on the same fixed terminal since the key is a function of the identifier of the mobile terminal ie the user. During the startup of the fixed terminal, it may be proposed to the user to select a user account with the entry of a password that identifies the user. Thus the selection of the account can automatically allow the selection of the configuration of the user for this fixed terminal since the personalization data are present in the downloaded application.

 According to one embodiment, the method of accessing a multi-media content further comprises:

storing in one or more database the key of configuration and routing parameters with the user's configuration data relating to the service in a profile associated with the fixed terminal.

 The profile associated with the fixed terminal is stored for example in the profile database known as Device Profile Server.

 According to one embodiment, the method of access to a multi-media content is such that the content provider manages a database that contains for a given user, the list of subscribed services and the list of services activated by terminal with the configuration key associated with the terminal and the service, the method further comprises:

 updating the database with the configuration key generated for the fixed terminal and the requested service.

 This database makes it possible to know the list of activated services for a given user and by terminal. It thus makes it possible to know all the terminals configured for the services activated by the user. Such a base is particularly advantageous for enriching the information system of the content provider and for example serve as a help for after-sales services during a problem reported by the user.

 The configuration key is used to link to the Profile Profile Server to obtain the profile details of a given terminal. When configuring a new terminal, the service provider can retrieve a set of user preferences relating to its uses on each of the terminals where it has activated a given service. By default, the preferences used for setting up a new fixed terminal are those of the handheld. The provider and / or the user can set preference selection rules among its different configurations for a given service. For example, a rule may be to select preferences associated with a terminal whose characteristics are closest to those of the new terminal on which the activation of the service is requested.

 According to one embodiment, the method of accessing a multi-media content further comprises:

 a transmission from the mobile terminal of a deactivation request of the service parameterized with the configuration key to the service provider management server of the content provider.

 This request allows the user to initiate the deactivation of the service he activated on the fixed terminal.

This mode is particularly advantageous for the user in a context where the fixed terminal is that of a hotel room. The user thus has the possibility of controlling the period during which the service to which he has subscribed with a content provider is active. Thus, the user can disable access to this service at any time and especially as soon as he leaves or leaves his room permanently.

 According to one embodiment, the method of accessing a multi-media content further comprises:

 a transmission from the service provider management server of the content provider of a deactivation request of the service set with the configuration key to the fixed terminal.

 This request allows the service provider to initiate the deactivation of the service that the user was able to activate on the fixed terminal. This mode is particularly advantageous for the user in a context where the fixed terminal is that of a hotel room. This request can be triggered automatically when the user pays for his hotel bill.

 This mode ensures a secure operation to the user by ensuring a final stop after leaving any use of the service he had activated even if he himself did not take the initiative to disable this service.

 According to one embodiment, the method of accessing a multi-media content further comprises:

 a transmission from the mobile terminal of a service update request parameterized with the configuration key to the service provider management server of the content provider.

 This request allows the user to start the update of the activated service. This mode is advantageous when the content provider changes the service offering for its customers and for example enriches the service already subscribed by the user.

 According to one embodiment, the method of accessing a multi-media content further comprises:

 the reception by the mobile terminal of a security code generated from the service provider's management server of the content provider,

 the provision of the security code to the fixed terminal,

 the transmission from the fixed terminal of the security code to the service provider management server of the content provider,

the transmission of a request for authorization to activate the management server provision of services from the content provider to the fixed terminal only if the security code received is identical to the generated code.

 This mode makes it possible to add additional security to the access method by prohibiting any activation of the service on the fixed terminal without the provision of a security code. This code is previously generated by the offer server of the content provider and transmitted to the mobile terminal. The transmission of the code to the mobile terminal can be done by SMS, or via an https notification. The code can then be inserted for example via manual input by the user. This input can intervene from a remote control of the fixed terminal. Transmission from the fixed terminal can be done via an https request.

 According to one embodiment, the method for accessing a multi-media content is such that the discovery phase implements a short-distance point-to-point link between the mobile terminal and the fixed terminal.

 The discovery phase takes place for example according to a UPnP protocol (Universal Plug and Play) by borrowing a wired physical link or wireless point-to-point type NFC, bluetooth, IR, USB, dongle with WiFi ... short distance that has for the advantage of limiting the location area in which the fixed terminal can be located that the user can configure by means of his mobile terminal. The short-distance link physically limits the field of fixed terminals that can be configured by the user by means of his mobile terminal. This is particularly advantageous in a hotel since this physical limitation reduces the possibility of configuring the television of a neighboring room.

 According to one embodiment, the method of access to a multi-media content is such that the discovery phase includes a return to the user of fixed terminal profile data for confirmation by the user of the continuation of the method with this fixed terminal.

 This confirmation request gives the user the opportunity to verify that the fixed terminal discovered by the mobile terminal is the one he intends to configure.

This mode is particularly advantageous in a hotel because it allows the user to check that he is not configuring the television of a neighboring room. The implementation can be done using the UPnP protocol and the Discovery function. The use of the SSDP Notify message makes it possible, for example, to enter the character string "terminal TV of the room 111". The display of the room number in which is located the fixed terminal allows the user to ensure that his mobile terminal is the right fixed terminal (the television in his room) during a discovery in Wifi. This mode greatly reduces an erroneous configuration of the fixed terminal of a neighboring chamber.

 The invention furthermore relates to a software module comprising program instructions such that their execution by a mobile terminal implements the following steps:

 a phase of discovering a fixed terminal near the mobile terminal, comprising storing by the mobile terminal profile data of the fixed terminal,

 a transmission from the mobile terminal of a request for activation of a multi-media content access service enriched with fixed terminal profile data to a service provider management server of a provider content,

 a download of an application corresponding to the required service selected according to the profile data of the fixed terminal and adapted according to user configuration data relating to the service, an installation on the fixed terminal of the application downloaded to the terminal mobile.

 The invention further relates to an information carrier comprising program instructions adapted to the implementation of the following steps when said program is loaded and executed in a mobile terminal:

 a phase of discovering a fixed terminal near the mobile terminal, comprising storing by the mobile terminal profile data of the fixed terminal,

 a transmission from the mobile terminal of a request for activation of a multi-media content access service enriched with fixed terminal profile data to a service provider management server of a provider content,

a download of an application corresponding to the required service selected according to the profile data of the fixed terminal and adapted according to user configuration data relating to the service, an installation on the fixed terminal of the application downloaded to the terminal mobile. The invention furthermore relates to a mobile terminal comprising a software module with program instructions such that their execution implements the following steps:

 a phase of discovering a fixed terminal near the mobile terminal, comprising storing by the mobile terminal profile data of the fixed terminal,

 a transmission from the mobile terminal of a request for activation of a service for access to multi-media content enriched with the profile data of the fixed terminal to a service provider management server of a provider content,

 a download of an application corresponding to the required service selected according to the profile data of the fixed terminal and adapted according to user configuration data relating to the service, an installation on the fixed terminal of the application downloaded to the terminal mobile.

 The invention furthermore relates to a fixed terminal comprising a software module with program instructions such that their execution implements the following steps:

 a discovery phase between a mobile terminal and the fixed terminal, the mobile terminal being close to the fixed terminal, comprising storing by the mobile terminal profile data of the fixed terminal,

 an installation phase on the fixed terminal from the mobile terminal of an application previously downloaded to the mobile terminal, the application corresponding to a multi-media content access service selected according to the profile data of the terminal fixed and adapted according to user configuration data relating to the service,

 an activation phase of the multi-media content access service between the fixed terminal and a service provider management server of a multi-media content provider.

 List of Figures

Other features and advantages of the invention will emerge more clearly on reading the following description of particular embodiments, given as simple illustrative and non-limiting examples, and the appended drawings, among which: FIG. commented in relation to the prior art, is an illustration of the general architecture of the 2G / 3G (UMTS) network with a GPRS backbone involved in streaming services in reference to 3GPP standard TS 26 233,

FIG. 2, already commented on in relation to the prior art, is an illustration of the general architecture of the 2G / 3G / 4G network with an EPC backbone involved in streaming services with reference to the 3GPP standard TS 26 233,

FIG. 3, already commented on in relation to the prior art, is an illustration of the system logical architecture of the capacity negotiation mechanism implemented in a PSS streaming service with reference to the 3GPP standard TS 26 233,

FIG. 4, already commented on in relation to the prior art, is a schematic representation of the contents of an equipment profile of a profile server conforming to 3GPP standard TS 26 233,

FIG. 5 is a schematic representation of the content of an enriched equipment profile according to the invention,

FIG. 6 is a diagram of different enriched equipment profiles with the respective links with a database of subscribed services and of active services for a user, according to the invention.

FIG. 7 represents the different entities involved according to a first embodiment of a method according to the invention,

FIGS. 8-10 are schemas of exchanges (call flow) between the different entities represented in FIG. 7 according to one embodiment of a method according to the invention,

FIG. 11 represents the various entities involved according to a second embodiment of a method according to the invention,

FIGS. 12-14 are schematic diagrams of exchanges (call flow) between the different entities represented in FIG. 11 according to one embodiment of a method according to the invention,

FIG. 15 is a block diagram of the exchanges (call flow) between the different entities represented in FIG. 11 according to one embodiment of a method according to the invention,

FIG. 16 is a block diagram of the exchanges (call flow) between the different entities represented in FIG. 11 according to an embodiment of a method according to the invention,

 FIG. 17 is a diagram of a simplified structure of a mobile terminal according to the invention,

 Figure 18 is a schematic diagram of a simplified structure of a fixed terminal according to the invention.

 Description of Embodiments of the Invention

 The general principle of the invention relies on the use of a mobile terminal as a trusted terminal with which the user can configure other terminals, more particularly fixed to view multi-media content. The user has subscribed to a subscription and more generally to a service offer from a mobile operator who has given him a call number in return. With reference to certain standards such as GSM, this call number is generally identical to an identifier designated by the MSISDN acronyms.

 In parallel, the user can subscribe to content providers of additional and more generally additional offers.

 In its residential environment, the user can share one or more fixed terminals such as television equipment (TV) with members of his family. Each member can hold a personal mobile terminal.

 The user may not share the same preferences or uses of content viewing as members of his family. As a result, he may be forced to configure each time the TV he uses at a time t to obtain a configuration that corresponds to its content offer, which corresponds to its use, which corresponds to his preferences.

 According to one embodiment of the invention, the user can automatically configure a fixed terminal with his preferences and uses associated with his mobile terminal. The mobile terminal retrieves certain data elements from the profile of the fixed terminal and requests the content provider to adapt his profile associated with his mobile to the fixed terminal from the data elements of the profile of the fixed terminal that he transmits to him. This allows the user to extend its content offering to other terminals accessible via a fixed network.

The standard 3GPP TS 26 234 specifies a profile illustrated in Figure 4 associated with a terminal equipment. In the context of the invention, this profile is used by the multi-media content service, it is generally stored on a server called "device profile server". It is understood that this server can actually correspond to several servers. The profile contains data on the hardware capabilities of the terminal referred to as hardware capabilities, data on software capabilities referred to as software capabilities. These capabilities are enriched by the user or the service provider by means of plug-ins, referred to as "Hardware / Software plug-in", for example an extension of the memory capacity, a downloaded software module. The user can enter parameters classified in the "User Preferences", for example the choice of an audio sound and not stereo.

 The invention proposes to enrich the profile of a device with two modules, a routing module designated by the terms "routing policies" and a module with a configuration key designated by the terms "Configuration key" as illustrated in FIG. .

 The invention further proposes to manage a database in which the subscribed services and the services activated by the user are stored on different terminals. FIG. 6 represents this database designated by the terms "list of services subscribed by the user and list of services activated for the user by terminal" ("subscribed and activated services per user") as well as the different profiles associated with each terminal and the link between a profile and this database. According to one embodiment, the information system SI manages the database "list of services subscribed by the user and list of services activated for the user by terminal". Thus according to this mode, the information system SI gives elements of response following a customer call relating to a service unavailable. The service platform usually manages the "device profile server" database since the "routing policies" module refers to configuration data relating to the service platform such as the URL or the IP address to enable the terminal sending these service requests. These two bases make it possible to know all the terminals which are configured to give access to the services of the user. The database "list of services subscribed by the user and list of services activated for the user by terminal" gives the list of services activated by terminal for a given user. When configuring a new terminal, the service provider can retrieve a set of user preferences for the uses on each of the terminals where the services are enabled. At a minimum, the service provider retrieves the user's preferences for the mobile terminal (for example smartphone) which has an active subscription.

Thus, the invention makes it possible to export the profile associated with a service of the mobile terminal to a fixed terminal to display a multi-media content on this fixed terminal. The mobile terminal serves as a trusted terminal in the activation of the service on the fixed terminal.

 According to a first mode of implementation of the invention, the mobile operator and the content provider are different actors. This mode is detailed with reference to FIG. 7 which represents the various entities involved and to FIGS. 8-10 which are schemas of exchanges (call flow) between the different entities during the execution on the mobile terminal of program instructions of a software module according to an embodiment of the invention.

The mobile terminal is identified with a mobile operator OM, the fixed terminal "TV" is located for example in a hotel or any other building such a house, a building. The mobile and fixed terminals are respectively accessible via a mobile access network and a fixed access network by the telecommunication network. The mobile and fixed access networks are designated by "Ntw" and distinguished by two vertical lines Mob, Fix. An ISP access provider allows access of the fixed terminal TV to the telecommunication network via the fixed access network. The service provider platform PFS includes a mobile TV portal OM mobile operator and a TV portal content provider FC, four vertical lines are attached thereto. The FE referenced features (Front End) correspond to functions that implement the exchanges with the user, the features referenced BE (Back End) correspond to the other exchanges respectively of the portal of the mobile operator and the portal of the content provider and the 4 ^th line corresponds to the profile management function. This platform corresponds to one or more servers. The servers of the information system are identified by the term "SI", two vertical lines are attached to it. ¹ line corresponds to the information system of OM mobile operator. The ^2nd line corresponds to the FC content provider information system.

 The Sqx sequences of messages exchanged according to the illustrated embodiment are listed below.

 Sql: "device discovery ()" sequence. This sequence corresponds to the discovery from the mobile terminal of a fixed terminal nearby via a wired link (for example USB) or a wireless link. This sequence is for example based on a UPnP protocol based on an SSDP notification.

Sq2: sequence "device_discovery (user agent device type)". This sequence corresponds to the response of the fixed terminal to the mobile terminal. The fixed terminal transmits data of its profile such as "user agent device type" with reference to the Open Mobile Alliance, which has published a User Agent profile version 2.0 referenced document of February 2006 defining the UAProf profile of a User Agent Pofile agent. The fixed terminal may also transmit "fixed access type" characteristics of the access network to which it is connected. This response is based on the same protocol used in the Sql sequence, for example the UPnP protocol.

 Sq3: sequence "activation_request (mobile type, TV device type, service type)". This sequence corresponds to the request to activate a service for access to multi-media content transmitted from the mobile terminal to the content provider. It contains data on the mobile terminal (mobile type), on the fixed terminal (TV device type) as well as on the requested service (typical service). Possibly, it contains data on the fixed access type network.

 Sq4: sequence "activation_request enrichment (+ OM_UI)". This sequence corresponds to the insertion of the mobile identifier of the mobile terminal by the mobile access network in the activation request "activation_request" issued by the mobile terminal. This identifier is known by the acronyms MSISDN in the case of a 2G or 3G access network (GSM, UMTS). Such a sequence does not exist in the case of a wireless access network, for example WiFi type, not interconnected with the mobile core network (also called "3GPP Core Network" in Figure 1).

 Sq5: during the sequences 5.1, 5.2, 5.3, 5.4 the resources of the mobile operator OM analyzes the request of the user.

 Sq5.1: sequence "activation_request (TV device type, OM_UI, service type). This sequence corresponds to the passage of the activation request between the FE applications of the portion of the platform under the control of the mobile operator that exchanges with the terminals and the BE applications that process the requests transmitted by the FE applications for processing.

 Sq5.2: sequence "Aliasing_request (service type, OM_UI)". This sequence from the part of the platform under the control of the mobile operator to its information system SI M corresponds to the request to obtain an alias identity known to the content provider. This alias allows the operator to guarantee to the user that his mobile identity is not communicated to the content provider. In addition, it allows the mobile operator to outsmart the role of guarantor to the content provider with respect to the identity of the user who invokes the requested service.

Sq5.3: sequence "Aliasing_response (FC_UI)". This sequence in response to the previous message contains the known FC_UI alias of the content provider of the identity mobile OM_UI of the user of the mobile terminal.

 Sq5.4: sequence "activation_request (TV device type, FC_UI, service type). This sequence corresponds to the passage of the request to activate the sequence Sq5.1 between the part of the platform under the control of the mobile operator and the part of the platform under control of the content provider, the request is transmitted between two actors. different. As a result, the sequence contains the parameters / data necessary to analyze the request according to the service offer subscribed by the user with the content provider. The sequence thus contains the type of fixed terminal (TV device type), the requested service (service type) and Γ alias (FC_UI). Optionally, the sequence contains the fixed access type.

 Sq6: During sequences 6.1, 6.2 the content provider FC analyzes the request of the user.

 Sq6.1: "fetch_subscribed_offer_data (FC_UI)" sequence between the PFS TV platform and the SI information system in the content provider environment. The PFS TV service offering platform queries the content provider's information system SI to obtain the subscribed subscription data from the user. The exchanges contain the FC_UI alias. The platform retrieves the subscribed services and the set of active configuration keys (configuration_keys) for the FC_UI user.

 Sq6.2: "fetch_device_capabilities (TV device type)" sequence between the portion of the PFS TV platform under the control of the service provider and a database of equipment from different manufacturers. During this exchange, the platform retrieves the characteristics of the hardware and software capabilities of the fixed terminal.

 Sq6.3 step "Check eligibility {subscribed offer, device capabilities}". This step corresponds to the verification by the platform of PFS TV service offer of the eligibility of the service offer subscribed in the context of an activation of the service on the fixed terminal from the characteristics of the hardware and software means " device capabilities "of which the fixed terminal benefits. Based on these means, the platform determines if the terminal has sufficient resources for the requested service. The verification is performed in the content provider environment.

Sq6.4: sequence "activation_response (FC_UI)". This sequence from the part of the service platform that depends on the content provider is for the mobile terminal identified by its alias. The PFS TV service offering platform tells the user the status of the process. Depending on the subscribed offer and the characteristics of the fixed terminal (TV device type), access to the service may be refused (access denied), access to the service may be restricted (restricted access) or access to the service can be authorized (installation under progress).

 Sq6.5: step "Aliasing (FC_UI, OM_UI)". During this step, the part of the platform under the control of the mobile operator replaces Γ alias by the mobile identity of the user.

 Sq6.6: sequence "activation_response (OM_UI)". This sequence corresponds to the sequence Sq6.3 with the identity of the mobile instead of Γ alias. It is in response to the sequence Sq3. This exchange Sq6.5-Sq3 can use the http protocol.

 Sq6.7: "user service request for application download ()" sequence. This sequence from the mobile terminal to the content provider is a request to obtain the application to download corresponding to the required service.

 Sq6.8: "Fetch user preferences (configuration_keys)" sequence between the part of the PFS TV platform under the control of the service provider and the "Profile server" profile database. By querying the profile database from the "configuration_keys" parameter (s), the platform can retrieve the user's usage preferences for each of the terminals where the requested service is active.

 Sq7: step "application selection {device capabilities, OS, service type ...}". This step corresponds to the selection by the platform PFS TV of the application to be downloaded to the mobile terminal according to the capabilities of the fixed terminal and the multi media TV offer subscribed by the user and the type of service requested by the user. user for the fixed TV terminal.

 Sq8: "routing policies selection" step In this step, the PFS TV platform configures the routing parameters of the application according to the capabilities of the fixed terminal. This typically corresponds to the setting of the platform URL (Front End URL of the PFS TV platform that is under the control of the content provider) which becomes accessible to the fixed terminal after download and installation via the mobile terminal. These routing policies allow the fixed terminal to access the content provider's server for viewing content on that terminal.

Sq9: "service personalization" step. During this step, the PFS TV platform takes into account the personalization data (usage preferences) that will be exported to the fixed terminal. The data includes all of the data from customization of the user services as well as known usage data of the PFS TV platform. In practice, this data may correspond to cookies that incorporate usage preferences, configuration data and implicit authentication identity data. Optionally, a weighting is performed to give greater importance for uses associated with terminals of the type close to that of the fixed terminal. By default, the platform takes into account prior uses on the mobile terminal (typically smartphone type).

 SqlO: step "configuration_Key generation". This step corresponds to the generation by the platform PFS TV of the unique Configuration-Key configuration key from FC_UI alias known content provider, fixed terminal characteristics determined from the type of terminal (TV device type) and the requested service. This key is used for several purposes:

 during the configuration of the fixed TV terminal, the latter inserts this key which enables the PFS TV to recognize the configuration context, in particular in sequence Sql3,

 when using the service, this configuration key is present in the two databases ("list of services subscribed by the user and list of services activated for the user by terminal" and "device profile server") and allows the service provider to ensure that the configuration data of the TV terminal ("routing policies") are consistent with the services subscribed and activated on the TV terminal. Verification of this consistency is particularly necessary in case of notification by the user of problem of access to the content services.

 Sq.lObis: The "writing of configuration parameters in DB" sequence from the platform to the subscribed service and profile DB databases and services databases in the content provider environment. configuration settings in the Profile server and subscribed services databases, and more specifically the routing policies and the configuration key.

Sql ll: sequence "application_download (software, personalized preferences, FC_UI, routing policies, configuration key)" from the platform PFS TV to the mobile terminal. This sequence corresponds to the download on the mobile terminal of the application to be installed on the fixed terminal. Download includes software, personalization data (eg favorite Live Channels, bookmarked VoDs, social networking links, personalized homepage (welcome custom screen)), Γ alias FC_UI, routing policies, configuration key. The configuration key allows implicit authentication of the user for content provider services. The addition of the FC_UI alias known to the content provider to the application to be downloaded to the fixed terminal makes it possible to manage several accounts on the fixed terminal from the content provider's homepage.

 Sql l.2: step "Aliasing (FC_UI, OM_UI)". During this step, the part of the platform under the control of the mobile operator replaces the alias with the mobile identity. It is similar to step Sq6.4.

 Sql l.3: sequence "application_download (software, personalized preferences,

OM_UI, routing policies, configuration key) ". This sequence corresponds to the sequence Sql l.l with replacement of the alias by the identifier of the mobile terminal. This sequence is in response to the sequence Sq6.7. This exchange Sq6.7-Sql l.3 can use the http protocol.

 Sql2: sequence "application install". This sequence corresponds to the installation on the fixed terminal of the TV application downloaded from the mobile terminal. This sequence is for example based on a UPnP protocol.

 Sql3: sequence "activation_request (configuration_key)". This sequence corresponds to a request for activation of the service from the fixed terminal to the part of the platform under control of the content provider. This sequence can be based on an https protocol.

 Sql4: The 14.1-14.4 sequences correspond to a requirement of the content provider FC to perform a final check before activation of the service. This sequence game remains optional.

 Sql4.1: sequence "Security code generation (Secure_code, FC_UI) from the part of the platform under the control of the content provider to the part under control of the mobile operator. This sequence contains a code (Secure_code) and the alias of the user.

 Sql4.2: step "Aliasing (FC_UI, OM_UI)". During this step, the part of the platform under the control of the mobile operator replaces the alias with the mobile identity. It is similar to step Sq6.5 and step Sql 1.2.

Sql4.3: sequence "Security code transfer (Secure_code)". This sequence corresponds to the transmission of the Sql4.1 sequence from the part of the platform under the control of the mobile operator to the mobile terminal. This sequence can be based on a push API mechanism.

 At this stage, the user of the mobile terminal must enter on the fixed terminal the code received on his mobile terminal.

 Sql4.4: sequence "Security code insertion (Secure_code, configuration_key)" from the fixed terminal to the content provider. Given that the fixed terminal knows the routing policies and the configuration key, it transmits the code entered with the same configuration key and using the routing parameters to point to the content provider. This sequence can be based on an https protocol.

 The receipt of a code entered identical to the issued code terminates the last verification by the content provider.

 Sql5.1: sequence "account_activation (configuration_key)". This sequence corresponds to the activation of the account requested by the service platform to the information system SI of the content provider.

 Sql5.2: sequence "successful_activation (configuration_key)" between BE and FE applications of the part of the platform under the control of the content provider.

 Sql5.3: sequence "activation_response (configuration_key)" from the part of the platform under the control of the content provider to the fixed terminal. This sequence corresponds to the response to the Sql3 sequence. The Sql3-Sql5.3 exchange can be based on an http or https protocol.

 Sql5.4: "successful_activation" sequence from the PFS platform to the mobile terminal. This sequence is intended to inform the mobile terminal of the success of the activation. This sequence contains the user's alias.

 Sql5.5: step "Aliasing (FC_UI, OM_UI)". This sequence is similar to the sequence Sql4.2.

 Sql5.6: sequence "user notification ()" from the part of the platform under control of the mobile operator. The notification message contains the mobile identifier of the user. The notification to the mobile terminal may include an indication that the service is available (service available). This sequence can be based on a "push API" mechanism.

According to a second embodiment, the mobile operator and the content provider are seen as a single actor. Figure 11 illustrates the different entities. The principle of exchanges remains that described for the first mode. Some exchanges disappear as there is no longer any distinction between the mobile operator and the content provider. There is more according to this mode of use of aliases, only the mobile identifier OM_UI is used. Figures 12, 13 and 14 are schematic diagrams of exchanges according to the embodiment.

 According to one embodiment, the user can request an update of his service offering to his fixed TV terminal, from his mobile terminal such as the subscription to new TV services or the unsubscription to certain content. This request may require updating the application installed on the fixed TV terminal. This mode is detailed with reference to FIG. 15 which is a circuit diagram of the exchanges (call flow) between the previous entities when the mobile terminal executes program instructions of a software module according to the embodiment of FIG. the invention.

 SqlOl: sequence "update_account_request (configuration_key, requested_services)" from the handheld to the content provider. This sequence corresponds to the update request sent by the mobile terminal. The message sent contains the configuration key associated with the profile of the fixed terminal. It also contains the services to be updated (requested_services). The sending of the "Configuration_Key" parameter makes it possible to know which service profile is to be updated when several accounts belonging to different users are activated on the same fixed TV terminal.

 Sql02: sequence "update_account_request enrichment (+ OM_UI)" by the mobile access network to the content provider's PFS TV service offering platform. This sequence is similar to the sequence Sq4 of the first mode.

 Sql03: sequence "update_account_request (OM_UI, requested_services)" between the PFS platform and the SI information system. The PFS service offering platform polls the mobile network information system SI to obtain updated data on the mobile subscription subscribed by the user. The exchanged messages contain the identifier of the mobile terminal (OM_UI).

 Sql04: "Check of Compatibility (subscribed offer, device capabilities)" step. This step corresponds to the verification by the PFS service offer platform of the compatibility of the subscribed offer updated in the context of an activation on the fixed terminal. This step is similar to step Sq6.3 of the first mode.

Sql05: step "application update (device capabilities, OS, ...). This optional step corresponds to the update of the selection by the PFS platform of the application to download on the terminal according to the capabilities of the fixed terminal and the updated multi-media offer subscribed by the user.

 Sql06: "routing policies update" step. During this optional step, the PFS platform updates the routing parameters of the application. This typically corresponds to the update of the configuration of the FE application URL of the platform (ie URL that allows the fixed TV terminal to access this update services) which becomes accessible to the fixed terminal after download . These routing policies update allow the fixed terminal to access the server of the content provider for viewing content on this terminal associated with the update of the subscription.

 Sql07: "service personalization update" step. During this optional step, the PFS platform updates the personalization data (in particular from previous uses on the mobile terminal) that will be exported to the fixed terminal.

 Sql08: step "configuration_Key generation update". This optional step corresponds to the update by the platform PFS of the unique Configuration-Key configuration key from the identifier OM_UI of the mobile terminal, characteristics of the fixed terminal determined from the type of terminal (device type) and the update of the requested service.

 Sql08bis: The "writing of configuration parameters in databases" sequence from the platform to the subscribed services and profile databases This sequence corresponds to the update of the configuration parameters in the Profile server and subscribed services databases. sequence is similar to the SqlObis sequence of the first mode.

 Sql09: "application_download (personalized preferences, OM_UI, routing policies, configuration key) sequence" from the PFS platform to the handheld. This optional sequence corresponds to the download on the mobile terminal of the update of the application already installed on the fixed terminal. The download includes customization data (favorite Live Channels, bookmarked VoDs, social networking links, personalized welcome screen) updated, the mobile terminal identifier OM_UI, the updated routing parameters, the key of configuration (configuration key) update. This sequence is similar to the sequence Sql l.3 of the first mode.

Sql09bis: sequence "application install". This sequence corresponds to the installation on the fixed terminal of the updates of the application already downloaded from the mobile terminal relating to the requested service. This sequence is similar to the Sql2 sequence of the first mode.

 Sql 10: sequence "application_update" (configuration_key). This optional sequence corresponds to the status (successful / non successful) of the update of the service offer transmitted from the fixed terminal to the PFS service platform.

 Sql l l: "account_update" sequence. This sequence corresponds to the update of the account requested by the service platform to the information system SI of the content provider.

 Sql 12: sequence "user_notification (optional: account update)" from the PFS platform to the mobile terminal. This sequence corresponds to a notification of the update to the mobile terminal.

 According to one embodiment, the user can obtain an update of his service offer from a fixed terminal on which a service of his offer is already activated. This mode is detailed with reference to FIG. 16, which is a circuit diagram of the exchanges (call flow) between the previous entities during the execution on the fixed and mobile terminals of the program instructions of a software module conforming to the mode of communication. embodiment of the invention.

 Sq201: sequence "update_account_request (configuration_key, requested_services)" from the fixed terminal to the content provider. This sequence corresponds to the update request sent by the fixed terminal. This sequence is similar to the update sequence Sq101 from the mobile terminal.

 Sq202: sequence "user notification (OM_UI, requested_services)" by the mobile access network to the mobile terminal. This sequence corresponds to a request for authorization of the mobile terminal to continue in the update.

 Sq202bis: sequence "user confirmation". This sequence is a response to the sequence Sq202.

 Sq203: sequence "update_account_request (OM_UI, requested_services)" between the PFS platform and the SI information system. This sequence is similar to the sequence Sql03 update mode from the mobile terminal.

 Sq204: "Check of Compatibility (subscribed offer, device capabilities)" step.

This sequence is similar to the sequence Sql04 update mode from the mobile terminal.

Sq205_Sq208bis: These sequences are similar to the Sql05_Sql08bis sequences of the update mode from the mobile terminal. Sq209: "application_download (personalized preferences, OM_UI, routing policies, configuration key) sequence" from the PFS platform to the fixed terminal. This sequence corresponds to the download on the fixed terminal of the update of the application already installed on the fixed terminal. The download includes customization data (favorite Live Channels, bookmarked VoDs, social networking links, personalized welcome screen) updated, the mobile terminal identifier OM_UI, the updated routing parameters, the key of configuration (configuration key) update.

 Sq210_Sq212: These sequences are similar to the Sql 10 -Sql 12 sequences of the update mode from the mobile terminal.

 The simplified structure of a mobile terminal according to the invention implementing a method of access to a multi-media content according to the invention is described below and illustrated by FIG. 17.

 Such a terminal TM comprises an antenna ANT, a transmission / reception chain E / R_IR for Γ transmission / reception of a signal according to a short distance technology, a transmission / reception chain E / R_Rw for Γ transmission / reception of a signal according to a radio technology, a memory MEM_TM comprising a RAM buffer, a processing unit μΡ_ΤΜ equipped for example with a microprocessor and driven by a computer program Pg_TM for an implementation of an access method to a multi media content according to the invention.

 At initialization or following input from the user via a human machine interface (HMI), the code instructions of the computer program Pg_TM are for example loaded into the buffer before being executed by the processor of the computer. processing unit μΡ_ΤΜ. The microprocessor of the processing unit μΡ_ΤΜ implements in particular the following steps according to the instructions of the computer program Pg_TM, cooperating with the various means of the terminal:

 a discovery phase Sql, Sq2 of a fixed TV terminal near the mobile terminal TM, comprising storage by the mobile terminal of device type data of the fixed terminal,

 a transmission Sq3 from the mobile terminal of a request for activation of a service of access to multi-media content enriched with data (device type) profile of the fixed terminal to a server (PFS TV) management offer of services from an FC content provider,

an Sql 1.3 download of an application corresponding to the required service selected according to the device type data of the fixed terminal and adapted according to user configuration data relating to the service,

 a Sql2 installation on the fixed terminal of the application downloaded to the mobile terminal.

 The mobile terminal can implement other steps, in particular those detailed in the previously described embodiments.

 The transmitting / receiving means E / R_IR cooperates with the processing unit μΡ_ΤΜ particularly during the discovery and installation phases. The transmitting / receiving means E / R_Rw and the antenna ANT cooperate with the processing unit μΡ_ΤΜ more particularly during the transmission and download phases.

 The simplified structure of a fixed terminal according to the invention implementing a method of access to a multi-media content according to the invention is described below and illustrated by FIG. 18.

 Such a TV terminal comprises an antenna ANT_TV, a transmission / reception chain E / R_HF for the reception of a television signal (in accordance with a broadcast standard for example of the DVB-T type, DBT-T2, etc.) transmitted for example in HF, VHF, a transmission / reception chain E / R_IR for Γ transmission / reception of a signal according to a short distance technology, a transmission / reception chain E / R_IP for the transmission / reception of messages according to a protocol ΓΡ, for example transmitted in ADSL, a memory MEM_TV comprising a RAM buffer, a processing unit μΡ_Τν equipped for example with a microprocessor and driven by a computer program Pg_TV for implementing a method access to a multi-media content according to the invention.

 At initialization or following an input from the user via a human machine interface (HMI), the code instructions of the computer program Pg_TV are for example loaded into the buffer before being executed by the processor of the computer. μ unité_Τν processing unit. The microprocessor of the processing unit μΡ_Τν implements in particular the following steps according to the instructions of the computer program Pg_TV, cooperating with the various means of the terminal:

a discovery phase Sql, Sq2 between a mobile terminal TM and the fixed terminal TV, the mobile terminal being close to the fixed terminal, comprising storage by the mobile terminal of "device type" profile data of the fixed terminal, an installation Sql2 on the fixed terminal from the mobile terminal of a downloaded application (Sql 1.3) beforehand on the mobile terminal, the application corresponding to a service of access to a multimedia content selected according to the data (device type) of the fixed terminal profile and adapted according to user configuration data relating to the service,

 a Sql3, Sql5.3 activation phase of the multi-media content access service between the fixed terminal and a service provider management server of a multi-media content provider.

 The fixed terminal may implement other steps, in particular those detailed in the previously described embodiments.

 The transmitting / receiving means E / R_IR cooperates with the processing unit μΡ_Τν more particularly during the discovery and installation phases. The transmitting / receiving means E / R_IP cooperates with the processing unit μΡ_Τν more particularly during the activation phase.

 Although in the context of the description of the invention, a distinction is made between a fixed terminal and a mobile terminal, the access method according to the invention is fully compatible with an implementation with a mobile terminal. place and place of the fixed terminal. In the claims, it must therefore be understood that the words "fixed terminal" may be replaced by the words "mobile terminal". The latter must then be considered as a second mobile terminal, for example smartphone, tablet, ipod.

Claims

 A method of accessing a multi-media content accessible via a telecommunication network, initialized from an identified mobile terminal (OM_UI) from a mobile operator (OM), characterized in that the method comprises:  a discovery phase (Sql, Sq2) by the mobile terminal of a fixed terminal (TV) nearby, including storage by the mobile terminal of device type data of the fixed terminal,  a transmission (Sq3, Sq4, Sq5.1, Sq5.2, Sq5.3, Sq5.4) from the mobile terminal of a request to activate a service for access to multimedia content enriched with data ( device type) of the fixed terminal profile to a content provider (FC) service provider management server (PFS TV), a check (Sq6, Sq6.1, Sq6.2, Sq6.3, Sq6 .4, Sq6.5, Sq.6.6) of a legitimacy of access to the content based (Sq6.1) of a service offer subscribed by the user of the mobile terminal to the content provider (FC),  a selection (Sq7) of an application corresponding to the required service, to be installed (Sql2) on the fixed terminal, according to data (Sq6.2) of the profile of the fixed terminal,  an adaptation (Sq 9) of the application by the bid management server based on user configuration data relating to the service, an installation (Sql2) on the fixed terminal of the downloaded application (Sql 1.1, Sql 1.2, Sql 1.3) on the mobile terminal. A method of accessing a multi-media content according to claim 1 wherein: the discovery phase (Sq1, Sq2) further comprises a storage by the mobile terminal of characteristics (access type) of the fixed access network, the mobile terminal further transmits the characteristics of the fixed access network to the content provider (FC) service offering management server, the fixed terminal (TV) having an addressable IP address via the telecommunication network.  A method of accessing a multi-media content according to one of claims 1 to 2 wherein the activation request is transmitted from the mobile terminal via a cellular mobile access network, further comprising: the substitution (Sq5.2, Sq5.3) by the mobile access network of an identifier (OM_UI) of the mobile terminal present in the activation request by an identifier (FC_UI) known to the content provider. A method of accessing a multi-media content according to one of claims 1 to 2 wherein:  the content provider's service offer management server (PFS TV) requests the mobile terminal to identify itself to obtain an identifier of the mobile terminal in the absence of the activation request of an identifier of this mobile terminal (OM_UI).  A method of accessing a multi-media content according to one of claims 1 to 4, further comprising:  generation (SqlO) by the service provider management server of the content provider of a unique configuration key from an identifier (OM_UI, FC_UI) of the mobile terminal, from the device type data of fixed terminal profile and from the required service,  inserting in application settings to download the configuration key and routing parameters for access from the fixed terminal to the multi-media content by the application to be downloaded, an activation request ( Sql3) of the application from the fixed terminal set with the routing parameters and the configuration key. A method of accessing a multi-media content according to the preceding claim further comprising:  storing (lObis) in one or more databases of the configuration key (configuration_key) and routing parameters with the user configuration data relating to the service in a profile associated with the fixed terminal. A method of accessing a multi-media content according to the preceding claim wherein the content provider manages a database which contains for a given user, the list of subscribed services and the list of services activated by terminal with the associated configuration key at the terminal and at the service, further comprising:  the update (SqlObis) of the database with the configuration key generated for the fixed terminal and the requested service. A method of accessing a multi-media content according to one of claims 6 to 7, further comprising: a transmission from the mobile terminal of a request to deactivate the service configured with the Content Provider (FC) Service Offer Management (FC) server configuration key (Configuration_Key).  9. A method of accessing a multi-media content according to one of claims 6 to 8, further comprising:  a transmission from the content provider (FC) service provider management server (PFS TV) of a deactivation request of the service parameterized with the configuration key to the fixed terminal.  A method of accessing a multi-media content according to one of claims 6 to 9, further comprising:  a transmission (SqlOl) from the mobile terminal of a service update request parameterized with the configuration key to the content provider (FC) service provider management server (PFS TV).  The method of accessing a multi-media content according to one of claims 1 to 10, further comprising:  the reception (Sql4.3) by the mobile terminal of a security code generated from the Content Provider (FC) service offering management server (PFS TV),  the provision of the security code to the fixed terminal,  the transmission (Sql4.4) from the fixed terminal of the security code to the content provider (FC) service offering management server (PFS TV), - the transmission (Sql5.3) of a content provider (FC) service offering management (FC) server activation authorization request (PFS) to the fixed terminal only if the security code received is identical to the generated code. 12. A method of accessing a multi-media content according to one of claims 1 to 11 wherein the discovery phase implements a short-distance point-to-point link between the mobile terminal and the fixed terminal.  13. A method of accessing a multi-media content according to one of claims 1 to 12 wherein the discovery phase comprises a return to the user of fixed terminal profile data for confirmation by the user of the continuation of the process with this fixed terminal.  14. A mobile terminal comprising a software module with program instructions such that their execution implements the following steps: a discovery phase (Sql, Sq2) of a fixed terminal (TV) near the mobile terminal, comprising a storage by the mobile terminal of device type data of the fixed terminal,  a transmission (Sq3) from the mobile terminal of a request to activate a service for access to multi-media content enriched with the device type data of the fixed terminal to a server (PFS TV) content provider (FC) service offering management,  a download (Sql l.3) of an application corresponding to the required service selected according to the device type data of the fixed terminal and adapted according to user configuration data relating to the service,  an installation (Sql2) on the fixed terminal of the downloaded application (Sql 1.3) on the mobile terminal.  15. Fixed terminal (TV) comprising a software module with program instructions such that their execution implements the following steps:  a discovery phase (Sql, Sq2) between a mobile terminal (TM) and the fixed terminal (TV), the mobile terminal being close to the fixed terminal, including storage by the mobile terminal of device type data of fixed terminal,  an installation phase (Sql 2) on the fixed terminal from the mobile terminal of a downloaded application (Sql l.3) beforehand on the mobile terminal, the application corresponding to a multi-content access service; media selected based on the fixed device profile data type (device type) and adapted according to service configuration data of the user,  an activation phase (Sql3, Sql5.3) of the multi-media content access service between the fixed terminal and a service provider management server of a multi-media content provider.