Dynamic control of SIM proactive-command communication

By sending a custom terminal profile or response error code to the SIM, the method prevents unwanted proactive-command transmission from the SIM, conserving resources during undesirable operational states.

WO2026235699A1PCT designated stage Publication Date: 2026-11-12GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2025/028464
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-08
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

SIMs in mobile terminals continue to send proactive commands even when the mobile terminal is in operational states where such transmissions are undesirable, such as low battery, non-terrestrial-network service mode, emergency mode, or airplane mode, leading to unnecessary resource consumption.

Method used

The mobile terminal sends a custom terminal profile to the SIM indicating it does not support proactive commands, or includes a response error code to terminate the session, preventing further transmissions.

Benefits of technology

Effectively blocks proactive-command transmission from the SIM during undesirable operational states, conserving battery and network resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2025028464_12112026_PF_FP_ABST
    Figure US2025028464_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Methods and systems for controlling proactive SIM communication in a mobile terminal. The mobile terminal determines that it is operating in a service mode in which proactive command transmission from the SIM should be blocked. In response, the mobile terminal sends to the SIM a message that provides the SIM with false information that results in blocking of proactive-command transmission. For instance, the mobile terminal may send to the SIM a custom terminal-profile that makes the SIM perceive that the mobile terminal does not support proactive-command transmission even though the mobile station actually does, and / or the mobile terminal may send to the SIM in response to a proactive command a TERMINAL RESPONSE that reports an error even though there is not actually an error, the reported error causing the SIM to not retransmit the proactive command.
Need to check novelty before this filing date? Find Prior Art

Description

Dynamic Control of SIM Proactive-Command Communication BACKGROUND

[0001] A SIM (Subscriber Identity Module) in a mobile terminal (i.e., mobile equipment (ME)) typically serves as a secure element that stores critical information to authenticate a subscriber on a mobile network. It holds unique identifiers such as the International Mobile Subscriber Identity (IMSI) and a secret authentication key, which are used by the network to verify the legitimacy of a user. Depending on the mobile terminal type, this may enable access to voice, text, data, and / or other services.

[0002] A SIM usually takes the form of a secure microcontroller chip. As such, the SIM may include a SIM processor and SIM data storage. When the SIM is situated in its host mobile terminal, a logical and physical interface called the SIM-ME interface provides a channel through which the SIM communicates with the host terminal, such as with a modem or host processor of the terminal for instance. Further, a SIM Application Toolkit (STK) defines a set of commands and procedures defined by the SIM card that allows it to interact with the mobile terminal.

[0003] Traditionally, SIM cards are physical, removable chips (pSIMs) that can be transferred between devices, allowing users to retain their mobile identity and settings even when switching devices. With the evolution of mobile technology, eSIM (embedded SIM) has also emerged as a flexible and efficient alternative. Unlike traditional SIM cards, eSIMs are embedded directly into the device's hardware and cannot be physically removed. Instead of swapping cards, users can download SIM profiles over the air, making it easier to switch carriers or manage multiple profiles (e.g., personal and business numbers) without needing multiple pSIMs.

[0004] As used herein, the term “SIM” encompasses both pSIM and eSIM.SUMMARY

[0005] At times, a SIM in a mobile terminal may proactively initiate a messaging session between the SIM and the mobile terminal. (This communication between the SIM and the mobile terminal is between the SIM and an element of the mobile terminal other than SIM, such as between the SIM and a modem or host processor of the mobile terminal.) To facilitate this, the STK may define a set of “proactive commands” that the SIM can transmit to the mobile terminal. Examples of these proactive commands include, without limitation, “OPEN1CHANNEL”, “SEND DATA”, and “REFRESH”. The OPEN CHANNEL command instructs the mobile terminal to open a new communication channel, usually over a cellular-wireless link or possibly a Wi-Fi or other link. The SEND DATA command instructs the mobile terminal to send data over a previously opened channel. And the REFRESH command instructs the mobile terminal to update itself, such as when SIM state has changed.

[0006] In practice, the mobile terminal may support some or all of the proactive commands defined by the STK. In order for the SIM to know which proactive commands the SIM can send to the mobile terminal, the mobile terminal may send to the SIM over the SIMMS interface, upon power up or SIM reset, a TERMINAL PROFILE message that carries a terminal profile of the mobile terminal, informing the SIM of the mobile terminal’ s capabilities, including which of proactive commands the mobile terminal supports the SIM sending to the mobile terminal. When the SIM receives this TERMINAL PROFILE message, the SIM reads and stores the provided terminal profile, thus effectively becoming configured with settings of which proactive commands the SIM can send to the mobile terminal.

[0007] To send a proactive command to the mobile terminal over the SIM-ME interface, the SIM first sends a status word such as 91xx to the mobile terminal to indicate that the SIM has a proactive command to send. The mobile terminal then responds to this status word by sending a FETCH command to the SIM. And the SIM responds to the FETCH by sending the proactive command to the mobile terminal.

[0008] Once the mobile terminal receives a proactive command from the SIM, the mobile terminal may then take action in accordance with the proactive command if possible. For instance, in response to receiving from the SIM an OPEN CHANNEL command, the mobile terminal may open a communication channel with a serving cellular wireless network. Likewise, in response to receiving from the SIM a SEND DATA command providing data to be transmitted on a channel, the mobile terminal may transmit the data on the channel.

[0009] Further, as a response to the proactive command, the mobile terminal may send to the SIM a TERMINAL RESPONSE that indicates whether the mobile terminal successfully carried out the indicated action. In particular, the mobile terminal may include in the TR a result value (e.g., a byte) that may indicate a result such as successful performance of the command, limited or no performance of the command, or an error preventing performance of the command, among other possibilities.

