Method, device and system for admitting a remote-controlled device to a communication network

Abstract

The invention relates to a method for admitting a remote-controlled device (DR) to a communication network (RES), the method being implemented in a server (EIR) for managing identifiers of remote-controlled devices associated with the communication network and suitable for comprising information relating to the control of the device, and comprising the steps of: obtaining, from a server (UTM / USS) for controlling remote-controlled devices, an authorisation message comprising an identifier of the device and an item of data indicating an authorisation of the device associated with a service of the device; removing the obtained identifier of the remote-controlled device from a list of identifiers of devices not authorised to connect to the communication network; and authorising the admission to the communication network of the remote-controlled device of which the identifier has been removed from the list, after obtaining an admission request sent by the device and comprising the identifier of the device.

Description

Description Title: Method, device and system for admitting a remote-controlled device to a communication network Technical field

[0001] The present disclosure belongs to the field of communications networks. More particularly, the invention relates to the communication of a remote-controlled device, such as a drone, via a communications network. The invention aims more specifically to enable the control of admission of such a device to a communications network. Prior art

[0002] In communication networks, and more particularly in mobile communication networks, the attachment of a terminal to a communication network is necessary, prior to any establishment by the terminal of a data session allowing the exchange of application or control data with a corresponding entity.

[0003] According to prior art techniques, the identifier of a mobile terminal must be checked when attaching or registering the mobile terminal to a communication network, prior to any data session implemented by the terminal with a corresponding entity (fixed or mobile terminal, data server, communication equipment, etc.) in accordance with what is described in particular in the 3GPP TS 23.502 specification (version 15.0.0, December 2017).

[0004] This control aims to ensure that a terminal identified as stolen or lost cannot access a communications network. According to the known technique, the terminal has a permanent identifier, for example called IMEI (International Mobile Equipment Identity), IMEI-SV (International Mobile Equipment Identity software vendor) or PEI (Permanent Equipment Identifier) ​​depending on the type of communications network considered. A database, for example of the El R (Equipment Identity Register) type, shared between a plurality of operators also includes information concerning permanent identifiers. Thus, the database includes for example three lists of permanent identifiers according to their authorization or not to be able to attach to a communications network administered by the operators sharing the database. - A first list, called Whitelisted, includes identifiers authorized to attach to a communication network - A second list, called Blacklisted, includes identifiers not authorized to attach to a communications network, - A third list, called Greylisted, includes identifiers authorized to attach temporarily.

[0005] Thus, when a terminal sends a request for attachment or registration to a communication network, a piece of equipment in the communication network, for example of the SGSN (Serving GPRS Support Node), MME (Mobility Management Entity) or AMF (Access and Mobility Management Function) type, transmits to the El R database the fixed identifier of the mobile terminal received and the database responds to the network equipment by indicating whether or not the mobile terminal is authorized to attach to the network, for example by using the three aforementioned lists.

[0006] This verification mechanism, while relevant for any mobile terminal wishing to attach or register to a communication network, including a drone, nevertheless proves insufficient for the drone. Indeed, the drone must not only appear as stolen or lost in a database but it is also required that a drone is actually controlled by a pilot, for example a UAVC (Unmanned Aerial Vehicle Controller) during its movement and authorized for example by a USS (Unmanned Aircraft System Traffic Management Service Supplier) drone service. The control technique as described above therefore proves insufficient for a mobile terminal such as a drone. Summary of the invention

[0007] The present disclosure aims to remedy all or part of the limitations of the prior art solutions, in particular those set out above, by proposing a solution which makes it possible to control that a drone can actually attach or register to a communication network in accordance with admission control information.

[0008] To this end, a method is proposed for admitting a remote-controlled device to a communication network, the method being implemented in a server for managing identifiers of remote-controlled devices associated with said communication network and adapted to include information relating to the control of said device, and comprising - obtaining from a remote-controlled device control server an authorization message comprising an identifier of said device and data indicating an authorization of the device associated with a service of said device, - an authorization for the admission of the remote-controlled device to said communication network, following the obtaining of an admission request issued by said device and including the identifier of said device.

