WO2017089710A1

WO2017089710A1 - Method for distributing rights to a service and service platform

Info

Publication number: WO2017089710A1
Application number: PCT/FR2016/053072
Authority: WO
Inventors: Emmanuel Bertin; Stéphane CAZEAUX
Original assignee: Orange
Priority date: 2015-11-25
Filing date: 2016-11-24
Publication date: 2017-06-01
Also published as: FR3044192A1; FR3044192B1

Abstract

The method for distributing rights to a service according to the invention is intended to be implemented by a service platform and comprises: - a step of constructing (G30) a database (DB) referred to as an identities and rights database, comprising, for each device participating in the service, an identity (ID(3)) intended to be used by said device during participation thereof in the service and, associated with said identity, at least one item of information representative of the rights to the service allocated to the device; and - a step of transmitting (G50) of said identity and rights database to each device participating in the service.

Description

Method of distributing rights on a service and service platform

Background rinenvention

The invention relates to the general field of communications.

It relates more particularly to the implementation of services such as communication services such as a conference service (video conference, audio conference or audio / video type conference) or a multimedia data stream broadcasting service, or any other type of services involving a plurality of actors, as well as the management of related rights.

Most known conferencing systems are based on the use of a service platform (audio, video, web, etc.), also called a conference bridge, which centralizes and controls all the resources implemented during a conference. the conference. This service platform is based on a centralized management of access and rights related to the conference (eg right to moderate the conference, right to close the conference, etc.).

Thus, when a user wishes to perform an action during the conference, such as for example enter the conference, mute the microphone of one of the devices participating in the conference or close the conference, the service platform controls that the the user has the right to request such action, and if necessary, executes the said action.

However, the emergence of new technologies, and in particular web technologies such as the Web Real-Time Communication (WebRTC) technology developed within the W3C and IETF consortia, makes it possible today to envisage an evolution of communication services, particularly conference services, which no longer requires the implementation of centralized resources at a single service platform. Such a service is for example described in the patent application FR 1,359,692.

According to the approach adopted in the document FR 1 359 692, the terminals of the users participating in a communication service such as a conference service can, according to their respective capacities, make available to the conference service their own resources to establish directly between them flow transmission channels, these channels then serving as a support for a communication session implemented as part of the conference service. The rendering of the conference service is no longer centralized at the level of the service platform (that is to say the conference bridge), but is relocated and distributed in whole or in part to the terminals of the users participating in the service. .

In such a context, the use of centralized management at the service level of rights and access to conference services can be complex or even inappropriate. There is therefore a need for an alternative rights management mechanism relating to a service such as for example a communication service, which notably makes it possible to effectively manage these rights when the rendering of the service is distributed over several devices, and in particular on user terminals of the service. Object and summary of the invention

The invention responds in particular to this need by proposing a method for distributing rights on a service, intended to be implemented by a service platform and comprising: a step of building a database called identities and rights comprising, for each device participating in the service, an identity intended to be used by this device during its participation in the service and, associated with this identity, at least one information representative of rights on the service allocated to the device; and

A step of transmitting this database of identities and rights to each device participating in the service.

The invention correlatively targets a service platform capable of broadcasting rights on a service, this service platform comprising:

A construction module, configured to construct a database of identities and rights comprising, for each device participating in the service, an identity intended to be used by this device during its participation in the service and associated with this identity at least one representative information of service rights allocated to the device; and

A transmission module, configured to transmit this database of identities and rights to at least one other device participating in the service.

The invention thus advantageously proposes to construct, at the level of a centralized service platform, a database of identities and rights on the service, and then to broadcast this database of identities and rights to the various devices participating in the service for they can have local information on the rights of each device participating in the service.

This database of identities and rights has for example the form of a matrix grouping, for each of the devices participating in the service, the identity used by this device during its participation in the service and one or more information relating to rights assigned to this device on the service. The identity of the device stored in the database of identities and rights is typically information of reachability of the device during the service, such as for example a telephone number, an email address, etc. The information about the rights assigned to a device on the service may be in the form of actions authorized to the device (eg mute the microphone of another device during the conference, close the conference, etc.). , and / or one or more roles associated with the device during its participation in the service (for example a moderator role), each device having the prior knowledge of the correspondence between a role and the actions authorized by this role, or having the possibility to access it freely.

Advantageously, the database of identities and rights thus constructed is transmitted in accordance with the invention to the devices participating in the service. In this way, each service user is informed of the rights and roles assigned to other users of the service. Thus, when a device A requires from a device B an action during the implementation of the service, it can, from the information contained in the database that has been transmitted, determine whether the device A is authorized to request such action and if necessary perform the action or otherwise refuse to perform this action. This verification can be done very quickly, thanks to the database stored locally at device B, without consulting the service platform.

The invention therefore has a preferred application, but not limited to, when the rendering resources of a service are distributed over several devices (terminal (ux) of user (s), platform (s) of service, server (s) , etc.), by coupling rights management on the service with the rendering of the service itself, a control of the rights that can be carried out thanks to the database of identities and rights diffused by the service platform at the level of each device participating in the service. rendering of the service.

It is noted that no limitation is attached to the type of service rendered. For example, it may be a service for distributing media or conference streams as mentioned above, as a service to which several connected objects participate by cooperating with each other so as to perform different actions (eg measurement of parameters , processing of measurements, rendering of measurements, etc.).

According to a first variant embodiment of the invention, for at least one device participating in the service, the identity and said at least one information representative of the rights on the service allocated to this device are obtained, by the service platform, from the device when registering with it.