[0010] From time to time, the mobile terminal may be in an operational state in which it would be desirable for the SIM to not engage in proactive-command transmission to2the mobile terminal, i.e., in which the SIM should not engage in proactive-command transmission. Examples of these operational states include, without limitation, the mobile terminal having threshold low remaining battery energy, the mobile terminal operating in a non-terrestrial-network (NTN) service mode, the mobile terminal operating in an emergency mode, and the mobile terminal operating in airplane mode.

[0011] When the mobile terminal’s remaining battery energy is threshold low, it may be desirable to avoid having the SIM engage in proactive-command transmission to the mobile terminal, since a proactive command from the SIM may cause the mobile terminal to engage in action that may consume more battery energy. Further, when the mobile terminal is operating in an NTN service mode, the mobile terminal’s air-interface bandwidth and / or other resources may be especially limited, so it may be desirable in that situation as well to avoid having the SIM engage in proactive-command transmission to the mobile terminal. Likewise, when the mobile terminal is operating in an emergency mode, such as working to engage in an emergency communication, it may be desirable to avoid having the SIM engage in proactivecommand transmission, to avoid associated use of mobile terminal resources that may be better devoted to the emergency situation. In addition, when the mobile terminal is operating in airplane mode (e.g., in which the mobile terminal will not engage in cellular air-interface communication), it may be desirable to avoid having the SIM engage in proactive-command transmission, to avoid unnecessary use of mobile terminal processing resources.

[0012] A technical problem, however, is that the SIM may continue to send proactive commands to the mobile terminal even in these or other operational states. Therefore, a solution is desired.

[0013] The present disclosure provides a technical solution as one or more mechanisms for helping to block proactive-command transmission from a SIM when the SIM’ s host mobile terminal is operating in a mode in which proactive-command transmission from the SIM should be blocked.

[0014] In a first respect, disclosed is a method for controlling proactive-command transmission by provisioning the SIM with a terminal profile that makes the SIM perceive that its host mobile terminal does not support proactive-command transmission from the SIM even though the mobile terminal does actually support proactive-command transmission from the SIM.

[0015] More particularly, an example method provides for controlling proactivecommand transmission within a mobile terminal, from a SIM of the mobile terminal, where the3mobile terminal supports proactive-command transmission from the SIM. The method includes (i) determining that the mobile terminal is operating in a service mode in which proactivecommand transmission from the SIM should be blocked and (ii) responsive to the determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked, sending to the SIM a terminal profile specifying that the mobile terminal does not support proactive-command transmission from the SIM. The terminal profile specifying that the mobile terminal does not support proactive-command transmission from the SIM is interpretable by the SIM to cause the SIM to not engage in proactive-command transmission.

[0016] In some implementations, this example method may apply with respect to all available proactive commands from the SIM (e.g., all proactive commands defined by the STK). In other implementations, this may apply with respect to just a proper subset of all available proactive commands from the SIM, possibly excluding one or more proactive commands that it would be useful to let the SIM continue to be able to transmit (such as the REFRESH command for instance).

[0017] In another respect, disclosed is a method for controlling proactive-command transmission within a mobile terminal, from a SIM in the mobile terminal. The method includes the mobile terminal determining that the mobile terminal is operating in a service mode in which proactive-command transmission from the SIM should be blocked, and, responsive to the determining that the mobile terminal is operating in the service mode in which proactivecommand transmission from the SIM should be blocked, the mobile terminal including, in a TERMINAL RESPONSE that the mobile terminal sends to the SIM in response to a proactive command transmitted by the SIM, a response error code that is interpretable by the SIM to cause the SIM to not retransmit the proactive command.

[0018] In yet another respect, disclosed is a computing system including at least one processor, non-transitory data storage, and program instructions stored in the non-transitory data storage and executable by the at least one processor to carry one or more of these methods. Further, in yet another respect, disclosed is at least one non-transitory computer-readable medium embodying program instructions executable by at least one processor to carry out one or more of these methods. And in still another respect, disclosed is a computer program product comprising instructions executable by at least one processor to carry out one or more of these methods.

[0019] These as well as other aspects, advantages, and alternatives will become apparent to those of ordinary skill in the art by reading the following detailed description, with reference where appropriate to the accompanying drawings. Further, it should be understood that the descriptions provided in this summary and below are intended to illustrate the invention by way of example only and not by way of limitation.BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a flow diagram illustrating an example method for controlling proactive-command transmission in a mobile terminal.

[0021] Figure 2 is a flow diagram illustrating an example method for controlling a proactive session in a mobile terminal.

[0022] Figure 3 is a simplified block diagram of an example computing system.

[0023] Figure 4 is a simplified block diagram of an example mobile terminal.

[0024] Figure 5 is a simplified block diagram illustrating terrestrial and nonterrestrial network service arrangements.DETAILED DESCRIPTION

[0025] The present disclosure will discuss example implementation in relation to a mobile terminal, which may be a smartphone, a wearable device, an Internet of Things (loT) device, an embedded wireless device, or other mobile equipment. It will be understood, however, that the disclosed principles can apply in other contexts as well, not limited to the disclosed embodiments.

[0026] Further, it will be understood that variations from the specific arrangements and processes disclosed are possible. For instance, various disclosed entities, components, connections, operations, and other elements can be added, omitted, distributed, replicated, relocated, re-ordered, combined, or changed in other ways. In addition, it will be understood that various disclosed technical operations can be implemented at least in part by a processing unit programmed to carry out the operations or to cause one or more other entities to carry out the operations.

[0027] Referring to the drawings, as noted above, Figure 1 is a flow diagram illustrating an example method for controlling proactive-command transmission from a SIM 100 in a mobile terminal 102. In particular, this flow diagram depicts actions of and communication between the SIM 100 and the mobile terminal 102 for controlling proactive-command transmission from the SIM 100 to the mobile terminal 102, e.g., to a host processor or modem of the mobile terminal 102.