[0009] The admission process implemented in an identifier management server such as that an El R server or database, thus makes it possible to take into account authorization information, for example of movement or flight, associated with a service, issued by a control server, such as a USS or USS / UTM type server. According to the prior art, such a management server only includes identifiers (IMEI, IMEI-SV or PEI for example) corresponding to a mobile terminal to which access is to be authorized or, on the contrary, access prohibited. This authorization or prohibition, valid for any mobile terminal, is based only on the identifier itself independently of any service for example. The admission method has the advantage of being able to authorize the admission, that is to say the registration or access, of the remotely controlled device not only on the basis of the identifier of the device but also on the basis of data indicating an authorization of the device associated with a service of the device.Thus, the remote-controlled device could transmit a valid identifier which would be sufficient for a mobile terminal such as a smartphone but which must also be supplemented, with regard to the remote-controlled device, by an authorization for a service, for example by a flight authorization, in order to be able to be effectively admitted prior to any formalized data session establishment, for example by a bearer establishment, PDN (Packet Data Network) connection or any equivalent procedure. The method thus prevents any remote-controlled device from being able to be admitted to attach itself to a communication network without having an effective service authorization, for example a flight authorization, thus reinforcing the security of infrastructures and environments where remote-controlled devices move.It should be noted that, according to the prior art, when a data session is established, an authorization to establish the session is received by the remote-controlled device but this authorization more specifically targets an authorization of a user of the device and this authorization occurs after the emission of an admission request as indicated in the admission method. This procedure implemented during the establishment of a data session does not reduce the risks induced by an unwanted attachment, for example in the absence of a flight authorization, of a remote-controlled device to a communication network. In addition, the authorization assigned during the establishment of a data session may relate to an access point, also called APN (Access Point Name), which does not reduce the risks linked to another access point which would not require the same authorization.The process thus makes it possible to strengthen security independently of the user and independently of the access point and prior to any establishment of a data session.

[0010] According to one aspect of the invention, the admission method further comprises removing the identifier of the obtained remote-controlled device from a list of identifiers of non-controlled devices. authorized to attach to said communication network and the authorization for the admission of the remote-controlled device is valid for the remote-controlled device whose identifier has been removed from the list.

[0011] According to one aspect of the invention, in the method of admitting a remote-controlled device to a communication network, the list of identifiers of devices not authorized to attach to said communication network is obtained from a register of remote-controlled devices, prior to the withdrawal step.

[0012] Advantageously, the remote-controlled device identifier management server obtains a list of identifiers of devices that do not have authorization to attach to a communication network for which the management server ensures the management of valid or invalid identifiers for access to the network. The remote-controlled device registry can, according to one example, obtain from the manufacturers of remote-controlled devices identifiers of the various remote-controlled devices constructed and the management server or the device registry constructs a list, for example of the "Blacklisted" type, to prohibit by default an attachment of any remote-controlled device unless it has authorization for a USS or USS / UTM type service, in accordance with the data relating to the authorization indicated in the admission process.

[0013] According to another aspect of the invention, in the method of admitting a remote-controlled device to a communication network, the data indicating an authorization of the device associated with a service of said device comprises a movement plan of the remote-controlled device.

[0014] The method can be applied to a particular context where the movement of the remote-controlled device is linked to a movement plan of the device such as a flight plan. The data from the control server essentially indicates that a movement authorization has been issued to the device and that it can therefore be authorized to attach to the communication network.

[0015] According to another aspect of the invention, in the method of admitting a remote-controlled device to a communication network, the withdrawal of the identifier of the remote-controlled device obtained is accompanied by an addition of the withdrawn identifier to a list of identifiers of devices authorized to attach to said communication network.

[0016] In this embodiment, the identifier management server manages at least two lists, namely a first (“blacklisted”) in which the identifiers of unauthorized devices and a second (“whitelisted”) comprising the identifiers of devices authorized to attach to the communication network in accordance with the data indicating an authorization of the device associated with a service of said device. Thus, these two lists make it possible to accelerate the response to a request for admission of a device, typically by comparing the received identifier with the identifiers of one of the two lists, for example according to the size of the respective lists.

[0017] According to another aspect, in the method of admitting a remote-controlled device to a communication network, the data indicating an authorization of the device associated with a service comprises information on the duration of said authorization and in which the withdrawal is effective for said duration.

[0018] The authorization data may only be valid for a specific period. For example, if it is a movement or flight authorization, the movement authorization may advantageously include a period during which the device may actually be authorized to attach to the communication network. If the device issues an admission request within the actually valid interval or duration, it may be authorized to attach or register, whereas this will not be the case outside this interval or duration.