This identity and the related rights may have been transmitted to the device in advance by a platform of rights of service.

According to a second variant embodiment of the invention, for at least one device participating in the service, said at least one information representative of the service rights allocated to this device comprises a role associated with the device during its participation in the service.

The use of one or other of the aforementioned variants depends on the architecture envisaged for rendering the service, the service rights allocation platform making it possible to specify to each user and / or participant in the service the rights and the roles assigned to it.

In a particular embodiment, the identity and rights database is encrypted and / or signed by the service platform before being transmitted to each device.

In particular, the identity and rights database can be encrypted and / or signed according to a known asymmetric cryptographic scheme, using a private key allocated to the service platform, the public key associated with this private key. being accessible by the devices participating in the service (for example stored in memory of these devices).

With such an encryption and / or signature, the devices can ensure the origin and integrity of the database of identities and rights transmitted to them.

Thus, thanks to the invention, the devices participating in the service do not need to establish a relationship of trust between them (for example via an authentication or a mechanism two-by-two pairing), since a trusted entity, the Service Rights Management Platform, has certified them through the transmission of the identity and rights database that they can to trust each other. The invention thus simplifies the implementation of the service.

Alternatively, other mechanisms can be envisaged to allow each device to verify the origin of the identity and rights database that is transmitted to it, such as a control of the IP address (Internet Protocol) source to the origin of the transmission of the database, or the domain name to which the service platform is attached, or a prior authentication mechanism implemented between each device and the service platform, etc. The choice of one or the other of these mechanisms can depend in particular on the level of security imposed by the context of use of the service.

In a particular embodiment, the distribution method comprises:

A step of receiving a device participating in the service of an indication of a change in the rights allocated to this device on the service;

A step of updating the database of identities and rights for the identity used by the device according to said indication; and

A step of transmitting the identity and rights database updated to each device participating in the service.

This embodiment advantageously makes it possible to take into account an evolution of the rights and / or the roles of the devices during the use of the service.

In a particular embodiment, the change of rights indication includes an authentication token corresponding to at least one new right assigned to the device.

This allows the service platform to ensure that the device is allowed to change rights during service.

As mentioned above, the invention is therefore based on the construction and distribution to the devices participating in a service of an identity and rights database by a centralized service platform managing the rights to this service, but also on the use of this database of identities and rights by the devices during their participation in the service.

Thus, according to another aspect, the invention also relates to a method of processing a request by a first device intended to be implemented during a participation of the first device in a service, this method comprising:

A step of obtaining a database of identities and rights transmitted by a service platform following the execution by said platform of a service rights distribution method according to the invention, said database of identity and rights comprising, for each device participating in the service, an identity intended to be used by this device during its participation in the service and, associated with this identity, at least one piece of information representative of rights on the service allocated to the device; A step of receiving a request from a second device participating in the service, this request comprising an identity used by the second device during its participation in the service and an action intended to be performed by the first device;

A verification step, in the database of identities and rights, if the identity included in the request has the right to request the execution of said action by the first device; and

- where appropriate, a step of performing the required action.

Correlatively, the invention also relates to a device, said first device, able to participate in a service, this first device comprising:

A obtaining module, able to obtain a database of identities and rights transmitted by a service platform according to the invention able to broadcast rights on the service, said identity and rights database comprising, for each device participating in the service, an identity intended to be used by this device during its participation in the service and, associated with this identity, at least one representative information of rights on the service allocated to the device;

A reception module, able to receive a request from a second device able to participate in the service, this request comprising an identity used by the second device during its participation in the service and an action intended to be executed by the first device; device;

A verification module, activated by the reception module following receipt of the request from the second device, and configured to verify in the identity and rights database whether the identity included in the request has the right to require the execution of said action by the first device; and

An execution module configured to perform the action required in the request, activated if the verification module determines that the identity included in the request has the right to request the execution of this action by the first device.

In addition, in a particular embodiment, the identity and rights database transmitted by the service platform is encrypted and / or signed, the processing method comprising a step of decryption and / or validation of the signature of the service provider. identity and rights base before implementing the verification step.

The processing method and the device according to the invention benefit from the same advantages mentioned above as the rights distribution method and the service platform according to the invention.

In a particular embodiment, the various steps of the distribution method and / or the processing method are determined by computer program instructions.

Accordingly, the invention also relates to a computer program on an information carrier, this program being capable of being implemented in a service platform or more generally in a computer, this program comprising instructions adapted to the implementation of the steps of a distribution method as described above. The invention also relates to a computer program on an information medium, this program being capable of being implemented in a device such as a terminal, a service platform, a server or more generally in a computer, this program comprising instructions adapted to the implementation of the steps of a treatment method as described above.

Either of these programs can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form , or in any other desirable form.

The invention also relates to a computer-readable information medium, comprising instructions of a computer program as mentioned above.

The information carrier may be any entity or device capable of storing the program. For example, the medium may comprise storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording means, for example a hard disk.

On the other hand, the information medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The program according to the invention can be downloaded in particular on an Internet type network.

Alternatively, the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the method in question.

In another aspect, the invention also provides a system providing a service and comprising:

A service platform according to the invention, able to broadcast rights on the service; and

A plurality of devices according to the invention able to participate in the service.

The system according to the invention has the same advantages mentioned above as the rights distribution method, the processing method, the service platform and the device according to the invention.

In a particular embodiment, the system may further include a rights allocation platform on the service, this rights allocation platform comprising:

An authentication module, configured to authenticate a device intended to participate in the service;

