Method for configuring a chip module with a configuration file, chip module and device having such a chip module

Abstract

The invention relates to a method (200) for configuring a chip module (10) using a configuration file, comprising the following steps: transmitting (201) an initial configuration file to the chip module (10); storing (202) the initial configuration file in a memory (14) of the chip module (10); transmitting (203) the profile type information to the chip module (10) and linking the profile type information with the initial profile to generate a typed profile; requesting (204) profile data (53) from a profile provision unit (30); transmitting (205), by the profile provision unit (30), the profile data (53) to the profile management unit (20); transmitting (206) the profile data (53) to the chip module (10) by means of the profile management unit (20); the profile data (53) is linked (207) with the typed profile to generate a modified profile.

Description

Technical Field

[0001] The present invention relates to a method for configuring a chip module using a configuration file, a chip module for maintaining multiple selectively active configuration files, and a device having a communication module and the chip module. Background Technology

[0002] In many fields, chip cards or chip modules in the form of integrated circuits are used to grant or deny access to services. Chip modules contain data that uniquely identifies a person or device. Furthermore, chip modules contain processors capable of performing computational steps.

[0003] If the chip module is designed as a chip card, it has, for example, a card body and an integrated circuit, in the form of a chip module embedded in the card body. The chip module is inserted into a cavity or module opening in the card body.

[0004] Chip modules can also be designed as integrated electronic circuits. In this regard, it should be understood that the references to chip cards and the descriptions of chip cards in this specification generally apply to chip modules and their implementation as integrated electronic circuits.

[0005] Before a chip card can be used to access services, it must typically be equipped with a configuration file. One or more configuration files can be stored on the chip card, each of which enables or requires the chip card and the device containing the chip card to have different access permissions or different operating modes.

[0006] When accessing mobile communication services, chip modules, often referred to as SIM cards (subscriber identity modules) or eSIMs (embedded SIMs), are frequently used to grant devices or users corresponding access permissions. Configuration files are stored on the chip module and used to configure the entry point for the communication services.

[0007] There exist configurations in which the device can use different types of profiles to transmit data over a communication network. Therefore, it is conceivable that the device contains multiple chip modules, for example, to transmit user data using a first profile, while using a second profile for data exchange between the device and the manufacturer for maintenance or other purposes.

[0008] Similarly, it is conceivable that different configuration file types should be used to run the device at different times or in different environments.

[0009] In the consumer electronics sector, the relevant GSMA standard is SGP.22, while in the IoT sector it is SGP.32. There are differences in how configuration files are transferred to the chip module and how they are managed under SGP.22 and SGP.32. Currently, this necessitates using separate chip modules for SGP.22 and SGP.32 respectively.

[0010] To personalize a chip module or device with a chip module for a user—that is, to set a configuration file for the chip module or device with a chip module that uniquely identifies the user and defines their permissions in the communication network—the configuration file must be transmitted to the chip module. This transmission process may require the exchange of multiple messages, which can make the process complex and error-prone. Summary of the Invention

[0011] It can be considered that the technical problem to be solved by the present invention is to reduce the overhead of generating configuration files in chip modules.

[0012] The aforementioned technical problem is solved by the method for configuring a chip module using a configuration file according to the independent claim, the chip module for maintaining multiple selectively active configuration files, and the device having a communication module and the chip module. Other embodiments are derived from the dependent claims and the following description.

[0013] According to one aspect, a method for configuring a chip module using a configuration file is provided. The method includes the following steps: transmitting an initial configuration file to the chip module; storing the initial configuration file in the chip module's memory; transmitting configuration file type information to the chip module and linking the configuration file type information with the initial configuration file to generate a typed configuration file; requesting configuration file data from a configuration file providing unit; transmitting the configuration file data to a configuration file management unit through the configuration file providing unit; transmitting the configuration file data to the chip module through the configuration file management unit; and linking the configuration file data with the typed configuration file to generate a modified configuration file. Then, in addition to other configuration files, the modified configuration file can be used as the chip module's configuration file.

[0014] Profiles are used to identify devices and / or people relative to service providers and to assign access permissions and / or roles to devices and / or people. Service providers can use profiles to grant or deny specific permissions for access to services.

[0015] Before a device accesses a service for the first time, it must prepare for that access. This specifically includes storing a configuration file. In the case described here, this is particularly true for a configuration file used to access a communication network, such as a wireless mobile communication network.

[0016] The device first obtains an initial configuration file, which can generally be used to access the communication network. Subsequently, this initial configuration file can be categorized and modified, as will be further described below.

[0017] The initial configuration file initially sent to the chip module is, for example, a generic configuration file. The chip module or the device containing the chip module can basically function normally using this initial configuration file; that is, the chip module or device can use this initial configuration file to establish a connection with a network, especially a wireless communication network.

[0018] Preferably, during the manufacturing process of the device containing the chip module, the initial configuration file is transferred to the chip module and stored in the chip module's memory. Therefore, during device manufacturing, for example, in one of the final steps of manufacturing, the chip module is configured to establish basic functionality for connecting to a communication network and enabling the exchange of information through the communication network.