[0019] According to another aspect, in the method of admitting a remote-controlled device to a communication network, the data indicating an authorization of the device associated with a service of said device further comprises an identifier of an access point to the service and the admission request comprises said access point to the service.

[0020] The control server can transmit an access point to the service for which the device's authorization is valid. The list of identifiers can thus include information on the access point to the service, for example an APN (Access Point Name) identifier, which will be taken into account for the admission of the device. When the device transmits the admission request, the information on the access point, included in the admission request, will be taken into account to authorize or not the admission of the device to the communication network, and more particularly for the access point transmitted by the control server, for example prohibiting attachment to an access point different from that indicated by the control server.

[0021] According to another aspect, in the method of admitting a remote-controlled device to a communication network, the data indicating an authorization of the device associated with a service of said device further comprises an identifier of the communication network and the admission request comprises the identifier of the communication network.

[0022] The control server may transmit an identifier of the communication network to the service for which the device authorization is valid. The device identifier may thus include information on the communication networks, for example an MNC (Mobile Network Code) and / or MCC (Mobile country code) identifier, which will be taken into account for the admission of the device. When the device transmits the admission request, the information on the communication network to which the device wishes to attach is included in the admission request, and this information, if it corresponds to one of the communication network identifiers associated with the device identifier removed from the list of unauthorized devices, will allow the device to be admitted to the communication network. This information thus makes it possible to authorize or not the admission of a device to a specific communication network depending on the authorization transmitted by the control server for the communication network and for the service, for example for the theft of the device. This information thus makes it possible, for example, to restrict the access of the device to a country or to an operator of a country according to the code used.

[0023] According to another aspect, in the method of admitting a remote-controlled device to a communication network, the identifier of the remote-controlled device is an identifier of a network access module of the device.

[0024] According to this embodiment, the device identifier can advantageously be an access module identifier of the device. In the case where a remote-controlled device comprises several modules, the identifier of one of the modules can be removed from the list while another can be kept in the list for example. This makes it possible to authorize admission for a given technology, if the modules are of different technologies, and / or to limit the number of authorizations for a device, and / or to authorize admission for one service and not for another depending on the data indicating an authorization of the device associated with a service of said device.For example, it may be useful to allow admission for a device control service using a device module, so that a IIAVC type controller can control the device via a communication network while a value-added service, e.g., video via another device module, will not be allowed via the information on the identifier of a specific device module.

[0025] The various aspects of the admission process just described can be implemented independently of each other or in combination with each other.

[0026] The invention also relates to a device for admitting a remote-controlled device to a communication network, implemented in a server for managing identifiers of remote-controlled devices associated with said communication network and adapted to include information relating to the control of said device, said admission device comprising at least one processor configured to - obtain from a remote-controlled device control server an authorization message comprising an identifier of said device and data indicating an authorization of the device associated with a service of said device, - authorize the admission of the remote-controlled device to said communication network, following obtaining an admission request issued by said device and including the identifier of said device.

[0027] According to one aspect of the invention, the at least one processor of the admission device is further configured to: remove the identifier of the remote-controlled device obtained from a list of identifiers of devices not authorized to attach to said communication network and authorize the admission of the remote-controlled device to said communication network for the remote-controlled device whose identifier has been removed from the list.

[0028] This admission device is capable of implementing in all its embodiments the admission method which has just been described above.

[0029] The invention also relates to a system for admitting a remote-controlled device to a communication network comprising - a device for admitting this disclosure, - the device configured to transmit to the admission device an admission request comprising an identifier of said device.

[0030] The invention also relates to a computer program product comprising a set of program code instructions which, when executed by at least one processor, configure said at least one processor to implement the admission method according to any of the embodiments of the present disclosure.

[0031] The invention also relates to a computer-readable recording medium having recorded thereon a set of program code instructions which, when executed by at least one processor, configure said at least one processor to implement an admission method according to any of the embodiments of the present disclosure. Brief description of the drawings

[0032] The invention will be better understood by reading the following description, given as a non-limiting example, and made with reference to the figures which represent: [Fig. 1] Figure 1: a schematic representation of a method of admitting a remote-controlled device according to a first embodiment, [Fig. 2] Figure 2: a diagram illustrating the main steps of a method for admitting a remote-controlled device according to another embodiment, [Fig. 3] Figure 3: a representation of a device for admitting a remote-controlled device according to an example,