A module for assigning to this device an identity intended to be used by the device during its participation in the service and rights on the service; and A module for transmitting, to the device and / or the service platform, the identity and at least one piece of information representative of the rights assigned to the device by the assignment module.

This embodiment has a preferred application when the assignment of rights and the distribution of rights are distributed on separate platforms, for example in the event of a distributed service architecture.

It can also be envisaged, in other embodiments, that the rights distribution method, the processing method, the service platform, the device and the system according to the invention present in combination all or part of the aforementioned characteristics.

Brief description of the drawings

Other features and advantages of the present invention will emerge from the description given below, with reference to the accompanying drawings which illustrate an embodiment having no limiting character. In the figures:

FIG. 1 represents a system offering a conference service according to the invention in a particular embodiment;

- Figures 2 and 3 respectively show an example of hardware architecture of a service platform and a device according to the invention in a particular embodiment;

FIG. 4 represents, in the form of a flow chart, the main steps of a method implemented by a device of the system of FIG. 1, according to the invention, in a particular embodiment;

FIG. 5 represents, in the form of a flow chart, the main steps of a method implemented by a platform for assigning rights to the conference service offered by the system of FIG. 1, in a particular embodiment. ;

FIG. 6 represents, in the form of a flow chart, the main steps of a method for distributing rights over the conference service offered by the system of FIG. 1 as it is implemented by a distribution platform of FIGS. rights of the system of Figure 1, in a particular embodiment;

FIG. 7 illustrates a first basic example of identities and rights that can be used by the system of FIG. 1;

FIG. 8 represents, in the form of a flow chart, the main steps of a processing method implemented by a device of the system of FIG. 1, in a particular embodiment; and

FIG. 9 illustrates a second basic example of identities and rights that can be used in the context of the invention for a system comprising a plurality of connected objects.

Detailed description of the invention FIG. 1 represents, in its environment, a system 1 according to the invention, offering a plurality of devices a service such as for example a CONF conference type service (audio conference, videoconference or audio / video conference) .

There is no limitation, however, on the nature of the service offered by the system.

1, and other services may be envisaged, such as another multimedia data stream broadcasting service (audio, video, text, etc.), an online gaming service, a service based on several connected objects. between them, etc.

In the example envisaged in FIG. 1, the rendering of the conference service CONF is distributed on several devices 3 of the system 1 participating in the same session of the service, these devices 3 being in accordance with the invention and able to communicate with each other via a telecommunications network 2 (eg Internet, intranet, fixed or mobile network, etc.). The devices 3 more particularly here comprise a plurality of user terminals (three in the example of FIG. 1 referenced by 3-1, 3-2, 3-3) and a service platform 3-4, this platform of service being for example a conference bridge known per se.

Each terminal 3-1, 3-2, 3-3 hosts here a web application (or "web app" in English) of decentralized conference, accessible in a manner known per se by the user of the terminal via a web browser. The rendering of the conference service is for example distributed on the terminals 3-1, 3-2, 3-3 and on the service platform 3-4 in a way similar or identical to that proposed in the document FR 1 359 692 , not detailed here.

This example is of course only given for illustrative purposes, and no limitation is attached to the nature of the devices 3 on which the rendering of the communication service CONF is based. It can thus be user terminals such as mobile phones, digital tablets or PC or portable computers, servers, service platforms, connected objects, etc. Similarly, no limitation is attached to the number of devices considered.

In the embodiment described here, the system 1 also includes, for managing rights on the CONF conference service:

A service platform 4 in charge of assigning rights to the CONF service (hereinafter referred to as rights allocation platform 4). It is this platform which, in the example envisaged in FIG. 1, assigns to each of the devices 3 of the system 1 an identity intended to be used by each device during its participation in the conference service CONF, as well as rights, or in an equivalent way, one or more roles on this service; and

A service platform 5 in charge of distributing the rights allocated on the CONF service to the devices 3 of the system 1, in accordance with the invention (hereinafter referred to as the rights distribution platform 5).

The platform 5 of distribution of rights is hosted here by a management server 6 as described in document FR 1 359 692, able to allow rendering of the conference service CONF distributed on the devices 3 of the system 1. The manner in which the management server 6 proceeds to this effect is described in detail in the document FR 1 359 692 and is not repeated here.

The platform 4 rights allocation can also be hosted by the server 6, or alternatively, as in the example shown in Figure 1, by a server 7 separate from the server 6 but able to communicate with the server 6, by example via the telecommunications network 2, so as to allow interaction between the two platforms 4 and 5.

In the embodiment described here, the rights distribution platform 5 has the hardware architecture of a computer, as represented in FIG. 2. It notably comprises a processor 8, a read-only memory 9, a random access memory 10, a non-volatile memory 11 and a communication module 12 comprising in particular means known per se for communicating on the telecommunications network 2 (eg depending on the network considered, a network card, a SIM card (Subscriber Identity Module), etc.; ). The read-only memory 9 constitutes a recording medium according to the invention, readable by the processor 8 and on which is recorded a computer program PROG1 (or software) according to the invention comprising instructions for executing the steps of the diffusion method according to the invention.

The computer program PROG1 here defines modules or functional components and software rights distribution platform 5, able to implement the steps of the broadcast method according to the invention. These software modules are able to access and / or control the hardware resources of the platform 5 (and in particular the hardware resources 9-13 mentioned above). They include here:

A construction module 5A of a database DB called identities and rights on the CONF conference service; and

A distribution module 5B of the database DB to the devices of the system 1.

