Method of Providing a Communication Function in a User Equipment

Abstract

A method of providing a communication function in a user equipment includes receiving, at the user equipment, a login request to log the user in to the user equipment; determining, by the user equipment, based on the login, whether the user equipment has a communication profile associated with the user; if it is determined that the user equipment has a communication profile associated with the user, enabling the stored communication profile; if it is determined that the user equipment does not have a communication profile associated with the user stored: sending, by the user equipment, a first request to a first server to request support information for obtaining a communication profile associated with the user; receiving, at the user equipment, the support information from the first server; and obtaining, by the user equipment, the communication profile from the first server or a second server based on the support information.

Claims

1. A method of providing a communication function in a user equipment, the method comprising: receiving, at the user equipment, a login request to log a user in to the user equipment; determining, by the user equipment, based on the login request, whether the user equipment has a communication profile associated with the user; upon determining that the user equipment has the communication profile associated with the user, enabling the communication profile; upon determining that the user equipment does not have the communication profile associated with the user: sending, by the user equipment, a first request to a first server to request support information for obtaining the communication profile associated with the user; receiving, at the user equipment, the support information from the first server; and obtaining, by the user equipment, the communication profile from the first server or a second server based on the support information.

2. The method of claim 1, further comprising: enabling, by the user equipment, the communication profile obtained from the first server or the second server.

3. The method of claim 1, wherein the first request includes at least one of user equipment identification information, Subscriber Identity Module information, or user information.

4. The method of claim 1, wherein the support information includes an activation code for the communication profile.

5. The method of claim 4, wherein the support information further includes at least one of Subscriber Identity Module information, a communication profile type, user information, or a confirmation code.

6. The method of claim 1, wherein obtaining, by the user equipment, the communication profile from the first server or the second server based on the support information includes: sending, by the user equipment, a second request to the first server to request a download of the communication profile from the first server, or sending, by the user equipment, a second request to the second server to request a download of the communication profile from the second server.

7. The method of claim 1, wherein obtaining, by the user equipment, the communication profile from the first server or the second server based on the support information includes: sending, by the user equipment, a second request to the first server to request a download of the communication profile from the first server, wherein the first server obtains the communication profile from the second server; or sending, by the user equipment, a second request to the second server to request a download of the communication profile from the second server.

8. The method of claim 1, further comprising: determining, by the user equipment, whether sufficient memory is available for installation of the communication profile.

9. The method of claim 8, further comprising: upon determining that sufficient memory is available, installing the communication profile obtained from the first server or the second server.

10. The method of claim 8, further comprising: upon determining that sufficient memory is not available, deleting at least one other communication profile stored in the user equipment; and installing the communication profile obtained from the first server or the second server.

11. The method of claim 10, wherein the at least one other communication profile comprises at least one of an unknown communication profile, a least used communication profile, a recently least used communication profile, or an oldest communication profile.

12. The method of claim 1, further comprising: receiving, at the user equipment, a logout request to log the user out; and disabling the communication profile.

13. The method of claim 1, further comprising: receiving, at the user equipment, a logout request to log the user out, wherein the logout request is received via user input or automatically triggered by one or more events; and disabling the communication profile.

14. The method of claim 1, further comprising: receiving, at the user equipment, a communication profile deletion request; and deleting the communication profile according to the communication profile deletion request.

15. The method of claim 1, further comprising: receiving, at the user equipment, a communication profile deletion request, wherein the deletion request is received via user input or automatically triggered by one or more events; and deleting the communication profile according to the communication profile deletion request.

16. A computer product comprising a non-transitory computer-readable storage medium having stored thereon program code, that, when executed on a processor, carries out the method according to claim 1.

17. A management module for a communication module, the management module comprising: a communication interface configured for communication with the communication module and a server, wherein the communication interface is configured to receive a login request or information about a user login; and a processor module configured to: determine, based on the login request or the information about the user login, whether the communication module has a communication profile associated with a user; upon determining that the communication module has the communication profile associated with the user, initiate enabling of the communication profile; and upon determining that the communication module does not have the communication profile associated with the user, send a request to a first server via the communication interface to request support information for obtaining the communication profile associated with the user, wherein the communication interface is configured to receive the support information from the first server, and wherein the management module is configured to obtain the communication profile from the first server or a second server based on the support information.

18. A user equipment, comprising the management module of claim 17 and the communication module.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0055] FIG. 1 shows a flow chart of a method for providing a communication function in a user equipment according to embodiments described herein.

[0056] FIG. 2 shows a user equipment, a management server, and an MNO server according to embodiments described herein.