[0028] As shown in Figure 1, at block 104, this example method begins in a scenario where the SIM 100 is configured with a default terminal profile A of the mobile terminal 102. For instance, on power-up or upon SIM reset, the mobile terminal 102 may have sent to the SIM 100 a TERMINAL PROFILE message providing the SIM with a default terminal profile A of the mobile terminal 102, and the SIM 100 may have read and stored that default terminal profile A and therefore be configured with settings indicating a plurality of proactive commands that mobile terminal supports the SIM 100 transmitting to the mobile terminal 102 and thus that the SIM 100 can send to the mobile terminal 102. For one reason or another, this default terminal profile A may also indicate lack of support for one or more proactive commands. However, for present purposes, an assumption in the example method is that the default terminal profile A indicates the plurality of proactive commands that are supported.

[0029] In this scenario, at block 106, the mobile terminal 102 determines (e.g., detects) that the mobile terminal 102 is operating in a mode in which proactive-command transmission from the SIM 100 to the mobile terminal 102 should be blocked - e.g., that one or more proactive commands of the plurality of proactive commands should be blocked, possibly that all proactive-command transmission from the SIM 100 to the mobile terminal 102 should be blocked.

[0030] As noted above, examples of this mode include the mobile terminal 102 operating with threshold low remaining battery energy, the mobile terminal 102 operating with NTN service, the mobile terminal 102 operating in engaged in an emergency communication, and the mobile terminal 102 operating in airplane mode, among other possibilities. The designation of a given such mode as being one in which proactive-command transmission from the SIM 100 to the mobile terminal 102 should be blocked may be an engineering decision, and the mobile terminal 102 may be configured accordingly. The mobile terminal 102 may then determine that the mobile terminal is operating in such a mode, without a need for the mobile terminal 102 to determine that the mode is one in which proactive-command transmission should be blocked.

[0031] At block 108, in response to the mobile terminal 102 determining that the mobile terminal 102 is operating in a mode in which proactive-command transmission from the SIM 100 to the mobile terminal 102 should be blocked, the mobile terminal 102 sends to the SIM 100, over the SIM-ME interface for instance, a TERMINAL PROFILE message6carrying a custom terminal profile B that makes the SIM 100 perceive the mobile terminal 102 as not supporting proactive-command transmission from the SIM 100 to the mobile terminal 102, even though the mobile terminal 102 actually does support the proactive-command transmission. This custom terminal profile B thus serves to newly block transmission from the SIM 100 to the mobile terminal 102 of one or more proactive commands of the plurality of proactive commands that were not blocked under the default terminal profile A. Thus, the mobile terminal 102 provides false information to the SIM 100 in order to help achieve this goal.

[0032] At block 110, in response to receiving this custom terminal profile B from the mobile terminal 102, the SIM 100 accordingly becomes configured to avoid the indicated proactive-command transmission to the mobile terminal 102, such as by storing in the SIM 100 the received custom terminal profile B. Therefore, in a scenario when the SIM 100 might otherwise transmit one of the indicated proactive commands to the mobile terminal 102 as allowed by the default terminal profile A, the SIM 100 will forgo doing so, because the SIM’s records, based on this custom terminal profile B, will indicate that the mobile terminal 102 does not support such proactive-command transmission.

[0033] At block 112, the mobile terminal 102 then determines that the mobile terminal 102 is no longer operating in the mode in which the proactive-command transmission from the SIM 100 to the mobile terminal 102 should be blocked. For instance, with the examples above, this may involve the mobile terminal 102 determining that the mobile terminal 102 is no longer operating with threshold low remaining battery energy (e.g., that the mobile terminal 102 battery is now charging or has been recharged), that the mobile terminal 102 is no longer operating with NTN service (e.g., that the mobile terminal has moved out of NTN service and possibly into terrestrial-network (TN) service), that the mobile terminal 102 is no longer engaged in an emergency communication, and / or that the mobile terminal 102 is no longer operating in airplane mode, among other possibilities.

[0034] At block 114, in response to the mobile terminal 102 determining that the mobile terminal 102 is no longer operating in the mode in which proactive-transmission from the SIM 100 to the mobile terminal 102 should be blocked, the mobile terminal 102 then reverses the blocking process, by again sending to the SIM 100 the mobile terminal’s default terminal profile A. At block 116, the SIM 100 thus reverts to be configured with the mobile terminal’s default terminal profile A. At this point, in a scenario when the SIM 100 wouldtransmit one of the indicated proactive commands to the mobile terminal 102, the SIM 100 will do so as allowed by the default terminal profile A.

[0035] Accordingly, as discussed above, a method of controlling proactivecommand transmission within a mobile terminal, from the SIM 100 of the mobile terminal 102, where the mobile terminal 102 supports proactive-command transmission from the SIM 100 (e.g., particular proactive-command transmission from the SIM 100), involves (i) determining that the mobile terminal 102 is operating in a service mode in which proactive-command transmission from the SIM 100 should be blocked (e.g., that the particular proactive-command transmission from the SIM 100 should be blocked) and (ii) responsive to the determining that the mobile terminal 102 is operating in the service mode in which proactive-command transmission from the SIM 100 should be blocked, sending to the SIM 100 a terminal profile that specifies that the mobile terminal 102 does not support proactive-command transmission from the SIM 100 (e.g., that the mobile terminal 102 does not support the particular proactivecommand transmission from the SIM 100). Thus, even though the mobile terminal 102 in fact supports the proactive-command transmission from the SIM 100, the sending of this terminal profile specifying that the mobile terminal 102 does not support the proactive-command transmission from the SIM 100 is interpretable by the SIM 100 to cause the SIM 100 to not engage in the proactive-command transmission to the mobile terminal 102.

[0036] Further, upon thereafter determining that the mobile terminal 102 is no longer operating in the mode in which the proactive-command transmission from the SIM 100 should be blocked, the method may then involve reverting configuration of the SIM 100 by sending to the SIM 100 a default terminal profile of the mobile terminal 102.