[0019] When the chip module already contains an initial configuration file, the configuration file type information is transmitted to the chip module. Based on this initial configuration file and the configuration file type information, a typed configuration file is generated. This means setting additional parameters for the initial configuration file to achieve behavior according to specific pre-given parameters and to meet specific requirements related to connectivity to the communication network imposed on the typed configuration file. By transmitting the configuration file type information and linking this configuration file type information with the initial configuration file, the initial configuration file is transformed into a configuration file with a different configuration file type.

[0020] The configuration file type information defines the configuration file type. The configuration file type, in particular, can affect how configuration files are managed and how the chip module behaves when the corresponding configuration file is activated.

[0021] Configuration file type information indicates which configuration file type the configuration file belongs to. Configuration file type information can be a data field or value that is uniquely associated with a specific configuration file type. For example, the first value of configuration file type information could point to the initial configuration file, the second value could point to the SGP.22 configuration file, and the third value could point to the SGP.32 configuration file.

[0022] Storing the initial configuration file in the chip module's memory and transferring the configuration file type information to the chip module are preferably performed in separate steps. This has the advantage that the steps of storing the initial configuration file in the chip module's memory and subsequently transferring the configuration file type information to the chip module can be performed at different times and by different units. For example, the initial configuration file can be stored in the device's chip module as part of the device's manufacturing process, while the configuration file type information can be transferred to the chip module after manufacturing and linked to the initial configuration file. Linking the transferred configuration file type information to the initial configuration file means, for example, that the value of the configuration file type in the initial configuration file is replaced, thereby changing the configuration file type from "initial configuration file" to another configuration file type, such as SGP.22 or SGP.32. The step of transferring the configuration file type information and linking it to the initial configuration file can also be performed by the device manufacturer, but it can also be performed by a distributor or, similarly, by the device user.

[0023] For example, the profile type can indicate whether the profile is for a device belonging to a natural person who is a consumer in nature (i.e., a consumer device) or for a networked device used in an IoT environment (i.e., a so-called IoT device). The GSMA's SGP.22 series of specifications defines the process for providing and using profiles for consumer devices. The SGP.32 series of specifications defines the process for providing and using profiles for IoT devices. SGP.22 and SGP.32 describe how profiles reach the chip module and how the device behaves when the corresponding profile is used.

[0024] After generating the typed configuration file, the personalized configuration file data can be transferred to the chip module to generate the modified configuration file as given. It should be noted that the initial configuration file may already contain standard set configuration file data, which enables registration and login within the communication network. However, this standard set of configuration file data is typically not assigned to any individual user. Therefore, to modify the configuration file, it is usually necessary to replace the standard set of configuration file data with personalized configuration file data or assign the initial configuration file data to the user.

[0025] Although the initial configuration file is described as a generic configuration file above, in the first step, an SGP.22, SGP.32, or other type of configuration file can also be loaded onto the chip module as the first or initial configuration file, and then converted to other configuration file types. Furthermore, multiple configuration files can be loaded onto the chip module in the first step, for example, the initial configuration file and an SGP.22 or SGP.32 configuration file, and then one or two configuration files can be converted to other configuration file types (the same or different target configuration file types).

[0026] In one implementation, an initial configuration file is stored in the chip module's memory before the chip module is put into operation.

[0027] This approach has the advantage that an initial configuration file can be set up for the chip module or the device containing it before it is put into operation. Therefore, data exchange with the chip module can occur via a network before it is linked to the user's personalized configuration file.

[0028] In another implementation, storing the initial configuration file in the chip module's memory and transmitting the configuration file type information to the chip module are performed separately.

[0029] This means, for example, that these steps are performed sequentially in time, and / or spaced apart from each other, that is, performed with time intervals between them.

[0030] In another implementation, configuration file type information is transmitted to the chip module after the chip module is put into operation.

[0031] This means that the chip module is first put into operation using the initial configuration file, and only after the chip module is put into operation is it typed, that is, a typed configuration file is generated.

[0032] Typically, the remaining configuration file data is transferred to the chip module after the chip module is put into operation, in order to generate the modified configuration file.

[0033] The scheme described herein begins with the transmission of an initial configuration file, followed by the creation of a typed configuration file and then a modified configuration file. This allows some of the steps in the method described herein to be transferred to the manufacturing process of the chip module or the device containing the chip module. Therefore, since a portion of the configuration file can already be incorporated into the chip module at the device manufacturer or supplier, the overhead of transmitting the fully modified configuration file to the chip module is reduced. This will be further explained below with reference to transmitting the configuration file in an "offline" or "online" manner. With this design of the method, the number of steps required to put the device into operation, the amount of data to be transmitted to the device or chip module, and the overhead for securely transmitting the data are significantly reduced.

[0034] In another implementation, the initial configuration file is transmitted to the chip module via a wired connection.

[0035] For example, during the manufacturing process of the equipment, a wired connection is established with the communication interface of the chip module, and the initial configuration file, along with other data, is transmitted to the chip module and stored in its memory. However, the initial configuration file can also be transmitted wirelessly to the device with the chip module. Crucially, the initial configuration file is transmitted to the chip module offline before the user puts the equipment into operation.

