Patent Description:
<CIT> discusses a mobile device that operates in a standard mode of operation, or operates in a visually impaired (VI) mode of operation designed for visually impaired users. The display screen of the mobile device remains turned off in the visually impaired (VI) mode of operation. Further, the mobile device can automatically transition from the VI mode to the standard mode if a gaze directed towards the display screen is detected.

<CIT> relates to a band selection method for a dual-band mobile phone having both the functions of a system requiring SIM (subscriber identification module) and a system not requiring the SIM card, for example, PHS (personal handy-phone system). The band selection method detects whether or not a SIM card is mounted when the mobile phone is powered on and automatically sets the operating mode based on SIM card presence detection.

<CIT> relates to a method and an apparatus for testing compatibility of a subscriber identity module (SIM), and a communication module. When the insertion of the user identification card is detected, the method acquires a network system supported by the user identification card. A compatibility test result is generated which comprises the type of the user identification card, the applications supported by the user identification card and the result of the traversal registration.

<CIT> relates to a system and method for controlling power saving functions of wireless communication stations. A radio interface layer between an operating system and a wireless modem controls reinitialization of the operating system and wireless modem when a notification associated with a dispatch communication service is received from a wireless communication network.

The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate examples, instances, and/or aspects of concepts that include the claimed subject matter, and explain various principles and advantages of examples, instances, and/or aspects.

For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of examples.

The apparatus and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the examples, instances, and aspects illustrated so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

A converged wireless communication device (for example, a converged communication device) is a device capable of communicating within multiple communication systems implementing different communication modalities. For example, a converged device may communicate simultaneously in both a Land Mobile Radio (LMR) communication system and a cellular communication system. Some converged devices incorporate multiple subsystems of different types, for example, a cellular subsystem and an LMR subsystem. In some devices, the LMR subsystem can be connected to an entity's private, secure LMR network, while the cellular subsystem may connect to the entity's private cellular system or a public cellular system, which has access to, among other things, the public Internet.

To mitigate information leakage risks, some converged communication devices are configured to operate in independent secure and non-secure operation modes. Different data partitions, using different encryption keys or methods, are used with each mode. Access to public networks is restricted while operating in the secure operation mode. The operation mode is selected upon device powerup, and only secure or non-secure modules are loaded and activated, depending on the operation mode selected.

For certain types of users (for example, public safety personnel), land-mobile communications are a critical aspect of their use of the communication device. Accordingly, an LMR subsystem boots in a relatively short period of time (for example, three to seven seconds). However, a cellular subsystem may take a relatively long time to boot up (for example, thirty seconds or longer). As a consequence, it may be possible for the LMR subsystem to be capable of secure or privileged communications with a private LMR network before it has been established whether the cellular subsystem will operate in a secure or non-secure operation mode. Accordingly, examples described herein provide, among other things, a converged communication device, which allows for the manual or automatic selection of an operation mode for a cellular subsystem while providing operation mode synchronization with an LMR subsystem.

Using examples provided herein, a converged communication device is capable of automatically enabling and disabling communication modalities based on the last operation mode for the device. In one example, the LMR subsystem will powerup and operate to communicate based on the last operation mode, and, if necessary, alter its operation based on a mode notification from the cellular subsystem. Using such examples, users are able to access both cellular and LMR communications, while maintaining desired security levels.

One example provides a converged communication device including a first subsystem and a second subsystem. The first subsystem includes a first electronic processor and a first communication interface configured to communicate wirelessly using a first communication modality. The second subsystem includes a second electronic processor and a second communication interface configured to communicate wirelessly using a second communication modality. The first electronic processor is coupled to the first communication interface and configured, during a startup sequence of the first subsystem, to determine a last operation mode for the first subsystem. The first electronic processor is configured to detect whether a subscriber identity module is installed in the converged communication device. The first electronic processor is configured to, responsive to detecting that a subscriber identity module is installed in the converged communication device, determine a network type for the subscriber identity module. The first electronic processor is configured to control the first communication interface based on the network type and the last operation mode. The first electronic processor is configured to, responsive to detecting that a subscriber identity module is not installed in the converged communication device, control the first communication interface to not communicate wirelessly. The second electronic processor is coupled to the second communication interface and configured, during the startup sequence of the second subsystem, to determine the last operation mode for the first subsystem. The second electronic processor is configured to control the second communication interface based on the last operation mode.

Another example provides a method for operating a converged communication device including a first subsystem and a second subsystem. The method includes determining, during a startup sequence of the first subsystem and with a first electronic processor of the first subsystem, a last operation mode for the first subsystem. The method includes detecting whether a subscriber identity module is installed in the converged communication device. The method includes determining, responsive to detecting that a subscriber identity module is installed in the converged communication device, a network type for the subscriber identity module. The method includes controlling, with the first electronic processor, a first communication interface based on the network type and the last operation mode. The method includes determining, during a startup sequence of the second subsystem and with a second electronic processor of the second subsystem, the last operation mode for the first subsystem. The method includes controlling, with the second electronic processor, a second communication interface based on the last operation mode.