[0037] In an example implementation as noted above, the proactive-command transmission from the SIM 100 can be proactive-command transmission from the SIM 100 to a modem of the mobile terminal 102. Further, the method can be carried out by the modem of the mobile terminal 102. Alternatively, the proactive-command transmission from the SIM 100 can be proactive-command transmission from the SIM 100 to a host processor of the mobile terminal 102, and the method can be carried out by the host processor, among other possibilities.

[0038] Further, as discussed above, the act of determining that the mobile terminal 102 is operating in the service mode in which proactive-command transmission from the SIM 100 should be blocked can involve determining that the mobile terminal 102 is operating in a NTN mode, determining that the mobile terminal 102 is operating with threshold low batteryenergy, determining that the mobile terminal 102 is operating in an emergency-communication mode, and / or determining that the mobile terminal is operating in an airplane mode, among other possibilities.

[0039] In addition, under a representative STK, the terminal profile that gets sent to the SIM 100 can take the form of a bit string in which bits indicate mobile terminal capabilities. For instance, each bit of a plurality of bits at predefined bit positions in the string may correspond with a respective capability, with a bit value of one indicating that the mobile terminal 102 has that capability and a bit value of zero indicating that the mobile terminal 102 does not have that capability.

[0040] At least a group of these bits may correspond with specific proactive commands, with their bit values indicating whether or not the mobile terminal 102 supports those proactive commands. Thus, the mobile terminal 102 can indicate whether or not the mobile terminal 102 supports the SIM 100 sending a particular proactive command by the mobile terminal 102 specifying an appropriate bit value as the bit corresponding with that particular proactive command.

[0041] For instance, a predefined bit in the terminal profile may correspond with the OPEN CHANNEL command, so the mobile terminal 102 may configure the terminal profile with that bit having a value of one to indicate that the mobile terminal 102 supports the SIM 100 sending the OPEN CHANNEL command to the mobile terminal 102 or with that bit having a value of zero to indicate that the mobile terminal 102 does not support the SIM 100 sending the OPEN CHANNEL command to the mobile terminal 102. Likewise, another predefined bit in the terminal profile may correspond with the SEND DATA command, so the mobile terminal 102 may configure the terminal profile with that bit having a value of one to indicate that the mobile terminal 102 supports the SIM 100 sending the SEND DATA command to the mobile terminal 102 or with that bit having a value of zero to indicate that the mobile terminal 102 does not support the SIM 100 sending the SEND DATA command to the mobile terminal 102. Further, another predefined bit in the terminal profile may correspond with the REFRESH command, so the mobile terminal 102 may configure the terminal profile with that bit having a value of one to indicate that the mobile terminal 102 supports the SIM 100 sending the REFRESH command to the mobile terminal 102 or with that bit having a value of zero to indicate that the mobile terminal 102 does not support the SIM 100 sending the REFRESH command to the mobile terminal 102, and similarly for other proactive commands.

[0042] Accordingly, in the example method, the act of the terminal profile specifying that the mobile terminal 102 does not support proactive-command transmission from the SIM 100 can involve each bit of the plurality of bits in the terminal profile being configured with a value that indicates that the mobile terminal 102 does not support SIM 100 transmission of the respective proactive command with which the bit corresponds.

[0043] If the SIM 100 in the example method is a pSIM, a technically efficient way to stop proactive-command transmission from the SIM 100 to the mobile terminal 102 is to configure the terminal profile as a null profile, simply by configuring all bits in the profile with a value of zero. Sending to the SIM 100 a null terminal profile effectively indicates to the SIM 100 that the mobile terminal 102 has none of the capabilities indicated by the bit positions in the profile. As a result, the SIM 100 should then not send any proactive commands to the mobile terminal 102.

[0044] If the SIM 100 in the example method is an eSIM, however, then it may be technically useful to at least retain an indication of mobile terminal support for the REFRESH proactive command, as it may be important to allow the SIM 100 to send the REFRESH command to the mobile terminal 102 when the SIM’s state change (e.g., when the SIM 100 switches mobile-carrier profiles, possibly at user direction, among other possibilities). Therefore, in the terminal profile that gets sent to the SIM 100 in the example method, even though the bits for other proactive commands may be configured with a value of zero, a useful implementation would be to keep the REFRESH-command bit configured with a value of one. Thus, the proactive-command transmission that the terminal profile specifies the mobile terminal 102 does not support can usefully exclude at least the REFRESH proactive command that the SIM 100 supports sending to the mobile terminal 102 in response to a state change at the SIM 100.

[0045] Further, another bit in the terminal profile may indicate whether the mobile terminal 102 supports the REFRESH command indicating profile state change of the SIM 100. This relates to a change of carrier profile, e.g., when the mobile terminal 102 sends to the SIM 100 a command (e.g., BF31) for the SIM 100 to switch from one carrier profile (i.e., mobile network operator (MNO) profile) to another.

[0046] If this bit of the terminal profile indicates that the mobile terminal 102 supports profile state change, then, when SIM 100 changes from one carrier profile to another, the SIM 100 may include in its REFRESH command to the mobile terminal 102 a predefined refresh-type value (e.g., 09) that indicates a profile-state change, and the mobile terminal 10210may responsively simply update the mobile terminal’s records, without resetting the SIM 100. Whereas, if this bit of the terminal profile indicates that the mobile terminal 102 does not support this, then, when the SIM 100 changes from one carrier profile to another, the SIM 100 may instead include in its REFRESH command to the mobile terminal 102 a different predefined refresh-type value (e.g., 04) that indicates a SIM reset, and the mobile terminal 102 may responsively update its records and reset the SIM 100, such as by power-cycling (e.g., cold-rebooting) the SIM 100.

[0047] If the mobile terminal 102 supports an indication of profile state change in a REFRESH command from the SIM 100, it would be technically useful to also retain an indication of that mobile terminal support, to facilitate having the SIM 100 include the profile-state-change refresh-type value in the SIM’s REFRESH command to the mobile terminal 102. Allowing the SIM 100 to include this profile-state-change refresh-type value is technically useful, as that will help to avoid a need for the mobile terminal 102 to reset the SIM 100, which would be a time consuming process that may create user-experience issues if applicable.