[0036] In another embodiment, the configuration file data is transmitted to the configuration file management unit via a wireless connection through the configuration file providing unit.

[0037] This variant enables the wireless transmission of configuration file data used to generate the modified configuration file to a device containing the chip module. Therefore, it is particularly useful after the device is put into operation, i.e., in a so-called online mode, to transmit the configuration file data to the device.

[0038] In another embodiment, the method further includes: removing configuration file type information from the modified configuration file to generate a reset configuration file.

[0039] In this step, as preparation for changing the configuration file type, the configuration file data is preferably retained in the configuration file, while only the configuration file type is removed. When removing the configuration file type information from the modified configuration file, for example, the configuration file type "Initial Configuration File" can be set to a standard value.

[0040] The chip module can be retyped from its initial state, and the configuration file type can be changed, for example, from the initial configuration file to SGP.22 or SGP.32, or from SGP.22 to SGP.32 or the initial configuration file, or from SGP.32 to SGP.22 or the initial configuration file.

[0041] In another embodiment, the method further includes the following steps: transmitting the modified configuration file type information to the chip module, and linking the modified configuration file type information with the reset configuration file to regenerate the typed configuration file.

[0042] It's conceivable that removing the configuration file type information would also remove the configuration file data. In this case, regenerating the configuration file would also require the configuration file data. This is achieved by performing the following steps: requesting configuration file data from the configuration file providing unit; transmitting the configuration file data to the configuration file management unit via the configuration file providing unit; transmitting the configuration file data to the chip module via the configuration file management unit; and linking the configuration file data with the typed configuration file to generate the modified configuration file. However, it's also possible to remove the configuration file type information without removing the configuration file data, instead retaining the configuration file data within the configuration file, thus only replacing the configuration file type information.

[0043] After the chip module is first reset to its initial state, it can be retyped and modified. During this retypening, the initial configuration file can adopt characteristics of a different configuration file type than in the first type. In this process, configuration file data from other users can also be linked to this configuration file.

[0044] In another embodiment, the method further includes the following steps: transmitting an instruction to the chip module to create a second configuration file; transmitting second configuration file type information to the chip module and linking the second configuration file type information with an initial configuration file to generate a typed second configuration file; requesting second configuration file data from a configuration file providing unit; transmitting the second configuration file data to a configuration file management unit through the configuration file providing unit; transmitting the second configuration file data to the chip module through the configuration file management unit; and linking the second configuration file data with a typed second configuration file to generate a modified second configuration file.

[0045] To create a modified second configuration file based on the same initial configuration file, the method is to first send an instruction to the chip module to create the second configuration file, followed by sending the second configuration file type information and the second configuration file data that define the second configuration file.

[0046] The chip module described herein can store multiple configuration files, which can have different configuration file types; that is, each configuration file has one configuration file type, and multiple different configuration file types are available for selection. The configuration file type is determined by the transmitted configuration file type information.

[0047] In another embodiment, the method further includes the steps of: selecting a configuration file from the configuration file storage space of the chip module; and running the chip module according to the selected configuration file.

[0048] A chip module can contain multiple configuration files in its configuration file storage space. The number of configuration files is limited only by the size of the configuration file storage space.

[0049] Preferably, a new configuration file can be created in the chip module at any time. This is achieved by sending the corresponding instructions, configuration file type information, and configuration file data to the chip module after it already contains one or more configuration files. A configuration file can be selected from those contained in the configuration file storage space to run the chip module using that configuration file. This selected configuration file can also be referred to as the active configuration file.

[0050] According to another aspect, a chip module is provided. This chip module is designed to hold multiple optional configuration files. The chip module has a processor, memory, and a communication interface. The chip module is designed to receive an initial configuration file, configuration file type information, and configuration file data via the communication interface. The processor is designed to store the initial configuration file, configuration file type information, and configuration file data as configuration files in the memory, and to generate modified configuration files based on the initial configuration file, configuration file type information, and configuration file data. The memory is configured to contain multiple modified configuration files (at least two modified configuration files may have the same configuration file type or different configuration file types). The chip module is designed to operate using the initial configuration file in a first operating mode, using the modified first configuration file in a second operating mode, or using the modified second configuration file in a third operating mode.

[0051] The chip module described herein can be configured using the methods described herein. The chip module can run using an initial configuration file, or it can run using multiple modified configuration files contained in memory.

[0052] According to another aspect, a device having a communication module and a chip module is provided, wherein the chip module is an embodiment of the chip module described herein. The chip module is associated with the communication module, and the chip module enables the communication module to access communication services via at least one configuration file. The device has a configuration file management unit designed to receive configuration file type information and configuration file data from a configuration file providing unit. The configuration file management unit is designed to forward the configuration file type information and configuration file data, such that a modified configuration file is generated and stored in the memory of the chip module based on the initial configuration file, the configuration file type information, and the configuration file data.

[0053] This aspect describes the chip module described above within the context of a device having a communication module. This chip module, within the communication module, is used to obtain or generate one or more configuration files, and enables the use of communication services through the communication module.

