Method of configuring a network device, and communication module and network device comprising the method
Patent Information
- Application Number
- CN202580023705.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-03-26
- Filing Date
- 2025-03-24
- Publication Date
- 2026-10-27
AI Technical Summary
然而,由于可部署性和可用性限制,可能并不总能确保应用程序以及安全元件具有相同来源或对应版本
Smart Images

Figure CN122996632A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of authenticating applications, such as Local Profile Assistants (LPAs) and / or Internet of Things (IoT) Profile Assistants (IPAs) for interacting with secure elements of network devices, such as embedded universal integrated circuit cards (eUICCs). Specifically, this disclosure relates to a method for configuring a network device, a communication module configured to communicate via a telecommunications network and including a secure element (such as an eUICC), and a network device configured to communicate via a telecommunications network and including a secure element (such as an eUICC). Background Technology
[0002] Prior art knows of network devices such as personal mobile devices or IoT devices configured to use electronic subscriber profiles for communication over mobile networks. Such network devices are typically equipped with an electronic / embedded secure element (SE, eSE), such as UICC, eUICC, iUICC, SIM, eSIM, or iSIM, configured to store one or more electronic subscriber profiles that allow the network device to connect to one or more mobile networks. The subscriber profile (e.g., an eSIM profile) may be generated by a mobile network operator (MNO) and may be stored (e.g., downloaded to) the mobile network device. The subscriber profile can then be installed on the secure element of the network device and used by the network device for communication over the corresponding mobile network.
[0003] Corresponding applications, such as LPAs and / or IPAs, assist in the storage, installation, and management of subscriber profiles. Therefore, LPAs and / or IPAs are functional elements in network devices or SEs, providing Local Profile Download (LPD), Local Discovery Service (LDS), and Local User Interface (LUI) capabilities. When LPAs and / or IPAs are located in a device, they are referred to as LPAd, LPDd, LUId, or LDSd. When LPAs are located in an eUICC, they are referred to as LPAe, LPDe, LUIe, or LDSe. The use of LPA, LPD, LDS, or LUI applies to the element, regardless of whether the element is located in a device or an eUICC.
[0004] Typically, the LPA service provides the necessary access to the services and data required for the LPA's functionality. These services may include: providing configuration file packet transfer from the LPA to the ISD-P, a list of installed configuration files, retrieving SE identifiers (such as the so-called EID), and other local configuration file management operations. The IPA service provides the necessary access to the services and data required for the IPA's functionality. These services may include: providing the address of the root SM-DS and (if configured) the address of the default SM-DP+, transferring binding configuration file packets from the IPAd to the ISD-P, a list of installed configuration files and their configuration file metadata, retrieving the EID, and providing configuration file status management operations, eUICC execution results, and notifications.
[0005] For example, WO 2023 / 017031 A1 relates to a method, interface, and sending device for delegated management of profiles of an eUICC included in a mobile device. Delegated management of a selected profile is provided by registering the eUICC with a server and adding a profile selected from a list of profiles available from the eUICC to an existing profile subscription group on the server, or by creating a new subscription group on the server based on the selected profile.
[0006] WO 2021 / 047765 A1 describes a mechanism for processing configuration files of a batch of identity modules. Each identity module in this batch has credentials for securely installing the configuration file. One method is performed by the LPA of the agent device. The LPA includes credentials for downloading the configuration file. These credentials include a certificate. These credentials enable the LPA to act as a virtual identity module. Another method is performed by a subscription management entity. Yet another method is performed by the identity modules within this batch of identity modules.
[0007] As described above, according to existing technologies, methods for handling applications (such as LPAs and IPAs), subscriber profiles, and the associated system architecture (e.g., the operating system (OS)) of network devices may not fully meet all requirements regarding deployability and availability, nor may they fully meet all requirements regarding functional safety and security. For example, to ensure functional safety and security, it is desirable for the application and security element to have the same source and preferably the same development status. However, due to deployability and availability limitations, it may not always be possible to ensure that the application and security element have the same source or corresponding version. This can compromise functional safety and security when operating the device, and may even lead to the device failing to be configured correctly. Summary of the Invention
[0008] Improving the interaction between applications and secure elements can be considered an objective. Specifically, providing a way of processing applications and secure elements can therefore be considered an objective, ensuring functional safety and security without compromising deployability and availability. These objectives are achieved, at least in part, through the subject matter of the independent claims.
[0009] According to one aspect, a method for configuring a network device is provided, the method comprising the steps of: providing an application, particularly an LPA and / or an IPA, adapted to interact with a security element (such as eUICC) of the network device; and utilizing the security element to check an authentication certificate for authenticating the origin of a local application.
[0010] According to one aspect, a communication module configured to communicate via a telecommunications network is provided, the communication module including a security element, such as an eUICC, the security element being configured to check the source of an authentication certificate for an application, particularly an LPA and / or IPA, and being adapted to interact with the security element.
[0011] According to one aspect, a network device configured to communicate via a telecommunications network is provided, the network device including a security element, such as eUICC, the security element being configured to check authentication certificates used to authenticate the source of an application, particularly an LPA and / or IPA, and being adapted to interact with the security element.
[0012] The proposed solution offers the following advantages over existing technologies: Authenticating the application's origin helps verify and thus ensures that the application comes from a trusted vendor or supply chain. This guarantees reliable interaction between the application and the secure element to a degree that the application from a specific source can be specifically designed, tested, and its architecture verified to function with the appropriate type of secure element. By having the secure element check the authentication certificate, the authentication process itself becomes highly secure and can be performed during the setup phase when the network device's communication capabilities are limited, or even offline before the network device is enabled to communicate via the communication network.
[0013] Furthermore, for example, version control can be performed during the process of authenticating the application's origin to ensure the existence of appropriate versions of the application and / or security elements. In other words, the step of checking authentication certificates can be part of a routine used to configure network devices to enable them to communicate over telecommunications networks. This helps to handle applications and security elements in a way that ensures functional security and safeguards without compromising deployability and availability.
[0014] Further developments can be derived from the dependent claims and the following description. Features described with reference to communication modules, network devices, and components thereof can be implemented as method steps, and vice versa. Therefore, the description provided in the context of communication modules, network devices, and components thereof is also applicable to the corresponding methods in a similar manner. Specifically, the features and functions of communication modules, network devices, and components thereof can be implemented as method steps, and these method steps can in turn be implemented as corresponding device features or functions.
[0015] According to one possible embodiment of the method, the method further includes the step of issuing an authentication certificate to the secure element. This authentication certificate may be issued and / or provided by a trusted entity. The issuer and / or manufacturer of the secure element may act as and / or control the trusted entity. This further facilitates handling the application and secure element in a manner that ensures functional safety and security without compromising deployability and availability.
[0016] According to one possible embodiment of the method, the method further includes the step of providing an authentication certificate to the network device via a telecommunications network. The authentication certificate may be sent from a trusted entity, such as from a corresponding server device controlled by the trusted entity, for receipt by the network device. This further facilitates handling applications and security elements in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0017] According to one possible embodiment of the method, the method further includes the step of passing an authentication certificate from the application to the secure element. The authentication certificate may be passed to the secure element via a corresponding application programming interface (API) that ensures proper interaction of the application at the secure element. This further facilitates handling the application and the secure element in a manner that ensures functional safety and security without compromising deployability and availability.
[0018] According to one possible embodiment of the method, the method further includes the step of storing the authentication certificate in the secure element. The secure element can provide secure memory space, for example, as part of non-volatile memory implemented within the secure element. This further facilitates handling the application and the secure element in a manner that ensures functional safety and security without compromising deployability and availability.
[0019] According to one possible embodiment of the method, the method further includes the step of obtaining an identifier from the secure element. This identifier can help verify the origin of the secure element. This further facilitates handling the application and secure element in a manner that ensures functional safety and security without compromising deployability and availability.
[0020] According to one possible embodiment of the method, the identifier is a unique device identifier for the secure element. Therefore, an authentication process can be performed separately for each unique secure element. This further facilitates handling applications and secure elements in a manner that ensures functional safety and security without compromising deployability and availability.
[0021] According to one possible embodiment of the method, the method further includes the step of requesting the security element to check the authentication certificate. This allows the authentication process to be initiated at a desired time or state when configuring the network device. This further helps to handle applications and security elements in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0022] According to one possible embodiment of the method, the step of checking the authentication certificate involves determining whether the authentication certificate exists. Based on the presence or absence of the authentication certificate, certain configurations of the network device can be performed and / or selected. This further helps to handle applications and security elements in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0023] According to one possible embodiment of the method, the method further includes the steps of: enabling at least one function of the application if an authentication certificate exists, or disabling at least one function of the application if an authentication certificate does not exist. This also allows for the execution and / or selection of certain configurations of the network device. This further facilitates handling the application and security elements in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0024] According to one possible embodiment of the method, the inspection step involves assessing the validity of the application certificate. To assess the validity of the application certificate, the certificate signature can be checked. This certificate signature may be issued and / or provided by a trusted entity. This further helps to handle applications and secure components in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0025] According to one possible embodiment of the method, the method further includes the steps of: enabling at least one function of the application if the authentication certificate is valid, or disabling at least one function of the application if the authentication certificate is invalid. This also allows for the execution and / or selection of certain configurations of the network device. This further facilitates handling the application and security elements in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0026] According to one possible embodiment of the method, the method further includes the step of rejecting a response from the secure element to the application if the authentication check indicates a certificate problem. This prevents unauthorized combinations of the application and the secure element. This further helps to handle the application and secure element in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0027] According to one possible embodiment of the method, the method further includes a step of returning the result of the step of checking the authentication certificate to a trusted entity. The trusted entity may be the issuer of the authentication certificate. The result will be sent to the appropriate server device. This further helps to handle applications and secure elements in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0028] According to one possible embodiment of the method, the method further includes the following steps: if the authentication check step indicates a certificate problem, then taking action. The trusted entity may take this action. This action may involve obtaining data about network devices and / or security elements. This data may be provided to the provider offering the telecommunications network and / or access to the telecommunications network. This further facilitates handling applications and security elements in a manner that ensures functional security and safeguards without compromising deployability and availability.
[0029] According to one possible embodiment of the network device, the network device includes a storage unit containing applications. For example, the applications may be stored in a dedicated memory space within the storage unit. This further facilitates handling applications and security elements in a manner that ensures functional safety and security without compromising deployability and availability.
[0030] According to one possible embodiment of the network device, the application is configured to process at least one subscriber profile of a subscriber of the telecommunications network. Therefore, any desired or required profile management functions can be performed using this application. This further contributes to improving the functional security and assurance of the network device.
[0031] According to one possible embodiment of the network device, the network device is configured to be associated with at least one of a personal entity and a machine entity. The personal entity may involve a personal mobile device, such as a smartphone, smartwatch, etc. The machine entity may involve an Internet of Things (IoT) device suitable for communication via a telecommunications network, such as a multimedia device, camera, speaker, home appliance, vehicle, vending machine, etc. This further contributes to improving the functional security and assurance of personal or machine communication, respectively.
[0032] A computer program may include instructions that, when executed by a computing device, cause the computing device to perform a method, control a communication module, a network device, and / or a server device to execute any step of the method described herein. Specifically, the computer program may include instructions that, when executed by a network device configured to communicate via a telecommunications network, cause a security element (e.g., eUICC) of the network device to examine, using the security element, an authentication certificate for the source of an application, particularly an LPA, adapted to interact with the security element. The computer program may be carried by a computer-readable data carrier (e.g., a computer-readable medium and / or a data carrier signal). Attached Figure Description
[0033] Figure 1 This is a schematic diagram of an authentication system for authenticating applications according to the method of the present invention.
[0034] Figure 2 yes Figure 1 The diagram shows the communication hierarchy of the components involved in the authentication system. Detailed Implementation
[0035] The following detailed description is exemplary in nature only and is not intended to limit the invention or its uses. Furthermore, it is not intended to be limited by the foregoing background art or any theory set forth in the following detailed description. The representations and illustrations in the drawings are schematic and not drawn to scale. The same reference numerals denote the same elements. A deeper understanding of the described subject matter can be obtained by reviewing these illustrations in conjunction with the following detailed description.
[0036] Figure 1 A schematic diagram of an authentication system 1 is shown, comprising a computer device 2 (e.g., a server device controlled by a trusted entity T) and a network device 3. The network device 3 may take the form of a personal mobile device (such as a smartphone, smartwatch, etc.) to be associated with a personal entity; and / or may take the form of an Internet of Things (IoT) device (such as a multimedia device, camera, speaker, home appliance, vehicle, vending machine, etc.) to be associated with a machine entity, and the network device 3 is adapted to communicate via a telecommunications network (not shown) using at least one subscriber profile P. The network device 3 may include a storage unit 4 for storing an application A (such as an LPA and / or IPA), and a communication module 5 having a security element 6 (such as a UICC, eUICC, iUICC, SIM, eSIM, iSIM, SE, or eSE), thereby enabling communication via the telecommunications network. The security element 6 may be identified by an identifier E (such as an EID) and may include a storage area 7 (such as non-volatile memory) for storing the subscriber profile P and an authentication certificate C for authenticating the source O of the application A.
[0037] The method for authenticating the source O of the application may have multiple steps S, which may be performed by and / or with the assistance of an authentication module M, which may be stored in storage unit 4 and may be part of application A. In the first step S1, application A may obtain identifier E from security element 6, for example, by reading identifier E. In the second step S2, for a period of time before authentication is successfully performed, at least one function F of the network device 2 may be restricted according to its corresponding functionality. For example, security element 6 may be silenced so that no communication function is performed via the communication network before authentication is successfully performed. In the third step S3, application A may send an authentication request to security element 6 to perform authentication of the source O of application A.
[0038] In step S4, authentication of the source O of application A is performed by secure element 6, for example, within secure element 6. This application step may involve checking the signature D of certificate C, which may be issued by computing device 2. After authentication, in step S5, the functionality of network device 3, particularly communication module 5, can be determined. For example, if authentication is not (completely) successful, this can be determined by returning to step S2, which restricts functionality, for example, by blocking any communication or at least response to Application Protocol Data Units (APDUs) between application A and secure element 6. Conversely, if authentication is (completely) successful, the restrictions on the functionality of network device 3 and / or communication module 5 can be lifted, thereby enabling the desired set of corresponding functions F. In step S6, the authentication result R can be returned from secure element 6 to application A. In step S7, network device 3 can forward the authentication result R to computing device 2.
[0039] In step S8, certificate C (e.g., with signature D) can be sent from computing device 2 to network device 3. For example, a certificate request can be initiated by sending identifier E to computing device 2 and in step S7, enabling computing device 2 to assess whether security element 6 meets certain requirements, such as having the same source O or at least a certified source O. Providing certificate C from computing device 2 to network device 3, particularly to application A, can be considered a zero step S0 preceding all previous steps, for example, if certificates were provided for application A and / or security element 6 during the manufacture of network device 3.
[0040] In step S9, certificate data, including, for example, authentication result R and / or signature D, may routinely be sent from network device 3 to computing device 2, for example, after a certain period of time, after a reset, or after network device 3 performs any other type of specific operation. Therefore, application A, particularly application module M, may return to step S1 and / or step S3 to subsequently execute all subsequent steps. In step S10, if authentication is (completely) successful, the authentication result R can be confirmed; and / or, if authentication is (completely) unsuccessful, computing device 2 may take action based on the authentication result R. For example, in the latter case, application A, particularly authentication module M, may cause security element 6 to return to step S2 and / or step S5 to determine, in particular, restrict the functionality of network device 3, especially the functionality of communication module 5 and / or its security element 6, by disabling certain functions F to be performed.
[0041] The authentication system 1, and in particular the computing device 2 and / or network device 3, are configured to execute the computer program 10. A computer-readable data carrier 11 may have the computer program 10 stored thereon, and may take the form of a computer-readable medium 12 and / or a data carrier signal 13. When the computer program 10 is executed, the authentication system 1 and any of its components communicate in accordance with the manner specified in the computer program 10. Parameters associated with and / or based on the authentication system 1, any of its components, and / or any steps performed by it may be defined in and / or by the computer program 10.
[0042] Figure 2 It shows Figure 1 The diagram illustrates the communication hierarchy of the components involved in the authentication system 1, conforming, for example, to the International Telecommunication Union (ITU) X.509 format specification for constructing certificate D and its configuration. A trusted entity T, for example as source O, may be at the highest level and can provide and / or create application A, authentication module M, certificate C, signature D, and computing device 2, which can be considered to be located at the second higher level. The trusted entity can also provide and / or create a security element 6, which can be configured to communicate via application A and / or authentication module M, and therefore can be considered to be located at the third higher level.
[0043] List of reference numerals
[0044] 1. Authentication System
[0045] 2. Computing devices / server devices
[0046] 3. Network devices / Mobile devices / IoT devices
[0047] 4 storage units
[0048] 5 Communication Modules
[0049] 6 safety elements
[0050] 7. Storage Areas / Non-volatile Memory
[0051] 10 Computer Programs
[0052] 11 Computer-readable data carriers
[0053] 12 Computer-readable media
[0054] 13 Data carrier signal
[0055] Application A
[0056] C Certificate
[0057] D signature
[0058] E identifier
[0059] F function
[0060] M Authentication Module
[0061] O source
[0062] P Subscriber Profile
[0063] R certification results
[0064] Step S
[0065] Trusted Entity
[0066] S0 creates / provides certificates
[0067] S1 obtains the identifier.
[0068] S2 Limitation Functionality
[0069] S3 Request Authentication
[0070] S4 performs certification / inspection of certificates
[0071] S5 determines functionality
[0072] S6 returns authentication results.
[0073] S7 forwarding identification results
[0074] S8 Send Certificate
[0075] S9 (routine) inspection and certification
[0076] S10 Confirm certification results / Take action based on certification results
[0077] all aspects
[0078] 1. A method for configuring a network device, the method comprising the steps of: providing an application, particularly an LPA and / or an IPA, the application being adapted to interact with a security element (such as eUICC) of the network device; and using the security element to check an authentication certificate used to authenticate the origin of the application.
[0079] 2. The method according to aspect 1 further includes the step of issuing the certification certificate to the security element.
[0080] 3. The method according to aspect 1 further includes the step of providing the authentication certificate to the network device via a telecommunications network.
[0081] 4. The method according to aspect 1 further includes the step of passing the authentication certificate from the application to the security element.
[0082] 5. The method according to aspect 1 further includes the step of storing the authentication certificate in the secure element.
[0083] 6. The method according to aspect 1 further includes the step of obtaining an identifier from the security element.
[0084] 7. The method according to aspect 6, wherein the identifier is a unique device identifier of the security element.
[0085] 8. The method according to aspect 1 further includes the step of requesting the security element to check the authentication certificate.
[0086] 9. The method according to aspect 1, wherein the step of checking the authentication certificate involves determining whether the authentication certificate exists.
[0087] 10. The method according to aspect 9 further includes the steps of: enabling at least one function of the application if the authentication certificate exists, or disabling at least one function of the application if the authentication certificate does not exist.
[0088] 11. The method according to aspect 1, wherein the step of the inspection involves assessing the validity of the application certificate.
[0089] 12. The method according to aspect 11 further includes the steps of: enabling at least one function of the application if the authentication certificate is valid, or disabling at least one function of the application if the authentication certificate is invalid.
[0090] 13. The method according to aspect 1 further includes the step of: if the step of checking the authentication indicates that there is a certificate problem, then rejecting the response from the security element to the application.
[0091] 14. The method according to aspect 1 further includes the step of: returning the result of the step of checking the authentication certificate to the trusted entity.
[0092] 15. The method according to aspect 14 further includes the step of: taking action if the step of checking the authentication indicates that there is a certificate problem.
[0093] 16. A communication module configured to communicate via a telecommunications network, comprising a security element, such as an eUICC, the security element being configured to check authentication certificates for the origin of an application, particularly an LPA and / or an IPA, adapted to interact with the security element.
[0094] 17. A network device configured to communicate via a telecommunications network, comprising a security element, such as an eUICC, the security element being configured to check authentication certificates for the origin of an application, particularly an LPA and / or an IPA, adapted to interact with the security element.
[0095] 18. The network device according to aspect 17, including a storage unit containing the application.
[0096] 19. The network device according to aspect 17, wherein the application is configured to process at least one subscriber profile of a subscriber of the telecommunications network.
[0097] 20. The network device according to aspect 17, wherein the network device is configured to be associated with at least one of a personal entity and a machine entity.
Claims
1. A method for configuring a network device (3), the method comprising the following steps: Provide an application (A), particularly an LPA and / or an IPA, the application being adapted to interact with a security element (6) of the network device (3), the security element (6) being such as an eUICC; and utilize the security element (6) to check an authentication certificate (C) for authenticating the origin of the application (A).
2. The method according to claim 1, further comprising: The step of issuing the certification certificate (C) to the security element (6); The step of providing the authentication certificate (C) to the network device (3) via a telecommunications network; The steps of transferring the authentication certificate (C) from the application (A) to the security element (6); and / or The step of storing the authentication certificate (C) in the security element (6).
3. The method according to claim 1 or 2, further comprising the step of obtaining an identifier (E) from the security element (6).
4. The method according to claim 3, wherein, The identifier (E) is a unique device identifier for the security element (6).
5. The method according to any one of claims 1 to 4, further comprising the step of requesting the security element (6) to check the authentication certificate (C).
6. The method according to claim 5, wherein, The step of checking the certification certificate (C) involves determining whether the certification certificate (C) exists and / or evaluating the validity of the application certificate (C).
7. The method according to claim 6, further comprising the following step: If the authentication certificate (C) exists, then enable at least one function (F) of the application (A), or if the authentication certificate (C) does not exist, then disable at least one function (F) of the application (A); and / or the following steps: If the authentication certificate (C) is valid, at least one function (F) of the application (A) is enabled; or if the authentication certificate (C) is invalid, at least one function (F) of the application (A) is disabled.
8. The method according to any one of claims 1 to 7, further comprising the step of: If the authentication check indicates a certificate problem, then the response from the security element (6) to the application (A) is rejected.
9. The method according to any one of claims 1 to 8, further comprising the step of returning the result of the step of checking the authentication certificate (C) to the trusted entity (T).
10. The method according to any one of claims 1 to 9, further comprising the step of: If the verification process indicates a certificate issue, then action is taken.
11. A communication module (5) configured to communicate via a telecommunications network, comprising a security element (6), such as an eUICC, the security element being configured to perform the method according to any one of claims 1 to 10.
12. A network device (3) configured to communicate via a telecommunications network, comprising a security element (6), such as an eUICC, the security element being configured to perform the method according to any one of claims 1 to 10 to check an authentication certificate (C) for the source of an application (A), the application being particularly an LPA and / or an IPA adapted to interact with the security element (6).
13. The network device (3) according to claim 12, comprising a storage unit (4) containing the application (A).
14. The network device (3) according to any one of claim 12 or 13, wherein, The application (A) is configured to process at least one subscriber profile (P) of the subscribers of the telecommunications network.
15. The network device (3) according to any one of claims 12 to 14, wherein, The network device (3) is configured to be associated with at least one of a personal entity and a machine entity.
Citation Information
Patent Citations
Profile handling of a batch of identity modules
WO2021047765A1
Delegated euicc profile management
WO2023017031A1