[0048] Therefore, in the terminal profile that gets sent to the SIM 100 in the example method, even though the bits for various proactive commands may be configured with a value of zero, a useful implementation would be to keep the REFRESH-command bit configured with a value of one and to also keep configured with a value of one the bit corresponding with including in the REFRESH command a profile-state-change refresh-type value. Thus, the proactive-command transmission that the terminal profile specifies the mobile terminal 102 does not support can usefully exclude at least a PROFILE-STATE-CHANGE REFRESH proactive command that the SIM 100 supports sending to the mobile terminal 102 in response to an MNO profile state change at the SIM 100.

[0049] Figure 2 is next a flow diagram illustrating another example method for controlling proactive-command transmission within a mobile terminal, from a SIM in the mobile terminal. This flow diagram also depicts actions and communications between the SIM 100 and the mobile terminal 102, such as between the SIM 100 and a host processor or modem of the mobile terminal 102.

[0050] The flow diagram of Figure 2 relates to a proactive session in which the mobile terminal 102 receives from the SIM 100 a proactive command and the mobile terminal 102 sends to the SIM 100 a TERMINAL RESPONSE in response to the proactive command and includes in the TERMINAL RESPONSE a result value as indicated above. This example11method functions to end the proactive session and prevent the SIM 100 from retransmitting the proactive command to the mobile terminal 102.

[0051] As shown in Figure 2, at block 200, the example method involves the mobile terminal 102 determining (e.g., detecting) that the mobile terminal 102 is operating in a mode in which proactive-command transmission from the SIM 100 should be blocked. Examples of this mode include the modes noted above, namely, the mobile terminal 102 operating with threshold low remaining battery energy, the mobile terminal operating in an NTN mode, the mobile terminal 102 operating in an emergency-communication mode, and the mobile terminal operating in an airplane mode, among other possibilities. The designation of a given such mode as being one in which a proactive session between the SIM 100 and the mobile terminal 102 should be terminated may be an engineering decision, and the mobile terminal 102 may be configured accordingly. The mobile terminal 102 may then determine that the mobile terminal is operating in such a mode, without a need for the mobile terminal 102 to determine that the mode is one in which proactive-command transmission should be blocked.

[0052] And at block 202, the example method involves, responsive to determining that the mobile terminal 102 is operating in the service mode in which proactive-command transmission from the SIM should be blocked, the mobile terminal 102 including, in aTERMINAL RESPONSE that the mobile terminal 102 sends to the SIM 100 in response to a proactive command transmitted by the SIM, a response error code that is interpretable by the SIM 100 to cause the SIM 100 to not retransmit the proactive command. At block 204, the SIM 100 thus ends the proactive session and does not retransmit the proactive command to the mobile terminal 102.

[0053] As with the method of Figure 1, this method may involve the mobile terminal 102 providing the SIM 100 with false information in order to help avoid transmission of a proactive command, in this case specifically re-transmission of a proactive command. In particular, in this method, the response error code that the mobile terminal 102 includes in its TERMINAL RESPONSE to the SIM 100 may indicate that the mobile terminal 102 has encountered an error in processing the SIM’s proactive command even though the mobile terminal 102 has not actually encountered that error. A purpose of indicating this error in this method is, rather, to cause the SIM 100 to end the proactive session without retransmitting the proactive command to the mobile terminal 102.

[0054] In an example implementation of this method, as noted above, the proactivecommand transmission from the SIM 100 can be proactive-command transmission from the12SIM 100 to a modem of the mobile terminal 102. Further, the method can be carried out by the modem of the mobile terminal 102. Alternatively, the proactive-command transmission from the SIM 100 can be to a host processor of the mobile terminal 102, and the method can be carried out by a host processor, among other possibilities.

[0055] Further, the timing of this method can take various forms. In one implementation, for instance, the act of the mobile terminal 102 determining that the mobile terminal 102 is operating in the service mode in which proactive-command transmission from the SIM should be blocked is done upon the mobile terminal receiving the proactive command from the SIM. Thus, the mobile terminal 102 may receive the proactive command and then, in response to receiving the proactive command, may check to see if the mobile terminal 102 is in operating such a mode.

[0056] In another implementation, however, the act of the mobile terminal 102 determining that the mobile terminal 102 is operating in the service mode in which proactivecommand transmission from the SIM should be blocked is done before the mobile terminal 102 receives the proactive command from the SIM. For instance, the mobile terminal 102 may make this determination when the mobile terminal 102 enters into that mode of operation. In that case, the responsive action of the mobile terminal 102 can be forward-looking as to any proactive session that the SIM 100 may thereafter initiate.

[0057] Thus, the act of the mobile terminal responsively including the response error code in the TERMINAL RESPONSE can involve (i) responsive to the mobile terminal 102 determining that the mobile terminal 102 is operating in the service mode in which proactivecommand transmission should be blocked, the mobile-terminal responsively configuring itself (e.g., setting a flag in its memory) such that, when the mobile terminal 102 later receives the proactive command from the SIM 100, the mobile terminal 102 will include the response error code in its TERMINAL RESPONSE, and (ii) in accordance with that configuring, the mobile terminal 102 including the response error code in its TERMINAL RESPONSE when the mobile terminal 102 later receives the proactive command from the SIM 100.

[0058] In an example implementation, the STK may define multiple response error codes that are normally for use in certain error scenarios. For instance, STK may include a list of error codes such as the following: (i) Command beyond terminal's capabilities, (ii) Command type not understood by terminal, (iii) Command data not understood by terminal, (iv) Command number not known by terminal, and (v) Error, required values are missing.

[0059] To terminate a proactive session and avoid proactive-command retransmission when the mobile terminal 102 has determined that the mobile terminal 102 is operating in a service mode in which the proactive session should be terminated, the mobile terminal 102 may include one of these defined error codes in its TERMINAL RESPONSE to the SIM 100.