For ease of description, each of the example systems presented herein may be illustrated with a single exemplar of each of its component parts. Some examples may not describe or illustrate all components of the systems. Actual applications of the example systems described herein may include more or fewer of each of the illustrated components, may combine some components, or may include additional or alternative components.

<FIG> illustrates a converged communication device <NUM> according to one example. In the example illustrated, the converged communication device <NUM> includes two subsystems, a cellular subsystem <NUM> and a land mobile radio (LMR) subsystem <NUM>. In the example shown, the cellular subsystem <NUM> and the land mobile radio (LMR) subsystem <NUM> are communicatively coupled to one another via an inter processor link (IPC) <NUM>. As described herein, the cellular subsystem <NUM> is configured to connect to and wirelessly communicate using a first private network <NUM> or a public network <NUM>, based on an operation mode for the cellular subsystem <NUM>, while the LMR subsystem <NUM> is configured to connect to and wirelessly communicate using a second private network <NUM> based on the operation mode for the cellular subsystem <NUM>. <FIG> illustrates a single converged communication device <NUM> configured to communicate wirelessly using the illustrated example networks. This is provided as a non-limiting example. In other instances, the converged communication device <NUM> may communicate using multiple different private and public networks. Although <FIG> illustrates a single converged communication device <NUM>, the methods described herein are applicable to instances where multiple networks of differing types operate to provide communications for tens, hundreds, or thousands of converged communication devices.

The first private network <NUM> is an example communication network, which includes wireless connections, wired connections, or combinations of both, operating according to an industry standard cellular protocol, for example, the Long Term Evolution (LTE) (including LTE-Advanced or LTE-Advanced Pro compliant with, for example, the 3GPP TS <NUM> specification series), or the <NUM> (including a network architecture compliant with, for example, the 3GPP TS <NUM> specification series and a new radio (NR) air interface compliant with the 3GPP TS <NUM> specification series) standard, among other possibilities, and over which, among other things, an open mobile alliance (OMA) push to talk (PTT) over cellular (OMA-PoC), a voice over IP (VoIP), or a PTT over IP (PoIP) application may be implemented. The first private network <NUM> is, for example, a corporate or government network, which provides access only to authorized users of particular organizations or agencies. Consumer cellular devices are not allowed to authenticate to, roam on, or otherwise access the first private network <NUM>.

The public network <NUM> is an example communication network operating according to cellular protocols, as described above with respect to the private network <NUM>. The public network <NUM> is provided by a carrier, which sells access to ordinary consumers (for example, private citizens). Consumer cellular devices from other public networks may be able to roam on or otherwise access the public network <NUM>.

The second private network <NUM> is a land mobile radio network, which includes wireless connections, wired connections, or combinations of both, operating according to the Project <NUM> (P25) standard defined by the Association of Public Safety Communications Officials International (APCO), the Terrestrial Trunked Radio (TETRA) standard defined by the European Telecommunication Standards Institute (ETSI), the Digital Private Mobile Radio (dPMR) standard also defined by the ETSI, among other possibilities, and over which multimedia broadcast multicast services (MBMS), single site point-to-multipoint (SC-PTM) services, or Mission Critical Push-to-talk (MCPTT) services may be provided. The second private network <NUM> may operate using talkgroups, which are virtual radio channels used to provide communication for groups of converged communication devices and other types of LMR subscriber units. The second private network <NUM> is, for example, a corporate or government network, which provides access only to authorized users of particular organizations or agencies. In some instances, the first private network <NUM> and the second private network <NUM> are operated by or for the same entity, for example, a law enforcement agency.

The converged communication device <NUM> may include other components, for example, one or more antennas, a land-mobile radio modem, a baseband modem, a microphone, a speaker, and other processors and chipsets (not shown).

In the illustrated example, the cellular subsystem <NUM> includes an electronic processor <NUM>, a memory <NUM>, an input/output interface <NUM>, a firmware <NUM>, a communication interface <NUM>, and a subscriber identity module <NUM>. The illustrated components, along with other various modules and components are coupled to each other by or through one or more control and/or data buses that enable communication therebetween (for example, a communication bus <NUM>).

