eUICC automatic profile switcher

Abstract

The present invention relates to a method for allowing a UE (User Equipment) to automatically attach or connect to a private network by using an eUICC (Embedded Universal Integrated Circuit Card) application, the method comprising the steps of: prioritizing, by the eUICC application, a private network by replacing the content of a public EHPLMN (Equivalent Home Public Land Mobile Network) of a public profile with a cumulative private EHPLMN list containing the private network, and switching, by the eUICC, to a private profile corresponding to the private network when the UE attempts to attach or connect to the private network, while the public profile remains enabled, wherein the private profile contains credentials for the attachment or connection, the invention also relates to an eUICC application, to an eUICC comprising the eUICC application, and to a computer program product for performing the method.

Description

Technical Field

[0001] This invention relates to a method and application for enabling eUICC (Embedded Universal Integrated Circuit Card) to automatically switch to a private profile, particularly in fields where both public and private networks are available. Background Technology

[0002] Recently, mobile devices configured to communicate over mobile networks using electronic subscriber profiles have emerged. These mobile devices are typically equipped with electronic / embedded secure element devices, such as electronic / embedded universal integrated circuit cards (eUICCs), configured to store one or more electronic subscriber profiles, such as electronic subscriber identification module (eSIM) profiles that allow the mobile device to connect to one or more mobile networks. The subscriber profile (e.g., the eSIM profile) can be generated by the mobile network operator (MNO) and can be downloaded to the mobile network device. The subscriber profile can then be installed on the secure element of the mobile device and used for communication by the mobile device over the corresponding mobile network.

[0003] The ETSI (European Telecommunications Standards Institute) describes and defines the automatic network selection process in the TS 123.122 V17.6.0 specification. The process defined by ETSI is based on a series of SIM base files containing priority-ordered lists of preferred and allowed networks, configured by the MNO (Mobile Network Operator). The MNO may use several sets of parameters, each applicable to a large number of eUICCs. However, end users can also define their own preferences, thus influencing automatic network selection, but user preferences take precedence over MNO preferences.

[0004] Original Equipment Manufacturers (OEMs) typically have their own networks, which are considered private networks. MNOs (such as Vodafone) networks, on the other hand, are considered public networks. These private networks of OEMs are independent of the public networks of MNOs. Therefore, OEM private networks do not exist in the MNO's configuration files. Consequently, it is impossible for an OEM to prioritize its private networks for its users.

[0005] If an OEM requires a User Equipment (UE) to successfully attach or connect to its own private network, with the aim of sharing relevant data while the UE is in an area where both the OEM's private network and the MNO's public network coexist, such as when an electric vehicle acting as the UE enters a charging area and the OEM needs to exchange data with the vehicle, the OEM should enable the private file within the card (i.e., eUICC) corresponding to the OEM's private network to provide the appropriate credentials for network attachment.

[0006] According to existing technology, in scenarios with coexisting network coverage—that is, where both public and private networks exist in an area—although the User Equipment (UE) can theoretically scan all networks (including private networks) radiating in the area where the UE is currently located, it will not automatically scan for and attempt to attach to private networks because the UE is unaware that private networks have been prioritized (priority sorting). As a result, eUICC cannot seamlessly detect the existence of private networks and automatically switch its operation profile to the private profile corresponding to the private network.

[0007] Therefore, it is desirable to provide a method that enables a UE to scan and attempt to attach to a private network, wherein the attempt to attach to the private network is reported to the eUICC so that the operation profile is switched to the appropriate private profile corresponding to the private network, thereby allowing a successful attachment. Summary of the Invention

[0008] The present invention addresses the aforementioned objectives through the subject matter covered by the independent claims. Preferred embodiments of the invention are defined in the dependent claims.

[0009] According to a first aspect of the invention, a method is provided for allowing a UE (User Equipment) to automatically attach to or connect to a private network using a UICC (Universal Integrated Circuit Card) application. The method includes the step of prioritizing the private network by the UICC application by replacing the content of the public EHPLMN (Equivalent Home Public Land Mobile Network) of a public profile with an accumulated list of private EHPLMNs containing the private network. The content of the public EHPLMN in the public profile may refer to the EHPLMN list of the public profile. The method further includes the step of switching the eUICC to the private profile corresponding to the private network when the UE attempts to attach or connect to the private network, while the public profile remains enabled, wherein the private profile contains credentials for attaching or connecting.