[0054] The device may be, for example, a smartphone or other personal device used by a human user and accessing communication services. However, the device may also be other networked devices that use a communication module to receive and send data, such as sensors, medical devices, control devices, entertainment devices, etc.

[0055] For details relating to the chip module and the methods for configuring it, see the corresponding description. The features and functions of the chip module and the methods for configuring it are not repeated here, but these features and functions also apply to the chip module in the context of the device described herein. The device is specifically designed to perform the methods described herein or the steps of those methods. The steps of the methods mentioned can be implemented as functions of the device, and these steps are not explicitly repeated here.

[0056] The initial configuration file can be transmitted to the chip module without involving the configuration file management unit. The configuration file management unit obtains the configuration file type information and configuration file data, and then generates a modified configuration file based on these and the initial configuration file.

[0057] In one embodiment, the configuration file management unit has a first submodule and a second submodule, wherein the first submodule is designed to process configuration files of a first configuration file type, and the second submodule is designed to process configuration files of a second configuration file type.

[0058] However, the configuration file management unit can also have more than two submodules, each designed to handle a specific configuration file type. One submodule can handle configuration files of the first configuration file type, such as the initial configuration file, SGP.22 configuration file, or SGP.32 configuration file. Another submodule can handle configuration files of the second configuration file type (such as the initial configuration file, SGP.22, or SGP.32).

[0059] Therefore, the first submodule is the so-called FPA (Factory Profile Assistant), the second submodule is the so-called LPA (Local Profile Assistant), and the third submodule is the so-called IPA (IoT Profile Assistant).

[0060] The configuration file management unit implements two sub-modules, thus handling two different configuration file types. Depending on the configuration file type, when a configuration file of type one or two is written to the chip module, the first or second sub-module executes the corresponding steps. Similarly, the first or second sub-module requests configuration file data from the configuration file providing unit based on the configuration file type. Upon receiving the configuration file data, it preprocesses the data and transmits it to the memory in the chip module. In terms of basic functionality, the first and second sub-modules operate in the same way; however, the first sub-module responds through the local activation module, while the second sub-module responds through the remote access unit.

[0061] In another implementation, the configuration file management unit is a functional module that executes in the device or on the chip module.

[0062] Depending on the computing power available in the chip module, the configuration file management unit can be a software-implemented module executed by the chip module's processor. However, it is also conceivable to provide the configuration file management unit as a separate functional module within the device.

[0063] In another embodiment, the device has an activation module. The activation module is a local functional module executed on the device and is designed to accept user input and, based on the input, send a message to a first submodule, thereby triggering the transmission of configuration file data of a first configuration file type to the chip card. Alternatively, a second submodule is designed to receive a message from a remote access unit, thereby triggering the transmission of configuration file data of a second configuration file type to the chip card.

[0064] The activation module is, for example, an application or program running on the device. The activation module enables the device user to load configuration file data of a first configuration file type, such as a configuration file according to SGP.22, onto the chip module. The activation module outputs information indicating that the configuration file to be loaded is a first configuration file type, causing the chip module to associate the configuration file with the matching configuration file type. When the configuration file is activated, the chip module and the device will operate in the corresponding operating mode.

[0065] When configuration data of a second configuration file type, such as a configuration file according to SGP.32, needs to be loaded onto the chip module, this is initiated by the remote access unit by sending a corresponding command to the second submodule of the configuration file management unit. The second submodule generates and outputs a corresponding message so that the chip module is ready to transmit the configuration file data of the second configuration file type. Furthermore, the second submodule can retrieve configuration file data from the configuration file providing unit and forward this configuration file data to the chip module's memory. In the chip module, the corresponding data is marked to associate it with the configuration file type, and when the configuration file of the second configuration file type is activated, the chip module and the device operate in a second operating mode.

[0066] In summary, the methods, chip modules, and devices described herein enable the initial configuration of a chip module, allowing it to establish basic connectivity with a communication network. In subsequent steps, the chip module can be categorized and modified, both temporally and spatially, in a manner separate from the first step of transmitting the initial configuration to the chip module. After categorization and modification, the chip module can be reset to the initial configuration and re-categorized and modified to receive configuration type information for other configuration types and personalized configuration data for other users. Multiple configuration files of different types can be stored on a single physical chip module, and these configuration files can be selectively activated. The chip module and device can operate in a first operating mode using the initial configuration, or in a second or third operating mode depending on the configuration type of the activated configuration file (or multiple activated configuration files). Therefore, the steps necessary for modifying the chip module using the configuration file can be executed at different times. In particular, it is no longer necessary to transmit all configuration file data wirelessly and simultaneously, simplifying the process of transmitting the information required for the configuration file.

[0067] References to SGP.22 and SGP.32 are merely illustrative. It should be understood that the methods, chip modules, and devices described herein can also operate using configuration files according to other standards. Attached Figure Description

[0068] The following is a more detailed description of some details with reference to the accompanying drawings. These drawings are schematic and not to scale. The same reference numerals indicate the same or similar elements. In the accompanying drawings:

[0069] Figure 1 A schematic diagram of the chip module is shown;