[0033] In these figures, identical references from one figure to another designate identical or similar items. For clarity, items shown are not to scale unless otherwise stated. Description of the embodiments

[0034] More generally, it should be noted that the methods of implementation and embodiment considered above have been described as non-limiting examples, and that other variants are consequently conceivable.

[0035] In the remainder of the description, a remote-controlled device is presented, i.e. a device whose movement is controlled remotely by a control entity. According to one example, the remote-controlled device is a drone, also called a UAV (Unmanned Aerial Vehicle), controlled by a control entity, also called a UAVC. In the remainder of the description, the term drone is used but can be replaced by any type of remote-controlled device.

[0036] We first refer to [Fig 1] which describes a schematic representation of a method of admitting a remote-controlled device according to a first embodiment.

[0037] A DR drone and a TERM mobile terminal, for example of the smartphone type, are represented so as to be able to more easily distinguish the particularities of the admission procedure, implemented during the attachment or registration of the DR drone, in comparison with the same procedure for the TERM mobile terminal.

[0038] The DR drone and the TERM mobile terminal attach or register with a RES communication network, for example a mobile network. The RES communication network is for example a network using technologies as specified in 3GPP. The DR drone and the mobile terminal attach or register with the RES communication network via an access device, such as an ANT antenna carrying control data and application data for value-added services (audio, video, data, etc.). An SRV server of the RES communication network allows the DR drone and the TERM mobile terminal to exchange with an EIR server or database. The SRV server, according to one example, may be an SGSN, an MME or an AMF.Figure 1 is a simplified view of the architecture and a plurality of devices providing various functions can be located between the DR drone / TERM terminal and the SRV server as well as between the SRV server and the EIR database.

[0039] According to the F1 exchanges in [Fig 1], when the mobile terminal TERM attaches or registers to the RES network, the SRV server transmits an identifier of the TERM terminal, which it transmitted to the SERV during its access / registration. This identifier can be an identifier of type IM El, IMEI-SV or even of type PEI. Any fixed identifier of the TERM terminal can be used. The EIR database includes the identifiers of terminals for which access or registration must not be allowed. The TERM terminal can access the RES communication network if its identifier does not appear in a list, for example of the "Blacklisted" type, maintained by the El R database. Its identifier may, for example, be in the "Blacklisted" list if the mobile terminal has been declared lost or stolen. This condition alone is sufficient to allow access / registration to the TERM mobile terminal. This TERM mobile terminal, once access is authorized, can establish a data session by opening a session with a gateway, for example of the UPF (User Plane Function) or PDN-GW (Packet Data Network Gateway) or GGSN (Gateway GPRS Support Node) type or any other equivalent gateway of the RES communication network depending on its service subscription profile to the RES network.

[0040] For the DR drone, the admission process is more complex because it is not enough that a DR drone identifier is not prohibited from access or registration as for the terminal, it is also necessary that the DR drone benefits from an admission authorization associated with a DR drone service.

[0041] During a step E0, an entity or an OEM (Organization Equipment Manufacturer) database, also identified as a register of remote-controlled devices, managing drone identifiers transmits to the entity El R drone identifiers which are considered by default as drones which should not be authorized access to a communications network RES. The entity El R, according to one example, is a database associated with a plurality of communications networks possibly managed by separate operators. Thus, each of the communications networks refers to this database when a terminal, for example the drone DR, wants to attach itself to a communications network RES. The OEM database is for example a multi-manufacturer database which is updated with drone identifiers when these are built. Thus, this possibly distributed OEM database includes the drone identifiers as soon as they are built.

[0042] The update of the El R entity by the OEM database can be carried out via an entity named UAVIR (in English UAV Identity Registry) in charge of managing drone identifiers for an operator. Thus, the OEM entity, in charge of managing drone identifiers, informs the UAVIR of an operator about the drone identifiers to which it is not appropriate to authorize access. In the remainder of the description, the access authorization is also valid for a registration authorization.