[0010] The proposed solution allows the eUICC application to first internally collect EHPLMNs from all private and disabled profiles stored on the eUICC to generate an accumulated private EHPLMN list. This accumulated private EHPLMN list is then transmitted to the UE as if it were the EHPLMN list for the currently enabled public profile. In other words, instead of returning the original EF_EHPLMN content of the currently enabled public profile to the UE as in existing technologies, the eUICC returns the accumulated private EHPLMN list generated by the eUICC application. After obtaining the accumulated private EHPLMN list, once the UE enters an area where both the public network corresponding to the currently enabled public profile and the private network corresponding to the disabled private profile exist, the UE will attempt to attach to the private network (which has higher priority than the current public network due to the content of the accumulated private EHPLMN list). Therefore, the eUICC will be notified of this attach attempt (using available standard mechanisms) and can switch to the appropriate private profile while the public profile is currently enabled, i.e., active.

[0011] Furthermore, the proposed solution provides an offline mechanism for profile switching. In this context, the term "offline" means making the decision about which profile to enable locally on the eUICC based on the eUICC configuration and current network events, without any interaction with any server. The advantage of the offline mechanism is that it can switch to the appropriate profile even if the currently enabled profile has no connectivity, i.e., no communication with any server.

[0012] Preferably, the step of prioritizing the private network further includes the following step: when the UE reads the EF_EHPLMN file during its initialization, the eUICC application hijacks the binary command response for reading the EF_EHPLMN file of the public configuration file.

[0013] "EF_EHPLMN" represents the Basic File Equivalent Home Public Land Mobile Network (PFMN). It is a specific file on the eUICC containing a list of EHPLMNs, or a list of networks considered equivalent to the home network for network selection purposes. The "Read Binary Command" is a specific command sent to the eUICC to read the binary data contained in the EF_EHPLMN file. The "Command Response" is the data returned by the eUICC after the "Read Binary Command" has been executed. Therefore, the "EF_EHPLMN file Read Binary Command Response" refers to a list of multiple EHPLMNs in the currently enabled public configuration file. After executing the Read Binary Command on the EF_EHPLMN file, the eUICC returns the EHPLMN list to the UE.

[0014] Preferably, the prioritized private network further includes: the step of configuring a list of private profile entries containing one or more operation profile filtering conditions by the eUICC application; the step of traversing the private profile entries by the eUICC application when the UE starts; and the step of constructing a cumulative private EHPLMN table by the eUICC application containing a cumulative private EHPLMN list, the cumulative private EHPLMN list including EHPLMN items from each private profile and their corresponding private profile.

[0015] Before the UE starts up (e.g., when the UE powers on or resets the eUICC), the eUICC application has already configured a list of private profile entries. This list of entries contains one or more operational profile filtering conditions. In other words, the list of entries provides the order or sequence in which private profiles stored in the eUICC are filtered. When the UE starts up, the eUICC application iterates through all entries in the list. Based on the order or sequence of the private profiles provided by the list, the EHPLMN entries in each private profile are collected in a cumulative private EHPLMN list. It is possible that an EHPLMN entry for a private profile is not collected in the cumulative private EHPLMN list because that private profile was filtered out by the list of private profile entries. The cumulative private EHPLMN list is contained within a cumulative private EHPLMN table, which also contains the name of the private profile to which each EHPLMN entry in the cumulative private EHPLMN list belongs. An EHPLMN entry can refer to a PLMN, which is a combination of MCC and MNC.

[0016] Preferably, the process of switching to a private profile for a private network includes: receiving events from the UE via the eUICC; extracting MCC (Mobile Country Code) / MNC (Mobile Network Code) values ​​from the event data via the eUICC; searching for values ​​that match the extracted MCC / MNC values ​​via the eUICC; identifying the private profile via the eUICC based on the searched values ​​via the eUICC; and activating the private profile via the eUICC.