[0070] Figure 2 A schematic diagram of the components involved in transmitting a configuration file to a chip module is shown;

[0071] Figure 3 A schematic diagram illustrating message exchange when receiving configuration file data for different configuration file types is shown;

[0072] Figure 4 A schematic diagram of the chip module is shown;

[0073] Figure 5 A schematic diagram of a device having a communication module and a chip module configured by a device management unit is shown;

[0074] Figure 6 A schematic diagram illustrates the steps of a method for configuring a chip module using a configuration file. Detailed Implementation

[0075] Figure 1 Chip module 10 is shown. Chip module 10 includes a processor 12 and a memory 14. Memory 14 is, for example, non-volatile memory. The processor 12 is designed to execute instructions, specifically instructions stored in memory 14. Furthermore, chip module 10 has a communication interface 16. Data can be written to memory 14 via communication interface 16.

[0076] Figure 2 The components involved are schematically shown when configuring the chip module using a configuration file and when transmitting data for the configuration file to the chip module 10.

[0077] First, the configuration file providing unit 30 provides each configuration file, and each configuration file can reach the chip module 10 through different paths. For example, the configuration file providing unit 30 provides one or more initial configuration files to the device management unit 110 of the manufacturer of the device with the chip module. Then, the device management unit 110 transmits the initial configuration file to the chip module, as will be further described below. The configuration file providing unit 30 transmits configuration file type information and / or configuration file data to the configuration file management unit 20, and then the configuration file management unit 20 transmits it to the chip module.

[0078] The device management unit 110 transmits the initial configuration file to the chip module 10 and stores the initial configuration file in the configuration file storage space 50 in the memory 14. This can be, for example, the chip module 10 or a device 100 containing the chip module 10 (see [link]). Figure 5 As part of the manufacturing process, for example, using a wired connection between device management units 110, the initial configuration file is written to memory 14 in a wired manner. Device management unit 110 may be, for example, a configuration computer.

[0079] Device management unit 110 can call one or more initial configuration files from configuration file providing unit 30 and use the initial configuration files for the chip module accordingly. Device management unit 110 can also determine which configuration file type the configuration file contains in one step, but this can also be determined at a later point in time.

[0080] After the initial configuration file is transmitted to the chip module, a modified configuration file can be created. This is achieved by the configuration file providing unit 30 transmitting configuration file type information and configuration file data to the chip module 10 via the configuration file management unit 20, and then using this data to create the modified configuration file based on the initial configuration file. For example, the transmission of configuration file type information to the chip module can also be performed by the device management unit, initiated by the device management unit, or initiated by the device user when the device is put into operation. In particular, the step of transmitting the configuration file type information can be performed after the device has been delivered to the user or organization, for example, after the device manufacturing process is completed.

[0081] After linking the configuration file type information with the initial configuration file, the configuration file activation unit 40, such as a user-operated application or remote access unit, sends a message to the configuration file management unit 20. The configuration file management unit 20 queries the configuration file providing unit 30 for configuration file data. In this query, the configuration file management unit 20 may transmit information indicating the configuration file data to be provided to the configuration file providing unit 30. The configuration file providing unit 30 sends the configuration file data to the configuration file management unit 20. During transmission to the chip module 10, an encryption mechanism can be used to protect the configuration file data from unauthorized access.

[0082] The chip module 10 is placed into receive mode by a message from the configuration file management unit 20. After receiving configuration file data from the configuration file providing unit 30, the configuration file management unit 20 can perform some processing or preparation steps on the configuration file data. Then, the configuration file management unit 20 transmits the configuration file data to the chip module 10.

[0083] The chip module 10 links the initial configuration file, configuration file type information, and configuration file data received from the configuration file management unit 20, thereby forming a modified configuration file, and saves the modified configuration file in the configuration file storage space 50 in the memory 14.

[0084] The configuration file providing unit 30 is, for example, a service provider, such as a central entity of a mobile radio network operator. The configuration file providing unit 30 may be, for example, a so-called SM-DP+ unit (Subscription Manager - Data Preparation unit) as defined in the GSMA protocol. Typically, after the chip module is delivered to the user along with a device that has or can have the chip module installed, the SM-DP+ transfers the configuration file to the chip module. In this case, the configuration file is transferred to the chip module "online," because it is transferred to the chip module after the device is delivered and put into operation.

[0085] In another implementation, the configuration file providing unit 30 can also be a so-called SM-DPf unit (Subscription Manager - Data Preparation factory), which provides configuration files to the manufacturer of the device and / or chip module so that these configuration files are stored on the chip module during the manufacturing phase of the device and / or chip module. In this case, the configuration files are transferred to the chip module "offline" because they are transferred to the chip module during the manufacturing process, i.e., before being put into operation. In the scenario described here, the initial configuration file is transferred to the chip module offline, while the modified configuration file is transferred to the chip module online.

[0086] Although Figure 2 The diagram illustrates a single configuration file providing unit 30 capable of both online and offline configuration file transfer. However, these functions can also be separated into distinct configuration file providing units, where a first configuration file transfer unit (offline) provides the initial configuration file, while a second configuration file transfer unit (online) provides the configuration file type information and configuration file data for the modified configuration file. The modified configuration file could, for example, be a configuration file based on SGP.22 or SPG.32.

