• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    This method is implemented by a profile management server (500) for managing the profiles (P1, P2, PROV) of a secure entity. It comprises: - a step (S25) of sending a message (302) to said secure entity to modify the active profile of said entity; a step (V50) for initializing and triggering a timer (TIM); and in case of non-reception by said server (500), before the expiration of a predetermined duration counted from said trigger, of a message indicating the active profile in said secure entity (100): a triggering step an audit procedure (V100) for determining the actually active profile in said secure entity (100).
    公开号:FR3021835A1
    申请号:FR1454765
    申请日:2014-05-27
    公开日:2015-12-04
    发明作者:Arnaud Danree；Guillaume Larignon
    申请人:Oberthur Technologies SA；
    IPC主号:
    专利说明:

    [0001] BACKGROUND OF THE INVENTION The invention lies in the field of providing a profile to a secure entity incorporated in a mobile communication terminal. It is preliminary recalled that a "profile", in the context of the invention, is a set of files, data and applications installed on or intended for a secure entity and allowing the terminal that incorporates this secure entity, when this profile is activated, to access the services of a mobile telecommunication network defined by this profile. Figure 1 illustrates a profile management method according to the current state of the art. In this figure there is shown a profile management server 300, a network router 200 and a secure entity 100 incorporated in a mobile terminal 80. This secure entity 100 is an entity type eUICC (English "embedded Universal Integrated Circuit Card" ) as defined by the GSMA (GSM Association). It is recalled that unlike removable SI'M cards, an entity eUICC is an entity, generally welded, in any case that is not intended to be removed or replaced and that allows the change of profiles in a secure manner. We will assume that the profile management server 300 receives a request 301, during a step S10, to activate a profile on a secure entity. This request can be of the type: request (enable-profile (EID, ICCID)) in which: - EID is the unique identifier of the secure element eUICC; and - ICCID is a unique identifier for identifying a profile in a secure entity.
    [0002] It is recalled that the activation of a profile in a secure element consists of deactivating the current active profile and activating the new profile specified in the request. Returning to FIG. 1, the profile management server 300 maintains a profile management table 300T1 for each secure element EID, as shown in Appendix A. This table includes for each profile: 302 1 8 3 5 2 - the ICCID of the profile in the secure entity EID; - the type of this profile. In the example in Appendix A, the table includes a provisioning profile ("provisioning profile") and two operational profiles P1, P2; 5 - profile status: disabled or active; and an MSISDN phone number associated with this profile. It should be noted in this example that the profile management server 300 is aware that the current active profile of the secure element 100 is the operational profile P1.
    [0003] During a step S15, upon receipt of the request 301, the profile management server 300 identifies in the table 300T1, the profile P2 from the identifier ICCID contained in this request, and then generates an APDU request ( in English "Application Protocol Data Unit") in accordance with the IS07816 standard: 15 ENABLE PROFILE (P2) During a step S20, the profile management server 300 encrypts this APDU command and affixes a security header to it, for example. example an SCP80 security header conforming to the Global Platform standard.
    [0004] 20 Scp80-header ENABLE PROFILE (P2) During a step S25, the profile management server 300 uses a transport service to send the frame built in step S20 to the MSISDN telephone number associated with the active profile P1 in the table 300T1. The profile management server defines a time-to-live time for this message, for example equal to 24 hours. The transport service used to route this message and manage the aforementioned lifetime may for example be the SMS short message service, the GGSN service or the Internet network. We will assume later that this is the SMS service.
    [0005] The SMS message, referenced 302 in FIG. 1, is routed to a profile manager 120 Manager ") of the secure entity 100 via the transport network, and in particular via the router 200. The profile manager 120 receives the SMS message 302 during a step G10.
    [0006] 302 1 8 3 5 3 The profile manager 120 of the secure entity 100 maintains a profile management table 100T1, as shown in Appendix B. This table is similar to the table 300T1 maintained by the management server. 300 profiles for this secure entity, except that it does not include a fourth column MSISDN. In this example, we notice that the active profile of the secure element EID is the profile P1 and that the knowledge of the profile management server 300 is therefore correct. During a step G15, the profile manager 120 removes the security header SCP80 and decrypts the content of the SMS message 302: dectypt-scp80 (302) During a step G20, the profile manager 120 executes the activation command of the profile P2, which amounts to deactivating the current active profile P1 and activating the new profile P2.
    [0007] During a step G30, the profile manager 120 places a SIM Toolkit REFRESH command in the buffer intended for the mobile terminal 80. The processing of this REFRESH command has the effect of resetting the secure entity 100 and the execution In this restart procedure, the mobile terminal reads the table 100T1 and starts the authentication procedure associated with the new profile P2. This authentication procedure is defined by ETSI TS 131 102 V11.6.0 (2013-10). During a G35 test, the profile manager 120 checks whether the authentication procedure has been successful. If it is the case, the profile manager 120 updates its table 100T1 during a step G36 and sends, during a step G40, an SMS message 306 to the profile management server 300 to indicate it that the P2 profile is actually active. For example, the profile manager 120 can retrieve the MSISDN number of the server 300 from the message 302 or obtain this number from a memory of the entity 300. secure. The message 304 is normally received by the profile management server 300 during a step S30.
    [0008] 3021835 4 This message 306 is normally received by the profile management server 300 during a step S35. In which case, the profile management server 300 stores in its table 300T1 that the profile P2 is active so that the tables 300T1 and 100T1 are synchronized (step S36).
    [0009] In the event that the authentication procedure fails, the profile manager 120 triggers a fallback procedure consisting of activating the provisioning profile (step G50), updating the table 100T1 ( step G51) and send (step G55) an SMS message 310 to the profile management server 300 to indicate that the provisioning profile has been activated. The message 310 is normally received by the profile management server 300 during a step S45. In which case, the profile management server 300 stores in its table 300T1 that the profile P2 is active so that the tables 300T1 and 100T1 are synchronized (step S46). Therefore, and in summary, four messages are likely to be sent by the profile manager 120 of the secure entity 100 to the profile management server 300: the message 304 for acknowledging the message 302 activation of the P2 profile; the message 306 indicating that the activation of the profile P2 has been carried out successfully; the message 308 indicating that the activation of the profile P2 has failed; message 310 indicating that activation of the provisioning profile has been successfully performed. The non-receipt by the message profile management server 300 of the messages 306 or 310 indicating the effective activation of the profile P2 or the provisioning profile leads to desynchronization of the profile management tables 300T1 and 100T1 since in one or the other In another of these 30 situations, the profile management server considers that the profile P1 is still the current active profile. This situation is harmful because if the server 300 later wishes to contact the secure entity 100, for example to communicate an update script, it will use, by consulting the table 300T1, the phone number MSISDN of the profile 35 P1 to place of the number of the profile actually active.
    [0010] The present invention provides a method of managing profiles which does not have the aforementioned drawbacks. OBJECT AND SUMMARY OF THE INVENTION More specifically, and according to a first aspect, the invention relates to a method implemented by a profile management server for managing the profiles of a secured entity. This method comprises: a step of sending a message to this secure entity to modify the active profile of this entity; a step of initializing and triggering a time counter; and in the event of the server not receiving, before the expiry of a predetermined duration counted from said triggering, a message indicating the active profile in said secured entity: a step of triggering a procedure of audit to determine the actual active profile in this secure entity. Correlatively, the invention also relates to a profile management server for managing the profiles of a secured entity. This server 20 comprises: means for sending a message to this secure entity to modify the active profile of this entity; means for initializing and triggering a time counter; and 25 - if the server does not receive, before the expiry of a predetermined duration counted from said triggering, a message indicating the active profile in the secure entity: - means for triggering a procedure to determine the actual active profile in this secure entity.
    [0011] Thus, and in general, the invention proposes the implementation of an audit procedure to enable the profile management server to determine the profile actually active in a secure entity when this server does not receive not this information explicitly following the sending of a message to change active profile.
    [0012] The invention thus allows synchronization between the profile management tables managed by the server and by the entity itself.
    [0013] The invention makes it especially possible for the profile management server to keep accurate information as to the current active profile in the secure element. It can thus, for example, address this profile without fail, to give it an update script.
    [0014] The message sent by the server to modify the active profile of the entity may be: a message for installation and activation of a new profile; a message to disable or delete the active profile for a new operational profile or provisioning profile; 10 - any message likely to cause a modification of the active profile or a switch to the provisioning profile in case of failure of the modification. In a particular embodiment, the time counter is initialized to a duration corresponding to the lifetime of the message sent by the server to modify the active profile of the secure entity. This characteristic makes it possible to delay the triggering of the auditing procedure as much as possible. In a particular embodiment, the auditing procedure consists in sending at least one script to said secure entity to obtain at least the state of: the profile of the secure entity that said server considers active before modification; the profile of the secure entity that said server considers active after modification; 25 of the provisioning profile of the secure entity. Alternatively, the auditing procedure consists of sending at least one script to the secure entity to obtain the status of all known entity profiles of the profile management server. In one particular embodiment, this or these scripts 30 comprise an APDU GET STATUS command. This command advantageously makes it possible to obtain a state without modifying it. Alternatively, a GET DATA command, a SELECT command, or any other command or command set that reads the state in one or more files of the trusted entity without modifying it can be used.
    [0015] The aforementioned scripts can be sent one after another without waiting for the lifetime of the message carrying these scripts. In a variant, it is expected before sending a script, the lifetime of the sending message of the previous script if no response is received to the sending of this message. In a particular embodiment, the different steps of the transmission control method are determined by computer program instructions. Consequently, the invention also relates to a computer program on an information medium, this program being capable of being implemented by a computer, this program including instructions adapted to the implementation of the steps of the method. emission control as mentioned above. This program 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 form. another desirable form. The invention also relates to a computer-readable information medium, comprising instructions of a computer program as mentioned above.
    [0016] 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 floppy disk or a diskette. 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 in particular be downloaded to 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.
    [0017] BRIEF DESCRIPTION OF THE DRAWINGS Other features and advantages of the present invention will emerge from the description given below, with reference to the drawings and the appendices which illustrate an embodiment thereof which is devoid of any limiting nature. . In the figures: - Figure 1 already described illustrates a profile management method according to the state of the art; FIG. 2 represents a profile management server according to the invention; - Figure 3 illustrates a profile management method according to a particular embodiment of the invention. DETAILED DESCRIPTION OF THE EMBODIMENT FIG. 2 shows a profile management server 500 according to the invention. This profile management server 500 comprises a processor 101, a random access memory 102, a ROM-type ROM 103 and a network access module 104. These different elements are interconnected by a non-referenced bus system. The module 104 is capable of transmitting and receiving frames and messages of the type of the messages 301, 302, 304, 306 and 308 described with reference to FIG. 1. The profile management server 500 implements a method of the invention. profile management according to the invention and whose main steps are represented in flowchart form in FIG. 3. This method of managing profiles can be implemented by executing a computer program stored in the 103. FIG. 3 represents in flowchart form the main steps of a profile management method according to the invention. The steps Sxx of this method are identical to the steps Sxx of the state-of-the-art profile management method already described with reference to FIG. The profile management method according to the invention is remarkable in that, after step S25, it sends a message 302 for modifying the active profile of the secure entity 100, a step V26 302 1 8 3 5 9 initialization of a time counter, constituted in this example by a countdown 11M. Alternatively, the time counter may be constituted by a clock or any means for measuring a duration.
    [0018] In the embodiment described herein, this countdown TIM is initialized to a duration corresponding to the lifetime of the message 302. According to the invention, if the countdown TIM expires before receiving a message 306 or 310 indicating the effective activation of a new profile (P2 profile or PROV Provisioning Profile), the profile management server 500 triggers an audit procedure V100 referenced in Figure 3. For this purpose, the method according to the invention comprises a step V50 for checking whether the timer TIM has expired, the audit procedure being triggered if the result of the test V50 is positive.
    [0019] This auditing procedure consists of sending several scripts to the secure entity 100 to obtain at least the state of: the profile that the server 500 considers to be active at the current time, P1 in the example described here; of the profile for which the server 500 requests activation, P2 in the example described herein; Provisioning Profile PROV. Alternatively, the auditing procedure consists of sending scripts to obtain the status of all the profiles of the trusted entity 100 known to the server 500, namely of all the profiles listed in the profile management table 300T1. this entity. In the embodiment described here, the different status request scripts are sent to each of the profiles in parallel (step V55), using the APDU GET STATUS command. SMS (Scp80-header GET STATUS, MSISDN (P1)) SMS (Scp80-header GET STATUS, MSISDN (P2)) SMS (Scp80-header GET STATUS, MSISDN (PROV)) Using the GET STATUS command advantageously to know the state of the profile, without modifying this state. When the profile management server 500 receives a acknowledgment (step V60), it updates its profile management table 300T1 (step V65).
    [0020] The server profile management table 300T1 of the server 500 in accordance with the invention is thus synchronized with that 100T1 of the secure entity, even in the event of failure in the routing of the messages 306 and 310. the server 500 receives one of its messages 306 or 310 before the expiration of the TIP countdown, it disarms this countdown during a step V70. In the embodiment described here, the profile state request scripts are sent in parallel. They can alternatively be sent in series.
    [0021] 10 P1: P2: 302 1 8 3 5 11 APPENDIX A ICCID Status Type MSISDN profile 89103900000116765 Provisioning Disabled +34717742007 91038900000167165 Operational Active +34717742009 98139000001671605 Operational Disabled +34177420097 Table 300T1 APPENDIX B ICCID Profile Type Status 89103900000116765 Provisioning Disabled 91038900000167165 Operational Active 98139000001671605 Operational Disabled Table 100T1 5 10 P1: P2:
    权利要求:
    Claims (10)
    [0001]
    REVENDICATIONS1. Method implemented by a profile management server (500) for managing the profiles (P1, P2, PROV) of a secure entity (100) comprising: - a step (S25) for sending a message (302) ) said secure entity for modifying the active profile of said entity; a step (V50) for initializing and triggering a timer (TIM); and in case of non-reception by said server (500), before the expiration of a predetermined duration counted from said trigger, of a message indicating the active profile in said secure entity (100): a triggering step an audit procedure (V100) for determining the actually active profile in said secure entity (100).
    [0002]
    2. A profile management method according to claim 1, characterized in that said message (302) for modifying the active profile of said entity is a message for activating a new profile (P2) or a deactivation message. active current profile (P1).
    [0003]
    3. Profile management method according to claim 1 or 2, characterized in that said timer is initialized to a duration corresponding to the lifetime of the message (302) sent by said server to modify the active profile of the server. secure entity (100).
    [0004]
    4. Profile management method according to any one of claims 1 to 3, characterized in that said auditing procedure consists of sending (V55) at least one script to said secure entity to obtain at least the state: the profile (P1) of said entity (100) that said server 500 considers active before said modification; the profile (P2) of said entity (100) that said server 500 considers active after said modification; 35 of the provisioning profile (PROV) of said entity (100). 302 1 8 3 5 13
    [0005]
    5. Profile management method according to any one of claims 1 to 3, characterized in that said auditing procedure consists in sending (V55) at least one script to said secure entity to obtain the status of all the profiles. of said known entity (100) of said server.
    [0006]
    6. Profile management method according to claim 4 or 5, characterized in that said at least one script comprises an APDU GET STATUS command.
    [0007]
    7. Profile management method according to claim 4 to 6, characterized in that said scripts are sent in parallel.
    [0008]
    8. A profile management server (500) for managing the profiles (P1, P2, PROV) of a secure entity (100) comprising: means (104) for sending a message (302) to said entity secure to modify the active profile of said entity; means (101) for initializing and triggering a timer (TIM); and in case of non-reception by said server (500), before the expiry of a predetermined duration (TIM) counted from said triggering, of a message indicating the active profile in said secured entity (100): means (101) for triggering an audit procedure (V100) for determining the actually active profile in said secure entity (100).
    [0009]
    A computer program comprising instructions for performing the steps of a profile management method according to any one of claims 1 to 7 when said program is run by a computer.
    [0010]
    A computer-readable recording medium on which a computer program is recorded including instructions for performing the steps of a profile management method according to any one of claims 1 to 7.
    类似技术:
    公开号 | 公开日 | 专利标题
    EP3149983B1|2018-07-04|Profile management method and server
    FR3029728A1|2016-06-10|METHOD FOR PROVIDING A SUBSCRIBER PROFILE FOR A SECURE MODULE
    US9578492B2|2017-02-21|Secure mechanism to deliver mobile traffic management configuration upon stub activation on a mobile device of a global service discovery server
    FR3036574A1|2016-11-25|LOADING SUBSCRIPTION PROFILE IN AN EMBARCED SIM CARD
    EP2692113B1|2015-09-30|Method for updating secure elements included in terminals of a telecommunication network, and corresponding update server
    EP3155823B1|2020-05-20|Management, by an intermediate device, of the quality of transmission of a data stream to a mobile terminal
    FR2984050A1|2013-06-14|METHOD FOR MANAGING THE CONNECTIVITY OF A TERMINAL
    JP6420476B2|2018-11-07|Electronic device configuration for wireless communication
    FR2892837A1|2007-05-04|File data downloading method for e.g. payment card, involves notifying campaign server that event relating to presence of communicating object satisfies transmitted campaign rules to initiate downloading of data towards object
    EP2862391A1|2015-04-22|Method of roaming in the event of deficiency of the data service of a mobile telephone network
    FR3067197A1|2018-12-07|METHOD FOR SELECTING A NETWORK SLIDER RELATING TO AN APPLICATION
    EP3375169B1|2019-08-21|Method for managing network traffic related to a mechanism for signalling the presence of a terminal
    FR3079644A1|2019-10-04|METHOD FOR MANAGING A GROUP OF EQUIPMENTS, SERVER AND SYSTEM THEREFOR
    EP3278542B1|2019-01-02|System and method for executing an application on a terminal provided with a chip card
    EP3811679A1|2021-04-28|Method and device for managing an overload of a network core controlling a mobile access network
    WO2021234250A1|2021-11-25|Method for notifying a mobile terminal
    CN111064798A|2020-04-24|Node network access method, device, client node and storage medium
    FR2967327A1|2012-05-11|SYSTEM AND METHOD FOR MANAGING COMMUNICATIONS OF AT LEAST ONE TERMINAL IN A COMMUNICATION NETWORK
    FR3067538A1|2018-12-14|METHOD FOR CONTROLLING THE OBTAINING BY A TERMINAL OF A CONFIGURATION FILE
    EP2424315A1|2012-02-29|Method for updating a database of subscribers registered on an OTA platform, corresponding card and OTA platform
    FR3038176A1|2016-12-30|PROVIDING AND MANAGING PROFILES ON A SECURE ELEMENT, SECURE ELEMENT AND ASSOCIATED SERVER
    EP2448235A2|2012-05-02|Electronic entity managing a credit for using a resource in which access to same is controlled by a control device
    同族专利:
    公开号 | 公开日
    KR102191176B1|2020-12-15|
    EP3149983A1|2017-04-05|
    RU2673845C2|2018-11-30|
    RU2016151382A3|2018-10-12|
    US9883386B2|2018-01-30|
    EP3149983B1|2018-07-04|
    RU2016151382A|2018-06-27|
    US20170188230A1|2017-06-29|
    CN106537957A|2017-03-22|
    JP6514238B2|2019-05-15|
    KR20170008273A|2017-01-23|
    CN106537957B|2020-03-10|
    FR3021835B1|2016-06-17|
    WO2015181485A1|2015-12-03|
    JP2017521908A|2017-08-03|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    KR20130049730A|2011-11-04|2013-05-14|주식회사 케이티|Method, embedded uicc, and device for managing multiple profile in embedded uicc|
    EP2600587A1|2011-11-29|2013-06-05|Oberthur Technologies|Method for authenticating a terminal with a telecommunication network|
    EP2680627A1|2012-06-26|2014-01-01|Giesecke & Devrient GmbH|Methods and devices for locking secure element to a mobile terminal|
    KR20140024796A|2012-08-20|2014-03-03|주식회사 케이티|Method for managing profiles in subscriber identidy module embedded in user terminal and apparatus using the method|
    GB0213479D0|2002-06-12|2002-07-24|Nokia Corp|Downloadable profiles for mobile terminals|
    US7903817B2|2006-03-02|2011-03-08|Cisco Technology, Inc.|System and method for wireless network profile provisioning|
    CN101079763A|2006-06-12|2007-11-28|腾讯科技（深圳）有限公司|A remote configuration and management system and method of servers|
    US8571585B2|2007-11-01|2013-10-29|Blackberry Limited|Method, system and apparatus for updating a terminal profile|
    US8208900B2|2008-03-04|2012-06-26|Apple Inc.|Secure device configuration profiles|
    WO2010006637A1|2008-07-14|2010-01-21|Nokia Siemens Networks Oy|A method and apparatus for a subscriber database|
    CA2689247C|2008-12-29|2016-05-10|Research In Motion Limited|Device-based network service provisioning|
    ES2354331B1|2009-04-24|2012-01-30|Vodafone España, S.A.U.|PROCEDURE AND SYSTEM FOR MIGRATING PROFILES IN TELECOMMUNICATIONS DEVICES.|
    US8898748B2|2009-05-21|2014-11-25|Mobile Iron, Inc.|Remote verification for configuration updates|
    US8996002B2|2010-06-14|2015-03-31|Apple Inc.|Apparatus and methods for provisioning subscriber identity data in a wireless network|
    WO2012003564A1|2010-07-08|2012-01-12|Redknee Inc.|Method and system for dynamic provisioning while roaming|
    CN102624538B|2011-01-27|2016-06-15|中兴通讯股份有限公司|The method of a kind of initialize process exception process and system|
    US9148487B2|2011-12-15|2015-09-29|Verizon Patent And Licensing|Method and system for managing device profiles|
    KR101661264B1|2012-02-10|2016-09-29|애플 인크.|Methods and apparatus for correcting error events associated with identity provisioning|
    US8577337B2|2012-03-05|2013-11-05|Rogers Communications Inc.|Radio management method and system using embedded universal integrated circuit card|
    US9585000B2|2012-05-25|2017-02-28|Kt Corporation|Method of providing subscriber profile of eUICC based on change of network|
    US9137656B2|2012-06-27|2015-09-15|Rogers Communications Inc.|System and method for remote provisioning of embedded universal integrated circuit cards|
    KR102072592B1|2012-09-24|2020-02-03|삼성전자 주식회사|METHOD FOR MANAGING IDENTIFIER OF eUICC AND APPARATUS FOR PERFORMING OF THE SAME|
    EP2747466B1|2012-12-21|2017-10-04|Giesecke+Devrient Mobile Security GmbH|Methods and devices for ota subscription management|
    CN103108262B|2013-03-07|2016-03-23|烽火通信科技股份有限公司|The method of optical network unit configuration file upgrading in GPON system|
    KR102133450B1|2013-05-30|2020-07-13|삼성전자 주식회사|Method and apparatus for setting profile|
    US9674691B2|2014-03-21|2017-06-06|T-Mobile Usa, Inc.|Polling by universal integrated circuit card for remote subscription|KR102303504B1|2015-03-25|2021-09-17|삼성전자 주식회사|Method and apparatus for installing profile by a terminal in a wireless communication system|
    DE102015008179A1|2015-06-25|2016-12-29|Giesecke & Devrient Gmbh|Communicating a subscriber identity module to a server, especially when changing profiles|
    CN109756882B|2017-11-03|2021-11-19|中国电信股份有限公司|Communication method, system, SMSR and computer readable storage medium|
    FR3077457B1|2018-01-30|2020-02-21|Thales|METHOD FOR MANAGING ACCESS TO A TELECOMMUNICATION INFRASTRUCTURE INCLUDING PUBLIC AND PRIVATE NETWORKS AND ASSOCIATED DEVICES|
    US10187784B1|2018-06-11|2019-01-22|Verizon Patent And Licensing Inc.|Systems and methods for transferring SIM profiles between eUICC devices|
    法律状态:
    2015-04-22| PLFP| Fee payment|Year of fee payment: 2 |
    2015-12-04| PLSC| Search report ready|Effective date: 20151204 |
    2016-04-22| PLFP| Fee payment|Year of fee payment: 3 |
    2017-04-21| PLFP| Fee payment|Year of fee payment: 4 |
    2018-04-23| PLFP| Fee payment|Year of fee payment: 5 |
    2019-04-19| PLFP| Fee payment|Year of fee payment: 6 |
    2020-04-22| PLFP| Fee payment|Year of fee payment: 7 |
    2021-04-21| PLFP| Fee payment|Year of fee payment: 8 |
    优先权:
    申请号 | 申请日 | 专利标题
    FR1454765A|FR3021835B1|2014-05-27|2014-05-27|PROFILE MANAGEMENT METHOD AND SERVER|FR1454765A| FR3021835B1|2014-05-27|2014-05-27|PROFILE MANAGEMENT METHOD AND SERVER|
    CN201580040788.1A| CN106537957B|2014-05-27|2015-05-26|Method and server for managing configuration files|
    RU2016151382A| RU2673845C2|2014-05-27|2015-05-26|Method and server for profile management|
    US15/314,004| US9883386B2|2014-05-27|2015-05-26|Method and a server for managing profiles|
    KR1020167035143A| KR102191176B1|2014-05-27|2015-05-26|Method and a server for managing profiles|
    PCT/FR2015/051379| WO2015181485A1|2014-05-27|2015-05-26|Profile management method and server|
    JP2016569845A| JP6514238B2|2014-05-27|2015-05-26|Profile management method and server|
    EP15732799.0A| EP3149983B1|2014-05-27|2015-05-26|Profile management method and server|
    [返回顶部]