[0017] Events can refer to network rejection or location status. "Network rejection" means that a UE with an eUICC is not allowed to connect to a specific network. This can happen when the UE is outside the coverage area of ​​the network associated with the active eUICC profile. "Location status" is a notification or update triggered when the UE's network location changes. For example, this can happen when the UE moves from one cell to another, or from one tracking area to another. The eUICC will receive an event when the UE enters an area where both a public network (corresponding to the currently enabled public profile) and a private network (corresponding to the currently disabled private profile) exist. The event data contains a PLMN value as a combination of MCC and MNC. This value is extracted by the eUICC and used to search for a matching value in the accumulated private EHPLMN list. Once a matching value is found in the accumulated private EHPLMN list, the corresponding private profile is identified by referring to the accumulated private EHPLMN table, which contains both the accumulated private EHPLMN list and the name of the corresponding private profile. After identifying the private profile, the eUICC automatically switches the operating profile to the private profile containing the appropriate credentials for successful attachment.

[0018] Preferably, one or more operation profile filtering conditions include whether the profile IMSI (International Mobile Subscriber Identity) matches a predetermined pattern and / or whether the profile ISDP AID (Application Identifier) ​​matches a predetermined pattern and / or whether the profile ICCID (Integrated Circuit Card Identifier) ​​matches a predetermined pattern.

[0019] A "predetermined pattern" for an IMSI can refer to a specific range of IMSI numbers, a specific mobile network operator, or some other standard. For example, an eUICC can be programmed to use only profiles whose IMSI numbers fall within a specific range. Alternatively, if a UE with an eUICC is using international roaming services, the IMSI can be used to determine the appropriate profile for the local network to connect to. To determine if a profile's IMSI matches a predetermined pattern, it is typically necessary to compare the IMSI number associated with that profile with an established pattern or rule. This might involve checking if the IMSI falls within a certain numerical range, if it begins or ends with a certain number, or if it contains a sequence of numbers.

[0020] ISDP stands for "Issuer Security Domain Profile". It is a specific area in the eUICC file system dedicated to a particular profile (such as a network operator profile). Each ISDP is identified by an AID (Application Identifier), which is a unique identifier that helps eUICC search for and select the appropriate profile when needed. When we talk about whether the profile ISDP AID matches a predetermined pattern, it is similar to a discussion about whether the IMSI matches a predetermined pattern. In this context, "predetermined pattern" can refer to a specific range of AID numbers, a specific network operator, or other criteria.

[0021] ICCID stands for Integrated Circuit Card Identifier, which is a unique serial number that identifies each profile on the eUICC. When we talk about whether a profile ICCID matches a predetermined pattern, we are referring to comparing the ICCID associated with a specific profile on the eUICC with some defined rule or pattern.

[0022] Preferably, the credentials are network authentication parameters or values ​​used to attach to the network. Credentials may include: IMSI (International Mobile Subscriber Identity), a unique identifier linking a mobile user to a specific network; an authentication key (Ki), a secret key used for authentication purposes, with the same key stored in the network's Authentication Center (AuC); and OPC, a value derived from the operator variable algorithm and Ki, used in the authentication and encryption process. Additionally, information stored in the MSISDN (Mobile Station International Subscriber Directory Number), which is the phone number associated with each profile on the eUICC; the ICCID (Integrated Circuit Card Identifier), a unique serial number for each profile on the eUICC; and LOCI (Location Information) and EPS LOCI, files storing the user's last known location and used during network connection; all of this information can be used for network authentication.

[0023] Preferably, service N°71 is enabled by the eUICC application, causing the EHPLMN file to be displayed on the card, allowing the UE to read and use the contents of the EHPLMN file. For this purpose, a UST (USIM Service Table) file containing a list of numbered services can be adjusted by the eUICC. The UST file contains a list of bits (0 / 1), where each bit defines whether the corresponding service is supported by the card. The UE reads the UST file at startup to check card capabilities. Service N°71 can then be enabled by setting bit 71 to 1. EHPLMN (Equivalent Home Public Land Mobile Network) is a concept used in mobile communications to indicate the network that should be considered the "home" network by the UE. N°71 refers to a specific 3GPP (3rd Generation Partnership Project) technical specification, TS31.102. This specification outlines the features of the UICC (Universal Integrated Circuit Card) application toolkit for "USIM" applications, which are applications on the SIM card that allow it to connect to 3G, 4G, and 5G networks.

[0024] When it says "Service No. 71 is enabled by eUICC application", it means that the eUICC has been programmed to support the functions described in these specifications. In other words, the UE is able to recognize certain networks as its home network by reading EHPLMN content from the eUICC, and it also supports the functions described in 3GPP TS 31.102 specification.