[0057] FIG. 3 shows a messaging process for providing a communication function in a user equipment according to embodiments described herein.

DETAILED DESCRIPTION OF THE DRAWINGS

[0058] Reference will now be made in detail to the various embodiments of the disclosure, one or more examples of which are illustrated in the figures. Within the following description of the drawings, the same reference numbers refer to same components. Generally, only the differences with respect to individual embodiments are described. Each example is provided by way of explanation of the disclosure and is not meant as a limitation of the disclosure. Further, features illustrated or described as part of one embodiment can be used on or in conjunction with other embodiments to yield yet a further embodiment. It is intended that the description includes such modifications and variations.

[0059] Although the embodiments of the present disclosure are described with reference to a vehicle, it is to be understood that the present disclosure is not limited thereto and that the embodiments described herein may be implemented in and/or used with a number of different types of UE devices, including but not limited to cellular phones, tablet computers, wearable computing devices, portable media players, vehicles, and any of various other computing devices.

[0060] FIG. 1 shows a flow chart of a method 100 for providing a communication function in a user equipment according to embodiments described herein.

[0061] The method 100 includes in block 110 receiving, at the user equipment, a login request from the user to log the user in to the user equipment; and in block 120 determining, by the user equipment, based on the login, whether the user equipment has stored a communication profile associated with the user.

[0062] In particular, the user is known to the user equipment through the login. This may be due to the possibility that during the login process the user equipment communicates with the first server, which may have stored all relevant information, e.g., in a user profile of the user. The user equipment may then obtain information necessary to determine whether the user equipment has stored a communication profile associated with the user.

[0063] In some embodiments, the communication profile is a CSIM or an eSIM profile

[0064] of the user.

[0065] The login request is received at a user interface of the user equipment, or an external entity connected to the user equipment. The user interface of the user equipment may be a Human Machine Interface (HMI), and may include, or be, a Touchscreen. The external entity may be, for example, a mobile terminal.

[0066] If it is determined that the user equipment has stored a communication profile associated with the user, the method 100 includes in block 130 enabling the stored communication profile to provide the communication function for the user.

[0067] Optionally, it can be checked whether communication functionalities, such as eSIM functionalities, have been previously enabled for the user (e.g., via a so-called onboarding). If not, the user may be directed to the account-federation with his/her MNO to enable eSIM functionalities. If it is determined that communication functionalities have been previously enabled for the user, block 130 may be executed. It is noted that this check can be done before or after the determining whether the user equipment has stored a communication profile associated with the user.

[0068] If it is determined that the user equipment does not have a communication profile associated with the user stored, the method 100 includes in block 140 sending, by the user equipment, a first request to a first server to request support information for obtaining a communication profile associated with the user; in block 150 receiving, at the user equipment, the support information from the first server; and in block 160 obtaining, by the user equipment, the communication profile from the first server or a second server based on the support information.

[0069] The first request may include at least one of user equipment identification information (e.g., a Vehicle Identification Number, VIN), Subscriber Identity Module information (e.g., an EID), and user information. The user information may be sent to the first server so that the first request can be mapped to a logged-in user. In some embodiments, the user information can be a Customer (C)-ID. It should be noted that the communication between the first server and the second server described later may not include the user information, such as the C-ID. Instead, communication between the first server and the second server may use a token generated by the second server.

[0070] According to some embodiments, the support information can include an activation code for the communication profile. The activation code can be used to request the communication profile from the first server or the second server.

[0071] In some embodiments, the support information further includes at least one of Subscriber Identity Module information (e.g., an EID), a communication profile type (e.g., “personal” if the profile is assignable to one user only, or “default” if the profile is assignable to different users), user information (e.g., the C-ID), and a confirmation code (optional). The confirmation code can be used by the second server to verify that the user wants to use the communication profile in the user equipment. In particular, the user can be asked whether he/she really wants to download the communication profile.

[0072] In some embodiments the method 100 may further include enabling, by the user equipment, the communication profile obtained from the first server or second server.

[0073] The step of obtaining, by the user equipment, the communication profile from the first server or a second server based on the support information may include sending, by the user equipment, a second request to the first server to request a download of the communication profile from the first server. Preferably, the first server obtains the communication profile from the second server using any suitable process.

[0074] Alternatively, the step of obtaining, by the user equipment, the communication profile from the first server or a second server based on the support information can include sending, by the user equipment, a second request to the second server to request a download of the communication profile from the second server. Accordingly, the user equipment may directly obtain the communication profile from the second server by communicating with the second server.