The functions of the modules 5A and 5B are detailed later with reference to the corresponding steps of the distribution method according to the invention.

In the embodiment described here, the rights allocation platform 4 also has the hardware architecture of a computer, this architecture being identical or similar to that of the rights distribution platform 5 illustrated in FIG. platform 4 read-only memory is a recording medium, readable by the processor of the platform 4, and on which is recorded a computer program defining here various modules (functional components) and software of the platform 4. These software modules are able to access and / or control the hardware resources of the service platform 5 and include here:

An authentication module 4A, configured to authenticate the devices 3 of the system 1 wishing to participate in the CONF conference service;

An assignment module 4B to these identity and rights devices on the CONF conference service; and A 4C transmission module of these identities and rights to the devices of the system 1. In a variant, the transmission module 4C can be configured to transmit these identities and rights to the rights distribution platform 5 via the network of Telecommunications 2 for example, or if both platforms 4 and 5 are hosted by the same server, via a data bus or communication specific to the server.

The functions of the 4A-4C modules are detailed later.

Similarly, in the embodiment described here, each device 3 of the system 1 (ie terminals 3-1, 3-2, 3-3, and conference bridge 3-4), have the hardware architecture of a computer, as represented in FIG. 3. It comprises in particular a processor 13, a read-only memory 14, a random access memory 15, a non-volatile memory 16 and a communication module 17 comprising, in particular, means known per se for communicating on the network of telecommunications 2 (eg depending on the network considered, a network card, a SIM card (Subscriber Identity Module), etc.). The read-only memory 14 constitutes a recording medium in accordance with the invention, readable by the processor 13 and on which is recorded a computer program PROG2 (ie software) according to the invention comprising instructions for performing the steps the method of processing a request according to the invention.

The computer program PROG2 here defines modules or functional components and software devices 3, able to implement the steps of the treatment method according to the invention. These software modules are able to access and / or control the hardware resources of the device (and in particular the hardware resources 13-17 mentioned above). They include here:

A obtaining module 3A of the database DB distributed by the platform 5 of distribution of rights;

A reception module 3B for requests relating to the CONF conference service;

A verification module 3C able to interrogate the database DB; and

A 3D execution module, able to perform various actions required by the device as part of the CONF conference service and the functions that it performs for rendering the CONF conference service.

The functions of the modules 3A-3D are detailed later with reference to the corresponding steps of the treatment method according to the invention.

We will now describe, with reference to FIGS. 4 to 6, the main steps of the processes implemented respectively according to the invention, by the devices 3 of the system 1 (FIG. 4), by the platform 4 of assignment of rights ( FIG. 5), and by the distribution platform 5 (FIG. 6), in a particular embodiment. FIG. 4 represents the processing method implemented by each of the devices 3 of the system 1 participating in the rendering of the conference service CONF during a session involving these devices, that is to say by the terminals 3-1, 3-2, 3-3 and by the conference bridge 3-4. For the sake of simplification in the following description, unless explicit reference is made to one of the devices 3-1, 3-2, 3-3 or 3-4, the general reference 3 to designate any of these devices. When this general reference 3 is used, it means that the steps and other parameters described in connection with this general reference are applied to each of the devices 3- 1, 3-2, 3-3 and 3-4.

Referring firstly to Figures 4 and 5, it is assumed here that in order to access CONF conference service, each of the devices 3 of the system 1 has registered prior to this service (step E10), for example with the platform 4 for the assignment of rights. During this recording, in a manner known per se, each device 3 has agreed with the platform 4, an identifier (or "login" in English) and a password to authenticate with it.

It is now assumed that the devices 3 of the system 1 wish to confer with one another via the CONF service (otherwise referred to as "session" of the conference service in the description). For this purpose, each device 3 authenticates here in a first time with the platform 4 rights assignment (steps E20 and F10), in a manner known per se, using the identifier and the password exchanged during prior registration of the device 3.

With reference to FIG. 5, following the authentication of a device 3 via its authentication module 4A, the platform 4, responsible for managing the access rights to the conference service CONF, establishes via its assignment module 4B the identity ID (3) intended to be used by this device on the service (ie identity ID (3-1) for the terminal 3-1, identity ID (3-2) for the terminal 3 -2, identity ID (3-3) for the terminal 3-3 and identity ID (3-4) for the device 3-4 respectively) (step F20). This identity reflects the way in which the device 3 in question will be recognized by the other devices participating in the service. For example, for a conference service, it may be the IP address of the device 3. It is assumed here that the platform 4 affects:

At the terminal 3-1, the identity ID (3- 1) corresponding to the IP address @ 3-1 of the device 3-1;

At the terminal 3-2, the identity ID (3-2) corresponding to the IP address 3-2 of the device 3-2;

At the terminal 3-3, the identity ID (3-3) corresponding to the IP address 3-3 of the terminal 3-3; and

To the device 3-4, the identity ID (3-4) corresponding to the IP address @ 3-I of the device 3-4.

Alternatively, other identities may be envisaged, depending in particular on the service in question. For example, the identity established by the platform 4 for a device 3 may correspond to its telephone number, a nickname, etc.