[0025] Preferably, the cumulative private EHPLMN list is derived from individual EHPLMNs in each private configuration file. Each private configuration file has its own EHPLMN list containing multiple PLMNs. Because the configuration files containing EHPLMNs are filtered and sorted, at least a portion of these PLMNs are filtered and set in a predetermined or desired order to generate the cumulative private EHPLMN list. However, PLMN filtering and sorting do not occur within the same configuration file.

[0026] According to a second aspect of the invention, an eUICC application is provided for allowing a UE (User Equipment) to attach to or connect to a private network.

[0027] The eUICC application is configured to enable the UE to prioritize private networks by replacing the content of the public EHPLMN (Equivalent Home Public Land Mobile Network) with an accumulated private EHPLMN list containing private networks, and to enable eUICC to switch to the private profile corresponding to the private network when the UE attempts to attach or connect to the private network, while the public profile is currently enabled, wherein the private profile contains credentials for attaching or connecting.

[0028] Preferably, the UICC application is also configured to: hijack the binary command response for reading the EF_EHPLMN file when the UE reads the EF_EHPLMN file in the public files during initialization.

[0029] Preferably, in order to enable the UE to prioritize private networks (i.e., give priority to private networks), the eUICC application is further configured to: configure a list of private profile entries containing one or more operation profile filtering conditions; when the UE starts, it traverses the private profile entries, constructs a cumulative private EHPLMN table containing a cumulative private EHPLMN list (the cumulative private EHPLMN list includes EHPLMN items from each private profile and its corresponding private profile), and returns the cumulative private EHPLMN list to the UE.

[0030] Preferably, the eUICC application is configured to enable the services of EHPLMN and N°71.

[0031] Preferably, the eUICC application is configured to export a cumulative list of private EHPLMNs from the individual EHPLMNs of each private profile.

[0032] According to a third aspect of the present invention, an eUICC is provided, which includes the eUICC application according to the second aspect described above.

[0033] According to a fourth aspect of the present invention, a computer program product is provided, comprising instructions that, when executed by a computer, cause the computer to allow a UE (User Equipment) to automatically attach to or connect to a private network using a UICC (Universal Integrated Circuit Card) application, in the following manner: the eUICC application prioritizes the private network by replacing the contents of the public EHPLMN (Equivalent Home Public Land Mobile Network) with an accumulated private EHPLMN list containing the private network; and when the UE attempts to attach to or connect to the private network, the eUICC switches to a private profile corresponding to the private network, while the public profile remains enabled, wherein the private profile contains credentials for attaching or connecting.

[0034] It should be noted that all devices, elements, units, and apparatuses described in this application may be implemented as software or hardware elements or a combination thereof. All steps performed by the various entities described in this application, and the functions described, are intended to indicate that the respective entities are suitable for or configured to perform the corresponding steps and functions.

[0035] Further aspects, features, and advantages of the invention will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments and variations of the invention in conjunction with the accompanying drawings. Attached Figure Description

[0036] Now refer to the attached diagram, in which

[0037] Figure 1 This illustrates a scenario that demonstrates the relationship between different parties;

[0038] Figure 2 A flowchart is shown for a method to allow a UE to automatically attach to a private network using an eUICC application; and

[0039] Figure 3 The process of configuring a list of private configuration files is shown, which is sorted in the desired order based on one or more operation configuration file filtering conditions contained in a table. Detailed Implementation

[0040] The present invention will now be described in detail with reference to the accompanying drawings, which illustrate specific embodiments of the invention. These embodiments have been described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the invention, while different, are not necessarily mutually exclusive. For example, a particular feature, structure, or characteristic described herein in connection with one embodiment may be implemented in other embodiments without departing from the scope of the invention. Furthermore, it should be understood that the position or arrangement of various elements within each disclosed embodiment may be modified without departing from the scope of the invention. Therefore, the following detailed description should not be considered limiting, and the scope of the invention is defined only by the appended claims as properly interpreted and the full scope of their equivalents. In the drawings, the same reference numerals refer to the same or similar functions throughout several views.