[0043] The entity El R, or identifier management server, whose role is to authorize or not the access of the DR drone to the RES communication network, therefore receives during step E0 a set of drone identifiers, including the identifier of the DR drone, for which access to the RES communication network must not be authorized. This may be stolen or lost drone identifiers such as for the TERM terminal and / or constructed drone identifiers for which access authorization is refused by default. The El R identifier management server can thus establish a "Blacklisted" list including these identifiers for which access is prohibited. Drone identifiers can indifferently be IMEI or IMEI-SV or PEI type identifiers or any identifier allowing unambiguous identification of a drone. It should be noted that a drone can be equipped with several communication interfaces or modems and the identifier can then be associated with an interface / modem of the drone and not with the drone itself. A drone can therefore have several identifiers and admission management by identifier is therefore possible.

[0044] During a step E1, a service entity SERV ensuring the provision of a service developed from the drone DR requests from a USS (UAS Service Supplier) type entity, also called a remote-controlled device control server, an authorization to move the drone DR associated with the service managed by the entity SERV. This authorization may concern any type of service implemented from the drone (surveillance, video recording, control, provision of access, delivery, etc.) and may also include, according to one example, a duration of implementation of the service and possibly geographic data in which the service is implemented. The service requested by the server SERV may generically correspond to a movement or flight plan of the drone DR. The request may also include information on an access point to the service, such as an APN (Access Point Name) identifier, used for the provision of the requested service.This request includes a DR drone identifier, or a DR drone Modem or access module identifier, requesting access to the RES communication network for the provision of the requested service.

[0045] The USS control server, upon receipt of this request transmitted by the SERV entity, can interact for example with a regulation entity (not shown) of a space in which the DR drone must move for the provision of the service indicated by the SERV entity and decides whether or not to authorize the movement of the DR drone, in accordance with the various information indicated in the request issued during step E1. The USS entity, advantageously deployed with a UTM (UAV Traffic Management) type entity, can modify the data relating to the service requested by the SERV entity to make them compatible with the safety or control requirements of the regulation entity.

[0046] In a step E2, possibly once the control server has obtained authorization to move the DR drone for the provision of the required service, informs the UAVIR about the movement of the DR drone for the provision of the required service by the SERV entity and further transmits the data relating to the required service, possibly modified by a regulatory entity. This transmission of information during step E2 is advantageously transmitted via a NEF (Network Exposure Function) entity responsible for providing an interface between a RES communication network and third-party applications such as the USS control entity. This NEF entity can thus translate the service information required by the USS control entity and the UAVIR entity responsible for managing drone identifiers and the authorizations associated with them.

[0047] The UAVIR is thus updated with an identifier of the DR drone, or of a modem of the DR drone, authorized to attach itself possibly with additional information such as a start and end time of authorization, geographical information of movement linked to the service, information on the RES communication network for which the access authorization is valid.

[0048] The reception of this update from the UAVIR during step E2 triggers, during a step E3, the sending by the UAVIR to the identifier management server El R, of a message comprising the identifier of the drone DR as well as data indicating an authorization of the drone DR associated with the service required by the entity SERV. This message is transmitted via the entities NEF and UAVIR in this embodiment but the message can, according to another example, be transmitted directly by the control server USS to the identifier management server El R. Whatever the case, the identifier management server El R receives the authorization from the control server USS, directly or indirectly.This authorization includes data as indicated above which may correspond to a duration for which the authorization is valid, to a movement plan of the drone, to an identifier, for example of the MNC (Mobile Network Code) and / or MCC (Mobile Country Code) type, to a specific access point that the DR must use, for example of the APN type of the RES communication network to which the drone is admitted. The identifier management server, upon receipt of this authorization message, removes during a step E4 the identifier of the authorized DR drone from a list of identifiers prohibited from access. For example, if the management server E1 R manages a “blacklisted” list, it removes the identifier of the DR drone from this list. This removal may be valid for a limited duration, if for example the authorization is only valid for a corresponding limited duration.The El R identifier management server can, alternatively, manage a "whitelisted" list comprising the identifiers of drones authorized to access a communication network, in this case the RES communication network. In this case, the El R identifier management server adds the identifier of the DR drone to this "Whitelisted" list. The El R identifier management server can further manage a "Greylisted" list of identifiers authorized to temporarily access the RES communication network, in which case it will add the identifier of the DR drone to this list if. the authorization received from the USS control server is only temporary.