This identity is established here by the platform 4 from information previously stored in a non-volatile memory of the platform, and obtained for example during the registration of the device 3 (it may be in particular information provided by the user of the device. device 3 when recording at conference service or selected by platform 4). It should be noted that the identity ID (3) established in step F20 by the platform 4 for the device 3 is not necessarily linked to the identifier used by the device 3 to authenticate with the platform 4. The rights allocation platform 4 also allocates (ie allocates) to the device 3, through its assignment module 4B, rights RGT (3) on the conference service CONF (ie rights RGT (3 -1) for the terminal 3-1, TMR rights (3-2) for the terminal 3-2, GTA rights (3-3) for the terminal 3-3 and GTA rights (3-4) for the device 3-4 respectively) (step F30). By rights allocation is meant here that the platform 4 allows certain actions specific to the device 3 in the framework of the service CONF to the device 3. It may be actions consisting in requesting from one or more other devices the performance of a particular action (eg mute a device, disconnect a device, obtain device information, etc.), or actions that may apply to the device itself if this is relevant to the service in general (eg reboot the service), or to all devices (eg terminate the conference). No limitation is attached to the nature of the rights allocated to each of the devices 3 by platform 4, these rights depending of course on the service in question.

The rights assigned to a device 3 may be specified directly as such or in a coded manner, or may derive indirectly from one or more roles assigned by the platform 4 to the device 3 vis-à-vis one or more devices of system 1 (eg in the case of a conference service: organizer, moderator, participant, etc.). The correspondence between role and related rights is here assumed to be known by each of the devices 3 participating in the conference service CONF and the service platforms 4 and 5. It is for example communicated to each device 3 when it is registered with the CONF conference service.

Whatever the form in which they are represented, the TMN rights (3) constitute information representative of the rights on the service CONF allocated to the device 3 within the meaning of the invention.

In the example of the CONF conference service considered here as an illustration, two distinct roles, ie "moderator" (or supervisor) or "participant", that can be attributed by the platform 4 to the devices 3, for which the associated rights, are considered resulting therefrom are:

- role of "moderator" (or supervisor):

o Right to cut the microphone of another device;

o right to disconnect another device; and

o right to obtain information from another device;

- role of "participant":

o Right to obtain information from another device.

More specifically, it is assumed here that platform 4 assigns the terminal 3-1 the role of moderator, and terminals 3-2, 3-3 and device 3-4 roles of participant in the conference.

In the embodiment described here, the assignment module 4B of the rights allocation platform 4 then constructs, for each device 3, an object OBJ (3) (ie a data structure) comprising the identity ID (3) and the rights RGT (3) assigned to the device 3 (step F40).

Then it encrypts this object OBJ (3) using an asymmetric encryption algorithm implemented by its transmission module 4C, in a manner known per se, using a PrivK4 private encryption key characteristic of the CONF service and previously allocated to platform 4 by a trusted authority (step F50). This private encryption key PrivK4 is for example stored in the non-volatile memory of platform 4, and associated with a public encryption key PubK4. No limitation is attached to the asymmetric encryption algorithm used by the platform 4C transmission module 4 to encrypt the object OBJ (3). The resulting encrypted object is designated CRYPT_OBJ (3).

As a variant, a symmetric encryption algorithm can be envisaged for encrypting the OBJ object (3), which uses a secret encryption key SK4 shared between the rights allocation platform 4 and the platform 5. This shared key SK4 has for example been exchanged between the platform 5 and the platform 4 when registering the device 3 to the CONF service.

In another variant, the platform 4 signs the object OBJ (3) or the encrypted object

CRYPT_OBJ (3) using a known digital signature algorithm and PrivK4 private encryption key.

The encrypted object CRYPT_OBJ (3) is then transmitted to the device 3 by the transmission module 4C of the entitlement platform 4 via the telecommunications network 2 (step F60).

It should be noted that the encryption or signature of the object OBJ (3) makes it possible to ensure that the identity and the rights assigned to the device 3 by the rights allocation platform 4 are not modified by a third party (device 3 or other), only the platform 4 as a trusted entity having the knowledge of the private key PrivK4 which allowed to encrypt, respectively to sign the object OBJ (3).

Referring back to FIG. 4, the encrypted object CRYPT_OBJ (3) is received, via the telecommunications network 2, by the obtaining module 3A of the device 3 (step E30).

In the embodiment described here, the device 3 then registers with the rights distribution platform 5 and transmits to it during this registration, via the telecommunications network 2, the encrypted object CRYPT_OBJ (3) received from the rights affection platform 4 (step E40). It should be noted that the device 3, in the embodiment described here, does not decipher the encrypted object CRYPT_OBJ (3), but transmits it as it is to the platform 5.

With reference to FIG. 6, the rights distribution platform 5 thus receives, from each device 3, an encrypted object CRYPT_OBJ (3) comprising the identity ID (3) established by the platform 4 for this device 3, as well as the GTA rights (3) assigned to it (step G10).

It is assumed here that the rights distribution platform 5 has, stored for example in its non-volatile memory 11, the public key PubK4 associated with the private key PrivK4 used by the platform 4 for assigning the rights to encrypt the object OBJ ( 3). In the embodiment described here, the rights distribution platform 5 deciphers, via its construction module 5A, the encrypted object CRYPT_OBJ (3) received from the device 3 using the public key in a manner known per se. PubK4 (step G20). At the end of this decryption step, the module 5A obtains the object OBJ (3) comprising the identity ID (3) and the rights RGT (3) assigned for the use of the service CONF to the device 3.

It should be noted that if the encrypted object CRYPT_OBJ (3) comes from a device other than platform 4 and was not encrypted using the private key PrivK4 assigned to the CONF service and owned by the platform 4, this decryption step is not possible.

In another embodiment in which object CRYPT_OBJ (3) is an object signed by platform 4, platform 5 checks in step G20 the digital signature of the object in a manner known per se.