[0041] In this specification, the term "eUICC" is understood as an integrated circuit IC designed to securely store at least one subscription profile with profile data. The "profile" on the eUICC (Embedded Universal Integrated Circuit Card) (also known as an embedded SIM or eSIM) refers to a set of information required for the device to connect to a specific mobile network operator. This information includes the ICCID (Integrated Circuit Card Identifier) ​​as the SIM's unique serial number, the IMSI (International Mobile Subscriber Identity) identifying the user of the mobile network and stored in the network's user database, an authentication key (Ki) used to authenticate the SIM on the mobile network, and the MCC (Mobile Country Code) and MNC (Mobile Network Code) identifying the mobile network operator. Furthermore, the profile in the eUICC may include a profile name.

[0042] MCC is a three-digit number identifying the country where the mobile network operator is located, while MNC is a two- or three-digit number identifying a specific mobile network operator within that country. Together, MCC and MNC form the PLMN (Public Land Mobile Network) identifier. This globally unique identifier is used to distinguish networks in different countries and identify the home network of a mobile user. The PLMN is a key part of the information stored in the configuration file on the eUICC, as devices require it to connect to the cellular network.

[0043] A Public Land Mobile Network (PLMN) is a network established and operated by an administrative body or Authorized Operating Authority (ROA) with the specific purpose of providing land mobile telecommunications services to the public. The term "home" in EHPLMN refers to the network to which a mobile device belongs or subscribes, which may be different from the network the device is currently connected to (e.g., when roaming). The "equivalent" part of an EHPLMN refers to the idea that multiple networks can exist that a device considers to be essentially the same as its home network. These equivalent networks can be different networks operated by the same company or networks from different companies that have an agreement to consider each other's customers as their own. A list of EHPLMNs is stored on the device's eUICC, and the device uses this list to decide which network to connect to. If the device is in a location where multiple networks are available, it will preferentially choose a network on its EHPLMN list over others.

[0044] When a "profile" is said to be "enabled," it means that the profile is currently active and being used by the device. eUICC can store multiple profiles, but typically only one profile can be enabled at a time. When a profile is enabled, the device uses the information in that profile to connect to the corresponding network.

[0045] Figure 1 This illustrates a scenario that demonstrates the relationship between different parties.

[0046] UE 30 can be a vehicle manufactured by an OEM. Nearby are a public network 10 from the MNO (e.g., Deutsche Telekom) and a private network 20 from the OEM. UE 30 includes an eUICC 40, which can be embedded within a telematics control unit (TCU) or communication module. The TCU is responsible for sending signals from the vehicle to and receiving signals from other devices or networks. It is the primary hub for sending and receiving data, such as GPS signals, data from onboard sensors, or even entertainment data. The exact location of the TCU within the vehicle can vary depending on the manufacturer and the specific model of the vehicle. However, it is typically placed in a secure and protected location, such as under the dashboard, inside the center console, or in the trunk area. The eUICC application 50 is installed on the eUICC 40.

[0047] When UE 30 is in an area where only public network 10 from MNO exists, it uses the conventional method to attach to public network 10. Once the UE enters an area where both public network 10 and private network 20 exist, eUICC application 50 allows UE 30 to automatically attach to private network 20. Figure 2 The process is described in detail below.

[0048] Figure 2 The process of allowing a user device (UE) to automatically attach to or connect to a private network by using an embedded universal integrated circuit card (eUICC) is illustrated.

[0049] The process mainly consists of two steps: the first step, S10, where the eUICC application prioritizes the private network by forcing the UE to understand it as its preferred home network; and the second step, S20, where the eUICC switches to the private profile corresponding to the private network. Each of these steps comprises several sub-steps, which will be explained in the following paragraphs.

[0050] First, the UE instructs the eUICC to reset during the "Card Reset" step, or performs such a reset in any other suitable manner, such as via power-on or cold reset (e.g., power off and on again). During the reset, the eUICC application has already performed step S11, which configures a list of private profile entries, ordered according to one or more operation profile filter conditions contained in the table. Figure 3 The process is described in detail below. Once the UE is started, the eUICC application executes step S12: iterating through the list of private profile entries configured above. Based on these private profile entries filtered in the desired order, the eUICC application also executes step S13, which constructs a cumulative private EHPLMN table containing a list of cumulative private EHPLMNs and their corresponding private profiles. Figure 3 The cumulative private EHPLMN table is described in detail.