[0075] According to some embodiments, the method 100 further includes determining, by the user equipment, whether sufficient memory is available, e.g., on a storage medium of the user equipment, for installation of the communication profile.

[0076] Preferably, the memory is provided by (a storage medium of) a Universal Integrated Circuit Card, UICC, in particular an eUICC.

[0077] If it is determined that sufficient memory is available, the communication profile obtained from the first server or second server is installed e.g. on the eUICC. The installing of the communication profile may be done according to the GSMA standard.

[0078] If it is determined that sufficient memory is not available, at least one other communication profile stored in the user equipment can be deleted before the new communication profile is installed. The at least one other communication profile may be an unknown communication profile, a least used communication profile, a recently least used communication profile, and/or an oldest communication profile.

[0079] The term “sufficient memory” is to be understood in the sense that the memory contains sufficient free storage to install and enable the communication profile. In some embodiments, the memory or total memory available for storing communication profiles may by preset. Optionally, the memory or total memory available for storing communication profiles may be changeable, e.g., in the user equipment and/or by the first server.

[0080] According to some embodiments, the method 100 further includes receiving, at the user equipment, a communication profile deletion request from the user; and deleting the communication profile according to the communication profile deletion request. Preferably, the deletion request is received at the user interface of the user equipment, or the external entity connected to the user equipment.

[0081] In some implementations, the method 100 further includes receiving, at the user equipment, a logout request to log the user out; and disabling the communication profile. Preferably, the logout request is received at the user interface of the user equipment, or the external entity connected to the user equipment.

[0082] FIG. 2 shows a schematic view of a vehicle (UE) 10, a first server 400, and a second server 500 according to embodiments described herein. However, the present disclosure is not limited thereto, and the embodiments may be implemented in and/or used with a number of different types of UE devices, including, but not limited to, cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.

[0083] The vehicle 10 includes a communication module 200 and a management module 300 for the communication module 200. In some embodiments, the communication module 200 and the management module 300 are integrated in a single hardware and/or software module. In further embodiments, the communication module 200 and the management module 300 can be provided as separate hardware and/or software modules.

[0084] The term “module” as used throughout the present application may be understood in the sense of hardware components and software components or software instances which are designed to implement different tasks of the embodiments of the present disclosure.

[0085] The communication module 200 may include one or more sub-modules used for communication purposes, such as a Local Profile Assistant (LPA), a modem, and an eUICC.

[0086] The management module 300 may include a communication interface configured for communication with the communication module 200 and at least one server, such as the first server 400 and optionally the second server 500. For example, the communication interface may use a dedicated UE communication profile for communication with the at least one server via a mobile network. The dedicated UE communication profile can be provided in the management module 300, the communication module 200 (e.g., the eUICC of the communication module 200), or another module.

[0087] The vehicle 10 and the first server 400 communicate via a transmission medium, such as a network. In a preferred embodiment, the network is a mobile network. The transmission medium may use any of various wireless communication technologies, or telecommunication standards, such as GSM, UMTS, LTE, LTE-Advanced (LTE-A), 5G, HSPA, and the like.

[0088] In some embodiments, the vehicle 10 and the second server 500 may communicate via the same network used for communication with the first server 400 or a different network. In alternative embodiments, the vehicle 10 does not communicate with the second server 500 at all or communicates with the second server 500 via the first server 400.

[0089] According to some embodiments, the first server 400 is a management server or backend for managing a plurality of UE devices. For example, the first server 400 can be owned and/or operated by a manufacturer of the UE devices, such as a car manufacturer. However, the present disclosure is not limited thereto, and the first server 400 may be owned and/or operated by another third party.

[0090] Additionally, or alternatively, the second server 500 is a mobile network operator, MNO, server or backend. The MNO may also be referred to as a wireless service provider, wireless carrier, cellular company, or mobile network carrier. The MNO can provide the communication profile for the user which should be downloaded and installed in the user equipment.

[0091] The management module 300 includes the communication interface, and further includes a processor module to implement the aspects of the method described with respect to FIG. 1.

[0092] In particular, the communication interface can be configured to receive a login request from a user or information about a successful user login. The processor module is configured to: determine, based on the login, whether the communication module 200 has stored a communication profile associated with the user; if it is determined that the communication module 200 has stored a communication profile associated with the user, initiate enabling of the stored communication profile; and, if it is determined that the communication module 200 does not have a communication profile associated with the user stored, send a request to a first server 400 via the communication interface to request support information for obtaining a communication profile associated with the user.