[0087] The configuration file management unit 20 is a local module implemented on the off-center device 100 or chip module 10. When transmitting configuration file type information and configuration file data online, the configuration file management unit 20 obtains the configuration file data from the configuration file providing unit 30 and transmits it to the chip module 10.

[0088] The configuration file management unit 20 specifically implements the functions of FPA (Factory Configuration File Assistant), LPA (Local Configuration File Assistant), and / or IPA (IoT Configuration File Assistant, where IoT refers to the Internet of Things). The configuration file management unit 20 is also specifically used to handle the transmission of configuration file data from the configuration file providing unit 30 to the chip module 10. For example, the configuration file management unit 20 can temporarily store configuration file data and then transmit the configuration file data to the chip module 10 in a format that allows the configuration file data to be transmitted.

[0089] During the transmission of the configuration file from the configuration file providing unit 30 to the configuration file management unit 20 and the chip module 10, when the initial configuration file is transmitted in offline mode, the device management unit 110 can assume the function of the configuration file management unit 20.

[0090] Figure 3The illustration schematically shows the exchange of a portion of messages and information for different configuration file types, wherein, in Figure 3 The diagram does not show the transfer of the initial configuration file to the chip module; the transfer of the initial configuration file to the chip module can be achieved from... Figure 2 I saw it in the middle. Figure 3 In particular, the steps for transferring configuration file data of different configuration file types to the chip module are shown.

[0091] exist Figure 3 The diagram shows two branches for different configuration file types. The left side shows the flow for the first configuration file type (e.g., SGP.22, indicated by the letter A in the figure), and the right side shows the flow for the second configuration file type (e.g., SGP.32, indicated by the letter B in the figure).

[0092] The generation of the modified configuration file of the first configuration file type involves activation module 40A, which requests configuration file data of the configuration file of the first configuration file type from the first sub-module 20A of configuration file management unit 20 using message 61A. Now, the first sub-module 20A sends message 62A to chip module 10. Message 62A points to the configuration file of the first configuration file type (e.g., SGP.22) and instructs chip module 10 to create a first configuration file 50A in memory 14 based on the initial configuration file, configuration file type information, and configuration file data. The first sub-module 20A requests configuration file data from configuration file providing unit 30 using message 63A. Configuration file providing unit 30 sends the configuration file data to chip module 10 using message 64A. This configuration file data in message 64A is associated with the first configuration file 50A.

[0093] The transmission and generation of a configuration file of the second configuration file type are triggered by the remote access unit 40B. The remote access unit 40B requests configuration file data for the second configuration file type from the second submodule 20B of the configuration file management unit 20 using message 61B. Now, the second submodule 20B sends message 62B to the chip module 10. Message 62B points to the configuration file of the second configuration file type (e.g., SGP.32) and instructs the chip module 10 to create a second configuration file 50B in memory 14 based on the initial configuration file, configuration file type information, and configuration file data. The second submodule 20B requests configuration file data from the configuration file providing unit 30 using message 63B. The configuration file providing unit 30 sends the configuration file data to the chip module 10 using message 64B. This configuration file data in message 64B is associated with the second configuration file 50B.

[0094] Currently, chip module 10 contains two configuration files 50A and 50B with different configuration file types. Chip module 10 can operate using configuration files of different configuration file types because the configuration file management unit 20 can handle different configuration file types accordingly and store the configuration files in the memory 14 of chip module 10 with corresponding descriptions of the configuration file types. Configuration files 50A and 50B can be selectively activated, and chip module 10 can operate in the corresponding operating mode.

[0095] It is also conceivable that chip module 10 contains only one configuration file, and for each change in the configuration file type and / or configuration file data, the typing and / or modification process is re-executed to generate a matching modified configuration file for the desired use of the device. The modified configuration file is generated based on the initial configuration file and the corresponding requested configuration file type information and configuration file data, wherein the initial configuration file is preferably retained in the chip module and forms the basis for the typing and modification of future configuration files.

[0096] Arrows 61A / B, 62A / B, 63A / B, and 64A / B should not be forcibly interpreted as a direct reproduction of the message exchange path. Instead, these arrows indicate from which entity sent the message and from which entity received it. The path for receiving the message may also be... Figure 3 The schematic diagrams are different. Therefore, configuration file data can be transmitted from the configuration file provider unit 30 to the chip module 10 via different paths.

[0097] In the first variation, configuration file data is sent from configuration file providing unit 30 to configuration file management unit 20. Configuration file management unit 20 receives the configuration file data, temporarily stores it, and prepares to further transmit it to chip module 10, for example, using other protocols. In the second variation, configuration file data is sent directly from configuration file providing unit 30 to chip module 10. In this second variation, the functions of configuration file management unit 20, which has first submodule 20A and second submodule 20B, can be implemented on chip module 10 and, in principle, can perform the same tasks as in the first variation. In the third variation, configuration file data is sent from configuration file providing unit 30 to configuration file activation unit 40, from there to configuration file management unit 20, and then from configuration file management unit 20 to chip module 10. In the fourth variation, configuration file data is sent from configuration file providing unit 30 to configuration file activation unit 40, and from there to chip module 10. In some or all of these four variations, configuration file data can be transmitted between configuration file providing unit 30 and chip module 10 via an end-to-end encrypted data transmission connection.