The electronic processor <NUM> obtains and provides information (for example, from the memory <NUM>, the input/output interface <NUM>, the firmware <NUM>, and combinations thereof), and processes the information by executing one or more software instructions or modules, capable of being stored, for example, in a random access memory ("RAM") area of the memory <NUM> or a read only memory ("ROM") of the memory <NUM>, the firmware <NUM>, or another non-transitory computer readable medium (not shown). The software can include firmware, one or more applications, program data, filters, rules, one or more program modules, and other executable instructions. The electronic processor <NUM> is configured to retrieve, from the memory <NUM> and the firmware <NUM>, and execute, among other things, software related to the control processes and methods described herein.

The memory <NUM> can include one or more non-transitory computer-readable media and includes a program storage area and a data storage area. The program storage area and the data storage area can include combinations of different types of memory, as described herein. In the example illustrated, the memory <NUM> stores, among other things, a secure partition <NUM> and a non-secure partition <NUM>. As described herein, the electronic processor <NUM> boots the cellular subsystem <NUM> using either the secure partition <NUM> or the non-secure partition <NUM> based on an operation mode for the cellular subsystem <NUM>.

The secure partition <NUM> is used to store and allow to access data (for example, the user data <NUM>) and applications (for example, the secure applications <NUM>) securely on the converged communication device <NUM> or in a remote environment (for example, a cloud-based secure computing environment accessible via the first private network <NUM>). The secure partition <NUM> is, for example, an authenticated, encrypted area of the memory <NUM>, which can be used to insulate sensitive information from non-secure partition <NUM>. The secure partition <NUM> allows a user of the converged communication device <NUM> to access the secured data, applications, or remote environments, but only allows authorized functions or applications on the converged communication device <NUM> to access data, applications or other functions inside the secure partition <NUM> or the remote environment. For example, the LMR subsystem <NUM> may be able to access or store data from the secure partition <NUM>. Similarly, applications running on the secure partition <NUM> (for example, a computer aided dispatch client) may be able to operate the LMR subsystem <NUM> to communicate via the second private network <NUM>.

The non-secure partition <NUM> is used to store and allow to access data (for example, the user data <NUM>) and applications (for example, the applications <NUM>) on the converged communication device <NUM> or in a remote environment (for example, a cloud-based computing environment accessible via the public network <NUM> or the Internet). In some instances, the non-secure partition <NUM> may be used to provide a user access to smart telephone functions and applications, for example, when the private network <NUM> or another private cellular network is unavailable. In other instances, the non-secure partition <NUM> may provide an official user with a non-official personal device persona to use while not operating in an official capacity, for example, rather than operating a bring your own device (BYOD) environment. Regardless of its purpose, the non-secure partition <NUM> is not allowed access to the private networks to which the secure partition <NUM> is allowed access. Similarly, the non-secure partition <NUM> is not allowed to access the functions of the LMR subsystem <NUM>.

In this description, the terms "secure" and "non-secure" are used to distinguish, in a general way, between how data and applications in those partitions may be secured from unauthorized access, for example, through the use of different authentication mechanisms, encryption mechanisms, network security mechanisms, and the like. The terms, however, are not meant to imply that anything so labeled is superior or inferior. "Secure" partitions utilize mechanisms that provide a relatively higher security level relative to "non-secure" partitions. The converse is also true. Partitions labeled "non-secure" do not lack all security, but rather utilize mechanisms that provide a relatively lower security level relative to "secure" partitions.

The input/output interface <NUM> is configured to receive input and to provide system output. The input/output interface <NUM> obtains information and signals from, and provides information and signals to, (for example, over one or more wired and/or wireless connections) devices both internal and external to the converged communication device <NUM>. The input/output interface <NUM> may include one or more human machine interfaces that enable a user to interact with and control the cellular subsystem <NUM> and other aspects of the converged communication device <NUM>. For example, the input/output interface <NUM> may include a display (for example, a liquid crystal display (LCD) touch screen, an organic light-emitting diode (OLED) touch screen, and the like) and suitable physical or virtual selection mechanisms (for example, buttons, keys, knobs, switches, and the like). In some instances, the input/output interface <NUM> implements a graphical user interface (GUI) (for example, generated by the electronic processor <NUM>, from instructions and data stored in the memory <NUM>, and presented on a suitable display), that enables a user to interact with the converged communication device <NUM>.

In one instance, the firmware <NUM> is a non-volatile, electrically-rewritable computer storage medium, which includes a bootloader <NUM> and an operating system <NUM>. In some instances, all or part of the bootloader <NUM>, the operating system <NUM>, or both may be stored in a read only memory of the memory <NUM> or in another suitable electronic memory.

The communication interface <NUM> includes components operable to communicate wirelessly with the first private network <NUM>, the public network <NUM>, and other networks using a cellular communication modality, as described herein. The communication interface <NUM> may include, for example, one or more baseband processors, transceivers, antennas, as well as various other digital and analog components, which for brevity are not described herein and which may be implemented in hardware, software, or a combination of both. Some instances may include separate transmitting and receiving components, for example, a transmitter and a receiver, instead of or in addition to a combined transceiver.