[0049] During a step E5, the drone DR transmits an admission request, corresponding to an attachment or registration request, to the communication network RES via the antenna Ant and the access server SRV. The access server SRV transmits this access request, possibly modified by the server SRV, to request authorization for admission of the drone DR to the communication network RES. This access request includes an identifier of the drone DR as well as possibly an access point (for example of the APN type) to the communication network RES and possibly an identifier of the communication network RES (for example of the MCC and / or MNC type). Upon receipt of this admission request transmitted by the drone DR, the identifier management server E1 R compares the data received in the admission request with the information included in the attachment authorization list(s) of the drones (“blacklisted”, “whitelisted”, “greylisted”) and authorizes or denies admission.In this case, the DR drone having an access or admission authorization for the service required by the SERV entity, an admission authorization is granted to the DR drone and the El R server transmits to the DR drone possibly via the SRV access server and the Ant antenna an access authorization. The mechanisms specific to the DR drone's access to the RES communication network are thus implemented following this authorization. In the case where the admission authorization is valid for a limited period, the admission authorization will be granted if the admission request is received by the El R server during the period when an authorization is valid, for example in accordance with the data present in a "greylisted" list.In the case where the authorization is valid for a particular RES communication network and / or for a specific access point and / or for a modem of the DR drone in particular, the information present in the admission request concerning the access point, the RES network and / or the modem must correspond to the valid data for the authorization so that the DR drone is authorized to attach to the RES communication network. The admission method for authorizing the DR drone to attach to the RES communication network therefore requires additional information and steps compared to an authorization for attachment of a mobile terminal, distinct from a drone, described in step F1.

[0050] We then refer to [Fig 2] which illustrates the main steps of a method of admitting a remote-controlled device according to another embodiment. During a step E0, an OEM register of remote-controlled devices, including the drone DR, transmits PEI identifiers of remote-controlled devices to a server E1 R for managing identifiers of remote-controlled devices. The OEM register of remote-controlled devices may, for example, be maintained by one or more device manufacturers. remotely controlled. This registry transmits these identifiers, for example, as soon as they are constructed. The identifiers can be advantageously transmitted via a UAVIR database responsible for managing remotely controlled devices for one or more communication network operators. Thus, the UAVIR can also indicate to the El R server that devices whose identifier is among those transmitted by the OEM registry must not be authorized to access a communication network for which the El R server ensures admission authorizations. In the case where the identifiers are directly transmitted to the El R server, then the latter can position these identifiers as prohibited from admission, in the absence of other movement authorization information, for example, to one of the communication networks. To this end, the El R server can maintain a list of unauthorized identifiers, such as a so-called "Blacklisted" list.

[0051] During a step E1, a SERV manager of the DR device requests from a USS / UTM control server a movement authorization for the remote-controlled device DR. The manager thus transmits to the USS / UTM entity an identifier of a modem of the DR device which will need to attach to a communication network for a remote control service of the device. The device must always be attached to a network to be able to be controlled, in particular when the device is located remotely, for example BLOS (in English Beyond Line Of Sight). The DR device, at least for its modem associated with the control, must always be admitted to a communication network managed by the El R register to be able to be effectively controlled remotely, the service effectively consisting of a control of the drone.

[0052] This request transmitted by the SERV manager includes a PEI identifier of the access module also called modem, for example of type 3G, 4G, 5G, xG of the device used for controlling the DR device. According to one example, this request may include a movement plan of the device corresponding for example to GPS data or to any type of information allowing the UTM / USS entity to identify the movement plan of the device. The request may, according to an alternative, include a minimum duration (or a start and end time required for controlling) during which the device must be able to be admitted to a communication network, thus guaranteeing permanent connectivity of the DR device to a communication network. The request may, according to another example, include an identifier of an access point used by the DR device to access a communication network.For example, this may be an APN identifier if the communication network is a cellular network. According to yet another example, the request includes an identifier of a communication network, for example of the MNC type, to which the DR device wishes to request admission. This information is of interest in the case where several communication networks can be reached and / or the manager has. established an agreement with one or more communications network operators. This optional information may be transmitted alternatively or one or more of this information may be transmitted simultaneously in the request.

