Abstract:
An embodiment of an emergency call system comprises a device for triggering an emergency call and a communications device having a secure element. In various implementations, the secure element includes at least two profiles, one of which is an emergency profile; means suitable for receiving, over a local communications channel, an event issued by the device for triggering an emergency call; means for activating an emergency profile, enabling emergency calls to be made in a communications network, if said profile is not already active; and means for calling an emergency number in said network in order to make said emergency call.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    The invention lies in the field of emergency call methods and systems, specifically methods and systems that enable an emergency number to be called, typically in order to call an emergency center, emergency doctors, the fire service, . . . . 
         [0002]    The document “Pan-European eCall Implementation Guidelines”, Draft v3.0 by the European eCall Implementation Platform (EeIP) and published on Feb. 3, 2012 sets the objective, in the context of the eCall service of the European Union, of devising a system enabling a vehicle that has suffered an accident to contact an emergency number and automatically communicate to emergency teams data suitable for giving such teams fast and effective access to the site of the accident. 
         [0003]    The invention proposes a solution for implementing those directives. 
       OBJECT AND SUMMARY OF THE INVENTION 
       [0004]    More precisely, in a first aspect, the invention provides an emergency call system comprising: 
         [0005]    a device for triggering an emergency call; and 
         [0006]    a communications device having a secure element, the secure element comprising:
       at least two operational profiles, one of which is an emergency profile;   means suitable for receiving, over a local communications channel, an event issued by the device for triggering an emergency call;   means for activating an emergency profile, enabling emergency calls to be made in a communications network, if the profile is not already active; and   means for calling an emergency number in the network in order to make the emergency call.       
 
         [0011]    In corresponding manner, the invention also provides an emergency call method performed by a secure element having at least two operational profiles, one of which is an emergency profile, the secure element being included in a communications device locally connected to a device for triggering an emergency call, the method comprising: 
         [0012]    a step of receiving, from the device, an event for triggering an emergency call via a local communications channel; 
         [0013]    a step of activating an emergency profile enabling emergency calls to be made in a communications network, if the profile is not already active; and 
         [0014]    a step of calling an emergency number in the network in order to make the emergency call. 
         [0015]    Thus, and in general manner, the invention proposes a solution for switching automatically to an emergency operational profile referred to below as “eCall Profile” when a specific event is detected. 
         [0016]    It should be recalled that an operational profile is a set of data and applications that enable a secure element in which the profile is installed and activated to authenticate itself with a telecommunications network. 
         [0017]    Depending on the country, the emergency profile may: 
         [0018]    either need to authenticate itself with a network (in application of the 3GPP 31.102 standard). This applies in particular in Russia, which has a virtual operator with priority over the others and dedicated to emergency calls; 
         [0019]    or else have no need to authenticate itself on a particular network. This applies in particular to France where there is no need to be authenticated in order to call emergency numbers such as 112 for medical emergencies or 18 for the fire brigade. 
         [0020]    However, in the present state of the art, switching over to an operational profile can take place only on receiving a command issued by an external entity of the subscription manager-secure routing (SM-SR) type. This constraint is not compatible with the requirements of an emergency service. 
         [0021]    In a preferred embodiment, the emergency call management system of the invention is for incorporating in a vehicle. 
         [0022]    In another embodiment, the communications device is a portable device, e.g. a telephone, coupled to sensors suitable for detecting a health state of the user of the device in order to trigger an emergency call. 
         [0023]    Thus, and in very advantageous manner, the invention provides the possibility of activating an emergency profile automatically in order to make an emergency call when a predetermined event occurs. 
         [0024]    The invention thus makes it possible to make an emergency call very quickly even if the operational profile that is active at the time the accident occurred is not the emergency profile. 
         [0025]    The invention also serves to switch to the emergency profile even if the vehicle is outside the coverage of the network associated with the active operational profile, where this was not possible in the prior art since such a switchover could only be undertaken on receiving a command from the SM-SR. 
         [0026]    In an embodiment, the device for triggering an emergency call comprises an airbag type mechanism and/or an on-board computer suitable for generating the above-mentioned event. 
         [0027]    The invention also makes it possible for the changeover and the emergency call to be performed completely automatically without human intervention. This characteristic is particularly important in the event of bodily injury. 
         [0028]    In a first particular embodiment, the secure element is a secure element contained in and soldered to the communications device, e.g. a micro-circuit of the eUICC type, e.g. as defined by the ETSI 102.221 standard. For further information about UICC and eUICC secure elements, the person skilled in the art should refer respectively to the ETSI 102.221 standard and to the ETSI TS 103.383 specifications. 
         [0029]    In a particular embodiment, each of the profiles in the eUICC type security element is associated with a particular security domain. 
         [0030]    In a particular embodiment, the emergency call is used for communicating data for locating the emergency call and preferably for calling the communications device back on a number associated with one of the profiles other than the emergency profile. 
         [0031]    By way of example, the data is stored in the emergency profile or in a non-volatile memory of the operating system of the vehicle. 
         [0032]    In a particular implementation, the emergency call method of the invention includes a step of identifying the emergency profile from data associated with the event. 
         [0033]    In a preferred implementation, the step of calling the emergency number is followed by a step of activating a profile different from the emergency profile, possibly after a predetermined duration. 
         [0034]    This characteristic is very important since it enables the emergency services to call back the vehicle that has suffered an accident. 
         [0035]    In a particular implementation, the profile is activated on receiving a command issued by an SM-SR entity. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0036]    Other characteristics and advantages of the invention appear more clearly and more completely on reading the following description, which is given by way of non-limiting example and with reference to the accompanying drawings, in which*. 
           [0037]      FIG. 1  is a flow chart showing the main steps of an emergency call method in accordance with the invention; and 
           [0038]      FIG. 2  is a block diagram of an emergency call system in accordance with a particular embodiment of the invention. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0039]      FIG. 1  is a flow chart showing the main steps of an emergency call method in accordance with the invention. 
         [0040]    In the presently-described implementation, the method is performed in the vehicle  100  shown in  FIG. 2 . 
         [0041]    The vehicle  100  includes a safety mechanism  110  of the airbag type and an on-board computer  120 , both themselves known. 
         [0042]    The vehicle  100  also has a communications device  130  including a secure element  150  in accordance with the invention and an interface  140  between the secure element  150  and the network. 
         [0043]    The interface  140  comprises, in conventional manner, a transceiver coupled to an antenna. 
         [0044]    In the presently-described embodiment, the secure element  150  is a secure element of the eUICC type. It comprises in particular: 
         [0045]    an operating system OS; 
         [0046]    a non-volatile memory  151 ; 
         [0047]    a profile management module  152 ; and 
         [0048]    a profile installation module  154 . 
         [0049]    In the presently-described embodiment, the non-volatile memory  151  has a privileged or “issuer” security domain ISD and secondary security domains SSD 1 , SSD 2 . 
         [0050]    The issuer security domain ISD is privileged in that it is suitable in particular, and in known manner, for creating or deleting secondary security domains SSD 1 , SSD 2  in the non-volatile memory  151 , in co-operation with the profile management module  152  and the profile installation module  154 . 
         [0051]    More precisely: 
         [0052]    the profile management module  152  communicates in secure manner with a subscription manager-secure routing (SM-SR) entity of the network in order to receive, install, and activate/deactivate a profile in the security domains SSD 1 , SSD 2 , the SM-SR entity communicating for this purpose with a policy control function (PCF) entity of the operator; and 
         [0053]    the profile installation module  154  communicates in secure manner with a subscription manager-data preparation (SM-DP) entity of the network in order to decrypt the blocks of a profile and install them in the security domains SSD 1 , SSD 2 , the SM-DP entity communicating for this purpose with a profile database DB of the operator. 
         [0054]    In the presently-described embodiment: 
         [0055]    the secondary security domain SSD 1  includes an operational profile P 1  enabling the communications device  130  to communicate in a first mobile network MN 1 ; and 
         [0056]    the secondary security domain SSD 2  includes an emergency profile P_eCall enabling the communications device  130  to communicate in a mobile network MN_eCall in order to make eCall emergency calls. 
         [0057]    In the presently-described embodiment, the emergency call is used in particular for communicating data DCV enabling the emergency call to be located and preferably enabling the communications device  130  to be called on a number associated with a profile different from the emergency profile P_eCall. 
         [0058]    To this end, in the presently-described embodiment, the emergency profile P_eCall has a data file DCV specific to the vehicle  100  and to the main driver of the vehicle and for transmission to emergency teams. 
         [0059]    In the presently-described embodiment, the data DCV comprises: 
         [0060]    physical characteristics of the driver (blood group, allergies); 
         [0061]    characteristics of the vehicle (marque, model, color, . . . ); 
         [0062]    the number of passengers in the vehicle; and 
         [0063]    the telephone number of the vehicle associated with the profile P 1  that was active before the event EV. 
         [0064]    In accordance with the invention, the communications device  130  is suitable during a step E 10  for receiving an event EVT via a local communications channel  155 . 
         [0065]    The local communications channel may be a wired bus or a wireless communications channel, e.g. of the Bluetooth type. 
         [0066]    In the presently-described embodiment, this event EVT is received by a software module PSM of the operating system OS of the secure element  150 , coming from the operating system  125  of the vehicle. 
         [0067]    In the presently-described embodiment, the event EVT is generated by the airbag type mechanism  110  and/or by the on-board computer  120 . By way of example, and more precisely, the operating system  125  sends an event EVT to the software module PSM on receiving a signal SIG generated either: 
         [0068]    on triggering of the airbag system  110 ; or else 
         [0069]    when a person (e.g. a driver or a passenger of the vehicle) actuates a control  121  of the on-board computer  120 . 
         [0070]    On receiving the event EVT, the module PSM acts during a step E 20  to identify the identifier of the emergency profile P_eCall. This identification may be performed with the help of data, e.g. an identifier or a flag associated with the event EVT. 
         [0071]    During a step E 22 , the module PSM verifies whether the emergency profile P_eCall is active. 
         [0072]    If it is not, the emergency profile P_eCall needs to be activated. To this end, the step E 22  is followed by: 
         [0073]    a step E 25  during which the module PSM stores the identifier P 1  of the active profile; 
         [0074]    a step E 30  during which the module PSM operates the profile management module  152  so as to cause it to activate the emergency profile P_eCall; and 
         [0075]    a step E 40  during which the operating system OS of the secure element  150  restarts the secure element  150 , by performing a “RESET” operation, thereby automatically causing all of the data of the active profile to be read, and specifically the data of the emergency profile P_eCall. 
         [0076]    Once the emergency profile P_eCall has been activated, the communications device  130  makes an emergency call to an emergency number NU stored in this profile during a step E 50 . The data DCV relating to the driver and to the vehicle and stored in the non-volatile memory  151  is preferably communicated to the emergency teams. 
         [0077]    This emergency call may be initiated by the emergency profile P_eCall, by the operating system OS, or by a person via the interface  121  of the on-board computer  120 . 
         [0078]    In the presently-described embodiment, the communications device  130  waits for a predetermined duration D (step E 60 ) before terminating the emergency call. Waiting for this duration D is not essential, and the emergency call may be terminated as soon as the data DCV has been transmitted to the emergency services. 
         [0079]    Therefore, in the presently-described embodiment, the system switches back (step E 70 ) to the profile that was active before the event EVT, i.e. to the profile P 1  having the identifier that was stored in step E 25 . For this purpose, the module PSM operates the profile management module  152  so that it activates the profile P 1 , and then, the operating system OS of the secure element  150  restarts the secure element  150 . 
         [0080]    The emergency center is then in a position to call the vehicle, the telephone number of the vehicle associated with the re-activated profile being communicated to the emergency service in the data DCV in step E 50 . 
         [0081]    If, during above-described step E 22 , it is determined that the emergency profile P_eCall is active, then the step S 22  is followed by the step E 50  of making the emergency call, and then followed by switching back to the profile P 1  (step E 70 ), possibly after waiting for a predetermined duration D (step E 60 ). 
         [0082]    In the above-described embodiment, the data file DCV specific to the vehicle  100  and to the main driver is stored in the emergency profile P_eCall. 
         [0083]    In a variant that is not shown, this data may be stored in a non-volatile memory of the operating system  125  of the vehicle. This data is then accessible by the communications device  130  after an authentication and decoding process when it makes an emergency call (step E 50 ). 
         [0084]    In another variant that is not shown, the data DCV is stored in the non-volatile memory  151  outside the emergency profile P_eCall. 
         [0085]    In the above-described embodiment, the emergency call is terminated by switching back to the profile that was active before the event EVT (step E 70 ). 
         [0086]    In a variant that is not shown, the emergency call may be terminated on receiving a command sent by an entity that is external to the vehicle, e.g. by the SM-SR entity, with the reception of such a command causing the profile that was active before the event EVT to be activated and causing the secure element to be restarted (RESET). 
         [0087]    In another variant embodiment, the system remains on the emergency profile P_eCall after making the emergency call, the data DCV sent to the emergency teams then including a number associated with this profile P_eCall enabling the vehicle to be called back.