In another embodiment, the encrypted object CRYPT_OBJ (3) associated with the device 3 is transmitted directly by the rights allocation platform 4 to the rights distribution platform 5, without intervention of the device 3, for example via a internal data bus if both platforms are located on the same server, or via an Application Programming Interface (API) or via the telecommunications network 2.

The module 5A for constructing the rights distribution platform 5 extracts from the object decrypted OBJ (3) the identity ID (3) of the device 3 as well as the rights (3) which have been assigned to it and stores them in a data structure, and more particularly in the DB database of identities and rights (step G30).

The construction module 5A implements the steps G10, G20 and G30 for each of the devices 3-1, 3-2, 3-3 and 3-4 so as to build a database of identities and rights DB grouping the rights GTA (3) and identities ID (3) of all devices participating in the CONF service and in relation to each other. So we have a DB base for each use (i.e. each session) of the CONF service (that is, for each conference established as part of this service between multiple devices).

In the embodiment described here, the DB identity and rights database has more particularly the form of a matrix, that is to say a two-dimensional array, an example of which is illustrated in FIG. 7.

According to this example, each line Li of the matrix is associated with a device 3-i of the system 1 and indicates the rights allocated by the platform 4 to this device on the devices 3-j identified in the columns Cj of the matrix, where i , j = l, ..., N and N denotes the number of devices 3 of the system 1 participating in the session of the service to which the database DB relates (N = 4 in the example illustrated). The devices 3-i and 3-j are identified in line and in column by the identity established by the platform 4 of affection of rights.

Thus, the line L1 indicates that the device 3-1 whose identity is ID (3-1) = @ 3-1 has a role of moderator (indicated by "SUP" in the matrix DB) with respect to devices 3-2, 3-3 and 3- 4. In other words, the line Ll includes all the rights specified by the GTA information (3-1). Similarly, lines L2, L3 and L4 (with all the rights specified in the TMN (3-2), GTA (3-3), GTA (3-4)) indicate respectively that:

The device 3-2 whose identity is ID (3-2) = @ 3-2 has a role of participant (indicated by "PART" in the matrix DB) vis-à-vis the devices 3-1, 3 -3 and 3-4;

The device 3-3 whose identity is ID (3-3) = @ 3-3 has a role of participant (indicated by "PART" in the matrix DB) vis-à-vis the devices 3-1, 3 -2 and 3-4;

The device 3-4 whose identity is ID (3-4) = @ 3-4 has a role of participant (indicated by "PART" in the matrix DB) vis-à-vis the devices 3-1, 3 -2 and 3-3.

In other words, in view of the previously established correspondence, the device 3-1 as moderator of the service CONF has the rights to cut the microphone of the devices 3- 2, 3-3 and 3-4, to disconnect the devices 3- 2, 3-3 and 3-4 and to obtain information on devices 3-2, 3-3 and 3-4. Devices 3-2, 3-3 and 3-4 as a participant in the CONF service only have the right to obtain information from other devices in the system 1.

The DB database or matrix thus constructed by the platform 5 thus gives a synthetic overview of all the devices participating in the considered session of the conference service and the rights and identities relating to these devices. It is stored by the construction module 5A in the non-volatile memory 11 of the platform 5.

In the embodiment described here, the digital rights distribution platform 5, via its transmission module 5B, the identity and rights database DB thus constructed (step G40). It uses for this purpose an asymmetric encryption algorithm, known per se, and a private key PrivK5, associated with the conference service CONF, and assigned by a trusted authority to the platform 5. This private key PrivK5 is for example stored in the nonvolatile memory 11 of the platform 5. No limitation is attached to the asymmetric encryption algorithm used by the transmission module 5B of the platform 5 to encrypt the DB database of identities and rights. The encrypted DB database obtained is designated CRYPT_DB.

As a variant, a symmetric encryption algorithm can be envisaged for encrypting the database DB, which uses a secret encryption key SK5 shared between the rights allocation platform 5 and the devices 3. This shared key SK5 has, for example, been encrypted. exchanged between the device 3 and the platform 5 when registering the device 3 at the platform 5.

According to yet another variant, the platform 5 signs the DB identity and rights database or its encrypted version by means of a known digital signature algorithm and the PrivK5 private encryption key.

Then the 5C transmission module of the platform 5 transmits the identity and encrypted rights database CRYPT_DB to each of the devices 3 of the system 1 (step G50).

Referring back to FIG. 4, each device 3 receives the encrypted identity and rights database CRYPT_DB distributed by the platform 5 (step E50), and decrypts it using the public key PubK5 associated with the key of PrivK5 private encryption (step E60). The base identities and rights DB thus decrypted is stored by each device 3, for example in its non-volatile memory.

Thus, via the database of identities and rights DB distributed by the platform 5 of distribution of the rights on the service CONF, each device 3 participating in the conference session is informed of its own role and its rights, as well as the roles and the rights of other devices participating in this session.

We will now describe, with reference to FIG. 8, the manner in which the devices 3 use, during the conference, this database DB distributed by the platform 5 and stored locally at the level of each device, in particular for processing requests in from another device participating in the conference according to the invention.

It is now assumed that, following the distribution of the DB database, the devices 3 participate strictly speaking to a conference implemented as part of the CONF service.

It is further assumed that the user of one of the devices, for example the terminal 3-1, wishes to cut the microphone of the terminal of one of the conference participants, for example the terminal 3-2. FIG. 8 illustrates the steps implemented by the terminal 3-2 (steps of a processing method according to the invention).