[0053] During a step E2, the USS / UTM control server transmits an authorization message comprising the identifier of the modem of the DR device as well as data indicating an authorization of the DR device associated with the device control service. This data may correspond to a coding of the type of service on several binary elements and to an indicator, or flag, indicating that the modem of the device whose identifier must be allowed to attach or register to a communication network. The information present in the request transmitted by the SERV manager, namely the movement plan, the duration, the access point, the communication network, may supplement the authorization message so as to limit the authorization of the device to certain geographical coordinates of the device, to a certain duration, to an access service and / or to a particular communication network.This authorization message can be transmitted directly or via the NEF entity and / or the UAVIR entity as in [Fig 2]. In the case where the UAVIR intervenes, this entity can for example collect authorization messages for one or more devices and transmit only in step E3 to the EIR identifier management server the relevant information (PEI identifier, period during which to authorize an admission for this identifier) ​​to authorize or not an admission of the DR device during an admission request required by a modem of the DR device. According to another example, steps E2 and E3 are combined and the UTM / USS control server transmits the authorization message directly to the EIR management server.

[0054] Upon receipt of the message during step E3, the EIR server removes during a step E4 the identifier of the access module from the “Blacklisted” list and possibly transfers it to a “whitelisted” list if the admission authorization is permanent or possibly to a “greylisted” list if the admission authorization for the access module of the device is for a limited duration in accordance with the information included in the authorization message.

[0055] In a step E5a, the DR device transmits an access request, for example in an “Attach Request” type message, to an SRV access device of a communication network. The reception of this access request triggers, in a step 5b, the sending by the SRV access device of an admission request to the EIR identifier management server, this admission request comprising the PEI identifier of the access module transmitting the access request and possibly location data of the DR device, an identifier of the communication network comprising the access device SRV, an identifier of an access point. The El R server identifies whether the modem's PEI identifier is absent from the "blacklisted" list or present in the "whitelisted" list. If the authorization is valid for a certain duration or between a start and end time, the El R server further determines whether the access request is transmitted in the slot or during this start and end interval, and possibly whether the information present in the admission request corresponds to the data for which an authorization is permitted according to the information received in the authorization message and with which one or more lists have been updated.

[0056] If the device is allowed to attach or register to the communication network, an admission acceptance message is transmitted by the server E1 R to the access server SRV during a step E6a and the access server SRV retransmits this acceptance message to the device DR during a step E6b.

[0057] Upon receipt of this message, during a step E7 the device can establish a data session by transmitting a session establishment request message to the access SRV device so that it can actually be remotely controlled in accordance with the service required by the entity. This request message is transmitted by the SRV device to a PASS device such as a PDN-GW or UPF type gateway.The DR device having been authorized to attach to the communication network, the network operator may not perform a new admission control during session establishment during step E7 or it may perform such a control in addition to the admission control during attachment or registration of the DR device, for example if the admission control during establishment relates to information which did not give rise to an admission control during attachment or registration of the DR drone implemented during step E5a.

[0058] If the admission authorization is temporary, the El R server adds the access module's PEI identifier to the "Blacklisted" list (and possibly removes it from the "Greylisted" list) at the end of the authorized admission period. If the access module whose identifier has been removed attempts to register again, after the end of the data session specific to the control of the DR device, then admission will be refused until a new authorization is received from a USS / UTM control server.

[0059] In this example a pilot service was considered but such a process is valid for any type of service (video, voice, data).

[0060] Please note that the SERV entity can subscribe to the USS / UTM entity. In this case, the subscription-specific information (USS / UTM identifier for the DR device, authorization slots, other types of location data, access point, communication network) will be transmitted to the EIR entity possibly through the UAVIR, which will be able to manage them locally and will avoid receiving changes in authorizations granted to the DR device as soon as a change occurs in the successive phases specific to the subscription, thus avoiding an exchange of too many messages and possible errors during these exchanges.

[0061] Information on operator networks, for example of the MCC (Mobile country code) and / or MNC (Mobile Network Code) type, possibly used to authorize or not a device to attach to a communication network can be advantageously used to authorize or prohibit an attachment of the DR device in a given geographical area, for example to limit the movement of the device to a well-defined territory thanks to the MCC.

[0062] We now refer to [Fig. 3] which presents a representation of a device 100 for admitting a remote-controlled device to a communication network, implemented in an identifier management server, for example of the El R type, of remote-controlled devices associated with said communication network and adapted to include information relating to the control of said device.