The subscriber identity module (SIM) <NUM> includes various subscription profiles, access credentials, and configuration information (for example, the network type <NUM>) used by the cellular subsystem <NUM> to authenticate to and communicate via the first private network <NUM>, the public network <NUM>, and other networks using a cellular communication modality. In some instances, the SIM <NUM> is removable from the converged communication device <NUM>. In one example, the SIM <NUM> is a universal integrated circuit card (UICC).

In one example, the electronic processor <NUM> is configured to, upon powerup or reboot of the converged communication device <NUM>, execute the bootloader <NUM>. The bootloader <NUM> is configured to initiate start-up of the cellular subsystem <NUM> by retrieving the operating system <NUM> from the firmware <NUM> and placing it into memory <NUM>. As described herein, the electronic processor <NUM> reads the operating system <NUM> from the memory <NUM> and boots the operating system <NUM> using either the secure partition <NUM> or the non-secure partition <NUM>, based on a selected operation mode for the cellular subsystem <NUM>. In some instances, the operating system <NUM> remains in, and is executed from, the firmware <NUM>. In one example, the bootloader <NUM> operates to read and write data to and from the cellular subsystem <NUM> and the LMR subsystem <NUM> via the inter-processor communication link <NUM>.

The operating system <NUM> is, for example, a Unix operating system variant such as Android™. Before the cellular subsystem <NUM> can be used (for example, but executing applications stored on one of the partitions), it must boot. The boot time for the operating system <NUM> (that is, the time between power up and when the operating system <NUM> is ready for operation) is, for certain operating systems, for example, thirty seconds or longer.

The LMR subsystem <NUM> includes an electronic processor <NUM>, a memory <NUM>, an input/output interface <NUM>, a firmware <NUM>, and a communication interface <NUM>. The illustrated components, along with other various modules and components are coupled to each other by or through one or more control and/or data buses that enable communication therebetween (for example, a communication bus <NUM>). The electronic processor <NUM>, memory <NUM>, input/output interface <NUM>, and firmware <NUM> are similar and operate similarly to their respective counterparts in the cellular subsystem <NUM>.

In one example, the input/output interface <NUM> includes a push-to-talk (PTT) button for activating components of the communication interface <NUM> to transmit voice or other communications (not shown). The PTT button may be implemented, for example, as a physical switch or by using a soft key or icon in the graphical user interface on a display of the input/output interface <NUM> or, as noted above, the input/output interface <NUM>.

The communication interface <NUM> includes components operable to communicate wirelessly with the second private network <NUM> and other networks using a land mobile radio communication modality, as described herein (for example, using or according to the LMR data <NUM> and other LMR applications <NUM>). The communication interface <NUM> may include, for example, one or more baseband processors, transceivers, antennas, as well as various other digital and analog components, which for brevity are not described herein and which may be implemented in hardware, software, or a combination of both. Some instances may include separate transmitting and receiving components, for example, a transmitter and a receiver, instead of or in addition to a combined transceiver.

In one example, the electronic processor <NUM> is configured to, upon powerup or reboot of the converged communication device <NUM>, execute the bootloader <NUM>. The bootloader <NUM> is configured to initiate start-up of the LMR subsystem <NUM> by retrieving the operating system <NUM> from the firmware <NUM> and placing it into memory <NUM>. In one example, the operating system <NUM> contains or executes software for communicating over a land mobile radio network (for example, using the LMR data <NUM> and other LMR applications <NUM>). In one example, the operating system <NUM> is a real-time operating system (RTOS). Similar to the cellular subsystem <NUM>, before the LMR subsystem <NUM> can be used, it must boot. The boot time for the LMR operating system <NUM> may be much shorter than the boot time for cellular operating system <NUM>. In some instances, for example, the boot time for the operating system <NUM> may be between three and seven seconds.

When the converged communication device <NUM> is powered up or rebooted, both the cellular subsystem <NUM> and the LMR subsystem <NUM> begin their startup routines (also referred to herein as startup sequences). Before either of the subsystems and its respective functions can be used, it must complete start-up. The startup routines for the subsystems include the booting of the processor and the loading of their respective operating systems. As noted above, the LMR subsystem <NUM> may boot up significantly faster than the cellular subsystem <NUM>. In one example, the start-up for the LMR subsystem <NUM> completes well before the start-up for the cellular subsystem <NUM>. As a consequence, it may be possible for the LMR subsystem <NUM> to be capable of secure or privileged communications with the second private network <NUM> before it has been established whether the cellular subsystem <NUM> will operate in a secure or non-secure operation mode.