[0098] Figure 4 A chip module 10 is shown, having a memory 14 and three configuration files 50I, 50A, and 50B stored therein. Each configuration file is constructed identically in principle and contains at least the following information: a unique configuration file number 51, configuration file type information 52, and configuration file data 53. Configuration file 50I corresponds to the initial configuration file, 50A schematically shows a modified first configuration file, and 50B shows a modified second configuration file. Configuration files 50A and 50B are based on the initial configuration file 50I, but differ from the initial configuration file 50I in, for example, in the configuration file type information 52 and the configuration file data 53. This means that the modified configuration files 50A and 50B can have different configuration file types and can also contain different configuration file data. Each configuration file 50I, 50A, and 50B can have a unique configuration file number 51. The configuration file can be selected and activated using this unique configuration file number. The modified second configuration file 50B is constructed in principle similarly to the modified first configuration file 50A. The second configuration file 50B is also based on the initial configuration file 50I. The modified first configuration file 50A is created based on the initial configuration file 50I. For example, not only for the modified first configuration file 50A, but also for the modified second configuration file 50B, different configuration file type information and different configuration file data are used.

[0099] Despite Figure 4The initial configuration file 50I is shown, and only two modified configuration files 50A and 50B are shown. However, it should be understood that the number of configuration files stored in memory 14 is limited only by the available storage space in memory 14.

[0100] The initial configuration file 50I can be stored in a separate storage area. The initial configuration file 50I forms the standard configuration file used to configure the chip module before it is typed and modified. This initial configuration file can then be used as the basis for other configuration files. When generating a personalized configuration file based on the initial configuration file, the information in field 52 (configuration file type information) and field 53 (configuration file data) is typically replaced or overridden.

[0101] Figure 5 A schematic diagram of a device 100 having a communication module 105 is shown, wherein the device 100 is communicatively connected to a device management unit 110.

[0102] Communication module 105 is associated with chip module 10 according to one of the examples described above to transmit an initial configuration file to chip module 10. Chip module 10 enables registration of communication module 105 in a communication network and the reception and transmission of data through the communication network.

[0103] The device 100 can be a user's personal device, such as a smartphone, or it can be a networked device that does not directly interact with the user, such as an IoT device. The IoT device can perform any function and transmit collected or received values ​​so that it can then perform actions based on the received values.

[0104] The chip module and method described herein enable the execution of steps for transferring a configuration file to the chip module during the manufacturing of the chip module or a device having the chip module, thereby reducing the complexity, overhead, and scope of data transfer during the configuration file's operation. Thus, the device can initially operate using an initial configuration file, and before this configuration file is typed using an optional configuration file type (e.g., according to SGP.22 and / or SGP.32) and modified for a specific user, the device already has access to the communication network.

[0105] Figure 6 Method 200, having steps 201 to 207, is schematically illustrated. This method reflects the combination of Figures 1 to 5 The described function.

[0106] In step 201, the initial configuration file is transmitted to the chip module. In step 202, the initial configuration file is stored in the chip module's memory. In step 203, configuration file type information is transmitted to the chip module, and the configuration file type information is linked with the initial configuration file to generate a typed configuration file. In step 204, configuration file data is requested from the configuration file providing unit. In step 205, the configuration file providing unit transmits the configuration file data to the configuration file management unit. In step 206, the configuration file management unit transmits the configuration file data to the chip module. In step 207, the configuration file data is linked with the typed configuration file to generate a modified configuration file.

[0107] In addition, it should be noted that "comprising" or "having" does not exclude other elements or steps, and "a" or "an" does not exclude multiple. Furthermore, it should be noted that a feature or step described with reference to one of the above embodiments may also be used in combination with other features or steps of some of the embodiments described above. Reference numerals in the claims should not be considered limiting.

[0108] List of reference numerals

[0109] 10. Chip modules (cards or electronic components)

[0110] 12 processors

[0111] 14 memory

[0112] 16 communication interfaces

[0113] 20 Configuration File Management Units (FPA, LPA, IPA)

[0114] 20A First Submodule (FPA, LPA, or IPA)

[0115] 20B Submodule 2 (FPA, LPA, or IPA)

[0116] 30 Configuration File Provider Unit (SM-DP)

[0117] 40 Configuration File Activation Units (End User, eIM)

[0118] 40A Activation Module

[0119] 40B Remote Access Unit

[0120] 50 configuration file storage space

[0121] 50I Initial Configuration File

[0122] 50A First Configuration File

[0123] 50B Second Configuration File

[0124] 51 Configuration File Number

[0125] 52 Configuration File Type Information

[0126] 53 Configuration File Data

[0127] 61 Request configuration file data

[0128] 62. Create configuration file space

[0129] 63 Request configuration file data