[0063] For example, the admission device 100 comprises a processing unit 130, equipped for example with a microprocessor pP, and controlled by a computer program 110, stored in a memory 220 and implementing the admission method according to the invention. Upon initialization, the code instructions of the computer program 210 are for example loaded into a RAM memory, before being executed by the processor of the processing unit 130. Such an admission device 100 further comprises - a obtaining module 101, configured to obtain from a remote-controlled device control server an authorization Mess message comprising an identifier of said device and data indicating an authorization of the device associated with a service of said device, - an authorization module 103, configured to authorize the admission of the remote-controlled device to said communication network, following the obtaining of an admission request Req issued by said device and comprising the identifier of said device.

[0064] According to one embodiment, the admission device 100 further comprises a removal module 102, configured to remove the identifier of the remote-controlled device obtained from a list of identifiers of devices not authorized to attach to said communication network.

[0065] The modules 101, 102, 103 may be physical modules and / or software modules.

Claims

Claims

1. Method for admitting a remote-controlled device (DR) to a communication network (RES), the method being implemented in a server (El R) for managing identifiers of remote-controlled devices associated with said communication network and adapted to include information relating to the control of said device, and comprising - obtaining (E3) from a control server (USS / UTM) of remote-controlled devices an authorization message comprising an identifier of said device and data indicating an authorization of the device associated with a service of said device, - an authorization (E6) for the admission of the remote-controlled device to said communication network following the obtaining (E5) of an admission request issued by said device and comprising the identifier of said device.

2. A method of admitting a remote-controlled device to a communication network, according to claim 1, further comprising removing the identifier of the remote-controlled device obtained from a list of identifiers of devices not authorized to attach to said communication network and the authorization of the admission of the remote-controlled device is valid for the remote-controlled device whose identifier has been removed from the list.

3. Method for admitting a remote-controlled device to a communication network, according to claim 2, in which the list of identifiers of devices not authorized to attach to said communication network is obtained from a register (OEM) of remote-controlled devices, prior to the withdrawal step.

4. Method for admitting a remote-controlled device to a communication network, according to one of the preceding claims, in which the data indicating an authorization of the device associated with a service of said device comprises a movement plan of the remote-controlled device.

5. Method for admitting a remote-controlled device to a communication network, according to one of claims 2 to 4, in which the withdrawal of the identifier of the remote-controlled device obtained is accompanied by an addition of the withdrawn identifier to a list of identifiers of devices authorized to attach to said communication network.

6. Method for admitting a remote-controlled device to a communication network, according to one of the preceding claims, in which the data indicating an authorization of the device associated with a service comprises information of duration of said authorization and in which the withdrawal is effective for said duration.

7. Method for admitting a remote-controlled device to a communication network, according to one of the preceding claims, in which the data indicating an authorization of the device associated with a service of said device further comprises an identifier of an access point to the service and the admission request further comprises said access point to the service.

8. Method for admitting a remote-controlled device to a communication network, according to one of the preceding claims, in which the data indicating an authorization of the device associated with a service of said device further comprises an identifier of the communication network and the admission request comprises the identifier of the communication network.

9. Method for admitting a remote-controlled device to a communication network, according to one of the preceding claims, in which the identifier of the remote-controlled device is an identifier of a network access module of said device.

10. Device (100) for admitting a remote-controlled device to a communication network, implemented in a server for managing identifiers of remote-controlled devices associated with said communication network and adapted to include information relating to the control of said device, said admission device comprising at least one processor configured to - obtain from a remote-controlled device control server an authorization Mess message comprising an identifier of said device and data indicating an authorization of the device associated with a service of said device, - authorize the admission of the remote-controlled device to said communication network, following the receipt of an admission request Req issued by said device and including the identifier of said device.

11. Device for admitting a remote-controlled device to a communication network, according to claim 10, comprising at least one processor further configured to remove the identifier of the remote-controlled device obtained from a list of identifiers of devices not authorized to attach to said communication network and authorize the admission of the remote-controlled device to said communication network for the remote-controlled device whose identifier has been removed from the list.

12. System for admitting a remote-controlled device to a communication network comprising - an intake device according to claim 10 or claim 11, - the device configured to transmit to the admission device the admission request comprising the identifier of said device.

13. Program product comprising program code instructions for implementing an admission method according to claims 1 to 9, when executed by a processor.

14. A recording medium readable by an input device on which the program according to claim 13 is recorded.

Images