[0051] When the UE powers on or after the eUICC resets, the terminal profile is transferred from the UE to the eUICC. The terminal profile informs the eUICC which features and functions the device supports. This includes network and connectivity capabilities, user interface characteristics, and other specific functions. This information allows the eUICC to customize its behavior based on the device's specific capabilities. For example, if the device does not support a certain network protocol, the eUICC will know not to attempt to use that protocol.

[0052] Subsequently, or simultaneously, the UE will read the EF_IMSI file on the eUICC to obtain the IMSI, and then the UE uses the IMSI to register with the cellular network. Thus, the UE can connect to the public network and begin sending and receiving data. "EF" stands for Basic File. This is a specific type of file on the card that contains data. The EF_IMSI file contains the IMSI, which is a unique identifier for public network users. The network uses the IMSI to identify and authenticate users. The IMSI consists of the MCC (Mobile Country Code) identifying the country of the network operator, the MNC (Mobile Network Code) identifying the specific network operator within that country, and the MSIN (Mobile Subscription Identifier) ​​identifying the individual user within the network.

[0053] After this, the IMSI value is sent from the eUICC to the UE. The IMSI value is a unique numeric string that identifies each user in the cellular network. It is typically 15 digits long, but can be shorter.

[0054] Subsequently or simultaneously, the eUICC application executes step S14, hijacking the "EF_EHPLMN file read binary command response," and then executes step S15, replacing the contents of the EHPLMN list of the currently enabled public profile with the cumulative private EHPLMN list generated above, which includes private networks, in order to prioritize private networks. "EF_EHPLMN" represents the base file equivalent home public land mobile network, which is a specific file on the eUICC containing a list of EHPLMNs, or a list of networks considered equivalent to the home network for network selection purposes. The "read binary command" is a specific command sent to the eUICC to read the binary data contained in the EF_EHPLMN file. The "command response" is the data returned by the eUICC after the "read binary command" has been executed. Therefore, the "EF_EHPLMN file read binary command response" refers to the list of EHPLMNs returned by the eUICC after the read binary command is executed on the EF_EHPLMN file.

[0055] Subsequently, the accumulated private EHPLMN list is transferred from the eUICC to the UE as if it were the EHPLMN list of the currently enabled public profile. At this point, the UE interprets the private networks contained in the accumulated private EHPLMN list as home networks, i.e., preferred networks.

[0056] When the UE is in an area where only the MNO's public network exists and the OEM's private network does not exist, the UE will attach to or connect to the MNO's public network as usual. "Event Location Status" is a notification or update triggered when the UE's network location changes. For example, this may occur when the UE moves from one cell to another, or from one tracking area to another.

[0057] Once the UE enters an area containing both public and private networks, it establishes an event and transmits it to the eUICC. If the UE attaches to a non-home network (i.e., not one of the networks listed in the EHPLMN), the UE will periodically scan for higher-priority networks (i.e., those from the EHPLMN) according to the ETSI specification. Once such a network is found, the UE will attempt to attach to it. Regardless of the attachment outcome, the UE will send an event location status and / or network rejection event to the eUICC, notifying the eUICC of the attachment attempt. Accordingly, the "event location status" will be triggered and transmitted to the eUICC. This will allow the eUICC to retrieve the MCC / MNC of the network the UE attempted to attach to (either directly from the event data or by actively sending a "Provide Local Information" command to the UE). Knowing the MCC / MNC, the eUICC will be able to perform all further activities. Specifically, the eUICC performs step S21, receiving the event from the UE. Subsequently, if these values ​​are present in the event, the eUICC performs step S22, extracting the MCC / MNC values ​​contained in the event. In the event of a rejection during an attach attempt (i.e., when the network does not allow the UE to attach to it), the event location state will not contain the MCC / MNC value. However, in this case, the MCC / MNC value can still be retrieved using the active command to provide local information. Alternatively, in the case of rejection, the MCC / MNC value can be extracted using the network rejection event (which contains the MCC / MNC value). Generally, extracting the MCC / MNC value refers to one of these methods for obtaining the MCC / MNC value. After extracting the value, the eUICC further performs step S23, which searches the accumulated private EHLMN list to find a value that matches the extracted MCC / MNC value. If a matching value is found in the accumulated private EHLMN list, the eUICC performs step S24, which identifies the private profile corresponding to the matching value in the accumulated private EHLMN table. Figure 3 As shown in the image.