[0130] 64 Transfer configuration file data

[0131] 100 devices

[0132] 105 communication module

[0133] 110 Equipment Management Unit

[0134] 200 methods

[0135] Methods and steps 201-207

Claims

1. A method (200) for configuring a chip module (10) using a configuration file, the method comprising the following steps: The initial configuration file (50I) is transmitted (201) to the chip module (10). The initial configuration file (50I) is stored (202) in the memory (14) of the chip module (10); The configuration file type information (52) is transmitted (203) to the chip module (10), and the configuration file type information (52) is linked with the initial configuration file (50I) to generate a typed configuration file; Request (204) configuration file data (53) from the configuration file providing unit (30); The configuration file data (53) is transmitted (205) to the configuration file management unit (20) through the configuration file providing unit (30). The configuration file management unit (20) transmits (206) the configuration file data (53) to the chip module (10). The configuration file data (53) is linked with the typed configuration file (207) to generate the modified configuration file.

2. The method (200) according to claim 1. in, Before putting the chip module (10) into operation, the initial configuration file (50I) is stored in the memory (14) of the chip module (10).

3. The method (200) according to claim 1 or 2. in, Storing the initial configuration file (50I) in the memory (14) of the chip module (10) and transmitting the configuration file type information (52) to the chip module (10) are performed separately from each other.

4. The method (200) according to any one of the preceding claims. in, After the chip module (10) is put into operation, the configuration file type information (52) is transmitted to the chip module (10).

5. The method (200) according to any one of the preceding claims. in, The initial configuration file (50I) is transmitted to the chip module (10) via a wired connection.

6. The method (200) according to any one of the preceding claims. in, The configuration file data (53) is transmitted to the configuration file management unit (20) via a wireless connection through the configuration file providing unit (30).

7. The method (200) according to any one of the preceding claims, further comprising: The configuration file type information (52) is removed from the modified configuration file to generate a reset configuration file.

8. The method (200) according to claim 7, further comprising: The modified configuration file type information (52) is transmitted to the chip module (10), and the modified configuration file type information is linked with the reset configuration file to regenerate the typed configuration file.

9. The method (200) according to any one of the preceding claims, further comprising: Send instructions to the chip module (10) to create a second configuration file; The second configuration file type information is transmitted to the chip module (10), and the second configuration file type information is linked with the initial configuration file (50I) to generate a typed second configuration file; Request second configuration file data (53) from the configuration file providing unit (30); The second configuration file data (53) is transmitted to the configuration file management unit (20) through the configuration file providing unit (30). The second configuration file data (53) is transmitted to the chip module (10) through the configuration file management unit (20). The second configuration file data (53) is linked with the typed second configuration file to generate the modified second configuration file.

10. The method (200) according to claim 9, further comprising: Select a configuration file (50A, 50B) from the configuration file storage space (50) of the chip module (10); The chip module (10) is run according to the selected configuration file (50A, 50B).

11. A chip module (10) for holding multiple selectively usable profiles (50A, 50B), the chip module (10) comprising: Processor (12); Memory (14); Communication interface (16); The chip module (10) is designed to receive an initial configuration file (50I), configuration file type information (52), and configuration file data (53) through the communication interface (16). The processor (12) is designed to store the initial configuration file (50I), the configuration file type information (52), and the configuration file data (53) as configuration files (50A, 50B) in the memory (14), and to generate a modified configuration file based on the initial configuration file, the configuration file type information, and the configuration file data. The memory (14) is configured to contain multiple modified configuration files (50A, 50B). The chip module (10) is designed to run in a first operating mode using the initial configuration file (50I), in a second operating mode using the modified first configuration file (50A), or in a third operating mode using the modified second configuration file (50B).

12. A device (100) having a communication module (105) and a chip module (10) according to claim 11. in, The chip module (10) is associated with the communication module (105), and the chip module (10) enables the communication module (105) to access communication services through at least one configuration file; The device (100) has a configuration file management unit (20) which is designed to receive configuration file type information and configuration file data (53) from the configuration file providing unit (30). The configuration file management unit (20) is designed to forward the configuration file type information (52) and the configuration file data (53), so that the modified configuration files (50A, 50B) are generated and saved in the memory (14) of the chip module (10) based on the initial configuration file, the configuration file type information and the configuration file data.

13. The device (100) according to claim 12. in, The configuration file management unit (20) has a first submodule (20A) and a second submodule (20B); The first submodule (20A) is designed to process configuration files of the first configuration file type; The second submodule (20B) is designed to process configuration files of the second configuration file type.

14. The device (100) according to claim 12 or 13. in, The configuration file management unit (20) is a functional module that is executed in the device (100) or on the chip module (10).

15. The device (100) according to any one of claims 12 to 14. The device has an activation module (40A), which is a local functional module executed on the device (100) and is designed to accept user input and send a message to the first submodule (20A) based on the input, thereby triggering the transmission of configuration file data of a first configuration file type to the chip card; or in, The second submodule (20B) is designed to receive a message from the remote access unit (40B), thereby triggering the transmission of configuration file data of the second configuration file type to the chip card.

Images