[0060] It is possible that the SIM 100 may treat one or more of these error codes as meaning that the SIM 100 should terminate the proactive session without retransmitting the proactive command to the mobile terminal 102, in which case the SIM 100 may reply to the mobile terminal 102 with a success message (e.g., codeword 9000), ending the proactive session. However, it is also possible that the SIM 100 may treat one or more of the error codes as meaning that something went wrong in processing of its proactive command and therefore that the SIM 100 should retransmit the proactive command to the mobile terminal 102, in which case the SIM 100 may reply to the mobile terminal 102 by sending a status word (e.g., 91xx) to trigger a new FETCH followed by the SIM resending the proactive command to the mobile terminal 102.

[0061] In an example implementation, the mobile terminal 102 may select one of the response error codes from the set of available response error codes and may include that selected response error code in its TERMINAL RESPONSE to the SIM 100.

[0062] If the mobile terminal 102 then receives a success reply (e.g., 9000) from the SIM 100 and thereby detects that that particular response error code worked to cause the SIM 100 to terminate the proactive session without retransmitting the proactive command, then the mobile terminal 102 may responsively configure itself such that, next time the mobile terminal 102 receives a proactive command from the SIM 100 while the mobile terminal is operating in the service mode in which the proactive session should be terminated, the mobile terminal will include the same selected response error code when responding to the SIM 100. For instance, the mobile terminal 102 may record that response error code in a database record for later use and may accordingly later use that same response error code to again achieve the goal of blocking proactive-command retransmission.

[0063] On the other hand, if the mobile terminal 102 instead receives from the SIM 100 a failure reply (e.g., a new 91xx status word, and possibly then a new transmission of the proactive command), then the mobile terminal 102 may proceed to select a new response error code from the set of available error codes and may attempt use of that next selected response error code in its TERMINAL RESPONSE to the SIM 100, repeating the process. In practice,14the mobile terminal 102 can cycle through trying to use all of the available response error codes (e.g., in the order noted above, among other possibilities) in this way. If none of the response error codes succeeds in terminating the proactive session, then the mobile terminal 102 may proceed to carry out the method of Figure 1 instead or may take other action.

[0064] Figure 3 is a simplified block diagram of a computing system showing some of the components that can be included in the computing system to facilitate carrying out the operations of these methods. This computing system may represent part of an example mobile terminal for instance.

[0065] As shown in Figure 3, the example computing system includes at least one processor 300 and non-transitory data storage 302, which can be communicatively linked together by a system bus or other connection mechanism 304 or can be integrated together. Further, the example computing system includes a SIM 306, having a dedicated secure connection 308 with the at least one processor 300 to facilitate secure SIM -ME communications between the SIM 306 and the at least one processor 300.

[0066] In an implementation where the example computing system is at a mobile terminal, the at least one processor 300 can comprise a host processor of the mobile terminal and / or a processor of a modem of the mobile terminal, among other possibilities. The at least one processor 300 may comprise one or more general purpose processors (e.g., microprocessors) and / or one or more specialized processors (e.g., digital signal processors (DSPs), graphics processing units (GPUs), neural processing units (NPUs), etc.) And the non-transitory data storage 302 may comprise one or more volatile and / or non-volatile storage components (e.g., flash, optical, magnetic, read only memory (ROM), random access memory (RAM) (e.g., dynamic RAM (DRAM), static RAM (SRAM), or double data rate RAM (DDRAM)), electronically programmable read only memory (EPROM), and / or electronically erasable programmable read only memory (EEPROM), etc.), which may be integrated in whole or in part with the processor 300 or may be provided separately.

[0067] As further shown, the non-transitory data storage 302 may store (e.g., hold or embody) program instructions 310. These program instructions 310 may be executable by the at least one processor 300 to cause the computing system to carry out various operations as described herein, such as but not limited to the operations of the methods illustrated in Figures 1 and 2.

[0068] In addition, the present disclosure also contemplates non-transitory data storage (e.g., one or more non-transitory computer-readable medium components (e.g., optical,15magnetic, or flash storage, RAM, ROM, EPROM, EEPROM, cache memory, and / or other computer-readable media, etc.)) that stores program instructions executable by a processor to cause at least one processor to carry out various operations described herein, such as but not limited to the operations of the methods illustrated in Figures 1 and 2.

[0069] Further, the present disclosure also contemplates a computer program product that comprises instructions executable by at least one processor to carry out the operations described herein, such as but not limited to the operations of the methods illustrated in Figures 1 and 2.

[0070] Figure 4 is next a simplified block diagram of a mobile terminal, showing in more detail some of the components that can be included in the mobile terminal to facilitate carrying out the disclosed operations.

[0071] As shown in Figure 4, the example mobile terminal includes a host processor (application processor) 400, host non-transitory data storage 402, user interface components 404, a modem 406, an antenna structure 408, a SIM 410, and a battery 412. In the example arrangement shown, the host processor 400, host non-transitory data storage 402, user interface components 404, and modem 406 are interconnected by a system bus 414. Further, those components as well as the SIM 410 are served by a power bus 416 supplied with energy from the battery 412. And the SIM 410 is shown having a secure SIM-MME connection 418 with the modem 406.

[0072] In an example implementation, the host processor 400 can take any of the processor forms noted above, and the host non-transitory data storage 402 can take any of the data storage forms noted above. As further shown, the host non-transitory data storage 402 can store program instructions 420, which can be executable by the host processor 400 to carry out various mobile terminal operations disclosed herein.

[0073] The user interface components 404 (if applicable depending on mobile terminal type) can include output components such as a display screen, a sound speaker, indicator lights, and a haptic feedback mechanism, and input components such as a touch screen, a microphone, and a keypad, among other possibilities.