To cut the microphone of the terminal 3-2, the terminal 3-1 sends, via the telecommunications network 2 for example, a request REQ to the terminal 3-2 containing its identity ID (3- 1) and an action ACT to realize by the terminal 3-2, namely here cut off his microphone.

On reception by its reception module 3B of the request REQ sent by the terminal 3-1 (step H10), the terminal 3-2 extracts the identity ID (3-1) of the request REQ and verifies, by means of its verification module 3C, in the identity and rights DB database stored in its memory if this identity has the right to ask it to execute the ACT action contained in the REQ request, namely to cut off its microphone (step H20 ). This verification step is implemented by the verification module 3C via means for querying or consulting a database known per se, by checking whether among the rights RGT (3-1) reported in the database DB for the identity ID (3-1) is the authorization to ask the device 3-2 to cut off its microphone.

In the example described in FIG. 7, the database DB indicates to the terminal 3-2 that the terminal 3-1 corresponding to the identity ID (3-1) has the role of moderator of the conference with respect to him. In accordance with the pre-established role / rights correspondence mentioned above, the 3C verification module of the terminal 3-2 deduces from this role that the terminal 3-1 has the right to request from the terminal 3-2 that it execute the ACT action. that is, it cuts off its microphone (yes answer to test step H30).

Following this positive verification, the 3D execution module of the terminal 3-2 executes the action ACT required by the terminal 3-1 and cuts the microphone of the terminal 3-2 (step H40).

If, on the other hand, the verification module 3C of the terminal 3-2 determines with respect to the information contained in the database DB that the terminal 3-1 is not entitled to request the execution of the ACT action by the terminal 3-2 (answer no to the test step H30), the 3D execution module refuses to execute the action and rejects the request REQ of the terminal 3-1 (step H40).

Thus, thanks to the invention, each device 3 participating in the rendering of the CONF conference service can know the rights and roles of each of the other devices, and directly execute remote actions in a direct communication process between the devices.

Note that the invention also makes it easy to accommodate an update rights assigned to a device 3 in use of the conference service. Thus, with reference to FIG. 4, if one of the devices 3 participating in the service for example changes role and becomes illustrative "moderator" rather than simple "participant" (yes answer to the test step E70), it sends via the telecommunications network 2 a message M to the rights distribution platform 5 to notify him (indicate) this change of role (step E80). This message comprises its identity ID (3) as well as, in the embodiment described here, a TOK authentication token (also called security token or token) associated with the new role that has been assigned to it, for example via the platform 4 to assign the rights to this effect the TOK token associated with the new role in a secure manner. Alternatively, the device 3 or its user can acquire the TOK token by any other means in a secure manner to ensure that only an authorized device or user has this token.

In this embodiment, each role is associated with a separate security token, so that the authentication token TOK itself represents information representative of the rights on the service allocated to the device within the meaning of the invention. Such an authentication token offers, in a manner known per se, a strong authentication solution making it possible to prove to the platform 5 the right of the device to pretend to this new role. This may be for example a password associated with the new role claimed by the device 3.

The authentication token associated with a role can be managed by the device 3 in a manner that is transparent to its user. Alternatively, the token may be provided to the platform 5 by the user of the device 3, in which case the message M comprises, in addition to the identity ID (3), an indication of the role change of the device 3 (eg a information representative of the new rights allocated to this device on the service or simply a message of change of role or update of these rights).

In yet another variant, the token TOK is provided in the form of a new object N_OBJ (3) encrypted by the platform 4 to the device 3, this new object reflecting the new role assigned to the device 3. In this variant, the message M transmitted by the device 3 to the platform 5 to indicate its role change includes the new object N_OBJ (3) encrypted.

In yet another variant, the TOK token may be provided to the platform 5 by the device 3 or by its user in addition to a new object N_OBJ (3) encrypted and supplied to the device 3 by the platform 4, this new object reflecting the new role assigned to the device 3.

With reference to FIG. 6, upon receipt of the message M (answer yes to the test step G60), the platform 5 controls the TOK token included in the message and updates via from its building module 5A, in the database of identities and rights DB, the rights RGT (3) associated with the identity ID (3) with the role corresponding to the token sent by the device 3 (step G30). To control the TOK token, the platform 5 consults for example a preconfigured table and stored in its non-volatile memory, in which is associated with each role that can be assigned to a device participating in the CONF service a TOK token to be presented by the device for access this role if it differs from the role that was originally assigned to it in the OBJ (3) object it passed to platform 5. The TOK tokens associated with each of the roles may have been included by the platform 4 in the initial object OBJ (3) for example, and transmitted to the platform 5 via the device 3 as previously described.

In the variant described above in which a new encrypted object N_OBJ (3) is transmitted as token TOK in the message M, the fact for the platform 5 to be able to decrypt this object using the public key PubK4 associated with the The private key of the platform 4 makes it possible to control the TOK token and to determine that the device 3 is entitled to access this new role. The platform 5 then updates via its construction module 5A, in the database of identities and rights DB, the rights associated with the identity ID (3) with the rights RGT (3) indicated in the new object N_OBJ (3) (step G30).

Then the platform 5 transmits via its transmission module 5B to the devices 3 of the system 1 the database DB identities and rights thus updated, as described above with reference to the steps G40 and G50.

The devices 3 process and use the DB database thus updated in a manner similar to that described above with reference to steps E50 and E60 and FIG. 8.

In the example considered here, a conference service (audio, video or audio / video) has been considered. However, as mentioned above, this example is given for illustrative purposes only and the invention applies to other types of service whose rendering can be distributed over a plurality of devices. Thus, in particular, the invention also applies to a system comprising a plurality of connected objects.