<FIG> illustrates one example method <NUM> for operating a converged communication device. The method <NUM> is described as being executed by the electronic processors <NUM> and <NUM> (also referred to herein as the first and second electronic processors). However, in some examples, aspects of the method <NUM> may be performed by other components of the converged communication device <NUM>. For example, some or all of the method <NUM> may be performed by the electronic processors in conjunction with their respective bootloaders. As an example, the method <NUM> is described in terms of a first subsystem (the cellular subsystem <NUM>) and a second subsystem (the LMR subsystem <NUM>).

At block <NUM>, the converged communication device <NUM> boots. The bootup may be the result of a powerup from powered off state or the result of a reboot initiated during a previous powered on state. As illustrated in <FIG>, the first and second subsystems perform their respective powerup sequences as a result of the converged communication device <NUM> booting.

At block <NUM>, the electronic processor <NUM> determines a last operation mode for the first subsystem (for example, the cellular subsystem <NUM>). An operation mode of the first subsystem may be, for example, a secure mode and a non-secure mode. For example, when the first subsystem is operating in a secure mode, it has been booted using the secure partition <NUM>, and when the first subsystem is operating in a non-secure mode, it has been booted using the non-secure partition <NUM>. The last operation mode identifies the operation mode of the first subsystem immediately prior to the current powerup sequence. For example, if the cellular subsystem <NUM> is operating in a secure mode (that is, from the secure partition <NUM>) and is powered down, the last operating mode when it powers up is the secure mode. Similarly, if the cellular subsystem <NUM> is operating in a non-secure mode (that is, from the non-secure partition <NUM>) and is rebooted, the last operating mode when it begins booting up is the non-secure mode.

In one example, the electronic processor <NUM> determines the last operation mode by reading from a non-volatile memory of the cellular subsystem <NUM>. For example, a sequence of bits identifying the current operation mode may be written to a boot sector of the memory <NUM> while the cellular subsystem <NUM> is operating. Upon a subsequent bootup, the current operation mode that was saved in the boot sector represents the last operation mode of the cellular subsystem <NUM>.

In another example, the last operation mode is selected by the user of the converged communication device prior to device reboot and the electronic processor <NUM> determines the last operation mode by retrieving the user-selected operation mode from a memory of the converged communication device (for example, the memory <NUM>). For example, as described herein, a power menu of the device may allow for a user to select the operation mode prior to a reboot. In such instances, the "last operation mode" may not refer to the last operation mode in which the device was operating, but rather the last operation mode selected by the user.

At block <NUM>, the electronic processor <NUM> detects whether a subscriber identity module is installed in the converged communication device <NUM>. For example, the electronic processor <NUM> may put out a query on the bus <NUM> and listen for a response from the SIM <NUM>. In another example, the SIM <NUM> may trigger a signal to the electronic processor <NUM> when present in the device.

At block <NUM>, the electronic processor <NUM>, responsive to detecting that a subscriber identity module is installed in the converged communication device (at block <NUM>), determines a network type for the subscriber identity module. For example, the electronic processor <NUM> may query the SIM <NUM> and receive the network type <NUM> in reply. In another example, the powerup sequence may include a step where the SIM <NUM> provides, among other things, the network type <NUM> to the electronic processor <NUM>.

At block <NUM>, the electronic processor <NUM> controls the first communication interface (for example, the communication interface <NUM>) based on the network type and the last operation mode. For example, where the last operation mode was a secure mode and the network type is private, the electronic processor <NUM> may control the first communication interface to communicate wirelessly with a private communication network (for example, the first private network <NUM>) using a first communication modality (for example, an LTE cellular protocol). Other examples of controlling the first communication interface based on the network type and the last operation mode are described below with respect to <FIG> and <FIG>.

At block <NUM>, the electronic processor <NUM>, responsive to detecting that a subscriber identity module is not installed in the converged communication device (at block <NUM>), controls the first communication interface (for example, the communication interface <NUM>) to not communicate wirelessly. For example, the electronic processor <NUM> may issue a command to the communication interface <NUM> to enter an "airplane mode" (that is, to cease transmitting and receiving).

At block <NUM>, as the converged communication device is booting (at block <NUM>), the electronic processor <NUM>, during the powerup sequence, determines the last operation mode for the first subsystem. As noted, upon bootup, the LMR subsystem <NUM> is not able to access the cellular subsystem <NUM> (and vice versa). Accordingly, the last operation mode is stored in the LMR subsystem <NUM>. For example, the electronic processor <NUM> may retrieve the last operation mode information from a non-volatile memory of the LMR subsystem <NUM> (for example, the memory <NUM>). In one example, the last operation mode stored in the memory <NUM> was received (as the then-current operation mode) from the cellular subsystem <NUM> during the prior operation cycle. In another example, as described herein, the last operation mode is selected by a user of the converged communication device <NUM> and stored in the memory <NUM>. Because, as described herein, the last operation mode may be user selected, from the standpoint of the second subsystem <NUM>, the last operation mode for the first subsystem <NUM> is the last known operation mode, and may not be the actual operation mode, in which the first subsystem <NUM> was last operating.