[0074] The modem 406, together with the antenna structure 408 and possibly one or more other elements (not shown), operates to facilitate air-interface communication by the mobile terminal, such as communication with an access node, and communication in turn with other network infrastructure such as a cellular carrier’s core network for instance. Thesecomponents may cooperatively constitute one or more transmit / receive chains to facilitate one or more types of wireless service.

[0075] Without limitation, for instance, these modem components may facilitate terrestrial-network (TN) cellular service and non-terrestrial-network (NTN) cellular service. To do so, the modem 406 may include at least one modem processor 422, modem non-transitory data storage 424, and program instructions 426 stored in the modem non-transitory data storage 424 and executable by the modem processor 422 to carry out cellular-service-related operations. Further, the program instructions stored in the modem non-transitory data storage 424 may also be executable by the modem processor 422 to carry out various mobile terminal operations disclosed herein.

[0076] The SIM 410 also includes its own processing logic to facilitate carrying out SIM functions. Namely, the SIM 410 includes a SIM processor 428, SIM data storage 430, and program instructions 432 stored in the SIM data storage 430 and executable by the SIM processor 428 to carry out various SIM operations. Further, while not shown, the SIM data storage 430 may also store terminal profile and carrier profile data, among other information.

[0077] Figure 5 illustrates example arrangements of terrestrial and non-terrestrial cellular networks.

[0078] A traditional terrestrial cellular network may comprise multiple ground-based base stations or other access nodes 500 each configured to serve mobile terminals such as mobile terminal 102 over a respective terrestrial air interface 502 and to provide the mobile terminals with a path through which to communicate with a cellular core network 504. The cellular core network 504 may then facilitate communication between the mobile terminals and various endpoints, such as network services and other mobile terminals, among other possibilities. By way of example, one such endpoint may be an over-the-air (OTA) SIM provisioning server 506, which may operate to interact with the SIM in a served mobile terminal 102 to facilitate provisioning or updating a carrier profile on the SIM for instance.

[0079] A non-terrestrial cellular network, on the other hand, uses satellite access nodes 508 in place of terrestrial access nodes 500, which may usefully facilitate serving mobile terminals in situations where the mobile terminals are not within terrestrial cellular coverage. With this arrangement, the mobile terminal 102 may be served by a representative satellite access node 508 in the sky overhead, with an air interface 510 between the satellite access node 508 and the mobile terminal 102 being a “service link” and with the satellite access node 508 also having a backhaul air interface connection or “feeder link” 512 with an NTN gateway 514in the cellular core network 504. The satellite access node 508 can then be configured to function as a cellular access node just like a terrestrial access node 500, albeit over the satellite air interface 510, and / or as a relay access node, among other possibilities.

[0080] In practice, the mobile terminal 102 may regularly scan for presence of cellular coverage, preferring TN coverage. If the mobile terminal 102 finds sufficient TN coverage strength from a terrestrial access node 502, then the mobile terminal 102 may connect with that terrestrial access node 500 and then be served (whether idle or connected) in a TN service mode. Whereas, if the mobile terminal 102 does not find sufficient TN coverage strength, then, possibly upon user request if applicable, the mobile terminal 102 may scan for NTN coverage. And if the mobile terminal 102 finds sufficient NTN coverage strength from a satellite access node 508, then the mobile terminal 102 may connect with that satellite access node 508 and be served (whether idle or connected) in an NTN service mode.

[0081] In both TN and NTN service modes, from time to time the SIM 100 in the mobile terminal 102 may send to the mobile terminal a proactive command. For instance, the SIM 100 may send an OPEN CHANNEL command and SEND DATA command, to facilitate communication between the SIM 100 and the OTA provisioning server 506, such as to get a SIM update or the like. Unfortunately, having the SIM 100 cause the mobile terminal 102 to engage in these or other such actions while the mobile terminal is operating in an NTN service mode may be undesirable for the reasons discussed above. Therefore, when the mobile terminal 102 is operating in the NTN service mode, it may be useful to block proactive commands or terminate proactive sessions as noted above. The modem 406 may be aware when the mobile terminal 102 is operating in the NTN service mode and may also report that state to the host mobile terminal processor 400, so the modem and / or host processor can thus respond accordingly.

[0082] Furthermore, in both TN and NTN service modes, for one reason or another, the mobile terminal 102 may be operating in an emergency-communication mode, such as placing or engaging in an emergency services call or message communication. In fact, the use of NTN service may itself be for purposes of facilitating emergency communication through the NTN system when sufficient terrestrial coverage does not exist. When the mobile terminal 102 is in the emergency-communication mode, it may also be useful to block proactive commands or terminate proactive sessions as noted above. The modem 406 and / or the host processor 400 may be aware when the mobile terminal 102 is operating in the emergencycommunication mode and can thus respond accordingly.

[0083] Still further, in both TN and NTN service modes, the mobile terminal 102 may be operating with threshold low battery energy, and it may likewise be useful to block proactive commands or terminate proactive sessions in that state as well. A battery level meter (not shown) in the mobile terminal 102 may regularly monitor the level of battery energy of battery 412 and may report that battery level to the host processor 400 and / or to the modem 406, so that the host processor and / or the modem 406. Thus, the modem 406 and / or host processor 400 may be aware when the mobile terminal 102 is operating with battery energy that is at least as low as a predefined level of energy, and can respond accordingly.

[0084] Various other example service modes as well may justify having the mobile terminal take action to block proactive commands and / or to terminate proactive sessions as discussed herein.

[0085] Example embodiments have been described above. Those skilled in the art will understand, however, that changes and modifications may be made to these embodiments without departing from the true scope and spirit of the invention.19

Claims

CLAIMSWhat is claimed is:

1. A method of controlling proactive-command transmission within a mobile terminal, from a subscriber-identity module (SIM) of the mobile terminal, wherein the mobile terminal supports proactive-command transmission from the SIM, the method comprising: determining that the mobile terminal is operating in a service mode in which proactivecommand transmission from the SIM should be blocked; andresponsive to the determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked, sending to the SIM a terminal profile specifying that the mobile terminal does not support proactive-command transmission from the SIM,whereby, the terminal profile specifying that the mobile terminal does not support proactive-command transmission from the SIM is interpretable by the SIM to cause the SIM to not engage in proactive-command transmission.