[0058] After identifying the private profile, the eUICC seamlessly / automatically switches the operation profile to the private profile to activate the S25 private profile, which contains the appropriate credentials for successful attachment. This step includes a refresh operation implemented by a "refresh active command," which is a command used by the eUICC to request a device reset, reload files, or update applications stored on the eUICC.

[0059] "Private" and "public" can also be understood in a broad sense. That is, if a corresponding network (private network) exists, then the "private profile" can be understood as the profile that eUICC should switch to. The "public profile" can be understood as the default profile—also the fallback profile—which should be enabled when the currently enabled private profile has no connectivity.

[0060] Figure 3 The process of configuring a list of private profiles, which is sorted in the desired order based on one or more operation profile filtering conditions contained in a table.

[0061] exist Figure 3 The left-hand section contains several private configuration files: Configuration File 1, Configuration File 2, Configuration File 3, and Configuration File 4. These private configuration files can be pre-loaded onto the eUICC during production. Each configuration file has its own list of EHPLMNs contained in "EF_EHPLMN". The EHPLMN list is used by the UE when a network selection is required. Each EHPLMN list contains multiple PLMNs. A Public Land Mobile Network (PLMN) is a mobile network managed by an operator. Each PLMN is identified by a combination of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). This MCC-MNC combination uniquely identifies the mobile network operator in a specific country. EF_EHPLMN contains three PLMNs: PLMN 1-1, PLMN 1-2, and PLMN 1-3, where 1-1 indicates that it is the first PLMN in Configuration File 1, and 1-2 indicates that it is the second PLMN in Configuration File 1.

[0062] exist Figure 3 The middle section provides a list of profile entries based on the priority order of the Priv_Profile[] table (private profile[] table). This Priv_Profile[] table is configured by the eUICC application and contains one or more operational profile filtering conditions. Conditions can be expressed as "profile IMSI matches pattern 'XXX…X' and / or profile ISD AID matches pattern 'YYY…Y' and / or ICCID matches pattern 'ZZZ…Z'". Based on preset conditions, profile 2 is set to take precedence over profile 3, profile 3 is set to take precedence over profile 1, and profile 4 is not included.

[0063] exist Figure 3The right-hand side provides a cumulative private EHPLMN table, generated by traversing the private profile entries in the middle section according to their priority order. In this case, the priority order is profile 2, profile 3, and profile 1, as set in the middle section. As a result, the cumulative private EHPLMN table contains two columns: a left column and a right column. The left column is a list of cumulative private EHPLMNs containing the contents of the "EF_EHPLMN" files for profiles 2, 3, and 1, arranged in the priority order set in the middle section. The right column contains the profile from which the corresponding PLMN (a combination of MCC and MNC) originates. Figure 2 As shown on the right, “PLMN 2-1” in the left column comes from “Profile 2”, and “PLMN 3-1” in the left column comes from “Profile 3”.

[0064] The method described in the above embodiments allows the eUICC application to first internally collect EHPLMNs from all private and disabled profiles stored on the eUICC to generate an accumulated private EHPLMN list, and then transmit the accumulated private EHPLMN list to the UE as if it were the EHPLMN list of the currently enabled public profile. Therefore, an effective solution is provided for detecting the presence of a private network and forcing the eUICC to switch its operating profile to the private profile corresponding to the private network to allow successful attachment.

[0065] In the foregoing specification, the invention has been described with reference to specific embodiments thereof. However, it will be apparent that various modifications and alterations can be made thereto without departing from the broader scope of the invention. For example, the above process flow has been described with reference to a specific sequence of process actions. However, the order of many described process actions can be changed without affecting the scope or operation of the invention. Therefore, the specification and drawings are to be considered illustrative rather than restrictive.

Claims

1. A method for allowing a user device (UE) to automatically attach to or connect to a private network using an embedded general-purpose integrated circuit card (eUICC), the method comprising: - The eUICC application prioritizes (S10) the private network by replacing (S15) the content of the public equivalent home public land mobile network (EHPLMN) in the public profile with a cumulative private EHPLMN list containing the private network; and When the UE attempts to attach or connect to the private network, the eUICC switches (S20) to a private profile corresponding to the private network, while the public profile remains enabled, wherein the private profile contains credentials for the attachment or connection.

