Patent Grant
11003797
The present invention relates to a method for subscription management. More precisely, the invention relates to a method for managing subscriptions in a security element for a mobile end device.
Respectively one subscription profile is therefore associated with one subscription. Such a subscription profile is then stored in the security element as a data set or application. The subscription profile defines conditions, i.e. e.g. type, extent and costs, of a utilization by means of the security element of a mobile communication network associated with the subscription and of the mobile end device into which the security element is integrated.
Different subscriptions request in different ways functionalities of the security element, in which the subscription profile associated with the subscription is stored. A “simple” subscription, which for example allows merely a data transfer according to a pre-specified maximum volume via the mobile communication network associated with the subscription, requires very few functionalities of the security element. An “extensive” subscription, however, which for example allows a user to utilize practically all services supplied on the part of the mobile communication network (e.g. mobile communication, SMS, Internet) to the full extent, requires also numerous complex functionalities supplied on the part of the security element, for example cryptographic functionalities or access to a module for the contactless data communication (e.g. via NFC).
Because a subscription profile or applications executable within such a subscription profile in the security element can in principle utilize all functionalities of the security element supplied within the scope of an initialization of the security element, an access of a subscription to a functionality not required for the subscription can be restricted (e.g. for security reasons) only by coordinating an initialization of the security element to a subscription to be loaded onto the security element. On the one hand this is elaborate because respectively different initializations of a security element must be generated for different subscriptions. On the other hand this is then problematic if hereafter a further subscription is to be loaded onto the security element which differs from the already loaded subscription with regard to the access to functionalities of the security element necessary for operating the subscription.
The object of the present invention is thus to take into account the problems mentioned hereinabove.
The basic idea of the present invention is to subscription-profile-specifically restrict the access of a subscription profile to functionalities of the security element. In other words, a subscription profile itself comprises, after a suitable modification, the information item as to which functionalities of the security element are accessible for the subscription profile.
According to a preferred embodiment of a method for subscription management in a security element for a mobile end device, in which respectively a subscription profile stored or storable in the security element is associated with a subscription, an access of such a subscription profile to functionalities of the security element, which in principle are available in the security element, is subscription-specifically restricted. In other words, a subscription profile is specified or modified or supplemented such that thereby an access of the subscription profile to functionalities of the security element can be stated, i.e. in particular also be restricted.
Here, an access of an application, said application being associated with the subscription profile and executable in the security element within a subscription profile, to functionalities of the security element is preferably subscription-profile-specifically restricted.
According to a preferred embodiment, the functionalities of the security element are supplied by programming interfaces of the security element so that the restriction of the access to the functionalities is realized as a restriction of the access or opportunity for utilization to programming interfaces of the security element.
According to a preferred embodiment, the metadata specifying the subscription profile are generated for a pre-specified subscription profile. These metadata can be generated in particular as an header information item which, if the subscription profile is regarded as a data set, are present as components of the data set specifying the data set, as a rule at the beginning of the data set.
Such metadata can be stored in the security element on the one hand as a part of a modified subscription profile, or as an additional data set associated with the subscription profile, i.e. separate from the subscription profile.
These metadata specifying the subscription profile then designate those functionalities of the security element which the subscription profile or applications executable within the subscription profile can access.
Alternatively or additionally, the metadata can also designate such functionalities of the security element which cannot be employed on the part of the subscription profile, i.e. to which an access is refused by the subscription profile.
According to a preferred variant, the metadata designate those programming interfaces (API) of the security element which the subscription profile or applications executable within the subscription profile can access (or not access). In this manner, those functionalities are thus indirectly designated which the subscription profile can access (or not access) via the designating APIs.
Here, the metadata can be generated on the one hand already before the loading of the subscription profile into the security element and then be loaded together with the subscription profile into the security element or be stored therein.
Alternatively or additionally, it can likewise be provided that the metadata are generated only then and are stored in the security element or are changed in the security element after the subscription profile has already been loaded into the security element. Such a subsequent supplementation or change of the metadata can be effected for example via an over-the-air interface. In this manner an access of a subscription profile to functionalities of the data carrier can subsequently be adapted, whereby it can be flexibly reacted to for example a change of the subscription, i.e. a change or adaptations of the conditions for the utilization of the mobile communication network.
As a rule, a manufacturer or an issuer of the security element in the role of a subscription administrator or subscription manager will subscription-specifically restrict an access of a specific subscription profile to functionalities of the security element in the described manner. In other words, as a rule it is incumbent upon the manufacturer or issuer of the security element to generate the hereinabove described metadata specifying the subscription profile and to store or adapt said metadata in the security element. An operator of a mobile communication network, which a subscription is associated with, is as a rule not authorized and technically not able to define or influence an access of a subscription profile to functionalities of the security element on the basis of a subscription profile.
The substantial advantage of the inventive concept, according to which an access of a subscription profile to functionalities of a security element can be subscription-profile-specifically limited, lies therein that a manufacturer of a security element can standardizes and initialize the security element in its entirety, regardless of the subscriptions to be subsequently loaded thereon. An access of the subscriptions then later loaded onto the security element to individual functionalities of the security element can then be restricted subscription-specifically for each subscription in the hereinabove described manner.
In this manner it becomes possible that each subscription obtains through the subscription profile a pre-specified, limited access to functionalities of the security element which can be different from subscription to subscription. The manufacture of the security element is therefore simplified, because this can always be initialized according to a standard. Nevertheless, for each subscription loaded—even subsequently—onto the security element, an access to functionalities of the security element tailored specifically to the subscription can be guaranteed.
A preferred embodiment of an inventive security element for a mobile end device, in which security element one subscription profile is stored for at least one subscription, is characterized by the fact that an access of the subscription profile to functionalities of the security element is subscription-profile-specifically restricted.
As already indicated, metadata specifying the subscription profile for a subscription profile stored in the security element can additionally be stored in the security element. Preferably these metadata designate positively those functionalities or those programming interfaces of the security element which the subscription profile can access. Alternatively or additionally, the metadata can also designate negatively those functionalities and/or programming interfaces which the subscription profile cannot access.
An inventive mobile end device comprises a hereinabove described security element. Here, the security element can be removably integrated into the end device, for example in the form of a SIM/UICC mobile communication card, or firmly incorporated in the end device, e.g. as an embedded SIM/UICC.
A preferred embodiment of an inventive system comprises a subscription management device as well as at least one security element for a mobile end device of the described kind. The subscription management device is devised to specify a subscription profile, which is stored in the security element or is storable in the security element, such that thereby an access of the subscription profile to functionalities present in the security element is restricted.
The subscription management device is preferably arranged at a manufacturer or an issuer of the security element. An operator of a mobile communication network associated with a subscription has as a rule organizationally and technically no possibility to influence via a subscription profile an access of the subscription profile to functionalities of the security element.
The subscription management device is preferably devised to generate metadata specifying the subscription profile for a pre-specified subscription profile, in particular in the form of header information items or the like, and to store said metadata in the security element as a complementary component of the subscription profile or in addition to the subscription profile. These metadata designate an access of the subscription profile to the security element in the manner already described in detail hereinabove.
The subscription management device is ultimately devised to subsequently change or adapt corresponding metadata stored in the security element. In general, the subscription management device is devised to subsequently adapt a subscription profile stored in the security element to the effect that thereby the access of the subscription profile to functionalities of the security element is restricted.
The invention will hereinafter be described by way of example with reference to the attached figure. Said
In a first step S1, a security element having a standardized initialization is supplied.
This initialization in principle allows access to all functionalities of the security element for a subscription profile which can be loaded into the security element.
A security element as intended by the present invention is in particular a conventional SIM/UICC mobile communication card, an embedded SIM/UICC, or any other security element which is suitable to store a subscription profile for a subscription for utilizing a mobile communication network in secure manner.
In a second step S2, a subscription profile is supplied to a subscription associated with a mobile communication network. Such a subscription profile defines conditions (type, extent, costs, etc.) of a utilization of services which are supplied by a mobile communication network associated with the subscription.
The subscription profile is now specified in step S3. In this manner, an access of the subscription profile or applications executable within such a subscription profile can be restricted to selected functionalities of the security element.
According to a preferred variant, the specification of the subscription profile is effected by the fact that metadata are generated for the subscription profile, for example header information items, which are prefixed to the subscription profile.
Hereafter a possible encoding of a subscription profile thus specified is stated by way of example in the form of an XML file. Here, the actual, original subscription profile is merely indicated concisely in the last three lines (“profile data”). The “ProfileHeader” stated in the example corresponds to the metadata described hereinabove.
For example it can be seen from the hereinabove shown example that for the subscription profile, programming interfaces of the security element which the subscription profile can access are stated positively. In the shown example, these are all APIs of the “javacard.framework”. Further individual functionalities from the region “javacard.security” are accessible (e.g. encryption and decryption by means of RSA and DES), others of these are not accessible (e.g. encryption and decryption by means of AES and ECC).
It will be appreciated that the stated example is to be understood merely exemplary and that an implementation of a header data set can be effected in a different manner.
In general, those functionalities which a subscription profile can access and which are subscription-profile-specifically designated according to the present invention and thereby restricted, concern such functionalities which can be called up by a subscription profile or by an application executed within the subscription profile as an auxiliary functionality, such as cryptographic functionalities. In contrast, functionalities of the security element which are directed toward a change of the security element itself or to a change of the functionality of the security element are as a rule not be embraced by the present invention.
In step 4, such a specified subscription profile, in particular together with the metadata generated for the subscription profile, can then be loaded into the security element or be stored therein.
While the security element is already employed in accordance with the requirements, that is it is used integrated in a mobile end device, an adapting, as represented with reference to step S5, of the specified subscription profile can be effected in the security element. Thereby, an access of a subscription profile to functionalities of the security element can be changed subsequently. Such a change can mean on the one hand an extension of the access, on the other hand a further restriction of the access.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10 2015 008 117.9 | Jun 2015 | DE | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2016/001065 | 6/22/2016 | WO | 00 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2016/206806 | 12/29/2016 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 6961587 | Vilppula et al. | Nov 2005 | B1 |
| 7953445 | Brown | May 2011 | B2 |
| 8001375 | Hattori et al. | Aug 2011 | B2 |
| 9098714 | Sharp et al. | Aug 2015 | B2 |
| 9116768 | Sawhney | Aug 2015 | B1 |
| 9253588 | Schmidt et al. | Feb 2016 | B2 |
| 9262645 | Biswas | Feb 2016 | B2 |
| 9378383 | Sand-Soll | Jun 2016 | B2 |
| 9608989 | Corda et al. | Mar 2017 | B2 |
| 9626520 | Sharp et al. | Apr 2017 | B2 |
| 10311246 | Paczkowski | Jun 2019 | B1 |
| 20050070321 | Weigele | Mar 2005 | A1 |
| 20060253894 | Bookman | Nov 2006 | A1 |
| 20080039134 | Hattori et al. | Feb 2008 | A1 |
| 20090077643 | Schmidt et al. | Mar 2009 | A1 |
| 20100031366 | Knight | Feb 2010 | A1 |
| 20100205432 | Corda et al. | Aug 2010 | A1 |
| 20120331292 | Haggerty | Dec 2012 | A1 |
| 20130145429 | Mendel | Jun 2013 | A1 |
| 20130165073 | Madsen | Jun 2013 | A1 |
| 20130210484 | Jeenagala et al. | Aug 2013 | A1 |
| 20130227646 | Haggerty | Aug 2013 | A1 |
| 20140040979 | Barton | Feb 2014 | A1 |
| 20140143826 | Sharp et al. | May 2014 | A1 |
| 20140331279 | Aissi | Nov 2014 | A1 |
| 20150312873 | Cormier | Oct 2015 | A1 |
| 20160063260 | Sharp et al. | Mar 2016 | A1 |
| 20160094560 | Stuntebeck | Mar 2016 | A1 |
| 20160226860 | Schmidt et al. | Aug 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 60015748 | Nov 2005 | DE |
| 102013006621 | Oct 2014 | DE |
| 2010034912 | Feb 2010 | JP |
| 2010541059 | Dec 2010 | JP |
| 2013242878 | Dec 2013 | JP |
| 2015513821 | May 2015 | JP |
| 2016505929 | Feb 2016 | JP |
| 0069183 | Nov 2000 | WO |
| 2005121975 | Dec 2005 | WO |
| 2014081890 | May 2014 | WO |
| Entry |
|---|
| I. Podnar, M. Hauswirth and M. Jazayeri, “Mobile push: delivering content to mobile users,” Proceedings 22nd International Conference on Distributed Computing Systems Workshops, Vienna, Austria, 2002, pp. 563-568. (Year: 2002). |
| H. Jafarpour, S. Mehrotra and N. Venkatasubramanian, “A Fast and Robust Content-based Publish/Subscribe Architecture,” 2008 Seventh IEEE International Symposium on Network Computing and Applications, Cambridge, MA, USA, 2008, pp. 52-59, doi: 10.1109/NCA.2008.51. (Year: 2008). |
| German Search Report from DE Application No. 10 2015 008 117.9, dated Feb. 18, 2016. |
| International Search Report from PCT Applilcation No. PCT/EP2016/001065, dated Aug. 8, 2016. |
| International Preliminary Report on Patentability from PCT Application No. PCT/EP2016/001065, dated Dec. 26, 2017. |
| Extended European Search Report from EP Application No. 16731804.7, dated Jan. 23, 2019. |
| Japanese Office Communication from JP Application No. 2017-567449, dated Jan. 30, 2019. |
| “Metadaten,” retrieved from https://de.wikipedia.org/w/index.php?title=Metadaten&oldid=142121865 on Sep. 12, 2019, 14 Pages. |
| European Office Action from EP Application No. 16731804.7, dated Sep. 19, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| 20180189506 A1 | Jul 2018 | US |