To better illustrate this other example, consider for example a system comprising four objects connected to each other via a telecommunications network, such as a camera 01, a door 02, an object 03 carrying a facial recognition application and a boiler 04. These objects provide a service such as when the facial recognition application recognizes on an image captured by the camera a member of the family in front of the door, it asks the door to open and increases the temperature of the boiler. According to such an example, one can define the following rights on the service:

- right RI to obtain a state of the device;

- R2 right to restart the device;

Right R3 to obtain a media stream of the device;

Right R4 to open the door;

Right R5 to change the temperature; and constructing the DB 'identity and service database shown in FIG. 9, where ID (Ol), ID (02), ID (03), ID (04) designate the identities established for this service for the objects 01, 02, 03 and 04 respectively.

Claims

A service rights distribution method (CONF), to be implemented by a service platform (5) and comprising:

A step of construction (G30) of a database of identities and rights (DB) comprising, for each device (3) participating in the service, an identity (ID (3)) intended to be used by this device during its participation in the service and, associated with this identity, at least one information (RGT (3)) representative of rights on the service allocated to the device; and

A step of transmitting (G50) this database of identities and rights to each device participating in the service.

2. The method of claim 1 wherein, for at least one device participating in the service, the identity and said at least one representative information service rights allocated to this device are obtained by the service platform, said device during its registration (E40) with the service platform.

3. Method according to claim 1 or 2 wherein, for at least one device participating in the service, said at least one representative information service rights allocated to this device comprises a role (PART, SUP) associated with the device during its participation in the service.

4. Method according to any one of claims 1 to 3 wherein, for at least one device participating in the service, the identity and said at least one representative information rights to the service allocated to this device are obtained from a platform (4) assignment of rights on the service.

5. Method according to any one of claims 1 to 4 wherein the database of identities and rights is encrypted and / or signed (G40) by the service platform before being transmitted to each device.

The method of any one of claims 1 to 5 comprising:

A step of receiving (G60) a device participating in the service of an indication of a change in the rights allocated to this device on the service;

A step of updating (G30) the database of identities and rights for the identity used by the device according to said indication; and

A step of transmitting (G50) the identity and rights database updated to each device participating in the service.

7. The method of claim 6 wherein said indication comprises an authentication token (TOK) corresponding to at least one new right assigned to the device.

8. A method of processing a request by a first device intended to be implemented during a participation of the first device in a service, this method comprising:

A step of obtaining (E50) an identity and rights database transmitted by a service platform following the execution by said platform of a service rights distribution method according to any one of the claims 1 to 6, said identity and rights database comprising, for each device (3) participating in the service, an identity (ID (3)) intended to be used by this device during its participation in the service and, associated with this identity, at least one information (GTA (3)) representative of service rights allocated to the device;

A step of receiving (H10) a request from a second device participating in the service, this request comprising an identity used by the second device during its participation in the service and an action intended to be executed by the first device; ;

A verification step (H20), in the identity and rights database, if the identity included in the request has the right to request the execution of said action by the first device; and

Where appropriate (H30), an execution step (H40) of the required action.

9. Processing method according to claim 8 wherein the database of identities and rights transmitted by the service platform is encrypted and / or signed, the processing method comprising a step of decryption and / or validation of the signature ( E60) of the identity and rights database before implementing the verification step.

A computer program comprising instructions for executing the steps of the method for distributing rights on a service according to any of claims 1 to 7 and / or the processing method according to claim 8 or 9 when said program is executed by a computer.

A computer-readable recording medium on which a computer program is recorded including instructions for performing the steps of the method of distributing rights on a service according to any one of claims 1 to 7 and / or of the treatment method according to claim 8 or 9.

12. Service platform (5) capable of broadcasting rights on a service, this service platform comprising:

A construction module (5A) configured to construct a database of identities and rights comprising, for each device participating in the service, an identity intended to be used by this device during its participation in the service and, associated with this identity, at least one information representative of rights on the service allocated to the device; and

A transmission module (5B), configured to transmit this database of identities and rights to at least one other device participating in the service.

13. Device (3), said first device, adapted to participate in a service, this first device comprising:

A obtaining module (3A), able to obtain a database of identities and rights transmitted by a service platform according to claim 10 able to broadcast rights on the service, said identity and rights database comprising, for each device (3) participating in the service, an identity (ID (3)) intended to be used by this device during its participation in the service and, associated with this identity, at least one piece of information (RGT (3)) representative of service rights allocated to the device;

A reception module (3B) able to receive a request from a second device able to participate in the service, this request comprising an identity used by the second device during its participation in the service and an action intended to be executed by the first device;

A verification module (3D), activated by the reception module following the reception of the request coming from the second device, and configured to check in the identity and rights database whether the identity included in the request has the right to request the execution of said action by the first device; and

An execution module (3D) configured to perform the action required in the request, activated if the verification module determines that the identity included in the request has the right to require the execution of this action by the first device .

14. System (1) providing a service and comprising:

A service platform according to claim 12, able to broadcast rights on the service; and

A plurality of devices according to claim 13 capable of participating in said service.

The system of claim 14 further comprising a service rights allocation platform (4), said rights allocation platform comprising:

An authentication module (4A), configured to authenticate a device intended to participate in the service;

An assignment module (4B) for this device with an identity intended to be used by the device during its participation in the service and rights on the service; and - A transmission module (4C), the device and / or the service platform, the identity and at least one representative information rights assigned to the device by the assignment module.