At block <NUM>, the electronic processor <NUM> controls the second communication interface (for example, the communication interface <NUM>) based on the last operation mode. For example, where the last operation mode was a secure mode, the electronic processor <NUM> may control the second communication interface to communicate wirelessly with a second private communication network (for example, the second private network <NUM>) using a second communication modality (for example, a digital LMR protocol). Other examples of controlling the second communication interface based on the last operation mode are described below with respect to <FIG> and <FIG>.

<FIG> illustrates another example method <NUM> for operating a converged communication device. The method <NUM> is described as being executed by the converged communication device <NUM> and, in particular, by the electronic processors <NUM> and <NUM>. However, in some examples, aspects of the method <NUM> may be performed by other components of the converged communication device <NUM>. For example, some or all of the method <NUM> may be performed by the electronic processors in conjunction with their respective bootloaders. As an example, the method <NUM> is described in terms of a first subsystem (the cellular subsystem <NUM>) and a second subsystem (the LMR subsystem <NUM>).

At block <NUM>, the converged communication device <NUM> boots. The bootup may be the result of a powerup from powered off state or the result of a reboot initiated during a previous powered on state. The first and second subsystems perform their respective powerup sequences as a result of the converged communication device <NUM> booting.

At block <NUM>, the converged communication device <NUM> determines the last operation mode for the cellular subsystem <NUM>. As described above with respect to <FIG>, in some instances, this determination is made by both electronic processors <NUM> and <NUM>. In some instances, as described herein, the last operation mode is selected by a user of the converged communication device <NUM>.

At block <NUM>, when the last operation mode was a secure mode, the electronic processor <NUM> detects a SIM and, if detected, determines a network type (for example, public or private).

At block <NUM>, responsive to determining that the last operation mode for the first subsystem was a secure mode and that the network type is private, the electronic processor <NUM> initiates a boot up sequence for a secure data partition of the first subsystem and controls the first communication interface to communicate wirelessly with a private communication network using the first communication modality. For example, the electronic processor <NUM> may load and execute the bootloader <NUM> to launch the operating system <NUM> using the secure partition <NUM> and, when the operating system <NUM> launch has progressed sufficiently, control the communication interface <NUM> to communicate wirelessly with the first private network <NUM> using an LTE cellular protocol. In addition, in one example, responsive to determining that the last operation mode for the first subsystem was the secure mode, the electronic processor <NUM> controls the second communication interface to communicate wirelessly with a second private communication network (for example, the second private network <NUM>) using a second communication modality (for example, a digital LMR protocol), and initiates a secure inter-processor communication link with the first subsystem (as described with respect to <FIG>).

At block <NUM>, responsive to determining that the last operation mode for the first subsystem was a non-secure mode and that either the network type is commercial (that is, public) or that there is no SIM installed, the electronic processor <NUM> initiates a boot up sequence for a non-secure data partition of the first subsystem and controls the first communication interface to communicate wirelessly with a public communication network using the first communication modality. For example, the electronic processor <NUM> may load and execute the bootloader <NUM> to launch the operating system <NUM> using the non-secure partition <NUM> and, when the operating system <NUM> launch has progressed sufficiently, control the communication interface <NUM> to communicate wirelessly with the public network <NUM> using an LTE cellular protocol. In addition, in one example, responsive to determining that the last operation mode for the first subsystem was the non-secure mode, the electronic processor <NUM> controls the second communication interface to not communicate wirelessly and initiates a secure inter-processor communication link with the first subsystem (as described with respect to <FIG>).

In some examples, the electronic processor <NUM> is configured to retrieve a user boot mode selection and control the communication interface <NUM> based on the network type, the last operation mode, and the user boot mode selection. The user boot mode determines whether a user of the converged communication device <NUM> can select the operation mode for the device. In one example, the user boot mode may be set to manual (that is, the user is allowed to switch operation modes) or automatic (that is, the operation mode is set based on the type of SIM inserted into the device). In some instances, the user boot mode also determines how a power menu for the converged communication device is presented. For example, when the user boot mode is manual, a power menu may display the current operation mode (that is, secure or non-secure) and graphical user interface control elements that allow the user to select between restarting in the current operation mode or switching from the current operation mode to another available operation mode and restarting the device. In another example, when the user boot mode is automatic, a power menu may display the current operation mode (that is, secure or non-secure) and a graphical user interface control element that allows the user to restart in the current operation mode.