2. The method of claim 1, wherein the proactive-command transmission from the SIM is proactive-command transmission from the SIM to a modem of the mobile terminal, and wherein the method is carried out by the modem.

3. The method of claim 1, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked comprises determining that the mobile terminal is operating in a non-terrestrialnetwork (NTN) mode.

4. The method of claim 1, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked comprises determining that the mobile terminal is operating with threshold low battery energy.

5. The method of claim 1, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM shouldbe blocked comprises determining that the mobile terminal is operating in an emergencycommunication mode.

6. The method of claim 1, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked comprises determining that the mobile terminal is operating in an airplane mode.

7. The method of claim 1,wherein the terminal profile comprises a bit string in which bits indicate mobile terminal capabilities, wherein each of a plurality of the bits corresponds with a respective proactive-command; andwherein the terminal profile specifying that the mobile terminal does not support proactive-command transmission from the SIM comprises each bit of the plurality of the bits being configured with a value that indicates that the mobile terminal does not support SIM transmission of the respective proactive-command with which the bit corresponds.

8. The method of claim 1, wherein the SIM is an embedded SIM (eSIM), and wherein the proactive-command transmission that the terminal profile specifies the mobile terminal does not support excludes at least a REFRESH proactive command that the SIM supports sending to the mobile terminal in response to a state change at the SIM.

9. The method of claim 8, wherein the proactive-command transmission that the terminal profile specifies the mobile terminal does not support further excludes a PROFILE-STATE-CHANGE REFRESH proactive command that the SIM supports sending to the mobile terminal in response to a mobile network operator (MNO) profile state change at the SIM.

10. The method of claim 1, wherein the SIM is a physical SIM (pSIM), and wherein the terminal profile is a null terminal profile.

11. The method of claim 1, further comprising:thereafter determining that the mobile terminal is no longer operating in the service mode in which the proactive-command transmission from the SIM should be blocked; and21responsive to thereafter determining, reverting configuration of the SIM by sending to the SIM a default terminal profile of the mobile terminal.

12. A computing system configured to control proactive-command transmission within a mobile terminal from a subscriber-identity module (SIM) of the mobile terminal, wherein the mobile terminal supports proactive-command transmission from the SIM, the computing system comprising:at least one processor;non-transitory data storage; andprogram instructions stored in the non-transitory data storage and executable by the at least one processor to carry out the method of any of claims 1-11.

13. At least one non-transitory computer-readable medium storing program instructions executable by at least one processor to carry out the method of any of claims 1-11.

14. A computer program product comprising instructions executable by at least one processor to carry out the method of any of claims 1-11.

15. A method of controlling proactive-command transmission within a mobile terminal, from a subscriber identity module (SIM) in the mobile terminal, the method comprising:determining, by the mobile terminal, that the mobile terminal is operating in a service mode in which proactive-command transmission from the SIM should be blocked; and responsive to the determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked, including by the mobile terminal, in a TERMINAL RESPONSE that the mobile terminal sends to the SIM in response to a proactive command transmitted by the SIM, a response error code that is interpretable by the SIM to cause the SIM to not retransmit the proactive command.

16. The method of claim 15, wherein the proactive-command transmission from the SIM is proactive-command transmission from the SIM to a modem of the mobile terminal, and wherein the method is carried out by the modem.

17. The method of claim 15, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked comprises determining that the mobile terminal is operating in a non-terrestrialnetwork (NTN) mode.

18. The method of claim 15, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked comprises determining that the mobile terminal is operating with threshold low battery energy.

19. The method of claim 15, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked comprises determining that the mobile terminal is operating in an emergencycommunication mode.

20. The method of claim 15, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked comprises determining that the mobile terminal is operating in an airplane mode.

21. The method of claim 15, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked is done upon the mobile terminal receiving the proactive command from the SIM.

22. The method of claim 15, wherein determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked is done before the mobile terminal receives the proactive command from the SIM, and wherein responsively including the response error code in the TERMINAL RESPONSE comprises:responsive to the determining that the mobile terminal is operating in the service mode in which proactive-command transmission from the SIM should be blocked, self-configuring the mobile terminal such that, when the mobile terminal later receives the proactive command from the SIM, the mobile terminal will include the response error code in the TERMINAL RESPONSE; andin accordance with the configuring, including by the mobile terminal the response error code in the TERMINAL RESPONSE when the mobile terminal later receives the proactive command from the SIM.

23. The method of claim 15, further comprising:selecting by the mobile terminal the response error code from a set of available response error codes, wherein including the response error code in the TERMINAL RESPONSE comprises including the selected response error code in the TERMINAL RESPONSE;detecting by the mobile terminal that the including of the selected response error code in the TERMINAL RESPONSE successfully results in the SIM not engaging in proactivecommand retransmission; andresponsive to detecting by the mobile terminal that the response error code successfully results in the SIM not engaging in proactive-command retransmission, self-configuring the mobile terminal such that, next time the mobile terminal receives a proactive command from the SIM while the mobile terminal is operating in the service mode in which the proactive session should be terminated, the mobile terminal will include the same selected response error code when responding to the SIM.

24. A computing system configured to control proactive-command transmission within a mobile terminal, from a subscriber identity module (SIM) in the mobile terminal,, the computing system comprising:at least one processor;non-transitory data storage; andprogram instructions stored in the non-transitory data storage and executable by the at least one processor to carry out the method of any of claims 15-23.

25. At least one non-transitory computer-readable medium storing program instructions executable by at least one processor to carry out the method of any of claims 15-23.

26. A computer program product comprising instructions executable by at least one processor to carry out the method of any of claims 15-23.