[0093] The communication interface is further configured to receive the support information from the first server 400. The management module 300 is further configured to obtain (e.g., download) the communication profile from the first server 400 or second server 500 based on the support information and install the communication profile on, for example, the eUICC of the communication module 200.

[0094] In some embodiments, the communication profile obtained from the first server 400 or second server 500 and installed on the eUICC of the communication module 200 can be enabled by the LPA of the communication module 200.

[0095] FIG. 3 shows a messaging process for providing a communication function in a user equipment according to embodiments described herein.

[0096] FIG. 3 shows schematically a user (“User”), a vehicle (“UE”) having a user interface (“UI”), the communication module (“CM”) and the management module (“MM”), a management server (“MS”), and an MNO server (“MNO”).

[0097] The communication module CM and the management module MM can be integrated in a single hardware and/or software module. In further embodiments, the communication module CM and the management module MM can be provided as separate hardware and/or software modules.

[0098] The management module MM (e.g., the eSIM “brain” in the vehicle) handles the communication between the management server MS (e.g., a backend of the OEM or a 3rd party backend that performs the same function as the OEM backend) and the communication module CM in the vehicle in which the LPA, modem and SIM card are installed.

[0099] In the following, exemplary tasks of the management module MM are described.

[0100] Task 1: Download an eSIM profile

[0101] The user logs in to the vehicle (arrow 1). Based on the login, the vehicle recognizes the user. The management module MM is notified about the login (arrow 2) and checks whether eSIM functionalities have been previously enabled for the user (e.g., via a so-called onboarding). If not, the user may be directed to the account-federation with his/her MNO to enable eSIM functionalities.

[0102] If eSIM functionalities are enabled (e.g., due to a general setup and/or account settings), the management module MM checks whether the user has already loaded an eSIM profile or not. If the user has loaded an eSIM profile, the process continues with Task 2 (enable eSIM profile). If the user has not yet loaded an eSIM profile e.g. because the eSIM profile has been lost or deleted, or the user is sitting in this vehicle for the first time, a new eSIM profile should be loaded for this user. To do this, the management module MM takes vehicle information, SIM card information and user information and requests an activation code from the management server MS (arrow 3).

[0103] The management server MS now exchanges information with the MNO (arrow 4) and receives an activation code (arrow 5). The management server MS sends the activation code to the management module MM (arrow 6).

[0104] Before the management module MM sends the activation code to the LPA of the communication module CM, the management module MM checks whether there is enough space left on the SIM card to install another eSIM profile.

[0105] Task 2: Activate eSIM profile (enable)

[0106] Each time the user logs in, the corresponding eSIM profile must be enabled. The reason for this is that the eSIM profiles must be disabled for security reasons when the user logs out. To enable the eSIM profile (either the previously stored eSIM profile or the downloaded new eSIM profile), the management module MM sends a profile ID to the LPA of the communication module CM. The LPA enables the eSIM profile and then sends the result to the management module MM. The management module MM send this information as well as other status information of the SIM card and the eSIM profile to the management server MS.

[0107] Task 3: Deactivate eSIM profile (disable)

[0108] Each time the user logs out (arrows 9 and 10), the corresponding eSIM profile must be disabled. The reason for this is that the profiles must be protected in case of absence. This is not necessary for a cell phone or a watch, as these devices are not passed on to other users.

[0109] The management module MM instructs the LPA to disable the eSIM profile. The LPA disables the eSIM profile and then sends the result to the management module MM. The management module MM sends the result as well as other status information of the SIM card and the profile to the management server MS. In case of a successful disablement the process is finished. In case of an unsuccessful disablement or error a deletion process is triggered, because an eSIM profile that cannot be disabled represents a security risk (see Task 4).

[0110] Task 4: Delete eSIM profile

[0111] In a first example, if the user wants to delete an eSIM profile (in the car, via app, etc.; arrows 7 and 8), then the management module MM sends a delete command to the LPA to delete this very eSIM profile.

[0112] In a second example, one of multiple users logs in to the vehicle and wants to load an eSIM profile. If there is not enough memory on the SIM card, an eSIM profile must be deleted first. After deleting the eSIM profile, a new eSIM profile can be install on the SIM card.

[0113] In a third example, the management module MM can delete eSIM profiles which are installed but not assigned to any specific users.

[0114] The foregoing disclosure has been set forth merely to illustrate the invention and is not intended to be limiting. Since modifications of the disclosed embodiments incorporating the spirit and substance of the invention may occur to persons skilled in the art, the invention should be construed to include everything within the scope of the appended claims and equivalents thereof.