Returning to <FIG>, responsive to determining that the last operation mode for the first subsystem was a secure mode (at block <NUM>), determining that the user boot mode selection is manual (at <NUM>), and determining that either the network type is commercial (that is, public) or that there is no SIM installed (at block <NUM>), the electronic processor <NUM> (at block <NUM>) initiates a boot up sequence for a secure data partition of the first subsystem, and controls the first communication interface to not communicate wirelessly.

At block <NUM>, responsive to determining that the last operation mode for the first subsystem was a secure mode (at block <NUM>), determining that the user boot mode selection is automatic (at <NUM>) and determining that the network type is commercial (that is, public), the electronic processor <NUM> sets the last operation mode for the first subsystem to indicate a non-secure mode (for example, by writing a value to the memory <NUM>), provides a mode notification indicating the non-secure mode to the second subsystem via an inter-processor communication link (for example, as described with respect to <FIG>), and initiates a reboot sequence for the first subsystem (at block <NUM>). In one example, the electronic processor <NUM> provides the mode notification using a suitable electronic messaging protocol. In another example, the inter-processor communication link is a connection between general-purpose input/outputs (GPIOs) of the electronic processor <NUM> and the electronic processor <NUM> and the electronic processor <NUM> provides the mode notification by application of logic levels, which are predetermined to indicate particular operation modes. Upon receipt of such notification, the electronic processor <NUM> writes the operation mode to a non-volatile memory. In some examples, a reboot is not initiated and ordinary device operations resume.

In alternative examples, responsive to determining that the last operation mode for the first subsystem was a secure mode (at block <NUM>), determining that the user boot mode selection is automatic (at <NUM>) and that there is no SIM installed (at block <NUM>), the electronic processor <NUM> sets the last operation mode for the first subsystem to indicate a non-secure mode (for example, by writing a value to the memory <NUM>), provides a mode notification indicating the non-secure mode to the second subsystem via an inter-processor communication link (for example, as described with respect to <FIG>), and initiates a reboot sequence for the first subsystem (at block <NUM>).

At block <NUM>, responsive to determining that that the last operation mode for the first subsystem was a non-secure mode (at block <NUM>), determining that the user boot mode selection is manual (at block <NUM>), and determining that the network type is private (at block <NUM>), the electronic processor <NUM> initiates a boot up sequence for a non-secure data partition of the first subsystem, and controls the first communication interface to not communicate wirelessly. The electronic processor <NUM>, responsive to determining that the last operation mode for the first subsystem was a non-secure mode (at block <NUM>), controls the second communication interface to not communicate wirelessly.

At block <NUM>, responsive to determining that that the last operation mode for the first subsystem was a non-secure mode (at block <NUM>), determining that the user boot mode selection is automatic (at block <NUM>), and determining that the network type is private (at block <NUM>), the electronic processor <NUM> sets the last operation mode for the first subsystem to indicate a secure mode (for example, by writing a value to the memory <NUM>), provides a mode notification indicating the secure mode to the second subsystem via an inter-processor communication link (for example, as described with respect to <FIG>), and initiates a reboot sequence for the first subsystem (at block <NUM>). In some examples, a reboot is not initiated and ordinary device operations resume.

At block <NUM>, the converged communication device <NUM> boots. The bootup may be the result of a powerup from powered off state or the result of a reboot initiated during a previous powered on state (for example, as described with respect to <FIG>). The first and second subsystems perform their respective startup sequences as a result of the converged communication device <NUM> booting.

At block <NUM>, the electronic processor <NUM> selects an operational mode for the cellular (first) subsystem <NUM>. In one example, the selection is performed according to the method <NUM>, as described herein (that is, automatically or manually).

At block <NUM>, the electronic processor <NUM> provides a mode notification indicating the selected mode to the LMR (second) subsystem via an inter-processor communication link, as described herein.

At block <NUM>, the electronic processor <NUM> mounts either the secure partition <NUM> or the non-secure partition <NUM> based on the mode selection (at block <NUM>) and continues with device boot (at block <NUM>).

As noted, the LMR subsystem <NUM> typically boots faster than the cellular subsystem <NUM>. In such instances, the LMR subsystem <NUM> will powerup according to the sequence <NUM>, based on the last operation mode, and, if necessary, alter its operation based on the mode notification from the cellular subsystem <NUM>, as described below.

At block <NUM>, the electronic processor <NUM> determines the last operation mode, as described herein.

At block <NUM>, responsive to determining that the last operation mode for the first subsystem was the secure mode, the electronic processor <NUM> controls the second communication interface to communicate wirelessly with a second private communication network (for example, the second private network <NUM>) using a second communication modality (for example, an LMR protocol). In some instances, the electronic processor <NUM> retrieves from the firmware <NUM> a talkgroup identifier and controls the second communication interface to join the identified talkgroup upon joining the LMR network.