2. The method according to claim 1, wherein, The private network mentioned in the prioritization (S10) also includes: - When the UE reads the EF_EHPLMN file during its initialization, the eUICC application hijacks (S14) the binary command response for reading the EF_EHPLMN file of the public configuration file.

3. The method according to claim 1 or 2, wherein, The private network mentioned in the prioritization (S10) also includes: -A list of private profile entries containing one or more operation profile filtering conditions, provided by the eUICC application configuration (S11); - When the UE starts, the eUICC application traverses (S12) the private configuration file entries; and - An accumulated private EHPLMN table is constructed by the eUICC application (S13), the accumulated private EHPLMN table containing the accumulated private EHPLMN list, the accumulated private EHPLMN list including EHPLMN entries from each private configuration file and their corresponding private configuration files.

4. The method according to any one of the preceding claims, wherein, The private configuration file for switching to the private network includes: - The eUICC receives the event from the UE (S21); - The mobile country code (MCC) / mobile network code (MNC) value is extracted (S22) from the data of the event by the eUICC; - The value that matches the extracted MCC / MNC value obtained by the eUICC search (S23); - The private configuration file is identified by the eUICC based on the searched value (S24); and - The private configuration file is activated by the eUICC (S25).

5. The method according to any one of the preceding claims, wherein, The filtering conditions for the one or more operation configuration files include: -Whether the International Mobile Subscriber Identity (IMSI) profile matches the pre-defined pattern; and / or - Whether the ISDP Access Identifier (AID) in the configuration file matches the predefined pattern; and / or - Check if the configuration file's integrated circuit card identifier (ICCID) matches the predetermined pattern.

6. The method according to any one of the preceding claims, wherein, The credentials are network authentication parameters or values ​​used to attach to the network.

7. The method according to any one of the preceding claims, wherein service N°71 is enabled by the eUICC application by adjusting the corresponding value in the USIM service table file, i.e., the UST file.

8. The method according to any one of the preceding claims, wherein, The cumulative private EHPLMN list is derived from the individual EHPLMN of each private configuration file.

9. An embedded general-purpose integrated circuit card (eUICC) application for allowing a user device (UE) to attach to or connect to a private network, configured as follows: - Enables the UE to prioritize the private network by replacing the content of the Public Equivalent Home Public Land Mobile Network (EHPLMN) with a cumulative private EHPLMN list containing the private network, and When the UE attempts to attach or connect to the private network, the eUICC is enabled to switch to a private profile corresponding to the private network, while the public profile remains enabled, wherein the private profile contains credentials for the attachment or connection.

10. The eUICC application according to claim 9, wherein, The eUICC application is also configured to hijack the read binary command response of the EF_EHPLMN file when the UE reads the EF_EHPLMN file of the public configuration file during its initialization.

11. The eUICC application according to claim 9 or 10, wherein, in order to enable the UE to prioritize the private network, the eUICC application is further configured as follows: - Configure a list of private configuration file entries containing one or more operation configuration file filter conditions; - When the UE starts, iterate through the private configuration file entries; - Construct a cumulative private EHPLMN table, which contains a cumulative private EHPLMN list, which includes EHPLMN entries from each private configuration file and their corresponding private configuration files; - Return the cumulative private EHPLMN list to the UE.

12. The eUICC application according to any one of claims 9 to 11, wherein the eUICC application is configured to enable services for EHPLMN and N°71.

13. The eUICC application according to any one of claims 9 to 12, wherein the eUICC application is configured to derive the cumulative private EHPLMN list from a separate EHPLMN of each private profile.

14. An eUICC comprising an eUICC application according to any one of claims 9 to 13.

15. A computer program product comprising instructions that, when executed by a computer, cause the computer to allow a user device (UE) to automatically attach to or connect to a private network by using an embedded general-purpose integrated circuit card (eUICC) application: - The eUICC application prioritizes the private network by replacing the content of the Public Equivalent Home Public Land Mobile Network (EHPLMN) with a cumulative list of private EHPLMNs containing the private network; and When the UE attempts to attach or connect to the private network, the eUICC switches to a private profile corresponding to the private network, while the public profile remains enabled, wherein the private profile contains credentials for the attachment or connection.

Images