As described herein, it is possible, in some instances, for the cellular subsystem to boot into a non-secure operation mode after having operated in a secure operation mode. Because the LMR subsystem <NUM> typically boots faster than the cellular subsystem <NUM>, it will allow secure LMR communications based on the knowledge of the last operation mode. However, to prevent a non-secure operation of the cellular subsystem <NUM> from accessing the LMR systems, the electronic processor, at block <NUM>, initiates a secure inter-processor communication link with the first subsystem. Such a communication link only allows the electronic processor <NUM> to receive mode notification messages and prevents access to other aspects of the LMR subsystem <NUM> by the cellular subsystem <NUM>. As illustrated in <FIG>, when the last operation mode is a non-secure mode, the electronic processor <NUM> does not enable the communication interface <NUM>, but instead initiates a secure inter-processor communication link with the first subsystem.

At block <NUM>, the electronic processor <NUM> waits to receive the mode selection notification from the cellular subsystem <NUM>.

At block <NUM>, responsive receiving the secure mode notification via the inter-processor communication link with the first subsystem (at block <NUM>), controls the second communication interface to communicate wirelessly with a second private communication network using the second communication modality, enabling it in the case where it had yet to be started (at block <NUM>) and continues to operate in the secure mode (with LMR communications active) at block <NUM>.

At block <NUM>, responsive to receiving the non-secure mode notification via the inter-processor communication link with the first subsystem (at block <NUM>), the electronic processor <NUM> controls the second communication interface to not communicate wirelessly, disabling it in the case where it was already started (at block <NUM>) and continues to operate in the non-secure mode (with LMR communications turned off) at block <NUM>.

In the description above, the terms "cellular" and "land mobile radio" or "LMR" are used to distinguish between components included in a converged communication device that implement different communication modalities, for example, the long term evolution (LTE) cellular protocol and the Terrestrial Trunked Radio (TETRA) land mobile radio protocol. In addition, the terms "first" and "second" are used, in some instances, in place of the terms "cellular" and "LMR. " These terms, however, are not meant to imply that any of the components so labeled are superior or inferior to other components or arranged in a particular order. Nonetheless, in some of the foregoing examples, the "second" LMR subsystem <NUM> is subordinate to the "first" cellular subsystem <NUM> in the sense that the cellular subsystem <NUM> may include software and hardware for controlling certain aspects of the LMR subsystem <NUM> or of the converged communication device <NUM>, upon which the LMR subsystem <NUM> depends.

The systems and methods described herein, although described in terms of a converged communication device, are not limited in their applicability to a converged communication device. In view of the description above, a person of ordinary skill in the art could implement the examples described in many different types of electronic devices that include multiple subsystems where one subsystem is capable of booting multiple partition types and another subsystem is not. For example, a device capable of dual communications, including an LMR subsystem and a broadband (though not necessarily cellular) capable subsystem could operate using the methods described herein.

In the foregoing specification, specific examples have been described. However, one of ordinary skill in the art appreciates that various modifications and changes may be made without departing from the scope of the invention as set forth in the claims below.

Moreover, in this document relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "has," "having," "includes," "including," "contains," "containing," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises. a," "includes. a," or "contains. a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms "a" and "an" are defined as one or more unless explicitly stated otherwise herein. The terms "substantially," "essentially," "approximately," "about," or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting example the term is defined to be within <NUM>%, in another example within <NUM>%, in another example within <NUM>% and in another example within <NUM>%. The term "coupled" as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that way but may also be configured in ways that are not listed.

It will be appreciated that some examples may be comprised of one or more generic or specialized processors (or "processing devices") such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein.

Moreover, an example may be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (for example, comprising a processor) to perform a method as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.

Claim 1:
A method (<NUM>) for operating a converged communication device (<NUM>) including a first subsystem (<NUM>) and a second subsystem (<NUM>), the method comprising:
Determining (<NUM>), during a startup sequence of the first subsystem (<NUM>) and with a first electronic processor (<NUM>) of the first subsystem (<NUM>), a last operation mode for the first subsystem (<NUM>);
Detecting (<NUM>) whether a subscriber identity module is installed in the converged communication device (<NUM>);
Determining (<NUM>), responsive to detecting that a subscriber identity module is installed in the converged communication device (<NUM>), a network type for the subscriber identity module;
Controlling (<NUM>), with the first electronic processor (<NUM>), a first communication interface (<NUM>) based on the network type and the last operation mode;
Determining (<NUM>), during a startup sequence of the second subsystem (<NUM>) and with a second electronic processor (<NUM>) of the second subsystem (<NUM>), the last operation mode for the first subsystem (<NUM>); and
Controlling (<NUM>), with the second electronic processor (<NUM>), a second communication interface (<NUM>) based on the last operation mode.